Just FYI, I set up a website that compiles the latest commit of ARN at astronautlevel2.github.io/AuReiNand
It compiles it hourly, so it should be pretty up to date
It compiles it hourly, so it should be pretty up to date
It seems to be not patching them for me. For every update do we need to delete the patched_firms?working fine here, just pulled and compiled latest commit a min ago
Today's new special ability; Faster than a speeding bullet! More powerful than a locomotive!
It displays more info when something crashesWhat "Use developer UNITINFO" does?
It displays more info when something crashes
Not useful for most people
AlwaysIt seems to be not patching them for me. For every update do we need to delete the patched_firms?
Sadly, this didnt help. As soon as i try to update to the newest ARN my dsi and gba games no longer work. But if i go back to 4.27 they work fine.Always
Sent from my LG-D851 using Tapatalk
This means you're booting a 10.x NAND with the 9.0 FIRM. Check if the config is correct ("Updated sysNAND" probably isn't).Yeah just tried it a few more times to be sure and it's definitely not letting me launch another GBA after exiting from it and landing on sysNAND. Would need other people to confirm though just in case it's an isolated issue with me.
Also, forcing a softboot to turn into a regular cold boot doesn't seem to work anymore from sysNAND. Pressing just B reboots back into it, however pressing B and any other (non assigned) button forces the boot and defaults to my regular emuNAND setup. Not a big deal since I can force going back to emunand by pressing down a non-configured combo but wanted to let you know about it/in case someone else runs across this.
EDIT: It seems that pressing R doesn't work at all for me. Pressing nothing takes me to my emuNAND with no issues, pressing L takes me to sysNAND with no issues. However if I use R, the console gets stuck on a blank screen. I wonder if this is the reason why the above doesn't work?
I'm trying to boot into the sysNAND which is at 9.2 and emuNAND is at 10.7. In the commit notes I read:This means you're booting a 10.x NAND with the 9.0 FIRM. Check if the config is correct ("Updated sysNAND" probably isn't).
- The way AuReiNand works has changed. Now you can specify to autoboot SysNAND or not, and a NAND is no more tied to a FIRM (since 9.0 FIRM is autodetected). If you press nothing the default NAND is booted with its own FIRM, L boots the non-default NAND with its own FIRM, R boots EmuNAND with the SysNAND FIRM if you picked "Updated SysNAND", and vice-versa.
It's being testedwait, overclocking is integrated in the later builds now?!![]()
Check thisAnyone have comment 649b160 compiled?
Sent from my LG-D851 using Tapatalk
Just FYI, I set up a website that compiles the latest commit of ARN at astronautlevel2.github.io/AuReiNand
It compiles it hourly, so it should be pretty up to date![]()
Or letting the true power of the 3ds be used lolIts not overclocking; its more like performance vs battery saving mode
That's what I meant. If you deselect updated sysNAND, emuNAND FIRM will be considered suitable for booting sysNAND. That's all the option does now, basically. I don't have an updated emuNAND, but I have a 3ds with two 9.0 NANDs and one with updated sys and 9.0 emu, and it works on the first and (as expected) black screens on the second with updated sysnand disabled.I'm trying to boot into the sysNAND which is at 9.2 and emuNAND is at 10.7. In the commit notes I read:
Seeing the vice-versa means that if I hold down R, it should boot sysNAND (9.x) with the emuNAND's FIRM (10.x).
Either way the GBA situation is still the same, I just didn't know if this would be linked to it so I wanted you to be the judge![]()
Share it plez?
