Hardware Exiting apps causes 3DS to crash

[TurdPooCharger]

Yes that is true, I'm very curious to know how all this stuff works! Very interesting stuff imo! So I should use that backup NAND I have that for some reason gives me the latest JPN firmware?

And after using Decrypt9 to get the firmware back to 11.5 should I check if everything works before proceeding? I'm rather okai with hex editing as long as I got a very deeeetaaaiilled guide XD

That 11.9 JPN SysNAND image you have, I'm guessing it's your very first NAND backup made shortly after hacking the o3DS but before region changing the firmware.

If the system applets weren't working when you tried them out in 11.9 JPN, that means the o3DS was sold to you like that before it was hacked.

***

You have three (similar) approaches in how to go about this, and none of which we won't know if they'll work out.

Hmm... Since @ThoD does have a point that CTRTransfer in Decrypt9WIP should be avoid if it can be helped, let's try his idea first.

***

Is your o3DS currently flashed back to 11.9 EUR since you mentioned about playing games while waiting for test results?

 

[FarisMarie]

That 11.9 JPN SysNAND image you have, I'm guessing it's your very first NAND backup made shortly after hacking the o3DS but before region changing the firmware.

If the system applets weren't working when you tried them out in 11.9 JPN, that means the o3DS was sold to you like that before it was hacked.

***

You have three (similar) approaches in how to go about this, and none of which we won't know if they'll work out.

Hmm... Since @ThoD does have a point that CTRTransfer in Decrypt9WIP should be avoid if it can be helped, let's try his idea first.

***

Is your o3DS currently flashed back to 11.9 EUR since you mentioned about playing games while waiting for test results?

Sorry for late reply, I didn't get the notif! No I haven't flashed back the NAND yet. I decided to Wait. Should I go ahead and do so?

 

[TurdPooCharger]

Sorry for late reply, I didn't get the notif! No I haven't flashed back the NAND yet. I decided to Wait. Should I go ahead and do so?

1. Restore the SysNAND with your 11.9 EUR firmware using GodMode9.
2. Downgrade using the 11.5 EUR o3DS CTRTransfer with Decrypt9WIP. See post #50 (skip the 11.9 updating step; not yet).

Edit 1 - Bad instructions.

2 (fixed). Downgrade using the 11.5 EUR o3DS CTRTransfer with GodMode9.​

***

If you have SecureInfo_A,

3A. GodMode9 → [1:] SYSNAND CTRNAND/rw/sys/SecureInfo_A → Press (Y) to [CLIPBOARD] select.
4A. Press (Y) again → Copy path(s) → <A> yes → button combo → SecureInfo_B → <A> yes.
​

If you have SecureInfo_B,

3B. GodMode9 → [1:] SYSNAND CTRNAND/rw/sys/SecureInfo_B → Press (Y) to [CLIPBOARD] select.
4B. Press (Y) again → Copy path(s) → <A> yes → button combo → SecureInfo_A → <A> yes.​

Edit 2 - If a mistake was made with CLIPBOARD, press (Select) to reset selection.

Edit 3 - To change the name of the file, move the ^ symbol underneath the letters with the (left/right) d-pad. Change the letters with (up/down) d-pad.

***

• You should now have SecureInfo_A, SecureInfo_B, and SecureInfo_C.
• You want to default keeping SecureInfo_A as the original, unedited version.

***

5. SecureInfo_B → Press (A) → Show in Hexeditor → Hold (R)-shoulder & press (Y) to change hex view.
6. Press (A) → <A> yes → button combo → Scroll down to 0x100 hex offset. See post #13.
7. While the number is highlighted red, hold (A) and press (Up) d-pad. Change the value: 00 → 02.
8. Press (B) → <A> yes → Press (B) → <A> yes.
9. Turn off the 3DS. Turn it back on and hold (L)+(R)+(A)+(Up) d-pad to access Recovery Mode. Update to 11.9.0-42E.​

 

[FarisMarie]

1. Restore the SysNAND with your 11.9 EUR firmware using GodMode9.
2. Downgrade using the 11.5 EUR o3DS CTRTransfer with Decrypt9WIP. See post #50 (skip the 11.9 updating step; not yet).

***

If you have SecureInfo_A,

3A. GodMode9 → [1:] SYSNAND CTRNAND/rw/sys/SecureInfo_A → Press (Y) to [CLIPBOARD] select.
4A. Press (Y) again → Copy path(s) → <A> yes → button combo → SecureInfo_B → <A> yes.
​

If you have SecureInfo_B,

