Homebrew N3DS possibly bricked by closing lid while on wifi on 2.1?

[The Catboy]

You're a going to need a hardmod to fix this. Just make sure you keep all NAND back ups to properly restore your system.

 

[N7Kopper]

Make that a lesson to any newbies to modding scenes - if you're running a firmware build designed for different hardware, make dead sure you do what you needed to do as fast as possible, and get out. Don't even breathe on the damn thing at a weird angle. Just because the N3DS is backwards compatible with O3DS only games, and can do weird emulation stuff of the Circle Pad Pro using it's bult-in version, doesn't mean that it works with the firmware.

Kinda hoping I never have to downgrade a N3DS to O3DS firms like that.

 

[godstriker8]

Jesus just downgraded yesterday, and this terrified me at how close I was to breaking it.
All I needed to do was close the lid, maybe even by accident and it would've ruined it.

 

[uribemaster]

Why was this thread revived after 2 months?

 

[freedeess]

Happened to me aswell

Have you tried what GerbilSoft suggested and pull the battery? Pulling the battery is known to reset some stuff (like if WiFi is disabled), so maybe it resolves this too?

 

[Ordim3n]

Have you tried what GerbilSoft suggested and pull the battery? Pulling the battery is known to reset some stuff (like if WiFi is disabled), so maybe it resolves this too?

Already tried

 

[lplayerf]

After installing CFW, can you close the lid or will it still brick?

 

[pre10c]

It bricls if you close the lid while on 2.1, when you do the downgrade to 2.1. keep on going till the Point where you Restore your backup backup to 9.2. after that you are safe to close it

 

[bennyman123abc]

Closing the lid of the N3DS while it is running FW 2.1 corrupts the MCU partition for some reason. You need a hardmod to recover from that brick. Or you can just get a new 3DS.

 

[ketal]

I can't be bothered reading the first two pages, but if you left it in sleepmode while it was on 2.1, it's dead for good

 

[GerbilSoft]

Closing the lid of the N3DS while it is running FW 2.1 corrupts the MCU partition for some reason. You need a hardmod to recover from that brick. Or you can just get a new 3DS.

Not the standard eMMC hardmod, though. The methods for restoring the MCU aren't publicly available AFAIK.

 

[bennyman123abc]

Well, then you really f*cked up. Time for a new 3DS then

 

[adrifcastr]

Putting a New 3DS on 2.1.0 in sleep mode is known to cause an UNRECOVERABLE brick! This only happens when shutting the lid while the device is on; this does not apply to turning the device off. You should continue without delay to avoid any possibility of this happening!

 

[MarioMasta64]

Maybe @Plailect can add a warning about it in the guide.

im pretty sure he already has? and yea, no way through this than hardmod.

 

[adrifcastr]

im pretty sure he already has? and yea, no way through this than hardmod.

Putting a New 3DS on 2.1.0 in sleep mode is known to cause an UNRECOVERABLE brick! This only happens when shutting the lid while the device is on; this does not apply to turning the device off. You should continue without delay to avoid any possibility of this happening!

 

[mario-lucis-caelum]

Doesn't the guide warn you not to put your 3ds in sleep mode or else it would brick? O_O

 

[MarioMasta64]

hopefully he made the backup for the nand. also in my experience the screen dims more and more as youre on 2.1 (after doing the browser arm11.bin thing while making rainbows

 

[Eastonator12]

So I have been trying to setup A9LH, and I'm on the part where I injected 2.1 unbricked (N3DS) into my SysNAND, but I closed my 3DS on the 2.1 browser screen while I went to go take a shower (~20 min) and the screen was black when I came back. Now whenever I start up my system, I get "an error has occurred, please turn off the power" immediately as I boot. No luck trying to get into recovery mode, hangs at a black screen, screen turns on, but is pitch black. I've tried removing my SD when booting, but no luck there either. Is this recoverable or is a hardmod needed to restore a nand backup?

You need a hardmod, it says on then 2.1 ctr transfer not to close on new3ds systems...read everything beforehand

 

[Icirrus]

I'm sorry but this is your own fault tbh, if you don't read and follow the instructions properly you're done. I had installed a hardmod myself for a friends N3DS and was able to fix his so that's what you'll need to do

 

[adrifcastr]

hopefully he made the backup for the nand. also in my experience the screen dims more and more as youre on 2.1 (after doing the browser arm11.bin thing while making rainbows

the brick is unrecoverable as the guide says, for some unknown reason this bricks the MCU and there is no public way to recover that, he literally screwed up his 3ds, a nand backup wouldn´t bring you any success in recovering the MCU