Hacking Help! N3DS won't boot. (probably bricked)

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
It's a long story.
So back in 2015-2016 I decided to install Luma CFW to my N3DS XL with A9LH. I don't exactly remember which version of Luma it was but
it worked fine for about a year and a half. Then I update the system and it bricks? When I tried to turn it on it wouldn't boot, the screens would go black and the power indicator LED wouldn't change.
I tried safe/recovery mode but that wouldn't work either. So I start looking if other people had a similar problem on this forum and I had found a couple.
Eg: https://gbatemp.net/threads/3ds-har...en-cant-access-the-recovery-menu-help.524659/
https://gbatemp.net/threads/new-3dsxl-bricked-tried-everything-cannot-access-home-screen-or-recover/
. I had tried all of the suggested ways like those from @TurdPooCharger
in these threads and it had not worked. (BTW me troubleshooting it was just recently as I had left it on a shelf for a couple years, not noticing it until recently.)
 
Last edited by FizzlingFly,
Joined
Jan 1, 2018
Messages
7,292
Trophies
2
XP
5,942
Country
United States
I would have linked to you this other thread but felt your brick might need special attention.
***
  1. Take a small sized (4 GB minimum, preferably spare) microSD card and copy everything off it over to a computer.
  2. Quadruple reformat the card.
  3. Full Write + Verify the empty card in H2testw. Do not skip.
  4. If the card passes, delete the *.h2w test files.
    • :!:If an error was reported, replace the hardware failed card and go back to step 1.
  5. Download Luma3DS v7.0.5 and install this at:
  6. Download SafeB9SInstaller v0.0.7, rename the *.firm file, and install this at:
    • SafeB9SInstaller.firmboot.firm
    • sdmc:/boot.firm
  7. Do not add or put any other files back onto the card.
  8. Remove any game cartridge inserted in the n3DS, perform the battery trick, insert the microSD card into the n3DS, turn it on, and hold the (SELECT) button.
    • You may want to (un-&-re)insert the SD card several times to get a good read connection.
***

Scenario (A):
The n3DS boots to Luma3DS v7.0.5 configuration.

Scenario (B):
The n3DS boots to SafeB9SInstaller v0.0.7.

Scenario (C): The n3DS boots with blue LED indicator and black screens.
  • Solution: The 3DS firmware is most likely bricked. Repair this by rehacking with the ntrboot method and R4i Gold 3DS Plus.
  • Note: If you have another (o/n)(2/3)DS(i)(XL/LL)(phat/lite) system with working DS mode, you can opt getting the R4iSDHC series.

***

Scenario (D): The n3DS still boots with black screens despite ntrboot repair attempts specified in scenario (C).

***

Scenario (E): The n3DS still boots with black screens despite replacing the microSD card slot reader specified in Scenario (D).
  • Disassemble the n3DS. Check for disconnect or broken flex cables for the LCDs, camera module, speaker assembly, digitizer.
  • If nothing seems out of place, you may need to outsource hardware repair. Contact wiigotem or testerfan.
 

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
Update: Tried to follow steps 1-8. N3DS did not boot to luma config nor SafeB9Sinstaller. Ordered a R4i sdhc gold pro(2020) from amazon to try ntrboot.
 
Joined
Jan 1, 2018
Messages
7,292
Trophies
2
XP
5,942
Country
United States
Update: Tried to follow steps 1-8. N3DS did not boot to luma config nor SafeB9Sinstaller. Ordered a R4i sdhc gold pro(2020) from amazon to try ntrboot.
That flashcart requires a working (3)DS system to reflash it in ntrboot mode. The reason the R4i Gold 3DS Plus is recommended is not *only because it has a built-in switch that can change between between DS and ntrboot mode, but it also has the nice looking WOOD kernel user interface.

If you intend to use that R4i SDHC Gold Pro at some point playing DS games, you might come across the notorious Time Bomb; see also YS Menu.
 
Last edited by TurdPooCharger,

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
That flashcart requires a working (3)DS system to reflash it in ntrboot mode. The reason the R4i Gold 3DS Plus is recommended is not *only because it has a built-in switch that can change between between DS and ntrboot mode, but it also has the nice looking WOOD kernel user interface.

If you intend to use that R4i SDHC Gold Pro at some point playing DS games, you might come across the notorious Time Bomb; see also YS Menu.
I know about the Time bomb and I have another DS lite to reflash it (does it specifically need another 3ds system?
 
Last edited by FizzlingFly,

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
Any other ways to unbrick it? because I tried NTRboot and it didn't work or maybe I'm doing something wrong (BTW I'm 80% sure it isn't a hardbrick because I only had it for about a year or two)
 

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
Any other ways to unbrick it? because I tried NTRboot and it didn't work or maybe I'm doing something wrong (BTW I'm 80% sure it isn't a hardbrick because I only had it for about a year or two)
I'm dumb. SDXC cards are not supported by the N3DS XL. (I was using a 128GB SDXC card). That's why it didn't work.... :wtf:
 

Neyalex

Member
Newcomer
Joined
Feb 9, 2020
Messages
5
Trophies
0
Age
22
XP
54
Country
United States
Just commenting because I saw no mention of it, but I assume you've updated your Luma files and such (like the boot file in particular, which has no visible version number), using a FAT32 formatted card?

I can vouch for 128gb cards working when reformated as FAT32, that's what I've been running on my o3ds for years now.

If I remember correctly, the console can appear "bricked" when your console updates but your luma files are not up to date to match, especially if you've left it sitting on a shelf for a long time.
 
Last edited by Neyalex,
  • Like
Reactions: FizzlingFly

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
Update: I found a very basic error. I formatted my sd cards with 16KB allocation unit size instead of 32KB. Update ya on what happens later!

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

Just commenting because I saw no mention of it, but I assume you've updated your Luma files and such (like the boot file in particular, which has no visible version number), using a FAT32 formatted card?

I can vouch for 128gb cards working when reformated as FAT32, that's what I've been running on my o3ds for years now.

If I remember correctly, the console can appear "bricked" when your console updates but your luma files are not up to date to match, especially if you've left it sitting on a shelf for a long time.
Yes I have, if you need to know.
 

FizzlingFly

Member
OP
Newcomer
Joined
Jan 31, 2020
Messages
14
Trophies
0
Age
59
XP
60
Country
Canada
BTW, is this sysNAND_original.bin file of any use? seems like it could be.
found it on my backup for the original SD card I used for the N3DS
 
Last edited by FizzlingFly,

laramie

Well-Known Member
Member
Joined
Dec 15, 2014
Messages
911
Trophies
0
XP
1,387
Country
United States
BTW, is this sysNAND_original.bin file of any use? seems like it could be.
found it on my backup for the original SD card I used for the N3DS
you can use this in the future along with ntrboot to boot up godmode9 which can restore your operating system(sysNAND_originalbin) if you ever truly get a brick.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    LeoTCK @ LeoTCK: hmm