Hacking Need to finish a9'ing one, but how to I restore from the other?

[codezer0]

Okay, lemme see if I can summarize this properly?

Okay. First was a 3ds xl whose board started at 4.4. I had that one first with GW, but then using A9+GW. Had it up to date up to about 11.1 before something happened, and now that board won't boot anymore. Followed plailect's guide reasonably well.

Swapped the refurb board back in; started with 8.1 sysNAND. Followed plailect's guide as of today. Got up to where it was telling me to update, but it failed to update. So I had to restore the nand (preserving a9) to go back to 8.1. Got to the step of launching homebrew launcher, but found it just gives an error launching and tells me to press start to return back to the home menu. Trying luma updater presently as installed per the instructions, just causes it to basically endlessly stay at that "Nintendo 3DS" screen when it would launch a game or app. Still nothing.

So, a couple of questions.

1. I'm not kidding when I say I had everything on the first... a 32gig SD card with all my stuff installed, freeshop, and not least of which, a completed save file of Alpha Sapphire, which includes my fiance's loaned critters. Is there any way to restore the save files to have them work on this other unit? What about my NNID? the ambassador rewards?
2. For this new one, what should I do to get this stuff working correctly again?

 

[OrGoN3]

1. You can restore your NNID on any console. That will allow you to redownload any purchased content and keep your "gamertag". Ambassador rewards should be tied to your NNID. As for saves, yes. JK's Save Manager, or JKSM, https://github.com/J-D-K/JKSM/releases)

2. So you did the guide starting on 8.1, then did what? What type of 3DS? Did you do ctrtransfer or otpless A9LH? You then installed A9LH, put Luma3DS on there, did the right options, then went to update your system. The system failed to update so you thought it would be best to restore 8.1 for whatever reason? Ok but I'm still confused. If you already put A9LH on there and went back to 8.1, why would you attempt to launch the homebrew launcher? Wouldn't your first and only step be to update the system since A9LH is already on there?

If you can still load payloads prior to the home menu, then A9LH is still intact. I would repost with the error messages of why it won't update. Chances are, it's the home menu is the incorrect version. That seems to be the most common issue. Other issues can be if you still had it set to use custom DNS that blocks updates on the 3DS or on the router.

 

[codezer0]

1. You can restore your NNID on any console. That will allow you to redownload any purchased content and keep your "gamertag". Ambassador rewards should be tied to your NNID. As for saves, yes. JK's Save Manager, or JKSM, https://github.com/J-D-K/JKSM/releases)

2. So you did the guide starting on 8.1, then did what? What type of 3DS? Did you do ctrtransfer or otpless A9LH? You then installed A9LH, put Luma3DS on there, did the right options, then went to update your system. The system failed to update so you thought it would be best to restore 8.1 for whatever reason? Ok but I'm still confused. If you already put A9LH on there and went back to 8.1, why would you attempt to launch the homebrew launcher? Wouldn't your first and only step be to update the system since A9LH is already on there?

If you can still load payloads prior to the home menu, then A9LH is still intact. I would repost with the error messages of why it won't update. Chances are, it's the home menu is the incorrect version. That seems to be the most common issue. Other issues can be if you still had it set to use custom DNS that blocks updates on the 3DS or on the router.

I can't run JKSM on the original. It won't boot at all. JKSM won't help me if I can't start up the system that the saves originated on, last I recall.

Both of them are O3DS XL's. I got up to the part of installing A9, but right now it won't launch hbloader and it won't launch lumaupdater. I had to restore to 8.1 with A9 because it kept erroring out when attempting to do the regular update.

 

[OrGoN3]

I can't run JKSM on the original. It won't boot at all. JKSM won't help me if I can't start up the system that the saves originated on, last I recall.

Both of them are O3DS XL's. I got up to the part of installing A9, but right now it won't launch hbloader and it won't launch lumaupdater. I had to restore to 8.1 with A9 because it kept erroring out when attempting to do the regular update.

