Hacking Can't get past "Installing arm9loaderhax"

[FreakPrism]

It said gateway install failed error 00000006 (in red).

Likely because I had not done the EmuNAND steps at 9.2 since I switched to the 3ds.guide.

Is there any way to get back to 9.2 without the A9lh install?

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

How is your SDCard formatted? Sounds like it's corrupt for some reason.

I don't think so as I formatted it before starting and ran the tool in the guide to verify it is not corrupt.

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

Do you have a legitimate 3DS cart you can put in the system?
I'm not sure why you're having trouble on this step, but I've seen a couple times that it's helped.. somehow. Might help you.

I don't. Won't any of them want to install a system update since I am on 2.1?

 

[Quantumcat]

I don't think so as I formatted it before starting and ran the tool in the guide to verify it is not corrupt.

You definitely did a full read & write check with H2testw? Do you remember exactly what the result was? I think that's a likely reason for your problem (a corrupted or fake SD card).

 

[FreakPrism]

If I remember it said success or complete with no errors detected. I don't think the card is corrupt or fake. In addition it got me this far.

Let me try with another SD card just in case. At this point anything that helps get past this step

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

Using a different sd card ends up with the same result

No idea why this step is so problematic for me .....

 

[linuxares]

did you use GUIFormat or Windows to format the SD Card? The 3DS doesn't like Windows FAT32 most of the times.

 

[Xiphiidae]

The 3DS doesn't like Windows FAT32 most of the times.

What are you talking about? The 3DS only accepts FAT32.

 

[linuxares]

What are you talking about? The 3DS only accepts FAT32.

Re-read what I said, it doesn't like Windows FAT32. It formats FAT32 really crappy.

 

[Xiphiidae]

Re-read what I said, it doesn't like Windows FAT32. It formats FAT32 really crappy.

My mistake, but it's worth noting that the issue with Windows and FAT32 with 3DS SD cards is that Windows cannot format 64GB+ SD cards to FAT32, hence a third-party tool is necessary to get a 64GB+ SD to work on a 3DS. Regardless, it really shouldn't matter in this case, as plenty of people have used Windows-formatted SD cards and have been able to install A9LH fine.

That being said, it's always a good idea to use SD Formatter 4.0.

 

[linuxares]

Maybe something like this is causing the problem you are experience with GW?

 

[FreakPrism]

I used GuiFormat per the guide.

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

I tried holding it down and it still failed. I think my issue with GW would be I did not do the emuNAND step when it was at 9.2.

 

[lincruste]

Re-read what I said, it doesn't like Windows FAT32. It formats FAT32 really crappy.

No it doesn't. Apart from the 32 GB limit, there is no trouble with Windows formated SD cards. Windows does a lot of things wrong, but FAT32 formatting ain't one.

 

[linuxares]

No it doesn't. Apart from the 32 GB limit, there is no trouble with Windows formated SD cards. Windows does a lot of things wrong, but FAT32 formatting ain't one.

Cool, you proved me wrong. I guess my experience working with these kind of things for a living is wrong.

 

[FreakPrism]

So ... I have the backup of my SysNand I took at 9.2 with Decrypt9. I'm guessing I can restore and try with Gateway considering my backup is after I did the Time Machine from my 10.3 original FW.

Since I am on 2.1, how can I restore my SysNand with my Decrypt9 issued backup? Is my only option a hard mod?

 

[Pokem]

maybe you did a partial downgrade to 2.1?

 

[FreakPrism]

maybe you did a partial downgrade to 2.1?

Unlikely as here is the success log from Decrypt9:

Spoiler: Log output

Selected: [Auto CTRNAND Transfer]
A9LH not detected, checking FIRM0...
Select CTRNAND transfer image
Use arrow keys and <A> to choose a file
2.1.0-4U_ctrtransfer_o3ds.bin
Image size is: 794624000 byte

Step #0: Optional NAND backup
Press <B> to skip and continue without backup
Dumping SysNAND. Size (MB): 1240
Use arrow keys and <A> to choose a name
NANDmin.bin
Creating NANDmin.bin ...
NAND dump SHA256: 18E6A1E5...
Store to NANDmin.bin.sha: ok

Step #1: .SHA verification of CTRNAND image...
Checking hash from .SHA file...
Step #1 success!

Step #2: Dumping transfer files
Searching for SecureInfo_A...
Found at 0E7C8000, size 273b
Creating B3BA6873_SecureInfo_A ...
Searching for movable.sed...
Found at 0E788000, size 320b
Creating B3BA6873_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0E710000, size 272b
Creating B3BA6873_LocalFriendCodeSeed_B ...
Searching for configsave.bin...
Found at 0E5D8000, size 256kB
Creating B3BA6873_configsave.bin ...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Switching out NAND header first...
Injecting 2.1.0-4U_ctrtransfer_o3ds.bin (757 MB)...
Opening 2.1.0-4U_ctrtransfer_o3ds.bin ...
Step #3 success!

