Hacking 2DS XL crashing randomly

[fyredragon]

Yup, I'm afraid so.


Yah, about that. It's not on my GitHub page at this time. I haven't gotten around to doing a write-up talking about this updated script. You can find v1.4 at the way bottom in the release post.

So, I've got it downloaded and running, but then what do I do? flash a stock CTRnand? 'Cause I don't see any options to fix the 3DS firmware unless it's somewhere obvious, again.

 

[TurdPooCharger]

So, I've got it downloaded and running, but then what do I do? flash a stock CTRnand? 'Cause I don't see any options to fix the 3DS firmware unless it's somewhere obvious, again.

Post #18,

.
.

***

If the test setup failed and troubleshooting the 3DS firmware is required,

1. Backup the currently (borked) SysNAND *.bin image.
2. Restore the SysNAND with the image you made when you first hacked the n2DSXL.
3. Continue using the test setup to determine if the system still experiences random crashes.
4. If random crashes goes away, restore the (borked) SysNAND *.bin image to retain your user settings.
5. Fix the 3DS firmware with CTRTransfer (Type D9) - CTRTransfer (use the latest v1.4 script).

***
.
.

If you were planning to skip steps 1-4 and go straight to step 5, I insist at the minimum you at least do step 1.

 

[fyredragon]

Post #18,


If you were planning to skip steps 1-4 and go straight to step 5, I insist at the minimum you at least do step 1.

Sorry for the late response, bad internet.

Anyways, I backed up the borked NAND and restored a fresh one and the crashing went away. So, I understand that I have to use the script, but what option in the script? I've already restored the borked one to retain settings.

 

[TurdPooCharger]

Sorry for the late response, bad internet.

Anyways, I backed up the borked NAND and restored a fresh one and the crashing went away. So, I understand that I have to use the script, but what option in the script? I've already restored the borked one to retain settings.

Instructions in performing CTRTransfer with the script, CTRTransfer (Type D9).

 

[fyredragon]

Instructions in performing CTRTransfer with the script, CTRTransfer (Type D9).

So, I did the transfer, reinstalled everything, but I got one random crash from it bumping my leg.
Also, the volume slider broke somehow. Idk how it happened, but it did.

Should I just buy an entirely new 2DS? this one seems like a lost cause at this point.

 

[TurdPooCharger]

So, I did the transfer, reinstalled everything, but I got one random crash from it bumping my leg.

This reminds of someone who had a n2DSXL where his would either shut off or crash when angling his top screen at a certain way or (bumping?) it.

Due to a design flaw, his solution was to tape his certain flex cable. Finding his thread from the GBAtemp search bar eludes me atm.

Also, the volume slider broke somehow. Idk how it happened, but it did.

DIY fix: N2DS XL Volume Slider Repair

or

wiigotem: [eBay] Nintendo 2DS XL Game Console/System Repair Service,Game Slot.Top LCD & More

Should I just buy an entirely new 2DS? this one seems like a lost cause at this point.

No. Not another n2DSXL. If you're going to replace it, get a n3DSXL instead.

 

[TurdPooCharger]

Ah, found the thread.

• the button ZL chrashes my N2DS XL...

it's a hardware problem, inside of the 2ds there is a ribbon cable on the same site like the LZ button.
if you touch/move this cable a bit it turns the ds off, I fixed it with a bit of duck tape

I just wonder why this specific small ribbon cable does not have something to clip it in like all other ribbon cables

Here's the cable that's being referred to,

• [ifixit] New Nintendo 2DS XL
  • Step 11 at New Nintendo 2DS XL Front Buttons Replacement
• That flex cable next to the ZL push button looks to be part of the lower LCD.
  • [eBay] New Nintendo 2DS XL Replacement Bottom LCD Screen Display and Digitizer

***

With the n2DSXL turned on with HOME Menu running in the background,
Give your n2DSXL a minor slap to the under* side (battery / lower half), or lightly tap the bottom corners against your knee. If the n2DSXL crashes, it's definitely a hardware issue.

 

[fyredragon]

Ah, found the thread.

• the button ZL chrashes my N2DS XL...

Here's the cable that's being referred to,

• [ifixit] New Nintendo 2DS XL
  • Step 11 at New Nintendo 2DS XL Front Buttons Replacement
• That flex cable next to the ZL push button looks to be part of the lower LCD.
  • [eBay] New Nintendo 2DS XL Replacement Bottom LCD Screen Display and Digitizer

***

