Hacking Possible to remove AL9H?

  • Thread starter Thread starter astrangeone
  • Start date Start date
  • Views Views 4,272
  • Replies Replies 17

astrangeone

Well-Known Member
Member
Joined
Dec 1, 2009
Messages
2,228
Solutions
2
Reaction score
695
Trophies
0
Age
42
Location
Canada
Website
www.shophandmade.com
XP
1,366
Country
Canada
So, I'm running an o3DS XL with AL9H and Luma/ARN. I lost my original sysnand backups (pre-AL9H). Would it be possible to remove AL9H and then get a "fresh" install of the original firmware?

I am running updated sysnand on 10.7.32 U.
 
A9LH is more or less permanent. I don't recommend this at all, but on O3DS (DO NOT DO THIS ON N3DS, YOU WILL BRICK) you could update through safe/recovery mode. That should remove it, but I'm not really sure if anyone's been brave enough to try it.
 
  • Like
Reactions: Deleted User
You could also format a new EmuNand using your SysNand, unblock FIRM patches, boot into emunand, update it to a clean 9.2, format it twice, back up EmuNand.bin, then flash the freshly-dumped EmuNand.bin to SysNand.

Thanks. I might try that on a separate 3DS running AL9H too. Good grief.
 
I wonder if it is possible in the future someone finds a way to reverse the the a9lhinstaller process to uninstall a9lh

Might be useful, but I wish I had kept the original firmware now. If anything corrupts, I can't fix it with stock firmware.

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

Why do you want to remove a9lh?

Making a backup of a clean stock firmware, just in case something happens to the "A9LH" installation. There was a case of something going wrong with firm0 (was a N3DS), and the person was in my camp - no stock 9.2 backup. (He could access the aurei payloads fine, but the thing refused to boot.)

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

You could also format a new EmuNand using your SysNand, unblock FIRM patches, boot into emunand, update it to a clean 9.2, format it twice, back up EmuNand.bin, then flash the freshly-dumped EmuNand.bin to SysNand.

Thanks. I'd be doing this later tonight. (Urgh. Headaches.)
 
  • Like
Reactions: Deleted User
Might be useful, but I wish I had kept the original firmware now. If anything corrupts, I can't fix it with stock firmware.


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



Making a backup of a clean stock firmware, just in case something happens to the "A9LH" installation. There was a case of something going wrong with firm0 (was a N3DS), and the person was in my camp - no stock 9.2 backup. (He could access the aurei payloads fine, but the thing refused to boot.)

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



Thanks. I'd be doing this later tonight. (Urgh. Headaches.)
I see.. I was just posting there awhile ago lol
 
  • Like
Reactions: astrangeone
I'd imagine it should be possible, considering the majority of the A9LH tools we use are open-source!

And that's why I like the modding/hacking community. I want this to happen - an a9lh uninstaller so that people can send their stuff back to Nintendo when/if it breaks. If I were a little more talented with programming, I would give that a try.
 
And that's why I like the modding/hacking community. I want this to happen - an a9lh uninstaller so that people can send their stuff back to Nintendo when/if it breaks. If I were a little more talented with programming, I would give that a try.
I could be wrong too, though: There could alternatively be some valuable data accessible only to Nintendo that was lost by the user that no math will be able to solve without the proper variables (like a NAND password that is not easily attainable like the otp.bin, for example.)

I guess it's a bit pointless for me to speculate about it without actually getting a good look at the source, which, at this point in time, I don't think I have the proper skill level to do that. An uninstaller would be convenient to have, though! But I think the safest solution for now is just to have a proper SysNand backup in case one ever wants to revert back to pre-A9LH, which is also covered in the Plailect Wiki Guide.
 
I could be wrong too, though: There could alternatively be some valuable data accessible only to Nintendo that was lost by the user that no math will be able to solve without the proper variables (like a NAND password that is not easily attainable like the otp.bin, for example.)

I guess it's a bit pointless for me to speculate about it without actually getting a good look at the source, which, at this point in time, I don't think I have the proper skill level to do that. An uninstaller would be convenient to have, though! But I think the safest solution for now is just to have a proper SysNand backup in case one ever wants to revert back to pre-A9LH, which is also covered in the Plailect Wiki Guide.

Right now I'm moving ahead with your suggestion to basically have a new 9.2 emunand and then do the proper things to it (like tiny format x2 the thing), and not flash it back onto the system - this is my "Hail Mary" in case something else happens.
 
  • Like
Reactions: CrispyYoshi
Right now I'm moving ahead with your suggestion to basically have a new 9.2 emunand and then do the proper things to it (like tiny format x2 the thing), and not flash it back onto the system - this is my "Hail Mary" in case something else happens.
Good luck! I hope it works out!
 
Tangentially related: If you needed to return your console to Nintendo (and you're not in a progressive country that recognizes in law some hardware faults can't just be caused by software), write absolute junk to the nand so that it's really bricked and claim it just didn't turn on the morning!
 
Couldn't we just inject original Firm 1 and 2 using Decrypt9 booted into using Arm9LoaderHax? It's only Luma3DS that actually blocks the firm writing. So if we use Decrypt9 as the default payload, we could just do that :))))
 

Site & Scene News

Popular threads in this forum