You could send the nand file and 3ds to a hardmodder.I have a NAND, but i dont solder well. Im definitivelly screwed.
You could send the nand file and 3ds to a hardmodder.I have a NAND, but i dont solder well. Im definitivelly screwed.
A friend gave me this console because he bought the New model and, he lend it to a unproffesional shop, who for changing an L button, screwed anything. Its very difficult to open the console. The screws of the battery plate are in very bad condition, but the console works flawlessly.You could send the nand file and 3ds to a hardmodder.
Wait a minute,i updated to 11.3 sysnand from luma3ds and everything is fine.Gateway has no firm protection. You wiped off al9h from your console buddy :/
This is not true. A9LH doesn't protect itself (community a9lh or gateway a9lh). What protects A9LH is the CFW. Luma does it, Gateway CFW does not. So that's why Luma users do not complain about losing their A9LH and Gateway users may complain about it.On every startup, 11.3 attempts to overwrite A9LH. This normally means absolutely nothing because A9LH boots before the firmware and protects itself. This coupled with auto-shutdown if .bin files aren't present/no SD card makes it that in almost all circumstances, you cannot run a setup where A9LH is overwritten. However, Gateway's version of A9LH is sadly one such exception because it does NOT protect the firmware. Nor does Gateway offer a warning about this anywhere on the website.
It is a known fact that booting sysNAND with Gateway's loader on 11.3 bricks the console. Because there is no protection, the firmware attempts to remove A9LH. Perhaps it is trying to patch vulnerable files. Whatever the case, the result is corruption. Which renders the console unbootable.
If it is a O3DS: A9LH wipe.Wait a minute,i updated to 11.3 sysnand from luma3ds and everything is fine.
so if i tried to boot to gateway now i will brick my 3ds or i just can't boot to gateway?
Well first it won't work since Gateway doesn't support 11.3, so save some effort and don't do it.Wait a minute,i updated to 11.3 sysnand from luma3ds and everything is fine.
so if i tried to boot to gateway now i will brick my 3ds or i just can't boot to gateway?
Why are you so upset with Gateway? This issue has been covered in countless threads since the launch of 11.3. Sure it's not ok that Gateway doesn't have FIRM0/1 protection. But it's completely your fault for not researching an update that been part of the scene for over a month now.I'm fucking finished with gateway. Been a supporter from day 1 with 2 cards. I'm gonna sell them now. There last comment on there site said an update will be 2 weeks max and that was almost 4 weeks now. There a joke in the scene now.
I previously updated with Luma, a month ago. Yesterday i entered GW sysnand. Blackscreen (doesnt work in 10.3) and A9 wipe.Well first it won't work since Gateway doesn't support 11.3, so save some effort and don't do it.
Second, as the OP reported, booting sysNAND with a CFW that doesn't protect a9lh will make you lose a9lh. So don't boot to sysNAND with Gateway on 11.3.
Hey my systems are fine. Im well aware of updating or booting gateway on 11.3 from seeing the thread on here. Didn't believe it at first like a few others. I was just having a rant cause I'm sick of seeing there bullshit.Why are you so upset with Gateway? This issue has been covered in countless threads since the launch of 11.3. Sure it's not ok that Gateway doesn't have FIRM0/1 protection. But it's completely your fault for not researching an update that been part of the scene for over a month now.
Don't blame Gateway for your lack of research.
Yet you updated anyways? You knew it would be a problem and you did it anyways? Don't blame Gateway for this, this is completely your fault.Hey my systems are fine. Im well aware of updating or booting gateway on 11.3 from seeing the thread on here. Didn't believe it at first like a few others. I was just having a rant cause I'm sick of seeing there bullshit.
New major update my arse.As indicated before, we are working really hard to release as soon as possible our new major update that will once again revolutionize the (N)3DS scene. As it is now getting very close, we might have to delay the Emunand latest Nintendo firmware support by a couple of weeks max. We will keep you posted very soon, and be sure that as always, we will offer full support for all Gateway user,even for day one buyers from 4 years ago!
I haven't updated. I haven't even used gateway in about 6 months.Yet you updated anyways? You knew it would be a problem and you did it anyways? Don't blame Gateway for this, this is completely your fault.
Oh, it appears I am mixing up the posts here. My bad, I do apologize for that mix up.I haven't updated. I haven't even used gateway in about 6 months.
I don't mean a card without anything on it, I mean an SD card with the A9LH Gateway boot where I may have forgotten to also copy the emuNAND and booting it in sysNAND mode:@Searinox What are you talking about? If you boot "a different SD card" that presumably has no arm9loaderhax.bin on it's root then the console will either: Shut down and nothing happens OR boot into your CFW and nothing happens. The latter will happen if you've copypasted your arm9loaderhax.bin into the CTRNAND. Arm9loaderhax.bin is the only file you need or could be missing when it comes to a CFW and not having it will simply shut down the console .. It will not cause A9LH to get wiped because you will not boot to the sysnand in the first place.
Besides I don't see any of the scenarios you listed as plausible except GW. If you want to keep using Brickway then yes, perhaps having an emuNAND is a better choice overall. But that's only for Brickway .. not everyone uses it.
I could see it happening as I've experimented stuff before that required SD swapping, and it has happened to me by accident in the past. Back then my system was on 4.5 and I did not have A9LH installed, I was booting from MSET but later I did swap to the A9LH launcher. And it booted into Gateway-mode sysNAND. That same oversight scenario today with 11.3 on the sysNAND instead of 4.5 would have wiped A9LH.Searinox said:but forgetting the emuNAND
I think you'd need arm9 access for that? Back in the beginning when you downgraded to 2.1 to get your otp.bin then installed a9lh after updating again, you'd have to update to 9.2. But maybe we didn't have homebrew on higher firmwares then?Wait a sec, do you still have an otp.bin file? That will save your ass by launching SoundHax > SafeA9LHInstaller as 3dsx then full install.