Hacking 3DS stuck on 2.1 - read OP.

[Bu2d85]

What is the nand supposed to be named? NANDmin.bin or NAND.bin?

It depends on the type of backup he made. The default when doing the CTR transfer to 2.1 is NANDmin.bin. If he did not choose the default then it is NAND.bin.

Have him check to see if his computer is hiding extensions and to make sure it is not named NANDmin.bin.bin.

 

[Tenshi_Okami]

What is the nand supposed to be named? NANDmin.bin or NAND.bin?

It's the same thing tbh, it should be located in the files9 folder. First make a backup of it

Second, make sure it's not named NANDmin.bin.bin or NAND.bin.bin

Third, make sure the NANDmin.bin is located inside the files9 folder

When you followed this 3 stuff, and it still does not appear(or if it does) message in here.

 

[spacemaninspace]

I found myself stuck on 2.1 and I updated to 4.X via Animal Crossing New Leaf, which absolutely fucked me over. System settings and the browser were completely nonfunctional so I sent it to a hardmodder. If only the browser worked, then the solution would've been easier. Hope you have more luck than I did.

 

[Bedel]

He's got Decrypt9 loaded and no matter what he names his nand backup it says no usable file found.

It's not the file but the buckup itself. Say to him to search into the files9 folder for the backup, and if it's not there or something, then he'll need to do a CTRNAND Transfer to 9.x, a New3DS version.

 

[Bu2d85]

What is the nand supposed to be named? NANDmin.bin or NAND.bin?

Also, if you are using an older version of decrypt9 the nand.bin needs to be on the root of the sd card. Not in the files9 folder.

I messed that up once too.

 

[Majickhat55]

I don't see how it wasn't common sense to know you can't update in any capacity a N3DS from a firmware that it never had, or it will brick period. That's the entire reason you make a backup in the first place. The solution would have been to turn the DS off and leave it off until he got a better connection. The oldest available firmware on N3DS is 9.2 and is the ONLY one you can update from that won't cause a brick. Anything lower than that will definitely screw itself if you try to update it.

 

[lisreal2401]

It's all good now, his connection became stable and we got the latest version of Decrypt9 to work which restored the nand, downgraded again and got it hacked. Close one though.

 

[Tenshi_Okami]

I don't see how it wasn't common sense to know you can't update in any capacity a N3DS from a firmware that it never had, or it will brick period. That's the entire reason you make a backup in the first place. The solution would have been to turn the DS off and leave it off until he got a better connection. The oldest available firmware on N3DS is 9.2 and is the ONLY one you can update from that won't cause a brick. Anything lower than that will definitely screw itself if you try to update it.

Actually, 4.X is safe for N3DS, before it worked for people that ended with broken browsers n stuff. But it appears that TWL breaks when using CTR transfer. Sure we should not update to 4.X, but since it worked before, it was worth to do it again!

Now the community knows what would happen if the N3DS updates to 4.X, making it a slight chance to open Decrypt9 again and be able to restore the NAND :3

It's all good now, his connection became stable and we got the latest version of Decrypt9 to work which restored the nand, downgraded again and got it hacked. Close one though.

That's great! I'm glad it worked out in the end tell your friend that he also helped us to understand better what would happen with the new hacks if we updated to 4.X

To everyone reading this, don't try the updating method to 4.X until you don't have any other choice, ask around first before doing anything

 

[Majickhat55]

Any firmware that wasn't available on a N3DS, regardless if the console operates or not, has a chance to brick when you mess with system titles period. That's not just true for DS lines either. When you run an OS with an incompatible firmware, you're putting yourself at risk. Period.

 

[Tenshi_Okami]

Any firmware that wasn't available on a N3DS, regardless if the console operates or not, has a chance to brick when you mess with system titles period. That's not just true for DS lines either. When you run an OS with an incompatible firmware, you're putting yourself at risk. Period.

I see your point, but you don't see mine :/ if you read the thread, my intentions were not to do this update, it was just a theory, I saw it work before so I thought it would be good to mention it as an option.

Now we know what will happen if you do it, OP didn't read my warning by mistake, and continued to do the method. Nobody is at fault here, it's just a human error that's all

 

[Majickhat55]

I see your point, but you don't see mine :/ if you read the thread, my intentions were not to do this update, it was just a theory, I saw it work before so I thought it would be good to mention it as an option.

Now we know what will happen if you do it, OP didn't read my warning by mistake, and continued to do the method. Nobody is at fault here, it's just a human error that's all

Oh I wasn't blaming you or anything, just making a point in general about the risks of running incompatible softwares. They don't always play nice Lol

 

[Tenshi_Okami]

Oh I wasn't blaming you or anything, just making a point in general about the risks of running incompatible softwares. They don't always play nice Lol

Oh okay, I do know this! I wouldn't had told him the 4.X thing if it didn't work tbh