will it be possible to load xcis?All jokes aside, this completely defeats the only one left purpose of SX-OS.
xcis are nice because its easy to use them , no need to install ,reminds me of .3ds instead of cia.
EmuNAND has nothing to do with loading .XCI files. But its looking like free CFW will never receive the ability to mount .XCI files like SX OS so TX will always have that trump card similar to how Gateway and other 3DS flashcarts were the only to play .3DS/.3DZ titles.
thx nice explanation, but they say you might still get banned even if you used sysnand (original copy of game) etc.
Exactly, EmuNAND isn't going to save you if you don't have a clean SysNAND, or backup, in the first place.
so if i am not intending to play online or do not care about online stuff, then i dont need emunand?
The purpose of EmuNAND was not originally to be a ban shield. Like I said, EmuNAND is a way to update your firmware without updating SysNAND. For unpatched units, this means you can update your firmware without burning fuses or relying on AutoRCM. For patched units, it is the only way to update your system past 7.X which is the highest firmware Deja Vu supports which is the only way for patched units to load CFW.
This is where we get into theoreticals. SciresM made a post last year explaining the best firmware to get untethered coldboot is up to 3.0.1 however no one is working on it (he even has a bounty set up for it just to indicate how challenging it is). Technically, there may be an undiscovered coldboot exploit that works on higher firmware versions or all of them but the chances for this are slim to none. This is generally why the lower your firmware version, the better. I should also point out that its not the firmware version that is important here but the fuse count because if your fuse count exceeds the firmware version you are trying to boot, you will not be able to boot that firmware. I am also pointing this out because some people have very low fuse counts but are on the latest firmware so they can take advantage of an untethered coldboot exploit if its released on a very low firmware version.
Well downgrading before your backup is pointless since your NAND backup will end up downgrading your firmware. In fact, downgrading with a NAND backup is better than downgrading with ChoiDujour/ChoiDujourNX.
I'll just quote myself
I think it is valid to call you a moron. Especially when your first word is fist.
I think I rest my case.
A full NAND dump comprises of BOOT0/BOOT1 as well as the eMMC raw GPP. eMMC SYS can be substituted for eMMC raw GPP at the cost of any save data or installed content since those are found in eMMC USER (eMMC raw GPP is comprised of both eMMC SYS and USER). You need BOOT0/BOOT1 if your current firmware does not match the firmware of your eMMC raw GPP/eMMC SYS and consequently, BOOT0/BOOT1 should match the firmware of your eMMC raw GPP/eMMC SYS; it won't do you any good to have a random BOOT0/BOOT1 and eMMC raw GPP/eMMC SYS. If you have an eMMC raw GPP/eMMC SYS, you can generate a corresponding BOOT0/BOOT1 with ChoiDujour if you know the firmware of your NAND dump but keep in mind ChoiDujour only supports up to firmware 6.1. If your eMMC raw GPP/eMMC SYS has a firmware above 6.1 but you do not have a matching BOOT0/BOOT1, you will have to use mattytrog's custom Hekate to restore a smaller BOOT0/BOOT1 that he made which we cannot link here (but can be found on xbins).
There's a large number of us who haven't seriously delved into CFW because there was no real emunand option.
@
Psionic Roshambo:
@
Psionic Roshambo:
@
BigOnYa:
@
Psionic Roshambo:
@
Psionic Roshambo:
@
Psionic Roshambo:
