Homebrew SafeA9LHInstaller

  • Thread starter Thread starter Aurora Wright
  • Start date Start date
  • Views Views 212,258
  • Replies Replies 813
  • Likes Likes 117
People are mixing files from different forks, that's why.
People are bricking due to user error, not because of the installer.

There will be unforseen bricks that arise, but most will be user fault as @Supster131 stated. I just feel if you are installing A9LH for the first time this installer seems like the way to go. If your A9LH is already working why change it? Yes I have changed mine before and maybe that makes me somewhat of a hypocrite but since I changed to @FIX94 to use arm9select I will not change until there is a bonafide must have feature because eventually something will go wrong. If used in conjunction with AuReiNand all current forks of A9LH have no REAL advantages over one another. Screen init (@delebile/@dark_samus3 /No screen init (@Aurora Wright)/Screen init but backlight set to 0 (@FIX94). Read the documentation of each thoroughly and settle on 1 to remain on until an important development occurs. At that time you can make the educated decision and realize the risk of changing A9LH.
 
There will be unforseen bricks that arise, but most will be user fault as @Supster131 stated. I just feel if you are installing A9LH for the first time this installer seems like the way to go. If your A9LH is already working why change it? Yes I have changed mine before and maybe that makes me somewhat of a hypocrite but since I changed to @FIX94 to use arm9select I will not change until there is a bonafide must have feature because eventually something will go wrong. If used in conjunction with AuReiNand all current forks of A9LH have no REAL advantages over one another. Screen init (@delebile/@dark_samus3 /No screen init (@Aurora Wright)/Screen init but backlight set to 0 (@FIX94). Read the documentation of each thoroughly and settle on 1 to remain on until an important development occurs. At that time you can make the educated decision and realize the risk of changing A9LH.
Yeah, if you're going to change fork, you should know what you're doing first.
I personally changed to Aurora's fork as it has screen init disabled (which is what I want), but it mainly follows Dark Samus's fork. Such as it auto turning off with no SD card in the system. I don't think that feature has been pushed to Delebile's fork.
 
You don't need to change A9LH to make AuReiNAND's boot manager to work, it just does.
You need to make a folder in the /aurei/ folder called "payloads". You place your payloads in there.

I did create a payload folder and renamed decrypt and such but they still didn't work, so I used the installer to install stage 2, thinking that would work, it said success and next thing I know, blue light comes on and screen doesn't come on.

I'm guessing I'm an idiot since I had it already installed. I'm trying to see if I need a hard mod or not, can I activate the installer somehow to fix.this?
 
Yeah, if you're going to change fork, you should know what you're doing first.
I personally changed to Aurora's fork as it has screen init disabled (which is what I want), but it mainly follows Dark Samus's fork. Such as it auto turning off with no SD card in the system. I don't think that feature has been pushed to Delebile's fork.


Well said @Supster131. When I decided to change my A9LH it was for the release of arm9select and the main reason I chose to change was I use no splash screens with AuReiNand so the flash I would see was the screen init without a splash screen and I became annoyed by this as did @FIX94. After seeing the brick numbers rise from people changing forks and this and that (too many scenarios to list), I thanked my lucky stars and will stick with @FIX94 until a MAJOR development gives me the false sense of security to take the risk once more. We are all big boys and girls here, so we have seen posts from people who had something go wrong so there is an understanding each of us must accept if we brick. Changing A9LH is optional not required. Enjoy the holy grail don't reinvent it.
 
  • Like
Reactions: oFire
Well said @Supster131. When I decided to change my A9LH it was for the release of arm9select and the main reason I chose to change was I use no splash screens with AuReiNand so the flash I would see was the screen init without a splash screen and I became annoyed by this as did @FIX94. After seeing the brick numbers rise from people changing forks and this and that (too many scenarios to list), I thanked my lucky stars and will stick with @FIX94 until a MAJOR development gives me the false sense of security to take the risk once more. We are all big boys and girls here, so we have seen posts from people who had something go wrong so there is an understanding each of us must accept if we brick. Changing A9LH is optional not required. Enjoy the holy grail don't reinvent it.

I fully agree, I didnt realize different forks could brick you to the point of not even being able to load a9lh, and I updated mine...thankfully I did choose full install instead of just trying to update payload2, which may have saved my ass lol, but yeh, if you dont need to update it, I wouldnt try until either something insanely better is released or somehow the installer can compare forks to make sure it doesnt install one that will brick the device.
 
You don't need to change A9LH to make AuReiNAND's boot manager to work, it just does.
You need to make a folder in the /aurei/ folder called "payloads". You place your payloads in there.

Only the default.bin works :( I can't seem to get L + R + other button to work.

EDIT: Nevermind, apparently its the payload. Still, uncart worked with arm9select, why break with aureinand's chainloader?
 
Last edited by GinkREAL,
Only the default.bin works :( I can't seem to get L + R + other button to work.

EDIT: Nevermind, apparently its the payload. Still, uncart worked with arm9select, why break with aureinand's chainloader?


Payloads never worked for me, even the armloader9 versions, I did everything, so I said screw it and used the safe installed and went with stage 2 to see if that would fix why none of the payloads would work. I got a brick aswell, good thing it's cheap to get a hard mod.

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

Only the default.bin works :( I can't seem to get L + R + other button to work.

EDIT: Nevermind, apparently its the payload. Still, uncart worked with arm9select, why break with aureinand's chainloader?


Payloads never worked for me, even the armloader9 versions, I did everything, so I said screw it and used the safe installed and went with stage 2 to see if that would fix why none of the payloads would work.
Only the default.bin works :( I can't seem to get L + R + other button to work.

EDIT: Nevermind, apparently its the payload. Still, uncart worked with arm9select, why break with aureinand's chainloader?



Payloads never worked for me, even the armloader9 versions, I even put them in the damn folder called payloads, so I said screw it and used the installer, thinking that would fix it and used stage 2 and it bricked, good thing a hard mod is cheap.
 
I'm using the first dark_samus3 release that introduced screeninit via his updater. Has there been any major changes since then worth updating?
 
So just to verify (so that I don't brick my 3ds), if I wanted to switch from FIX94's fork to Aurora's fork, I would compile arm9loaderhax using Aurora's fork, then copy the payload_stage1 and payload_stage2 to the a9lh folder, as well as all the data_input files?
 
I mean is this worth a the trouble for a fresh install of a9lh? Isn't the Web compiler more safer to use?
Yes I think so it's literally drag and drop with this(although
So just to verify (so that I don't brick my 3ds), if I wanted to switch from FIX94's fork to Aurora's fork, I would compile arm9loaderhax using Aurora's fork, then copy the payload_stage1 and payload_stage2 to the a9lh folder, as well as all the data_input files?
yup stage 1, stage 2, firm1, firm0, secret_sector and otp(only needed if NOT launching thru a9lh)
 
People are mixing files from different forks, that's why.
People are bricking due to user error, not because of the installer.
Umm if we're only updating stage2 why should it matter which fork we use?
And yes i also bricked multiple times using this installer WITH aurora's fork stage2 (as others described, just boots to black screens).
And I'm not exactly a noob when it comes to messing with the (possibly) dangerous stuff on 3ds, so it wasn't user error...
 
Umm if we're only updating stage2 why should it matter which fork we use?
And yes i also bricked multiple times using this installer WITH aurora's fork stage2 (as others described, just boots to black screens).
And I'm not exactly a noob when it comes to messing with the (possibly) dangerous stuff on 3ds, so it wasn't user error...
AFAIK you have to do a full reinstall if switching to Aurora's fork, her stage2 is not compatible with delbile and friends stage1.
 

Site & Scene News

Popular threads in this forum