3B. GodMode9 → [1:] SYSNAND CTRNAND/rw/sys/SecureInfo_B → Press (Y) to [CLIPBOARD] select.
4B. Press (Y) again → Copy path(s) → <A> yes → button combo → SecureInfo_A → <A> yes.​

***

• You should now have SecureInfo_A, SecureInfo_B, and SecureInfo_C.
• You want to default keeping SecureInfo_A as the original, unedited version.

***

5. SecureInfo_B → Press (A) → Show in Hexeditor → Hold (R)-shoulder & press (Y) to change hex view.
6. Press (A) → <A> yes → button combo → Scroll down to 0x100 hex offset. See post #13.
7. While the number is highlighted red, hold (A) and press (Up) d-pad. Change the value: 00 → 02.
8. Press (B) → <A> yes → Press (B) → <A> yes.
9. Turn off the 3DS. Turn it back on and hold (L)+(R)+(A)+(Up) d-pad to access Recovery Mode. Update to 11.9.0-42E.​

Well it's already on 11.9 EUR from yesterday. Should I just CTRTransfer?

Nevermind I'll restore the one before because of fcs and stufd

 

[TurdPooCharger]

Well it's already on 11.9 EUR from yesterday. Should I just CTRTransfer?

CTRTransfer * with Decrypt9WIP (not with GodMode9).

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

Well it's already on 11.9 EUR from yesterday. Should I just CTRTransfer?

Nevermind I'll restore the one before because of fcs and stufd

Hey, can you stop for a moment. I had a brain fart.

 

[FarisMarie]

CTRTransfer * with Decrypt9WIP (not with GodMode9).

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


Hey, can you stop for a moment. I had a brain fart.

Okai stopping-

 

[TurdPooCharger]

Okai stopping-

Alright now that we've cleared my mistake. Yes, continue with CTRTransfer in GodMode9 as you correctly pointed out.

@ThoD, I think I'm losing my touch doing this. Sheeat.

 

[ThoD]

Alright now that we've cleared my mistake. Yes, continue with CTRTransfer in GodMode9 as you correctly pointed out.

@ThoD, I think I'm losing my touch doing this. Sheeat.

Don't worry about it, happens, I've lost my touch so much that unless it's for something simple I don't even bother with advice and instead tag you or someone else

 

[TurdPooCharger]

Picking up from yesterday, FarisMarie stated in PM her system applets were still stuck loading after completing the first approach in post #63 (* CTRTransfer in GodMode9).

We are now left with the sucky option(s). I tried a variation of 11.5 JPN n3DS CTRTransfer in Decrypt9WIP where there is only SecureInfo_A (no B and no C) that was 0x100 edited for JPN = 00, and my 3DS still soft bricked. There is no way around this except further corrections to be made in GodMode9.

***

With the o3DS now back at 11.9 EUR firmware,

1. GodMode9 → [1:] SYSNAND CTRNAND/rw/sys/SecureInfo_A → Copy to 0:/gm9/out.

• This will back up a clean (unedited) copy. Just in case.

2. SecureInfo_A → Press (X) → <A> yes → <A> yes → button combo → <A> yes.

• This will delete SecureInfo_A.

3. SecureInfo_B → Press (X) → <A> yes → <A> yes → button combo → <A> yes.

• This will delete SecureInfo_B.

4. SecureInfo_C → hold (R)-shoulder and press (X) → SecureInfo_A → <A> yes → button combo → <A> yes.

• This will rename SecureInfo_C as the new SecureInfo_A.
• Show in Hexeditor, make sure that the 0x100 offset is set to 02 (EUR).

5. Boot the o3DS to HOME Menu and Recovery Mode. Verify that both modes work with having only SecureInfo_A.

6. Downgrade using the 11.5 EUR o3DS CTRTransfer with Decrypt9WIP. See post #50 (skip the 11.9 updating step; not yet).

• Yes, Decrypt9WIP for realsies this time.
• Step #0: Optional NAND backup - You can skip this with (B) button since these are already made.
• Remember to put both *.bin and *.sha in files9 folder. This program will SHA-256 hash check the image.

***

After CTRTransfer, the o3DS will mostly likely boot with an ARM9 error.

***

7. GodMode9 → while hovering, white highlighting on [1:] SYSNAND CTRNAND → hold (R)-shoulder and press (A) → Fix CMACs for drive → <A> yes → button combo → <A> yes → button combo → <A> to continue → <A> yes.

• This will fix the CMAC hashes for certain *.db files found within the 1:/dbs directory that CTRTransfer in Decrypt9WIP was not able to account for.

***

