Hardware HardBricked while sitting

[link2877]

Well it seems like we can only fix this problem in six month intervals huh. Was messing with the old system tonight kinda just out of boredom and because I still wasn't completely convinced I had all the files right last time. And well what do you know I got stuff to boot up on screen. I can't install or back anything up though. ntr just fails at the crypto status section with a Firm partition fail and godmode doesn't even seem to be able to find a sysnand. It just says it's sysnand virtual 0 bytes. Try to do a nand backup through scripts and it fails there too. Any other steps I can do here? It feels like I'm not really using godmode9 correctly.

Spoiler: Images

 

[TurdPooCharger]

Well it seems like we can only fix this problem in six month intervals huh. Was messing with the old system tonight kinda just out of boredom and because I still wasn't completely convinced I had all the files right last time. And well what do you know I got stuff to boot up on screen. I can't install or back anything up though. ntr just fails at the crypto status section with a Firm partition fail and godmode doesn't even seem to be able to find a sysnand. It just says it's sysnand virtual 0 bytes. Try to do a nand backup through scripts and it fails there too. Any other steps I can do here? It feels like I'm not really using godmode9 correctly.

Because GodMode9 v1.9.0 is a really new release and what you're seeing might be a fluke, what happens when you ntrboot launch GodMode9 v1.8.0 or v1.7.1? Are items in [S:] SYSNAND VIRTUAL still missing in those older versions?

 

[link2877]

Because GodMode9 v1.9.0 is a really new release and what you're seeing might be a fluke, what happens when you ntrboot launch GodMode9 v1.8.0 or v1.7.1? Are items in [S:] SYSNAND VIRTUAL still missing in those older versions?

Nope no changes at all. It's like the sysnand isn't even connected. I don't really have much hope of fixing it now. I mean even if I did successfully do a hard mod I don't know if I'd even be able to see the nand let alone recover it? Is the section it's booting from to get to the blue screen even on the nand? Or is it in the SOC?

 

[Subtle Demise]

Ok this is my deduction:

• NAND was damaged by over-charging and/or improper storage.
• The system still kind of worked because it was running from RAM. It froze and shut down when trying to read the NAND.

It needs a hardware repair. A full motherboard replacement or simply buying a new 3DS.

 

[TurdPooCharger]

Nope no changes at all. It's like the sysnand isn't even connected. I don't really have much hope of fixing it now. I mean even if I did successfully do a hard mod I don't know if I'd even be able to see the nand let alone recover it? Is the section it's booting from to get to the blue screen even on the nand? Or is it in the SOC?

Blue screen bootrom 8046 comes from the SoC reporting that it cannot correctly communicate with the NAND.

If this was a softbrick due to corrupted firmware image on the NAND, GodMode9 should have been able to read, find, or list (at minimum) the nand.bin within [S:] SYSNAND VIRTUAL.

Your bootrom 8046 is definitely a hardbrick where the NAND is fried since GM9 lists 0 bytes (no items) for the [S:] when it's suppose to be 1.8 GB.

***

While not practical, it's possible to repair or replace the fried NAND chip with another eMMC.

• [r/3dshacks] Best Hardmods for New 3DS XL?
  • see the discussion chain started by MathewPKfan2001.

• [noodlevisions] Creating a USA Non-XL *New* 3DS Hardware Variant

Here's an example thread of where ClickCLK professionally micro electronics repaired/replaced a bad SoC amongst back-and-forth eMMC swapping.

• Repairing dead new 3ds LL

***

As what @Subtle Demise and others have suggested, the easiest and cheapest repair option would be to buy a replacement motherboard or another system entirely. Check my signature link buying 3DS systems from Nintendo.

 

[link2877]

Yeah that is cool and all but at this point I really only want the data off the nand. It was an ambassador system with all kinds of old data from as far back as the system launch and also like 200 hundred dollars worth of Eshop software on it. Could somebody explain just how much of your data is stored on the nand compared to the sd card. Because I did link my Nintendo account long before this all happened. If I bought a new system linked my account to it and inserted my old sd card, exactly how much of my old data would actually be recovered?

 

[TurdPooCharger]

Yeah that is cool and all but at this point I really only want the data off the nand. It was an ambassador system with all kinds of old data from as far back as the system launch and also like 200 hundred dollars worth of Eshop software on it. Could somebody explain just how much of your data is stored on the nand compared to the sd card. Because I did link my Nintendo account long before this all happened. If I bought a new system linked my account to it and inserted my old sd card, exactly how much of my old data would actually be recovered?

You can't recovery data from a fried NAND because it's essential brain dead. All your user information like friends list, nnid, activity log, and game saves for system titles like Face Raider are all gone.

Your eShop purchased titles and saves are installed on the SD card found in the Nintendo 3DS folder. These can only be recovered if you somehow manage to have backed up the NAND's movable.sed that has the exact KeyY that goes with the 32-char <ID0> subfolder.

Another round about way of obtaining or recreating that KeyY is find someone who friended you before, have him/her dump your Friend Code and its LocalFriendCodeSeed (1st half of the KeyY), and then use:

• bruteforcemovable.com

with the supplied <ID0> and 1st half of that KeyY.

Once the full key is produced, you use this method of importing the library to another system.

• (Very Messy Tutorial) SDTransfer: Moving or cloning a (source) system's Nintendo 3DS folder to another (target) system

***

Without that exact 16 bytes KeyY, there's no chance of decrypting the contents within Nintendo 3DS folder.

 

[link2877]

You can't recovery data from a fried NAND because it's essential brain dead. All your user information like friends list, nnid, activity log, and game saves for system titles like Face Raider are all gone.

Your eShop purchased titles and saves are installed on the SD card found in the Nintendo 3DS folder. These can only be recovered if you somehow manage to have backed up the NAND's movable.sed that has the exact KeyY that goes with the 32-char <ID0> subfolder.

Another round about way of obtaining or recreating that KeyY is find someone who friended you before, have him/her dump your Friend Code and its LocalFriendCodeSeed (1st half of the KeyY), and then use:

• bruteforcemovable.com

with the supplied <ID0> and 1st half of that KeyY.

Once the full key is produced, you use this method of importing the library to another system.

• (Very Messy Tutorial) SDTransfer: Moving or cloning a (source) system's Nintendo 3DS folder to another (target) system

***

Without that exact 16 bytes KeyY, there's no chance of decrypting the contents within Nintendo 3DS folder.

So not even a hard mod would do anything thing then huh? I mean it's not like I can break it anymore then it all ready is right.

 

[TurdPooCharger]

So not even a hard mod would do anything thing then huh? I mean it's not like I can break it anymore then it all ready is right.

A fried NAND chip is like a burnt out light bulb. Doing a hard mod would be the equivalent of taking that light bulb and putting it in a different socket. Your stand-in socket supplies the correct voltage and amp, but that doesn't matter when the bulb is now in an open circuit.

A NAND chip consists of millions of transistors where each are in states of either 0's and 1's (binary, bits). Each transistor is basically a light bulb where a state of 0 is (OFF) or 1 means it carries a long lasting charge (ON). When a NAND chip fries, those transistors (representing your data) are destroyed; they all become 0's or rather NULL.

***

In the coming years, replacement 3DS parts will become rarer and harder to find. Parts like shells, buttons, and batteries can be replenished by 3rd party manufacturers.

Unfortunately, PCBs parts (especially the mobo) will continually dwindle in supplies and these can't be replicated as only Nintendo and Foxconn has the blueprints to those.

I believe further damaging a broken but not dead motherboard would be a waste of resources if it can be revived by having its eMMC replaced by a professor micro electronics repair specialist.