Hacking Trouble flashing 3ds NAND

[StriderHiryu001]

I'm following this guide ([TUTORIAL] [Noob-Friendly] NAND Dumping 2DS/3DS/3DS XL/N3DS/N3DS XL!) to repair my bricked original 3ds. I'm at the stage where I have to reflash the patched rom into the 3ds, but I get this message on the blue 3ds screen
BOOTROM 8046
ERRCODE: 00F800FF
DFDFFFFF FFFFFFFF
00000005 00000000
and no disk shows up on my computer, although it does recognize the card reader. based on the error code, am I doing anything wrong? I checked continuity all the way from the points on the card reader to the 3ds main board and they're all good, and I kept the runs as short as I could. I read some other threads and I realize i might have let the 4 wires touch a bit while everything was plugged in, would that have fried something?
Any help is appriciated.

 

[Quantumcat]

Did you try ntrboot before you did this? How old is the guide? It is very rare to need to hardmod a console in today's world.

 

[StriderHiryu001]

Did you try ntrboot before you did this? How old is the guide? It is very rare to need to hardmod a console in today's world.

It was a bricked console i got from a friend. it was unmodded before i got my hands on it. it wouldnt boot, so the only way to get it working was to flash the nand, as i assumed thats what was wrong with it.

 

[KleinesSinchen]

Hardmod is not the way to go (anymore). It is easy to do damage something – even if you are good at soldering. There is little to no reason to even think of the soldering iron when troubleshooting a 3DS – thanks to ntrboothax. In order to flash B9S onto the NAND with a hardmod with the known plaintext attack you have to know which firmware is currently installed – another problem not even existing when using ntrboot.

Hopefully I remember this correctly: While the SD-reader is connected the 3DS is supposed to throw one of the 8046 blue screens of death errors – but with a different code. See [3dbrew] Bootloader for more information.

A not booting 3DS can have multiple (hard- and software) reasons. Did it show bootrom error before you attempted hardmod or did it show black screens? If the NAND chip has been shorted it may be already dead / unreadable.

 

[TurdPooCharger]

@StriderHiryu001, check my signature for ntrboot flashcart choices. If you can afford it, get the R4i Gold 3DS Plus for its easy to use dual mode switch ( DS / ntrboot ). If you get the R4iSDHC series, you'll need another working (o/n)(2/3)DS(i)(XL/LL)(phat/lite) to reflash the cart.

I would hold off flashing any SysNAND *.bin image if the 3DS firmware is mostly intact (ie, the CTRNAND, TWLN, and TWLP partitions are visible). If you can gain access to GodMode9 through ntrboot entry, I can help guide you in fixing the blue screens of death.

Typical causes of softbrick based bootrom 8046.

• For New 3DS XL systems that failed in A9LH 2.1.0 downgrade, sector0x96.bin (secret_sector.bin)
• FIRM0 & FIRM1 (firm0.bin & firm1.bin) - New series systems require fixed sector0x96.bin.
  
• The nand's NSCD header (nand_hdr.bin) can be rebuilt.
  
• The TWL partition table (twlmbr.bin) - This should be fixed first before trying to rebuild the NAND header.

 

[StriderHiryu001]

i want to reiterate that when i got the 3ds. it would not boot at all. it wouldnt run games, wouldnt go to the menu, nothing. just a blue light and black screens. once i got the sd card adapter hooked up to it it showed the blue screens, which told me there was some life left in it. But the code im getting doesnt show up anywhere online, not in the 3dbrew wiki entry anyways.
seeing as how the 3ds would not boot at all. i think this means that the only way to get in modded, or to get it running at all, was to flash the nand. i remember reading some forum posts about how leaving youe 3ds in sleep mode for too long would currupt the nand, i assumed that what happened according to what my friend told me.
if im wrong on any of this please let me know. Id love to get this thing working.

 

[lone_wolf323]

i want to reiterate that when i got the 3ds. it would not boot at all. it wouldnt run games, wouldnt go to the menu, nothing. just a blue light and black screens. once i got the sd card adapter hooked up to it it showed the blue screens, which told me there was some life left in it. But the code im getting doesnt show up anywhere online, not in the 3dbrew wiki entry anyways.
seeing as how the 3ds would not boot at all. i think this means that the only way to get in modded, or to get it running at all, was to flash the nand. i remember reading some forum posts about how leaving youe 3ds in sleep mode for too long would currupt the nand, i assumed that what happened according to what my friend told me.
if im wrong on any of this please let me know. Id love to get this thing working.

With what all you just typed. I would like to know if you have actually read what the others have posted. They are actually trying to help but all I see from you is just someone rambling on about nothing avoiding the topic at hand.

 

[TurdPooCharger]

