Homebrew 3ds blue screen

Jykzz

Member
OP
Newcomer
Joined
May 13, 2019
Messages
24
Trophies
0
Age
25
XP
74
Country
Colombia
ok guys this is the thing i was playing mario maker for 3ds and the its freeze then power off and when i turn power on only appears a blue screen what says: BOOTROM 8046
ERRCODE: 00F800DEF
FFFFFFFFF FFFFFFF
000000024 0000000
Im scared and i think i broke my console any solution or its definitely dead?
 

Shadow#1

Wii, 3DS Softmod & Dumpster Diving Expert
Member
Joined
Nov 21, 2005
Messages
12,354
Trophies
2
XP
8,015
Country
United States
ok guys this is the thing i was playing mario maker for 3ds and the its freeze then power off and when i turn power on only appears a blue screen what says: BOOTROM 8046
ERRCODE: 00F800DEF
FFFFFFFFF FFFFFFF
000000024 0000000
Im scared and i think i broke my console any solution or its definitely dead?
NTRBoot with a ds flashcart
 
Joined
Jan 1, 2018
Messages
7,292
Trophies
2
XP
5,947
Country
United States
nope i install with fbi
Try the battery trick. If it still gives bootrom 4046, you will need to go with Shadow#1's approach with ntrboot to gain access to GodMode9 (substituted as boot.firm).

Assuming your blue screens of death is software base, you'll need to recover with restore sysnand (you better have that .bin backup image made beforehand).
CTRTransfer probably isn't going to work as you most likely bricked one of the other partitions.

If the error is due to hardware fault such as a fried eMMC, your 3DS has semi-died. You can get around the dead NAND chip by using EmuNAND (requires NAND *.bin image to create and flash to SD card).
Other failed components means it's super dead.
 
Last edited by TurdPooCharger,

Jykzz

Member
OP
Newcomer
Joined
May 13, 2019
Messages
24
Trophies
0
Age
25
XP
74
Country
Colombia
i
Try the battery trick. If it still gives bootrom 4046, you will need to go with Shadow#1's approach with ntrboot to gain access to GodMode9 (substituted as boot.firm).

Assuming your blue screens of death is software base, you'll need to recover with restore sysnand (you better have that .bin backup image made beforehand).
CTRTransfer probably isn't going to work as you most likely bricked one of the other partitions.

If the error is due to hardware fault such as a fried eMMC, your 3DS has semi-died. You can get around the dead NAND chip by using EmuNAND (requires NAND *.bin image to create and flash to SD card).
Other failed components means it's super dead.
i dont think what is a eMMC problem because my console dont have the hardmode (i only think this)
 

PalindromicBreadLoaf

Just a duck floating in a pond.
Member
Joined
Aug 22, 2018
Messages
401
Trophies
0
Age
23
Location
Canada
XP
1,746
Country
Canada
The eMMC is your console main internal memory. It has multiple partitions, and one of those (CTRNAND) has your System files on it. If the chip died, then everything on it is gone, and the system won't detect it correctly and throw an error on boot, as it can't get past the BootROM. It doesn't (shouldn't) matter if your SD card is inserted or not, as it can't mount the NAND. In this scenario of course.
 
Last edited by PalindromicBreadLoaf,
  • Like
Reactions: TurdPooCharger

Jykzz

Member
OP
Newcomer
Joined
May 13, 2019
Messages
24
Trophies
0
Age
25
XP
74
Country
Colombia
The eMMC is your console main internal memory. It has multiple partitions, and one of those (CTRNAND) has your System files on it. If the chip died, then everything on it is gone, and the system won't detect it correctly and throw an error on boot, as it can't get past the BootROM. It doesn't (shouldn't) matter if your SD card is inserted or not, as it can't mount the NAND. In this scenario of course.
i dont know what do...the console is working normally but in this case if i insert a sdcard the screen appears?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Psionic Roshambo @ Psionic Roshambo: I had one it was fun lol