Looking for N3DS A9LH Installer From Trusted Source.

  • Thread starter Thread starter Raylight
  • Start date Start date
  • Views Views 2,942
  • Replies Replies 20
@Plailect OTP Guide. Follow that and I'm sure you can perform the A9LH install as easy as any other member. Even experienced users know the possibility of bricking. This usually is due to user error. Reference the guide, it is much easier than before creation of tools such as OTPHelper to aid in the process. You can do it but don't rush. Make multiple backups of all pertinent files (sysNAND and emuNAND prior to downgrade to 2.1, and your precious OTP.bin).
 
i dont have a hardmod so if it fails i cant fix it and some guy reported he got bricked after following the new guide exactly

I understand, did he mention which step he bricked at? The downgrade to 2.1 requires attention to detail to make sure the unbricked emuNAND that is flashed to sysNAND is prepared correctly. You will create sysNAND and emuNAND backups prior to this step so even if you were unfortunate to brick during your attempt you can get a hardmod at that point and restore using your sysNAND dump. That is what the other user seems to be facing. No doubt a setback but definitely not permanent. Believe in yourself and if you have a question about a step in the guide, STOP and ask for assistance from a fellow Temper. I can't count how many times I have had to lean on the community. Be respectful and you will get the help you need and you will succeed.
 
  • Like
Reactions: Wire and Soul1300
Anyone who would be willing to install a9lh for you will charge you for installing it and hardmodding if anything goes wrong. so you might as well get a hardmod. Hundshamer is a good bet on hardmodding
 
He has his sysNAND dump correct? After getting hardmod he will be back in action in not time. Which version of OTPHelper was he using. @d0k3 has been working tirelessly making revisions and having other members test. Like I said before there is no reason to rush. You could watch the OTPHelper thread and OTP guide thread for a few days to get a feeling of the going rate of success other members are having. Patience will set you free.
 
  • Like
Reactions: Raylight
@hundshamer does excellent professional work. I do not think you will need the hardmod. Once A9LH is installed it is like you have a hardmod as you can load Decrypt9 on boot an restore sysNAND if something went wrong later.
 
Im going to wait for the otp helper to stabilize if only there was a way to see if the unbricked nand is working before you take the ultimate risk everything up to that point is safe and easy to restore if something goes wrong but once you flash the unbricked emunand to your sysnand theres no turning back without a hardmod
 
Last edited by Raylight,
I can get behind that. You will get there. In the meantime continue to view the appropriate threads and enjoy the fact that have a N3DS with CTRBootManager 9.2 SysNAND and rXTools 3.0 Beta 2 with EmuNAND 10.7 and it works fine just the way it is.
 
im wondering what the chances of Nintendo patching out emunand are? you know updating on emunand but it really updates sysnand.
the entire point of emunand is that it doesn't have access to sysnand, and therefore can neither update sysnand nor destroy/brick sysnand. sysnand has access & authority over emunand, but not the other way around.

there are some advantages to a9lh (even using a9lh with a modded sysnand and no emunand), but it has nothing to do with any kind of threat that could be made against sysnand from inside of an emunand (afaik that is strictly impossible because emunand is not aware of sysnand and has no access to it, provided that the two have been unlinked from each other).
 
Last edited by teegeeack,
In the old guide, when you flashed the 2.1 firm to sysnand, you would have to delete the ext folder in the Nintendo 3ds folder, I believe it's in 2 numbered folders, you delete both exts to make it boot or take out the memory stick and boot it up and put the stick back in.

Whenever it acted bricked on 2.1, I would delete the ext folders, which would fix the problem and boot up.

I just realized that this is an old topic but still, if it acts bricked on 2.1 sysnand, you need to delete the ext folders.
 
In the old guide, when you flashed the 2.1 firm to sysnand, you would have to delete the ext folder in the Nintendo 3ds folder, I believe it's in 2 numbered folders, you delete both exts to make it boot or take out the memory stick and boot it up and put the stick back in.

Whenever it acted bricked on 2.1, I would delete the ext folders, which would fix the problem and boot up.

I just realized that this is an old topic but still, if it acts bricked on 2.1 sysnand, you need to delete the ext folders.

pulling out the SD card, booting, then putting it back in while on the URL entry screen works fine for this.
 
I just installed A9LH on two N3DSes. The installation went smoothly, but the tools seem a LOT MORE BUGGY. So many cold reboots back into sysnand and into the HBL just because the process froze or never started up normally.
 

Site & Scene News

Popular threads in this forum