Homebrew ARM9Loader -- Technical Details and Discussion

[Nintendo4DSXL]

So I done a lot more reading of this topic which I should probably have done before going head first off a cliff to get my OTP!

Basically I now understand I'm just going to have to be patient and wait for a payload that can boot directly into sysnand.

But hey thanks to the guys in the beginning who got all of this working.

Hello i have emunand and now i have recopy all the rei files and now it works i can boot directly into emunand now i have to wait for SysNAND payload

 

[Audioboxer]

Hello i have emunand and now i have recopy all the rei files and now it works i can boot directly into emunand now i have to wait for SysNAND payload

Yeah If you had emunand from the start it would work. Issue is I have no emunand! But I'm glad to hear your 3DS is back up and running.

We were brick buddies for a while lol.

 

[Nintendo4DSXL]

Yeah If you had emunand from the start it would work. Issue is I have no emunand! But I'm glad to hear your 3DS is back up and running.

We were brick buddies for a while lol.

I do not know if you had already found it but i found an a9lh.bin for AuReiNand http://gbatemp.net/threads/source-release-reinand-n3ds-cfw.394309/page-196#post-6083433

 

[Audioboxer]

I do not know if you had already found it but i found an a9lh.bin for AuReiNand http://gbatemp.net/threads/source-release-reinand-n3ds-cfw.394309/page-196#post-6083433

Yeah I was using it. Failed to get it booting into sysnand last night, but I'll try again today.

 

[Shadowtrance]

Yeah I was using it. Failed to get it booting into sysnand last night, but I'll try again today.

You still need the rei folder on sd root with firmware.bin in it of course.

 

[Audioboxer]

You still need the rei folder on sd root with firmware.bin in it of course.

Yeah I used rei-N3DS from Aurora (renamed to rei of course), and firmware.bin from latest official Rei build. Think it might be the firmware.bin that is wrong. Don't I need a specific one for FW 9.2? Can't remember 100% as I've been using emunand 10.x for ages.

 

[Shadowtrance]

Yeah I used rei-N3DS from Aurora (renamed to rei of course), and firmware.bin from latest official Rei build. Think it might be the firmware.bin that is wrong. Don't I need a specific one for FW 9.2? Can't remember 100% as I've been using emunand 10.x for ages.

Not sure. i just used the firmware.bin from the aurora build.

 

[Audioboxer]

Not sure. i just used the firmware.bin from the aurora build.

Aurora build doesn't come with it as standard (https://github.com/AuroraWright/AuReiNand/releases). I'll test a couple of firmware.bin files and one should work.

 

[Shadowtrance]

Aurora build doesn't come with it as standard (https://github.com/AuroraWright/AuReiNand/releases). I'll test a couple of firmware.bin files and one should work.

Oh right... hangon.

 

[Audioboxer]

Slight technical question, and a noob one, I'm pretty sure I know the answer though. Nintendo can't force this hack out of our sysnand can they? With something like a FW update? I know a sysnand restore can remove the loader, but Nintendos FW update process cannot? Seeing as Shadow is on 10.5 on sysnand it seems I do already have this answer.

 

[daxtsu]

Slight technical question, and a noob one, I'm pretty sure I know the answer though. Nintendo can't force this hack out of our sysnand can they? With something like a FW update? I know a sysnand restore can remove the loader, but Nintendos FW update process cannot? Seeing as Shadow is on 10.5 on sysnand it seems I do already have this answer.

If you stick with an emuNAND solution, then probably not. However, if you opt to go the sysNAND CFW route (like most probably will), I guess they could maybe try to look for it and remove it, but would it really be worth their time? I doubt CFW users are so numerous that we really pose a huge problem compared to the amount of PSP CFW users there were.

 

[Shadowtrance]