i want to reiterate that when i got the 3ds. it would not boot at all. it wouldnt run games, wouldnt go to the menu, nothing. just a blue light and black screens. once i got the sd card adapter hooked up to it it showed the blue screens, which told me there was some life left in it. But the code im getting doesnt show up anywhere online, not in the 3dbrew wiki entry anyways.
seeing as how the 3ds would not boot at all. i think this means that the only way to get in modded, or to get it running at all, was to flash the nand. i remember reading some forum posts about how leaving youe 3ds in sleep mode for too long would currupt the nand, i assumed that what happened according to what my friend told me.
if im wrong on any of this please let me know. Id love to get this thing working.

Forget everything about the hardmod method as it carries a high risk of damaging or frying the NAND chip. If that chip dies, your bootrom 8046 becomes a hardbrick which can't be (easily) fixed. You can see an example of this in this thread:

• HardBricked while sitting

Get an ntrboot capable DS flashcart, flash it into ntrboot mode per guide (unless it's R4i Gold 3DS Plus model which has a built-in switch), substitute GodMode9 for the sdmc:/boot.firm, and check if the [S:] SYSNAND VIRTUAL drive still lists the nand.bin.

If the drives below are present, it should be possible to unbrick the firmware without doing a (full) or forced sysnand restore.

• [1:] SYSNAND CTRNAND
• [2:] SYSNAND TWLN
• [3:] SYSNAND TWLP

 

[StriderHiryu001]

With what all you just typed. I would like to know if you have actually read what the others have posted. They are actually trying to help but all I see from you is just someone rambling on about nothing avoiding the topic at hand.

I'm sorry. i don't know how to reply to multiple posts on this forum and i was trying to answer some of the question that were asked, as well as give some more information

--------------------- MERGED ---------------------------

Forget everything about the hardmod method as it carries a high risk of damaging or frying the NAND chip. If that chip dies, your bootrom8046 becomes a hardbrick which can't be (easily) fixed. You can see an example of this in this thread:
Get an ntrboot capable DS flashcart, flash it into ntrboot mode per guide (unless it's R4i Gold 3DS Plus model which has a built-in switch), substitute GodMode9 for the sdmc:/boot.firm, and check if the [S:] SYSNAND VIRTUAL drive still lists the nand.bin.

I actually have an ntrboot compatible r4 cart. I just got it working with my friends 3ds LL, it booted into safeb9installer just fine. when I take the magnet off of mine though the backlight turns on, but nothing shows on the screen. I tried replacing boot.firm with godmode9 and the same thing happened.

 

[TurdPooCharger]

I actually have an ntrboot compatible r4 cart. I just got it working with my friends 3ds LL, it booted into safeb9installer just fine. when I take the magnet off of mine though the backlight turns on, but nothing shows on the screen. I tried replacing boot.firm with godmode9 and the same thing happened.

What model 3DS system are you trying to fix?

• First, make sure your R4 flashcart is actually in ntrboot mode. Once its flashed with ntrboot, you'll know this when its game icon no longer shows up in HOME Menu.
  
• Your (micro)-SD card has to be formatted correctly in order for the 3DS to read it. See quadruple reformat.
  
• You may need to try several (re)insertions for the SD card and flashcart in between magnet attempts before the 3DS successfully launches the boot.firm (GodMode9).
  
• During the magnet process, hold the button combo for up to 10 seconds before letting go. If you let go too soon, it might not trigger launching the FIRM payload.

 

[StriderHiryu001]

What model 3DS system are you trying to fix?

• First, make sure your R4 flashcart is actually in ntrboot mode. Once its flashed with ntrboot, you'll know this when its game icon no longer shows up in HOME Menu.
  
• Your (micro)-SD card has to be formatted correctly in order for the 3DS to read it.
  
• You may need to try several (re)insertions for the SD card and flashcart in between magnet attempts before the 3DS successfully launches the boot.firm (GodMode9).
  
• During the magnet process, hold the button combo for up to 10 seconds before letting go. If you let go too soon, it might not trigger launching the FIRM payload.

Im trying to fix a teal original 3ds system. Ive tried inserting it and reinserting the cart a few times, and repositioning the magnet. when it fails i can tell because the backlight doesnt come on. but when i do it right the backlight stays off until i take the magnet away, then the screen turns on, but nothing shows up. like i said, i was able to get it working on my friends 3ds.

 

[TurdPooCharger]

Im trying to fix a teal original 3ds system. Ive tried inserting it and reinserting the cart a few times, and repositioning the magnet. when it fails i can tell because the backlight doesnt come on. but when i do it right the backlight stays off until i take the magnet away, then the screen turns on, but nothing shows up. like i said, i was able to get it working on my friends 3ds.

From the hardmod disassembly, are any of the o3DS parts or components currently disconnected?

Edit - Try other FIRM payloads: SafeB9SInstaller and Luma3DS (v9.1) renamed as boot.firm.