Hacking A9LH Guide Update - Discussion

  • Thread starter Thread starter Quantumcat
  • Start date Start date
  • Views Views 77,046
  • Replies Replies 605
  • Likes Likes 22
Interesting. But if the new Nintendo firmware can't write to that, is it possible that it won't complete the install and then you might end up with a brick, precisely because of the said install didin't reach 100%?
That's unlikely to happen. Otherwise, A9LH itself would cause a brick, being a FIRM replacement :P
 
@grafate @DSpider Interesting points! However if it did brick or was nonfunctional in some way, a9lh users could go back to a NAND backup, and just await devs to find some way around it.

That is the way I understood it where you would have to wait for a fix to come or revert back. The only reason I asked that question was mainly because I keep seeing people ask should I keep a emunand or just to do the udpated sysnand. And I do feel many are advising do the updated sysnand without thinking it through. For me and my family's 3ds we just kept emunand to boot from luma a9lh.

Little longer to boot and got to install gba to both nands but at least that that possiblity of functionality being halted will not get affected with the emunand route. Would be nice to have that part in the guide as giving newcomers a heads up on that would be nice so a more informed decision can be made. Updated sysnand for some may be more convenient but the emunand route will still be better for others, especially for the younger ones who all they only want is to play games.
 
There actually was a problem exactly like you're describing with ReiNAND a while back, except it didn't brick but failed to update.

The firm protection patches redirect the install location iirc and don't just block FIRM partitions.

Luma has never had this issue, so as long as you use it you'll be fine.
 
  • Like
Reactions: VinsCool
Can you restore a sysNAND backup (created with Decrypt9WIP) to remove a9lh and revert back to the firmware you were on?
 
For part 2 after I get into decrypt9 I am supposed to take out my sd, put ctrnand on the card then reinsert it all what decrypt9 is running? Why not just put ctrnand on the sd before getting into decrypt9?
 
And I do feel many are advising do the updated sysnand without thinking it through.
However if you're using updated sysNAND, you can still revert back to a backup and create an emuNAND if need be. Although I guess you'd be losing a little bit of progress (however long ago you made the backup).
 
For part 2 after I get into decrypt9 I am supposed to take out my sd, put ctrnand on the card then reinsert it all what decrypt9 is running? Why not just put ctrnand on the sd before getting into decrypt9?
That could work too lol. That's what I remember doing: putting all files on my card, then did the entire process one way.
 
  • Like
Reactions: Ghassen-ga
Is there a way to do part 3 without internet access? Can I use the MSET exploit on the 2.1.0 firmware?
 
Is the nand (i think) file that's about 1gb in the files9 folder needed? Or can i remove it.
 
The reason is that for 1.0.0-0E carts you don't have a browser to start with so going to 9.9+ with cart and getting a dummy browser wouldn't hurt if it was verified that you could continue from that point.
But I will not be the first to verify that I can continue from that point with my normal freakyhax - I thought I had a Monster Hunter U cart available but it was a MH4 with 8.1 fw....

So instead I'm getting an R4i clone which will get me into MSET and be useful for all DS games.

(Incintentally nintendo decided to clear out the old stock of 1.0.0-0E consoles here with OOT bundled, perhaps the intention really was that you should use that backdoor :) )

1.0 has no browser and upgrading using a 9.9 cart won't get you the browser. So you're shit out of luck there.
 
Is there a way to do part 3 without internet access? Can I use the MSET exploit on the 2.1.0 firmware?
I was trying to host the site using my phone with an app called PAW server but every time I try, instead of the site saying "arm11.bin loading___________" as it should, what mine says is "arm.dat loading__________" after hosting it.

Honestly, I have yet to try using it on my 3ds, but I'm really bothered with the difference in output on the web browser.
1.0 has no browser and upgrading using a 9.9 cart won't get you the browser. So you're shit out of luck there.
I just updated my recently obtained 3ds last night from 1.1.0-0E directly to 9.2.0-0E, I didn't bother checking the dummy browser out because I have stickerhax to use in installing a9lh. But yeah, everything went smoothly, I even already sold and shipped the 3ds already. :)
 
I was trying to host the site using my phone with an app called PAW server but every time I try, instead of the site saying "arm11.bin loading___________" as it should, what mine says is "arm.dat loading__________" after hosting it.

Honestly, I have yet to try using it on my 3ds, but I'm really bothered with the difference in output on the web browser.

I just updated my recently obtained 3ds last night from 1.1.0-0E directly to 9.2.0-0E, I didn't bother checking the dummy browser out because I have stickerhax to use in installing a9lh. But yeah, everything went smoothly, I even already sold and shipped the 3ds already. :)

9.2 installs a dummy browser as well? I thought it installed the real thing? In any case, nice going! ^_^
 
OK, apologies if this issue has been covered before. I'm at an impasse.

I'm at Part 2, 2.1.0 ctrtansfer. I was able to open Decrypt9, have the 2.1.0 ctrtransfer .bin and .bin.sha files in my sd's /files9/ folder. But when I select auto ctrnand transfer, after I do the security keystroke to confirm I get this:

Selected: [Auto CTRNAND Transfer]
A9LH not detected, checking FIRM0 ...
Select CTRNAND transfer image
No usable file found
Auto CTRNAND Transfer: failed!

Press B to return, START to reboot.


(halp.)

EDIT: nvm, think I resolved it. The .bin and .bin.sha files need to be on the SD when you open Decrypt9WIP. The guide says you need to already be in Decrypt9WIP, then copy the files to the sd and reinsert the sd in the console, then proceed. Looks to me that Decrypt9WIP needs to be restarted in order for it to recognize the ctrtransfer bin is even there.
 
Last edited by Hanafuda,
OK, apologies if this issue has been covered before. I'm at an impasse.

I'm at Part 2, 2.1.0 ctrtansfer. I was able to open Decrypt9, have the 2.1.0 ctrtransfer .bin and .bin.sha files in my sd's /files9/ folder. But when I select auto ctrnand transfer, after I do the security keystroke to confirm I get this:

Selected: [Auto CTRNAND Transfer]
A9LH not detected, checking FIRM0 ...
Select CTRNAND transfer image
No usable file found
Auto CTRNAND Transfer: failed!

Press B to return, START to reboot.


(halp.)

EDIT: nvm, think I resolved it. The .bin and .bin.sha files need to be on the SD when you open Decrypt9WIP. The guide says you need to already be in Decrypt9WIP, then copy the files to the sd and reinsert the sd in the console, then proceed. Looks to me that Decrypt9WIP needs to be restarted in order for it to recognize the ctrtransfer bin is even there.

did you unmount the sd by pressing the select button first?
 
  • Like
Reactions: Hanafuda

Site & Scene News

Popular threads in this forum