Given that this is not some kind of prank or splash screen, which disappears after a few seconds (and should go away when trying to boot without SD), this is not good news.
This is very bad. See [3dbrew] Bootloader Error Codes→ NCSD header in sector 0 is corrupt (failed signature check).
I have some different ideas how this can happen:
Please do the following
If the NAND chip is failing, it might work after flashing a backup or repairing with CTRTransfer Type D9, and sooner or later the same will happen again.
Good luck!
This is very bad. See [3dbrew] Bootloader Error Codes→ NCSD header in sector 0 is corrupt (failed signature check).
I have some different ideas how this can happen:
- Experiments which should NEVER be done →
- Malware
(I've never heard of 3DS malware in the wild↓see below… about the Gateway brick code↓, but it would be trivial to built this) →
- Dying NAND chip →
Please do the following
- Provide an empty, FAT32 formatted SD and check it with h2testw or F3. If the SD passed the check, delete the testing files and proceed
- Place latest GodMode9.firm renamed to boot.firm on the empty SD (as well as the gm9 folder with the scripts) and boot into GodMode9 with ntrboot
- Backup the currently bricked status (NAND backup). Yes, it makes sense to create an image of a bricked state. Don't ignore this
A)
- Mount an old NAND backup, from when the console was working
- Open [S:] SYSNAND VIRTUAL/nand.bin in the GodMode9 hexeditor
- Open [I:] IMGNAND VIRTUAL/nand.bin in the GodMode9 hexeditor
I guess you could do easier comparison on a computer using a hexeditor there. If only a single or two things are modified,you could try manually repairing the damage with GodMode9 hexeditor.
B) Run a forced NAND restore of a known to be good image. I hope you didn't ignore the backup step with above.
above.
C) Try CTRTransfer Type D9 script. Make sure to find 11.5 and not 11.15 CTRTransfer Images.
=========If the NAND chip is failing, it might work after flashing a backup or repairing with CTRTransfer Type D9, and sooner or later the same will happen again.
Good luck!
Last edited by KleinesSinchen,
- Joined
- Sep 13, 2022
- Messages
- 7,162
- Trophies
- 3
- Location
- The Wired
- Website
- m4x1mumrez87.neocities.org
- XP
- 21,986
- Country
I've seen this happen to many Gateway owners as well if anybody remembers them.Given that this is not some kind of prank or splash screen, which disappears after a few seconds (and should when trying to boot without SD), this is not good news.
This is very bad. See [3dbrew] Bootloader Error Codes→ NCSD header in sector 0 is corrupt (failed signature check).
I have some different ideas how this can happen:
==========
- Experiments which should NEVER be done →
- Malware (I've never heard of 3DS malware in the wild, but it would be trivial to built this) →
- Dying NAND chip →
Please do the following
Then try one or more of these
- Provide an empty, FAT32 formatted SD and check it with h2testw or F3. If the SD passed the check, delete the testing files and proceed
- Place latest GodMode9.firm renamed to boot.firm on the empty SD (as well as the gm9 folder with the scripts) and boot into GodMode9 with ntrboot
- Backup the currently bricked status (NAND backup). Yes, it makes sense to create an image of a bricked state. Don't ignore this
A)
- Mount an old NAND backup, from when the console was working
- Open [S:] SYSNAND VIRTUAL/nand.bin in the GodMode9 hexeditor
- Open [I:] IMGNAND VIRTUAL/nand.bin in the GodMode9 hexeditor
I guess you could do easier comparison on a computer using a hexeditor there. If only a single or two things are modified,you could try manually repairing the damage with GodMode9 hexeditor.B) Run a forced NAND restore of a known to be good image. I hope you didn't ignore the backup step withC) Try CTRTransfer Type D9 script. Make sure to find 11.5 and not 11.15 CTRTransfer Images.=========
If the NAND chip is failing, it might work after flashing a backup or repairing with CTRTransfer Type D9, and sooner or later the same will happen again.
Good luck!
Came later to 3DS when Gateway was already frowned upon and not easy to find. I don't have it, sadly – would like to gain knowledge in this regard.
Those bricks intentionally caused by Gateway if detecting clone carts… did they cause the exact same error code? The bootrom can show many different errors, and only a few are listed on 3dbrew.
I don't know what they did back then and stand corrected: Of course there was(is?) malware for 3DS in the wild: The brick code by Gateway.
- Joined
- Sep 13, 2022
- Messages
- 7,162
- Trophies
- 3
- Location
- The Wired
- Website
- m4x1mumrez87.neocities.org
- XP
- 21,986
- Country
This also affected legitimate carts as well or even when the firmware was corrupted.
I thought something like this absolutely required an ntrboot flashcart and that it was a waste of time trying anything else, as per https://3ds.hacks.guide/troubleshooting .
Obviously yes, ntrboot is the only entrypoint left (unless it is some prank splash screen that disappears after some time).
At least this is an error code possibly software related, so attempting a fix by ntrbooting into GodMode9 is a good idea.
What are you trying to say? 8046 errors are not new and sadly not uncommon. Likely to happen more often with the NAND chips aging.
Ah ok that is why you have the error, it does not need to and cannot be flashed. Boot9strap is already flashed, just set the switch to 3ds mode, also I think it needs an sd card in the flashcart.
Maybe it could help to show us the card?
Most vendors sell the pictured card as Ace3ds plus, despite the actual cart saying Ace3ds X. If it is not like the one in the picture, it may not be compatible with ntrboot.
I did think that card was able to be flashed, which version of ntrboot flasher nds are you using?
This one:
https://github.com/jason0597/ntrboot_flasher_nds/releases/tag/5.1.1
Or this one:
https://github.com/ntrteam/ds_ntrboot_flasher/releases/tag/v4.0
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
32GBs is the baseline for 4K video editing these days and lots of recommendations for 64GBs but for games 16,GBs is honestly plenty for a long time. -
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Some sort of police thing going on near me lol "Get out of the car with your hands up and walk backwards towards us" over a loud speaker thing
-
-
like a 250 dollar kit back when DDR4 was Intel only
