https://github.com/Plailect/Guide/wiki

This guide includes information to get you from nearly any situation to full arm9loaderhax CFW.

If you appreciate this guide and the work I put into maintaining it, I accept donations through both Bitcoin and PayPal.

 

[androgynus]

Hey people! Me again, so i did everything on that guide https://github.com/Plailect/Guide/wiki/OTP-Info and everything went perfect. Ive been able to launch Aureinand and so on. Whats the point of step 2 and 3 of this tutorial (http://gbatemp.net/threads/guide-getting-arm9loaderhax.417719/ )then ? Are those step necessary or they are already included in the said guide ?

 

[Elaugaufein]

Hey people! Me again, so i did everything on that guide https://github.com/Plailect/Guide/wiki/OTP-Info and everything went perfect. Ive been able to launch Aureinand and so on. Whats the point of step 2 and 3 of this tutorial (http://gbatemp.net/threads/guide-getting-arm9loaderhax.417719/ )then ? Are those step necessary or they are already included in the said guide ?

They are from an earlier method of installing A9LHax from before SafeAH9LInstaller was released, so they aren't relevant anymore.

 

[Shivan]

I always get validation stage 0 failed, Basic NAND integrity check failed, FIRM0 hash mismatch and SecurInfo_A not found. what should I do?

This is my OTP.log Getting error in TMD part.
3DS model.

Edit: Have already checked manualy and .tmd sha256 mine is 2de0f383dd186a3af708a406935fa37b78bae70d0d9fbabd5178c21799d9e710 and the one in the helper has 882911071290efc42239793d6f7d777722d23377bd59d1508fa41f8fc752b4a4

tryied recovery from emunand_formatted.bin twice and got the same error.

How solve this??

Using EmuNAND @ 1D7800/000000

NAND CID: BD22E4191303473130434D4D00011100
TWL Customer ID: 0088483500000000
Your serial number is: CB10005758
Your region is: USA
Checking title 0004001000021000...
Checking title 0004001000021100...
Checking title 0004001000021200...
Checking title 0004001000021300...
Checking title 0004001000021400...
Checking title 0004001000021500...
Checking title 0004001000021700...
Checking title 0004001000021900...
Checking title 0004001000021A00...
Checking title 0004001000021B00...
Checking title 0004001000021D00...
Checking title 0004001000021E00...
Checking title 0004001000021F00...
Checking title 0004001000024000...
TMD not found or corrupt
Checking title 0004001B00010002...
Checking title 0004003000008A02...
Checking title 0004003000008A03...
Checking title 0004003000008F02...
Checking title 0004003000009002...
Checking title 0004003000009202...
Checking title 0004003000009302...
Checking title 0004003000009402...
Checking title 0004003000009602...
Checking title 0004003000009702...
Checking title 000400300000C502...
Checking title 000400300000C503...
Checking title 000400300000C802...
Checking title 000400300000C803...
Checking title 000400300000C902...
Checking title 000400300000CB02...
Checking title 000400300000CC02...
Checking title 0004009B00010202...
Checking title 0004009B00010402...
Checking title 0004009B00010602...
Checking title 0004009B00011402...
Checking title 0004009B00011602...
Checking title 0004009B00011D02...
Checking title 0004009B00011E02...
Checking title 0004009B00012302...
Checking title 0004009B00013302...
Checking title 0004009B00014002...
Checking title 0004009B00014102...
Checking title 0004009B00014202...
Checking title 0004009B00014302...
Checking title 0004009B00015302...
Checking title 000400DB00010302...
Checking title 000400DB00010502...
Checking title 000400DB00016302...
Checking title 000400DB00017302...
Checking title 0004013000001502...
Checking title 0004013000001503...
Checking title 0004013000001602...
Checking title 0004013000001702...
Checking title 0004013000001703...
Checking title 0004013000001802...
Checking title 0004013000001803...
Checking title 0004013000001A02...
Checking title 0004013000001A03...
Checking title 0004013000001B02...
Checking title 0004013000001B03...
Checking title 0004013000001C02...
Checking title 0004013000001C03...
Checking title 0004013000001D02...
Checking title 0004013000001D03...
Checking title 0004013000001E02...
Checking title 0004013000001E03...
Checking title 0004013000001F02...
Checking title 0004013000001F03...
Checking title 0004013000002002...
Checking title 0004013000002102...
Checking title 0004013000002103...
Checking title 0004013000002202...
Checking title 0004013000002203...
Checking title 0004013000002302...
Checking title 0004013000002303...
Checking title 0004013000002402...
Checking title 0004013000002403...
Checking title 0004013000002602...
Checking title 0004013000002702...
Checking title 0004013000002703...
Checking title 0004013000002802...
Checking title 0004013000002902...
Checking title 0004013000002903...
Checking title 0004013000002A02...
Checking title 0004013000002A03...
Checking title 0004013000002B02...
Checking title 0004013000002C02...
Checking title 0004013000002C03...
Checking title 0004013000002D02...
Checking title 0004013000002D03...
Checking title 0004013000002E02...
Checking title 0004013000002E03...
Checking title 0004013000002F02...
Checking title 0004013000002F03...
Checking title 0004013000003102...
Checking title 0004013000003103...
Checking title 0004013000003202...
Checking title 0004013000003203...
Checking title 0004013000003302...
Checking title 0004013000003303...
Checking title 0004013000003402...
Checking title 0004013000003502...
Checking title 0004013000003702...
Checking title 0004013000008002...
Checking title 0004013000008003...
Checking title 0004013800000002...
Checking title 0004013800000003...
Checking title 0004013800000102...
Checking title 0004800542383841...
Is a TWL title, skipped
Checking title 00048005484E4441...
Is a TWL title, skipped
Checking title 0004800F484E4841...
Is a TWL title, skipped
Checking title 0004800F484E4C41...
Is a TWL title, skipped

