That was a terrible idea.Of i downgrade my new 3ds xl and get the otp, can i upgrade back to 9.2?
Of i downgrade my new 3ds xl and get the otp, can i upgrade back to 9.2?
as long as your WiFi is on, yes. use the Decrypt9.bin (renamed to arm9.bin) and the arm11.bin posted in the OTP guide (just look in the guides section, it's the top post right now)Of i downgrade my new 3ds xl and get the otp, can i upgrade back to 9.2?
If you have a NAND backup just restore it.I have a nand back up lol... Im just asking before I start if I can go back to 9.2 after I get my otp as I heard with a new 3ds I cant and I dont want to be stuck at a low fw waiting.
you'll be fine, several users have reported success.I have a nand back up lol... Im just asking before I start if I can go back to 9.2 after I get my otp as I heard with a new 3ds I cant and I dont want to be stuck at a low fw waiting.

Someone should setup a virtual machine and get a compile environment setup and confirm that it works. Then distribute that as a VirtualBox image or something so people will have a quick and safe way of compiling Arm9LoaderHax. I do know some bricks are probably the result of Arm9loaderHax not compiling correctly. There are ways it can go wrong that won't result in a visible error message when compiling so perhaps that would be the best way to ensure a safe public Arm9LoaderHax installer.![]()

I'm working on itSomeone should setup a virtual machine and get a compile environment setup and confirm that it works. Then distribute that as a VirtualBox image or something so people will have a quick and safe way of compiling Arm9LoaderHax. I do know some bricks are probably the result of Arm9loaderHax not compiling correctly. There are ways it can go wrong that won't result in a visible error message when compiling so perhaps that would be the best way to ensure a safe public Arm9LoaderHax installer.![]()

And that's what I'm working on... I've got a working, load from SD payload, it's rough though so it'll be a bit before it's readyYeah. the compiled 3DSX has the payloads built into it and are console unique. Never share the resulting 3dsx/elf file with anyone one else. It's a guaranteed brick if you do.
And that's what I'm working on... I've got a working, load from SD payload, it's rough though so it'll be a bit before it's ready

YepI'm assuming the compiled 3DSX installs something permanently in sysnand, hence the guaranteed brick if you do it wrong?
In all fairness, the guy quoting me had already attempted the OTP dump and ran into a partial downgrade/softbrick thanks to sysUpdater failing out every time.If you need instructions, don't do it.
Seriously don't.
For the love of god.
We have 20+ bricks.
ON ONE DEVICE.
If you can't read the instructions or need to be told how to compile arm9loaderhax, here's a tip:
DON'T.
Not a brag post buy why everyone seems to be having issues with sysupdater? I used the .cia version with rxtools devmode to DG my o3ds and succeeded on the first run, dumped the OTP twice and verified their checksums, updated to 4.3 using OoT (Rev01 reprint) and launched Decrypt9 through MSET to restore back to 9.2