Hacking [Help] Brick on Waking from Sleep

[alcazar]

Hey all! I recently put CFW on my New 3DS (non-XL) using the 3ds hacks guide, which I did roughly a week and a half ago (before the new system update). During the installation, everything worked fine - I was able to immediately start installing CIAs, downloading themes, all the regular fun stuff. However, ever since I put the custom firmware on it, I've been having a consistent and incredibly annoying problem with waking the DS from sleep mode, in that it will randomly be bricked and force me to do a sysNAND restore.

The problem itself seems to strike at random, or at least be based on something like movement. I've intentionally left the DS on sleep mode overnight to try and brick it, but it always wakes up successfully. However, going for a walk longer than five minutes can lead to a brick, and I had it brick earlier today just from closing it, setting it down, and reopening it.

It doesn't happen immediately either, and neither is it based on the application open. The one earlier today was in the copy of Bravely Default I downloaded the CIA for - I opened the 3DS, moved around a bit, and saved in the game. When I pressed the home button, however, the entire screen froze and I couldn't do anything. I ''was'' able to open the Rosalina menu, but couldn't really think of anything to do other than reboot, which threw a bunch of errors before rebooting into a black, unactionable screen. This kind of brick is par for the course; Every time, I've been able to load into the updater with L + R + A + D-Pad Up, load into Rosalina with Select, and load into GM9 by holding start, but even the updating didn't change anything.

A couple of things that might effect the answers:
* I'm using a 64 GB SDXC card. However, I made sure it's in MBR and formatted to FAT32 with the correct allocation size before putting it into the DS
* When I first installed the CFW, the home menu didn't gain all the extra "pages"/software slots that it was supposed to; They didn't appear until after the first brick and subsequent sysNAND restore. I didn't really question it but it seems kind of weird in hindsight.
* I had previously put CFW on my N3DSXL with no issue, and this issue also didn't exist on my N3DS prior to putting the CFW on it.
* This isn't purely tied to being during games that I downloaded; I've had it happen from internet explorer and even the main home menu.
* I've now update to the new system update, although I've seen people say that it doesn't affect much anyway.
* I've tried to "induce" a brick my closing the DS and shaking it around in case the SD card slot was loose somehow, and was unable to ever intentionally brick it with movements.

Any suggestions would be appreciated, and I'll answer any questions that might help solve this
I'd just like to be able to use one of the most useful features again, as it's a huge drag to power it off every time I want to walk more than five minutes across campus to go to class.

 

[TurdPooCharger]

Check if your SD card is either fake or dying.

1. Copy everything off your SD card to a computer.
2. Quadruple reformat.
3. Full Write + Verify the empty card in H2testw. Do not skip.
   • During the "Verify" second half, you may stop if an error was reported.

Report back your log results.

***

Try clearing/resetting the RAM memory with the battery trick before resorting to sysnand restores.

 

[alcazar]

Thanks for the reply! I've done the quadruple reformat and the H2Testw, there were no errors and the SD card works perfectly. I moved all the files back onto the card afterwards, turned on my DS, put it into sleep mode, went for a walk and...
brick.

Which at least gives me a chance to try out the RAM clearing thing - I was able to get into the Recovery menu, Luma3DS, and the Home Menu, but not GodMode9. I'm unsure if that's what supposed to happen without the SD card in, but whatever, I made it to the actual home menu. After that I reinserted the SD card and everything worked again!

So this at least mitigates how much it sets me back when the issue itself happens, but doesn't resolve the issue itself. Any advice for where to go from here? Should I try removing and reinstalling CFW?

 

[TurdPooCharger]

Thanks for the reply! I've done the quadruple reformat and the H2Testw, there were no errors and the SD card works perfectly. I moved all the files back onto the card afterwards, turned on my DS, put it into sleep mode, went for a walk and...
brick.

Are you carrying your n3DS around in the pocket of tight fitting pants? Even though the 3DS systems (except for the o2DS) are pocketable, it is possible to physically damaged the motherboard if enough pressure is applied to it.

See this example:

• N3DS XL refuses to work correctly with CFW

***

See if lugging the n3DS secured in a hard case causes brick-like state when waking from sleep mode.

Which at least gives me a chance to try out the RAM clearing thing - I was able to get into the Recovery menu, Luma3DS, and the Home Menu, but not GodMode9. I'm unsure if that's what supposed to happen without the SD card in, but whatever, I made it to the actual home menu. After that I reinserted the SD card and everything worked again!

There's a Luma3DS chainloader bug where GodMode9 v1.8.0 won't launch unless there are two (2) *.firm found at:

• GodMode9 v1.8.0 boot issues with Luma 3DS chainloader
  
• [ SD card ] sdmc:/luma/payloads
• [ 3DS NAND ] [1:] SYSNAND CTRNAND/rw/luma/payloads

Update to GodMode9 v1.9.0 for both the SD card and 3DS internal storage.

So this at least mitigates how much it sets me back when the issue itself happens, but doesn't resolve the issue itself. Any advice for where to go from here? Should I try removing and reinstalling CFW?

NO REMOVING CUSTOM FIRMWARE!

• About removing B9S and the safety test

***

I'm currently helping another user debug his n2DSXL so don't feel like writing out steps in what to do again. Refer to his thread for details on how to troubleshoot and pinpoint unknown source of brick,

• 2DS XL crashing randomly

 

[alcazar]

Are you carrying your n3DS around in the pocket of tight fitting pants? Even though the 3DS systems (except for the o2DS) are pocketable, it is possible to physically damaged the motherboard if enough pressure is applied to it.

