Homebrew SafeA9LHInstaller

  • Thread starter Thread starter Aurora Wright
  • Start date Start date
  • Views Views 212,191
  • Replies Replies 813
  • Likes Likes 117
CTRBootManager9 is the one with the GUI, right?
If so, you're using the A9LH version with screen-init.
Yes it is. So in order to even use the UI of CTRBM9 screen-init is a must? well that's one huge pro for me in that case because I have a very good reason to use CTRBM9 over any other - I don't want to have to bind all my arm9 payloads.
 
So i've been out of the loop for quite a while. to install this do i still need to downgrade to 2.1 or so?
 
which version of a9lh is better, dark_samus version or delebile? I think dark_samus has new stuff in it that delebile doesnt.
 
which version of a9lh is better, dark_samus version or delebile? I think dark_samus has new stuff in it that delebile doesnt.
Delebile's is safer, since Dark Samus' version is mostly used for testing. Once everything seems to be working, it'll get pushed to Delebile's version.
 
  • Like
Reactions: survive9
Delebile's is safer, since Dark Samus' version is mostly used for testing. Once everything seems to be working, it'll get pushed to Delebile's version.
Thanks for the quick reply. I was debating on updating my A9LH via payload_stage2.bin from his version to get those features.
 
In the past couple of days I've been developing a brand-new A9LH installer.
It loads all the needed files from the SD card (no more need to build console-specific installers), and it's really fast. Other than that, it's way safer than the original one, as it does the following checks:
- Checks that it's able to encrypt FIRM partitions properly
- If you have a New 3DS and you're doing a first install of A9LH, or you're reinstalling from A9LH itself, it validates your OTP. Sadly I have no way of validating the OTP on an Old3DS first install.
- Hashes the secret_sector, FIRM0 and FIRM1 to verify their integrity
- Checks that stage1 and stage2 don't exceed a maximum size.

How to use:
- Copy the 3ds folder and the .dat if making a first install, and run the program from a vulnerable firmware; or load the .bin using A9LH itself. Press SELECT for a full install, and START for a stage2 update.
- If you only want to update stage2, copy a payload_stage2.bin (which is stage0x5C000.bin) to the a9lh folder on the root of the SD.
- If doing a full install, you also need to copy these files to the a9lh folder: payload_stage1.bin, firm0.bin (which is new3ds90.firm), firm1.bin (which is new3ds10.firm), secret_sector.bin and your personal otp.bin.

Thanks go to everyone in #cakey on IRC, to delebile for his A9LH implementation, and to StandardBus who hardmodded my consoles and made this possible. Code for writing to the screens is from CakesFW.

Download: https://github.com/AuroraWright/SafeA9LHInstaller/releases
Yay. More safe A9LH ^^
Thanks :3
 
Screen init seems to be broken for 9.2 emunand, it displays nothing after loading from hblauncher, however it still works when you press start or select and powers off when I press a button again.
 
Who is running what now? I'm still running dark_samus3 build (with sd fix unmount fix for stage 1)

Wonder if I can just update stage 2 of this installed build from fix94 to take advantage of brightness to 0 and keep stage 1 unmount fix from dark_samus3?
 
Last edited by democracy,

Site & Scene News

Popular threads in this forum