Hacking Luma3DS some question, please don't kill my thread this time :P

[Naxster]

Well guys... I don't know what the hell happened with my thread, but I read some of the posts this morning, and saw people roasting each other for something small...

What the hell happened?

But dammit guys I didn't have time to read some of your REAL answers for my questions

@Veho if it's possible could you please open the thread

If not, I have some more questions regarding "If Luma3DS is worth it" after it got deleted (I have no idea what happened in there) after reading some answers I reacted that some of you wrote that update you SysNAND, isn't that a bad thing?
Let say that I want to return to firmware 9.2 won't that be possible? (Just in case)

Also I know that some features (at least with RxTools) only work if you have SysNAND 9.2 (for instance menuhaxboot).. If you go above 9.2 it won't work...

And also won't my CFW disappear if I update my SysNAND to 11.0 or whatever, even if I use Luma3DS?
That's why I liked to have EmuNAND since it doesn't have to do anything with my SysNAND

 

[pbanj]

Well guys... I don't know what the hell happened with my thread, but I read some of the posts this morning, and saw people roasting each other for something small...

What the hell happened?

But dammit guys I didn't have time to read some of your REAL answers for my questions

@Veho if it's possible could you please open the thread

If not, I have some more questions regarding "If Luma3DS is worth it" after it got deleted (I have no idea what happened in there) after reading some answers I reacted that some of you wrote that update you SysNAND, isn't that a bad thing?
Let say that I want to return to firmware 9.2 won't that be possible? (Just in case)

Also I know that some features (at least with RxTools) only work if you have SysNAND 9.2 (for instance menuhaxboot).. If you go above 9.2 it won't work...

And also won't my CFW disappear if I update my SysNAND to 11.0 or whatever, even if I use Luma3DS?
That's why I liked to have EmuNAND since it doesn't have to do anything with my SysNAND

With a9lh it allows you to have an updated sysnand. So once you have it all set up with a9lh and luma you can update the sysnand. But that is only with a9lh. If you use say menuhax and luma you have to have an Emunand to be able to be on the newest firmware as your sysnand has to stay at 9.2

 

[Naxster]

With a9lh it allows you to have an updated sysnand. So once you have it all set up with a9lh and luma you can update the sysnand. But that is only with a9lh. If you use say menuhax and luma you have to have an Emunand to be able to be on the newest firmware as your sysnand has to stay at 9.2

But let say that i want at some point return to 9.2 if I update my SysNAND with a9lh, will that be possible?
Also that's the benefits to update SysNAND and not having a EmuNAND (beside it takes up a lot of storage)??

 

[Deleted member 366698]

But let say that i want at some point return to 9.2 if I update my SysNAND with a9lh, will that be possible?
Also that's the benefits to update SysNAND and not having a EmuNAND (beside it takes up a lot of storage)??

Yes you can return if you make a 9.2 nand backup and restore it with hourglass9 via a9lh keeping a9lh or with decrypt9 if you want to remove a9lh
And the benefits are way faster boot time and boot rate, brick protection , easier SD switch and the space save

 

[RyDog]

Follow this guide to install arm9loaderhax https://github.com/Plailect/Guide/wiki
With it, you can run cfw on boot on your sysNAND.

 

[pbanj]

But let say that i want at some point return to 9.2 if I update my SysNAND with a9lh, will that be possible?
Also that's the benefits to update SysNAND and not having a EmuNAND (beside it takes up a lot of storage)??

Yes you could return to 9.2 if you wanted. Emunands entire reason to be was so you could have Cfw and an updated nand because there were no exploits at the time that would allow for an updated sysnand. A9lh removes that need. With no Emunand you have the saved space it would have taken up, also GBA/dsiware games don't have to be installed twice either

 

[Wuigi]

SafeA9LHInstaller has an option to uninstall a9lh, but you need to be on 9.2 or lower as the developers thought of people that might be out of luck otherwise.

 

[Inochi.no.Zenmai]

after reading some answers I reacted that some of you wrote that update you SysNAND, isn't that a bad thing?
Let say that I want to return to firmware 9.2 won't that be possible? (Just in case)

Also I know that some features (at least with RxTools) only work if you have SysNAND 9.2 (for instance menuhaxboot).. If you go above 9.2 it won't work...

And also won't my CFW disappear if I update my SysNAND to 11.0 or whatever, even if I use Luma3DS?
That's why I liked to have EmuNAND since it doesn't have to do anything with my SysNAND

1. If you do A9LH, you will have to make a SysNAND backup before you start. You can always use that to restore your system to 9.2 and also delete A9LH from your system if you restore it with the correct option on Decrypt9.

