Hacking About to go from menuhax to a9lh via otpless method (N3DS).

[AlanWeird]

I just have a few questions.

So, I'm intent on using luma, as it seems to be the obvious choice.

But I'm going from a two nand situation (9.2 unlinked sysnand, and most up to date emunand, created with gateway, currently running reinand) to a single nand situation, right? So how do I achieve that? I'll be backing up with decrypt9wip in a few minutes.

Actually getting a9lh in there doesn't cause any problem, it's just what's best to do after.

 

[Olmectron]

I just have a few questions.

So, I'm intent on using luma, as it seems to be the obvious choice.

But I'm going from a two nand situation (9.2 unlinked sysnand, and most up to date emunand, created with gateway, currently running reinand) to a single nand situation, right? So how do I achieve that? I'll be backing up with decrypt9wip in a few minutes.

Actually getting a9lh in there doesn't cause any problem, it's just what's best to do after.

After installing A9LH, backup your EmuNAND via Hourglass9 and then restore it back to SysNAND.

 

[cheuble]

I just have a few questions.

So, I'm intent on using luma, as it seems to be the obvious choice.

But I'm going from a two nand situation (9.2 unlinked sysnand, and most up to date emunand, created with gateway, currently running reinand) to a single nand situation, right? So how do I achieve that? I'll be backing up with decrypt9wip in a few minutes.

Actually getting a9lh in there doesn't cause any problem, it's just what's best to do after.

Make a backup of your current EmuNAND. Once you've installed A9LH, you can flash this backup to your sysNAND

 

[AlanWeird]

After installing A9LH, backup your EmuNAND via Hourglass9 and then restore it back to SysNAND.

wow. that easy?

neat.

 

[Olmectron]

wow. that easy?

neat.

Yes, that easy. I recommend it that way, to have an updated SysNAND. If you preferred EmuNAND, you could leave it that way with A9LH, since it can load EmuNAND directly too.

 

[AlanWeird]

Yes, that easy. I recommend it that way, to have an updated SysNAND. If you preferred EmuNAND, you could leave it that way with A9LH, since it can load EmuNAND directly too.

I'll be happy to have everything on sysnand What's the best way to reclaim my emunand space after?

 

[Olmectron]

I'll be happy to have everything on sysnand What's the best way to reclaim my emunand space after?

After restoring the backup to SysNAND, and making sure it loads, backup everything in your SD card to the PC. Then get the latest release of EmuNAND9, and go to EmuNAND options -> Format SD (No EmuNAND) or something like that, and copy everything back to your SD card. Done.

 

[AlanWeird]

After restoring the backup to SysNAND, and making sure it loads, backup everything in your SD card to the PC. Then get the latest release of EmuNAND9, and go to EmuNAND options -> Format SD (No EmuNAND) or something like that, and copy everything back to your SD card. Done.

Well. Here I go

Your information has been superb. Glad you were here to help.

 

[Olmectron]

Well. Here I go

Your information has been superb. Glad you were here to help.

Thanks! Any other thing you may doubt about, don't hesitate to ask. If it's not me, someone else will surely help!

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

By the way. Be sure to ALWAYS use Hourglass9 for backing up and restoring SysNAND. Only use EmuNAND9 for the bit about formatting the SD card. Since you could accidentally delete A9LH when restoring a backup in EmuNAND9, but with Hourglass9 it's always 100% sure you won't lose the A9LH installation.

 

[AlanWeird]

So, the actual a9lh seemed to be a success. Just setting up my card.

Also, I'll need to track down a 3dsx version of hourglass9

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

Thanks! Any other thing you may doubt about, don't hesitate to ask. If it's not me, someone else will surely help!

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

By the way. Be sure to ALWAYS use Hourglass9 for backing up and restoring SysNAND. Only use EmuNAND9 for the bit about formatting the SD card. Since you could accidentally delete A9LH when restoring a backup in EmuNAND9, but with Hourglass9 it's always 100% sure you won't lose the A9LH installation.

