Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[tivu100]

OP or anyone still have the mod of ReiNAND 3.1 version?

 

[Aurora Wright]

OP or anyone still have the mod of ReiNAND 3.1 version?

No point in that. 3.2 only auto-calculates some offsets to patch firm for emunand and has cleaner code.

 

[tivu100]

No point in that. 3.2 only auto-calculates some offsets to patch firm for emunand and has cleaner code.

Please let have have 3.1 version if you can. I need it for O3DS SYSNAND. I have bad boot rate on the 3.2 I boot to ReiNAND and often stuck. I tried Gateway EMUNAND 9tool and Multi NAND tool with same result. Just stupid me deleted it now I can't go back.

 

[Aurora Wright]

Please let have have 3.1 version if you can. I need it for O3DS SYSNAND. I have bad boot rate on the 3.2 I boot to ReiNAND and often stuck. I tried Gateway EMUNAND 9tool and Multi NAND tool with same result. Just stupid me deleted it now I can't go back.

I don't think I have it anymore, but I can tell you it's just bad luck. In this mod the new version is exactly the same but does some math before doing the arm9 exploit. What causes a black screen is an unsuccessful arm11 kernel exploit (before reinand is even started) or an unsuccessful firmlaunchhax (which has always stayed the same in the code).
I use bootctr on both consoles (o3ds xl and n3ds xl) and boot rates are really good. Set a delay of 2500.

 

[ShadowOne333]

I don't think I have it anymore, but I can tell you it's just bad luck. In this mod the new version is exactly the same but does some math before doing the arm9 exploit. What causes a black screen is an unsuccessful arm11 kernel exploit (before reinand is even started) or an unsuccessful firmlaunchhax (which has always stayed the same in the code).
I use bootctr on both consoles (o3ds xl and n3ds xl) and boot rates are really good. Set a delay of 2500.

What changes were done to 3.2b in the official ReiNAND?
And are you going to include the changes made in 3.2b to your MOD?

 

[tivu100]

I don't think I have it anymore, but I can tell you it's just bad luck. In this mod the new version is exactly the same but does some math before doing the arm9 exploit. What causes a black screen is an unsuccessful arm11 kernel exploit (before reinand is even started) or an unsuccessful firmlaunchhax (which has always stayed the same in the code).
I use bootctr on both consoles (o3ds xl and n3ds xl) and boot rates are really good. Set a delay of 2500.

Okay. Please keep an eye out for the 3.1 mod for me. Thanks.

I have this problem for 2 O3DS after update to 3.2b mod. I tried both ctrlbootmanager and bootctrl same result. The counterpart on N3DS works just the same as as 3.1

What changes were done to 3.2b in the official ReiNAND?
And are you going to include the changes made in 3.2b to your MOD?

Hey do you still have the 3.1 mod? Can you back up and give it me please

 

[Aurora Wright]

What changes were done to 3.2b in the official ReiNAND?
And are you going to include the changes made in 3.2b to your MOD?

Auto-calculation of some offsets used to patch firm for emunand (before, the offsets were specified in the code. now it does math to calculate them, or finds them directly in the firmware.bin). Other than that, he made the code look cleaner. All the fixes related to the arm9 thread don't apply as this doesn't have the arm9 thread at all.
I've already included the 3.2b changes since the v3 of this mod.

 

[Supster131]

Any way to improve boot rate when booting into this mod directly from MenuHax? (I have like a 1/5 boot rate on an o3DS).

 

[kiwiis]

Any way to improve boot rate when booting into this mod directly from MenuHax? (I have like a 1/5 boot rate on an o3DS).

Scroll up a bit. Aurora posted some suggestions on how to improve the boot rate.

 

[Supster131]

Scroll up a bit. Aurora posted some suggestions on how to improve the boot rate.

I meant when booting directly into this CFW though, I'd rather not use a boot manager such as bootctr.

 

[tivu100]

I meant when booting directly into this CFW though, I'd rather not use a boot manager such as bootctr.

You can set it to boot directly to ReiNAND but configure the boot.cfg file.

 

[Aurora Wright]

I meant when booting directly into this CFW though, I'd rather not use a boot manager such as bootctr.

A delay is needed to improve boot rates from menuhax. The loader for this is an *untouched* cakebrah + cakehax (so the bootrates should be the same as Cakes). I suppose it's not designed to boot from menuhax, so it doesn't delay boot. You really need to use a boot manager, and after all, bootctr is basically cakebrah (with delay options) + a stripped down hbl.

 

[Aurora Wright]

I meant when booting directly into this CFW though, I'd rather not use a boot manager such as bootctr.

I added a single line of code to the Cakebrah loader to wait for the exact delay I have on bootctr. Could you try this? It's just the .3dsx, not the full reinand package.
http://www21.zippyshare.com/v/svr4PT9j/file.html

 

[The Catboy]

BTW, I second the idea of splitting this and calling it AurNAND!

 

[ShadowOne333]

@Aurora Wright does the link in the opening post have the latest v3.1 changes that you specify at the end of the OP? (the boot halt thing)

 

[Aurora Wright]

@Aurora Wright does the link in the opening post have the latest v3.1 changes that you specify at the end of the OP? (the boot halt thing)

Yeah, there's a changelog at the bottom,

BTW, I second the idea of splitting this and calling it AurNAND!

I don't really think it warrants my name in it After all, it's 99% Rei's code...

 

[The Catboy]

Yeah, there's a changelog at the bottom,

I don't really think it warrants my name in it After all, it's 99% Rei's code...

Yeah, but it would be nice to have some way to distinguish this version from Rei's official version. Maybe call it a "Spin," like "Ubuntu" has "Lubuntu," same code, just tweaked with a different name.

 

[Supster131]

I added a single line of code to the Cakebrah loader to wait for the exact delay I have on bootctr. Could you try this? It's just the .3dsx, not the full reinand package.
http://www21.zippyshare.com/v/svr4PT9j/file.html

Yup, that seemed to do the trick! Thanks! (Tried rebooting it a few times, it worked every time.)

 

[Kazuma77]

I made a NTR compatible build (just v3.1 with changed offsets). This needs 9.6 FIRM on O3DS and 10.2 FIRM on N3DS (NTR doesn't support the 10.2 one on O3DS), so I made a different zip on the iso site. I think some demos need the 10.2 FIRM (I seem to recall that from the cakes thread?) so you risk losing some compatibility

Demos? We don't need no stinking demos. I figured there might have been a problem implementing 10.2 on the O3DS. The Cakes nightlies skipped it after all. Oh well, there's actually room for both versions on my O3DS CBM config. I just have to rename one of the .dat files, and rename firmware files with CTRXplorer before switching. And I already have CTRXplorer on my CBM (useful for swapping FW in Cakes). If someone I mod for brings it up, I'll simply give them the regular one and have them use Cakes for NTR (which for most people I configure to boot straight to EmuNAND). So, no problems here.

Thanks a million times over.

 

[Svaethier]

Yeah, but it would be nice to have some way to distinguish this version from Rei's official version. Maybe call it a "Spin," like "Ubuntu" has "Lubuntu," same code, just tweaked with a different name.

Exactly my point, people can easily get confused between this and the official build.