I want to know too.With the latest Hekate there's a change that says:
File based now uses FastFS with speeds almost as fast as RAW
Does this apply to existing emuMMC or do we have to create a new emuMMC to take advantage of the FS?
For me it sounds like the file based Emunand was very slow in the past so not much ppl used it before, all used the emunand partition on sd cardWith the latest Hekate there's a change that says:
File based now uses FastFS with speeds almost as fast as RAW
Does this apply to existing emuMMC or do we have to create a new emuMMC to take advantage of the FS?
For me it sounds like the file based Emunand was very slow in the past so not much ppl used it before, all used the emunand partition on sd card
so for now if you will start fresh you can use fs based emunand and don't loose any speed
so for all who used emunand partition on sd card will not have any advantage since they used the fastest way all the time ;-)
emuMMC was designed first and foremost as a way to run higher firmware versions without updating sysMMC. This is also another way of updating your firmware without burning fuses and using AutoRCM. emuMMC can also act as a brick shield. emuMMC was never designed to be a "ban shield", its just a coincidence due to how it works.Any real reason to use emummc if you don't plan to go online ? I believe my switch have been banned although i never tried restore my nand and check it out. My setup has been always 90DNS and switched to rcm incognito soon after.
Have tried partition emummc before but after a couple of days or maybe weeks, things started to get slow and eventually corrupted. So how are things now?
Yup totally agree with you, having the ability to not touch your nand and boot into a seperate drive like a dual boot in a PC is pretty coolemuMMC was designed first and foremost as a way to run higher firmware versions without updating sysMMC. This is also another way of updating your firmware without burning fuses and using AutoRCM. emuMMC can also act as a brick shield. emuMMC was never designed to be a "ban shield", its just a coincidence due to how it works.
I've been using partition based emuMMC for a few months now and I have no issues. It might be worth testing if your SD card is fake or not if you haven't done so already.Yup totally agree with you, having the ability to not touch your nand and boot into a seperate drive like a dual boot in a PC is pretty cool
but due to the corrupted issue i used have, i am still debating on whether should i jumped on this. Would be great if others can share their experience. Maybe i just having a bad day?
PS: i am using a sandisk class 10 64gb sd card. Probably not the best but for cfw it gets the job done.
I've been using the same hidden emuMMC since it released for SXOS in like 2018 and haven't had any corruption issues. Same Sandisk SD card as you. Are you sure it was the emuMMC that corrupted? Or were you using exfat and the SD in general became corrupted?
was this answered elsewhereWith the latest Hekate there's a change that says:
File based now uses FastFS with speeds almost as fast as RAW
Does this apply to existing emuMMC or do we have to create a new emuMMC to take advantage of the FS?
With the latest Hekate there's a change that says:
File based now uses FastFS with speeds almost as fast as RAW
Does this apply to existing emuMMC or do we have to create a new emuMMC to take advantage of the FS?
Yes, you can do the complete emuMMC setup via Hekate, even the partitioning of the SD card is done by Hekate and on the SD card existing data (up to 1 GB) backed up and later restored.Can Hekate partition an sd card for emunand? I remember reading an update added something like that.