Hacking Luma3DS - Noob-proof 3DS Custom Firmware

  • Thread starter Thread starter Aurora Wright
  • Start date Start date
  • Views Views 3,156,436
  • Replies Replies 19,840
  • Likes Likes 262
Status
Not open for further replies.
No, you need completely different files!

Ah thank, the older AuReiNand.zip file didnt have the firmware.bin file in the Rei-O3ds folder before, but the 3.5 version does. I can now boot into EmuNand mode when i run ReiNand through the Homebrew channel.

But what do i need to do so it auto boots into ReiNand?, also i noticed when i check the CFW version it just said '10.3.028E', no mention of Rei, ie 'Rei-10.3.28E' is this normal?
 
Only if you create that file. Else, everything will stay the same.
That flag is for A9LH people who want to replace using emuNAND with sysNAND :D And in that case, having a 9.0 emuNAND is more useful than an updated one (as you can't use programs like Decrypt9 on an updated sysNAND/emuNAND)
well my emunand is updated since it meant I could install game updates without needs the update.cia files for them.
 
I do have A9LH, so pretty much I have to use the flag and update sysnand through mset, thanks for your hard work :)

Let me know if this works! I enjoy the idea of using an up to date sysnand and just keeping a 9.2 emunand for exploits.
 
"Nintendo4DSXL, post: 6090974, member: 378906"]Is there a way to keep all installed stuff from my emuNAND in sysNAND?

You can dump parts of your emunand and import them into sysnand but unfortunately I'm not sure how it is done.
 
Is there a way to keep all installed stuff from my emuNAND in sysNAND?
Use Decrypt9 to extract the CTRNAND, TWLN, TWLP and AGBSAVE partitions (DON'T, DON'T do it with FIRM0 and FIRM1) from emuNAND, import them on sysNAND. IF you want, export them from sysNAND and import them into emuNAND first, so you have a 9.0 emuNAND.
 
What about the part where System Update would break the FIRM partitions and break the exploit along with bricking the console?
she said it is patched:

New version!
  • Fixed A9LH boot detection
  • Added a new "updated sysNAND" mode, which is enabled by the "/rei/updatedsysnand" flag. In this mode, sysNAND is booted by default using the 9.6-10.4 FIRM, L boots emuNAND with 9.0 FIRM (for arm9 exploits and such) and L+R boots emuNAND with the 9.6-10.4 FIRM.
  • When sysNAND is booted on a A9LH setup, a patch (courtesy of delebile) is applied that makes updates skip writing to FIRM0 and FIRM1. This way, sysNAND can be updated without losing A9LH.
 
she said it is patched:

New version!
  • Fixed A9LH boot detection
  • Added a new "updated sysNAND" mode, which is enabled by the "/rei/updatedsysnand" flag. In this mode, sysNAND is booted by default using the 9.6-10.4 FIRM, L boots emuNAND with 9.0 FIRM (for arm9 exploits and such) and L+R boots emuNAND with the 9.6-10.4 FIRM.
  • When sysNAND is booted on a A9LH setup, a patch (courtesy of delebile) is applied that makes updates skip writing to FIRM0 and FIRM1. This way, sysNAND can be updated without losing A9LH.
Oh, nice. Thanks for the info.

all decrypt9 does is flash a red screen and go back to homebrew menu now using hbl on sysnand.
Are you holding L+R?
I was running into that because I was only holding L while booting sysNAND.
 
Oh, nice. Thanks for the info.


Are you holding L+R?
I was running into that because I was only holding L while booting sysNAND.
I'm using the new reinand mod version 3.5 that was just pushed out like 15 minutes ago which auto boots the patched sysnand.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum