Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[DJ91990]

Ok! That's it! I give up!

I have tied everything!

*Having my system update via System Update
*Manually downloading the TWL_FIRM files and installing them with FBI
*Trying the Dev Build of Luma
*System Format
*Patching ARM9LOADERHAX.bin
*Extracting TWLN.bin with GodMode9 from my oldest SYSNAND Backup and restoring it with Decrypt9.

The following works:
Installed .cias
Out-of-region .cias
GBA .cias
Super Smash Bros 4 3DS

The following doesn't work:
DS Wi-Fi Settings
DS Download Play
DS Games
DSi Ware

When I load anything to do with DS, it hangs on a black screen. Home menu music can still be heard.

If I do a NAND restore to BEFORE I had Arm9LoaderHax would it brick the system?
Someone mentioned getting the TWLN partition. How do I go about doing that? I still have the OTP.bin, and sysNAND_original.bin * sha files. Is there some way to extract the TWLN partition from any of those and restore it?

 

[Februarysn0w]

nop

 

[Favna]

Ok! That's it! I give up!

I have tied everything!

*Having my system update via System Update
*Manually downloading the TWL_FIRM files and installing them with FBI
*Trying the Dev Build of Luma
*System Format
*Patching ARM9LOADERHAX.bin
*Extracting TWLN.bin with GodMode9 from my oldest SYSNAND Backup and restoring it with Decrypt9.

The following works:
Installed .cias
Out-of-region .cias
GBA .cias
Super Smash Bros 4 3DS

The following doesn't work:
DS Wi-Fi Settings
DS Download Play
DS Games
DSi Ware

When I load anything to do with DS, it hangs on a black screen. Home menu music can still be heard.

If I do a NAND restore to BEFORE I had Arm9LoaderHax would it brick the system?
Someone mentioned getting the TWLN partition. How do I go about doing that? I still have the OTP.bin, and sysNAND_original.bin * sha files. Is there some way to extract the TWLN partition from any of those and restore it?

Sorta jumping in here but are you using any bootloader other than Luma's own chainloader? If not then you don't need to do the patchchanging. Furthermore resetting to stock TWL_FIRM only requires you to uninstall and reinstall 0004013820000102. Aforementioned 0004013820000202 if AGB_FIRM for GBA compatibility.