Validation Stage 0: SUCCESS
Validation Stage 1: FAILED
Validation Stage 2: FAILED
# TWL titles        :   4
# TMD success       : 107
# TMD not found     :   1
# APP success       : 107
# APP not found     :   0
# APP fragmented    :   0

WARNING: Validation Stage 1 failed!
!DO NOT RESTORE THIS TO SYSNAND!
Starting from scratch is recommended

Downgrade Validation failed!
You can not continue here
One Click Setup: failed!

All my tests got false fails... But to have 100% sure, you should check manually like the tutorial says in troubleshooting: https://github.com/Plailect/Guide/wiki/Troubleshooting . It's not hard, but you have to use GodMode9 carefully.
One point is that if there is only one .tmd in the folder you got a REAL FAIL. If there is more than one .tmd in the folder, only one .tmd has to match the hash. Other mistake that people can do is check the hashes with different regions.

 

[GerbilSoft]

This is my OTP.log Getting error in TMD part.
3DS model.

Edit: Have already checked manualy and .tmd sha256 mine is 2de0f383dd186a3af708a406935fa37b78bae70d0d9fbabd5178c21799d9e710 and the one in the helper has 882911071290efc42239793d6f7d777722d23377bd59d1508fa41f8fc752b4a4

tryied recovery from emunand_formatted.bin twice and got the same error.

How solve this??

Checking title 0004001000024000...
TMD not found or corrupt

Title 00040010 00024000 is the infamous "promotional video" (USA region) from 3DS System v1.1.0. Are you sure you're using the latest version of OTPHelper? These titles were removed from the verification list to prevent false positives in v0.81.

 

[V3N0MBR]

Title 00040010 00024000 is the infamous "promotional video" (USA region) from 3DS System v1.1.0. Are you sure you're using the latest version of OTPHelper? These titles were removed from the verification list to prevent false positives in v0.81.

Yeap, but i will download OTPHelper again.

That's it. Downloaded the latest OTP and no error now.
Thx everyone

 

[D34DL1N3R]

