Run luma with HBL, there's a .3dsx i think, and yeah, I had the same issue
Also a tip- immediately after you click the luma program in HBL, press select and edit the luma settings to indicate which nand you're on (select boot into sysnand, and enable the option to show a string in the system settings, this will let you be sure you're in luma), forgot the exact option, but it should be pretty straight forward. and make SURE you have EVERYTHING you need before installing a9lh, specifically arm9loaderhax.bin on the root
You also need to set an option in Luma to boot into Sysnand, and not emunand
You've been following this: https://github.com/Plailect/Guide/wiki/Part-3-(A9LH) correct?
Yikes. Any specific details about what happened?And I have the first bricked console being shipped to me using this method.... It was bound to happen and it has.
N3DS running 9.2, bricked using the unsafeal9h installer... Good thing they had a backup.
And I have the first bricked console being shipped to me using this method.... It was bound to happen and it has.
N3DS running 9.2, bricked using the unsafeal9h installer... Good thing they had a backup.
Run luma with HBL, there's a .3dsx i think, and yeah, I had the same issue
Also a tip- immediately after you click the luma program in HBL, press select and edit the luma settings to indicate which nand you're on (select boot into sysnand, and enable the option to show a string in the system settings, this will let you be sure you're in luma), forgot the exact option, but it should be pretty straight forward. and make SURE you have EVERYTHING you need before installing a9lh, specifically arm9loaderhax.bin on the root
You also need to set an option in Luma to boot into Sysnand, and not emunand
You've been following this: https://github.com/Plailect/Guide/wiki/Part-3-(A9LH) correct?
Would you advise the 2.1 CTR transfer method over the new SafeArm9Installer then?It won't be any safer.
Wait what? In the Luma options screen it hangs? Try redownloading Luma if that's the case, all you really have to enable is the load to sysnand setting, and once in the Sysnand with Luma loaded, you open HBL thru whatever method you please, and run the A9LH installerOk got same problem. I had followed ur instruction to run luma3ds through hbl. At luma3ds option screen, still no respond after i pressed button to choose an option. Up/down button also not responding. Seems like the screen just hang. Did i miss anything that should have been done before running luma?
Wait what? In the Luma options screen it hangs? Try redownloading Luma if that's the case, all you really have to enable is the load to sysnand setting, and once in the Sysnand with Luma loaded, you open HBL thru whatever method you please, and run the A9LH installer
I don't think that's all you require for it to work.In a sense, yes, but only until you download another arm9loaderhax.bin. a9lh boots milliseconds into your system and runs the aforementioned bin file. If that bin file is not present, then you are out of luck for booting. However, you can get said file in many many places online, and it is not console specific. Found in many guides, and even in basic setting up of Luma. Just relocate a copy of that bin file, place on a fresh SD card, and you should be able to boot, with very slight dependencies, depending on where you got the bin file from, for example, the luma directory, if you got it from the Luma setup.
Yes. Unless you have hardmod.
It won't be any safer.
Did their brick have to do with "SD card is no longer initialized after the reboot during OTPless installs (might fix corner case bricks where the SD is corrupted)"? How did it brick?
From the details they gave me, once they ran safearm9 it bricked.
otpless works because you can copy key0 to key1, put 10.0 New 3DS FIRM in firm0, put a payload into arm9 memory, reboot, and get the otp hash from there and install proper a9lh.