Is 2.50-7.
FIRM version is the same.
System version 9.2.0-20.
that's 10.0 FIRM wat - did the key switch even happen?Is 2.50-7.
That's what I was thinking, haha.that's 10.0 FIRM wat - did the key switch even happen?
I think you need to get into *hax, use FBI, and install a 9.0 New 3DS FIRM CIA.
all regions share the same FIRM. just make sure it's for *New* 3DS. you can get it from the 9.2 packs on Plailect's guideThat's what I was thinking, haha.
9.0 native firm is regionfree, correct?
Wouldn't that just install firm90 to ctrnand? I think he has to do a proper downgrade to get AM_InstallNativeFIRM or whatever it's called.that's 10.0 FIRM wat - did the key switch even happen?
I think you need to get into *hax, use FBI, and install a 9.0 New 3DS FIRM CIA.
FBI installs it properly. sysDowngrader/etc won't downgrade it since the one installed in CTRNAND is still 9.0.Wouldn't that just install firm90 to ctrnand? I think he has to do a proper downgrade to get AM_InstallNativeFIRM or whatever it's called.
Worked perfectly on EUR N3DS 9.2 without OTP
--------------------- MERGED ---------------------------
Oh one thing I should mention actually, the first time I ran the installer I got a black screen hang. I powered cucled, re-launched hax and tried again and it worked.
I suspected as much. Is it possible for this to be detected and an error displayed?That sounds like brahma failing to get arm9 code execution, and not a problem with unsafea9lhinstaller, heh.
I suspected as much. Is it possible for this to be detected and an error displayed?
(I realise this is alpha and that this is probably planned, just mentioning in case it didn't come up for other testers)
Oh right. No worries thenNah, can't handle that case -- my code isn't running if that happens. On the bright side, that'll never cause a brick -- that's just the "may take a few tries to launch" all arm9 homebrew gets.
nope, it needs arm9 exploit, so 9.2 onlyWill this work in a N3dsxl with 11.1E?
Sent from my SM-A310F using Tapatalk
Will this work in a N3dsxl with 11.1E?
it's still only for those on 9.2 or below/those who can downgrade to 9.2).
After the first reboot it should relaunch the unsafe installer (from an a9lh payload I think), then install again, and then reboot. You would have to replace the arm9loaderhax.bin that the installer creates in the SD card otherwise it would keep booting to the installer. If it doesn't do that, then it didn't install a9lh into sysnand.Hmmm.
At first I tried redownloading the unsafeinstaller since it may have been a botched download.
Copied all the files back to the root, deleted the arm9loaderhax.bin, deleted the previous files from the old download.
Opens HBL on a correct non-frankenfirmware 9.2.
Selects the installer.
Presses SELECT (#YOLO)
Console reboots. The installer actually says the console should reboot twice?
Anyway, console reboots (once) and throws me back into Menuhax with 10.0 nfirm. I've tried this out 6 times. Also, I can't join your IRC since I'm now at school, @SciresM.
no, they are on 9.2, but it keeps failing to write to the key sector(?), so it boots 10.0 NATIVE_FIRM normally.After the first reboot it should relaunch the unsafe installer (from an a9lh payload I think), then install again, and then reboot. You would have to replace the arm9loaderhax.bin that the installer creates in the SD card otherwise it would keep booting to the installer. If it doesn't do that, then it didn't install a9lh into sysnand.
Edit, wait, you're on 10.x? You need to be on 9.2 for this to work.
Oh sorry I misunderstood when he said he boots back to 10.0 NFIRM. @LinkSoraZelda do you already have A9LH installed?no, they are on 9.2, but it keeps failing to write to the key sector(?), so it boots 10.0 NATIVE_FIRM normally.
Nope.Oh sorry I misunderstood when he said he boots back to 10.0 NFIRM. @LinkSoraZelda do you already have A9LH installed?