Homebrew SafeA9LHInstaller

  • Thread starter Thread starter Aurora Wright
  • Start date Start date
  • Views Views 211,910
  • Replies Replies 813
  • Likes Likes 117
Hey @Aurora Wright can you add support for this?
So I was thinking, can we just use a SaltFW (SaltLite) payload to load arm9loaderhax without SD? Its size is super small, And it doesn't require any folder/firmware/etc for sigcheckpatching.
Is this possible?
This is entirely possible, but it's somewhat of a pain.

First of all you need a way to read files off the NAND via arm9 - this definitely possible, but difficult when you consider the space limit of k9lh payloads.

You'd then need a payload that's small enough to fit in the NAND (smaller the better, mainly for DSiWare and stuff). In addition, it would need patches for FIRM write protection at the very least, and would need to be able to load firmware.bin from NAND. SaltFW works perfectly for this, as it is relatively lightweight and contains necessary patches. Another option would be Mizuki.

Like I said, it's possible but a pain. Most developers aren't going to be working on it given that it's relatively low priority as few people boot without an SD card. I would be looking into it if I had a hardmod, but since I don't I'm too afraid to brick :P

EDIT:
I'm already working on a CFW that's on your NAND.

yes im the person who made saltfw
ShadowHand is a god
 
Last edited by Salamencizer,
With the latest version, Exploiting arm9 don't appear, is normla? (New 3DS)
 
I have a question: How do I know which version of a9lh I have installed (no init, screen init, etc.). I followed this tutorial, but I don't think it says which version it installs. Also, what difference will it make in updating a9lh? Is there a changelog for each update? Where do I find the update files?
 
Thx @Aurora Wright for the SafeA9LHInstaller, but there is something that I just don't know. Sorry if I am a noob but, how do I get the New3ds90 and 10 firm?
EDIT: I figured out that it was firm0.bin(which WAS new3ds90.firm) and firm1(which WAS new3ds90.firm).
EDIT2: Nevermind, I managed to get firm0 and firm1 somewhere.
 
Last edited by Ultracoolguy,
I installed A9LH months ago, following the plaiect guide. I followed the guide exactly, using all the files the guide linked to. By looking at the files I still have on my computer, I can see that I completed it on March 28th.

Has anything new come up since then that could be interesting? my CFW is Luma and it's fully up to date (5.4 at this moment), but is A9LH itself worth updating? (if there's something new to begin with at all)
 
No they are not optional you need them to install arm9loaderhax....he's not asking about firmware.bin
Well in that case, can someone tell me how to dump it?

BTW The good thing is that I'm not in the middle of the process.Just preparing for.
 
hello guys, I've been becoming a silent member and I would like to ask you guys a few things, I'm currently doing a permanent hack on my old 3ds, after I installed arm9loader, I cant press start to enter decrypt9, but I can access Luma3ds menu and i already put all the files. and also I've check my start button and it works perfectly, any idea?
 
Make sure to download the absolute Latest version of decrypt9

Rename to down_decrypt9.bin and place in payload folder inside the luma folder

I only say to use down since it's easier you can change it after to see if it works with start just rename to start_decrypt9.bin. Also make sure your holding the button BEFORE booting
 
The name is pretty self explanatory.

Spoiler: It installs A9LH.
Well, I was asking about A9LH itself, but I get it now.
It has better boot rate than menuhax, and plus some other stuffs.
I guess that's all there is.

I was just looking for something to mess with my O3DS because I have everything set up and I have nothing to do. :/
 
@Aurora Wright can you make a build for 2.1? The current procedure is to Downgrade to 2.1 for OTP, Restore 9.2 sysNAND, Install a9lh, then flash emunand_original.bin to sysnand while using the "keep a9lh" option. If this could work on 2.1, a9lh could directly be installed after getting otp, and while using the "keep a9lh" option, emunand_original.bin could be flashed to sysnand, which would save much time.
 
@Aurora Wright can you make a build for 2.1? The current procedure is to Downgrade to 2.1 for OTP, Restore 9.2 sysNAND, Install a9lh, then flash emunand_original.bin to sysnand while using the "keep a9lh" option. If this could work on 2.1, a9lh could directly be installed after getting otp, and while using the "keep a9lh" option, emunand_original.bin could be flashed to sysnand, which would save much time.

(As far as I know, maybe I am wrong) A9LH is only installable in 9.0 - 9.2. In 2.1 there was no "Arm9loader", which was added in 9.0, and in newer versions(>=9.3) the Arm9 permissions were patched, but if installed A9LH in 9.0 - 9.2 and keeped(no overwriting Firm0 and Firm1), it worked on newer versions.

BTW Sorry for my bad English.
EDIT:The Arm9loader was actually added in 9.6+. Thanks to Aurora Wright(https://github.com/AuroraWright/arm9loaderhax) in Readme and @GerbilSoft to pointing me out.
 
Last edited by Ultracoolguy,

Site & Scene News

Popular threads in this forum