Hacking Can't Boot Gateway Mode after install A9LH

  • Thread starter Thread starter jatikeren
  • Start date Start date
  • Views Views 12,366
  • Replies Replies 98
If you don't have a NAND backup you're pretty stuck. If you have a hardmod (and a backup of your system as it is now) and your sysNAND is on 9.0-9.2, try using SafeArm9Installer.3dsx from homebrew to "update" your a9lh installation with v2. However I have no idea if it would work and you definitely should not do it without a hardmod. If you do do it, please report back to inform us if it worked or bricked!

Edit: the Time Machine page on Gateway's website says that users are advised to have both a known valid NAND backup before proceeding AND a hardmod ... hopefully you have at least one of these! :-)
how i can do that ??
updateing to v2 A9LH so i can use LUMA ??
 
Dammed Gateway -____-
Well you have to shoulder some of this blame-

You chose to not backup your NAND and lose your OTP, even when there are specified details to do so. And installing the GW A9LH, at that, after countless warnings.
 
Well you have to shoulder some of this blame-

You chose to not backup your NAND and lose your OTP, even when there are specified details to do so. And installing the GW A9LH, at that, after countless warnings.
sorry for that...
becasue accidentaly formated my sd card so nand.bin and otp are gone...
and on the tutorial GW never tell me it need a Red Card to boot...
atough GW A9LH just like LUMA.... -___-
but its totally different...
 
Well well, hold your horses. This is a known issue right now, that will only happen if you install A9LH using the new method, restore (keep A9LH) to your previous SysNAND, then set up the GW type EmuNAND (which only GW users use right now) after.

I'll tell you the fix, but in turn I ask you to help other users having this issue and point them here.
  • Make a backup of your SysNAND (minimum size is enough)
  • Open said backup in a hex editor
  • Now be careful, please
  • Change the byte at 0x300 (the ASCII sequence at that point is 'NCSD') to something other than N
  • Restore this backup to your EmuNAND using Hourglass9, EmuNAND9, Decrypt9 or even GodMode9 (your choice)
  • Fixed!
As i said, please point any users having the same issue here. You could also use GodMode9 to speed up the process and do it all on console, but no help for that,
 
  • Like
Reactions: Quantumcat
Well well, hold your horses. This is a known issue right now, that will only happen if you install A9LH using the new method, restore (keep A9LH) to your previous SysNAND, then set up the GW type EmuNAND (which only GW users use right now) after.

I'll tell you the fix, but in turn I ask you to help other users having this issue and point them here.
  • Make a backup of your SysNAND (minimum size is enough)
  • Open said backup in a hex editor
  • Now be careful, please
  • Change the byte at 0x300 (the ASCII sequence at that point is 'NCSD') to something other than N
  • Restore this backup to your EmuNAND using Hourglass9, EmuNAND9, Decrypt9 or even GodMode9 (your choice)
  • Fixed!
As i said, please point any users having the same issue here. You could also use GodMode9 to speed up the process and do it all on console, but no help for that,
I apologise for my lack of understanding, but what does this fix? (Needing a GW card to boot after installing a9lh using their method?)
 