Did DS games *ever* work since installing A9LH? Because if they did you could make a backup of your current ticket.db and title.db etc (the list of files from plai's part 5 step 1 guide) then restore to the first backup you made after installing A9LH.

 

[EmperorOfCanada]

Ok! That's it! I give up!

I have tied everything!

*Having my system update via System Update
*Manually downloading the TWL_FIRM files and installing them with FBI
*Trying the Dev Build of Luma
*System Format
*Patching ARM9LOADERHAX.bin
*Extracting TWLN.bin with GodMode9 from my oldest SYSNAND Backup and restoring it with Decrypt9.

The following works:
Installed .cias
Out-of-region .cias
GBA .cias
Super Smash Bros 4 3DS

The following doesn't work:
DS Wi-Fi Settings
DS Download Play
DS Games
DSi Ware

When I load anything to do with DS, it hangs on a black screen. Home menu music can still be heard.

If I do a NAND restore to BEFORE I had Arm9LoaderHax would it brick the system?
Someone mentioned getting the TWLN partition. How do I go about doing that? I still have the OTP.bin, and sysNAND_original.bin * sha files. Is there some way to extract the TWLN partition from any of those and restore it?

Use hourglass9 and try restoring to sysnand_original (or sysnand.bin)

 

[9thSage]

Someone mentioned getting the TWLN partition. How do I go about doing that? I still have the OTP.bin, and sysNAND_original.bin * sha files. Is there some way to extract the TWLN partition from any of those and restore it?

One thing you could do if you wanted to try just restoring that TWLN partition is to make a back up of your current sysNAND. Restore the original (you can do this while preserving a9lh, which is what I'd recommend) to it and then use Decrypt9 to extract the TWLN partition. Restore the backup of the current sysNAND. Then have Decrypt9 insert that TWLN partition. It would take some time, but it wouldn't be very difficult at least.

There might be a way to do it on your computer as well with the proper keys and such, but I'm honestly not sure.

 

[Kazuma77]

Ok! That's it! I give up!

I have tied everything!

*Having my system update via System Update
*Manually downloading the TWL_FIRM files and installing them with FBI
*Trying the Dev Build of Luma
*System Format
*Patching ARM9LOADERHAX.bin
*Extracting TWLN.bin with GodMode9 from my oldest SYSNAND Backup and restoring it with Decrypt9.

The following works:
Installed .cias
Out-of-region .cias
GBA .cias
Super Smash Bros 4 3DS

The following doesn't work:
DS Wi-Fi Settings
DS Download Play
DS Games
DSi Ware

When I load anything to do with DS, it hangs on a black screen. Home menu music can still be heard.

If I do a NAND restore to BEFORE I had Arm9LoaderHax would it brick the system?
Someone mentioned getting the TWLN partition. How do I go about doing that? I still have the OTP.bin, and sysNAND_original.bin * sha files. Is there some way to extract the TWLN partition from any of those and restore it?

Restoring a pre-A9LH FW SysNAND dump to SysNAND should not brick your system (just avoid restoring an EmuNAND dump to SysNAND, that tends to brick systems). However, you might want to try it with the "keep a9lh" option, since that will allow you to keep A9LH, and see if that works first. Keeping A9LH should not prevent a good TWLN partition from functioning, after all. But if it doesn't work, you can try restoring it normally. You can mount the sysNAND_original.bin with GodMode9 to extract the TWLN.bin through the virtual file system. After mounting, it takes you back to the root, then you go to "IMGNAND VIRTUAL" and copy the twln.bin to the SD card (for good measure, you might do twlp.bin as well, though that really shouldn't have anything to do with primary DS functionality, since all it does is store photos). You could also restore "sysNAND_original.bin" using the "keep A9LH" option in Decrypt9, then extract the TWLN partition using Decrypt9 (only if you can bring up DS wifi settings after the restore though, otherwise, there's no point). It almost has to be a messed up TWLN partition if you can't even get the DS wifi settings to show up. I would think there would be at least one good backup, though. Especially with the A9LH installation procedure having you make so many of them.

Your problem is definitely unusual. I've not had any problems with DSiWare, or even my old Acekard 2i, on any of my systems. And I'm just running the regular stable release. I do have an "AIO A9LH Configurations" package on the iso site if you want to try other CFWs just to be sure it's not an issue with Luma. It seems extremely unlikely, but you might as well rule it out. Also, Corbenik and Cakes do load external copies of the TWL firmware, so they might get some things working, even if using them probably won't actually solve the underlying problem. I guess it's possible that the TWL part of the NAND has just failed (I would expect there to be an error when restoring the TWLN partition if that was the case, though). I'm not sure what to tell you. I've messed up my TWLN partition before, and the result is exactly what you describe. However, restoring a NAND backup has always fixed it for me.

 

[EmperorOfCanada]

Restoring a pre-A9LH FW SysNAND dump to SysNAND should not brick your system (just avoid restoring an EmuNAND dump to SysNAND, that tends to brick systems). However, you might want to try it with the "keep a9lh" option, since that will allow you to keep A9LH, and see if that works first. Keeping A9LH should not prevent a good TWLN partition from functioning, after all. But if it doesn't work, you can try restoring it normally. You can mount the sysNAND_original.bin with GodMode9 to extract the TWLN.bin through the virtual file system (after mounting, it takes you back to the root, then you go to "IMGNAND VIRTUAL" and copy the twln.bin to the SD card (for good measure, you might do twlp.bin as well, though that really shouldn't have anything to do with primary DS functionality, since all it does is store pictures). You could also restore "sysNAND_original.bin" using the "keep A9LH" option in Decrypt9, then extract the partition (only if you can bring up DS wifi settings after the restore though, otherwise, there's no point). It almost has to be a messed up TWLN partition if you can't even get the DS wifi settings to show up. I would think there would be at least one good backup, though. Especially with the A9LH installation procedure having you make so many of them.

Your problem is definitely unusual. I've not had any problems with DSiWare, or even my old Acekard 2i, on any of my systems. And I'm just running the regular stable release. I do have an "AIO A9LH Configurations" package on the iso site if you want to try other CFWs just to be sure it's not an issue with Luma. It seems extremely unlikely, but you might as well rule it out (Corbenik and Cakes do load external copies of the TWL firmware, so they might get some things working, even if using them probably won't actually solve the underlying problem). I guess it's possible that the TWL part of the NAND has just failed (I would expect there to be an error when restoring the TWLN partition if that was the case, though). I'm not sure what to tell you. I've messed up my TWLN partition before, and the result is exactly what you describe. However, restoring a NAND backup has always fixed it for me.

Why would an emunand dump brick a system? Plaicect guide makes you restore an emunand backup, I've never heard of anyone having issue?

 

[Kazuma77]

Why would an emunand dump brick a system? Plaicect guide makes you restore an emunand backup, I've never heard of anyone having issue?

AFTER you have A9LH installed. If you restored your EmuNAND to SysNAND before installing A9LH, or without the "keep a9lh" option checked, you would more likely than not brick your system. Trust me. I've done it. There's a reason I've got a red and black unit with a hard mod -- trying to restore an EmuNAND to SysNAND, and getting the black screen. Just don't do it unless said EmuNAND has never been updated.

 

[ihaveahax]

AFTER you have A9LH installed. If you restored your EmuNAND to SysNAND before installing A9LH, or without the "keep a9lh" option checked, you would more likely than not brick your system. Trust me. I've done it. There's a reason I've got a red and black unit with a hard mod -- trying to restore an EmuNAND to SysNAND, and getting the black screen. Just don't do it unless said EmuNAND has never been updated.

this is one reason Hourglass9 is used to restore sysnand now, it makes it impossible to accidentally overwrite arm9loaderhax when flashing sysnand.

 

[EmperorOfCanada]

AFTER you have A9LH installed. If you restored your EmuNAND to SysNAND before installing A9LH, or without the "keep a9lh" option checked, you would more likely than not brick your system. Trust me. I've done it. There's a reason I've got a red and black unit with a hard mod -- trying to restore an EmuNAND to SysNAND, and getting the black screen. Just don't do it unless said EmuNAND has never been updated.

Right but he has a9lh, so did you mean avoid restoring pre a9lh emunand (without keep a9lh) option then? Anyways, thanks for info

 

[Kazuma77]

this is one reason Hourglass9 is used to restore sysnand now, it makes it impossible to accidentally overwrite arm9loaderhax when flashing sysnand.

Is there really any reason to be using Hourglass9? I had a look at it. It just looked like a stripped down copy of Decrypt9, so I passed on it. I don't need to be protected from myself. I can't see any use for SafeMode9 either. GodMode9 asks if you're sure even more times than a Micro$oft app before enabling SysNAND writing. And it's not like I'd let a kid run either one (a wiped SD card still sucks).

Right but he has a9lh, so did you mean avoid restoring pre a9lh emunand (without keep a9lh) option then? Anyways, thanks for info

Yeah, that's exactly what I meant.

 

[ihaveahax]

Is there really any reason to be using Hourglass9? I had a look at it. It just looked like a stripped down copy of Decrypt9, so I passed on it. I don't need to be protected from myself. I can't see any use for SafeMode9 either. GodMode9 asks if you're sure even more times than a Micro$oft app before enabling SysNAND writing. And it's not like I'd let a kid run either one (a wiped SD card still sucks).

because most people don't need/shouldn't have all the features of Decrypt9, and also one too many reports of people accidentally not using "keep a9lh". also, Plailect's guide does include Decrypt9 as an alternate payload replacing Uncart, due to being able to dump game cards. you probably don't need to be protected from yourself but others do.

 

[MakkipMaster]

Hi everyone, I have a question, my apologies if it's been asked before,

I have an N3DS EMUnand on 9.2 firmware, with Luma3DS as my CFW. If I try to update to the latest firmware using Luma, will everything turn out fine? Anything I must do before trying it?

Thank you!

 

[EmperorOfCanada]

Hi everyone, I have a question, my apologies if it's been asked before,

I have an N3DS EMUnand on 9.2 firmware, with Luma3DS as my CFW. If I try to update to the latest firmware using Luma, will everything turn out fine? Anything I must do before trying it?

Thank you!

As long as you are updating your emunand, yeah you're fine

 

[MakkipMaster]

As long as you are updating your emunand, yeah you're fine

Thank you! Everything worked perfectly!

 

[Kazuma77]

because most people don't need/shouldn't have all the features of Decrypt9, and also one too many reports of people accidentally not using "keep a9lh". also, Plailect's guide does include Decrypt9 as an alternate payload replacing Uncart, due to being able to dump game cards. you probably don't need to be protected from yourself but others do.

You have a point. I can see it being good for a guide. But if you've seen my setup, you know part of my problem -- I have no hotkeys left. It would have to go on my CBM9 "Apps" menu. Unless I moved EmuNAND9 to said menu. Now there's a thought. Then again, maybe not a good one. If GW does withdraw their SysNAND support, cloning SysNAND to EmuNAND would become a frequent activity for many users.

 

[ihaveahax]

You have a point. I can see it being good for a guide. But if you've seen my setup, you know part of my problem -- I have no hotkeys left. It would have to go on my CBM9 "Apps" menu. Unless I moved EmuNAND9 to said menu. Now there's a thought. Then again, maybe not a good one. If GW does withdraw their SysNAND support, cloning SysNAND to EmuNAND would become a frequent activity for many users.

many are already moving to sysnand though? as far as I know, Gateway is the main reason why some users don't stop using emunand though, because GW is showing that they don't want to support sysnand by not blocking FIRM partition writes.

Hourglass9 is not for everyone, much like Decrypt9 is not for everyone. everything Hourglass9 does, Decrypt9 already has. it's just much simpler and safer for those who aren't entirely sure about what they're doing/etc.

 

[Temptress Cerise]

because most people don't need/shouldn't have all the features of Decrypt9, and also one too many reports of people accidentally not using "keep a9lh". also, Plailect's guide does include Decrypt9 as an alternate payload replacing Uncart, due to being able to dump game cards. you probably don't need to be protected from yourself but others do.

Haha, and then those same people blamed the guide, and not their lack of reading and choosing the correct option.

Any advance user can get rid of Hourglass9 if they don't need it, there's nothing stopping any advance and knowledgeable user from swapping out all the recommend hotkeys for stuff they want or for a BootLoader they want, or for a CFW they like.

 

[Orkna]

i used Hourglass9 to backup my emunands and restore them as sysnands. Just missing "clone emunand to sysnand" option.
Great tool.

 

[WakingMavUp]

I tried to run my Monster Hunter X Japanese cartridge with Luma3ds, both with Off and Clock mode, but it doesn't work. It stays in the Nintendo 3ds with red waves screen. Some suggestions?
Thanks in advance!

Edit: I've got a EU N3ds