https://github.com/AuroraWright/AuReiNand/blob/master/injector/source/patcher.c#L194Any idea about the "friends" patch?
https://github.com/AuroraWright/AuReiNand/blob/master/injector/source/patcher.c#L194Any idea about the "friends" patch?
Impossible to access your friend list with older firmware (server check), i think.
On my system, ARNbeta.7z behaves exactly like AuReiNand_v4.2 commit e882dd7 with respect to Custom and Ambassador GBA titles and rebooting afterwards.As some of you might already know, I was busy with a major AuReiNand overhaul. Now, I'll spoil the surprise for sure, but I learned that I need external testing to find bugs (there's always something that slips up). So, I'm publishing a beta.
http://www8.zippyshare.com/v/UioYD4Mt/file.html
There are a lot of changes:
- Gotten rid of the patched FIRMs, AuReiNand now finds and loads all the FIRMs from CTRNAND by default. If you are booting an emuNAND, the FIRMs will also be loaded from its CTRNAND. This also applies to AGB and TWL FIRM, and allows for a very fast boot with no firmware files on the SD card.
- If for some reason (like using NTR) you do not want to use the CTRNAND FIRM, you can place a firmware.bin in the aurei folder and it will be loaded just for the default NAND.
- 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.
- In order for AuReiNand to handle FIRM reboots, the .bin path needs to be hardcoded in the program. The default is /arm9loaderhax.bin (the AuReiNand.dat is also supported for 9.0 people). A PC tool was written to make changing the path easier.
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)
what region 3DS do you have?
Dlplay and dsinternet should stay
What was the issue?Just compiled the latest commit (7479bf8) and it fixes the twln issue. Everything seems to be working so far. Strong work!
Prior to the referenced commit I was getting a black screen/freeze when loading dsiware.What was the issue?
Ah, OKPrior to the referenced commit I was getting a black screen/freeze when loading dsiware.
Download the aureinand source. Replace the english text by the translated spanish text (no accent, you have to create them, pm me if you want to know how to do this) in the *.c files, recompile it.how can i translate it to my laguage? @AuroraWright
You would backup sysnand after the swap. It is no longer your emunand after you inject it into the sysnandokay there is one thing that does confuse me , regarding backups now.
lets say i have a 3ds which i have only sysNAND on it (having done the swap emuNAND method) and now wanting to backup my NAND just in case.
so which do i backup now though? off the emuNAND or the sysNAND ? i ask cause since it is the emuNAND that i have now inside sysNAND which i use with updated sysNAND option.
so the question is, which do i backup emu or sysNAND ? thanks in advance!
You would backup sysnand after the swap. It is no longer your emunand after you inject it into the sysnand
To update you just copy the new stuff over and delete the old stuff. You won't lose anything as its not touching the nand.Hi,
I am running this cfw after following Plailect's guide. I am not an expert by any means!
I would like to update my version of AuReiNand. I believe the version I setup my n3ds with was 3.14 and I can see there is a version 4.2 available.
I would like to backup before I update but I am not sure how.
Any help would be great. Thanks.
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.