Hacking Downgrade Custom Firmware, is it possible?

[WiiHoney]

Right, FW 9.2 has worked fine for me so far with GW as i keep emuNAND updated to the latest version.

I need to check v1 and see how it would hold

 

[Temptress Cerise]

Ah OK. From skimming it sounded like he wanted to be on 9.2 because he knew Gateway worked on 9.2.

Actually, I think that might have been his plan, until Hayleia mentioned flashing v1 A9LH. So..... >.>..... I kind of skimmed it too, and came in late.

 

[Quantumcat]

Right, FW 9.2 has worked fine for me so far with GW as i keep emuNAND updated to the latest version.

I need to check v1 and see how it would hold

If you are just going to use menuhax with Gateway, all your effort setting up a9lh was wasted. Seems a shame.

 

[astronautlevel]

I'm opposed to the three stage files, in my opinion boot selection shouldn't be done by a stage2 payload, and should instead be done by a stage3 payload. No point in overcomplicating your setup when you could literally drop the GW arm9loaderhax.bin into a folder and rename it and have the same effect.

 

[Temptress Cerise]

I'm opposed to the three stage files, in my opinion boot selection shouldn't be done by a stage2 payload, and should instead be done by a stage3 payload. No point in overcomplicating your setup when you could literally drop the GW arm9loaderhax.bin into a folder and rename it and have the same effect.

Same here. But I rather link that at least. I can't link Kazuma77 guide cause its on that iso site whose name shall not be named.

 

[WiiHoney]

I am back, couldnt do much to yls8.mtheall.com being down.

That wasn't even what I was thinking about actually. Just a regular v1 setup should work with Gateway's payload. As long as it isn't v2.
The three stage 2 thing was for the times when there wasn't even a payload.

And I just checked, you can find the old links by cloning plailect's guide and seeing an old version of it. Or maybe there is a way to do it directly from the browser but I don't know, I don't use github very often...

edit found it. https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax)/2aa4abe44b812609c4482c87b3fb3d9257fb9053
Though beware, you need a SafeA9LHInstaller that is compatible with v1, not one that is compatible with v2, otherwise you will brick.

Where can i find the SafeA9LHInstaller that is compatible with payload_stage1.bin downloaded from the link above?

I am receiving an error of incompatibility of SafeA(HLInstaller v2.0.1 and the payload_input.zip files from that link.

--------------------- MERGED ---------------------------

I tried both files with the same error:
SafeA9LHInstallerv1.5.2.7z and SafeA9LHInstallerv2.0.1.7z

 

[Hayleia]

Wow, you're lucky you only got errors and no brick. I guess it's not called safe for no reason but still.
Well anyway, no idea, because 1.5.2 is the one I used and it worked.
Did you completely clean the a9lh folder (well, just keeping the OPT.bin) before extracting data_input and payload_input in there? And did you extract them both actually? Because the new guide doesn't use "payload_input" so maybe you skipped that.

 

[WiiHoney]

Incase it helps, this is the setup with bootctr9, I use with my Gateway boot as default and boot Luma 3DS with L, R or Select, Uncart with X, Hourglass with Start and Emunand9 with Y. So long as you don't have an issue with a short boot screen, then this would probably ideal for your needs.

Download BootCTR from here: https://github.com/hartmannaf/BootCtr9/releases/tag/v0.4.1-alpha_

And put all the files onto the root of your SD card.

Replace the text in the boot_config.ini with the text in the below spoiler.

Spoiler: boot_config.ini

;Comments starts with ";" or "#", so you need to remove it first to the
;line actually do something.
[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 3
boot_splash_image = /arm9loaderhax/image2.bin
screenBrightness = 0xFF

[DEFAULT]
path = /GW.bin
delay = 100
offset = 0
payload = -1
splash = 1

[KEY_L]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
splash = 1

[KEY_R]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
screenEnabled = 1
splash = 1

[KEY_SELECT]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
screenEnabled = 1
splash = 1

[KEY_X]
path = /Uncart.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_Y]
path = /Emunand9.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_START]
path = /Hourglass.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1


;Each key can be defined using a section, like the example below. Section
;names must be ALL caps, and between "[]". Valid keys:
; * Common keys: KEY_A, KEY_B, KEY_X, KEY_Y, KEY_L, KEY_R, KEY_SELECT,
; KEY_START.
; * D-PAD: KEY_DUP, KEY_DDOWN, KEY_DLEFT, KEY_DRIGHT.
;You MUST set at least "path" for each section, and it is the ONLY option you
;should set in the majority of cases.
;You may pass a .3dsx file or a .dat/.bin payload, the file type is detect
;automatically based on extension. Double check the path, since it must be
;correct (including caps).
;[KEY_CPAD_LEFT] ;MUST BE ALL CAPS
;path = /And/Respect_Caps_in_Path.3dsx