Tried the guide again, but this time I started from Part 4 - Getting the OTP. I was a bit afraid due to the false positives that OTPHelper gave during the validation steps (regardless that one of the hashes matched, but it all turned out fine in the end. Goodbye emuNAND.

Question. Is it safe install the FBI.cia and then inject the original hs.app that was dumped from emuNAND... back into the final CFW SysNAND? I ask because I just think it looks ugly having it in H&S and since I have everything organized by folders I would just place the FBI.cia in my corresponding folder. I mean, if it was ever neecessary, FBI could just be injected back in... correct?

Edit: One other thing. In the final steps "Finalizing setup":

6. Update your CFW SysNAND to the latest version using system settings

It should already be updated to the latest since emuNAND gets updated during Part 3 (EmuNAND), so the step could be removed.

Anyone?

 

[9780553573404]

Hi...first off thanks for the guide

Down to business. I followed the guide without a single problem the entire time till the end.

Unlike everyone else (I suppose ?) I didn't do Copying EmuNAND data to SysNAND since I had nothing on there and was thinking it'd be faster to follow Installing FBI into SysNAND.
In Finalizing setup step 5 when I hit START but instead of rebooting I got this output:
AuReiNand configuration
Press A to select, START to save and reboot
( ) Updated SysNAND mode (A9LH-only)
( ) Use pre-pathed FIRMs
( ) Force A9LH detection

I couldn't find a single mention of this in the guide at least I don't recall it. So I just hit START to reboot which then produces this:
An error has occurred:
No emuNAND has been detected
Press any button to shutdown

After a bit I figured out booting whilst holding SELECT gets me the first dialog and I haven't messed with it much since I don't know what I'm doing but if I check off Updated SysNAND mode when I reboot it goes to SysNAND(presumably CFW SysNAND ?). But I'm not sure if this is the right thing to do. Could someone please advise ? Thanks.

 

[Hking0036]

Hi...first off thanks for the guide

Down to business. I followed the guide without a single problem the entire time till the end.

Unlike everyone else (I suppose ?) I didn't do Copying EmuNAND data to SysNAND since I had nothing on there and was thinking it'd be faster to follow Installing FBI into SysNAND.
In Finalizing setup step 5 when I hit START but instead of rebooting I got this output:
AuReiNand configuration
Press A to select, START to save and reboot
( ) Updated SysNAND mode (A9LH-only)
( ) Use pre-pathed FIRMs
( ) Force A9LH detection

I couldn't find a single mention of this in the guide at least I don't recall it. So I just hit START to reboot which then produces this:
An error has occurred:
No emuNAND has been detected
Press any button to shutdown

After a bit I figured out booting whilst holding SELECT gets me the first dialog and I haven't messed with it much since I don't know what I'm doing but if I check off Updated SysNAND mode when I reboot it goes to SysNAND(presumably CFW SysNAND ?). But I'm not sure if this is the right thing to do. Could someone please advise ? Thanks.

the 3.12 update for AuReiNand came out a little while ago, and replaces the flags you used to use (the AuReiNand Options.zip) with items in the menu. just check the first 2 and it will boot into cfw SysNAND.

 

[Falkiner]

I've trying to update using the "9.2.0 Update" section on your guide.

I was unable to inject H&S with the Decrypt9 so I've used the rxTools instead. After this, I've trying to update with SysUpdater and got the following message:

Then I've created this thread, people told me to try using the version 4.1, but I still got this error after the SysUpdater install the NATIVE_FIRM.

Yes, the updates folder is on the SD card.

I've trying searching the forum, but didn't found this error...

 

[9780553573404]

the 3.12 update for AuReiNand came out a little while ago, and replaces the flags you used to use (the AuReiNand Options.zip) with items in the menu. just check the first 2 and it will boot into cfw SysNAND.

Oh, I see. Thanks.

Hmm..I might've messed up. So, after I finished with the guide I started up Uncart to liberate my games. And I also visited the eShop. Haven't installed or messed with anything else. I was looking at my SD card on the computer and decided to clean it up a bit. Got rid of everything so that it looked like the screenshot at the end of the guide. Except that when I tried to turn on the O3DS the blue power light comes on then it just shuts off. I threw in a couple more files that I figured might be of importance and it worked again. Could having dumped games or visited the eShop have created some files that something requires to boot or has something changed since the guide was posted ?

 

[Omegapsy]

Just had to go through this guide with a New 3DS XL Hyrule edition and MUCH has changed since I floundered through installing it to my o3DS XL Props for the guide it was well written and very easy to understand (both from a technical standpoint and newbish standpoint) OTP Helper was new to me as it was not around when I originally installed a9lh to my o3dsXL so it was nice to learn that new system.

 

[Keylogger]

What exactly is MiniPasta and what is it useful for when installer A9LH?

 

[kfgtboy808]

So how do I remove armloader9hax completely? If I decide to go fully stock or sell my 3DS XL. Do I just sysnand restore via Decript9 with my sysNAND-original.bin that was on 9.2? Or is it more to it?

 

[pre10c]

So how do I remove armloader9hax completely? If I decide to go fully stock or sell my 3DS XL. Do I just sysnand restore via Decript9 with my sysNAND-original.bin that was on 9.2? Or is it more to it?

yes you have to install a pre-a9lh nand backup to remove a9lh

 

[kfgtboy808]

yes you have to install a pre-a9lh nand backup to remove a9lh

Alright thanks for quick reply. Will keep that in mind.

 

[FenrirWolf]

You'd prolly be doing a future buyer a favor if you left a9lh on there for them =P

 

[Elli27r]

hey Plailect I registered to say thank you, i followed your guide to the letter for about 5 hours(phew) and everything works, keep up the good work!

 

[xzeldax3]

I have a 3DS XL and am on 10.2 firmware. Will this process permanently reset my Activity Log at any point?

 

[Supster131]

I have a 3DS XL and am on 10.2 firmware. Will this process permanently reset my Activity Log at any point?

There's a small chance it may, but I doubt it.

 

[xzeldax3]

There's a small chance it may, but I doubt it.

What step would pose the risk? When I downgrade firmware?