Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Bu2d85]

Put it in the /rei/ folder.

Thanks, but now it's hanging on patching svc check.

EDIT: Got passed that but no says current firmware not supported.

 

[Supster131]

Thanks, but now it's hanging on patching svc check.

For some reason, at least for me, NTR doesn't work on the latest version of AuReiNAND, even with the 10.2 FIRM.

 

[Bu2d85]

For some reason, at least for me, NTR doesn't work on the latest version of AuReiNAND, even with the 10.2 FIRM.

I'm not on the latest, I'm about 2 or so revisions back from before the gbavc save fix.

 

[dsoldier]

For some reason, at least for me, NTR doesn't work on the latest version of AuReiNAND, even with the 10.2 FIRM.

it works for me with the ntr firm

 

[Bu2d85]

it works for me with the ntr firm

Booting with cubic ninja instead of the cia gives me an unknown firmware fault.

 

[Aurora Wright]

I just got chainloading Decrypt9 (or whatever arm9 payload) to work directly from AuRei. However, it's not very comfortable/useful: as AuReiNand is a normal brahma payload, it's running from 0x23F00000, however this is the same address other brahma payloads (like D9) use. So I can't overwrite AuRei while it's in memory I had to recompile D9 to run from 0x24F00000.

 

[Supster131]

I just got chainloading Decrypt9 (or whatever arm9 payload) to work directly from AuRei. However, it's not very comfortable/useful: as AuReiNand is a normal brahma payload, it's running from 0x23F00000, however this is the same address other brahma payloads (like D9) use. So I can't overwrite AuRei while it's in memory I had to recompile D9 to run from 0x24F00000.

You mean, like on 10.6?

Any test builds?

 

[Aurora Wright]

You mean, like on 10.6?

Any test builds?

No, I mean that you hold L+R on boot and it boots an "arm9payload.bin" file from SD instead of the CFW. But as I said, you'd need to recompile every arm9 payload to use it with this...

 

[Supster131]

No, I mean that you hold L+R on boot and it boots an "arm9payload.bin" file from SD instead of the CFW. But as I said, you'd need to recompile every arm9 payload to use it with this...

Shouldn't too big of a hassle (for the end user), right?

D9's probably the most useful one, maybe include it with aureinand?

 

[Bu2d85]

No, I mean that you hold L+R on boot and it boots an "arm9payload.bin" file from SD instead of the CFW. But as I said, you'd need to recompile every arm9 payload to use it with this...

It sounds like you're building a boot manager.

 

[Aurora Wright]

Shouldn't too big of a hassle (for the end user), right?

D9's probably the most useful one, maybe include it with aureinand?

I worked around it now. Basically I compiled a barebones 7 KB loader (which I put in rei/loader.bin) which runs from 0x24F00000 and its sole purpose is loading the real payload (in this case, D9) to 0x23F00000.
So aurei loads it to 0x24F00000 and jumps to it, and it loads the arm9 payload to 0x23F00000 and jumps to it (a bit convoluted, but works).

 

[DocKlokMan]

I worked around it now. Basically I compiled a barebones 7 KB loader (which I put in rei/loader.bin) which runs from 0x24F00000 and its sole purpose is loading the real payload (in this case, D9) to 0x23F00000.
So aurei loads it to 0x24F00000 and jumps to it, and it loads the arm9 payload to 0x23F00000 and jumps to it (a bit convoluted, but works).

That's great! I've been postponing updating my A9LH and AuReiNAND for something just like this. Will I need the A9LH screen-init update to make use of this new feature?

 

[Aurora Wright]

That's great! I've been postponing updating my A9LH and AuReiNAND for something just like this. Will I need the A9LH screen-init update to make use of this new feature?

If you want to run official Decrypt9 releases, yes. Currently I don't have screen init in A9LH itself, I bundled it into D9 itself.

 

[DocKlokMan]

If you want to run official Decrypt9 releases, yes. Currently I don't have screen init in A9LH itself, I bundled it into D9 itself.

See, this is how I think it should have been done. Instead of having screen init on boot up causing issues with Stable 3D and flickering it should just be in each A9LH compatible homebrew. Since you needed to add the screen init into D9 then what's the harm of changing the offset? You'd need a special build anyway. In your latest solution, could you implement screen init into the loader.bin instead?

 

[Supster131]

I worked around it now. Basically I compiled a barebones 7 KB loader (which I put in rei/loader.bin) which runs from 0x24F00000 and its sole purpose is loading the real payload (in this case, D9) to 0x23F00000.
So aurei loads it to 0x24F00000 and jumps to it, and it loads the arm9 payload to 0x23F00000 and jumps to it (a bit convoluted, but works).

Think you can share that build of yours?

Also, perhaps you can make another branch on your github for testing purposes? Things that aren't ready for prime time, but would help if people tried it out and gave feedback?

 

[Aurora Wright]

http://www44.zippyshare.com/v/qy7ZnEC5/file.html
Test build! Use the included arm9 payload only if you don't have A9LH screen init (that's the only change). Else use official D9.
Not a full build, replace/add files as needed. L+R chainloads the arm9payload.bin.

 

[Supster131]

http://www44.zippyshare.com/v/qy7ZnEC5/file.html
Test build! Use the included arm9 payload only if you don't have A9LH screen init (that's the only change). Else use official D9.
Not a full build, replace/add files as needed. L+R chainloads the arm9payload.bin.

Works!

 

[Svaethier]

yep it works

 

[dsoldier]

http://www44.zippyshare.com/v/qy7ZnEC5/file.html
Test build! Use the included arm9 payload only if you don't have A9LH screen init (that's the only change). Else use official D9.
Not a full build, replace/add files as needed. L+R chainloads the arm9payload.bin.

nice

 

[democracy]

Working great here Aurora, but the other boot option (L or R) are not working in the test build.

This is a pretty sweet cfw, thank you