If you can't boot up the original, how would you think you could recover a save? Will it power on at all to do a hardmod nand dump? You might be able to get saves from that. Other than that, unless the games saved to the SD card, you're out of luck.

Based on your setup, the only time you should've updated is after A9LH was installed. So when you say you got up to that part, did you finish it originally? You are still leaving out so much. I also asked if payloads will still load prior to home menu. This would be something like HourGlass9 or Decrypt9WIP that you would have to hold down start or x while powering on. If you hold select while powering on, do you see the Luma3DS config menu? If so then A9LH is on there and as I said, troubleshoot the update error. Still confused as to why you downgraded instead of troubleshooting the inability to update the system. It's a pretty common problem after A9LH'ing your system.

Also, A9LH = Arm9 Loader Hax. To just say A9, to each their own, but it sounds weird. If you want to stick with 2 characters, K9 would be appropriate.

 

[codezer0]

What do you mean I'm leaving out so much?

for the love of god...

I HAD an O3DS XL. It was on 4.4. This is the one I'd been using that has my NNID, my saves, my installs, my everything. it won't turn on anymore. It just immediately shuts itself off. I followed the directions back then, and have the files made from A9'ing that system then. I was led to believe that those dumped files could then be used to transfer the save data (at the VERY least) to the new(er) system I'm prepping now.

Refurb board. Stuck that back in into the same guts. It does turn on. Started with 8.1. Did the A9 process down to 2.1 and finish getting the OTP and the files over. However, when I get to the point of attempting to update, it just errors out and restarts the system. Per the advice on the page, I restored the NAND for 8.1 to restore it, and have A9. But after installing HB Launcher and LumaUpdater, I get to the point where it wants me to launch HBLauncher, but it flat out refuses to launch, saying it can't download something, tells me to press start and then throws up another error back on the home menu. And LumaUpdater never actually loads.

I don't need someone that's going to be argumentative and making me angry with this right now. I'm just trying to get at least SOMETHING going on here because far as it looks like, my original board is dead, and I'm having to make due with this refurb board and two busted screens that somehow still operate. If you're going to be this aggravating about it, please leave and let somebody more knowledgeable chime in. I'm already stressed out enough for the fact that all signs point to my original board being spontaneously dead.

 

[OrGoN3]

What do you mean I'm leaving out so much?

for the love of god...

I HAD an O3DS XL. It was on 4.4. This is the one I'd been using that has my NNID, my saves, my installs, my everything. it won't turn on anymore. It just immediately shuts itself off. I followed the directions back then, and have the files made from A9'ing that system then. I was led to believe that those dumped files could then be used to transfer the save data (at the VERY least) to the new(er) system I'm prepping now.

Refurb board. Stuck that back in into the same guts. It does turn on. Started with 8.1. Did the A9 process down to 2.1 and finish getting the OTP and the files over. However, when I get to the point of attempting to update, it just errors out and restarts the system. Per the advice on the page, I restored the NAND for 8.1 to restore it, and have A9. But after installing HB Launcher and LumaUpdater, I get to the point where it wants me to launch HBLauncher, but it flat out refuses to launch, saying it can't download something, tells me to press start and then throws up another error back on the home menu. And LumaUpdater never actually loads.

I don't need someone that's going to be argumentative and making me angry with this right now. I'm just trying to get at least SOMETHING going on here because far as it looks like, my original board is dead, and I'm having to make due with this refurb board and two busted screens that somehow still operate. If you're going to be this aggravating about it, please leave and let somebody more knowledgeable chime in. I'm already stressed out enough for the fact that all signs point to my original board being spontaneously dead.

There is no need to be a complete dick to somebody that is attempting to help you. Nor do you need to infer I don't know what I'm talking about. NOR did you need to create a brand new thread on top of posting to the 3DS noob thread. So how about starting off with following the rules before biting the hand that feeds?

