Maybe I control the Temp serverUnless my internet also broke at the same time as yours, I think that GBATemp derped.![]()
Interesting time for both the Temp and my internet to derp
Maybe I control the Temp serverUnless my internet also broke at the same time as yours, I think that GBATemp derped.![]()
huh, i deleted all the firmware.bin files on the aurei folder and i'm getting an error where it's looking for firmware.bin still. i'm using aurei 4.2, is this feature only available in a secret beta or something?Yep, it should load them from your NAND and patch them on-the-go.
You need to use the redirect program, else it won't work. Same for DS stuff.First let me say nice release (even if beta) @Aurora Wright, lots of cool stuff in the changelog.
Trying the AuReiNand re-write but I can't seem to get GBA to work. In the config I chose Autoboot SysNAND, show current NAND is System Settings and Show GBA boot screen in patched AGB_FIRM. I load AuReiNand using arm9select from down.bin in payloads folder on root of mSD. If anyone has GBA working that is not updated sysNAND, please share how you got it working. Thanks.
It's available in the beta posted by Aurora 2 pages back.huh, i deleted all the firmware.bin files on the aurei folder and i'm getting an error where it's looking for firmware.bin still. i'm using aurei 4.2, is this feature only available in a secret beta or something?
It's in the newest beta that you can find a few pages ago.huh, i deleted all the firmware.bin files on the aurei folder and i'm getting an error where it's looking for firmware.bin still. i'm using aurei 4.2, is this feature only available in a secret beta or something?
I have this same problem! You need to run the corresponding patcher in the "pathchanger," with windows, I believe you just need to drag and drop the current arm9loaderhax.bin and it will prompt to ask for the new name.First let me say nice release (even if beta) @Aurora Wright, lots of cool stuff in the changelog.
Trying the AuReiNand re-write but I can't seem to get GBA to work. In the config I chose Autoboot SysNAND, show current NAND is System Settings and Show GBA boot screen in patched AGB_FIRM. I load AuReiNand using arm9select from down.bin in payloads folder on root of mSD. If anyone has GBA working that is not updated sysNAND, please share how you got it working. Thanks.
I have this same problem! You need to run the corresponding patcher in the "pathchanger," with windows, I believe you just need to drag and drop the current arm9loaderhax.bin and it will prompt to ask for the new name.
With Linux, refer to my post here. I believe OSX follows the same steps (I could be wrong)
Yeah, you'd need to have the NTR (10.2) firmware.bin file in /aurei/ to keep using NTR.Okay, so let me get this straight... With the beta, there is no need for external firms from the firms.7z file from Aurora's git. But, in my case, I have an emuNAND setup and occasionally use NTR, so I would keep my NTR firmware.bin on the SD card and it should be loaded by default...? I just tried having the appropriate NTR firmware.bin file (from firms.7z) on the SD card but NTR spits out the "unknown firm" error whenever I launch it from my emuNAND.
I can confirm, however, that GBA games and DSi games are working perfectly from both the sysNAND and emuNAND.
You don't need to type the whole patch just type "down.bin"Did the pathchanger changing my path to payloads/down.bin, GBA not working for me. I am a 9.2 sysNAND user with 10.7.0-32U emuNAND. In the config I chose autoboot sysNAND. I guess my next question is what firmware does sysNAND boot into as GBA does not work in my setup. I have no files in my aurei folder.
You don't need to type the whole patch just type "down.bin"
And it will be loaded by default then? Or do I have to press a button in order to load the NTR firmware.bin file?Yeah, you'd need to have the NTR (10.2) firmware.bin file in /aurei/ to keep using NTR.
If not, it would load the FIRM on your NAND, which is 10.4. That FIRM doesn't work with NTR.
I believe that's only if they are stored in a folder. Like if they are stored in a payload folder, then you add it. But if it's stored in root, then you don't need to add anything to it. So if it's just renaming "arm9loaderhax.bin" to "down.bin," then you don't need to anything beyond that. At least, that's what just worked for me.@Aurora Wright posted this at the bottom of his beta release post.
To use the path changer program, just drag the .bin on top and type the filename. (suppose it's in randomloader/arn.bin, type just that).
I'd like to have feedback on "complicated" setups (NANDs with different FIRMs, and things like that)
Yeah, if your SD card has a firmware.bin file, it'll load that one by default.And it will be loaded by default then? Or do I have to press a button in order to load the NTR firmware.bin file?
I believe that's only if they are stored in a folder. Like if they are stored in a payload folder, then you add it. But if it's stored in root, then you don't need to add anything to it. So if it's just renaming "arm9loaderhax.bin" to "down.bin," then you don't need to anything beyond that. At least, that's what just worked for me.
If someone wants to chime in, that would be cool too because this is new and I am just quoting what worked for me! But I am not running an emuNAND.
Got it got it, okay now everything is loading just fine. I re-copied the 10.2 firmware.bin to my SD card via my computer's SD card reader as instead of FTP-ing it and everything seems to be working a-okay now. Thanks for the help! And major props Aurora, this is a pretty kick-ass beta!Yeah, if your SD card has a firmware.bin file, it'll load that one by default.
If it doesn't have a firmware.bin file, it'll load the one from NAND.
Because I can't stand to leave someone hanging. I am going to be blunt, I have no idea, sadly. But just wait a few minutes (maybe a few hours at worst,) and this will have been tested to death and easily fixed. AuReiNAND moves fasts.My AuReiNand bin is named down.bin and in folder payloads on msd. So I changed path to payloads/down.bin using pathchanger. AuReiNand boots to sysNAND when I hold down at boot. Once in sysNAND no GBA works (an error has occurred message). In AuReiNand 4.2 for me to get GBA to work I had to launch them from sysNAND using firmware.bin from mSD by holding R on boot. They will not launch on AuReiNand 4.2 using 9.0 Firmware (holding L). My question now is how does it work in the new beta?
Because I can't stand to leave someone hanging. I am going to be blunt, I have no idea, sadly. But just wait a few minutes (maybe a few hours at worst,) and this will have been tested to death and easily fixed. AuReiNAND moves fasts.
