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.
I think i'll wait for a new exploit.
DSiWarehax using another O3DS/2DS than has CFW to restore your NAND backup. Unless your console is banned to the point of not being able to system format, there's no reason why you can't do this (other than not having an O3DS/2DS with CFW to transfer from).
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?
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.
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.
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.
I previously updated with Luma, a month ago. Yesterday i entered GW sysnand. Blackscreen (doesnt work in 10.3) and A9 wipe.
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.
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!
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.
Still if you didn't update just yet, it's not too late to switch a free CFW
http://gbatemp.net/threads/faq-what-cfw-is-best-for-me.428509/
I was using Gateway up until about 2 months ago, after having already set up A9LH. Because I use emuNAND, I never took my system out of 2.1 after the guide downgrade because I never saw a reason to. I switched away from it before 11.3 came out, and I learned early about the risks but even then I did not forsee a situation where I could've booted say, from another card with the GW files but forgetting the emuNAND and ending up thus booting automatically into sysNAND by accident. If it would've been 11.3, that would have ended badly.
I am going to chime in again in support of the idea that by leaving sysNAND as untouched and unused as possible, one minimizes their chances of ending up in a scenario where they can mess it up. A third party bootloader, out of date or experimental CFW, Gateway, booting a different SD card or missing files on a CFW that then assumes to boot unprotected sysNAND, or some other mishap can still hose A9LH and in some cases, also brick the console while at it. A setup with emuNAND and an unlinked sysNAND ctrtransferred to 2.1(o3ds) or 9.2(n3ds) or just pre-11.3 locked away from the Internet protects from these, at the cost of 1GB storage space.
I am going to chime in again in support of the idea that by leaving sysNAND as untouched and unused as possible, one minimizes their chances of ending up in a scenario where they can mess it up. A third party bootloader, out of date or experimental CFW, Gateway, booting a different SD card or missing files on a CFW that then assumes to boot unprotected sysNAND, or some other mishap can still hose A9LH and in some cases, also brick the console while at it. A setup with emuNAND and an unlinked sysNAND ctrtransferred to 2.1(o3ds) or 9.2(n3ds) or just pre-11.3 locked away from the Internet protects from these, at the cost of 1GB storage space.
Last edited by Searinox,
D
Deleted User
Guest
well RIP
I'm gonna stay away from Gateway for now. I was lucky enough that shit didn't overwrite my FIRM while attempting to boot it on 11.2 using Luma3DS' chainloader until I gave up cuz of black screen.
I'm gonna stay away from Gateway for now. I was lucky enough that shit didn't overwrite my FIRM while attempting to boot it on 11.2 using Luma3DS' chainloader until I gave up cuz of black screen.
@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.
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 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:
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:
I'm not using Gateway anymore. Hence the past tense in the post. Also my sig.
Last edited by Searinox,
D
Deleted User
Guest
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.
Last edited by ,
- Joined
- Nov 23, 2014
- Messages
- 15,144
- Trophies
- 0
- Location
- Canberra, Australia
- Website
- boot9strap.com
- XP
- 11,119
- Country
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?
Similar threads
