Liked because you didn't create a new noob thread asking about it. Asking in a thread where it's on topic, even if it's been asked before, is compeltely acceptable.
Hacking The status of Gateway and A9LH
- Thread starter CreAtor135
- Start date
- Views 192,868
- Replies 1,476
- Likes 9
Could I restore a v2 sysnand backup after reinstalling v1 from a fresh 9.0 sysnand backup? Or would that brick? I just want to keep my games and stuff.
Just completed the A9LH install(FINALLY after 12 hours). Glad to have finally made the jump. This is awesome! I just hope that it's updated in the future when new system updates come out. As I rely only on CIA files really, I'm giving the Gateway card to a friend who wants to get a N3DS in the future as he's not too technical and it's more user friendly for him
Last edited by skydancer93,
There's no reason to be telling people to compile it for themselves. Just like there wasn't last time. All they need are the "payload_stage1.bin" and "payload_stage2.bin" files, not the console-specific installer that gets built. The same misconception happened when we were using DarkSamus payloads to get GW to work. Until I proved that the same "payload_stage1.bin" and "payload_stage2.bin" were generated regardless of which console's "otp.bin" I used. I guess I have to do it again, just to prove these aren't console-specific either. I really hate compiling crap. I was hoping someone else would do it for once.
EDIT: I've got the non-console-specific stage payloads (you don't even need the pack tool to get far enough into the compile to get them). Something's not right with them though. They don't seem to install right with Safe A9LH Installer v2 at all. It doesn't complain about the stage 1 payload, but it doesn't work once installed, either (the light comes on, but nothing happens). It will shut off without a card in the slot though (had to leave it in to hardmod flash it). Using v1 bricks for certain. I guess it's possible that delebile's fork is incompatible with BootCTR9. In which case, it's trading for an even bigger problem. You can get around the GW problem with Aurora's fork just by using BootCTR9 after all.
Last edited by Kazuma77,
I tried it with 3.7.1 and 4.0b. Gateway runs. I loaded a ROM on each. It played. I can't be certain there aren't any stability issues that only show up after a couple of hours or something, but it seems to work fine.
God, I love BootCTR9, so amazing, but I am still going to hold off on v2, as there's really nothing calling for it. But it's really nice to know, that even if GW doesn't update their A9LH.bin, that I won't need to change my setup at all.
Thanks. I'm still on V1 using Luma chainloading for my main n3ds console but I just done a v2 install on my 2nd o3ds console yesterday and haven't got around to trying you're config pack yet, and it is the modified bootctr9 isn't it for V2 to enable gw.
There's nothing modified about mine. Just the original release from Github. That's the one I include, and it seems to work. I advise getting the one from the iso site. It includes the modified Safe A9LH Installer in case you need to downgrade to v1. I can't include all 5 files here, and I don't want people to brick trying to downgrade without having the right files.
Also, I tried compiling delebile's version just for the stage payloads. Installing them with Safe A9LH Installer v2 gets the screen to light up, but it freezes. It's like BootCTR9 doesn't like it for some reason. Trying to install them with v1 bricks as advertised.
Slightly off topic: Finally got my bricked AUS N3DS XL reflashed (finally got the drive to show up using my HP Slate tablet, lol, but I still had to time it just right -- it's like you have just one second to connect the reader after the "200" blue screen shows up, or that's what it seems like anyway). But now that that's done, well, I lost one of the thumbstick screws in the process. Anyone know what length those screws are? I also somehow managed to knock one of the ribbon clamps loose on one side, then subsequently send it flying trying to snap the hinge back in. Fortunately, it's the one that other cable goes right over the top of, so it's probably not going anywhere.
EDIT: Looks like I did need that damn clamp. No lower screen. Argh. Could be all week finding that thing. Why is hard modding the N3DS XL such a bigger pain in the ass than the O3DS XL?
Last edited by Kazuma77,
I followed the Plailect’s guide and succeeded only to find out that v2 al9h I installed is incompatible with current GW’s payload. I’m not quite sure what should I do to downgrade it to v1, any pointers?
Also, I did this on a separate SD card, so my old GW’s EmuNAND is on another card. Is there a way to flash it to my current setup / use it at all?
Also, I did this on a separate SD card, so my old GW’s EmuNAND is on another card. Is there a way to flash it to my current setup / use it at all?
You can use a version of safe9lhinstaller to overwrite v2 files to v1. But make sure you use V1 versions of stage 1 and stage 2 bins as you will brick otherwise (don't mix n match) However, I recommend using decrypt9 to flash you're 9.2 sysnand original and then use a V1 installer with v1 files. Be careful of not mixing v1 files with a v2 installer, keep them separate from the ones you got when you followed the guide.
Last edited by retrofan_k,
- Joined
- Jun 24, 2012
- Messages
- 1,039
- Trophies
- 1
- Age
- 32
- Location
- Kanto <- Hyrule -> Unova
- Website
- maxlempira.deviantart.com
- XP
- 1,751
- Country
Hello, between all theses pages, I can't really find an answer.
I've fully downgraded a 2DS without any problem following Gateway's Guide and then installed A9LH with Plailect's one.
Now I wanted to do the same with my N3DS, and I got a few problems, first I should use my OoT3D Copy to launch GW Menu, but ok. When I get to the part of the install emuNAND to SysNAND (I guess, first time launching A9LH Installer on GW's Menu) The message "emuNAND isn't 2.x yet" Or something like that, and then the system shut off, when I try to go to emuNAND, I only get a black screen, is it any fix to this? Should I start using Menuhax instead of Oothax? Thanks in advance!
I've fully downgraded a 2DS without any problem following Gateway's Guide and then installed A9LH with Plailect's one.
Now I wanted to do the same with my N3DS, and I got a few problems, first I should use my OoT3D Copy to launch GW Menu, but ok. When I get to the part of the install emuNAND to SysNAND (I guess, first time launching A9LH Installer on GW's Menu) The message "emuNAND isn't 2.x yet" Or something like that, and then the system shut off, when I try to go to emuNAND, I only get a black screen, is it any fix to this? Should I start using Menuhax instead of Oothax? Thanks in advance!
- Joined
- Jul 13, 2008
- Messages
- 1,028
- Trophies
- 1
- Age
- 30
- Location
- Insomnia
- Website
- www.gbatemp.net
- XP
- 1,131
- Country
Uh what your explaining isn't making much sense... From what I can tell is that you missed a step when installing a9lh and using Gateways method then Plailect's guide isn't a good idea. Is your EmuNAND still on 2.1? Did you actually install a9lh?
- Joined
- Jun 24, 2012
- Messages
- 1,039
- Trophies
- 1
- Age
- 32
- Location
- Kanto <- Hyrule -> Unova
- Website
- maxlempira.deviantart.com
- XP
- 1,751
- Country
Sorry, let me clear what I've done.
On my 2DS I've followed the steps from Gateway until 2.x SysNAND, from there, I just installed A9LH from Plailect's Guide to be able to use Luma and Gateway. My 2DS is fine now.
My problem:
On my N3DS (9.2.0-20U), I followed the steps from Gateway:
- Boot into GATEWAY 3DS menu using Oothax
- Pick the format emuNAND option from the menu and create a NAND Backup (Which I can confirm that works)
- Boot into GATEWAY (emuNAND) mode using Oothax again
- Make sure you have WiFi configured and working correctly
- Bring up the OSD, select GATEWAY Time Machine
- Launch GATEWAY Time Machine, select 2.x downgrade
- Boot back into GATEWAY 3DS menu after rebooting (Again with Oothax)
- Select A9LH Installer menu option
"FATAL ERROR:
Your EmuNAND is not 2.x yet
Press A to continue"
And then my N3DS shut off, I can start normally my N3DS, but if I try to go to EmuNAND, I'm getting a Black Screen. I've already tried reinstalling EmuNAND, erasing "Nintendo 3DS" folder.
I haven't tried Menuhax yet. But, should I? or is it there any fix for this? Am I missing something?
- Joined
- Jul 13, 2008
- Messages
- 1,028
- Trophies
- 1
- Age
- 30
- Location
- Insomnia
- Website
- www.gbatemp.net
- XP
- 1,131
- Country
Well you did something wrong. I didn't use my Gateway to downgrade my n3DS but I do recommend just using Plailect's guide... Menuhax probably wont fix your problem so I say start from step 1 on Plailect's guide, then use gateways arm9loaderhax.bin.
- Joined
- Jun 24, 2012
- Messages
- 1,039
- Trophies
- 1
- Age
- 32
- Location
- Kanto <- Hyrule -> Unova
- Website
- maxlempira.deviantart.com
- XP
- 1,751
- Country
Well... thanks, I find quiet complicated Plailect's Guide (Too much info
) But I'll use it if there's no other way.
- Joined
- Jul 13, 2008
- Messages
- 1,028
- Trophies
- 1
- Age
- 30
- Location
- Insomnia
- Website
- www.gbatemp.net
- XP
- 1,131
- Country
Using Gateway's method is more dangerous and its still only a "Private Beta". The massive amount of information is the entire point about Plailect's guide and downgrading a n3DS is much more dangerous than a o3DS or 2DS. Follow the guide closely and you will have the perfect CFW solution for your n3DS.Well... thanks, I find quiet complicated Plailect's Guide (Too much info
Similar threads
- No one is chatting at the moment.
