Hacking An error occurred on 2.1.0 downgrade

[prototech]

So I may have made a huge mistake with this latest 3DS hack, so any help would be much appreciated.

I downgraded a N3DS to 2.1.0 successfully and booted into 2.1.0 sysNAND, but I believe I left it in sleep mode all night because I woke up to turning it on and seeing the dreaded "An error occurred".

The OTP guide says

"There have been multiple reports of bricks caused by leaving a 2.1.0 New 3DS in sleep mode for long periods of time. Because of this, you should avoid leaving the device in sleep mode and could complete Part V without delay (this strictly applies to devices left in sleep mode for long periods of time, not devices that are being used)."

But no recovery instructions are provided. Is there anything I can do?

EDIT
Could I possibly use the recovery menu to upgrade to 11.0, and then use my other 3DS to downgrade with DSIWare? (I saw some tutorial about that, though I haven't looked too far into it).

After reading more of the guide, it appears using the recovery mode would result in a brick on N3DS 2.1.0 if it wasn't already, so I guess that's out of the question...

EDIT
Kind people in the IRC say my only option is a hardmod. If anyone has other solutions, let me know, but I'll probably try and get this swapped for a warranty after work and if that doesn't work then I'll be looking into a hardmod.

 

[Quantumcat]

So I may have made a huge mistake with this latest 3DS hack, so any help would be much appreciated.

I downgraded a N3DS to 2.1.0 successfully and booted into 2.1.0 sysNAND, but I believe I left it in sleep mode all night because I woke up to turning it on and seeing the dreaded "An error occurred".

The OTP guide says

"There have been multiple reports of bricks caused by leaving a 2.1.0 New 3DS in sleep mode for long periods of time. Because of this, you should avoid leaving the device in sleep mode and could complete Part V without delay (this strictly applies to devices left in sleep mode for long periods of time, not devices that are being used)."

But no recovery instructions are provided. Is there anything I can do?

EDIT
Could I possibly use the recovery menu to upgrade to 11.0, and then use my other 3DS to downgrade with DSIWare? (I saw some tutorial about that, though I haven't looked too far into it).

After reading more of the guide, it appears using the recovery mode would result in a brick on N3DS 2.1.0 if it wasn't already, so I guess that's out of the question...

EDIT
Kind people in the IRC say my only option is a hardmod. If anyone has other solutions, let me know, but I'll probably try and get this swapped for a warranty after work and if that doesn't work then I'll be looking into a hardmod.

If you just bought it - you shouldn't have a problem returning it saying it doesn't work.

 

[fikatr]

Try booting into recovery mode and updating your system.
This probably will not work for an Old 3DS downgraded to 2.1.0
This will BRICK a New 3DS downgraded to 2.1.0

your only option is hardmod you cant do anything

 

[prototech]

If you just bought it - you shouldn't have a problem returning it saying it doesn't work.

That's what I'm hoping, it's less than a week old.

Try booting into recovery mode and updating your system.
This probably will not work for an Old 3DS downgraded to 2.1.0
This will BRICK a New 3DS downgraded to 2.1.0

your only option is hardmod you cant do anything

This is the sad truth I'm realizing. I've done the research and I think I can do it, but sadly this is a friends so I might go the route of a mobo swap if he doesn't want to risk the hardmod.

 

[fikatr]

That's what I'm hoping, it's less than a week old.


This is the sad truth I'm realizing. I've done the research and I think I can do it, but sadly this is a friends so I might go the route of a mobo swap if he doesn't want to risk the hardmod.

if you dont know anything about 3ds mobo swap is dangerous as hardmod there are so much little cables someone can just install a hardmod for your friend

 

[prototech]

if you dont know anything about 3ds mobo swap is dangerous as hardmod there are so much little cables someone can just install a hardmod for your friend

I worked in cell phone repair for almost two years, and I have replaced a circle pad on an O3DS XL, so I'm not too worried about swapping boards.

 

[Swiftloke]

I wonder why sleep mode of all things bricks an n3ds, and why it only happens when left for long periods of time.

 

[Majickhat55]

Why would you even go to bed without dumping the OTP first and getting back to 9.2 completing at LEAST that portion? IIRC the guide says NOT to put your 3DS in sleep mode on 2.1, or let it die, or let the battery fall out, or turn it off etc etc....

 

[prototech]

I wonder why sleep mode of all things bricks an n3ds, and why it only happens when left for long periods of time.

No idea, the possibility didn't even cross my mind. I was just happy the downgrade worked and I shut the lid and went to bed.

Why would you even go to bed without dumping the OTP first and getting back to 9.2 completing at LEAST that portion? IIRC the guide says NOT to put your 3DS in sleep mode on 2.1, or let it die, or let the battery fall out, or turn it off etc etc....

It was getting very late, the RedNAND downgrade failed once and took more time than it should have, and I wanted to get some rest and not be rushed and tired with the fear of making a mistake. Ironically enough, me being in my tired state trying to finish up that portion of the guide led me to completely missing the portion of text that details this exact problem. I have done this process several times and never actually noticed that text, I'm not even sure when it was introduced, so as soon as I saw 2.1.0 boot up I had a sigh of relief, shut the lid, and went to bed in hopes of finishing this with a fresh mind. Alas, that was not the case.

 

[Majickhat55]

Well lessons learned I guess. Still sucks you got a brick though, hope you can exchange it

 

[prototech]

Well lessons learned I guess. Still sucks you got a brick though, hope you can exchange it

So we now have a 11.0.0 brand new N3DS. It looks like I can downgrade using my already hacked 3DS' with DSiWare.

My new question is, so long as I back up my sysNAND, my game saves, and my SD card, I should be able to restore my 3DS to full functionality, correct? I want to factory reset my hacked 3DS to prevent any problems, since the DSiWare downgrade involves a system transfer.

https://github.com/Plailect/Guide/wiki/DSiWare-Downgrade

 

[fikatr]

So we now have a 11.0.0 brand new N3DS. It looks like I can downgrade using my already hacked 3DS' with DSiWare.

My new question is, so long as I back up my sysNAND, my game saves, and my SD card, I should be able to restore my 3DS to full functionality, correct? I want to factory reset my hacked 3DS to prevent any problems, since the DSiWare downgrade involves a system transfer.

https://github.com/Plailect/Guide/wiki/DSiWare-Downgrade

You can restore everything except your nnid




gatewait.

 

[prototech]

You can restore everything except your nnid




gatewait.

Right, unless I do another system transfer in a week, correct?
The downgrade worked and the 3DS and it's at 9.2.0, and I should have both of these for a week, so I should be good.