I bolded and underlined the part that you never mentioned that now tells me, or anyone else, where you were with the process. Describing it how you did without that part doesn't tell me where you left off. Sure, it made sense in your head, because you just experienced it. Moving on...

WHEN YOU ARE TURNING ON THE SYSTEM, IF YOU HOLD DOWN SELECT, DO YOU SEE THE LUMA3DS CONFIG MENU?

No idea why you keep ignoring that. If yes then I know that A9LH is still on the system. Just because you did the keep A9 option, doesn't mean everything was successful and A9LH wasn't overwritten for some reason. If you confirmed you have A9LH and Luma3DS, you can update via recovery mode (L+R+Up+A). This updates the system to the latest version, 11.2. Requires WiFi.

So you were on 2.1 and restored to 8.1. So now you're on 8.1 with Luma3DS, right? Homebrew launcher doesn't seem to like firmware under 9.x.x, as there are no otherapp payloads for firmware under 9.x.x. I don't think it can run below 9.x.x. Does FBI still load up and let you install? (of course this is pointless if you do the previous step).

Edit: When you said the guide told you to restore your previous NAND image, where were you that it said that? That part is still unclear, as I am clicking all of the troubleshooting links and don't see it. TY.

Edit2: You can't restore a NAND from a different system. So you can't restore your original system's NAND to your new one. You would have to look into extracting files from your NAND backup. I have no experience with that.

 

[trinhno]

Updating from 2.1 usually throws up error. Try again after confirming that you still have A9LH since you're now on 8.1.
If you're have the movable.sed from the old system, you can try injecting it using Decrypt9. Should be able to use the old Nintendo 3DS folder. Always back up first.

PS: Didn't think @OrGoN3 was aggravating or anything. He simply just asked for more info.

 

[OrGoN3]

Updating from 2.1 usually throws up error. Try again after confirming that you still have A9LH since you're now on 8.1.
If you're have the movable.sed from the old system, you can try injecting it using Decrypt9. Should be able to use the old Nintendo 3DS folder. Always back up first.

PS: Didn't think @OrGoN3 was aggravating or anything. He simply just asked for more info.

Thanks for confirming what I mentioned. Based on what he said, he may only have the NAND backup from his original unit. Do you know if there is a way to mount that without using a 3DS so that he can obtain his movable.sed? Or am I in fairytale land with that line of thinking?

 

[trinhno]

Thanks for confirming what I mentioned. Based on what he said, he may only have the NAND backup from his original unit. Do you know if there is a way to mount that without using a 3DS so that he can obtain his movable.sed? Or am I in fairytale land with that line of thinking?

Unless you also have the xorpad, there's no way to decrypt that NAND image without the original board working.

 

[proflayton123]

If you be rude to someone is trying to help it won't get you far, remember that for future reference, OP.

 

[OrGoN3]

Unless you also have the xorpad, there's no way to decrypt that NAND image without the original board working.

Darn. Well, let's hope OP reads what you wrote and maybe, just maybe, for some reason, he decided to dump his xorpads (perhaps for older cia creation??). It's a possibility. Thanks for answering that by the way.

 

[Amapola62]

I think..not really sur though that at some point the guide included a section where one of the tools automatically dumped some "rescue nand data" files like movable.sed or Xorpads...

 

[codezer0]

There is no need to be a complete dick to somebody that is attempting to help you. Nor do you need to infer I don't know what I'm talking about. NOR did you need to create a brand new thread on top of posting to the 3DS noob thread. So how about starting off with following the rules before biting the hand that feeds?

I bolded and underlined the part that you never mentioned that now tells me, or anyone else, where you were with the process. Describing it how you did without that part doesn't tell me where you left off. Sure, it made sense in your head, because you just experienced it. Moving on...

WHEN YOU ARE TURNING ON THE SYSTEM, IF YOU HOLD DOWN SELECT, DO YOU SEE THE LUMA3DS CONFIG MENU?

