Homebrew A9HL Help

  • Thread starter Thread starter Jacklack3
  • Start date Start date
  • Views Views 2,981
  • Replies Replies 22
I mean that the process will still remain the same and what you mentioned doesn't really make the installation complicated, just much longer. Another thing that you mentioned about the fact that he puts links in every step. That's because he made the guide so everyone can join from the state they are currently in.
Yeah but a Bunch of the links in every step are mostly external to githubs etc.
Homebrew is small enough that he could just make one Pre-Pack and you could just reference the folder he can even Prepackage it with the 2.1 FW as EVERYONE will be needing that

And yes process is the same in the end but the time it takes can be shaved majorly, im hearing people taking 6+ Hours to get A9LH from Emunand etc.

The guide tells you to get
Decrypt9WIP
TPlaiSysUpdater
TinyFormat
OTPHelper
FBI
Universal Inject Generator
2.1 Firm for your region


The after you get that you got to step 1 and it tells you to grab hombrewloader.cia instead of putting it in the list, so you backtrack straight away. also it tells you to optionally get a Savemanager

Section I - Prep Work




Actually it tells you to get homebrew loader CIA in the LAST STEP after making you backtrack to get it midway guide anyhow

Later on you will need

SafeA9LHInstaller
Uncart for arm9loaderhax



So regardless of steps you take because you will be Starting at Step4 at the latest you will need All of the Above minimum, Pre-paacking all this with the 2.1 Firm of Each region and just referencing the Folder will save a bunch of time in itself, and even cuts down steps.

The guide is good it works kudos but it can be simplified and just because you dont get the latest github version because its prepackage it shouldnt matter, the process is safe enough now that a new updated file shouldnt be needed unless it fixes something serious

uhh... You have to format twice with tinyformat to get rid of any fragmentation of emuNAND. You are not formatting it twice for no reason, y'know. Downgrading emuNAND to 2.1 without double formatting causes more errors and sysUpdater might fail, forcing you to reinject your emuNAND backup over and over again...

Apparently fragmentation of the Emunand is caused by gateway Emunand only so this step shoudl be optional for non GW users
 
Last edited by izy,
Apparently fragmentation of the Emunand is caused by gateway Emunand only so this step shoudl be optional for non GW users

Well... You know that every emuNAND set up with emuNAND9 is a Gateway emuNAND right? Gateway emuNAND doesnt mean you have to be a Gateway user...
And usage of redNAND hasnt been here since like 2 or 4 days ago.

I have no idea what you are talking about.... You can literally go into emuNAND9 and it'll tell you "GW emuNAND".:wtf:
 
Yeah but a Bunch of the links in every step are mostly external to githubs etc.
Homebrew is small enough that he could just make one Pre-Pack and you could just reference the folder he can even Prepackage it with the 2.1 FW as EVERYONE will be needing that

And yes process is the same in the end but the time it takes can be shaved majorly, im hearing people taking 6+ Hours to get A9LH from Emunand etc.

The guide tells you to get
Decrypt9WIP
TPlaiSysUpdater
TinyFormat
OTPHelper
FBI
Universal Inject Generator
2.1 Firm for your region


The after you get that you got to step 1 and it tells you to grab hombrewloader.cia instead of putting it in the list, so you backtrack straight away. also it tells you to optionally get a Savemanager




Actually it tells you to get homebrew loader CIA in the LAST STEP after making you backtrack to get it midway guide anyhow

Later on you will need

SafeA9LHInstaller
Uncart for arm9loaderhax



So regardless of steps you take because you will be Starting at Step4 at the latest you will need All of the Above minimum, Pre-paacking all this with the 2.1 Firm of Each region and just referencing the Folder will save a bunch of time in itself, and even cuts down steps.

The guide is good it works kudos but it can be simplified and just because you dont get the latest github version because its prepackage it shouldnt matter, the process is safe enough now that a new updated file shouldnt be needed unless it fixes something serious



Apparently fragmentation of the Emunand is caused by gateway Emunand only so this step shoudl be optional for non GW users
Well... You know that every emuNAND set up with emuNAND9 is a Gateway emuNAND right? Gateway emuNAND doesnt mean you have to be a Gateway user...
And usage of redNAND hasnt been here since like 2 or 4 days ago.

I have no idea what you are talking about.... You can literally go into emuNAND9 and it'll tell you "GW emuNAND".:wtf:
So if all this is the case, then shouldn't the guide be updated?
 

Site & Scene News

Popular threads in this forum