i installed the patched agb firm to my nand yes. not the gba cias as your not supposed to install those to nand lolYou can it set to your NAND, right?
i installed the patched agb firm to my nand yes. not the gba cias as your not supposed to install those to nand lolYou can it set to your NAND, right?
Did you install the GBA games to both your sysNAND and emuNAND?i installed the patched agb firm to my nand yes. not the gba cias as your not supposed to install those to nand lol
yep, again im pretty familar with 3ds cfw stuffDid you install the GBA games to both your sysNAND and emuNAND?
thanks for adding it in, saving these sweet 0.7 seconds on my o3ds just like I measured with my modification just that this code is looking even cleanerCreate an empty file called "usepatchedfw" for this in the "rei" folder. For me it saves like a second on New 3DS.
Maybe you could use a status file to identify the applied patches(maybe even with a patch version to identify changes in the patches), this way you could patch it only if needed.If someone uses this without a9lh (menuhax, etc.) and then switches to a9lh, the old FIRMs are no good (no FIRM writes patch, wrong 9.0 patched FIRM...)
can someone clarify what are those patched firmwares? The new aureinand build says we must remove them. Is firmware90.bin considered to be patched?
No.
Basically in a nut-shell (as I understand it)
Firmware90.bin and Firmware.bin are untouched, original NativeFirm binaries.
Firmwarepatched.bin is basically all the patches AuRei uses patched into the original nativefirm. This patched FW is the one that's firmlaunched.
It's as gunner said. By the way, I need some testing with a new feature. This is for people who use A9LH and emuNAND. It should fix the bug with GBA saves (it forces AuRei to reboot in sysNand if AGB_FIRM was just quitted): http://www52.zippyshare.com/v/YjYzRhNd/file.html
Update to 2.7 first (including the "rei" folder!) and then replace the .bin. Tell me how it goes.
So you launched a GBA game from emuNAND, quitted it and it correctly rebooted to sysNAND?Worked for me on N3ds 9.1 J, this is a big help, particularly since it also boots back to sysnand after you use settings.
So you launched a GBA game from emuNAND, quitted it and it correctly rebooted to sysNAND?
Yeah, other than the GBA bug fix it also forces the same thing to be booted (regardless of held buttons) after a soft reboot (like exiting from System Settings).
It's as gunner said. By the way, I need some testing with a new feature. This is for people who use A9LH and emuNAND. It should fix the bug with GBA saves (it forces AuRei to reboot in sysNand if AGB_FIRM was just quitted): http://www52.zippyshare.com/v/YjYzRhNd/file.html
Update to 2.7 first (including the "rei" folder!) and then replace the .bin. Tell me how it goes.
Thanks for this. Still a bit con fused about what to do and what not to do, can someone really dumb this down for me?https://github.com/AuroraWright/AuReiNand/releases/tag/v3.7
- Added a flag to skip decrypting and patching FIRM and use the already patched ones, for a slightly faster boot and to avoid writing 1 MB to SD on each boot. Warning!: You MUST remove the patched firmwares in the rei folder after switching from a non-A9LH usage to A9LH. You have been warned! Original idea and patch by Fix94.
Create an empty file called "usepatchedfw" for this in the "rei" folder. For me it saves like a second on New 3DS.
It's as gunner said. By the way, I need some testing with a new feature. This is for people who use A9LH and emuNAND. It should fix the bug with GBA saves (it forces AuRei to reboot in sysNand if AGB_FIRM was just quitted): http://www52.zippyshare.com/v/YjYzRhNd/file.html
Update to 2.7 first (including the "rei" folder!) and then replace the .bin. Tell me how it goes.
Thanks for this. Still a bit con fused about what to do and what not to do, can someone really dumb this down for me?
http://www52.zippyshare.com/v/frCWhyR6/file.html This one works fine here (but I don't have GBA games on emuNAND).TLDR: Works for save, reboot loop with exiting sysNAND from System Settings.
Confirmed working on my unit. A9LH (9.2 sys, 10.6 emu) [both with patched AGB firm]
Opened GBA game from emuNAND.
Played a bit and saved. [booted to original Rei] confirmed save not present.
Opened GBA game again from emuNAND [your new loader]
Played a bit and saved.
Rebooted to new A9LH.bin and thrown into sysNAND.
Powered off and booted back to emuNAND and relaunched GBA. Save present.
Though as stated above for Seita, using System Settings to back out seems to loop it. Powering off and on works fine.
This doesn't benefit people who mainly use sysNAND, I assume?http://www52.zippyshare.com/v/frCWhyR6/file.html This one works fine here (but I don't have GBA games on emuNAND).
I enter sysNAND, I launch a GBA game. I quit it, and I hold L pressed, it successfully blocks my attempt and I find myself in SysNAND again.
Then I enter system settings, and I hold L while quitting it. It blocks my attempt and I end up in SysNAND again.
This doesn't benefit people who mainly use sysNAND, I assume?
http://www52.zippyshare.com/v/frCWhyR6/file.html This one works fine here (but I don't have GBA games on emuNAND).
I enter sysNAND, I launch a GBA game. I quit it, and I hold L pressed, it successfully blocks my attempt and I find myself in SysNAND again.
Then I enter system settings, and I hold L while quitting it. It blocks my attempt and I end up in SysNAND again.