OP did you chainload using GW with luma? Oo
I believe he did, since he mentions playing MK7 on his gateway. However this shouldn't be an issue unless OP updated in gateway mode, and he claims he didn't, so..
OP did you chainload using GW with luma? Oo
I believe he did, since he mentions playing MK7 on his gateway. However this shouldn't be an issue unless OP updated in gateway mode, and he claims he didn't, so..
Luma doesn't say sys/emu, it's always just Ver. And the op can't open system settings anyway so it wouldn't really matter.When you load up your system (if it even does) does it say "Ver" or "Sys/Emu" ?
If Ver - youre in non-cfw
If Sys/Emu - youre in luma cfw sysnand or emunand
Luma doesn't say sys/emu, it's always just Ver. And the op can't open system settings anyway so it wouldn't really matter.
Didn't know about that, good to know.Since version 6 of luma it supports either customversion.txt for user created strings or Sys/Emu if "Show NAND identification on system settings" is ticked in luma's configuration screen.
What if OP never had a9lh, and was really just using menuhax after upgrading from MSET ROP?
Good Guess, since if he really install recently, he should have A9LHv4 + CTRNAND Luma3DS.What if OP never had a9lh, and was really just using menuhax after upgrading from MSET ROP?
Good Guess, since if he really install recently, he should have A9LHv4 + CTRNAND Luma3DS.
With the 2 layer firm protection, he shouldn't lose A9LH.
Just curious, what's is A9LH v4? If v3 is considered as sd-less (now known as CTRNAND cfw/luma)
It is my experience with this site that the user requesting help is not being 100% truthful. Not necessarily intentional, but due to a lack of knowledge. Just look at this exert from OP: "Hi, i was playing Mario kart with gateway (i had the normal A9LH not the gw A9lh) ". Assuming he is referring to Plailect's Guide over Gateway's A9LH installation, but who knows. Was he using a payload from https://gbatemp.net/threads/tutorial-using-luma3ds-with-gateway-on-v2-a9lh.431691/ or the wrong payload?
A9LH doesn't just disappear, especially with Luma3DS. Chances are, OP updated by accident in GW mode, which has no FIRM protection, and overwrote A9LH.
--------------------- MERGED ---------------------------
That is somebody using the incorrect terminology. They are referring to data input set v4.
There was A9LH, then A9LHv2 which are larger payloads. There was also A9LHv.2 which was the original SDLess A9LH. It has since been deprecated as Aurora's A9LH supports SDLess booting through CTRNAND.
It's really not spooky. In cases like this, the OP often just omits a detail to shift blame away from themselves. Considering how many tests that have been run (including my own.) It seems highly unlikely that Luma3DS failed and more likely that OP was the one who failed. Like they said, they were using a Gateway. Gateway does not have FIRM0/1 protection, which means updating your sysNAND in Gateway Mode will remove A9LH. It could be why the System Settings are broken.Well this is quite spooky.I just switched to a9lh not too long ago.Hopefully I have no issues updating next update.I don't plan on ever using gateway but I've been thinking on getting a r4i gold only for ds games
R4i run on TWL Firm so you shouldn't have any problem.Well this is quite spooky.I just switched to a9lh not too long ago.Hopefully I have no issues updating next update.I don't plan on ever using gateway but I've been planning on getting a r4i gold only for ds games
This. Highly doubtful it was anything outside of user error.It's really not spooky. In cases like this, the OP often just omits a detail to shift blame away from themselves. Considering how many tests that have been run (including my own.) It seems highly unlikely that Luma3DS failed and more likely that OP was the one who failed. Like they said, they were using a Gateway. Gateway does not have FIRM0/1 protection, which means updating your sysNAND in Gateway Mode will remove A9LH. It could be why the System Settings are broken.