Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[9thSage]

I have used Plailect's guide to update to aureinand initially (CFW with no Emu/RedNAND). I had been keeping it updated with the latest Luma3DS and everything was working alright for a few weeks. As I was installing my converted 3ds dumps to cia with FBI about a week ago, the system all of a sudden lost the ability to install unsigned cia files. Now I can't install old ones which were previously installable. Everything else seems okay.

What could have happened to cause this?

Well, if the stuff you already installed is still there, I wouldn't think it's Luma3DS... (that'd mean the sig patch is working right?)

 

[jimmyleen]

It looks like the new Luma3ds stable update will make the cfw boot 0.25s faster (probably won't make a difference on sysnand), now that is impressive.

 

[Kazuma77]

Hi, I have a problem.

Recently I installed Luma3DS on my classic old 3DS, but when I start the games Monster Hunter 4 Ultimate and Super Smash Bros for 3DS I got a black screen.

I installed the same CIAs games in another 3DS with rxtools, and works fine.

My 3DS with problem: Old 3DS classic EUR, Sysnand 9.2, Emunand 10.7, Luma3DS 5.4, CTRBootManager and SD 32g.

My 3DS without problem: OLD 3DS XL, EUR, Sysnand 9.2, Emunand 10.7, RxTools 3, CTRBootManager and SD 16g.

I found this: Installation and Upgrade · AuroraWright/Luma3DS Wiki
But I dont have a "Luma3DS .bin" on my SD.

I loved using Luma3DS but need a solution to play without problems. Any help?

The name of the file is "arm9loaderhax.bin" by default. You have to do the renaming yourself. If you're a MenuHax straggler, you're using Luma3DS.dat so this should not be an issue. Actually, I'm starting to think the reboot patch is broken in 5.4 for O3DS. Tried it with "a9lh/Luma3DS.bin" and "a9lh\Luma3DS.bin" and even "Luma3DS.bin" without a path, thinking it could be a mistake I made with path changer, but it works fine on an N3DS XL, so that can't be it. DSiWare just doesn't work on an O3DS. @Aurora Wright please look into this. In the meantime, try going back to 5.2 (I initially said 5.3.1, don't do it, because that version appears to corrupt TWL_FIRM -- 5.2 isn't working on the units I tried 5.3.1 with anymore, so, please stay away from it).

UPDATE: Confirmed the corruption. Reinstalled TWL_FIRM and DSiWare is working again in 5.2 on my O3DS XLs. So, if you have an O3DS, you apparently need to revert to 5.2 to get a working reboot patch for big RAM games, GBA, and DSiWare functionality. And for the love of science, avoid 5.3.1 (especially if you don't have a clean copy of TWL_FIRM handy -- just goes to show, you should always backup the latest firmware release with 3DNUS)

 

[pbanj]

I have used Plailect's guide to update to aureinand initially (CFW with no Emu/RedNAND). I had been keeping it updated with the latest Luma3DS and everything was working alright for a few weeks. As I was installing my converted 3ds dumps to cia with FBI about a week ago, the system all of a sudden lost the ability to install unsigned cia files. Now I can't install old ones which were previously installable. Everything else seems okay.

What could have happened to cause this?

Well the fact FBI is able to launch means the sig patches are working so I'm not sure wtf is the issue. Is you sd card full?

 

[astronautlevel]

It looks like the new Luma3ds stable update will make the cfw boot 0.25s faster (probably won't make a difference on sysnand), now that is impressive.

It will make a difference in sysnand

 

[a1user]

I believe I had ran something already installed then to see if it worked, which I -think- it did. What I had done afterwards though, was try to flash a backup of sysNAND-A9LHAX.bin over the sysNAND. It had soft-bricked it but I was able to still enter payloads. About to give up on this 3DS at that point, I deleted everything on the SD card and tried reusing a backup of the entire SD card I made from the time of install. Reflashed again, and that was able to get me back into CFW minus unsigned cia installing ability.

 

[pbanj]

Have you tried a newer build?
http://cloud.tapatalk.com/s/572ea8fb3cb18/arm9loaderhax.zip

Try this build

 

[BabyBichu]

Long time!Bump!

 

[a1user]

Well the fact FBI is able to launch means the sig patches are working so I'm not sure wtf is the issue. Is you sd card full?

Not even close - I have a 128GB formatted with the fat32 64k from the latest emunand9. Also tried with my old 16GB fat32 card (not with the 64k) and installs didn't work either, which leads me to believe its not the SD card.

 

[hacksn5s4]

im trying to use ntr with this cfw but it says unknown firm and i do have the firm file in luma 3ds

 

[astronautlevel]

im trying to use ntr with this cfw but it says unknown firm and i do have the firm file in luma 3ds

If you're using updated sysnand make sure you check the sysnand is updated option

 

[hacksn5s4]

If you're using updated sysnand make sure you check the sysnand is updated option

how do i edit the options

 

[astronautlevel]

how do i edit the options

Hold shift on boot

 

[hacksn5s4]

Hold shift on boot

3ds does not have shift

 

[astronautlevel]

3ds does not have shift

Sorry, I'm tired.

Select

 

[jimmyleen]

It will make a difference in sysnand

*faints*

 

[pbanj]

Not even close - I have a 128GB formatted with the fat32 64k from the latest emunand9. Also tried with my old 16GB fat32 card (not with the 64k) and installs didn't work either, which leads me to believe its not the SD card.

You try the build I posted a couple of posts above urs ?

 

[a1user]

You try the build I posted a couple of posts above urs ?

Just tried it - installed a previous cia, and it worked! Also, seems like it boots faster too as it was stated.

I'll try reinstalling some more cias tonight (time consuming process). If it doesn't work, I'll report back. I thank you for your time sir.

 

[_Vinny_]

The name of the file is "arm9loaderhax.bin" by default. You have to do the renaming yourself. If you're a MenuHax straggler, you're using Luma3DS.dat so this should not be an issue. Actually, I'm starting to think the reboot patch is broken in 5.4 for O3DS. Tried it with "a9lh/Luma3DS.bin" and "a9lh\Luma3DS.bin" and even "Luma3DS.bin" without a path, thinking it could be a mistake I made with path changer, but it works fine on an N3DS XL, so that can't be it. DSiWare just doesn't work on an O3DS. @Aurora Wright please look into this. In the meantime, try going back to 5.2 (I initially said 5.3.1, don't do it, because that version appears to corrupt TWL_FIRM -- 5.2 isn't working on the units I tried 5.3.1 with anymore, so, please stay away from it).

UPDATE: Confirmed the corruption. Reinstalled TWL_FIRM and DSiWare is working again in 5.2 on my O3DS XLs. So, if you have an O3DS, you apparently need to revert to 5.2 to get a working reboot patch for big RAM games, GBA, and DSiWare functionality. And for the love of science, avoid 5.3.1 (especially if you don't have a clean copy of TWL_FIRM handy -- just goes to show, you should always backup the latest firmware release with 3DNUS)

Well, I dont have arm9loaderhax installed. But I have the file arm9loaderhax.bin on my SD, it's fine proceed?

 

[blinky87]

Have the latest Luma3DS with A9LH. Tried a custom boot splash, but it flashed so quickly I barely had time to see it.

Is there a way to make the splash screen stay visible longer, maybe all the way up until the home menu is loaded?