So uh.. decent news? Gateway has released a public Private Beta of their 4.0 build! This is the second round, and everyone can test! (Although I wouldn't advise that you try this before we know more about the beta in question.) According to the Gateway Team,
Some things to clear up:
-3DS CAN be powered on without GW Card, but it boots the GW menu.
-If you're experiencing a black screen using Luma's chainloader, you'll have to reformat with emuNAND9 using the Format SD (no emuNAND) option.
-Gateway's implementation does NOT exactly lock you to their cart. Every tool you have access to from the Gateway menu is free and accessible to all with or without a cart.
What we know/can assume:
-Updating sysNAND after GW A9LH will either brick the 3DS, or remove A9LH from the system.
-It's possible to have 11.0 on Gateway sysNAND while still maintaining A9LH, it requires you flash an 11.0 NAND.bin during the A9LH install process, or updating to 11.0 sysNAND with a different CFW that supports FIRM protection.
-The downgrader is extremely unstable, but it's possible the GW Team has stabilized it. (we won't know until testers confirm.)
-A reddit user has confirmed that they were able to install A9LH using only Gateway's tools on their N3DS, so i guess they're doing something right for once
-No GBA support, although someone states that they can run GBA in sysNAND.
-DS Games and Flashcards may or may not work in emuNAND, there are mixed reports of this.
-N3DS users on 8.1J now have a solution for their consoles, they can use Gateway in sysNAND mode on 4.0a/b to update to a full 9.2 build with profi200's sysUpdater
-n3DS can't upgrade to 10.3 while o3DS can.
-o3DS will be upgraded to 10.3 before downgrading to 2.1 for OTP.bin, due to an error with direct downgrading from 9.2.
So far, not much is known about this new beta aside from what the GW team has told us. If you can test, please report your tests so I can update this thread with any new information that rolls by!
-The Gateway Team has released an arm9loaderhax.bin file on their website. It is confirmed to be working with current A9 payloads.
There's an ok chance that Gateway will fix their problems, as this is a beta test however,
it is much too early to make any final judgments about this whole release.
Please inform me of what I'm missing. Will update post. (pls no memes b0ss)
P.S. No one cares about what you like/dislike, what you think is worth it or not, or even why you want to use one CFW over the other. This thread has one purpose, and that's to document the status of GW's A9LH implementation as well as help those who are going through with it. I asked for a civil thread, so please don't bring your CFW vs. GW replies here.
Some things to clear up:
-3DS CAN be powered on without GW Card, but it boots the GW menu.
-If you're experiencing a black screen using Luma's chainloader, you'll have to reformat with emuNAND9 using the Format SD (no emuNAND) option.
-Gateway's implementation does NOT exactly lock you to their cart. Every tool you have access to from the Gateway menu is free and accessible to all with or without a cart.
What we know/can assume:
-Updating sysNAND after GW A9LH will either brick the 3DS, or remove A9LH from the system.
-It's possible to have 11.0 on Gateway sysNAND while still maintaining A9LH, it requires you flash an 11.0 NAND.bin during the A9LH install process, or updating to 11.0 sysNAND with a different CFW that supports FIRM protection.
-The downgrader is extremely unstable, but it's possible the GW Team has stabilized it. (we won't know until testers confirm.)
-A reddit user has confirmed that they were able to install A9LH using only Gateway's tools on their N3DS, so i guess they're doing something right for once
-No GBA support, although someone states that they can run GBA in sysNAND.
-DS Games and Flashcards may or may not work in emuNAND, there are mixed reports of this.
-N3DS users on 8.1J now have a solution for their consoles, they can use Gateway in sysNAND mode on 4.0a/b to update to a full 9.2 build with profi200's sysUpdater
-n3DS can't upgrade to 10.3 while o3DS can.
-o3DS will be upgraded to 10.3 before downgrading to 2.1 for OTP.bin, due to an error with direct downgrading from 9.2.
So far, not much is known about this new beta aside from what the GW team has told us. If you can test, please report your tests so I can update this thread with any new information that rolls by!
-The Gateway Team has released an arm9loaderhax.bin file on their website. It is confirmed to be working with current A9 payloads.
There's an ok chance that Gateway will fix their problems, as this is a beta test however,
it is much too early to make any final judgments about this whole release.
Please inform me of what I'm missing. Will update post. (pls no memes b0ss)
P.S. No one cares about what you like/dislike, what you think is worth it or not, or even why you want to use one CFW over the other. This thread has one purpose, and that's to document the status of GW's A9LH implementation as well as help those who are going through with it. I asked for a civil thread, so please don't bring your CFW vs. GW replies here.
Last edited by CreAtor135,
