Hacking Bricked :(

[royant1]

Upgrading 2.1 on a new New 3ds. Just restoring from backup.

 

[V0LT!GE]

Never update from 2.1 in n3ds...

 

[regnad]

So OP didn't do this part?

1. Copy your sysNAND_original.bin and RedNAND_original.bin backups from Section I to the root of your SD card
2. Reinsert your SD card into your 3DS then press B to return to the main menu
3. Go to "NAND Backup & Restore"
4. Restore SysNAND from sysNAND_original.bin
5. Restore RedNAND from RedNAND_original.bin
6. Cross your fingers
7. Reboot!

Looking at the original top OP, it looks like he did, but then got errors. How did this happen? How can other people avoid this?

Clearly he screwed up when he tried to upgrade with a game, but prior to that what could he have done wrong when he got those errors? And what should he have done instead of upgrading with a game?

 

[Bu2d85]

So OP didn't do this part?

1. Copy your sysNAND_original.bin and RedNAND_original.bin backups from Section I to the root of your SD card
2. Reinsert your SD card into your 3DS then press B to return to the main menu
3. Go to "NAND Backup & Restore"
4. Restore SysNAND from sysNAND_original.bin
5. Restore RedNAND from RedNAND_original.bin
6. Cross your fingers
7. Reboot!

Looking at the original top OP, it looks like he did, but then got errors. How did this happen? How can other people avoid this?

Clearly he screwed up when he tried to upgrade with a game, but prior to that what could he have done wrong when he got those errors? And what should he have done instead of upgrading with a game?

I've been gone for only a week but I feel like I missed everything... What is RedNand?

 

[FR0ZN]

I had a similar situation with NAND restoring once.
The filename is case sensitive iirc, nand.bin couldn't be found, NAND.bin could tho. Probably messed up in the same way?

 

[Bu2d85]

I had a similar situation with NAND restoring once.
The filename is case sensitive iirc, nand.bin couldn't be found, NAND.bin could tho. Probably messed up in the same way?

No, he used GW to make the nand backup and it was not compatible with the version of Decrypt9 used in OTP helper. The same thing happened to me but I used an old emunand backup and restored it to sysnand.

 

[regnad]

I've been gone for only a week but I feel like I missed everything... What is RedNand?

It's just a slightly more compact version of EmuNAND as far as I know. No real difference except smaller size.

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

No, he used GW to make the nand backup and it was not compatible with the version of Decrypt9 used in OTP helper. The same thing happened to me but I used an old emunand backup and restored it to sysnand.

Oh, so he wasn't following the Plailect guide then? Aren't 98% of bricks caused by that?

 

[The Real Jdbye]

It's just a slightly more compact version of EmuNAND as far as I know. No real difference except smaller size.

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



Oh, so he wasn't following the Plailect guide then? Aren't 98% of bricks caused by that?

Yes. So basically, this brick was caused by user error.

 

[FR0ZN]

No, he used GW to make the nand backup and it was not compatible with the version of Decrypt9 used in OTP helper. The same thing happened to me but I used an old emunand backup and restored it to sysnand.

I also restored a dump made with GW w/o problems. The case sensitivity was my only issue.

 

[Bu2d85]

I also restored a dump made with GW w/o problems. The case sensitivity was my only issue.

Maybe you were using a different version than me. Also mine was a N3DS which has a different NAND size than the O3DS.

I tried everything but I could not get it to accept my GW backup.

 

[royant1]

I also restored a dump made with GW w/o problems. The case sensitivity was my only issue.

I didn't use a GW backup but the one i created with OTHelper/Decrypt9 (don't remember which one but per the tutorial).

Also, it's not about the name of the file as i tried changing to upper case and different names.

BTW, this is the third time i'm doing this, first 2 devices worked great...

 

[regnad]

I didn't use a GW backup but the one i created with OTHelper/Decrypt9 (don't remember which one but per the tutorial).

Also, it's not about the name of the file as i tried changing to upper case and different names.

BTW, this is the third time i'm doing this, first 2 devices worked great...

So you were following the Plialect guide exactly and got an error trying to restore. So this wasn't user error, at least as far as we can tell. Right?

 

[royant1]

Bricking was a user error, as i shouldn't have upgraded using a game cartridge. I guess i could have restored if i played a bit more, tried different versions of otphelper etc.

Was sure that upgrading over the network to the latest version is safe, but it's not...

 

[mgrev]

if you update without restoring original nand on a n3ds, your device will brick. anything over 6.0 will brick your modified n3ds sysnand. the n3ds downloads the o3ds firmware package, because 8.1 and lower was never built for n3ds.

 

[Boot_8046]

I think that's because 2.1 was made for the o3DS and not for the n3DS, and u actually installed an o3DS firmware into your N3DS, but it's just a surmise.
Hope that I helped..

btw : ur actually the first user that I saw is from Israel..
ISRAEL FTW!!!

 

[royant1]

I think that's because 2.1 was made for the o3DS and not for the n3DS, and u actually installed an o3DS OS into your N3DS, but it's just a surmise.
Hope that I helped..

btw : ur actually the first user that I saw is from Israel..
ISRAEL FTW!!!

 

[regnad]

if you update without restoring original nand on a n3ds, your device will brick. anything over 6.0 will brick your modified n3ds sysnand. the n3ds downloads the o3ds firmware package, because 8.1 and lower was never built for n3ds.

But what do you suppose caused you to fail upgrading to begin with? That's the real issue. You wouldn't be where you are now if that hadn't happened. Did you use the newest version of OTPhelper linked to in the Plailect guide?

 

[Seepy]

btw, the GW is 1.98GB and the one i did during the otp process is 1.69GB, is this normal?

Isn't this the reason it failed? According to the guide, the file sizes should be either 1.21GB or 1.84GB.

Source: https://github.com/Plailect/Guide/wiki/NAND-Size

 

[TheHaxForU]

Wouldn't this have been prevented if he used the sysnand backup validation in otphelper? Not sure if it's in plailects guide, but it should be.

 

[frosty5689]

Should have come to this forum and ask for help when failing to restore backup instead of upgrading the firmware assuming it will be okay.

If that was a viable option, it would've been mentioned as alternative in the guide.