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.
***
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.
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.
- GodMode9 → [1:] SYSNAND CTRNAND
- Hold (R)-shoulder and press (X) to rename the data folder to data2.
- Press (START) button to exit GodMode9.
- 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.
- Press (HOME) → scripts... → CTRTransfer (Type D9) → Bypass Profile Setup
- 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
8
s. Finding which
extdata or
sysdata is the problematic one will be PITA.
(H)ardbrick ?
8
h. 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.
-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.