Slight technical question, and a noob one, I'm pretty sure I know the answer though. Nintendo can't force this hack out of our sysnand can they? With something like a FW update? I know a sysnand restore can remove the loader, but Nintendos FW update process cannot? Seeing as Shadow is on 10.5 on sysnand it seems I do already have this answer.

Updating via system settings WILL atm brick your system.
How I did it was... update with 10.5 cia's MINUS the native firm one...with sysupdater cia.
then eshop was bitching at me about updating so i THEN installed the native firm cia with devmenu.
fully functioning sysnand 10.5 with a9lh n3ds is the result.

 

[Audioboxer]

If you stick with an emuNAND solution, then probably not. However, if you opt to go the sysNAND CFW route (like most probably will), I guess they could maybe try to look for it and remove it, but would it really be worth their time? I doubt CFW users are so numerous that we really pose a huge problem compared to the amount of PSP CFW users there were.

True. I mean just wondering hypotheticals, as running a FW update is at your own peril anyway. I guess even if they do, a sysupdater style CIA update will probably be made to get onto later FWs.

Updating via system settings WILL atm brick your system.
How I did it was... update with 10.5 cia's MINUS the native firm one...with sysupdater cia.
then eshop was bitching at me about updating so i THEN installed the native firm cia with devmenu.
fully functioning sysnand 10.5 with a9lh n3ds is the result.

Interesting to know how you done it, but without a hardmod no thanks At least not for now till things mature with arm9.

Out of interest can you restore a sysnand backup to go back down to 9.2, or do you need to use your hard mod to do so? I'd assume sysnand backup is okay.

 

[daxtsu]

True. I mean just wondering hypotheticals, as running a FW update is at your own peril anyway. I guess even if they do, a sysupdater style CIA update will probably be made to get onto later FWs.



Interesting to know how you done it, but without a hardmod no thanks At least not for now till things mature with arm9.

Out of interest can you restore a sysnand backup to go back down to 9.2, or do you need to use your hard mod to do so? I'd assume sysnand backup is okay.

It should be okay to use Aurora's mod to boot decrypt9 and do it that way with no hardmod, but I can't promise success (never tried it..).

 

[Audioboxer]

It should be okay to use Aurora's mod to boot decrypt9 and do it that way with no hardmod, but I can't promise success (never tried it..).

Yeah I don't see why not considering the arm9loader is allowing us to execute everything "prior" to boot regardless of the sysnand FW version.

I'll probably just setup an emunand again to keep my noob self in check and leave sysnand until the actual devs continue their work.

 

[Shadowtrance]

It should be okay to use Aurora's mod to boot decrypt9 and do it that way with no hardmod, but I can't promise success (never tried it..).

D9 won't boot after the firm has loaded because it's too high so brahma fails and therefore D9 won't load.
D9 DOES load as arm9loaderhax.bin though but you can't see shit on screen yet obviously. lol

 

[daxtsu]

D9 won't boot after the firm has loaded because it's too high so brahma fails and therefore D9 won't load.
D9 DOES load as arm9loaderhax.bin though but you can't see shit on screen yet obviously. lol

What about holding the button which launches the FIRM from the actual sysNAND and not the SD?

 

[Kayak]

Audioboxer if you update through system settings it can lead to a brick, Shadow updated using Sysupdater with the Native_firm.cia removed, later he installed the native_firm but I would advise against it at the moment.

 

[Shadowtrance]

What about holding the button which launches the FIRM from the actual sysNAND and not the SD?

That isn't in this build as far as i know. and any builds I've compiled myself for some reason won't load. (NFI why...)
Either way if your sysnand is above 9.2 brahma will still fail... wtb brahma for >9.2 lol

 

[daxtsu]

That isn't in this build as far as i know. and any builds I've compiled myself for some reason won't load.
Either way if your sysnand is above 9.2 brahma will still fail... wtb brahma for >9.2 lol

I see. Hopefully we'll see a build that supports launching FIRM from sysNAND then, so restoring is an option (not that I'd want to personally).