Homebrew 3ds blue screen

[Jykzz]

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]

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

 

[TurdPooCharger]

Did you play Mario Maker with a Gateway 3DS (or Gateway clone) flashcart?

 

[Jykzz]

Did you play Mario Maker with a Gateway 3DS (or Gateway clone) flashcart?

nope i install with fbi

 

[PalindromicBreadLoaf]

Did you download the cia of it online, or was it legitimately purchased (dumped from a cart)? And if you did download it online, was it from a reputable source?

 

[Jykzz]

Did you download the cia of it online, or was it legitimately purchased? And if you did download it online, was it from a reputable source?

its a cia im poor

 

[TurdPooCharger]

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.

 

[Jykzz]

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]

Your eMMC could have died without a hardmod. It kinda just decides when it is done. And it is completely done then.

 

[Jykzz]

Your eMMC could have died without a hardmod. It kinda just decides when it is done. And it is completely done then.

if my eMMC is dead i can't acces to the console without the sd card?because i can

 

[PalindromicBreadLoaf]

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.

 

[Jykzz]

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?

 

[PalindromicBreadLoaf]

Wait, WHAT? So if you have the SD card inserted, the 3ds throws that error, but if you don't, then it is just fine?

 

[Jykzz]

Wait, WHAT? So if you have the SD card inserted, the 3ds throws that error, but if you don't, then it is just fine?

i dunno i dont try it i just shut up the console without the sdcard and start normally

 

[PalindromicBreadLoaf]

Hmm, do you have am EmuNAND installed and set to autoboot? I don't think that would cause it, but just seeing.

 

[Jykzz]

Hmm, do you have am EmuNAND installed and set to autoboot? I don't think that would cause it, but just seeing.

yes i have emunand but i dont know if i have a backup of the nand

 

[PalindromicBreadLoaf]

Do you have a spare SD card you could use to see if your 3ds would boot up with a SD card in it at all? Also, if your 3ds boots up without a SD card at all, your NAND probably isn't too screwed up.

 

[Jykzz]

d

Do you have a spare SD card you could use to see if your 3ds would boot up with a SD card in it at all?

yes i have an spare sd card and i just try it but when i put the sd card the screen come back

 

[Aletron9000]

I doubt this is the issue, but maybe something came loose inside? According to https://www.3dbrew.org/wiki/Bootloader, there is a bootrom error if the sd-card reader is connected to nand during boot.

 

[Jykzz]

I doubt this is the issue, but maybe something came loose inside? According to https://www.3dbrew.org/wiki/Bootloader, there is a bootrom error if the sd-card reader is connected to nand during boot.

could be the problem