Hacking Could someone compile A9LH for me?

[FenrirWolf]

Don't worry about it too much. If it does turn out that one of the NANDs is messed up somehow, you can always restore it from a backup.

Another thing to consider is that maybe one of your NANDs has a broken install of Menuhax on it. You can try deleting (or, better yet, removing and backing up) the extdata folders from the SD card and see if that fixes your issue.

 

[DrakeLyon]

What I would do is perform a few tests.

Test 1) Remove the SD card and turn on the console. Does it just hang on a blank screen and not boot to anything? Then you still have a9lh.

Test 2) Turn the console on and don't press anything. Since you have the updatedsysnand file in the rei folder, this should cause you to boot to sysnand.

Test 3) Temove (or rename) the updatedsysnand file, then turn the console on and don't press anything. Does it boot to something? If it does, that's your emunand.

If both test 2 and test 3 seem to return the same results, then it just means that your emunand and sysnand are currently clones of each other.

Ah.. I guess my NANDs are clones..both on 10.6 :/

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

Don't worry about it too much. If it does turn out that one of the NANDs is messed up somehow, you can always restore it from a backup.

Another thing to consider is that maybe one of your NANDs has a broken install of Menuhax on it. You can try deleting (or, better yet, removing and backing up) the extdata folders from the SD card and see if that fixes your issue.

Hmm, I'll try removing the extdata folders from the SD card in hopes that it can fix the problem booting into EmuNAND with the L button. If that works, I'll just downgrade my EmuNAND to 9.2 and all will be complete lol
As far as restoring NANDS from a backup, I thought I could only do that from 9.2. Is there another way?

 

[FenrirWolf]

Ah, so your sysnand and emunand are both on 10.6? That's not too big a problem.

First order of business would do is put the "updatedsysnand" file back on your SD card, so you know that booting while holding nothing = sysnand and booting while holding L/R = emunand. (unless you wanted to keep using emunand for everything, in which case you'd keep the file gone).

Next, instead of holding L to boot into emunand, try holding R instead. This should make the emunand launch successfully. It will just be running from your normal firmware.bin instead of firmware90.bin, meaning you can't use it to launch Decrypt9 or similar programs. But I don't recall if that would block the CIA version of SysUpdater from functioning or not. If it doesn't, then all you have to do is put a 9.2 update pack on your SD card, launch SysUpdater from your emunand, then downgrade it.

EDIT: And if that doesn't work, there will soon be versions of Decrypt9 that boot directly from a9lh. They might even be floating around already but I don't recall. Either way, you would be able to use that to directly flash a 9.2 backup to your emunand, assuming you have one lying around someplace. I'm guessing you do since you followed the OTP guide and all.

 

[DrakeLyon]

Ah, so your sysnand and emunand are both on 10.6? That's not too big a problem.

First order of business would do is put the "updatedsysnand" file back on your SD card, so you know that booting while holding nothing = sysnand and booting while holding L/R = emunand. (unless you wanted to keep using emunand for everything, in which case you'd keep the file gone).

Next, instead of holding L to boot into emunand, try holding R instead. This should make the emunand launch successfully. It will just be running from your normal firmware.bin instead of firmware90.bin, meaning you can't use it to launch Decrypt9 or similar programs. But I don't recall if that would block the CIA version of SysUpdater from functioning or not. If it doesn't, then all you have to do is put a 9.2 update pack on your SD card, launch SysUpdater from your emunand, then downgrade it.

EDIT: And if that doesn't work, there will soon be versions of Decrypt9 that boot directly from a9lh. They might even be floating around already but I don't recall. Either way, you would be able to use that to directly flash a 9.2 backup to your emunand, assuming you have one lying around someplace. I'm guessing you do since you followed the OTP guide and all.

Lol I'm keeping my SysNAND as primary. Also I just obtained the A9LH version of Decrypt9 so I'm gonna see how that turns out. Deleting ExtData folder only deleted my theme and rewrapped all of my CIAs, so L won't boot anything still, and using R to try and boot EmuNAND is kind of confusing me as I can't tell which is which. But that's probably because my NANDs are linked

 

[FenrirWolf]

Yeah. They're linked right now. But as long as you have the "updatedsysnand" flag set up, you know for sure that booting holding nothing = sysnand and booting holding L/R = emunand.

 

[DrakeLyon]

Yeah. They're linked right now. But as long as you have the "updatedsysnand" flag set up, you know for sure that booting holding nothing = sysnand and booting holding L/R = emunand.

Definitely lol
I'll let you know how it turns out when I get Decrypt9 set up and if it recovers anything

 

[DrakeLyon]

Decrypt9 did the trick! I'm so relieved! Whew! I've got the best O3DS in the world lol, now I just gotta get a N3DS and do the same XD

 

[TheSunGodNika]

Now a then...

My N3DS now have's Arm9LoaderHax.

But my O3DS... it doesn't.

So...

...Wanting to compile my O3DS's OTP this time? https://mega.nz/#!VwZwXJrR!s_LGYtQH128K_aJsdkyAnN_SAs6t7lreQt7PSp9dNq0