Homebrew ARM9Loader -- Technical Details and Discussion

[LooneyElsa]

Nope. No CFW supports patching 2.1 FIRM.

No current CFW supports booting 2.1 emuNAND.

I see. So in theory there could be a safe way of getting OTP if we had 2.1 firm launch?
Cheers.

 

[Mrrraou]

I see. So in theory there could be a safe way of getting OTP if we had 2.1 firm launch?
Cheers.

Yes, there could be. (A safer way, not 100% safe, user errors always happen)

 

[Vappy]

I see. So in theory there could be a safe way of getting OTP if we had 2.1 firm launch?
Cheers.

EDIT: nvm, misread

 

[LooneyElsa]

EDIT: nvm, misread

Well at least one would be able to tell if they have the right 2.1 nand rom.

 

[Mrrraou]

Well at least one would be able to tell if they have the right 2.1 nand rom.

Almost, as the NCSD header wouldn't be checked when firmlaunching a 2.1 FIRM.

 

[JacksonS]

Sorry to ask again, but I'm really curious what I have to do to get rid of emuNAND and update my sysNAND for use with Arm9LoaderHax. I can't use AuReiNAND (I don't think) because I would have to hold L every time to boot into sysNAND. So what does it take?

 

[Nintendo4DSXL]

Sorry to ask again, but I'm really curious what I have to do to get rid of emuNAND and update my sysNAND for use with Arm9LoaderHax. I can't use AuReiNAND (I don't think) because I would have to hold L every time to boot into sysNAND. So what does it take?

In the new update it autoboot sysnand
and it has a patch for System Update

 

[JacksonS]

In the new update it autoboot sysnand

Okay, I see, you have to enable it. Thank you. Can I update my sysNAND regularly? Won't that overwrite the FIRM0/FIRM1 partitions?

 

[Nintendo4DSXL]

Okay, I see, you have to enable it. Thank you. Can I update my sysNAND regularly? Won't that overwrite the FIRM0/FIRM1 partitions?

Here are the Changelog:

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.

 

[AtlasFontaine]

I had to compile with mSys since Cmd and python console did not work for me, so people having problems should try it.

 

[JacksonS]

Here are the Changelog:

Got it, I really wasn't reading closely enough. Now I feel bad .

 

[Earth97]

So, this new CFW booting system is permanent and updates can't patch it. I'll be allowed to update my sysNAND without losing patches. Did I get all correctly?

 

[JacksonS]

So, this new CFW booting system is permanent and updates can't patch it. I'll be allowed to update my sysNAND without losing patches. Did I get all correctly?

I think just updating normally will patch it by overwriting the FIRM0 and FIRM1 partitions. But the new release of AuReiNAND enables a patch that lets you update without overwriting those. I may be wrong though.

 

[Epicdaftman]

Are there people who are currently working on making emunand run 2.1? I'd like to know before I possibly screw my SysNand up?.

 

[Earth97]

Essentially, I could update all the system files without touching the FIRM partition necessary to have A9LH working. Does this mean we could "spoof" our firmware?

 

[Sgt. Lulz]

So, this new CFW booting system is permanent and updates can't patch it. I'll be allowed to update my sysNAND without losing patches. Did I get all correctly?

#1 is slightly off the mark. A system update on an unprepared payload (i.e. doesn't protect the FIRM partitions, sector 0x5C000 or the 0x96 keystore if Nintendo were insane enough to modify that) will brick the console completely and you'll need a hardmod to restore it.
Other than that, more or less, yes.
That said I still don't get why so many people want to do all their CFW stuff on sysNAND when emuNAND infers no disadvantages outside DSiWare and AGB titles.

 

[JacksonS]

That said I still don't get why so many people want to do all their CFW stuff on sysNAND when emuNAND infers no disadvantages outside DSiWare and AGB titles.

I am just hoping that it will make things quicker because it seems like anything I do on emuNAND (even before installing all my games) is much slower than sysNAND. I assume that's because it's accessing the SD card all the time.

 

[Earth97]

#1 is slightly off the mark. A system update on an unprepared payload (i.e. doesn't protect the FIRM partitions, sector 0x5C000 or the 0x96 keystore if Nintendo were insane enough to modify that) will brick the console completely and you'll need a hardmod to restore it.
Other than that, more or less, yes.
That said I still don't get why so many people want to do all their CFW stuff on sysNAND when emuNAND infers no disadvantages outside DSiWare and AGB titles.

What is stored in the FIRM partitions? I mean, if new firmwares were out (e.g. 10.6, 10.7) with updated FIRMs, what difference would exist between my payload-protected updated console and a commonly-updated console? Could I still access the Nintendo e-Shop and so on?

 

[valyr]

well after rebuilding my hardmod connector twice (i wired the microsd adaper end wrong) this took me a little over 20 minutes
from start to finish. my 9.2 O3dsxl now boots aureinand 3.5 straight to emunand from boot. im impressed with the loading speeds

 

[dark_samus3]

What is stored in the FIRM partitions? I mean, if new firmwares were out (e.g. 10.6, 10.7) with updated FIRMs, what difference would exist between my payload-protected updated console and a commonly-updated console? Could I still access the Nintendo e-Shop and so on?

Well you'd just need to update your firmware.bin... Since the arm9loaderhax uses both firm0 and 1 slots they cannot be updated