Hacking Updated to a9lhv2, decrypt9 doesn't start anymore...

[einhuman197]

Title says all, WTF Plailect, I updated for the future and now necessary stuff doesn't boot anymore? How can I downgrade my arm9loaderhax? Or how can I run decrypt9 and godmode9 again?

Posted with my LG G5 using Tapatalk

 

[Kyojin]

If you would share more info instead of blaming Plailect, people might be able to help.

- Did you install the noscreeninit version of Aurora's fork?
- Are you chainloading those apps from Luma3DS? Or trying to run them directly? Or something else?

 

[einhuman197]

I restored my firm0/firm1 with godmode9, used a old 11.0 nand Backup. Now I have my old a9lh back <3. Why does everybody say "update!!1"?!? This new a9lh is bullsh!t

Posted with my LG G5 using Tapatalk

 

[Halvorsen]

It's literally the exact same, just that v2 has more space for payloads. You probably installed the no screen init, blame yourself.

 

[OLineGuy]

I restored my firm0/firm1 with godmode9, used a old 11.0 nand Backup. Now I have my old a9lh back <3. Why does everybody say "update!!1"?!? This new a9lh is bullsh!t

Posted with my LG G5 using Tapatalk

It works if you dont f it up. Those payloads dont load only if you used the older safea9lh 2.0 and not 2.0.1

 

[einhuman197]

I used 2.0.1

Posted with my LG G5 using Tapatalk

 

[Kyojin]

I restored my firm0/firm1 with godmode9, used a old 11.0 nand Backup. Now I have my old a9lh back <3. Why does everybody say "update!!1"?!? This new a9lh is bullsh!t

Posted with my LG G5 using Tapatalk

LOL.

 

[The Catboy]

I restored my firm0/firm1 with godmode9, used a old 11.0 nand Backup. Now I have my old a9lh back <3. Why does everybody say "update!!1"?!? This new a9lh is bullsh!t

Posted with my LG G5 using Tapatalk

I am 90% sure you did something wrong and now are blaming everyone else for your problem.

 

[OLineGuy]

I used 2.0.1

Posted with my LG G5 using Tapatalk

then you are using something else outdated... like ctrbootmanager ... it works fine with luma chainloading

 

[The Catboy]

For shits and gigs, I updated the to the latest version, then updated my bootloader. Decrypt9 and all of my payloads are still working.
Edit: The only thing not working is the Gateway payload, which is k because I stopped using it when I realised I had better options.

 

[SirByte]

It's literally the exact same, just that v2 has more space for payloads. You probably installed the no screen init, blame yourself.

Aren't you supposed to install the no-screen-init version when used in combination with Luma3DS?

Quote from the options page: "Screen-init brightness: Only useful if you have a no-screen-init fork of A9LH (like my own). Changes the brightness to be used by Luma3DS's screen-init. It has no effect if your A9LH already has screen-init like dark-samus' fork."

 

[EmperorOfCanada]

I restored my firm0/firm1 with godmode9, used a old 11.0 nand Backup. Now I have my old a9lh back <3. Why does everybody say "update!!1"?!? This new a9lh is bullsh!t

Posted with my LG G5 using Tapatalk

Where is all this peer pressure to update? I havent seen it.

 

[TuxSH]

I used 2.0.1

Not sure.

It was typically a problem with 2.0.0

 

[Deleted User]

Did you download the latest release of D9? Sometimes using old versions can cause issues.

 

[Quantumcat]

Why does everybody say "update!!1"?!?

I'm pretty sure everyone said "no need to update yet as nothing is using the extra space". No one said you should update.

 

[Thelonewolf88]

I restored my firm0/firm1 with godmode9, used a old 11.0 nand Backup. Now I have my old a9lh back <3. Why does everybody say "update!!1"?!? This new a9lh is bullsh!t

Posted with my LG G5 using Tapatalk

Nobody forced you to update and V2 brings nothing to the table at the moment. So it's on you if stuff don't work as expected.

 

[Halvorsen]

[

Aren't you supposed to install the no-screen-init version when used in combination with Luma3DS?

Quote from the options page: "Screen-init brightness: Only useful if you have a no-screen-init fork of A9LH (like my own). Changes the brightness to be used by Luma3DS's screen-init. It has no effect if your A9LH already has screen-init like dark-samus' fork."

No?
The only difference is that you can change screen brightness for Luma settings if you don't install the screeninit version. The noscreeninit version initilizes the screen before Luma3DS loads, so it's better for other payloads like BootAnim9 or Decrypt9 that won't work without screeninit.

 

[SirByte]

[

No?
The only difference is that you can change screen brightness for Luma settings if you don't install the screeninit version. The noscreeninit version initilizes the screen before Luma3DS loads, so it's better for other payloads like BootAnim9 or Decrypt9 that won't work without screeninit.

I don't know about BootAnim9, but Decrypt9 chainloads after Luma initializes the screen so Decrypt9 works fine as a payload on my "old" A9LHv1/Luma n3DS XL. So the real question for @Aurora Wright is: will the next release version of Luma3DS no longer assume it has to initialize the screen so there won't be any flicker or anything of the sort?

 

[astronautlevel]

I don't know about BootAnim9, but Decrypt9 chainloads after Luma initializes the screen so Decrypt9 works fine as a payload on my "old" A9LHv1/Luma n3DS XL. So the real question for @Aurora Wright is: will the next release version of Luma3DS no longer assume it has to initialize the screen so there won't be any flicker or anything of the sort?

Luma3DS doesn't initialize the screen itself unless you tell it to...

 

[SirByte]

Luma3DS doesn't initialize the screen itself unless you tell it to...

Right, but under "v1" of A9LH, it did because you had to use AW's no-screen-init fork to use all functionality (screen brightness) in the Luma options menu. For the new version, AW released both a screen-init and a no-screen-init version. Is it logical to assume that the v2 no-screen-init version works the same in all cases where the v1 no-screen-init worked (EmuNAND9, Decrypt9WIP, etc.) or are the payloads assuming under v2 screen init has already been done?

Edit: oh wait a minute, the confusion is apparently about running these tools "standalone" as their own arm9loaderhax.bin, instead of being chainloaded through Luma. So to rephrase the question: is the no-screen-init version still the preferred way IF you ONLY chainload through Luma?