Hacking Hardware Help old 2ds brick bootrom error

  • Thread starter Thread starter Maylina53
  • Start date Start date
  • Views Views 4,781
  • Replies Replies 26

Maylina53

Member
Newcomer
Joined
Dec 4, 2022
Messages
12
Reaction score
1
Trophies
0
Location
Somewhere
XP
75
Country
France
BOOTROM 8046
ERRCODE 00F800EE FFFFFFFF FFFFFFFF 00000000 00000000
Help
 

Attachments

  • IMG_20221204_152222.jpg
    IMG_20221204_152222.jpg
    1.1 MB · Views: 177
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:
  • 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) → :shit:
  • Dying NAND chip → :shit::shit: :shit:
==========
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:!:
Then try one or more of these
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.​
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,
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:
==========
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:!:
Then try one or more of these
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.​
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!
I've seen this happen to many Gateway owners as well if anybody remembers them.
 
  • Like
Reactions: KleinesSinchen
I've seen this happen to many Gateway owners as well if anybody remembers them.
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.
 
  • Like
Reactions: SylverReZ
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.

Well This Is New
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.
 
I have ace3ds plus, not ace3ds x, I don't think I have the Switch

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.
 

Site & Scene News

Popular threads in this forum