Okay I was doing that anyway. Only bump I've hit is hourglass 9 itself. all it is, is a bin file. Will homebrew launcher load that?

 

[Alex658]

.bin files are launched from a9lh itself. Just go to the guide where the move emunand part is.
You need to create a payload folder inside of luma folder. in the payload folder attach a button to hourglass9 and it will boot at launch if you hold that button when you power on your console. No need for the HBL for backup things.
you would rename it to start_Hourglass9.bin if memory serves right.

then when you turn on your console you would hold the start button as well as the power button until hourglass9 comes up.

EDIT: this is stated directly in the guide, please try to follow it carefully to avoid any possible problems from arising.

 

[AlanWeird]

Alex, the guide has way more info than was required, by far.

I can report victory. My N3DS is running luma, via A9lh, on sysnand alone, which was restored from my now gone emunand backup.

My steps?

1. I installed UnsafeA9LHInstaller.beta by going into my 9.2 sysnand, using browserhax and getting to the homebrew launcher.
2. that took seconds to install, powered down, so I put luma files on my sd card.
3. everything booted. I then added aeskeydb.bin to root, and placed hourglass9.bin into a payload folder in luma, naming it as start_Hourglass9.bin
4. I booted using start button, hourglass9 loads, and I backup my sysnand and emunand. I then restore my emunand to sysnand.
5. After that was all said and done, I backed up my SD card, then I used SDFormatter on my windows 10 PC to eradicate emunand from the card.
6. Reformatted the card using minitool partition wizard, set as primary. 32kb cluster. Fat32.
7. Recopied all my backed up data. popped the card in, and everything is functioning well.

I have my brothers O3DS XL to do this to shortly, which is on 9.2 and has no emunand or anything to complicate matters and I know I'll have to follow plailects guide expressly, but here, at least, tons of it wasn't amazingly relevant.

 

[Alex658]

Alex, the guide has way more info than was required, by far.

I can report victory. My N3DS is running luma, via A9lh, on sysnand alone, which was restored from my now gone emunand backup.

My steps?

1. I installed UnsafeA9LHInstaller.beta by going into my 9.2 sysnand, using browserhax and getting to the homebrew launcher.
2. that took seconds to install, powered down, so I put luma files on my sd card.
3. everything booted. I then added aeskeydb.bin to root, and placed hourglass9.bin into a payload folder in luma, naming it as start_Hourglass9.bin
4. I booted using start button, hourglass9 loads, and I backup my sysnand and emunand. I then restore my emunand to sysnand.
5. After that was all said and done, I backed up my SD card, then I used SDFormatter on my windows 10 PC to eradicate emunand from the card.
6. Reformatted the card using minitool partition wizard, set as primary. 32kb cluster. Fat32.
7. Recopied all my backed up data. popped the card in, and everything is functioning well.

I have my brothers O3DS XL to do this to shortly, which is on 9.2 and has no emunand or anything to complicate matters and I know I'll have to follow plailects guide expressly, but here, at least, tons of it wasn't amazingly relevant.

The steps are there for a reason, a failsafe.
Also, remember that guide is adapted for o3ds as well. It tries to cover every possible scenario that may occur, and imho it does an outstanding job.

I'm glad to know you could pull it through!

I'm saying this because other users have had a similar way of thinking back when the guide wasn't so simple and neither ctr transfer nor otp-less were possible, and resulted in user error bricks specially on n3ds. It doesn't really hurt anyone to be a little cautious with their 150$ electronics...

 

[Olmectron]

The steps are there for a reason, a failsafe.
Also, remember that guide is adapted for o3ds as well. It tries to cover every possible scenario that may occur, and imho it does an outstanding job.

I'm glad to know you could pull it through!

I'm saying this because other users have had a similar way of thinking back when the guide wasn't so simple and neither ctr transfer nor otp-less were possible, and resulted in user error bricks specially on n3ds. It doesn't really hurt anyone to be a little cautious with their 150$ electronics...

My New 3DS XL (normal red version) costed me $300. So, yeah, everyone should be cautious with their really expensive electronics.