Hardware Exiting apps causes 3DS to crash

[FarisMarie]

OoO, juicy discovery.

Okay, so you're not going to like this, but you'll have to do it to truly rule this out.

Disassemble your o3DS and reseat the WiFi module board and antenna cables.

• [iFixit] Nintendo Handheld Console

Dear god I really didn't want to go that path. I'll look for the screwdrivers I need for this I guess...

Just want to mention that I had the exact same issue when I region changed my EmuNand to test some things. The old 3DS couldn't return to the home menu from any applet. I didn't really bother because it was an EmuNand and thought this was normal behavior when you region change a 3DS. The sysNAND that I used as a base works flawless to this very day on this 3DS

BTW I changed the EUR old 3DS to a USA and later to a JAP one

Hmm... so you're saying that's pretty much what happens when you region change? I mean I haven't really seen anyone else with the same problems

 

[ThoD]

Dear god I really didn't want to go that path. I'll look for the screwdrivers I need for this I guess...



Hmm... so you're saying that's pretty much what happens when you region change? I mean I haven't really seen anyone else with the same problems

It's NOT what happens when you region change! It's just a completely unrelated random issue that can happen for various reason.

Before taking apart the 3DS, make sure it happens ONLY when you have the Wi-fi on. If it doesn't, it is NOT a hardware issue and instead simply a problem with your NAND, meaning ctr transfer should fix it. As I said, most common cause for this is badly installed update. However, if it still freezes with Wi-fi off, then open up the 3DS.

 

[FarisMarie]

It's NOT what happens when you region change! It's just a completely unrelated random issue that can happen for various reason.

Before taking apart the 3DS, make sure it happens ONLY when you have the Wi-fi on. If it doesn't, it is NOT a hardware issue and instead simply a problem with your NAND, meaning ctr transfer should fix it. As I said, most common cause for this is badly installed update. However, if it still freezes with Wi-fi off, then open up the 3DS.

Everything still freezes even if wifi is turned off sadly

Edit: My parents don't have the right screwdrivers to fix it. I'll have to go buy some.

This is gonna take a while...

 

[ThoD]

Everything still freezes even if wifi is turned off sadly

Edit: My parents don't have the right screwdrivers to fix it. I'll have to go buy some.

This is gonna take a while...

If it freezes with Wi-fi off, it's almost definitely bad OS install. If only recovery mode worked for you... Don't know why it isn't really:/

 

[TurdPooCharger]

Everything still freezes even if wifi is turned off sadly

Edit: My parents don't have the right screwdrivers to fix it. I'll have to go buy some.

This is gonna take a while...

@FarisMarie, before you disassemble the 3DS, did you back up your SysNAND that has your JPN firmware?

There's another (safer) way to determine if WiFi module is at fault: revert to a previous NAND state last-last known working with Internet.

 

[FarisMarie]

@FarisMarie, before you disassemble the 3DS, did you back up your SysNAND that has your JPN firmware?

There's another (safer) way to determine if WiFi module is at fault: revert to a previous NAND state last-last known working with Internet.

I don't... I only have a NAND backup of before I updated to 11.9 (the firmware was 11.5 before updating)

 

[TurdPooCharger]

I don't... I only have a NAND backup of before I updated to 11.9 (the firmware was 11.5 before updating)

That's even better! Revert to 11.5 and then try updating to 11.9 in either Recovery Mode or System Settings.

If this 11.5 backup is the original JPN firmware, make a backup of the current EUR 11.9.

 

[FarisMarie]

That's even better! Revert to 11.5 and then try updating to 11.9 in either Recovery Mode or System Settings.

If this 11.5 backup is the original JPN firmware, make a backup of the current EUR 11.9.

The 11.5 backup in EUR region as far as I know, would it make a difference?

 

[TurdPooCharger]

The 11.5 backup in EUR region as far as I know, would it make a difference?

There's no difference if it's EUR or JPN.

If this 11.5 EUR NAND backup was made before updating to 11.9, you will quickly find out if the 3DS WiFi works or not. If it doesn't update like last time, there's good reason to believe it's the WiFi module.

Either way, if it's not WiFi, we'll know to look at NAND repair.

 

[FarisMarie]

There's no difference if it's EUR or JPN.