No idea why you keep ignoring that. If yes then I know that A9LH is still on the system. Just because you did the keep A9 option, doesn't mean everything was successful and A9LH wasn't overwritten for some reason. If you confirmed you have A9LH and Luma3DS, you can update via recovery mode (L+R+Up+A). This updates the system to the latest version, 11.2. Requires WiFi.

So you were on 2.1 and restored to 8.1. So now you're on 8.1 with Luma3DS, right? Homebrew launcher doesn't seem to like firmware under 9.x.x, as there are no otherapp payloads for firmware under 9.x.x. I don't think it can run below 9.x.x. Does FBI still load up and let you install? (of course this is pointless if you do the previous step).

Edit: When you said the guide told you to restore your previous NAND image, where were you that it said that? That part is still unclear, as I am clicking all of the troubleshooting links and don't see it. TY.

Edit2: You can't restore a NAND from a different system. So you can't restore your original system's NAND to your new one. You would have to look into extracting files from your NAND backup. I have no experience with that.

Me? Get rude? You're the one that kept asking the same question that I already answered if you'd bothered to pay attention the first time. The fact that I'm having to post it again when I'm already stressed out trying to figure out what the crap is going wrong is why I'm angry at you. It's already bad enough that I have a situation where the top screen is all purple and the bottom one is grainier than a VHS recording of a Sega Saturn Let's play. As it is, I still don't get what the hell happened with my original, much less why it's refusing to work when the other board will in the same guts...

Yes, if I hold select on the 8.1 system, I get the Luma3DS config. If I put the 4.4 board back in, it doesn't matter what I hold. It just powers on then immediately off. And this is with the same screens and guts and everything else. FBI loads fine. In the guide, it gets to the part to run system update. It says if it keeps erroring out, just restore the NAND backup that I made initially, which is what I did.

The older process did have me make a bunch of files from the 4.4 system, including the OTP and some other files that I backed up on my external hard drive and on my Google drive.

If you be rude to someone is trying to help it won't get you far, remember that for future reference, OP.

I have no patience for someone that isn't going to listen when I've already spelled it out for them. Asking for something I already explained in the beginning, just tells me that you couldn't be bothered to read/listen.

I'm already ticked off as it is that this 3DS system is in such a bad way, and that I'm not even able to repair this one, much less curently put anything away toward getting another. You really think I'm going to have time for someone trying to act like an MLG dude brah brat when I'm trying to salvage my last remaining system here?

--------------------- MERGED ---------------------------

I think..not really sur though that at some point the guide included a section where one of the tools automatically dumped some "rescue nand data" files like movable.sed or Xorpads...

Thankfully it did for both systems in question. But most of what I try to find myself toward making those save files accessible simply imply that I'm still able to turn on and use the original system in question. At this point, I can't do that.

--------------------- MERGED ---------------------------

Meanwhile, wake up this morning, start the process again. this time it's able to system update no problem, and now HBLauncher works as intended.

*headdesk* why wasn't it working last night? AUGH!

 

[el_gonz87]

Me? Get rude? You're the one that kept asking the same question that I already answered if you'd bothered to pay attention the first time. The fact that I'm having to post it again when I'm already stressed out trying to figure out what the crap is going wrong is why I'm angry at you. It's already bad enough that I have a situation where the top screen is all purple and the bottom one is grainier than a VHS recording of a Sega Saturn Let's play. As it is, I still don't get what the hell happened with my original, much less why it's refusing to work when the other board will in the same guts...

Yes, if I hold select on the 8.1 system, I get the Luma3DS config. If I put the 4.4 board back in, it doesn't matter what I hold. It just powers on then immediately off. And this is with the same screens and guts and everything else. FBI loads fine. In the guide, it gets to the part to run system update. It says if it keeps erroring out, just restore the NAND backup that I made initially, which is what I did.

