Gateway 3.0.4 works with a 9.5.0-23U EmuNAND fine for me.gateway 3.0.4 not work not support emunand 9.5.0-23
Gateway 3.0.4 works with a 9.5.0-23U EmuNAND fine for me.gateway 3.0.4 not work not support emunand 9.5.0-23
gateway 3.0.4 not work not support emunand 9.5.0-23
Good thing, no one can cheat in pokemon shuffle anymore (at least, those who updated to 9.5.0-23)
To bad for pkhex stuff (at least they don't lose money on hacking pokémon)
what happen to pkhex ?
gateway 3.0.4 not work not support emunand 9.5.0-23
Not noobs coming in not knowingBut thats kinda obvious, since we couldnt update Sysnand since 9.3?
Its affected for those who use region free, but for those playing games from their own reason are unaffectedSky3DS is not effected at all. works good. have a nice day ya'll
Its affected for those who use region free, but for those playing games from their own reason are unaffected
So if the Gateway exploit is blocked with this update, that means that the browser is not duplicated in emuNAND, but instead, the same browser is shared between sysNAND and emuNAND, yes? This also suggests that since the GW browser exploit is blocked with this update, using it to boot to emuNAND from sysNAND would no longer be possible, and we'd have to revert to the DS Profile exploit from before, correct?
What ?No. All updates installed on your emuNAND stay on emuNAND(this is the whole point of emuNAND), you don't share the same browser with your sysNAND. So you can still update your emuNAND to the latest version(for e-shop), and have access to your old browser through sysNAND(to launch GW mode).
I thought it was weird.. So then what Gateway exploit are people in this thread saying was blocked? Or did I just understand it wrong?
The gameboy/nes rom injections via the browserwhat's a virtual console stuff?
You could still exploit the browser in the previous version to run regionthree, you couldn't use it to enter GW mode, but you could use it for minor stuff like regionthree, which is now completely patched, and you will no longer be able use regionthree.
They're not shared.So if the Gateway exploit is blocked with this update, that means that the browser is not duplicated in emuNAND, but instead, the same browser is shared between sysNAND and emuNAND, yes? This also suggests that since the GW browser exploit is blocked with this update, using it to boot to emuNAND from sysNAND would no longer be possible, and we'd have to revert to the DS Profile exploit from before, correct?
They're not shared.