Make a dump of your gw's a9lh nand, open it in HxD > goto B800000 and select gw's stage, should be from B800000 to B802EF (9456 Bytes).
This is what gets executed on booting to start launcher.dat.
I will check it out. Thanks for the info.
Make a dump of your gw's a9lh nand, open it in HxD > goto B800000 and select gw's stage, should be from B800000 to B802EF (9456 Bytes).
This is what gets executed on booting to start launcher.dat.
Exactly. They didn't try to monopolize with MenuHax. Just put out the .3dsx file. So it seems out-of-place for them to be reinventing the wheel this time. They have to know lots of users have already installed A9LH. I think they will put out a .bin file ultimately. If they weren't already planning one, they probably will be now. They do tend to listen when enough customers complain.
I will check it out. Thanks for the info.
I found a way how GW A9LH can co-exist with our current A9LH.
As for this, i've extracted from GW A9LH's NAND the Stage from B800000 (9456 Bytes)
and tested to insert it into my non GW A9LH NAND. GW A9LH boots now Launcher.DAT
There is only one thing to do >> add a button combo to load it from another offset.
Something is wrong with your hardmod or your system. I've been flashing back and forth since last night. No problems. Flashing right now from GW_a9lh to my Luma a9lh backup. Reboot your PC, then unplug any iPhones or other card readers, and try again.If they do, hopefully they'll provide some sort of way out for people that are now stuck like I am. It was a low blow to lock out hardmods. In a day or so I might try reinstalling 9.0 FIRM via PlaiSysUpdater; in theory it should work as long as Gateway didn't issue some sort of lock command to the NAND chip itself, since 9.0 uses NAND key1, not key2.
Thanks for finding this out Please provide more information. It's not clear if you inject the GW stage.bin into your non-GW a9lh NAND or if you extracting the stage and load it up with a boot manager. If it's the former then it's not that helpful though because you still lock out the possibility to use other cfw with it.
Is the stage.bin per console encrypted (not talking about xorpads)? If yes could you share a decrypted copy?
EDIT: or do you inject the stage.bin into a different offset and load it up with a payload which jumps to different offsets. If it is, then it's pretty clever . That would make most sense.
Never said anything about bootmanager > injected into nand.bin, or to be exact, opened the disk drive in hxd via hardmod and connected new3ds in write mode.
The whole thing? Do I need to decrypt it first?Make a dump of your gw's a9lh nand, open it in HxD > goto B800000 and select gw's stage, should be from B800000 to B802EF (9456 Bytes).
This is what gets executed on booting to start launcher.dat.
Never said anything about bootmanager > injected into nand.bin, or to be exact, opened the disk drive in hxd via hardmod and connected new3ds in write mode.
It should work for everyone since its just gw's stage0x5C000.bin
Sector 5C000 = Offset B800000
Sector 5A000 = Offset B400000
Old3DS can use Home Button but New3DS fails since i2c is different initialized.
I just modified aurora's installer and switched Home Button out for Button_A.
Any way we could get one pre-compiled with B? I use A to go back to SysNAND when I exit System Settings on EmuNAND occasionally.
With all this, just as someone who looks from the side as I missed Gateway bandwagon when it started. Back then I was envious, back then when Gatway was new I wanted one if I had just also not updated my 3DS.
But now, I have to honestly ask what is the point in using or remaining a gateway user, current CFW's do things better, have better update response especially if you just follow the nightlies of your favorite non-RXtools CFW, and bunch of other features.
That is; does Gateway honestly currently have still some features that "pay back" it's shortcomings?