The older process did have me make a bunch of files from the 4.4 system, including the OTP and some other files that I backed up on my external hard drive and on my Google drive.

I have no patience for someone that isn't going to listen when I've already spelled it out for them. Asking for something I already explained in the beginning, just tells me that you couldn't be bothered to read/listen.

I'm already ticked off as it is that this 3DS system is in such a bad way, and that I'm not even able to repair this one, much less curently put anything away toward getting another. You really think I'm going to have time for someone trying to act like an MLG dude brah brat when I'm trying to salvage my last remaining system here?

--------------------- MERGED ---------------------------


Thankfully it did for both systems in question. But most of what I try to find myself toward making those save files accessible simply imply that I'm still able to turn on and use the original system in question. At this point, I can't do that.

--------------------- MERGED ---------------------------

Meanwhile, wake up this morning, start the process again. this time it's able to system update no problem, and now HBLauncher works as intended.

*headdesk* why wasn't it working last night? AUGH!

1) The saves are lost as the NAND that can decrypt the sd card contents is tied to the other motherboard that you cannot even boot, unfortunately it is the only device that can decrypt it. Do you have a backup of that NAND? If so you can hardmod and try to get it back to working order. Even better if you had a backup CTRNAND as that is injectable into the new mother board via decrypt9.

2) Looks fixed as of your latest comments.

About NNID call Nintendo and tell them you broke the system by dropping it in the water or something. Maybe they can do something about ambassador status as well, but for sure they have been known to unlink NNIDs.

Buy your fiancé a nice anniversary band to compensate for her lost content.

 

[OrGoN3]

Me? Get rude? You're the one that kept asking the same question that I already answered if you'd bothered to pay attention the first time. The fact that I'm having to post it again when I'm already stressed out trying to figure out what the crap is going wrong is why I'm angry at you. It's already bad enough that I have a situation where the top screen is all purple and the bottom one is grainier than a VHS recording of a Sega Saturn Let's play. As it is, I still don't get what the hell happened with my original, much less why it's refusing to work when the other board will in the same guts...

Yes, if I hold select on the 8.1 system, I get the Luma3DS config. <--First time you are answering this question after me asking it three times If I put the 4.4 board back in, it doesn't matter what I hold <---Who cares? You were asking how to get your 8.1 system back in order. It just powers on then immediately off. And this is with the same screens and guts and everything else. FBI loads fine. In the guide, it gets to the part to run system update. It says if it keeps erroring out, just restore the NAND backup that I made initially, which is what I did.

The older process did have me make a bunch of files from the 4.4 system, including the OTP and some other files that I backed up on my external hard drive and on my Google drive. <---Nobody asked you about generalizations. We asked if you have your NAND backups and if you have your XORpads. Try answering those questions instead of just saying you backed up a bunch of files. How are we to know what files you backed up?? We aren't you.

I have no patience for someone that isn't going to listen when I've already spelled it out for them. Asking for something I already explained in the beginning, just tells me that you couldn't be bothered to read/listen. Actually you didn't. You have no patience for someone trying to help. I read everything you wrote. You also saw 2 other members, whom I have never interacted with before, defending my actions and calling yours out. Perhaps you need to recollect.

I'm already ticked off as it is that this 3DS system is in such a bad way, and that I'm not even able to repair this one, much less curently put anything away toward getting another. You really think I'm going to have time for someone trying to act like an MLG dude brah brat when I'm trying to salvage my last remaining system here? <<<WTF is an MLG dude brah? I'm not going to report you but honestly, stop acting like a god damn asshole to someone who is helping you.
--------------------- MERGED ---------------------------


Thankfully it did for both systems in question. But most of what I try to find myself toward making those save files accessible simply imply that I'm still able to turn on and use the original system in question. At this point, I can't do that. <---That's why we asked if you dumped your XORPads from your original console

--------------------- MERGED ---------------------------

