What hax entrypoint are you using to run the installer?Nope.
What hax entrypoint are you using to run the installer?Nope.
Menuhax. Other than OoThax this should be the most stable environment.What hax entrypoint are you using to run the installer?
Do you have any other entrypoints? Menuhax can be buggy, so you may want to try using Ninjhax if possible. Also, when I did it I used a blank SD card with the exception of an updated boot.3dsx downloaded from smealum.github.io/3ds/ and the unsafe installer files. You may want to consider something similar, even if it means backing up your SD card, erasing it, then copying just those files.Menuhax. Other than OoThax this should be the most stable environment.
Menuhax. Other than OoThax this should be the most stable environment.
Can you run the downgrade check in my sig and post the results?Menuhax. Other than OoThax this should be the most stable environment.
This should brick it for the time being, no? That's gonna have to wait.@LinkSoraZelda you should downgrade FIRM to 9.0 again (make sure it says 2.46-0 in 3DSident), then try modifying the key sector a bit with GodMode9. change some byte after offset 0x10. I want to see if any edits to it persist.
Hol up.Can you run the downgrade check in my sig and post the results?
3ds/downgrade_check/check.log
Just want to see what else besides nfirm might be unusual.
no, it won't brick (as long as you edit things past 0x10) if you're using a pre-9.6 FIRM.This should brick it for the time being, no? That's gonna have to wait.
Change your region?Arm9 access? Well, still no for a Korean New 3DS
(Korean New 3DSes started with 9.3...)
That still needs an arm9 exploit to do it.Change your region?