Why do users constantly try to install A9LH without making backups OR copying them to another place (If you're on an android/tablet there is googledrive, dropbox etc)? The guide(s) only warn you like every other sentence how important they are. I see this on almost every [Bricked] post. I don't have a backup, my SD was too small, I forgot to transfer it before formatting, I skipped it because I had no games etc etc...... It just makes me wonder because I thought this was the MAIN reason to install A9LH in the first place. Why install it if you don't save backups to save you in case you brick anyway?
 
  • Like
Reactions: alpha_noj
I apologise for my lack of understanding, but what does this fix? (Needing a GW card to boot after installing a9lh using their method?)
Oh.

Well, I misunderstood this thread and gave the solution to another problem :D.

As for GW... Their implementation is beyound shitty, you need A9LH v1 for it to work. I'd suggest you complain to them, but will it have an effect? Will it? :)
 
Oh.

Well, I misunderstood this thread and gave the solution to another problem :D.

As for GW... Their implementation is beyound shitty, you need A9LH v1 for it to work. I'd suggest you complain to them, but will it have an effect? Will it? :)

Not exactly true... @liomajor released a a9lhv2 fork which works with up to three bootloaders+gateway (multiple stage2)
Those things are just going under between "a9lh install stuck1111!111" "lost otp-nand because I'm dumb" and of course "I need YT tut plz, can't read" threads
 
Last edited by GothicIII,
Oh.

Well, I misunderstood this thread and gave the solution to another problem :D.

As for GW... Their implementation is beyound shitty, you need A9LH v1 for it to work. I'd suggest you complain to them, but will it have an effect? Will it? :)
I was wondering of you could tell us what would happen if a user with Gateway a9lh and sysNAND on 9.0+ were to use SafeArm9Installer.3dsx to "update" to normal a9lh v2. Would it be a definite brick? Could it work to get rid of Gateway? A user earlier installed Gateway a9lh, and has no cartridge or previous NAND backup.
 
Why do users constantly try to install A9LH without making backups OR copying them to another place (If you're on an android/tablet there is googledrive, dropbox etc)? The guide(s) only warn you like every other sentence how important they are. I see this on almost every [Bricked] post. I don't have a backup, my SD was too small, I forgot to transfer it before formatting, I skipped it because I had no games etc etc...... It just makes me wonder because I thought this was the MAIN reason to install A9LH in the first place. Why install it if you don't save backups to save you in case you brick anyway?

I hear you. I almost made that mistake because my SD is too small. Ended up using my 16GB SD that I use with Gateway instead, just to be on the safe side. Better a bit more work for safety's sake.
 
first i want to flash CTRNAND 2.1 to it... for just get rid of A9LH ( if it can be done )
second... i dont have any NAND Backup or OTP backup...
Search your OTP on the console (not red card) SD card the OTP.BIN. Gateway installer dumps it before installing.

Enviado desde mi ZTE Blade S6 Flex mediante Tapatalk
 
Well well, hold your horses. This is a known issue right now, that will only happen if you install A9LH using the new method, restore (keep A9LH) to your previous SysNAND, then set up the GW type EmuNAND (which only GW users use right now) after.

I'll tell you the fix, but in turn I ask you to help other users having this issue and point them here.
  • Make a backup of your SysNAND (minimum size is enough)
  • Open said backup in a hex editor
  • Now be careful, please
  • Change the byte at 0x300 (the ASCII sequence at that point is 'NCSD') to something other than N
  • Restore this backup to your EmuNAND using Hourglass9, EmuNAND9, Decrypt9 or even GodMode9 (your choice)
  • Fixed!
As i said, please point any users having the same issue here. You could also use GodMode9 to speed up the process and do it all on console, but no help for that,
how to Access Hourglass9, EmuNAND9, Decrypt9 or even GodMode9 in GW mode.. ????
i can't access one of them...
 
how to Access Hourglass9, EmuNAND9, Decrypt9 or even GodMode9 in GW mode.. ????
i can't access one of them...
If you have a 9.2 NAND, use homebrew. You can't use the A9LH payloads on a 3DS with Gateway A9LH installed and you can't use the homebrew versions (.3dsx) on a NAND over 9.2.
 
If you have a 9.2 NAND, use homebrew. You can't use the A9LH payloads on a 3DS with Gateway A9LH installed and you can't use the homebrew versions (.3dsx) on a NAND over 9.2.
my NAND is 9.2 use homebrew just flash red.. and back to homebrew menu over and over again
 
my NAND is 9.2 use homebrew just flash red.. and back to homebrew menu over and over again
Did you downgrade in the past? Maybe an incomplete downgrade (flashing red and returning to the homebrew launcher is what happens if the firmware is too high). Try the homebrew downgrade checker and report back.
 

Site & Scene News

Popular threads in this forum