The o3DS should now be able to boot to HOME Menu. However...

***

8. Recreate your exact user profile from scratch.
9. Update to 11.9 EUR firmware in either System Settings or Recovery Mode.
10. Check all the system applets (Game Notes, Friend List, Nofications, Internet Browser [online website visits], etc).

• *crosses fingers*

11. Restore the missing tickets for HOME Menu games, DLCs, updates with faketik.
​

***

And we're not done yet..

***

12. In GodMode9, rename the (edited) SecureInfo_A back to SecureInfo_C.
13. Make a copy of SecureInfo_C and rename that as SecureInfo_B.
14. Go to 0:/gm9/out/SecureInfo_A → Press (Y) to [CLIPBOARD] select.
15. Back out with (B) button. Go to 1:/rw/sys directory. Press (Y) → Move path(s) → <A> yes → button combo → <A> yes.

• You should now have all three SecureInfo_A/B/C.

***

16. Verify again that both HOME Menu and Recovery Mode works. Also check those system applets are still working.
17. If everything is working as they're suppose to, back up a new SysNAND *.bin & *.sha image.​

 

[FarisMarie]

Picking up from yesterday, FarisMarie stated in PM her system applets were still stuck loading after completing the first approach in post #63 (* CTRTransfer in GodMode9).

We are now left with the sucky option(s). I tried a variation of 11.5 JPN n3DS CTRTransfer in Decrypt9WIP where there is only SecureInfo_A (no B and no C) that was 0x100 edited for JPN = 00, and my 3DS still soft bricked. There is no way around this except further corrections to be made in GodMode9.

***

With the o3DS now back at 11.9 EUR firmware,

1. GodMode9 → [1:] SYSNAND CTRNAND/rw/sys/SecureInfo_A → Copy to 0:/gm9/out.

• This will back up a clean (unedited) copy. Just in case.

2. SecureInfo_A → Press (X) → <A> yes → <A> yes → button combo → <A> yes.

• This will delete SecureInfo_A.

3. SecureInfo_B → Press (X) → <A> yes → <A> yes → button combo → <A> yes.

• This will delete SecureInfo_B.

4. SecureInfo_C → hold (R)-shoulder and press (X) → SecureInfo_A → <A> yes → button combo → <A> yes.

• This will rename SecureInfo_C as the new SecureInfo_A.
• Show in Hexeditor, make sure that the 0x100 offset is set to 02 (EUR).

5. Boot the o3DS to HOME Menu and Recovery Mode. Verify that both modes work with having only SecureInfo_A.

6. Downgrade using the 11.5 EUR o3DS CTRTransfer with Decrypt9WIP. See post #50 (skip the 11.9 updating step; not yet).

• Yes, Decrypt9WIP for realsies this time.
• Step #0: Optional NAND backup - You can skip this with (B) button since these are already made.
• Remember to put both *.bin and *.sha in files9 folder. This program will SHA-256 hash check the image.

***

After CTRTransfer, the o3DS will mostly likely boot with an ARM9 error.

***

7. GodMode9 → while hovering, white highlighting on [1:] SYSNAND CTRNAND → hold (R)-shoulder and press (A) → Fix CMACs for drive → <A> yes → button combo → <A> yes → button combo → <A> to continue → <A> yes.

• This will fix the CMAC hashes for certain *.db files found within the 1:/dbs directory that CTRTransfer in Decrypt9WIP was not able to account for.

***

The o3DS should now be able to boot to HOME Menu. However...

***

8. Recreate your exact user profile from scratch.
9. Update to 11.9 EUR firmware in either System Settings or Recovery Mode.
10. Check all the system applets (Game Notes, Friend List, Nofications, Internet Browser [online website visits], etc).

• *crosses fingers*

11. Restore the missing tickets for HOME Menu games, DLCs, updates with faketik.
​

***

And we're not done yet..

***

12. In GodMode9, rename the (edited) SecureInfo_A back to SecureInfo_C.
13. Make a copy of SecureInfo_C and rename that as SecureInfo_B.
14. Go to 0:/gm9/out/SecureInfo_A → Press (Y) to [CLIPBOARD] select.
15. Back out with (B) button. Go to 1:/rw/sys directory. Press (Y) → Move path(s) → <A> yes → button combo → <A> yes.

• You should now have all three SecureInfo_A/B/C.

***

16. Verify again that both HOME Menu and Recovery Mode works. Also check those system applets are still working.
17. If everything is working as they're suppose to, back up a new SysNAND *.bin & *.sha image.​

