Hardware Hardmod Capabilities/Limitations Question

LudivousKain

New Member
OP
Newbie
Joined
May 21, 2016
Messages
3
Trophies
0
Age
41
XP
41
Country
United States
Okay, I'm still a relative n00b when it comes to console modding, especially in handhelds. As it is, The only two consoles I've ever attempted to mod were my Wii and my :yaynds: (succeeded with both, btw).

I'm rather tech-savvy and handy with a soldering iron thanks to my work ("repairing" old/obsolete laboratory equipment with antiquated PCBs is one of the many joys in my line of work), so I'm very confident I would be able to successfully hardmod my 'former' o3DS. I've not been able to determine whether a hardmod would allow me to do what I want (if it's even possible), despite spending a few hours on a few days searching for any information about my issue/desire.

Long story short, I removed the microSD card from my original (Zelda ooT edition) o3DS, the card got physically damaged without me realizing it, and upon reinsertion to the system seems to have fried something that's now causing that 3DS to not boot. When the power buttom is pressed, the blue light appears to 'pulse' a single time before going out. There is no sound generated by the system. No flashing lights. The blue light just calmly turns on, then fades off at the same speed in which it turned on. It takes approximately one second to go from off, to fully on, and then return to off. I ended up "abandoning" the system as permenantly broken and purchased a used o3DS. (There were several issues I was battling including fussy shoulder buttons, so the used system was basically used for parts. I now have an o3DS that functions flawlessly, using the original ooT 3DS body)

Sorry about that wall of text, but the background may be useful in determining whether my goal is even possible. Basically, I had a TON of save data on the original system I want to salvage if it's possible. The only NAND backup I have was the last one I created when following the Plailect Guide. So, it is effectively useless.

I was wondering: If I hardmod the old motherboard, is it likely I would be able to somehow recover the save data for system titles (it had A9LH so I still have the OTP for that system) if the NAND itself was not damaged by whatever broke the system?

And yes, I am aware that each console is "unique" and that dumps are not interchangeable.
 

Temptress Cerise

Miss Magic~ <3
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
So wait, your Zelda ooT edition o3DS had A9LH? Sounds like your SD Card got corrupted, and because it couldn't find the arm9loaderhax.bin, it would refuse to boot. Since this is normal for an A9LH system. Did you try using a new SD card with an arm9loaderhax.bin file on it to see if it would boot?

As for your saves, if your SD card got corrupted, they may be gone, because as far as I am aware, saves are stored on the SD Card and not on the NAND, though I am not particularly knowledgeable on that.
 
  • Like
Reactions: LudivousKain

LudivousKain

New Member
OP
Newbie
Joined
May 21, 2016
Messages
3
Trophies
0
Age
41
XP
41
Country
United States
Sounds like your SD Card got corrupted, and because it couldn't find the arm9loaderhax.bin

That was my original thought, too. I had a backup of the sd card from immediately after I finished setting up A9LH so I put everything on another card. Still no love...

Previously, I had intentionally tried to boot the system without an SD card inserted to see what it was like, and the system typically would just automatically load the CakesFW config utility.

I just tried the same thing with the frankensteined system, and it did EXACTLY THE SAME THING the dead system does! I will investigate this further.

btw- I'm not sure what system titles save to the sd card and what saves make it to the internal memory. I _THINK_ the ones I care about (Streetpass Plaza, mainly) save to the NAND since I believe they remained with the system through several complete SD reformats before I initially modded my system.

I will post a follow-up reply after I do some more troubleshooting based on what I just learned. Thanks for reply, Cerise.
 

LudivousKain

New Member
OP
Newbie
Joined
May 21, 2016
Messages
3
Trophies
0
Age
41
XP
41
Country
United States
Okay, here's what I JUST discovered:

Apparently the SD card slot was damaged by the broken card mentioned in my OP. The original card was physically damaged (cracked), which likely resulted in a short that fried the actual card-reader. I just swapped the fried reader with a 3rd I have laying around (yes, my office is like a graveyard for random things that I think may be useful one day lol), attached the old screens/etc and would you have guessed it: the thing actually BOOTED! I have absolutely NO idea why it previously would autoboot to the CakesFW config without a card. This issue (as mentioned above) had cost me a significant amount of time trying to troubleshoot. I even tested continuity across the two micro-fuses...

I would have definitely benefited from a description better than the "you will no longer be able to boot without the SD card in, that is normal" statement on the guide I followed. In fact, even when entering the exact 'symptoms' I was only finding references to a broken ribbon cable (each case also referenced a pop sound, something I didn't have). Then again, maybe I'm the only one to ever have difficulty like this. ;)
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    SylverReZ @ SylverReZ: https://www.youtube.com/watch?v=uLN9qrJ8ESs