Hacking How Fucked am I?

[RyDog]

if you seen my last post, I was having trouble booting up gateway, so I formatted sysNAND. Still didn't work. Finally I downloaded 3.4.2 of gateway's launcher.dat. It finally booted and the main purpose of getting gateway to launch was to revert to my first NAND.bin backup. After restoring the NAND I turned off my DS and bam! 3DS got bricked -.- this is my second 3ds to be bricked. Now, my question is, Was my one and only NAND.bin the coperate for my brick? Or was it gateway and I can easily re flash my NAND with a hardmod? (The brick is a software brick where there is no backlight LED coming on)

 

[Deleted User]

It looks like you restored a NAND.bin that is somehow corrupted, ie some titles/FIRM are not compatible.

Are you sure this was a clean *WORKING* NAND.bin?
If you're going to restore this with a nand mod, it will probably result in the same thing

 

[Deleted-19228]

You had your 3ds booting, why would you reflash it? Doesn't make sense...

 

[bbcali89]

You could hard mod yeah.
That is pretty much your only option here.

iirc

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

You had your 3ds booting, why would you reflash it? Doesn't make sense...

This too. but I wanted to take into consideration he may have been trying something assuming that based off the "2nd brick, and hard mod" comment

 

[Deleted-19228]

Maybe he flashed the nand.bin from the other 3ds? heh

 

[zoogie]

Maybe he flashed the nand.bin from the other 3ds? heh

That would have given a blue screen brick.

 

[subcon959]

Not sure why no one has answered the question yet.. you are 73% fucked.

 

[wurstpistole]

Not sure why no one has answered the question yet.. you are 73% fucked.

I see your 73% and raise you to 75%, based on my exceptional 3DS haxxor knowledge.

 

[vb_encryption_vb]

Try reflashing with hard mod. Easiest way to see if your problem is fixed.

 

[RyDog]

You had your 3ds booting, why would you reflash it? Doesn't make sense...

I wanted to relink my sysNAND and emuNAND because I was having troubles signing in to NNID, where it completely blocked my emuNAND from connecting to Nintendo Servers until I signed into NNID from sysNAND, which was impossible since it was trying to force me to update.

Maybe he flashed the nand.bin from the other 3ds? heh

No, I named the folder the color of the 3DS and the sysNAND version, so I obviously didn't do that.

It looks like you restored a NAND.bin that is somehow corrupted, ie some titles/FIRM are not compatible.

Are you sure this was a clean *WORKING* NAND.bin?
If you're going to restore this with a nand mod, it will probably result in the same thing

How can I tell if it's corrupted? It's full size so I don't believe it's corrupted.

 

[vb_encryption_vb]

I wanted to relink my sysNAND and emuNAND because I was having troubles signing in to NNID, where it completely blocked my emuNAND from connecting to Nintendo Servers until I signed into NNID from sysNAND, which was impossible since it was trying to force me to update.

No, I named the folder the color of the 3DS and the sysNAND version, so I obviously didn't do that.

How can I tell if it's corrupted? It's full size so I don't believe it's corrupted.

Look at it in a hex editor and look to see if it looks trashed, would help if you had another known good nand to look at to get a rough idea of what it should look like. Or just do the hardmod.

 

[Deleted-236924]

I wanted to relink my sysNAND and emuNAND because I was having troubles signing in to NNID, where it completely blocked my emuNAND from connecting to Nintendo Servers until I signed into NNID from sysNAND, which was impossible since it was trying to force me to update.

Backup emunand, backup it's Nintendo 3DS folder, format emunand in system settings, re-link NNID, restore emunand backup + its Nintendo 3DS folder = win

At this point your only hope would be to try and flash emunand backup to sysnand, which may just result in the same black screen anyway.