Meh, I'd rather have it sooner than later... Though "later" won't be for hours, anyways the "trouble" I'll be going through is literally a two line change, compile, copy a few files and upload them somewhere, so no trouble at all really...
First thing's first arm9 code execution ON BOOT earlier than menuhax ever thought of being, on 10.5... If you brick your sysNAND, so what? You can just boot something like Decrypt9 and restore a NAND backup and be on your way, emuNAND is negated... Why? Easy, this exploit is unpatchable... Leave the FIRM(s) alone and you can update to the latest every time, no worries... Again if something happens, just boot D9 and restore a backup, easy peasy... It's the ULTIMATE 3ds hack, and the only way to fix it is with a hardware revision
I guess you're right I didn't think about that but the process just seems really convoluted for someone like me I dont want to say I need to be spoon fed but after reading that technical right up I might as well be a dribbling baby. Ill wait for clearer steps so I dont get my dick caught in a ceiling fan again.
LOL... It's really not THAT bad, assuming you have cubic ninja it's basically downgrade to 1.x-2.x, put files on SD card, scan QR code, get back to 9.2 then compile arm9loaderhax with your OTP dump then run the .3dsx installer which does most of the work for you... But it's really for developers only atm
Right, it's not an easy process, and attempting it without a hardmod really isn't recommended at all. For N3DS, it's all but required. If you're happy with menuhax and emuNAND, then keep using that. This is just for people who'll put in a lot to gain a little extra.
I don't think enough people have performed the downgrade and reported their success to really say what the best method is, but it does seem possible that 4.x FIRM will be more compatible with 2.x titles.
I have cubic Ninja and my N3DS is hard modded I just dont understand how to do this without scratching my head wondering why im getting black screens at step.X know what I mean.
Here's my experience with it, downgrading always errors out for some reason, and when booting again you have to restart the downgrade again... I seemed to have better luck with exploits if I went 9.2 -> 4.5 -> 2.1... But that's just me, several other users have reported just going direct from 9.2 to 1.0 with 0 problemsRight, it's not an easy process, and attempting it without a hardmod really isn't recommended at all. For N3DS, it's all but required. If you're happy with menuhax and emuNAND, then keep using that. This is just for people who'll put in a lot to gain a little extra.
I don't think enough people have performed the downgrade and reported their success to really say what the best method is, but it does seem possible that 4.x FIRM will be more compatible with 2.x titles.
Ah, yeah, haven't seen anyone with an n3ds get downgraded yet... I feel like there might be something more that we're missing, something stupid and obvious haha
Does the 3dsx have to be compiled with the otp.bin. I keep getting errors compiling it. It gets the firm0 and firm1 in data output then errors. Seeing as the data input goes on the sd root can someone share the 3dsx please
Yes, the OTP.bin is mandatory, and unique to each individual 3DS. You can't use anyone else's.
It'll work on N3DS. Just requires a hardmod and two xorpads using different keyslots.
You can start the process with emuNAND (though there's really no point for it on o3ds) but you cannot finish it... Mainly because the protection bit has already been set by the NATIVE_FIRM that is loaded on boot and booting it in emuNAND isn't enough to undo that... Also there's no emuNAND patches for 1.x-2.x (or 3.x for that matter) so it wouldn't work
Short answer, no.
Actually, you could just not use the OTP data... Change a byte in the secret sector and hope it works, if it doesn't try again and again until you get a jump to the payload (which is more likely than you'd think) once you get the jump to the payload you'd just need a payload to do the unbricking