Meanwhile, wake up this morning, start the process again. this time it's able to system update no problem, and now HBLauncher works as intended.

*headdesk* why wasn't it working last night? AUGH! <---PEBKAC

You created a thread. You posted in the noob thread. Right off the bat, breaking rules, as they were the same thing. You bitched and lied about my help. Perhaps it was to make yourself feel better? You also ignored my help and everybody else's. In the end, you blogged a bit and refused help from others. Perhaps next time you should try posting in one place and then following the advice.

Edit: When the original motherboard is in the guts, and you give it power, have you attempted to trace the power and see where it is dying/dissipating? I know this involves a very long and tedious process, but perhaps something simple went wrong with the original motherboard that you would be able to narrow down by power tracing. Just a thought and would only require a multimeter. You clearly know your shit so I'm not even going to ask if lightning or surge was the culprit. Random seems like a popped cap situation.

 

[codezer0]

You created a thread. You posted in the noob thread. Right off the bat, breaking rules, as they were the same thing. You bitched and lied about my help. Perhaps it was to make yourself feel better? You also ignored my help and everybody else's. In the end, you blogged a bit and refused help from others. Perhaps next time you should try posting in one place and then following the advice.

Edit: When the original motherboard is in the guts, and you give it power, have you attempted to trace the power and see where it is dying/dissipating? I know this involves a very long and tedious process, but perhaps something simple went wrong with the original motherboard that you would be able to narrow down by power tracing. Just a thought and would only require a multimeter. You clearly know your shit so I'm not even going to ask if lightning or surge was the culprit. Random seems like a popped cap situation.

It's more than a little challenging to try and hold the 3DS XL together to give it power, while at the same time using a multimeter. Unfortunately, even the "Helping hands" unit I have won't exactly have the ability to hold the board, the screen(s), and the battery in place long enough to try and trace. And even more annoying, that Nintendo makes their handhelds refuse to power on unless the battery is connected, even when it is receiving power.

The original motherboard basically powers on, then flickers off immediately, like if it couldn't read the screens. But in the same shell and same guts, the refurb does turn on. The top screen is all magenta-tinted and the bottom screen is grainy, but it is turning on.

Even more distressing, that GBAtemp as it is, doesn't really want to accept any images that would be straight from my digital camera, or my phone's camera for upload to show in detail and maybe see where I could attempt to try the multimeter to measure. Unlike the PSP, the 3DS XL's motherboard is very limited on the amount of capacitors (at least, that I could identify as such).

 

[OrGoN3]

It's more than a little challenging to try and hold the 3DS XL together to give it power, while at the same time using a multimeter. Unfortunately, even the "Helping hands" unit I have won't exactly have the ability to hold the board, the screen(s), and the battery in place long enough to try and trace. And even more annoying, that Nintendo makes their handhelds refuse to power on unless the battery is connected, even when it is receiving power.

The original motherboard basically powers on, then flickers off immediately, like if it couldn't read the screens. But in the same shell and same guts, the refurb does turn on. The top screen is all magenta-tinted and the bottom screen is grainy, but it is turning on.

Even more distressing, that GBAtemp as it is, doesn't really want to accept any images that would be straight from my digital camera, or my phone's camera for upload to show in detail and maybe see where I could attempt to try the multimeter to measure. Unlike the PSP, the 3DS XL's motherboard is very limited on the amount of capacitors (at least, that I could identify as such).

Images is the one true downfall to GBATemp that really hinders help. I tend to use imgur and then just share the album.

When you say the original powers on then flickers off, you are referring to the power LED and not the screens, correct? I am assuming the screens do not go through initialization with the old board? Sorry, but I just wanted to clarify.

The new board having screen issues can obviously be the board, or the ribbon cables. While I cannot come up with why they would get damaged in a console, they are quite fragile, as you are probably already well aware. I would recommend checking both and possibly swapping out the ribbon cables if you think they are damaged. Yes, this is starting to sound like more and more work, unfortunately.