Step #4: Injecting transfer files
Searching for SecureInfo_A...
Found at 0B9CC000, size 273b
Opening B3BA6873_SecureInfo_A ...
Fixing file CMAC for console...
Searching for SecureInfo_A...
Found at 0B9CC000, size 273b
File has no fixable CMAC
Searching for movable.sed...
Found at 13A14000, size 320b
Opening B3BA6873_movable.sed ...
Fixing file CMAC for console...
Searching for movable.sed...
Found at 13A14000, size 320b
Validated CMAC okay
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening B3BA6873_LocalFriendCodeSeed_B ...
Fixing file CMAC for console...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
File has no fixable CMAC
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Opening B3BA6873_configsave.bin ...
Fixing file CMAC for console...
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
0x30 KeyY: set up from NAND
Validated CMAC okay
Step #4 success!

Step #5: Fixing CMACs and paths
Checking and fixing <id0> folder
/DATA/<ID0>: renamed to match
Fixing essential system file CMACs
Searching for ticket.db...
Found at 17158000, size 35MB
CMAC id: 0
CMAC mismatch -> fixed CMAC
Searching for certs.db...
Found at 0B9C4000, size 24kB
CMAC id: 1
CMAC mismatch -> fixed CMAC
Searching for title.db...
Found at 0DD80000, size 403kB
CMAC id: 2
CMAC mismatch -> fixed CMAC
Searching for import.db...
Found at 0DD4C000, size 203kB
CMAC id: 3
CMAC mismatch -> fixed CMAC
Searching for movable.sed...
Found at 13A14000, size 320b
Validated CMAC okay
Fixing other system file CMACs
Searching for tmp_t.db...
Found at 0DDEC000, size 54kB
CMAC id: 4
CMAC mismatch -> fixed CMAC
Searching for tmp_i.db...
Found at 0DDE8000, size 10kB
CMAC id: 5
CMAC mismatch -> fixed CMAC
Searching for seedsave.bin...
Failed!
Searching for nagsave.bin...
Failed!
Searching for nnidsave.bin...
Failed!
Searching for friendsave.bin...
Failed!
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
0x30 KeyY: set up from NAND
Validated CMAC okay
Step #5 success!

Step #6: Dumping and injecting NATIVE_FIRM
Searching title "NATIVE_FIRM"...
Trying title ID 0004013800000002 (region 1)
Method 1: Search in title.db...
Found title ID 0004013800000002
TMD0 found at 137EC000, size 2868b
APP0 found at 11B04000, size 879kB
Dumping & decrypting NATIVE_FIRM.app...
Creating NATIVE_FIRM.app ...
Code / Crypto: CTR-P-CTAP / Standard
Decrypt ExHdr/ExeFS/RomFS (2kB/876kB/0MB)
Verify ExHdr/ExeFS/RomFS: OK/OK/-
Extracting binary FIRM...
Verifying NATIVE_FIRM.bin...
Verified okay!
NATIVE_FIRM found, injecting...
Step #6 success!
Auto CTRNAND Transfer: succeeded!

 

[Quantumcat]

Since I am on 2.1, how can I restore my SysNand with my Decrypt9 issued backup? Is my only option a hard mod?

Yeah you can't use Decrypt9 on 2.1 except if you have a9lh installed. Don't send away for a hardmod just yet, I heard something about an arm9 exploit discovered for <3.0 which would mean being able to access Decrypt9 from SoundHax on 2.1. So probably just hold tight for a while if you can't work out what's wrong or how to fix it.

 

[FreakPrism]

Cool good to know.

I also wonder if at that point I go back to 9.2, I wonder if I should get a game to update system to 10.x? That should remove anything Gateway may have corrupted, right?

 

[gamesquest1]

can't you just use the old otphelper, this will dump your otp and allow you to resort your original nand backup, from there you can run safea9lhinstaller on the updated fw to install a9lh

ps after doing a ctrtransfer any issues caused by gw''s downgrade tools should be gone, so I doubt it's a issue with the fact you used the gw downgrader

 

[lincruste]

Cool, you proved me wrong. I guess my experience working with these kind of things for a living is wrong.

I don't have to prove anything here, you're the one pretending MS can't properly format with its own proprietary file system.

 

[GilgameshArcher]

If people followed the High Priest Plailect words in The Bible A9LH Guide, without ever deviating from the path of truth nothing wrong would happen

 

[linuxares]

I don't have to prove anything here, you're the one pretending MS can't properly format with its own proprietary file system.

Then most IT personal must be wrong! Anyway, I don't know how to help OP anymore since it seem to be something with GW causing the issue.