Since I didnt get an ARM9 error while booting, I skipped step 7. I recreated my profile went into the applets and...

N o p e. Its still freezing. Restored all the Secure_Info files and everything still works except the applets.

 

[TurdPooCharger]

Since I didnt get an ARM9 error while booting, I skipped step 7. I recreated my profile went into the applets and...

N o p e. Its still freezing. Restored all the Secure_Info files and everything still works except the applets.

It is strange that neither CTRTransfer in GodMode9 and Decrypt9WIP coupled with updating in Recovery Mode or Setting Systems is fixing your system applets.
This leads me to believe there may be something wrong with your o3DS hardware. The 3DS/2DS systems are known to not have fail safe if parts are broken.

Can you verify if both your outer and inner cameras work?

• Press (L)+(R) shoulder buttons at the same time to pull up the camera applet.
• There's also launching Nintendo 3DS Camera.
• or, System Settings → Other Settings → [3D Screen Check | Outer Cameras]

Check the microphone with "Mic Test" or by blowing into the microphone while in HOME Menu. You should see games with 3D banners spin really fast.

Also check all your buttons, slider switches, and touch screen with the 3DSident-GUI.
When you're in this app, press (Start) + (Select) at the same time to pull up the interactive menu.

 

[FarisMarie]

It is strange that neither CTRTransfer in GodMode9 and Decrypt9WIP coupled with updating in Recovery Mode or Setting Systems is fixing your system applets.
This leads me to believe there may be something wrong with your o3DS hardware. The 3DS/2DS systems are known to not have fail safe if parts are broken.

Can you verify if both your outer and inner cameras work?

• Press (L)+(R) shoulder buttons at the same time to pull up the camera applet.
• There's also launching Nintendo 3DS Camera.
• or, System Settings → Other Settings → [3D Screen Check | Outer Cameras]

Check the microphone with "Mic Test" or by blowing into the microphone while in HOME Menu. You should see games with 3D banners spin really fast.

Also check all your buttons, slider switches, and touch screen with the 3DSident-GUI.
When you're in this app, press (Start) + (Select) at the same time to pull up the interactive menu.

Inner camera looks fine, but outer camera... I think ones broken beacuse the picture comes out in pink and purple. Nintendo 3DS Camera works. When using the camera in 3D it feels like its only going through one eye.

3D works if its not in camera. Mic works, and all buttons. The touch screen doesnt work around the sides. It was like that when I bought it so I already knew the touch screen problem. But it never affected my gameplay so I didnt mind much.

 

[TurdPooCharger]

Inner camera looks fine, but outer camera... I think ones broken beacuse the picture comes out in pink and purple. Nintendo 3DS Camera works. When using the camera in 3D it feels like its only going through one eye.

3D works if its not in camera. Mic works, and all buttons. The touch screen doesnt work around the sides. It was like that when I bought it so I already knew the touch screen problem. But it never affected my gameplay so I didnt mind much.

That camera view where one eye sees the 3D image and other does not means one of the dual rear lens is totally busted. The 3DS can't make a 3D image, so the parallax in the upper LCD shows one eye black (nothing) while the other sees the pink mess. If that one side sees pink, this indicates this side too may have a cracked lens, liquid damage, misalignment, etc.

For the touchscreen, the digitizer has lost the ability to register input for those sides. You might be able to fix this by:

• Removing any screen protector film it has on. Plastic film can dampen sensitivity or trap dust.
  
• Clean the side edges of dust and dirt specs with light strokes using a toothbrush and fine tip toothpick.
  
• Re-calibrate: System Settings → Other Settings → Touch Screen

While a slightly broken digitizer isn't likely to cause the 3DS to completely stop working, a dead rear camera assembly can make it refuse to boot to HOME Menu with an infamous Black Screens of Death symptom.

I think yours an edge case where that rear camera isn't dead but certain system modules freeze up when they don't get the input response they're expecting from the bad lens side. This would be kinda like if you're driving down a road where the light turns from green to yellow. Drivers are fairly certain whether they can drive past it or have to slow down before the light turns red. Now, the problem is this specific street light stays yellow and doesn't turn red at all. How are you suppose to react to that?

***

What does this all means?
To fix those system applet hang ups would require replacing the rear camera assembly. Because the parts located in the upper half of the 3DS have delicate flex cables that goes through one of the hinges, disassembly to get to that camera can end up breaking them.

Recommendation.
Until the day that rear camera dies and causes your system to experience BSoD, forget about replacing it and just live without those system applets. Your 3DS still works for the most part. It's not worth the risk.

 

[FarisMarie]

