Actually it does. It is a software implementation of the hardware otp method mentioned in the intro of the guide.OTPless never gets the OTP. Hence the name.
Actually it does. It is a software implementation of the hardware otp method mentioned in the intro of the guide.OTPless never gets the OTP. Hence the name.
...which is why I saidA lot of the bricks happened during the actual a9lh installation part. It takes less than 1 sec, and gives you an error if there are any missing or wrong files, thus why it is called *SAFE*a9lhinstaller. There is no possible way someone could screw this up without throwing their 3DS into a wall.
Not false in that exact case here
Indeed here it's more complicated to find a way to fail so I wouldn't say "user error" without thinking
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.Not false in that exact case here, but on the other hand, some people do stuff you never thought about and they never thought about it dangerously, such as closing the lid on a New 3DS on 2.1 even though the 2.1 wasn't supposed to support the New 3DS in the first place, or closing it during a downgrade to save battery while the console is working, this kind of stuff. Indeed here it's more complicated to find a way to fail so I wouldn't say "user error" without thinking but we never know what people can come up with these days.
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.Actually it does. It is a software implementation of the hardware otp method mentioned in the intro of the guide.
You were kinda arguing both sides........which is why I said
Okay."the first one"
definitely not the first one.
--------------------- MERGED ---------------------------
one of the other things is reading code, apparently
it doesn't. you can only get the OTP hash, not the OTP itself.Actually it does. It is a software implementation of the hardware otp method mentioned in the intro of the guide.
lol wtf are you sayingThere 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.
Actually it does. It is a software implementation of the hardware otp method mentioned in the intro of the guide.
Weren't the bricks caused by unchecked cache storage that just needed to be flushed?
That was what I was getting at. OTP hash. My first post was edited a few hours back correcting myself.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.
otpless bricks are not related to cache.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.
otpless bricks are not related to cache.
probably fcram/arm9 memory getting corrupted during the reboot.Oh? I guess I misunderstood from this thread. What is the cause then?
probably fcram/arm9 memory getting corrupted during the reboot.
https://gbatemp.net/threads/n3ds-xl-bricked-when-updating.450143/lol wtf are you saying
Are you being paranoid? Or do you have actual proof someone got bricked during a ctrtransfer.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.
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.Are you being paranoid? Or do you have actual proof someone got bricked during a ctrtransfer.
People brick because they go sleep mode in N3DS while on 2.1.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.
...and I supposed you have all this info graphed out? Lul, "analysis."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.