Related
Here's the scenario: say you try out encryption on a ROM, either because your employer makes you or because you want the extra security. What happens when you can root your phone, like we can (easily) with the S3, and you want to flash a different ROM? The problem you will find yourself in very quickly is that you cannot do a successful wipe. You can't format an encrypted /data in CWM or any other recovery. If you cannot format /data, you can't flash a ROM - it fails, because /data is encrypted, and it cannot proceed. It turns out none of the recoveries can format an encrypted /data. You also cannot reverse encryption once you've done it. You're stuck, all because you flipped the switch on encryption.
I found myself in this problem as others have in many other forums (like this one for the GNex) (and another one, more detailed).
I also tried, admittedly somewhat out of desperation, the soft-brick instructions here. That didn't work because Nand Erase All fails. You can flash on top, and luckily you can use your same password to decrypt your /data (which I did) but you're still not going to have a clean ROM. Dirty flashes = lots of problems down the road.
I finally found a simple way to do this and wanted to save anyone else the trouble of digging. You can do it using CWM and adb and a few commands. Credit goes Shawn Webb's blog and utkanos on FreeNode's irc at #cyanogenmod.
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Thanks for this. I fell into the same scenario yesterday but after reading a lot of helpful posts from people like yourself I have managed to solve the issue. Basically I found two ways of doing it, one is as you have suggested and the other is by just replacing the custom recovery with the stock recovery. The SGS3 toolkit available on XDA made the 2nd option just slightly simpler for me and by spending less than 10 mins (excluding time for backups and downloads) the issue was resolved.
Just to share this option to save others from the headache of looking for a solution:
1) Get the toolkit
2) Install drivers as recommended and follow instructions to choose the build, or closest build, for your S3
3) Restore stock recovery with toolkit via ODIN (follow instructions)
4) After rebooting, go into Android and reset to factory settings, this would bring you to the stock recovery and wipe
5) Restore custom recovery with toolkit via ODIN (follow instructions)
6) Restore your system (luckily for me I had a nandroid backup before I encrypted)
Note: I did "lose" my internal sdcard files (pictures/documents). But I backed that up on my external sdcard before starting the process. My sdcard was not encrypted.
kitleon said:
Thanks for this. I fell into the same scenario yesterday but after reading a lot of helpful posts from people like yourself I have managed to solve the issue. Basically I found two ways of doing it, one is as you have suggested and the other is by just replacing the custom recovery with the stock recovery. The SGS3 toolkit available on XDA made the 2nd option just slightly simpler for me and by spending less than 10 mins (excluding time for backups and downloads) the issue was resolved.
Just to share this option to save others from the headache of looking for a solution:
1) Get the toolkit
2) Install drivers as recommended and follow instructions to choose the build, or closest build, for your S3
3) Restore stock recovery with toolkit via ODIN (follow instructions)
4) After rebooting, go into Android and reset to factory settings, this would bring you to the stock recovery and wipe
5) Restore custom recovery with toolkit via ODIN (follow instructions)
6) Restore your system (luckily for me I had a nandroid backup before I encrypted)
Note: I did "lose" my internal sdcard files (pictures/documents). But I backed that up on my external sdcard before starting the process. My sdcard was not encrypted.
Click to expand...
Click to collapse
You just saved my month. Drop me a message if I can get you a beer via paypal for this.
Cheers!
THANKS!
olm3ca said:
Here's the scenario: say you try out encryption on a ROM, either because your employer makes you or because you want the extra security. What happens when you can root your phone, like we can (easily) with the S3, and you want to flash a different ROM? The problem you will find yourself in very quickly is that you cannot do a successful wipe. You can't format an encrypted /data in CWM or any other recovery. If you cannot format /data, you can't flash a ROM - it fails, because /data is encrypted, and it cannot proceed. It turns out none of the recoveries can format an encrypted /data. You also cannot reverse encryption once you've done it. You're stuck, all because you flipped the switch on encryption.
I found myself in this problem as others have in many other forums (like this one for the GNex) (and another one, more detailed).
I also tried, admittedly somewhat out of desperation, the soft-brick instructions here. That didn't work because Nand Erase All fails. You can flash on top, and luckily you can use your same password to decrypt your /data (which I did) but you're still not going to have a clean ROM. Dirty flashes = lots of problems down the road.
I finally found a simple way to do this and wanted to save anyone else the trouble of digging. You can do it using CWM and adb and a few commands. Credit goes Shawn Webb's blog and utkanos on FreeNode's irc at #cyanogenmod.
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Click to expand...
Click to collapse
Just wanted to say thanks very much for this. I'd tried the method of reloading the stock ROM as described by a previous poster, but this way worked.
I did run into a small issue I was wondering if you could shed some light on. When I entered "mount /data", I got the following:
Code:
~ # mount /data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
I bullied ahead and entered the last line "mount /dev/block/mmcblk1p1 /data/media" and got this:
Code:
~ # mount /dev/block/mmcblk1p1 /data/media
mount: mounting /dev/block/mmcblk1p1 on /data/media failed: No such file or directory
However after doing this, I was able to perform a complete wipe of /data using CWM and load a new ROM without issue.
I'd curious to know what might be causing these Invald argument responses.
My Device: HTC One (GSM)
Thanks again! :laugh:
olm3ca said:
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Click to expand...
Click to collapse
I'm trying to follow your instructions but fail at finding out my mount points.
Sorry for the noob question, but who do I find out what the mount points of internal and external SD card are on my device (Samsung Galaxy S4 Mini International 4G)? I found this post
stackoverflow. /questions/6824463/how-to-get-all-the-mount-point-information-for-android-device
which seems to include the answer but I don't know what tool / software they use. I'm no programmer.
My phone is encrypted and doesn't turn on, it doesn't accept my password saying it's wrong, though I know it's correct. OS is Cyanogenmod 10.1 stable. Booting into CWM v6.0.3.7 is possible though.
I appreciate everyone's help.
Stephan
Hello to everyone. Can anyone inform me about:
1. the exact commands in order to wipe all android partitions except /misc (/boot, /data, /cache, /recovery, /system).
2. the exact commands in order to flash two zip files (1. custom rom, 2. kernel)
3. is there anyway i can merge two android partitions specifically data with recovery because i don't want to use it anymore?
4. what exists after wiping a partition (unallocated space or allocated space)??
My device is HTC desire X UNLOCKED.
My purpose is to perform a clean install without using any custom recovery like TWRP or CWM.
Must have recovery
Got wipe then to advanced and click the box for cache do the wipe
Then go to install find your rom install it then find your kernel and install that then reboot
Kjssplass said:
Hello to everyone. Can anyone inform me about:
1. the exact commands in order to wipe all android partitions except /misc (/boot, /data, /cache, /recovery, /system).
2. the exact commands in order to flash two zip files (1. custom rom, 2. kernel)
3. is there anyway i can merge two android partitions specifically data with recovery because i don't want to use it anymore?
4. what exists after wiping a partition (unallocated space or allocated space)??
My device is HTC desire X UNLOCKED.
My purpose is to perform a clean install without using any custom recovery like TWRP or CWM.
Click to expand...
Click to collapse
1. You need a custom recovery.
2. You need a custom recovery.
3. If you need the data from them just copy and paste them. Not only is it not possible without compiling Android, but it is not useful.
4. Since wiping is usualy done with mkfs (or even rm -rf) allocated space will be made.
Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Cepillado said:
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Click to expand...
Click to collapse
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
sosukeaizen said:
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
Click to expand...
Click to collapse
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Cepillado said:
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Click to expand...
Click to collapse
try flashing a lower version of the same frimware you've already installed e.g if the latest is nougat 7.1.1 with the recent security update, try flashing with another nougat version that is lower to the recent one's security patch #
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Just to be clearer, you have to delete all inside /data, unless /media folder.
Salieri99 said:
Just to be clearer, you have to delete all inside /data, unless /media folder.
Click to expand...
Click to collapse
I think the problem with the term 'delete' is that people will think you mean 'wipe'. 'Wipe' and 'format' actually mean different things. The latter is what is actually required.
This method will not Work at 100%
It depends on the encryption Key from the Rom
Deleting /Data without deleting Media will simply Work to have a bootable State of the flashed Rom but your internal Data will be encrypted and your Rom cant decrypt /Data/media anymore also the Recovery after reboot.
it Happens because of a different Decryption Key in /Data
For Safety and Security reasons i would Not recommend doing this, unless you have a Backup.
Smilex93 said:
This method will not Work at 100%
It depends on the encryption Key from the Rom
Deleting /Data without deleting Media will simply Work to have a bootable State of the flashed Rom but your internal Data will be encrypted and your Rom cant decrypt /Data/media anymore also the Recovery after reboot.
it Happens because of a different Decryption Key in /Data
For Safety and Security reasons i would Not recommend doing this, unless you have a Backup.
Click to expand...
Click to collapse
1.the rom boots and can't decrypt data anymore ??? wtf is this ??? a new science ???
2.where do you think encryption keys are stored ??? in the cloud ???
3. a device with FOD requires encryption in data otherwise the FOD will not work !
4. how do you think i built the TWRP for this device ???? (check my first thread in the forum for this device)
You should never talk about things you don't know very well !!!
The world is upside down these days ... and i'm really bored with idiocracy !
Sorry If i have Not so much knowledge.
But i have done your steps above
Went from Evo X to Derpfest Rom
Everything was fine then i realised my Internal Storage was encrypted.
Maybe i forgot to mention ive used Official Twrp Not your twrp, also maybe its my own mistake
Thank you for your serious words.
Smilex93 said:
Sorry If i have Not so much knowledge.
But i have done your steps above
Went from Evo X to Derpfest Rom
Everything was fine then i realised my Internal Storage was encrypted.
Maybe i forgot to mention ive used Official Twrp Not your twrp, also maybe its my own mistake
Thank you for your serious words.
Click to expand...
Click to collapse
All devices with FOD (fingerprint on display) require encryption to work (These are the new standard policies by Qualcomm & Google). If you use a decryption script that you can find here and there ... your FOD will not work !!! It's not a normal fingerprint ... can you understand ???
My TWRP was made 3 months before the official one. It's built by stock official blobs from xiaomi !
The official TWRP uses a generic kernel not official kernel by xiaomi ! So there are and will be always
some stuffs missings !!! That's why there are many people struggling with backups and rom installations !
im almost got it.
But the only except is Dirty unicorns Rom, they need always an internal storage format.
They are not using Public keys
maybe i known why from alex cruz
gringo80 said:
All devices with FOD (fingerprint on display) require encryption to work (These are the new standard policies by Qualcomm & Google). If you use a decryption script that you can find here and there ... your FOD will not work !!! It's not a normal fingerprint ... can you understand ???
My TWRP was made 3 months before the official one. It's built by stock official blobs from xiaomi !
The official TWRP uses a generic kernel not official kernel by xiaomi ! So there are and will be always
some stuffs missings !!! That's why there are many people struggling with backups and rom installations !
Click to expand...
Click to collapse
if i am just going from Miui EU to New or older MIUI Eu roms ... will i have be encrypted also or not ?
gringo80 said:
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Click to expand...
Click to collapse
To avoid encryption problems between flashing different roms the easiest thing to do is just go to lockscreen settings and delete the PIN or Pattern, this will delete the FP stored as well and you can then flash any rom you want without issues. No more encryption problems and no need to flash any zips and kill the FOD.
Also, I always wipe data as well as "internal storage" if changing roms, there's nothing wrong with that... That way I have a perfectly clean start.
gringo80 said:
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Click to expand...
Click to collapse
U used some roms or only your lineage?
This is exactly what I was searching for!
Does this apply to other phones as well? The ones for which ROM developers always ask to format the internal storage on the phone (OnePlus 6T for me)?
Now that I've finally found this thread, I'd like to also know, is encryption the only culprit due to which it's recommended to format all the data? If yes, why wouldn't one simply remove their screen-lock (I assume that will decrypt any data on the phone), change ROM without formatting internal storage and then keep another screen-lock?
Actually, encryption issues jumping from ROM to ROM is more complicated than that if you don’t know what encryption type is used by the ROMs.
A. Sometimes you might need to format (not just wipe) the data partition. If you format the data partition before flashing the new ROM, then you must reboot OrangeFox immediately afterwards, and, most definitely, before doing anything else.
B. If you are moving from a ROM that uses a different encryption protocol (eg, from FDE ROM to FBE ROM or vice-versa), then you must format the data partition preferably after flashing the new ROM, and then boot to system.
C. If you are moving from a stock ROM to a custom ROM (or vice versa), then you must format the data partition.
D. If you boot the newly flashed ROM, and it gets stuck forever on the Google/Android logo, or just dumps you at fastboot or straight back to OrangeFox, this might be a sign that you need to format the data partition.
source : https://wiki.orangefox.tech/en/guides/flashing
You are right Just
gringo80 said:
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Click to expand...
Click to collapse
Thats right just changed my Rom for Crdroid to Spark I didnt format data just WIPED it. The rom Boots up clean. I also deleted the ANDROID folder in case. there were nothing else in the DATA. You must have to Flash Force Decrypt file after flashing a rom