I guess you cracked it on the first try - I put the 3DS in my pocket and did some stretches as a stress test of sorts, at which point I opened it and found it unresponsive. I cleared the RAM, did the exact same movements but this time but cupping the DS on the equivalent position of my leg (and feeling really silly while doing so), and found it perfectly okay. Guess I'm too tragically fashionable :/

So this gives me the thing to avoid, but I do distinctly remember having had this happen in my backpack at one point, which makes it a tad bit more finicky than I'm really comfortable with. Unscrewing the back to clear the memory every time is pretty obnoxious, so is there any other way to do that? A cursory Google search turned up nothing on that front.


...I could also just make things easier on myself and stop wearing skinny jeans, but where's the fun in that?

 

[TurdPooCharger]

I guess you cracked it on the first try - I put the 3DS in my pocket and did some stretches as a stress test of sorts, at which point I opened it and found it unresponsive. I cleared the RAM, did the exact same movements but this time but cupping the DS on the equivalent position of my leg (and feeling really silly while doing so), and found it perfectly okay. Guess I'm too tragically fashionable :/

Time to start traveling with the n3DS other than by pockets.

You'll want one that encloses the entire n3DS in a hard case or shell. Avoid the ones that are soft fabric pouches.

• [Amazon] Nintendo 3DS & 2DS Cases & Storage

So this gives me the thing to avoid, but I do distinctly remember having had this happen in my backpack at one point, which makes it a tad bit more finicky than I'm really comfortable with. Unscrewing the back to clear the memory every time is pretty obnoxious, so is there any other way to do that? A cursory Google search turned up nothing on that front.

There is no other way in fully resetting the RAM other than by battery removal. Carry a tiny screwdriver along with you like of these:

• [eBay] Cross Screwdriver Repair Tool Screwdriver For NDS, 3DS XL, PS4 Controller

I'm not entirely sure if the crashes you experience is an early sign that one of the accessory parts that connects to the motherboard is dying or rather the motherboard itself is on its way to RIP. Both scenarios are bad, but dying mobo = really bad.

...I could also just make things easier on myself and stop wearing skinny jeans, but where's the fun in that?

No need to give up your lifestyle of wearing skinny jeans. Just don't continue carry the n3DS in your pants pocket, or doing so will eventually hardbrick the system. There's no fun having a n3DS, which is an exceptionally rare model compared to the others, die on you.

If not a hard case holding the n3DS within a back pack or purse/handbag, you can try holstering yours to the side with a phone clip-on case.

• Does a case for 3ds that clip on to your pants like a cell phone holster exist?

 

[The Real Jdbye]

Hey all! I recently put CFW on my New 3DS (non-XL) using the 3ds hacks guide, which I did roughly a week and a half ago (before the new system update). During the installation, everything worked fine - I was able to immediately start installing CIAs, downloading themes, all the regular fun stuff. However, ever since I put the custom firmware on it, I've been having a consistent and incredibly annoying problem with waking the DS from sleep mode, in that it will randomly be bricked and force me to do a sysNAND restore.

The problem itself seems to strike at random, or at least be based on something like movement. I've intentionally left the DS on sleep mode overnight to try and brick it, but it always wakes up successfully. However, going for a walk longer than five minutes can lead to a brick, and I had it brick earlier today just from closing it, setting it down, and reopening it.

It doesn't happen immediately either, and neither is it based on the application open. The one earlier today was in the copy of Bravely Default I downloaded the CIA for - I opened the 3DS, moved around a bit, and saved in the game. When I pressed the home button, however, the entire screen froze and I couldn't do anything. I ''was'' able to open the Rosalina menu, but couldn't really think of anything to do other than reboot, which threw a bunch of errors before rebooting into a black, unactionable screen. This kind of brick is par for the course; Every time, I've been able to load into the updater with L + R + A + D-Pad Up, load into Rosalina with Select, and load into GM9 by holding start, but even the updating didn't change anything.

A couple of things that might effect the answers:
* I'm using a 64 GB SDXC card. However, I made sure it's in MBR and formatted to FAT32 with the correct allocation size before putting it into the DS
* When I first installed the CFW, the home menu didn't gain all the extra "pages"/software slots that it was supposed to; They didn't appear until after the first brick and subsequent sysNAND restore. I didn't really question it but it seems kind of weird in hindsight.
* I had previously put CFW on my N3DSXL with no issue, and this issue also didn't exist on my N3DS prior to putting the CFW on it.
* This isn't purely tied to being during games that I downloaded; I've had it happen from internet explorer and even the main home menu.
* I've now update to the new system update, although I've seen people say that it doesn't affect much anyway.
* I've tried to "induce" a brick my closing the DS and shaking it around in case the SD card slot was loose somehow, and was unable to ever intentionally brick it with movements.

Any suggestions would be appreciated, and I'll answer any questions that might help solve this
I'd just like to be able to use one of the most useful features again, as it's a huge drag to power it off every time I want to walk more than five minutes across campus to go to class.

The extra pages don't start showing up until you have enough games installed to make use of them (or you can make a folder and move it all the way to the right to generate more pages)
I have no idea what would cause those random bricks but it does sound like it might be symptoms of a NAND chip going bad. You could set up an emuNAND and boot off of that for testing purposes and if the bricking issues don't occur there, I suppose sacrificing 1-2 GB of space on your SD card is worth it to avoid those issues.
BTW, it's called a web browser. Internet Explorer is made by Microsoft