;Boot examples for almost every CFW out there.
;You can use both .3dsx files or binary (.bin, .dat) payloads
;[KEY_A]
;path = /rxTools/sys/code.bin
;[KEY_B]
;path = /Cakes.dat
;[KEY_X]
;path = /3ds/GW/GW.3dsx
;[KEY_Y]
;path = /ReiNand.dat

;An important remark: the majority of CFWs set L button to show menu instead
;of autobooting. So it is generally a bad idea to set L button to CFW boot,
;or the CFW menu will be shown instead of booting directly to CFW.
;[KEY_L]

Put the Gateway payload on the root of the SD and name it "GW.bin"

Put the Luma payload on the root of the SD and name it "Luma.bin"

Put the Uncart payload on the root of the SD and name it "Uncart.bin"

Put the Emunand9 payload on the root of the SD and name it "Emunand9.bin"

Put the Hourglass9 payload on the root of the SD and name it "Hourglass.bin"

It works for me. Might not be for you, but will allow you to boot gateway by default and Luma with L or R for when you want to update the sysnand firmware.

Also, make sure the gateway LAUNCHER.DAT is on the root of the SD card too.

Hope it helps.

I updated back to A9HL v2 and your steps were perfect!

Thank you

 

[KJ1]

Incase it helps, this is the setup with bootctr9, I use with my Gateway boot as default and boot Luma 3DS with L, R or Select, Uncart with X, Hourglass with Start and Emunand9 with Y. So long as you don't have an issue with a short boot screen, then this would probably ideal for your needs.

Download BootCTR from here: https://github.com/hartmannaf/BootCtr9/releases/tag/v0.4.1-alpha_

And put all the files onto the root of your SD card.

Replace the text in the boot_config.ini with the text in the below spoiler.

Spoiler: boot_config.ini

;Comments starts with ";" or "#", so you need to remove it first to the
;line actually do something.
[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 3
boot_splash_image = /arm9loaderhax/image2.bin
screenBrightness = 0xFF

[DEFAULT]
path = /GW.bin
delay = 100
offset = 0
payload = -1
splash = 1

[KEY_L]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
splash = 1

[KEY_R]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
screenEnabled = 1
splash = 1

[KEY_SELECT]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
screenEnabled = 1
splash = 1

[KEY_X]
path = /Uncart.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_Y]
path = /Emunand9.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_START]
path = /Hourglass.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1


;Each key can be defined using a section, like the example below. Section
;names must be ALL caps, and between "[]". Valid keys:
; * Common keys: KEY_A, KEY_B, KEY_X, KEY_Y, KEY_L, KEY_R, KEY_SELECT,
; KEY_START.
; * D-PAD: KEY_DUP, KEY_DDOWN, KEY_DLEFT, KEY_DRIGHT.
;You MUST set at least "path" for each section, and it is the ONLY option you
;should set in the majority of cases.
;You may pass a .3dsx file or a .dat/.bin payload, the file type is detect
;automatically based on extension. Double check the path, since it must be
;correct (including caps).
;[KEY_CPAD_LEFT] ;MUST BE ALL CAPS
;path = /And/Respect_Caps_in_Path.3dsx


;Boot examples for almost every CFW out there.
;You can use both .3dsx files or binary (.bin, .dat) payloads
;[KEY_A]
;path = /rxTools/sys/code.bin
;[KEY_B]
;path = /Cakes.dat
;[KEY_X]
;path = /3ds/GW/GW.3dsx
;[KEY_Y]
;path = /ReiNand.dat

;An important remark: the majority of CFWs set L button to show menu instead
;of autobooting. So it is generally a bad idea to set L button to CFW boot,
;or the CFW menu will be shown instead of booting directly to CFW.
;[KEY_L]

Put the Gateway payload on the root of the SD and name it "GW.bin"

Put the Luma payload on the root of the SD and name it "Luma.bin"

Put the Uncart payload on the root of the SD and name it "Uncart.bin"

Put the Emunand9 payload on the root of the SD and name it "Emunand9.bin"

Put the Hourglass9 payload on the root of the SD and name it "Hourglass.bin"

It works for me. Might not be for you, but will allow you to boot gateway by default and Luma with L or R for when you want to update the sysnand firmware.

Also, make sure the gateway LAUNCHER.DAT is on the root of the SD card too.

Hope it helps.

Does it still shows GW image/logo while booting, like A9LH v1?

 

[TheBroCode]

Does it still shows GW image/logo while booting, like A9LH v1?

I've just followed these instructions, and it does

 

[KJ1]

I've just followed these instructions, and it does

Okay, so there is nothing as of now to update to v2..