If this 11.5 EUR NAND backup was made before updating to 11.9, you will quickly find out if the 3DS WiFi works or not. If it doesn't update like last time, there's good reason to believe it's the WiFi module.

Either way, if it's not WiFi, we'll know to look at NAND repair.

Okai then I'll do that. Before I do I need to know... I've heard downgrading firmware will result in a brick. Is this a difference situation?

Also the backup was before I downloaded any CIAs. So do I back up all the data through checkpoint or is there a better way?

 

[TurdPooCharger]

Okai then I'll do that. Before I do I need to know... I've heard downgrading firmware will result in a brick. Is this a difference situation?

Also the backup was before I downloaded any CIAs. So do I back up all the data through checkpoint or is there a better way?

Downgrading through sysUpdater with system title *.cia files is the one known to easily brick. People who employ this method are most likely creating a fraken firmware so they can continue using the obsolete Gateway 3DS flashcart.

Downgrading with your own made SysNAND image that is known to work shouldn't brick. The only ways you can brick restoring your SysNAND is if:

1. Your SD card is fake or faulty. If you never checked it before, better do a full Write + Verify with the card empty using H2testw.
2. The 3DS shuts off in mid SysNAND restore due to power failure; you intentionally pulled out the battery or it ran out of juice.

 

[FarisMarie]

Downgrading through sysUpdater with system title *.cia files is the one known to easily brick. People who employ this method are most likely creating a fraken firmware so they can continue the obsolete Gateway 3DS flashcart.

Downgrading with your own made SysNAND image that is known to work shouldn't brick. The only ways you can brick restoring your SysNAND is if:

1. Your SD card is fake or faulty. If you never checked it before, better do a full Write + Verify with the card empty using H2testw.
2. The 3DS shuts off in mid SysNAND restore due to power failure; you intentionally pulled out the battery or it ran out of juice.

Oh I see. Well at first I thought my SD card was fake because it's a 16GB SD card but when inserted into my laptop it says it's 14GB. So I did the H2testw. It said that it's legit so I shouldn't worry right...?

 

[lone_wolf323]

Oh I see. Well at first I thought my SD card was fake because it's a 16GB SD card but when inserted into my laptop it says it's 14GB. So I did the H2testw. It said that it's legit so I shouldn't worry right...?

Your card takes up some room for the internal components. Which is why you never have the full 16gb or 32gb to use.

 

[TurdPooCharger]

Oh I see. Well at first I thought my SD card was fake because it's a 16GB SD card but when inserted into my laptop it says it's 14GB. So I did the H2testw. It said that it's legit so I shouldn't worry right...?

Had your computer stated 16 GB, that would have raised red flags of fake card.

Did you scan the card when it was empty? Testing with H2testw will not provide clean results if there is preoccupied data.

 

[FarisMarie]

Your card takes up some room for the internal components. Which is why you never have the full 16gb or 32gb to use.

Ah, I didn't know that. Thank you for clarifying!

Had your computer stated 16 GB, that would have raised red flags of fake card.

Did you scan the card when it was empty? Testing with H2testw will not provide clean results if there is preoccupied data.

Yes I backed up all the files on the SD card, formatted it and did the test

 

[TurdPooCharger]

Ah, I didn't know that. Thank you for clarifying!

Yes I backed up all the files on the SD card, formatted it and did the test

Okay, then you're good to go with restoring the SysNAND. Other thing to keep in mind is whether or not the SysNAND *.bin image was created on a good SD card.

 

[FarisMarie]

Okay, then you're good to go with restoring the SysNAND. Other thing to keep in mind is whether or not the SysNAND *.bin image was created on a good SD card.

It was created on the same SD card so...

 

[TurdPooCharger]

It was created on the same SD card so...

Let us know if the 11.5 downgrade followed by 11.9 update worked or not.

 

[FarisMarie]

Let us know if the 11.5 downgrade followed by 11.9 update worked or not.

Will do. But the game CIAs? What do I do with them?

 

[TurdPooCharger]

Will do. But the game CIAs? What do I do with them?

Oh I forgot about those. Back up the saves + extdata with Checkpoint or JKSM. Your installed games will still be in the Nintendo 3DS folder.

After you downgrade, you will lose tickets for your games. However, this is easily fixable with faketik. This app which will regenerate and reinstall tickets for titles missing them.