Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Kazuma77]

Listen, 1F.app is 4.5 FIRM, and Nintendo's code always deletes the *currently used .app/.tmd* when updating. The only way you can have 4.5 FIRM is by downgrading to 4.5 with GW (which doesn't use Nintendo's code, and leaves multiple .app/.tmd files in CTRNAND for all titles). For some reason if you do that and then re-update to 10.7 (say) Nintendo's code is tricked and it won't delete the 4.5 .app, it will only delete the .app of the FIRM you were using prior to the DG.

I actually said 0000000f.app, for TWL_FIRM. It's probably the 4.0 one actually. The fact that I installed that after downgrading also makes it not possible more than one was present on SysNAND. Anyway, one of these old 3DS XLs started on 4.x -- I updated it to 4.5 using SMT IV, so, that's one way to have it without the downgrade. The other, a Zelda unit, I kept the original profile for (for obvious reasons) in EmuNAND. I downgraded after formatting to unlink, therefore, the extra files would have only been in SysNAND (and again, not after installing the 4.0 TWL_FIRM). With any system I downgraded from 9.2, I formatted EmuNAND then unlinked first. No extra files should be in the EmuNAND.

 

[Aurora Wright]

I actually said 0000000f.app, for TWL_FIRM. It's probably the 4.0 one actually. The fact that I installed that after downgrading also makes it not possible more than one was present on SysNAND. Anyway, one of these old 3DS XLs started on 4.x -- I updated it to 4.5 using SMT IV, so, that's one way to have it without the downgrade. The other, a Zelda unit, I kept the original profile for (for obvious reasons) in EmuNAND. I downgraded after formatting to unlink, therefore, the extra files would have only been in SysNAND (and again, not after installing the 4.0 TWL_FIRM). With any system I downgraded from 9.2, I formatted EmuNAND then unlinked first. No extra files should be in the EmuNAND.

It's starting to get exhausting. If you only use Nintendo code (updating from carts/online/whatever) you will NEVER EVER have two .app files. Is that much clear? The only way to have them is Gateway downgrading messing with things and having Nintendo's code malfunction.
And as I said, no formatting/update fixes it. It's there to stay unless you go and fix it the way I mentioned.
I won't reply about this anymore.

 

[HenryLeonheart]

Build 1 was fine
Shows and looks fine, goes away and then boots the home menu


Build 2 has the line
It comes up fine but then transitions(no flashing) into it looking like shit + the line

I can confirm the same results.

 

[Kazuma77]

It's starting to get exhausting. If you only use Nintendo code (updating from carts/online/whatever) you will NEVER EVER have two .app files. Is that much clear? The only way to have them is Gateway downgrading messing with things and having Nintendo's code malfunction.
And as I said, no formatting/update fixes it. It's there to stay unless you go and fix it the way I mentioned.
I won't reply about this anymore.

Well, apparently I found a second way with that one unit. There was no downgrade on the EmuNAND profile (let's call that profile 1) and I had downgraded TWL_FIRM to 4.0 using DevMenu on the unlinked SysNAND (which is on what we'll call profile 2). Neither profile 1 nor 2 should therefore have had more than one file. If it's any consolation, it's only happened to one of three units I've checked, but I can pretty much rule out the downgrade on all three. Furthermore, TWL_FIRM got an update with 4.4, so it should be a different file if it was from the downgrade. And I would think all of them would get the new file at least, but two of them only had the old file. That was most of the problem.

Anyway, I thought you were referring me to the part that talked about patched firmware. I see that's not the case now. Still, GW could not have even possibly been the issue with two of the three, because they only had one file -- the old one. My mistake was thinking I had killed the old TWL_FIRM by overwriting it with EmuNAND, but it somehow stayed. How is irrelevant at this point. The fact is, two of them only had the old file. And that can only be because D9 didn't overwrite it. I can understand if you want to eliminate support for the old TWL_NAND. But please document that you're doing so, and that overwriting SysNAND with EmuNAND may not necessarily overwrite all of the old files.

 

[pbanj]

@astronautlevel do you have the latest cia ver of your updater handy i cant seem to find where i put the damn file

 

[astronautlevel]

@astronautlevel do you have the latest cia ver of your updater handy i cant seem to find where i put the damn file

https://github.com/astronautlevel2/StarUpdater/releases

 

[pbanj]

https://github.com/astronautlevel2/StarUpdater/releases

bookmarked thanks. google kept giving me reddit threads to other peoples shit/ your comments on reddit.

 

[Ordim3n]

Help, ntr don't want to boot with luma 3ds.

 

[ihaveahax]

Help, ntr don't want to boot with luma 3ds.

i'm going to assume you are getting unknown firmware version. the wiki gives you a link to the NTR firmware.bin you need to use if you want NTRCFW.

https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-Upgrade#installing

 

[pbanj]

read the damn wiki

 

[Ordim3n]

read the damn wiki

I read the faq

 

[Cortles]

I can't load some apps launched via the homebrew launcher cia that I installed with FBI. Can launch stuff like custom theme manager but not things like decrypt9 or OTPhelper (yet I can load decrypt9 via the A9LH payload). what do?

Spoiler

@pbanj

 

[pbanj]

I can't load some apps launched via the homebrew launcher cia that I installed with FBI. Can launch stuff like custom theme manager but not things like decrypt9 or OTPhelper (yet I can load decrypt9 via the A9LH payload). what do?

Spoiler

@pbanj

that is normal. also there is cias for chmm2, ftp, and fbi

 

[TuxSH]

I read the faq

Use @Shadowtrance 's BootNTR build as well.

 

[Cortles]

that is normal. also there is cias for chmm2, ftp, and fbi

That's what I like to hear. You're a good pal, sandwichman.

Another question out of curiosity then: why can some apps be loaded and others can't? I'm gonna pretend to be smart and say decrypt and emunand not loading is because of the payloads.

Thanks guys for the responses

 

[Ordim3n]

Use @Shadowtrance 's BootNTR build as well.

I use BootNTR primary for screen mirroring

 

[Ordim3n]

I can't load some apps launched via the homebrew launcher cia that I installed with FBI. Can launch stuff like custom theme manager but not things like decrypt9 or OTPhelper (yet I can load decrypt9 via the A9LH payload). what do?

Spoiler

@pbanj

Decrypt9 and OTPhelper uses arm9, but arm9loaderhax already uses arm9 so it can't be launched

 

[pbanj]

That's what I like to hear. You're a good pal, sandwichman.

Another question out of curiosity then: why can some apps be loaded and others can't? I'm gonna pretend to be smart and say decrypt and emunand not loading is because of the payloads.

they need 9.2/9.2(9.0?) firm to work. thats why some dont work

--------------------- MERGED ---------------------------

Decrypt9 and OTPhelper uses arm9, but arm9loaderhax already uses arm9 so it can't be launched

WRONG lol its a firm issue

 

[astronautlevel]

@TuxSH has just added a feature to the latest commit that allows for longer lasting splash screens (it's also customisable if you're willing to build the source yourself). The splash screen should now last 3 seconds, by popular demand.

If you want to test out this new feature, use the latest commit on my site:

http://astronautlevel2.github.io/Luma3DS

It would be helpful to him if you guys were able to test it

 

[pbanj]

@TuxSH has just added a feature to the latest commit that allows for longer lasting splash screens (it's also customisable if you're willing to build the source yourself). The splash screen should now last 3 seconds, by popular demand.

If you want to test out this new feature, use the latest commit on my site:

http://astronautlevel2.github.io/Luma3DS

It would be helpful to him if you guys were able to test it

/me loads up luma updater