D
Deleted User
Guest
There were unkown random bricks that got reported on version 3's otpless that I beleave was sead to happen during a update,so on version 4 the file needed for otpless got patched out to prevent it from happening.What happens is the old 3ds uninstalls a9lh after the update while the new3ds bricks completely,the old3ds issue however could of been a gateway problem.
Last edited by ,
Oh, trust me, I understand in general that user error is the leading cause of something going wrong. But there really isn't much of a chance of user error in this case. The install is quick enough that you can't interrupt it by doing something stupid, there aren't really any competing sets of files that can cause issue (and the installer makes sure everything is in the right place), etc.
It's not like the 9.2 downgrade, especially before hash checks were put in place, where people could get corrupt files or the wrong region files, or didn't have the system plugged in/enough battery, or put the system into sleep mode. It's not like the 2.1 downgrade back when it was a complicated dance of formatting an EmuNAND, downgrading to 2.1 with the correct files, unbricking it on N3DS, blindly flashing that to sysNAND because there was no possible way to check to see if the downgrade was fully successful - where there were any number of ways that the user could fuck everything up by not paying attention.
OTPless is a simple process to the user that is hard to fuck up. Grab the files, launch the software, press Select. It just annoys me that some people are so adamant that it has to be user error without stopping to think.
Then why doesn't it dump it to sd:/a9lh/otp.bin like the normal method? Not doubting you, I don't know the technical details of it.
Last edited by Cuphat,
Okay."the first one"
definitely not the first one.
--------------------- MERGED ---------------------------
one of the other things is reading code, apparently
I just thought he was because of the original thread where UNSafeA9LHInstaller developed.
Also. Hi! I'm a big fan of yours. I like your avatar a lot. (Also, no sarcasm here, trust me).
it doesn't. you can only get the OTP hash, not the OTP itself.
--------------------- MERGED ---------------------------
lol wtf are you saying
Nope, it gets the OTP's hash. Not the OTP.
The hash of the OTP is the only thing you need to do to generate an a9lh keysector, though.
Seems so. Kind of hilarious in hindsight that something like invalid cache is the reason these bricks happened, though perhaps it's not so funny for the victims.
Last edited by metroid maniac,
Just at random?
I guess it makes sense that RAM being preserved on reboot isn't something than you can count on.
D
Deleted User
Guest
https://gbatemp.net/threads/n3ds-xl-bricked-when-updating.450143/
https://gbatemp.net/threads/i-lost-a9lh.451246/
Read these 2 posts.Both had the same problem updating with a9lh about a month ago when the otpless version was still in the guide.One person had a new 3ds and the other was using a old 3ds.Like I sead the old 3ds poster probley got bricked with gateway.
Last edited by ,
If you're beign at the day at least on thios forum you will see an sligh rise of bricks using the CTRTRANSFER method, why? Because more people is using it, exactly the same what happened to OTPless.
D
Deleted User
Guest
Are you being paranoid? Or do you have actual proof someone got bricked during a ctrtransfer.
Not DURING CTRTRANSFER specifically but counting the overall method, check the new posts... and that why? because is the only method, its the natural behavior of any analysis.
People brick because they go sleep mode in N3DS while on 2.1.
People brick because they try to update via System Settings a N3DS while on 2.1.
People brick because they get fake/bad cards and don't check them before the whole process.
People brick because their own fault.
It's been proven more secure than the OTPLess installs.
...and I supposed you have all this info graphed out? Lul, "analysis."
Similar threads
