SX chips cannot be updated ....

[pegast73]

Hi. I need advice. I have SXCore chips that have Spacecraft_nx version 0.1 installed since purchase. I would like to reinstall them at 0.2 or even the new 0.21_hotfix for now, but the installation of the new fw will not start at all via USB. I also bought a GD-link 0B programmer and the situation is the same there. Those chips where there was still fw SX, so they can be reinstalled, the installation will still start. But those who came to me with a rocket do not react at all. Let me remind you that these are originally SX chips and no longer new HWFLY clones. Thanks for your help.

[sthetix]

are you confident that your chip is the real sx produc? btw space 0.2.0 is for oled, not for other variants

On Tue, Jan 25, 2022, 19:00 pegast73 @.***> wrote:

Hi. I need advice. I have SXCore chips that have Spacecraft_nx version 0.1 installed since purchase. I would like to reinstall them at 0.2 or even the new 0.21_hotfix for now, but the installation of the new fw will not start at all via USB. I also bought a GD-link 0B programmer and the situation is the same there. Those chips where there was still fw SX, so they can be reinstalled, the installation will still start. But those who came to me with a rocket do not react at all. Let me remind you that these are originally SX chips and no longer new HWFLY clones. Thanks for your help.

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23DZZIB3DZ33ZTZUZW2TUX2GFRANCNFSM5MYBWA7Q . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[pegast73]

I will explain the reason for the update. I still have a few chips that started selling as the first clones but they were sanded SX chips with fw Spacecraft-nx but probably the fw is modified somehow. The problem with them is that when the chip is used and the sysnand is updated to the newer OFW, after the update the chip no longer works, the console always boots to the OFW and does not monitor the micrSD card, it ignores it. When the card in the console is not inserted, no rocket or NO SD will appear, but it will start to OFW. One dev advised me how to solve this, using the UartAssist program and delete payload.bin from sysnand, because after the update it will write there and a broken glitch chip. So after each sysnand update, OFW, you need to disassemble the console again and clean up the sysnand. But since these chips can't be updated because even if windows sees them but the update doesn't want to run, I can't remove any bugs in fw that's on the chip. I assume that the spaceraft_nx is modified there, because after connecting to GD-link 0B the LED flashes, lights up red and cannot be connected so that I can change fw in the chip. The chips that I myself upgraded from SX to Spacecraft_nx do not behave so badly, they work correctly and can also be updated fw into them without any problems. I enclose a photo of the problem chip in question ...

[sthetix]

The thing is , you want to install this chip to OLED?

On Tue, 25 Jan 2022 at 21:04, pegast73 @.***> wrote:

I will explain the reason for the update. I still have a few chips that started selling as the first clones but they were re-grounded SX chips with fw Spacecraft-nx but probably the fw is modified somehow. The problem with them is that when the chip is used and the sysnand is updated to the newer OFW, after the update the chip no longer works, the console always boots to the OFW and does not monitor the micrSD card, it ignores it. When the card in the console is not inserted, no rocket or NO SD will appear, but it will start to OFW. One dev advised me how to solve this, using the UartAssist program and delete payload.bin from sysnand, because after the update it will write there and a broken glitch chip. So after each sysnand update, OFW, you need to disassemble the console again and clean up the sysnand. But since these chips can't be updated because even if windows sees them but the update doesn't want to run, I can't remove any bugs in fw that's on the chip. I assume that the spaceraft_nx is modified there, because after connecting to GD-link 0B the LED flashes, lights up red and cannot be connected so that I can change fw in the chip. The chips that I myself upgraded from SX to Spacecraft_nx do not behave so badly, they work correctly and can also be updated fw into them without any problems. I enclose a photo of the problem chip in question ... [image: 20220125_143718] https://user-images.githubusercontent.com/90899762/150991305-6e7b684d-ac49-426a-a5d5-cde192f3e110.jpg

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3#issuecomment-1021214072, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23DZ6HCWCD6JMVHYS5ATUX2UWHANCNFSM5MYBWA7Q . You are receiving this because you commented.Message ID: @.***>

[pegast73]