I have some thoughts regarding your saves, or at least your NNID (depends if your saves were on your system when you made the NAND image backup, or if you created the saves afterwards). Using the refurb board, create an emuNAND using the NAND image from the original system. Now, since it is an emuNAND from a different system, it will not boot. However, you can still load up a payload, such as hourglass9, or decrypt9wip, and attempt to extract the CTR partition of the emunand. This may not work at all because your system lacks the encryption to decrypt the partition. Perhaps it is possible using custom xorpad if you backed that up as well. That I am unsure of. I have not read about people trying this prior, so I figured I would just throw it out there. I'm sure somebody will chime in saying this is not possible/will not yield the results, but until then...

Edit: Thank you being cordial. I know that you are very frustrated right now, and that you are seeking answers, not questions. I apologize that I do not have the exact solution for you, but hope that we can put our heads together and come up with the best possible solution for you.

 

[el_gonz87]

Images is the one true downfall to GBATemp that really hinders help. I tend to use imgur and then just share the album.

When you say the original powers on then flickers off, you are referring to the power LED and not the screens, correct? I am assuming the screens do not go through initialization with the old board? Sorry, but I just wanted to clarify.

The new board having screen issues can obviously be the board, or the ribbon cables. While I cannot come up with why they would get damaged in a console, they are quite fragile, as you are probably already well aware. I would recommend checking both and possibly swapping out the ribbon cables if you think they are damaged. Yes, this is starting to sound like more and more work, unfortunately.

I have some thoughts regarding your saves, or at least your NNID (depends if your saves were on your system when you made the NAND image backup, or if you created the saves afterwards). Using the refurb board, create an emuNAND using the NAND image from the original system. Now, since it is an emuNAND from a different system, it will not boot. However, you can still load up a payload, such as hourglass9, or decrypt9wip, and attempt to extract the CTR partition of the emunand. This may not work at all because your system lacks the encryption to decrypt the partition. Perhaps it is possible using custom xorpad if you backed that up as well. That I am unsure of. I have not read about people trying this prior, so I figured I would just throw it out there. I'm sure somebody will chime in saying this is not possible/will not yield the results, but until then...

Edit: Thank you being cordial. I know that you are very frustrated right now, and that you are seeking answers, not questions. I apologize that I do not have the exact solution for you, but hope that we can put our heads together and come up with the best possible solution for you.

No xorpad no dice. The only thing that can decrypt the NAND is the dead motherboard. That will need to be fixed by someone who has experience, maybe a tech shop. If that can't get fixed, then no other hardware can decrypt it without the xorpad.

In future I recommend having a CTRNAND backup as well as NAND backups. Those are portable and can be flashed from console to console. This can save a lot of headache if things go wrong.

 

[codezer0]

No xorpad no dice. The only thing that can decrypt the NAND is the dead motherboard. That will need to be fixed by someone who has experience, maybe a tech shop. If that can't get fixed, then no other hardware can decrypt it without the xorpad.

In future I recommend having a CTRNAND backup as well as NAND backups. Those are portable and can be flashed from console to console. This can save a lot of headache if things go wrong.

Not like I was expecting anything to go wrong as suddenly as it did.

wait, one of the files I did back up from the original is xorpad, and an emergency moveable.sed file. wouldn't that be what I'd need?

 

[el_gonz87]

Not like I was expecting anything to go wrong as suddenly as it did.

wait, one of the files I did back up from the original is xorpad, and an emergency moveable.sed file. wouldn't that be what I'd need?

Exactly what you need, you can use the xorpad to recover the saves.

This post has useful information: https://gbatemp.net/threads/tutorial-manual-system-transfer-for-saves-content.388033/

Use hourglass9 to flash NAND onto new system to avoid losing A9LH. Also you will need xorpads from new motherboard and a NAND dump prior to doing this.