Can I assume that OP doesn't have a NAND Backup?
Since if this is true, he installing A9LH with others console OTP without access to decrypt9.
= No 2.1 CTRtransfer & No Backup.
How did he do the 2.1 CTRtransfer? According to the guide it says to use Auto CTRNAND Transfer in decrypt9.
This process backups the NAND (if given the a ok) validates the NAND backup, install the CTR image.
If he actually installed a9lh not in 2.1 with some others otp then it's bricked as far as I know.
This process backups the NAND (if given the a ok) validates the NAND backup, install the CTR image.
If he actually installed a9lh not in 2.1 with some others otp then it's bricked as far as I know.
Last edited by Natsuru,
That's the issue, too many people are skipping the process because of lack of space (instead of making space) or because they think they don't need it. Then they get fucked up and ruin their system.
Do you have the "arm9loaderhax.bin" from Luma in the root of your SD card?
Last edited by The Catboy,
Since he said he was using other console OTP & from the text he post, I assume he wasn't using bible.
He accidentally put SafeA9LHinstaller file instead of Decrypt9WIP, accidentally leave his other O3DS OTP.bin in files9 folder.
And accidentally launcher SafeA9LHinstaller from Safehax.
So, he process without accessing Decrypt9, so he doesn't use Auto CTRNAND Transfer.
Last edited by nechigawara,
So, he process without accessing Decrypt9, so he doesn't use Auto CTRNAND Transfer.[/QUOTE]
Ya kinda got that. I have never heard of someone doing this before.
Ya kinda got that. I have never heard of someone doing this before.
This is the first time I saw this case too. But, since both Decrypt9 and SafeA9LHinstaller need an arm9 exploit to run,
I think it possible to also run SafeA9LHinstaller from safehax.
And if the user using newer version of SafeA9LHinstaller (OTPless + N3DS) or having OTP of that console already,
that user can install A9LH without going back to 2.1.
I'm the type of person that gets over-paranoid about becoming that kind of person, so I make 3 different backups, compare them, and then make backups. I've been like this ever since using my E3 Flasher for my PS3, because that was the only way to make sure the E3 Flasher correctly read the NAND chip.
well as already mentioned there is the plaintext attack possibility, but you would still need a hard mod and ability to figure something out by yourself
Sighax requires existing hax already installed to work. It's not a hax you can load on an unmodded 3DS, due to it needed NAND write access, something only CFW or other exploits can give.
Last edited by Dimensional,
Do you really think an average user (or lesser than that) that didn't even follow the guide correcly, installed using with someone else's OTP knows what you're even talking about? Or that he'd be able to "figure it out". You're known for hardmodding in this community and if even you don't know how to do it - how would he?
Damn sucks m8 you need to follow the 3ds.gude to the letter just did it my self almost no problem.
I have unbricked systems using the plaintext method,, and I have always tried to discourage end users from trying to hardmodding themselves (too many complete screw up for my liking), it would be better for him to send it off to someone else and maybe they would be able to unbrick for him, but yeah your right someone who can't follow simple instructions would probably screw up even worse than they already have
I did when I studied the process for 1 month and a half and everything worked out (asperger for the win)
I just went almost blind but followed the guide to the letter,Only problem i had was i named a file the wrong name LOL.
Similar threads