No, I haven't even had OLED in my hands yet. The chips will go to V2 Mariko. I know that OLED is being solved here, but I've been watching you for a long time and I don't know who else could help me, I take you as an expert ....

[sthetix]

as i said previously, u don't /. never uodate the firmware to 0.2.0

use spacecraft 0.1.0 for v2

On Tue, Jan 25, 2022, 21:23 pegast73 @.***> wrote:

No, I haven't even had OLED in my hands yet. The chips will go to V2 Mariko. I know that OLED is being solved here, but I've been watching you for a long time and I don't know who else could help me, I take you as an expert ....

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3#issuecomment-1021232650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23DYML6EUQNY46PIEU2DUX2W6DANCNFSM5MYBWA7Q . You are receiving this because you commented.Message ID: @.***>

[pegast73]

In the problematic ones, there is about 0.05 or some beta or modified version. So even if I wanted to flash to 0.1, I still can't. I don't believe that there is the 0.1 in them, which is normally available for download, as they are the original SX chips and also someone had to upgrade them to a rocket before selling to Ali ... Maybe the one who changed them from SX to rocket locked them so that they could no longer be given higher than 0.1.0

[sthetix]

try flashing with the gdlink then.

On Tue, Jan 25, 2022, 21:41 pegast73 @.***> wrote:

In the problematic ones, there is about 0.05 or some beta or modified version. So even if I wanted to flash to 0.1, I still can't. I don't believe that there is the 0.1 in them, which is normally available for download, as they are the original SX chips and also someone had to upgrade them to a rocket before selling to Ali ...

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3#issuecomment-1021252819, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23D57VIYJY3XYHMQ7NXTUX2ZCDANCNFSM5MYBWA7Q . You are receiving this because you commented.Message ID: @.***>

[pegast73]

If I could flash them to public 0.1.0 and verify my theory about a faulty or bluffed fw, I would be better. After all, these are the same chips that I have with the original fw SX, which can be easily changed fw ....

[pegast73]

try flashing with the gdlink then.

It doesn't work, the ice turns red, it goes out and gdlink doesn't see them, not something to flash. It's a mystery ...

[sthetix]

Gd link should always detect the chip if it doesn't then your chip is not the original sx core, but the hwfly core.

On Tue, 25 Jan 2022 at 21:48, pegast73 @.***> wrote:

It doesn't work, the ice turns red, it goes out and gdlink doesn't see them, not something to flash.

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3#issuecomment-1021259473, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23DYJZWXFNZ2G3PREWVLUX2Z3NANCNFSM5MYBWA7Q . You are receiving this because you commented.Message ID: @.***>

[pegast73]

Depending on the contents of the motherboard and the appearance, it should be the original SX C.

[sthetix]

if it is a true sx product you can flash it

On Tue, Jan 25, 2022, 22:29 pegast73 @.***> wrote:

Depending on the contents of the motherboard and the appearance, it should be the original SX C.

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3#issuecomment-1021308376, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23DYS4SVLPUNQ2BQWKA3UX26WRANCNFSM5MYBWA7Q . You are receiving this because you commented.Message ID: @.***>

[pegast73]

I already understand that, clone makers also sell the original SX chips as HWFLY, they put their deliberately modified software there so that they cannot be read and written and therefore not updated. He found an article where you also discussed. You can lock it up, because for me there is no other way than to accept it and tolerate such insidious clones ....

[sthetix]

have you tried flashing the clones with RPI? the guide is on gbatemp

On Wed, Jan 26, 2022, 20:57 pegast73 @.***> wrote:

I already understand that, clone makers also sell the original SX chips as HWFLY, they put their deliberately modified software there so that they cannot be read and written and therefore not updated. He found an article where you also discussed. You can lock it up, because for me there is no other way than to accept it and tolerate such insidious clones ....

— Reply to this email directly, view it on GitHub https://github.com/sthetix/OLED-DIAGRAM/issues/3#issuecomment-1022221244, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23D4BQRO5ZOOUD5UT5OLUX74VZANCNFSM5MYBWA7Q . You are receiving this because you commented.Message ID: @.***>