Hardware Old3DS Black Screen of Death

[Dikop]

Hi everyone, i did get O3DS and it has some kind of "black screen of death". It turns on, but both screens are black(backlight is worked), noise from speakers and wi-fi diod blinking. I checked all internals and they work(check it with another O3DS motherboard). Tried some known solutions(update from safe mode, delete home data, insert sd with firm files) and they dont give result. 3DS wasnt previosly hacked and there is no backups , so i made hardmod and try write nand data from another O3DS, but (of course) i get bootrom error (00F800FF F8F8FFFF FFFFFFFF 00000000 00000000). There is some methods to repair O3DS using another 3DS or PC?

 

[TurdPooCharger]

You can't flash another o3DS nand image on a different o3DS as each system has their own console unique encryption. Unless you backed up that bricked o3DS nand image before the reflash, you also permanently erased all its console unique files. Basically, even you manage to unbrick it, that o3DS has lost its access privileges to Nintendo services like eShop and online play.

Troubleshooting the 3DS firmware should have been done with the ntrboot method and GodMode9.

 

[Dikop]

You can't flash another o3DS nand image on a different o3DS as each system has their own console unique encryption. Unless you backed up that bricked o3DS nand image before the reflash, you also permanently erased all its console unique files. Basically, even you manage to unbrick it, that o3DS has lost its access privileges to Nintendo services like eShop and online play.

I made a NAND backup (and write it back), but this is a backup of the console that has already received BSOD. The console turns on and works limitedly (sound, image, wifi), but only in recovery mode. I understand that the firmware files in Firm0 and Firm1 were somehow damaged. Are there any ways to pull out keys or brute force them? Or is the only option ntrboot?

 

[TurdPooCharger]

I made a NAND backup (and write it back), but this is a backup of the console that has already received BSOD. The console turns on and works limitedly (sound, image, wifi), but only in recovery mode. I understand that the firmware files in Firm0 and Firm1 were somehow damaged. Are there any ways to pull out keys or brute force them? Or is the only option ntrboot?

Sorry, I'm not too familiar with the hardmod method and whether the FIRM0 and FIRM1 partitions can be directly edited without the need of bootrom files: boot9.bin, boot11.bin, and console unique otp.bin.

However, it's much easier and safer to access and repair the 3DS firmware with ntrboot even if the firmware is severely softbricked.

• FIRM0 and FIRM1 can be repaired when (re)hacking the o3DS with ntrboot.
• SafeB9SInstaller will reinstall boot9strap to both FIRM0/1.
• Another option is using OpenFirmInstaller to install fastboot3ds as a alternative bootloader.
  
• If SafeB9Sinstaller doesn't work, there is also force reflashing the FIRM0/1 partitions using GodMode9.

Check my signature for ntrboot compatible flashcarts. Since you already have another working o3DS, you can go with the shitty R4iSDHC series when reflashing the cart to ntrboot mode.

 

[Dikop]

Sorry, I'm not too familiar with the hardmod method and whether the FIRM0 and FIRM1 partitions can be directly edited without the need of bootrom files: boot9.bin, boot11.bin, and console unique otp.bin.

Maybe you know where people who familiar with this question hang out?

 

[TurdPooCharger]

Maybe you know where people who familiar with this question hang out?

Many 3DS homebrew users from the hardmod era have either retired by now or moved onto Switch homebrew. You can try your luck asking around the [discordapp] Nintendo Homebrew channel. If the hardmod tutorial is not installing boot9trap to the borked o3DS, you'll most likely be told the same advice about troubleshooting by ntrboot.

 

[Dikop]

Ok, thank a lot.