Do you have arm9loaderhax.bin on your SD card?Now it gets stuck with the LED on, and the screens are black. HELP!!!!!!!!!!!!
If the problem was missing arm9loaderhax.bin then the console would flash on then off, not stay on.Do you have arm9loaderhax.bin on your SD card?
Load safehax, and then safeA9LHinstallerBut you're supposed to use SafeArm9Installer to install a9lh.... what exactly did you do, step by step? What step did you get up to in the guide, and at which point did you deviate from the guide?
Exactly steps in the guide please, not a descriptionLoad safehax, and then safeA9LHinstaller
1. Load up the files to the root of the SD Card. Make sure the SD Card is fat32. To check, find the SD Card and hit properties. If it is NOT Fat32, convert it now! It won't work unless you do it!!!Exactly steps in the guide please, not a description
That doesn't sound familiar. You should be using http://3ds.guide.1. Load up the files to the root of the SD Card. Make sure the SD Card is fat32. To check, find the SD Card and hit properties. If it is NOT Fat32, convert it now! It won't work unless you do it!!!
2. Then load up Soundhax. Just hit the music player and hit down twice and the A button twice!
3. Then find "Safehax." It will load up Decrypt9WIP if it is done correctly. If there is a black screen, place a game cartridge into the 3DS and hopefully, the bug will disappear and it will load.
Instead, it showed safeA9LHinstaller, so I thought the person did something wrong.
same thingEdit: what happens if you boot up without the SD card in?
whoopsDid you have another console's OTP in the a9lh folder of your SD card? if so, trying to install a9lh using another console's OTP will brick it.
If not, I don't know what it could be. SafeArm9Installer should just not work if you're not on 2.1 and don't have any OTP in the SD card.
Your 3ds has been deathed.whoops
i used my o3ds's OTP.bin
HOW DO I FIX IT?!?!?!?
Do you have a NAND backup? If yes, you can fix it with a hardmod.whoops
i used my o3ds's OTP.bin
HOW DO I FIX IT?!?!?!?
wellDo you have a NAND backup? If yes, you can fix it with a hardmod.
If not, you're probably screwed. There's still a chance it can be fixed with the known-plaintext attack and a hardmod to rewrite the FIRM partition back to normal. While theoretically that's doable I'm not aware of anyone that's actually done it for a case such as this.
well
what now