Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Februarysn0w]

Where? On sysNAND?

both nand. because you know I have updated sysnand and emunand and I want to have a ntr. so using ntr-rei folder's firmware.bin. it's maybe 10.2 firm right?

 

[RayFirefist]

both nand. because you know I have updated sysnand and emunand and I want to have a ntr. so using ntr-rei folder's firmware.bin. it's maybe 10.2 firm right?

Now I really don't know how downgrade NATIVE_FIRM...

 

[Februarysn0w]

Now I really don't know how downgrade NATIVE_FIRM...

ignore my post. it's all bullshit.
my sysnand and emunand firmware is 10.6
firmware.bin is from rei-ntr folder.

 

[Aurora Wright]

The original ReiNand just patches "Ver" when it loads. It's fine on original ReiNand since it can only run emuNand. However it would also patch AuReiNand on sysNand, and I want to have different version strings on Sys/EmuNand.
So I need a way to check if we're actually on EmuNAND OR on SysNAND.

Only have a string on emunand => easy (there's already a function in the code that only gets called when emunand is loaded)
Have different strings on emu/sysnand => less easy, two different threads would be needed (rxtools has a completely different emunand patch which allows them to detect. not sure how to implement that). Sorry but not going to spend time on this as I think it's useless.
Also, you need to find the offsets for the thread for all the involved FIRMs (or find a pattern to locate it).

 

[Deleted member 373223]

i think even having the same in both sysnand/emunand would be useful, just to be sure ar,9loaderhax actually loaded the right stuff and that we can update.

 

[DigitalJosee]

Aurora, Could you implement an "on-the-fly" patch for GBA/DS(i) titles?
Like:

1. Check the Title ID;
2. If it match larger RAM mode games, does nothing;
3. If it isn't match that games, use the AGB reboot mode.

 

[Februarysn0w]

I'm very sorry for these bullshit post. but gba game works fine.

 

[Aurora Wright]

i think even having the same in both sysnand/emunand would be useful, just to be sure ar,9loaderhax actually loaded the right stuff and that we can update.

Do you realize that if SysNAND loaded from a9lh that's a pretty good indicator that this code worked? As there's no cfw-less boot when using a9lh. You can be 100% sure that if you have a9lh, and sysnand boots (with this cfw), you can update.

A proper reboot patch that doesn't make AGB/TWL stuff fail is possible. There's a private one, so I know. But until something is publicly released I'm not a reverse engineer so I can't make one on my own.

 

[Supster131]

I'm very sorry for these bullshit post. but gba game works fine.

oh damn, calling people out!

But yeah, GBA games work fine, they probably need to install the patched AGB_FIRM.

 

[Aurora Wright]

oh damn, calling people out!

But yeah, GBA games work fine, they probably need to install the patched AGB_FIRM.

O3DS users have to deal with the reboot patch.

 

[Zaertix]

O3DS users have to deal with the reboot patch.

AHA that's the problem then!~~~

Thanks, I forgot to mention I was on o3ds LOL <3

 

[Koryushin]

3) On Old3DS, if you're not using the 9.0 FIRM, the FIRM reboot patch is applied by default, to allow games which work in the larger RAM mode (Smash Bros, MH4...) to work. This prevents GBA and DS/DSiWare games from working, however, you can disable the patch by holding A on boot. If you create a "/rei/reversereboot" file, the patch will be disabled unless you hold A (so, the opposite behavior).

 

[shadowofdarkness]

O3DS users have to deal with the reboot patch.

Is that reboot patch for emunand only? I ask because I'm on a O3DS with updated sysnand and have the reverseboot file to make gba/ds work but large RAM games still work fine with no special triggers at boot which if I read correctly shouldn't happen. I just want to know if I can claim having all features working simultaneously as a feature of using a updated sysnand over a emunand.

 

[Aurora Wright]

Is that reboot patch for emunand only? I ask because I'm on a O3DS with updated sysnand and have the reverseboot file to make gba/ds work but large RAM games still work fine with no special triggers at boot which if I read correctly shouldn't happen. I just want to know if I can claim having all features working simultaneously as a feature of using a updated sysnand over a emunand.

reboot patch is applied => GBA/DS/i fail, Smash/MH4 work
reboot patch is not applied => Smash/MH4 fail, GBA/DS/i work

This patch doesn't allow for both things to work at the same time.

 

[jackb994]

reboot patch is applied => GBA/DS/i fail, Smash/MH4 work
reboot patch is not applied => Smash/MH4 work, GBA/DS/i fail

This patch doesn't allow for both things to work at the same time.

So gba/Ds fails either way

 

[PixelBurst]

I'm very sorry for these bullshit post. but gba game works fine.

Is that only for people that have swapped sysnand and emunand? Or does it only work if NANDs are linked? I'm trying to get VC working, but I just get the "error has occured power off" message. I've already installed the patched AGB_Firm.

 

[Aurora Wright]

So gba/Ds fails either way

Sorry I derped, it's that I have enough of people not reading the OP XD

 

[dkabot]

Is that only for people that have swapped sysnand and emunand? Or does it only work if NANDs are linked? I'm trying to get VC working, but I just get the "error has occured power off" message. I've already installed the patched AGB_Firm.

Running from EmuNAND has always required additionally installing the software (but not the FIRM, IIRC) in SysNAND.

 

[PixelBurst]

Running from EmuNAND has always required additionally installing the software (but not the FIRM, IIRC) in SysNAND.

Cheers, new to the scene in general, but have got through most things without asking too many questions - the stuff on AGB_Firm seems to be all over the place with no definitive answers on what to do!

 

[peteruk]

@Aurora Wright

thanks for all your hard work, 3.5.3 is working great