Hacking Hardware Need advanced help with 3DS SD card issue, unable to find a solution anywhere

ResomationAudio

New Member
Newbie
Joined
Feb 17, 2026
Messages
2
Reaction score
1
Trophies
0
Age
40
XP
26
Country
United States
Hello! New member but a long time lurker. I am a hardware technician with 15+ years of professional electronics repair experience. Normally, I do extensive research and the solution to my problem presents itself, and I attempt every reasonably solution I can find.

I am currently working on a modded Old 3DS XL handheld that is running the latest version of Luma, and while playing Miitopia the SD card stopped functioning. Upon returning to the home screen, a message popped up: "Could not detect an SD card. The software on the SD card could not be displayed." This is the fourth Old 3DS XL unit I have modded, and the other three have functioned for months with no issues, so I do not believe it to be the result of a faulty install.

Technical details of the system:
  • System software: Sys 11.17.0-50U
  • SD card details - 64GB SanDisk ImageMate, 140MB/s, Formatted FAT32 with 32kb allocation unit size
  • Running current version of Luma and Godmode9

My troubleshooting steps, in order, are below:
  • Cleaned SD card pins and contacts inside SD socket on motherboard using 93% isopropyl alcohol, no change
  • Backed up contents of SD card, reformatted/wiped card, verified using h2testw. Test was good and SD was verified
  • Loaded a fresh copy of Luma and Godmode9 with all applicable folders onto SD and booted into chainloader. Godmode9 will not load past "...booting" message in bottom right corner.
  • Got a second SD card, Toshiba 2GB. Formatted as FAT32, verified with h2testw, but left it blank. Booted to home screen of 3DS and inserted card, got the same "Could not detect an SD card" issue.
  • Removed the motherboard and desoldered SD card reader. Replaced with a known good reader from a second unit. Cleaned after installation using 93% isopropyl.
  • Inserted original SanDisk SD card into unit and powered on. Boots to Luma settings menu, but after saving settings it loads to the homescreen correctly. Since the software had been removed, there was nothing to load, but it did boot correctly once and it read the SD card, and it created a new Nintendo 3DS folder in the file structure.
  • I attempted to restore a previous image using Godmode9. When booting, Godmode9 loads correctly. However, when attempting to open the SD inside Godmode9, an error message pops up saying the SD is corrupted. After returning to the main menu of Godmode9, the SD is no longer present. Attempted to load SD using menu prompt, but it failed.
  • Booted to the luma home screen, and the "Could not detect an SD card" message appears again.
  • Using a known good board and a signal injector/oscilloscope, verified correct readings on all SD card reader pins. They were practically identical to the known good unit.
  • Cleaned SD socket pins again, no change.

My best guess is that this is a software issue, based on the hardware repair restoring SD functionality before the failure repeated. Am I missing anything? Are there any other possible solutions to this issue? Any assistance is greatly appreciated. I have been unable to find documentation on signal paths from each of these pins, and am unable to trace them to other components that may be causing the issue. I don't want to randomly start swapping ICs either, since I really hate reballing chips without a stencil and the risk of that process resulting in a failure is very, very high.
 
Got a second SD card, Toshiba 2GB. Formatted as FAT32, verified with h2testw, but left it blank. Booted to home screen of 3DS and inserted card, got the same "Could not detect an SD card" issue.
Don't you have another SD card to test?
Shouldn't 2GB be formatted as FAT?
Is the OP using an SD card adapter? The adapter can easily have issues.
.
If it is confirmed that the SD card and the slot connections are fine, check the power supply to the SD card slot, the problem might be with the CPU connection, and the CPU need to be re-soldered.
 
Last edited by k66,
  • Like
Reactions: Kwyjor
Don't you have another SD card to test?
Shouldn't 2GB be formatted as FAT?
Is the OP using an SD card adapter? The adapter can easily have issues.
.
If it is confirmed that the SD card and the slot connections are fine, check the power supply to the SD card slot, the problem might be with the CPU connection, and the CPU need to be re-soldered.
Correct, the 2GB card was formatted as FAT. I was tired and fat fingering things.

Since the original post, I performed additional testing with two more SD cards, one full size 32GB and one micro 32GB in an adapter. No change. Didn't have any time to test further yesterday but I'm diving in again today. Can't believe I didn't consider it wasn't getting power, that's a real obvious thing to check. I'll test the signal along the power connection and then check solder points on the CPU.

Thanks for the help! I'll reply to the thread (or edit this message if there are no replies) if I get stumped again.
 
  • Like
Reactions: k66
Any more results from this?
I Have been having the similar issues, tested like the 5 micro sd cards I own.
Sys 11.17.0-50U
New 3ds XL has CFW.

It has been opened into , Needed to replace like , everything, Screen, Speakers, Even changed the SD card Reader and that didnt change anything, (also no home button so I havent done some fixes)
mistakenly changed the boot.firm in the system so now it doesnt boot at all ( Just blue lights for a second and softly turns off) .
and without it being able to read the SD , cant read the boot.firm, so its kinda bricked.


But before that it also said "could not detect SD card" in the setting menu and gm9 used to just freeze when an SD card was inserted).

Ive seen a few others having this problem this year...makes me wonder is these systems are just dying ...
 
This is entirely unrelated and a total 3am thought (so probably bs) but have you used the pretendo network at all? Or any other sort of secondary NNID?
I wouldn't be surprised if it was a software issue related to authenticating what data you are able to access. Since you're not supposed to use a 3ds without a NNID, it would make sense that you don't have access to whatever storage there is. But idk how it really works on a technical level

I also think that it possibly be something you downloaded from like the homebrew store or something with sd reading functionality. Games with miis are interesting because they inevitably have to do some reading of the miis on the system, and i would bet that the fault lies somewhere in there.

Just a shot in the dark but we could also look into software constants. Has everyone with this issue played a specific game like Miitopia where they encountered the issue during runtime?
 
I wouldn't be surprised if it was a software issue related to authenticating what data you are able to access. Since you're not supposed to use a 3ds without a NNID, it would make sense that you don't have access to whatever storage there is. But idk how it really works on a technical level
Why exactly would you expect an NNID to do anything when a unit is not connected to the Internet? People use units without an NNID all the time, i.e. after a region change.

This is entirely unrelated and a total 3am thought (so probably bs)
If you're about to post something that you think is "probably bs", perhaps you should at least wait until morning..?
 
Last edited by Kwyjor,
A friend of mine has been working on bringing my own New 3ds XL back from the dead after a local tech butchered it, and after everything was back together and they finally got it booting again, the exact issue described in the op occurred, port's been swapped, connector swapped, all the values they could measure seem good, and there's zero resources for tracking where and how the traces connect to everything besides just surface photos of the board. any direction would be a godsend
 
A friend of mine has been working on bringing my own New 3ds XL back from the dead after a local tech butchered it, and after everything was back together and they finally got it booting again, the exact issue described in the op occurred, port's been swapped, connector swapped, all the values they could measure seem good, and there's zero resources for tracking where and how the traces connect to everything besides just surface photos of the board. any direction would be a godsend
Sorry to bump this but does anyone have any further inside into this problem?
 

Site & Scene News

Popular threads in this forum