Honestly I was thinking it had water damage due to the digitizer not working on the sides. Calibrating the touch screen doesnt help. I'll try the other methods tho (even if I did check for dirt but there wasnt any). As for the cameras, thanks for the explanation. I dont wanna risk breaking it more so I will leave it as is until it gives up on life xD All that matters is that it still works with that problem eh?

I'd like to thank everyone who helped! I really appreaciate it!

That camera view where one eye sees the 3D image and other does not means one of the dual rear lens is totally busted. The 3DS can't make a 3D image, so the parallax in the upper LCD shows one eye black (nothing) while the other sees the pink mess. If that one side sees pink, this indicates this side too may have a cracked lens, liquid damage, misalignment, etc.

For the touchscreen, the digitizer has lost the ability to register input for those sides. You might be able to fix this by:

• Removing any screen protector film it has on. Plastic film can dampen sensitivity or trap dust.
  
• Clean the side edges of dust and dirt specs with light strokes using a toothbrush and fine tip toothpick.
  
• Re-calibrate: System Settings → Other Settings → Touch Screen

While a slightly broken digitizer isn't likely to cause the 3DS to completely stop working, a dead rear camera assembly can make it refuse to boot to HOME Menu with an infamous Black Screens of Death symptom.

I think yours an edge case where that rear camera isn't dead but certain system modules freeze up when they don't get the input response they're expecting from the bad lens side. This would be kinda like if you're driving down a road where the light turns from green to yellow. Drivers are fairly certain whether they can drive past it or have to slow down before the light turns red. Now, the problem is this specific street light stays yellow and doesn't turn red at all. How are you suppose to react to that?

***

What does this all means?
To fix those system applet hang ups would require replacing the rear camera assembly. Because the parts located in the upper half of the 3DS have delicate flex cables that goes through one of the hinges, disassembly to get to that camera can end up breaking them.

Recommendation.
Until the day that rear camera dies and causes your system to experience BSoD, forget about replacing it and just live without those system applets. Your 3DS still works for the most part. It's not worth the risk.

Honestly I was thinking it had water damage due to the digitizer not working on the sides. Calibrating the touch screen doesnt help. I'll try the other methods tho (even if I did check for dirt but there wasnt any). As for the cameras, thanks for the explanation. I dont wanna risk breaking it more so I will leave it as is until it gives up on life xD All that matters is that it still works with that problem eh?

A huge thank you to you and @ThoD for helping! I really appreaciate it!

 

[Jhynjhiruu]

I hate to bump a dead thread and I'm sorry for that, but I'm having this exact issue, having made an EmuNAND and region changed to CHN. The system works absolutely fine, system applications work perfectly, updating seems to work as normal, but exiting the applets causes the console to hang on the home menu loading screen as shown in this thread. SecureInfo_A in my EmuNAND has 0x100 set to 02 (EUR), _C has it set to 04 (CHN), and to make sure, I copied _A to _B and changed that to 04 - still no change. Any ideas?

 

[Dragonface]

I have the same exact problem region changing from JPN to USA.

 

[TurdPooCharger]

I have the same exact problem region changing from JPN to USA.

Adding your first post from,

• Applets freeze when pressing home after region transfer

So it's an odd one. I did a region transfer following the guide here (JP to US). It was successful, no problems. So I did the updates and whatnot, and I'm good to go. I open up notifications, but if I press home, it'll show the normal screen "HOME Menu" but will just freeze.

I read a page where someone had similar issues on here (can't post links unfortunately, too new, but the title of the post is "Exiting apps causes 3DS to crash", posted by FarisMarie)
I tried a few of the things, but no luck. I tried checking all my hardware bits but it doesn't seem to be the issue, and I did the part where the dude asked him to check that the correct region is set in the hex edit, and it is correct.

So then I figured maybe I just did something wrong, so I tried the region transfer again. Same issue.

So THEN I wondered if perhaps it's nothing to do with the region transfer and I just have a busted 3DS. So I restored to the original NAND before I region transferred.....and there's no problems. I can open and close applets with no issue. Weird. So I tried the region transfer again, with all new fresh files...and it's happening again. I thought maybe it's just stalled and will resolve, but it's definitely frozen (Waited 5 mins, no results.)

Does anyone have any idea how to figure something like this out? It's an odd one.

Edit just checked, if I close the lid, the screen will turn off, but it looks like the 3DS doesn't actually sleep. It just turns the screen off.

Attempt to repair the 3DS firmware + custom firmware with CTRTransfer (Type D9) - CTRTransfer. Carefully read and follow the Instructions.