Yup, you're fucked.
if you updated through emunand then you're fine.
Yes, it looks like you didn't format sysNAND before updating to unlink the NANDs. If you made a NAND backup like you were supposed to you can get a hardmod and flash it to your sysNAND. If not, you can hardmod anyway and to the hardmod workaround for downgrading on 11.0. Basically your only option is to get a hardmod, so either shell out the UK equivalent of $50+ USD to @gamesquest1 or DIY.
Only if you update through System Settings, while in EmuNAND. Using the prompt, you'll update your SysNAND.
Again, if you did use the prompt, you are out of luck, you'll need to get a hardmod.
As was already mentioned, if you update through an update prompt and not through the System Settings, you risk updating your sysNAND. As was also already mentioned, you should have unlinked your NANDs.
really? luckily i never did that before and i've got arm9 now
Heh. I still only update through System Settings, even though I have A9LH. It's just been drilled into me so much by now.
Even if you're sure you're in emuNAND, updating from the update prompt has the potential to update your sysNAND.
the only potential is that if your not in emunand, if you are certain that your in emunand it would only update emunand....atleast in every cfw i know of, the risks only come from users who didnt actually setup emunand or specifically booted into sysnand rather than emunand
You are mistaken. Under certain conditions, updating through the update prompt while in emuNAND will update one's sysNAND. One should only update emuNAND from the System Settings.
I must agree. My children who do not like to follow all directions all of the time have updated via this prompt. Luckily it was on emuNAND, and only it updated. This has happened 3 times over. If the potential is there, it is very slight.
