Proceeded with the otpless at your own risk.If you want the best installation experience I sudjest uninstalling menuhax once you are in the homebrew launcher then proceed with the guide and launch decrypt9.Keeping menuhax uninstalled during decrypt9 increases the success rate I think.
I wouldn't risk if it I were you. I installed A9LH on my N3DS, and a few others, when ctrtransfers were the standard and nothing ever went wrong. Just note that SafeA9LHInstaller might glitch out and won't display anything during installation. This is ok. Just don't close your 3DS when on 2.1, or you will get permanently bricked.
Quite a bit. It's used to downgrade to 9.2 if you're not on it already, then to 2.1, then to upgrade back to 9.2 (provided you don't have an EmuNAND dump to flash over SysNAND, in which case you use D9 to do so).Please elaborate, at what point is decrypt9 used?
I don't even believe that 1 single report of bricks was real and was made by a bunch of people who very clearly didn't want or like otpless when it first came out. And it was impossible for any dev and any person purposely trying to recreate this "bug" to have it happen.
I still hack 3ds and to this day use otpless, obviously do what you want but I never saw one video of someone running safearm9installer and bricking just reports from "new" users. It's very fishy to me
It's actually a very rare MCU brick. This is why devs haven't been able to reproduce it because it's totally random and there's like a 1/1000 chance of it happening. That's still too much of a risk regardless of how miniscule the chances are, though, and this is why it was removed from the guide.I don't even believe that 1 single report of bricks was real and was made by a bunch of people who very clearly didn't want or like otpless when it first came out. And it was impossible for any dev and any person purposely trying to recreate this "bug" to have it happen.
I still hack 3ds and to this day use otpless, obviously do what you want but I never saw one video of someone running safearm9installer and bricking just reports from "new" users. It's very fishy to me
It's actually a very rare MCU brick. This is why devs haven't been able to reproduce it because it's totally random and there's like a 1/1000 chance of it happening. That's still too much of a risk regardless of how miniscule the chances are, though, and this is why it was removed from the guide.
I completely agree that it's all user error. Look at any "did you get [X] hacked successfully" poll taken for any system that can be modded and you will see north of 1% failure rate on every single system.
People don't read carefully, don't fully understand what or why they're doing something, and then they brick and blame others.
I did the OTP-less install of Luma and a9lh on my first try, working around a partial downgrade failure because I read and re-read multiple guides on how to do it.
No? It's not a MCU brick. For some reason you just don't get code execution again after the soft reboot. You can't recover a MCU brick with an hardmod.It's actually a very rare MCU brick. This is why devs haven't been able to reproduce it because it's totally random and there's like a 1/1000 chance of it happening. That's still too much of a risk regardless of how miniscule the chances are, though, and this is why it was removed from the guide.
I know you can't. And I'm going by what was said in #Cakey last night, so that's where that misinformation came from.No? It's not a MCU brick. For some reason you just don't get code execution again after the soft reboot. You can't recover a MCU brick with an hardmod.
For the poll sure. For OTPLess installs, no.
Has there been any proof? Anecdotal reports aren't good enough for proof, especially when that user's skill level is unknown. I'm honestly asking, not arguing.
The reason I refuse to believe that this isn't just user error sans proof is because I do software QA for a living, and even on my team there are people who are professionally certified (multiple levels too) for this work through the ISTQB/ASTQB who miss things in the software documentation (I'm not claiming I'm above this). I closed two erroneously-reported defects today alone because the coworker (she holds certifications) who reported them did not understand the intended behavior. She didn't read carefully enough which led her to run "unsuccessful" tests.