Hey guys,
Just installed my first rom and my head is spinning at the unanswered questions i have.
my first question is regarding clockworkmod
if i go into "apply update from .zip..." theres an option that says "apply /sdcard/update.zip". That option was there even before i loaded a custom rom. If i clicked on that when I have a custom rom running, what exactly does it do. My understanding is that "update.zip" is from the original rom. Is that correct?
Second question
What is the difference between doing a wipe data/factory reset from CWM when compared to doing it through the settings menu?
I never make a back up because I have no issues starting over but i just realized that some roms require you to install it with a "stock device." If a rom requires a stock start, does that mean you have to odin and wipe it to the stock rom before installing that specific rom?
If a rom doesn't require you to have the stock rom, does that mean you can just flash over custom rom after custom rom?
In those situations, do you move the rom.zip to the root folder THEN go into CWM and wipe dalvik THEN choose "install zip" or is it another order?
Under mounts and storage, what does "format/system" do? is that the same as "wipe data/factory reset"?
maybe i should just go back to iphone. this is just a cluster**** of info.
Update.zip is old stuff, as you suspected its to do with official updates. Cwm works across many devices that's why it's still there.
Your phone is divided into several partitions. They are prefixed with a / because the Linux convention treats partitions exactly the same as directories. Unless you have been living under a rock you probably know android is a fork of Linux.
/boot contains the Linux kernel
/recovery contains the recovery mode software, in your v case cwm.
/system holds the system apps and files.
/cache is similar to the swap file on a Windows pc or the /tmp directory on Linux. Dalvik cache is stored here as well although I'm not 100% site how that works. It's something to do with the java runtime.
/data is all your user settings and apps.
Factory reset wipes /data and /cache thus removing all installed apps and your account settings etc. A factory reset achieves the same thing regardless if you launch it in cwm or from the settings menu.
When changing roms you don't need to go back to stock first, it's just the way some devs have written their instructions. You should however always wipe /cache when changing roms. A full wipe is not usually required unless you are changing to a completely new base e.g. upgrading from an xxalf Rom to xxlfb you shouldn't need full wipe or going from one xxlfb Rom to another shouldn't need wipe. Changing from a Samsung based Rom to something like Cyanogenmod you should always full wipe.
Always wipe before flashing as some roms modify /data.
Sent from my GT-I9300 using Tapatalk 2
dr.m0x said:
Update.zip is old stuff, as you suspected its to do with official updates. Cwm works across many devices that's why it's still there.
Your phone is divided into several partitions. They are prefixed with a / because the Linux convention treats partitions exactly the same as directories. Unless you have been living under a rock you probably know android is a fork of Linux.
/boot contains the Linux kernel
/recovery contains the recovery mode software, in your v case cwm.
/system holds the system apps and files.
/cache is similar to the swap file on a Windows pc or the /tmp directory on Linux. Dalvik cache is stored here as well although I'm not 100% site how that works. It's something to do with the java runtime.
/data is all your user settings and apps.
Factory reset wipes /data and /cache thus removing all installed apps and your account settings etc. A factory reset achieves the same thing regardless if you launch it in cwm or from the settings menu.
When changing roms you don't need to go back to stock first, it's just the way some devs have written their instructions. You should however always wipe /cache when changing roms. A full wipe is not usually required unless you are changing to a completely new base e.g. upgrading from an xxalf Rom to xxlfb you shouldn't need full wipe or going from one xxlfb Rom to another shouldn't need wipe. Changing from a Samsung based Rom to something like Cyanogenmod you should always full wipe.
Always wipe before flashing as some roms modify /data.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
thank you for taking the time out to write that.
What is the difference between advanced restore and advanced back up against regular restore and back up (in CWM).
Also, which exactly do i have to wipe. Which cache? There are three different options i think.
Lastly, if i made a nandroid backup of the rooted stock rom in its stock form with no mods, do i still have to wipe the cache when i install a new rom?
fruitycups said:
thank you for taking the time out to write that.
What is the difference between advanced restore and advanced back up against regular restore and back up (in CWM).
Also, which exactly do i have to wipe. Which cache? There are three different options i think.
Lastly, if i made a nandroid backup of the rooted stock rom in its stock form with no mods, do i still have to wipe the cache when i install a new rom?
Click to expand...
Click to collapse
Advanced backup and restore lets you choose which partitions to backup or restore, vs the standard option which backs up everything.
As I mentioned earlier you only need to wipe the cache. Dalvik cache is a sub directory of /cache so wiping /cache will wipe that also.
You should always wipe /cache when installing a new Rom. It doesn't affect anything from the user perspective except that first boot will be long while android rebuilds the cache. It probably isn't strictly necessary when moving to roms with the same base but can't hurt since it has no negative impact. Even factory updates wipe the cache automatically for you. Some custom roms do as well but better safe than sorry since most don't tell you either way in the description.
Sent from my GT-I9300 using Tapatalk 2
Hi,
since 2 days I have a very annoying problem: my GT 7510 reboots every 2 min.
this is not a bootloop! I can successfully boot and work - but only for about 2 mins.
then the device reboots.
What I had done:
due to low disk space, I deleted my old nandroid backups (pre 10.1) using 'file explorer'.
then I turned on the setting "root explorer" in 'file explorer' to access the newer nandroid backups.
I wanted to copy them to a usbstick. this failed.
So I decided to delete these backups as well (using 'file explorere').
this task somehow failed and the device rebooted unexpectedly.
since then, the device keeps rebooting after about 2 min.
what I had tried:
- install previous rom zip ( cm-10.1-20130116-UNOFFICIAL-pd4wifi.zip) --> no success, still rebooting
- reinstall latest rom zip on device (cm-10.1-20130208-NIGHTLY-p4wifi.zip) --> no success, still rebooting
- wipe cache --> still rebooting
- wipe cache + dalvic -> still rebooting
- factory reset -> still rebooting.
I am now back on cm-10.1-20130116-UNOFFICIAL-pd4wifi.zip (flashed over cm-10.1-20130208-NIGHTLY-p4wifi.zip)
I also noticed that I cannot do successful backups anymore.
in recovery > backup, it reboots while data is being backup up.
problem now is:
a) I don't have any backups anymore on the sdcard which I could restore
b) when trying to copy backups to /data/media/clockworkmod/ , the device reboots after 2 min (2mins not enough time to copy 4 GB dump
luckily, the 2min were enough to install 'remotelogcat'.
I run it on my notebook. the logcat is attached.
(the logcat output is an .html file which I zipped)
Hope someone can have a look and find out what is happening and why.
edit: attachment removed because I was able to solve this myself
Any help is appriciated.
tnx a lot
thg-droider
Update:
I did some test using adb (on Windows 7).
Findings:
- copying a handfull of files from tablet to pc works
- copying a handfull of files from pc to tablet works
BUT: when I try to copy an old nandroid backup from pc to tablet, the tablet reboots...
Question: is it possible that the internal sdcard of the tablet is somehow 'broken' ?
if this was the case: would the cmd in CWM 6.0.2.7 recovery potentially help?: "mounts and storage" > "format /data and /data/media (sdcard)"
anyone with a better idea?
tnx
Update 2:
I ended up formatting /data in recovery using "mounts and storage" > "format /data and /data/media (sdcard)"
Doing so, I obviously lost all my stuff.
But luckily, I had a (not to old) backup of TitaniumBackup, which I was able to copy from pc to tablet after the setup.
With this, I was able to restore most of my stuff. :good:
My persoanl lesson learned:
1. do backups on a regualar schedule!
2. save the backups to pc (or another media, e.g. usb stick)
3. don't delete 'old' backup files using a 'file manager', but use the 'delete' option in CWM > "backup and restore"
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.
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.