D
Deleted User
Guest
Nope, making it so I need the red card to boot? Screw that, Plailect's guide is great and works a treat now, and is even simpler than before
I did it on my n3ds and it worked perfectly fine (I reverted to an old nand dump and use community A9LH now, but I tested it out and it works fine with n3ds). It just marries your 3ds to a gateway red card, and it's just not cricket.... GWTM A9LH has a 100% of bricking N3DS's
Restore an old nand dump and proceed with plailect's guide.Actually, is there any way to go from an A9LH install with "GW red card mandatory" to a standard install that doesn't require GW card?
No I mean to go from an A9LH install with "GW red card mandatory" to a standard A9LH install, ofc without re-doing everything..Restore an old nand dump and proceed with plailect's guide.
If you have your OTP I believe you can just install regular A9LH, else you need to restore an old nand dump and redo it. But I'm not sure whether it may brick from being gateway, I've not heard of anybody saying they did it.No I mean to go from an A9LH install with "GW red card mandatory" to a standard A9LH install, ofc without re-doing everything..
Hey hey hey now, nothing wrong with Gateway itself, just the Time Machine method
Well, if you were talking to me-The initial release of GW A9LH installation DID have 100% brick rate on o3ds because they didn't properly modify the 2.1 o3ds files to work on n3ds. It may be different now, but people aren't saying it when it never happened, because it did happen.
For now, their tools are far too brick prone. I wouldn't say they brick as often as people like to believe, but I do believe they are more prone to bricking than the community tools.
Along with that, the GW A9LH marries your console to Gateway, which is just stupid as there are so many tools that can boot on the community A9LH that GW A9LH simply doesn't have an equivalent for.
And to add to that, even Gateway themselves say you shouldn't use it unless you have a hardmod to recover. Why? Because the software is still beta, meaning it still isn't fully tested.
Plus Gateway's CFW does not have FIRM write protection, meaning sysNAND should not be used due to the fact that if you accidentally update you will lose A9LH.
At this point I would never suggest GW A9LH to anyone, especially when you can boot gateway from the community A9LH anyway. Until they can offer anything even close to what the community tools offer, I would just stick with community A9LH and then loading gateway with that if you want to use gateway's CFW.
My message was not meant for you. And I did mean n3ds bricked with the initial release of time machine. I just somehow managed to accidentally type o3ds.Well, if you were talking to me-
I said their installation of a9lh in general was faster and simpler, had it been more polished, everyone could've used it to retrieve their otp.bin faster than community's tools, then restore a backup to get rid of Gateway's a9lh. Simple.
Also it wasn't the o3ds that had 100% brick rate. It was n3ds because they forgot to unbrick emuNAND before cloning it to sysNAND.
Despite all this, however, like I've previously said with the new update to plailect's guide, any edge Gateway possibly had is now gone.