2. Nothing will disappear from your EmuNAND. You'll keep your savefiles and your games. There's no problem with updating the SysNAND as A9LH has various layers of protection, and in fact, the exploit is active before the firmware loads.

SafeA9LHInstaller has an option to uninstall a9lh, but you need to be on 9.2 or lower as the developers thought of people that might be out of luck otherwise.

10.7 or lower actually. As these versions are easily downgradable. Aurora just restricted uninstalling for 11.x versions onwards as they added the minimum version titlelist that makes impossible to downgrade with ARM11 kernel exploits.

 

[Wuigi]

Well I once didn't know that one has to format the 3DS twice before downgrading so I was lucky I made a nand backup via hardmod before so I could restore it.
It's pretty easy and safe from 10.7, but I would like to play it safe and choose 9.2 as firmware of choice for a9lh stuff.
And also pretty tedious until the exploit finally works at times.

 

[Naxster]

Isnt it better if I just follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

I don't want to mess around with the SysNAND
I don't really care about the boot time :/

 

[Kwartel]

Isnt it better if I just follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

I don't want to mess around with the SysNAND
I don't really care about the boot time :/

If you don't feel safe doing a9hl, you should. There's no reason to feel unsafe about the a9hl, but each his cup of tea.

 

[Naxster]

If you don't feel safe doing a9hl, you should. There's no reason to feel unsafe about the a9hl, but each his cup of tea.

Thanks mate!
Will it almost be the same as if I chose the a9hl method?

 

[Kwartel]

Thanks mate!
Will it almost be the same as if I chose the a9hl method?

Yeah. It's effectively the same. a9hl is faster and it's easier to work with backups and all. Once you've a9hl, you're practically brick proof.

 

[Naxster]

Yeah. It's effectively the same. a9hl is faster and it's easier to work with backups and all. Once you've a9hl, you're practically brick proof.

Things like that really want me to get the a9hl... But I'm not sure if I want to mess around with the SysNAND

One question though, I do know that you need to open "LumaUpdater" and update it first before you update the system..
But let say that I use EmuNAND and I forgot to open and update "LumaUpdate" and just update the EmuNAND directly in settings, will that ruin the 2DS??
Because in RxTools all I have to do is to just enter settings and from there just update the system without having to open a second program

 

[DocKlokMan]

I'm upset my post was deleted instead of the thread simply locked, but all well. Let's see if I can clear this up for you.

@theasker:

The 9.2 sysNAND had a historical use for two reasons: 1. It was a ARM9 exploitable entry point to allow us to disable signature verification and load CFW. 2. A safety net incase something happens while messing around with emuNAND that we could use to boot Decrypt9 and load backups with.

With A9LH, we install ARM9 accessibility straight into the FIRM, allowing use to load homebrew (including Decrypt9) before the system firmware even launches. Because of this we can now signature patch sysNAND and still have a safety net. It also comes with the pros of having faster and more reliable boot time along with only needing to manage one NAND, which is much easier and safer when it comes to things like backups, accidental updates, and GBA virtual console games.

In the last 4 days, installing A9LH on a new 3DS XL is as simple as running a homebrew from your 9.2 sysNAND. No need to downgrade to 2.1 anymore. Once it's installed, sysNAND will now be the CFW and you can even clone your emuNAND to sysNAND so you keep all your games and save data. You can then remove emuNAND from your memory card, reclaiming that extra 1GB of space. Never again will you need to worry about accidentally updating sysNAND, installing GBA on both NANDs or remembering to dump emuNAND to move to a bigger memory card. And if something fudges up, you can use Luma3DS to boot Hourglass9 by holding Start while powering on and restore a backup.

Luma Updater is just to ensure you have the latest version of Luma3DS, you can also manually update by copying the new updated files to your SD card. Unlike RxTools, Luma3DS is actively being updated with new features. You still update your 3DS through Settings like with RxTools.

EDIT: Odd, I thought I read you had a new 3DS XL, but I may have gotten confused. 2DS still requires a downgrade to 2.1, but its safe and takes about 10 minutes to do before you go back to 9.2 and proceed with the emuNAND to sysNAND swap.

 

[Naxster]

I'm upset my post was deleted instead of the thread simply locked, but all well. Let's see if I can clear this up for you.

@theasker:

The 9.2 sysNAND had a historical use for two reasons: 1. It was a ARM9 exploitable entry point to allow us to disable signature verification and load CFW. 2. A safety net incase something happens while messing around with emuNAND that we could use to boot Decrypt9 and load backups with.