With the n2DSXL turned on with HOME Menu running in the background,
Give your n2DSXL a minor slap to the under* side (battery / lower half), or lightly tap the bottom corners against your knee. If the n2DSXL crashes, it's definitely a hardware issue.

Again, sorry for the super late reply. The 2DS ran perfectly fine with the hit on the knee and the back. I was wondering, What about ReiSix CFW? I know it hasn't been worked on in years, but would it work? would it fix the crashes?

 

[TurdPooCharger]

Again, sorry for the super late reply. The 2DS ran perfectly fine with the hit on the knee and the back. I was wondering, What about ReiSix CFW? I know it hasn't been worked on in years, but would it work? would it fix the crashes?

The knee tap and buttox slap were simple checks to try crashing the n2DSXL by disturbing loosely connected flex cables like the touchscreen digitizer next to the ZL button. However, they're not definitive in ruling out the cables aren't bad or some other hardware fault.

Your success at restoring the SysNAND with no crashes (post #23) led me to believe your issue was borked 3DS firmware, yet the leg bump (post #25) and rough treatments (post #17) coupled with the general consensus that the n2DSXL's tolerance against abuse and drops is much lower compared to the other 3DS models, also has me to believe your motherboard is damaged like in Scenario (B) (post #16).

***

Rei-Six doesn't work on 3DS firmware 11.12.0-44.

• Update 11.12 and Homebrew

***

If the crashes are software based...
Since SysNAND restore with the good *.bin image worked, but restoring the borked *.bin image, CTRTransfer (Type D9), and 11.12U system update didn't with the crashes returning, the most likely culprit is corrupt file(s) found in:

• [1:] SYSNAND CTRNAND/data

Except for the anti-savegame restore sysdata (00010011) that gets deleted, CTRTransfer (Type D9) v1.4 leaves alone the data folder when repairing the 3DS firmware because that contains the user profile settings. (Type D9) doesn't fix "gamecoin"-type softbricks.

• cfw 2ds xl has black screen on bootup and cant get to home menu

To determine if your crashes are related to this softbrick, perform a (simulated) Format System Memory.

• Don't do a (real) Format System Memory. Avoid System Settings.

1. GodMode9 → [1:] SYSNAND CTRNAND
2. Hold (R)-shoulder and press (X) to rename the data folder to data2.
3. Press (START) button to exit GodMode9.
4. The n2DSXL should boot asking you to make a new user profile. Turn off the n2DSXL and boot back to GodMode9.
   • Don't bother making a dummy profile.
5. Press (HOME) → scripts... → CTRTransfer (Type D9) → Bypass Profile Setup
6. Exit the script. Press (START) to exit GodMode9 and boot HOME Menu.

Outcome

(S) If the crashes go away, the root cause is corrupt files found in data folder.​

-or-

(H) If the crashes persist, restore that (good) sysnand *.bin image and restart from scratch. Check again
​

Continuing...

7. Go back to GodMode9. Press (X) to delete the (dummy) data folder. Rename data2 back to data.​

(S)oftbrick

8s. Finding which extdata or sysdata is the problematic one will be PITA.

• Debugging "gamecoin"-type brick.
• Adjust the procedure by launching to HOME Menu and checking for stability.

(H)ardbrick ?

8h. Either replace the n2DSXL with a n3DSXL, System Transfer or SDTransfer your setup to the target system, and then sell away your n2DSXL for as-is parts. Handle and take better care for that n3DSXL.

• How to perform a System Transfer without losing non-legitimate titles
• (Very Messy Tutorial) SDTransfer: Moving or cloning a (source) system's Nintendo 3DS folder to another (target) system.

-or-

Try to get someone who has a heatgun workstation or electronic oven to fix the n2DSXL motherboard with a solder reflow.

• The RAM and/or NAND chips could have their solder balls busted from the accidental drops and board flex (ie, bending in the pant pockets or back pack with no hard case).
• There's no guarantee a solder reflow will fix the motherboard nor work as a long term solution.
  
• Don't fix it yourself by baking the motherboard in a personal kitchen oven.

 

[Alexander1970]

• Don't fix it yourself by baking the motherboard in a personal kitchen oven.

I thought that only works for PC Graphiccards.

 

[E1ite007]

I thought that only works for PC Graphiccards.

Nope, reflowing works with any kind of electronic components, and it's actually used a lot with Xbox 360s and PS3s.
Reflowing however doesn't work correctly sometiemes with small PCBs and motherboards like the ones in handheld devices like the 3DS, and specific to the New 2DS XL, it's not recommended whatsoever because the New 2DS XL solder points on the motherboard are pretty cheaply made in some units, and can damage the other internals or can burn the entire board.

 

[TurdPooCharger]

Nope, reflowing works with any kind of electronic components, and it's actually used a lot with Xbox 360s and PS3s.
Reflowing however doesn't work correctly sometiemes with small PCBs and motherboards like the ones in handheld devices like the 3DS, and specific to the New 2DS XL, it's not recommended whatsoever because the New 2DS XL solder points on the motherboard are pretty cheaply made in some units, and can damage the other internals or can burn the entire board.

Probably more trouble than it's worth if someone doesn't already have a rework station. If the choice ultimately came down to reflowing the n2DSXL motherboard like for a nand data recovery scenario, I would suggest applying Amtech VS-213-A-TF flux to the SoC & FCRAM and shielding everything else that's close-by with Kapton tape when hitting it with the hot air.

 

[fyredragon]

The knee tap and buttox slap were simple checks to try crashing the n2DSXL by disturbing loosely connected flex cables like the touchscreen digitizer next to the ZL button. However, they're not definitive in ruling out the cables aren't bad or some other hardware fault.

Your success at restoring the SysNAND with no crashes (post #23) led me to believe your issue was borked 3DS firmware, yet the leg bump (post #25) and rough treatments (post #17) coupled with the general consensus that the n2DSXL's tolerance against abuse and drops is much lower compared to the other 3DS models, also has me to believe your motherboard is damaged like in Scenario (B) (post #16).

***

Rei-Six doesn't work on 3DS firmware 11.12.0-44.

• Update 11.12 and Homebrew

***

If the crashes are software based...
Since SysNAND restore with the good *.bin image worked, but restoring the borked *.bin image, CTRTransfer (Type D9), and 11.12U system update didn't with the crashes returning, the most likely culprit is corrupt file(s) found in:

• [1:] SYSNAND CTRNAND/data

Except for the anti-savegame restore sysdata (00010011) that gets deleted, CTRTransfer (Type D9) v1.4 leaves alone the data folder when repairing the 3DS firmware because that contains the user profile settings. (Type D9) doesn't fix "gamecoin"-type softbricks.

• cfw 2ds xl has black screen on bootup and cant get to home menu

To determine if your crashes are related to this softbrick, perform a (simulated) Format System Memory.

• Don't do a (real) Format System Memory. Avoid System Settings.

1. GodMode9 → [1:] SYSNAND CTRNAND
2. Hold (R)-shoulder and press (X) to rename the data folder to data2.
3. Press (START) button to exit GodMode9.
4. The n2DSXL should boot asking you to make a new user profile. Turn off the n2DSXL and boot back to GodMode9.
   • Don't bother making a dummy profile.
5. Press (HOME) → scripts... → CTRTransfer (Type D9) → Bypass Profile Setup
6. Exit the script. Press (START) to exit GodMode9 and boot HOME Menu.

Outcome

(S) If the crashes go away, the root cause is corrupt files found in data folder.​

-or-

(H) If the crashes persist, restore that (good) sysnand *.bin image and restart from scratch. Check again
​

Continuing...

7. Go back to GodMode9. Press (X) to delete the (dummy) data folder. Rename data2 back to data.​

(S)oftbrick

8s. Finding which extdata or sysdata is the problematic one will be PITA.

• Debugging "gamecoin"-type brick.
• Adjust the procedure by launching to HOME Menu and checking for stability.

(H)ardbrick ?

8h. Either replace the n2DSXL with a n3DSXL, System Transfer or SDTransfer your setup to the target system, and then sell away your n2DSXL for as-is parts. Handle and take better care for that n3DSXL.

• How to perform a System Transfer without losing non-legitimate titles
• (Very Messy Tutorial) SDTransfer: Moving or cloning a (source) system's Nintendo 3DS folder to another (target) system.

-or-

Try to get someone who has a heatgun workstation or electronic oven to fix the n2DSXL motherboard with a solder reflow.

• The RAM and/or NAND chips could have their solder balls busted from the accidental drops and board flex (ie, bending in the pant pockets or back pack with no hard case).
• There's no guarantee a solder reflow will fix the motherboard nor work as a long term solution.
  
• Don't fix it yourself by baking the motherboard in a personal kitchen oven.

I believe I had the softbrick. So, I followed the "gamecoin" brick method that you mentioned, and so far the 2DS has been stable! I've had it on for 2 days straight in sleep mode on PKUS and no crashes or freezes. If anything does happen, I'll update you asap.