I'm going to be ROM-ing for the first time (well, other than Safestrapping the Bionic for a day or two) and want to make sure I have the right thought in terms of running and upgrading a ROM over the long term. If I'm moving to AndroWook as my daily driver, I want to make sure I have a good procedure in place for quickly and easily upgrading to the latest version of the ROM.
The following is my understanding of this whole process. Is this procedure correct? My main concern is making sure I am doing everything right to be able to quickly update to the latest version of the ROM when it comes out, not spend a day re-configuring. Is there anything I am missing?
BACKGROUND: Partitions
Main Partitions Involved With Wiping
/system = Where the OS lives, along with the apps that are preinstalled
/data = Where user installed programs & their associated data/settings live. This data/settings is the part that gets deleted when you go Settings -> Applications -> pick an application and click "Clear Data". This is what Titanium Backup backs up for user apps (both the "apps" and "data" backed up live here). Also has SMS, contacts, settings, etc... the "system data" in TiBu
/cache = Cache files that help programs to load quickly. Harmless to wipe, as it will regenerate.
/sdcard = Internal sd card area where you keep files and use file manager. some programs also put files here. Not usually wiped.
external sdcard = Physical external sd card, if applicable. Not usually wiped.
Other partitions
/boot = Kernel and ramdisk. Don't wipe unless you fix it before rebooting.
/recovery = Where the recovery (stock or custom) lives.
/misc = Other settings not normally touched.
BACKGROUND: Types of Wiping
Cache = harmless. Cache regenerates itself over time to speed up phone.
Dalvik = harmless. This is simply another cache, this one having to do with Java.
Factory Reset = wipe /data and /cache. internal and external sdcard is NOT wiped
Wipe system = wipes /system (where the os and its preinstalled apps live)
Format data = wipes /sdcard (the internal sdcard)
Format external sd = wipes external sd card
ASSUMPTIONS & NOTES
You are rooted
You have Titanium Backup (TiBu)
For multi-user environment, modify the instructions to account for the need to backup/restore with TiBu for each user. Backup for each user, flash, then restore for each user.
BACKING UP
1. TiBu: Batch Backup all user apps & data (everything) in current ROM
2. TiBu: Batch verify the backup
3. Make a sketch of how your widgets/homescreen is supposed to look
4. If you are doing a total deep clean that wipes sdcard (generally not), here is where we want to back up anything else (sdcard files, etc)
5. File Manager: Backup apk for both TiBu & TiBu Pro to SD card
Alternate: Do nothing now, and we use market in new ROM later6. Download ROM & put on SD
WIPING & FLASHING
This part subject to change based on ROM maker's recommendations
1. Boot into recovery
2. Wipe and flash:
Option A: Clean flash (typically done, does NOT wipe sdcard):
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. For a total deep clean (not usually done, DOES wipe sdcard): Wipe system; Format data
5. Flash zip
Option B: Dirty Flash (usually only OK for minor updates):
1. Wipe cache
2. Wipe dalvik
3. Flash zip
4. There is no need to set up the ROM again in this case.
SETTING UP NEW ROM
1. Boot into new ROM
It will take 30-60 minutes to get up to full speed. After that time, it will be full speed after a reboot.
You can tell it to keep backed up to Google (backups up TO Google), but tell it NOT to restore from Google right now (restores FROM Google right now).
2. System > Applications > Unknown Sources
Restore TiBu & TiBu Pro from apk backup
Alternate: get from market
3. TiBu: Batch Restore system data - ONLY THE GREEN ITEMS
Do not restore red items
Do not restore user stuff yet. We are doing system stuff first.
Note that icons will not show correctly yet... nothing to be concerned about.
If the new ROM is vastly different, take care to restore only what is necessary.
4. Reboot
5. TiBu: Batch Restore missing apps with data - ONLY THE WHITE ITEMS
6. Click Market Doctor to verify that everything is hooked back up to the Market OK
7. Fix up homescreen - widgets & wallpaper
One by one, delete empty Widget then add new one.
Also choose the wallpaper you want
8. Check:
Date & time, alarms, ringtone, voicemail number, other settings
Anti-theft is operating properly
9. Market Place > My apps > Update any other apps
10. If over the course of time you find any apps giving problems, use the market to uninstall them and reinstall them to clear out any problems it may have had in restoring from TiBu
I just glanced thru that and this is what I saw quickly.
Option A: clean flash..... I always wipe system as well. This is not a big deal if you don't do it because I format the system in the installer in case people have forgotten.
I also delete cache and dalvik in the installer also in case people forget but I still end up doing them on the wipe page.
The only one really you need to use for a major version update is factory reset. This is just on my rom tho.. I can't speak for how others do it so always best to do the manual wipes also.
Tibu : It is never advised to restore system apps. Even between minor updates in case I have changed a system app.
If there is one that you really need restored then try restoring just the data for that one app and test it properly.
In the installer I do not write all apps to system anyway. There is very little in there that would take more than a few seconds to set back up.
Related
How much wiping do you need to do when you are upgrading to a new ROM release? I don't really want to have to go through all of the setup every time a ROM is updated. What does every generally do?
I'm running the G-Harmony ROM.
Use Titanium backup or the like to take a backup of everything if you are upgrading from one version of the rom to a new version. At first I wasn't backing up and spent hours getting everything back to the way it was. Now, in a matter of minutes I'm back running the same way I was before, but on a newer ROM.
Take the backup -> copy the backup folder to your micro sd card or computer -> follow the steps to install the ROM (do what is recommended such as the user data, dalvik, cache) -> once the rom is up and running, copy the backup folder back to your tablet -> download titanium backup, it will see the folder you copied over containing your backup-> restore data, apps, user settings from titanium backup.
I'm not sure how it works if going from ROM to ROM, probably want to search on it.
Cool, that's pretty much what I did. Unfortunately, I hadn't copied off the TitaniumBackup folder, and the new ROM version switched the emmc and SDCard mount locations, so I had to switch them back to be able to get at my backups. I didn't have an external micro SDCard reader with me, so I couldn't easily copy the folder from the internal card to the external. Ah, well. Going through the Titanium restores right now. I really should buy this software to prevent having to approve every restore
chadness,
One of the main things I try to help people here with is boot loops and I spend a
lot of time trying to figure out the cause so we can prevent it.
IT IS MY OPINION that one of the things causing the boot loops and making
people have to re-flash and re-partition -- is the stuff leftover in flash after
flash playing with their tablets.
I'm not sure the Android file system is all that good. I don't believe in tablet formats
because it doesn't work like a hard disk. You can delete a file and go back later and
the file is still there. You can nvflash the tablet and stuff is still let there.
When stuff gets left over it can conflict with the new stuff and BAM -- boot loops.
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid
version -- bekit 1105 (2538) or 3588 -- the repartition to 2048 and 0, Fix Permissions,
Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
I can't prove it yet -- but I bet if people would do that most of the boot loops would stop -- and probably some of the other little stuff too.
This is just my opinion -- but then I have only nvflashed either of my G-Tablets one time in five months now (involuntarily -- because of problems.)
Think about it.
Rev
Interesting! I've been flashing different ROMs this week and haven't run in to any problems as long as I've formatted system and data.
butchconner said:
. . .
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid version -- bekit 1105 (2538) or 3588 -- then repartition to 2048 and 0, Fix Permissions, Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
. . . . Rev
Click to expand...
Click to collapse
Rev, what is your opinion about using 'Calkukin's_Format_All.zip & wiping Dalvik Cache' vs all the above steps ?
Hey everyone, I am looking for a little clarification on something. I have a Canadian Rogers i717r. I am running the stock Rogers Jellybean ROM I717RUXMD1_I717RRWCMD1_RWC, with root. Recently, I have been noticing some issues with it hanging, and doing other odd things, so I just think it is time for a reinstall. I may have installed a bad app or something along the way, because it does happen from time to time. My main question is this: How do I do a complete system wipe? Now I am talking every old file, so there are no remnants of the old information left. I have done the factory wipe and dalvik wipe, along with the cache wipe, prior to installing a ROM, every time I have done a new ROM install.. It always seems to leave files behind though. Old game files will still be there and such. Is there a way to get rid of it all, so it is a complete clean slate for the install?
Now, I use TWRP, but the idea is generally the same when it comes to this procedure, and I have found these instructions online;
-- The correct procedure for doing a full wipe is below.
Go to clockworkmod recovery.
Volume up, power button, and home button all pressed together for a couple of seconds.
Go to Advanced menu and wipe the dalvik cache and batt stats if present!
Go to mounts and storage and select it.
Go to format / system and select it.
Scroll down to format system and select yes.
Go to format / data and select it
Scroll down to format data and select yes.
Go to format / cache and select it.
Scroll down to format cache and select yes.
Now go back and install the rom from the internal or external sd card.
This is the correct way of doing a full wipe everything is erased and formatted ready for the new rom, no old system files, old kernel remnants etc....
I am curious as to what will have to be done after the install is complete. I am going to lose ALL of the info. I would basically need to redo all the programming on the phone, including the IMEI and all the info for the networks and what the phone needs to recognize what network it is allowed to access and such. Is this what it will boil down to? I will basically need to reprogram the behind the scenes info also, or no?
Thanks in advance!
Shad
ShadNuke said:
Hey everyone, I am looking for a little clarification on something. I have a Canadian Rogers i717r. I am running the stock Rogers Jellybean ROM I717RUXMD1_I717RRWCMD1_RWC, with root. Recently, I have been noticing some issues with it hanging, and doing other odd things, so I just think it is time for a reinstall. I may have installed a bad app or something along the way, because it does happen from time to time. My main question is this: How do I do a complete system wipe? Now I am talking every old file, so there are no remnants of the old information left. I have done the factory wipe and dalvik wipe, along with the cache wipe, prior to installing a ROM, every time I have done a new ROM install.. It always seems to leave files behind though. Old game files will still be there and such. Is there a way to get rid of it all, so it is a complete clean slate for the install?
Now, I use TWRP, but the idea is generally the same when it comes to this procedure, and I have found these instructions online;
-- The correct procedure for doing a full wipe is below.
Go to clockworkmod recovery.
Volume up, power button, and home button all pressed together for a couple of seconds.
Go to Advanced menu and wipe the dalvik cache and batt stats if present!
Go to mounts and storage and select it.
Go to format / system and select it.
Scroll down to format system and select yes.
Go to format / data and select it
Scroll down to format data and select yes.
Go to format / cache and select it.
Scroll down to format cache and select yes.
Now go back and install the rom from the internal or external sd card.
This is the correct way of doing a full wipe everything is erased and formatted ready for the new rom, no old system files, old kernel remnants etc....
I am curious as to what will have to be done after the install is complete. I am going to lose ALL of the info. I would basically need to redo all the programming on the phone, including the IMEI and all the info for the networks and what the phone needs to recognize what network it is allowed to access and such. Is this what it will boil down to? I will basically need to reprogram the behind the scenes info also, or no?
Thanks in advance!
Shad
Click to expand...
Click to collapse
First, If you're currently using TWRP I'd suggest updating to the latest version, if you haven't already. There's a few of the newer ROMS which specifically require it. On the question of wiping, before you get too carried away it might help you to backup a few things. Within TWRP (ver 2.8.1.0) you have the options to backup EFS (anywhere you please, Internal storage, internal SDcard or MicroSD card) by clicking on the Storage: bar just above the swipe icon. Your IMEI >> located within EFS folder. Also, search the TWRP website for more specific instructions. What you posted is CW instructions. Hope it helps!
LOOK HERE!!
TWRP version 2.8.1.0: http://teamw.in/project/twrp2
TWRP XDA post: http://forum.xda-developers.com/showthread.php?t=2551499
Hi guys!
I've been fiddling around with different ROMs. With every new rom I install, I always wipe data/factory reset, wipe cache + Dalvik cache.
However, it seems there still are files lingering from earlier versions (eg. wallpaper settings).
Is it possible, and if so how, to do an ultimate reset, to make the phone as bare as possible before installing a new rom?
I've tried using CM recovery, TWRP, CWM, and others based on earlier mentioned recoveries. Right now I'm running the latest Candy 5 (infected) + CWM
It's not quick but if you encrypt before wiping it that is one way. I've always reccomended doing this when selling your device.
Sent from my D6503 using XDA Free mobile app
usually I do a full wipe with TWRP (go advanced wipe and check everything including internal sdcard), this will wipe everything you have on the phone like pics and other stuff, so make sure TO COPY THEM FIRST, the are not included in a nandroid backup, had to learn that the hard way
There's no better wipe then what you do (except formatting sd card).
I think the settings that stay between flashing are the one restored by your Google account.
Uncheck backup / restore from Google settings next time you install a rom and it should be all new !
pec0ra said:
There's no better wipe then what you do (except formatting sd card).
I think the settings that stay between flashing are the one restored by your Google account.
Uncheck backup / restore from Google settings next time you install a rom and it should be all new !
Click to expand...
Click to collapse
I'm quite sure it's more than just the google back-up files lounging around, but I'll make sure to try and set it up as a new phone next time around. Thank you for your help
munte89 said:
I'm quite sure it's more than just the google back-up files lounging around, but I'll make sure to try and set it up as a new phone next time around. Thank you for your help
Click to expand...
Click to collapse
If you mean files that are on your sd (internal or external) they are not Google's backup but have no big effect on your settings (except for some apps). If you want to get rid of this, just format your sd.
Now if you mean some settings like the wallpapers, they are restored by Google automatically but the setting is stored on the data partition (which you wiped).
Do you have other examples of things that stay between wipes?
pec0ra said:
If you mean files that are on your sd (internal or external) they are not Google's backup but have no big effect on your settings (except for some apps). If you want to get rid of this, just format your sd.
Now if you mean some settings like the wallpapers, they are restored by Google automatically but the setting is stored on the data partition (which you wiped).
Do you have other examples of things that stay between wipes?
Click to expand...
Click to collapse
Nothing that comes to mind, only the reoccuring feeling of "Huh? That shouldn't be there anymore". However, I'm quite sure I solved it using PhilZ to advance wipe and wiped everything but the boot.
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
ic2e said:
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
Click to expand...
Click to collapse
use miflash to start fresh with miui, use miflashunlock to check if bootloader is unlocked properly, flash twrp, redownload the rom and gapps, start flashing through twrp
If you're flashing ROM, do not restore data.
Wipe system+data+cache+dalvik ,then flash ROM+gapps then reboot.
Don't restore anything from other backup
Preliminary guide to BACKUP / RESTORE with
OrangeFox recovery by ManoloRey
LINK
or
TWRP recovery 3.5.X_10-x by brigudav
LINK
! ! ! USE ONLY LINKED VERSIONS OF RECOVERIES ! ! !
Consider this guide for (decrypted vendor (or encryption disabler) + decrypted storage used) as BETA, I don't recommend backup/restore procedures with OrangeFox recovery Beta or TWRP 3.5.0_10-x for actual backups of your data (TRY THIS ONLY AT YOUR OWN RISK) ONLY FOR TESTING / EDUCATIONAL PURPOSES !
Do not ask for help if your data have been lost because they can't be restored, or suddenly your backup - successfully restored several times before - now can't be! This is still buggy and sometimes for unknown reasons restore of your data can fail ! Restore process always worked 100 % for me, but results sometimes differ !
YOU HAVE BEEN WARNED!
(decrypted vendor (or encryption disabler) + decrypted storage used)
Spoiler: Backup method A (not recommended):
- backup boot and data partition
Restore:
- wipe cache, dalvik, data
- flash ROM + GAPPS that you have installed when you created backup
- restore backup of boot and data partition
- remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !) but before reboot!
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Reboot
Comment(s):
- if you remove your password/PIN/pattern protection directly before backup you can end up after restore with system where you can't change your password/PIN/pattern anymore
- if you forget to remove your password/PIN/pattern protection AFTER RESTORE you can end up after boot with system demanding to enter your password/PIN/pattern which MAY or MAY NOT BE ACCEPTED even if it is CORRECT and maybe INACCESSIBLE because of that
- Google Pay will never be restored properly (or anything depending on actual password in time of backup), because of the removed password, you will need to set up it again after restore
Spoiler: Backup method B (recommended):
- backup super, boot, dtbo and data partition (metadata partition is optional)
Restore:
- wipe cache, dalvik, data (optional)
- restore super, boot, dtbo and data partition (metadata partition is optional)
Reboot
(everything will be restored to the state in time of the backup) ¹)
- if needed remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !)
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Comment(s):
¹) your backups will be fully restored along with password/PIN/pattern and fingerprints - this will work until you'll format data (or for something else that needs to be discovered yet), after that you'll loose the ability to use your password to enter the system and depending on ROM features you can either skip password entering with fingerprints (RRemix) or reset your password so you can enter the system (CrDroid), in RRemix everything works, except you can't change your password etc, in CrDroid you need to re-setup your password depending apps
- if you remove your password Google Pay will never be restored properly (or anything depending on actual password in time of backup), you will need to set up it again after restore
x x x(encrypted vendor and storage used)
Spoiler: Backup method A (OFFICIAL for OrangeFox & UNOFFICIAL for TWRP)
Backup:
- backup boot and data partition
Restore:
If you are restoring a data backup of an encrypted device, there are precautions that you should take before starting the restore process (obviously, your backup must be on MicroSD or other external storage medium - NOT on the internal storage):
Format the data partition (NOTE: format - not just wipe)
Reboot OrangeFox / TWRP
Flash the original zip of the ROM whose backup you are trying to restore
Wipe cache and dalvik
Reboot to system to ensure that the newly-flashed ROM actually boots, and that it re-encrypts the device with its own encryption
Reboot to OrangeFox / TWRP
Tap on the Backup icon
Select the partition(s) that you wish to restore
Swipe to restore
If you do not follow all these steps, you can expect problems with restoring data
Reboot
Comment(s): TBA
Credits: OrangeFox devs as this guide (for encrypted vendor and storage used) is copied directly from OrangeFox wiki slightly modified by me by adding "/ TWRP" to the text
this guide will be updated if I discover new facts or post new, updated steps or how-to's
reserved
jeryll said:
reserved
Click to expand...
Click to collapse
Thanks for your experiments and hard work in putting this together!
backup super, boot, dtbo and data partition (metadata partition is optional)
Click to expand...
Click to collapse
there is 2 checkboxes for super with the same size in OF. one says (Product, Vendor, System).
which one to select or both?
drahtwurst said:
there is 2 checkboxes for super with the same size in OF. one says (Product, Vendor, System).
which one to select or both?
Click to expand...
Click to collapse
Only one, backup of super from either is identical
Thanks for this flashlight on the darkness.
Let me ask you a help. How can I decrypt my device? Wanna do it just like my old MI8, where I didnt need to do format data ever when go to update a rom.
Ever I go do recovery (OFOX or TWRP) I got this in screenshot.
- download and flash decrypted (hacked) vendor from this thread or
- use encryption disabler zip, but that is a little tricky to use - you need to flash encryption disabler every time you update your MIUI base, or custom rom, if you forget that, on next boot your internal storage will be encrypted
- - to remove encryption from data partition after - you need to do initial format data (yes) - after that you can start to use wipe data if needed (some ROMs still need to use format data (yes) or they'll not boot - RR 8.6.6/8.6.7 for example)
jeryll said:
- use encryption disabler zip, but that is a little tricky to use - you need to flash encryption disabler every time you update your MIUI base, or custom rom, if you forget that, on next boot your internal storage will be encrypted
Click to expand...
Click to collapse
Yep, that fact just bit me today as I was away from the computer and had to reflash the latest Xiaomi.eu...
jeryll said:
- use encryption disabler zip
Click to expand...
Click to collapse
Are there further instructions for first install? I did google but failed to find anything reliable...
pnin said:
Are there further instructions for first install? I did google but failed to find anything reliable...
Click to expand...
Click to collapse
not that I know of, just flash it as last thing before you reboot (either recovery or to system), but you need to format data (yes) to remove encryption
As this [surya] 'encryption-disabler-v1' is basically a shell script (pasted to https://paste2.org/804aemGx, BTW), I took the risk to flash it without formatting 'Data' -- only I disabled any security beforehand, i.e., no pin, password or fingerprint.
It appears to have worked, cause I rebooted into system with no issues. But how to verify?
not sure what do you want to achieve by flashing of encryption disabler without actually disabling encryption by formatting your data partition...
so what do you want to verify?
if you start OFOX, on the initial screen you can see the state of your data partition (encrypted/decrypted)
Thanks for your patience. I was under the impression that if you disable security locks then you had no encryption and the script would just ensure it would remain so. By your reaction I'm assuming I was wrong...
Overall, I am just getting fed up with always having to format data and having to start from scratch.
I not longer have OFox, I'm currently running brigudav's TWRP "v3.5.0_10-5-surya".
pnin said:
Thanks for your patience. I was under the impression that if you disable security locks then you had no encryption and the script would just ensure it would remain so. By your reaction I'm assuming I was wrong...
Overall, I am just getting fed up with always having to format data and having to start from scratch.
I not longer have OFox, I'm currently running brigudav's TWRP "v3.5.0_10-5-surya".
Click to expand...
Click to collapse
As you said, that encryption_disabler.zip is a shell script, which makes the folder in /product/vendor_overlay/29/etc and copies fstab.qcom from vendor to it. Then edits every line using the shell command sed (aka stream editor) that includes the string fileencryption= with the string encryptable=.
The above described process is usually done on the first boot of a newly installed ROM as is with every vendor_overlay entry in product (minus the edited strings ofc). Editing it after the ROM reads vendor fstab.qcom and encrypts the data partition is useless. However, formatting data (deleting keystore essentially) and flashing that .zip should also do the trick. Might as well update your base MIUI and ROM while you're at it
Thanks for the detailed explanation, Slim K. Sadly there's no escaping formatting data, which I'll do next...
Slim K said:
Might as well update your base MIUI and ROM while you're at it
Click to expand...
Click to collapse
I had done so already, hence my reluctance to do it again.
jeryll said:
Preliminary guide to BACKUP / RESTORE with
OrangeFox recovery by ManoloRey
LINK
or
TWRP recovery 3.5.X_10-x by brigudav
LINK
! ! ! USE ONLY LINKED VERSIONS OF RECOVERIES ! ! !
Consider this guide for (decrypted vendor (or encryption disabler) + decrypted storage used) as BETA, I don't recommend backup/restore procedures with OrangeFox recovery Beta or TWRP 3.5.0_10-x for actual backups of your data (TRY THIS ONLY AT YOUR OWN RISK) ONLY FOR TESTING / EDUCATIONAL PURPOSES !
Do not ask for help if your data have been lost because they can't be restored, or suddenly your backup - successfully restored several times before - now can't be! This is still buggy and sometimes for unknown reasons restore of your data can fail ! Restore process always worked 100 % for me, but results sometimes differ !
YOU HAVE BEEN WARNED!
(decrypted vendor (or encryption disabler) + decrypted storage used)
Spoiler: Backup method A (not recommended):
- backup boot and data partition
Restore:
- wipe cache, dalvik, data
- flash ROM + GAPPS that you have installed when you created backup
- restore backup of boot and data partition
- remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !) but before reboot!
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Reboot
Comment(s):
- if you remove your password/PIN/pattern protection directly before backup you can end up after restore with system where you can't change your password/PIN/pattern anymore
- if you forget to remove your password/PIN/pattern protection AFTER RESTORE you can end up after boot with system demanding to enter your password/PIN/pattern which MAY or MAY NOT BE ACCEPTED even if it is CORRECT and maybe INACCESSIBLE because of that
- Google Pay will never be restored properly (or anything depending on actual password in time of backup), because of the removed password, you will need to set up it again after restore
Spoiler: Backup method B (recommended):
- backup super, boot, dtbo and data partition (metadata partition is optional)
Restore:
- wipe cache, dalvik, data (optional)
- restore super, boot, dtbo and data partition (metadata partition is optional)
Reboot
(everything will be restored to the state in time of the backup) ¹)
- if needed remove Android password (OFOX recovery functionality) restored from backup either directly after restore or later from the menu with OFOX addons (the file PassReset.zip MUST EXIST in this location: /storage/emulated/0/Fox/FoxFiles/ for this to work !)
- in case you lost your OFOX addons thanks to format data or you are using TWRP 3.5.0_10-x, you can also directly delete all file(s) in /data/system which starts with locksettings* = remove password
Comment(s):
¹) your backups will be fully restored along with password/PIN/pattern and fingerprints - this will work until you'll format data (or for something else that needs to be discovered yet), after that you'll loose the ability to use your password to enter the system and depending on ROM features you can either skip password entering with fingerprints (RRemix) or reset your password so you can enter the system (CrDroid), in RRemix everything works, except you can't change your password etc, in CrDroid you need to re-setup your password depending apps
- if you remove your password Google Pay will never be restored properly (or anything depending on actual password in time of backup), you will need to set up it again after restore
x x x(encrypted vendor and storage used)
Spoiler: Backup method A (OFFICIAL for OrangeFox & UNOFFICIAL for TWRP)
Backup:
- backup boot and data partition
Restore:
If you are restoring a data backup of an encrypted device, there are precautions that you should take before starting the restore process (obviously, your backup must be on MicroSD or other external storage medium - NOT on the internal storage):
Format the data partition (NOTE: format - not just wipe)
Reboot OrangeFox / TWRP
Flash the original zip of the ROM whose backup you are trying to restore
Wipe cache and dalvik
Reboot to system to ensure that the newly-flashed ROM actually boots, and that it re-encrypts the device with its own encryption
Reboot to OrangeFox / TWRP
Tap on the Backup icon
Select the partition(s) that you wish to restore
Swipe to restore
If you do not follow all these steps, you can expect problems with restoring data
Reboot
Comment(s): TBA
Credits: OrangeFox devs as this guide (for encrypted vendor and storage used) is copied directly from OrangeFox wiki slightly modified by me by adding "/ TWRP" to the text
this guide will be updated if I discover new facts or post new, updated steps or how-to's
Click to expand...
Click to collapse
Hello
I tried to do a backup with this orfox version including 'super'. At the end it says:
Backing up Super...
Backup Failed, Cleaning Backup Folder
Do you have a idea what happened?
Edit: I guess it's because my phone is encrypted
XtraWater said:
Hello
I tried to do a backup with this orfox version including 'super'. At the end it says:
Backing up Super...
Backup Failed, Cleaning Backup Folder
Do you have a idea what happened?
Edit: I guess it's because my phone is encrypted
Click to expand...
Click to collapse
Make sure you have enough space on the destination. Have a look at the OF log.
I guess this is as good a place as any to ask: what is the advantage of decrypting data?
I don't think running encrypted slows things down (not like it used to in the past when devices weren't as powerful), and there is the huge benefit of having your data secure. Any lost/stolen phone will soon send up in the hands of someone (on either side of the law) who knows adb/fastboot, so just having a password isn't going to protect your data if it's not encrypted.
It's possible to do backups of encrypted data, just the same as unencrypted.
Formatting vs wiping: ends up doing the same - all the data is gone and has to be restored. So that's a non-issue.
So, why should one prefer to decrypt?
temporarium said:
I guess this is as good a place as any to ask: what is the advantage of decrypting data?
I don't think running encrypted slows things down (not like it used to in the past when devices weren't as powerful), and there is the huge benefit of having your data secure. Any lost/stolen phone will soon send up in the hands of someone (on either side of the law) who knows adb/fastboot, so just having a password isn't going to protect your data if it's not encrypted.
It's possible to do backups of encrypted data, just the same as unencrypted.
Formatting vs wiping: ends up doing the same - all the data is gone and has to be restored. So that's a non-issue.
So, why should one prefer to decrypt?
Click to expand...
Click to collapse
From my understanding the only benefit would be to update firmware without format data.
re backup super: There are about 70GB available on the SD card (destination of the backup). I tried to backup it again with the same result. Just looking at the log file but can't see what has failed. The line before Backup failed is:
I:Error writing destination fd(operation not permitted)
XtraWater said:
From my understanding the only benefit would be to update firmware without format data.
re backup super: There are about 70GB available on the SD card (destination of the backup). I tried to backup it again with the same result. Just looking at the log file but can't see what has failed. The line before Backup failed is:
I:Error writing destination fd(operation not permitted)
Click to expand...
Click to collapse
Your card is probably formatted as fat32 which won't allow such big files.