With A9LH, we install ARM9 accessibility straight into the FIRM, allowing use to load homebrew (including Decrypt9) before the system firmware even launches. Because of this we can now signature patch sysNAND and still have a safety net. It also comes with the pros of having faster and more reliable boot time along with only needing to manage one NAND, which is much easier and safer when it comes to things like backups, accidental updates, and GBA virtual console games.

In the last 4 days, installing A9LH on a new 3DS XL is as simple as running a homebrew from your 9.2 sysNAND. No need to downgrade to 2.1 anymore. Once it's installed, sysNAND will now be the CFW and you can even clone your emuNAND to sysNAND so you keep all your games and save data. You can then remove emuNAND from your memory card, reclaiming that extra 1GB of space. Never again will you need to worry about accidentally updating sysNAND, installing GBA on both NANDs or remembering to dump emuNAND to move to a bigger memory card. And if something fudges up, you can use Luma3DS to boot Hourglass9 by holding Start while powering on and restore a backup.

Luma Updater is just to ensure you have the latest version of Luma3DS, you can also manually update by copying the new updated files to your SD card. Unlike RxTools, Luma3DS is actively being updated with new features. You still update your 3DS through Settings like with RxTools.

EDIT: Odd, I thought I read you had a new 3DS XL, but I may have gotten confused. 2DS still requires a downgrade to 2.1, but its safe and takes about 10 minutes to do before you go back to 9.2 and proceed with the emuNAND to sysNAND swap.

Wow thank you for the information!
It helped a lot!

Well the space is not an issue, since I won't have that many games in my 2DS, so far it has been working great with 32GB

I have one question, do I really need to downgrade to 2.1?
I'm going to follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

And it doesn't tell me to downgrade to 2.1 at all

 

[JCCG1989]

Wow thank you for the information!
It helped a lot!

Well the space is not an issue, since I won't have that many games in my 2DS, so far it has been working great with 32GB

I have one question, do I really need to downgrade to 2.1?
I'm going to follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

And it doesn't tell me to downgrade to 2.1 at all

I think it is because its using Menuhax, forget about it, use arm9lh please, it will be easier and more protected.

 

[DocKlokMan]

Th

Wow thank you for the information!
It helped a lot!

Well the space is not an issue, since I won't have that many games in my 2DS, so far it has been working great with 32GB

I have one question, do I really need to downgrade to 2.1?
I'm going to follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

And it doesn't tell me to downgrade to 2.1 at all

That guide does not install A9LH, so you'd have the same setup you have right now with sysNAND 9.2 and emuNAND 11.1 but you'd be booting your emuNAND with Luma3DS rather than RxTools. Everything else would be pretty much identical to what you're doing now. All the changes would be behind the scenes and you'd likely notice nothing different. You don't need a tutorial for this since you're already on sysNAND 9.2 and have an emuNAND. You'd just download the latest Luma3DS here and extract these files to your SD card:

arm9loaderhax.bin to the root of your SD:\ card (yes, Luma3DS uses this even if you don't have A9LH installed)
menuhax\boot.3dsx to the root of your SD:\ card overwriting the one you have there.

That's it. If you have menuhax installed, which I believe you do, then it would boot automatically. You'll know it works because the first time it boots you'll see the Luma3DS config screen.

 

[nechigawara]

Wow thank you for the information!
It helped a lot!

Well the space is not an issue, since I won't have that many games in my 2DS, so far it has been working great with 32GB

I have one question, do I really need to downgrade to 2.1?
I'm going to follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

And it doesn't tell me to downgrade to 2.1 at all

If you're on O3DS or 2DS, Yes. A9LH need Console OTP which can't be extract unless your console on lower FW.
Only N3DS can do OTPless A9LH.

 

[Olmectron]

Wow thank you for the information!
It helped a lot!

Well the space is not an issue, since I won't have that many games in my 2DS, so far it has been working great with 32GB

I have one question, do I really need to downgrade to 2.1?
I'm going to follow this guide:
https://gbatemp.net/threads/tutoria...s-full-menuhax-rednand-autoboot-setup.432499/

And it doesn't tell me to downgrade to 2.1 at all

For installing A9LH on O3DS (that includes O3DS XL and 2DS), you need to downgrade to 2.1.

For installing A9LH on N3DS (that includes N3DS XL too), you don't need to dowgrade if you're already on 9.2.

That guide is for menuhax, if you want A9LH, follow the guide everyone has been linking: https://github.com/Plailect/Guide/wiki/Part-1-(ARM9)