Hacking firm1.bin is invalid...

[raylgo]

I have been redoing the prep work for A9LH installation thrice now but I keep getting this message... Which file do I need to redownload? I downloaded everything just 3 days ago so I doubt it's an outdated file problem...

Could it be a problem with SafeA9Installer? I just realized that I have 2 different versions downloaded in the 3ds hacking folder I created...

 

[rubycrow]

Follow the guide step by step and redownload all the files (as you should always use the newest version or the version specified in the guide base on which section and which console you are on). The error is likely caused by you forgetting to copy a9lh folder from the datainput_v4.zip into the root of your sd card or having the incorrect version of SafeA9Installer or having the older version of the datainput zip.

 

[gameboy92]

try to use SafeA9LHInstallerv 2.6.2. The newest is problem with firm1.bin.

 

[raylgo]

OK now I have 3 different safe a9lh installers... I have 2.03,2.62, and 2.67 along with 2 different data-input folders. V3 and v4... Which combination do I use? 0_o

And why does only safe a9lh installer version 2.03 have an arm 11. Bin inside?

 

[Tenshi_Okami]

OK now I have 3 different safe a9lh installers... I have 2.03,2.62, and 2.67 along with 2 different data-input folders. V3 and v4... Which combination do I use? 0_o

And why does only safe a9lh installer version 2.03 have an arm 11. Bin inside?

Which console are you doing A9LH?

 

[raylgo]

Which console are you doing A9LH?

On a new3dsxl which was originally on 11.0.0.33-u. The dsiware downgrade and the ctr transfer all went off without a hitch but now I'm stuck. The guide links to safe a9lh installer 2.03 and data input V3 but I got the firm. Bin invalid error... Used the 2.67 installer with input v4 and get a payload ecxeeds max size error...

Tried erasing the arm 11. Bin from the 2.03 installer and the 3ds gets stuck at arm 11. Bin loading...

I'm guessing I can't use the arm 11. Bin of 2.03 coz it always keeps the installer version at 2.03 no matter which of the 3 I use. But the other 2 don't have their own...

 

[Tenshi_Okami]

On a new3dsxl which was originally on 11.0.0.33-u. The dsiware downgrade and the ctr transfer all went off without a hitch but now I'm stuck. The guide links to safe a9lh installer 2.03 and data input V3 but I got the firm. Bin invalid error... Used the 2.67 installer with input v4 and get a payload ecxeeds max size error...

Tried erasing the arm 11. Bin from the 2.03 installer and the 3ds gets stuck at arm 11. Bin loading...

I'm guessing I can't use the arm 11. Bin of 2.03 coz it always keeps the installer version at 2.03 no matter which of the 3 I use. But the other 2 don't have their own...

use the 2.03 one, thats what the guide told me to download. And i did 2 A9LH O3DS yesterday using 2.03. So it should be safe

 

[chaser]

use the 2.03 one, thats what the guide told me to download. And i did 2 A9LH O3DS yesterday using 2.03. So it should be safe

Similarly, following the guide exactly, I did a dsiware downgrade & ctr transfer of an 11.0.0.33-E n3ds xl yesterday, using safea9lhinstaller v2.0.3 & data input 3, and it worked perfectly. Recheck you are using all the correct files, and they are all copied to the correct folder on your SD card. Also, double check that your SD card is working correctly.

 

[jupitersj]

I did both my od3sxl and new3dsxl with 2.0.3 and data input v3. The new3dsxl was done via system transfer legends of exidia method from the o3dsxl. The only issue I had with the new3dsxl, was after 2.1 ctrtransfer with no errors, I installed A9LH. but I could not boot, just "mounting CTRNAND" error. I could get into Luma and Hourglass9 fine though; all I had to do was reinstall my 9.2 nand backup and everything was fine again ...then I system updated to 11.2.0-35u, system format to put my real nnid back onto my new3dsxl, and inject fbi etc.

 

[raylgo]

Turns out that the original files linked by the guide were the ones I needed but the console was one of those that would have a crazy screen that would seem to stop responding during the a9lh step. I decided to go to the next step anyway and it worked out fine.