Related
I have a LG G5 H850, with 6.0.1 and stock V10c-EUR-xx.
I disabled disk encryption using the no-verity-opt-encrypt.zip utility by jcadduono.
Now I wiped again using TWRP, but encryption is still disabled as the boot.img/partition still has his modifications to the fstab files (where he does
the change s/\bforceencrypt=/encryptable=/g etc.)
How to I set that back to as it was?
I got into this sitation as I kept finding TWRP could not access the partition - asked for password and there was none.
I do want to use encryption but in my first hour of setting up the phone I had a problem where when I booted into TWRP it would ask for a password and it was not "default_password", and I had not set anything and never used lock screen/pin etc. I tried setting a lock screen/boot screen password - the phone worked but TWRP could not access the filesystem. I tried the cryptfs application and still TWRP was not able to decrypt/access the partition.
Then I tried a terminal with vdc cryptfs changepw command and that just locked me out of the phone completely, as the new or old boot password would not work.
So I went for the no-verity-opt-encrypt.zip solution - but I dont want an unencrypted phone either. Now I want to try encryption and TWRP again - this time setting a pin at the first setup screen opportunity to see if that gets set as the password that TWRP could use. However I can't remove the disable encryption patch!
Ideally I am trying to get to a setup where:
encryption is enabled
I want to be able to boot TWRP and access the encrypted filesystem and install more zip files such as xposed/supersu updates etc anytime in the future.
I dont want to use the "no-verity-opt-encrypt.zip" patch.
I do not want TWRP to be locked out from modifying the encrypted system partition.
Additionally, I havbe not been able to install xposed using TWRP and the zip file (http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip) .
In TWRP it installs, I dont see any errors, but on boot up I have no xposed icon. I have been able to install it by downloading the apk and installing as an untrusted source, not sure if there is something wrong in having to do it this way?
Thanks.
current TWRP build for G5 doesn't support encryption
you can use encryption but in TWRP you won't be able to access some partitions (if I remember right is data partition but I might be wrong here)
in order to do so, you need to restore base firmware with LGUP that will turn encryption back on
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
tomb007 said:
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
Click to expand...
Click to collapse
may i ask how did you root it after that? because everytime i try to rooted while encrypted,i flash the zip in twrp (with no errors) but system still has no root! the only way i could root was to format /data in twrp, hence have a decrypted phone!
I am looking for the same thing as you are : encrypted phone with twrp and root access.
I rooted using TWRP adding supersu at the time of installing the OS before the OS encrypts the partition. Once the partition is encrypted TWRP can no longer access it, and I can no longer install supersu or anything else.
I may have installed root before encrypting, then reflashed the boot partition so that encryption is re-enabled, then ran twrp to reapply supersu - which would fail to put files on the encrypted partition - but this is fine as they were already there, and let the twrsp supersu installation modify the boot partition.
The result is an encrypted phone with root and TWRP. However, TWRP can not access the encrypted partition so I don't think I can update supersu using TWRP, and I dont think I can patch the OS easily without wiping the encrypted data and reinstalling everything due to this. As I am not sure if updating the OS works without wiping data, I have yet to try that.
you shouldnt have to mess with data at all to use supersu while encrypted.
my g5 is encrypted and always has been (besides in various testing) and there's never been an issue of flashing supersu.
though there may be some issues if trying to restore encryption and flashing supersu in the same reboot cycle.
and yes, data partition in twrp cant be accessed in twrp if encrypted.. but you can just push a file to the /tmp directory while in twrp and then flash anything... or enable adb sideload and flash something that way... or use an external sd card and put the file on there. the only thing you really miss out of if using twrp while encrypted is being able to manipulate the data partition... it does not stop you from flashing files or running scripts that modify /system or other partitions (besides /data).
supersu uses the unencrypted /cache/ partition to work in when you flash it while encrypted so an encrypted /data partition should not be relevant.
I flashed twrp on my redmi 6a, but i haven't been able to succeed at formatting data, or anything from advanced wipe. Also ADB sideload has refused to start. First i thougt it was because of the encrypted data and tried every way to decrypt like flashing universal disabler before magisk. I noticed that preserve force encryption in magisk was unticked but twrp still asked for the password and also my root was screwed big time and most apps couldn't find it, so i flashed the stocked rom and started afresh, now i want to try resurrection remix(not sure it's a good idea) but process is involved with formatting data and advanced wipe. I'm using twrp 3.2.3.2-cactus. Some help
it seems that no one can solve encryption problem in twrp?
All google result said that this should be formatting data partition. One question is: how could the format partition data whlie the partition is untouchable?
adista said:
it seems that no one can solve encryption problem in twrp?
All google result said that this should be formatting data partition. One question is: how could the format partition data whlie the partition is untouchable?
Click to expand...
Click to collapse
Use the TWRP-1020 one.
jonaaa, how does that work any different.
Update May 23 2019
Now with new Twrp wzsx150 u dont need to follow this Tutorial to get full Backup to work because twrp can Auto decrypt your files
For all Who followed the guide already and want a encrypted device. Do a Format and dont use remove forceencrypt.
New twrp
https://mega.nz/#!TG4RwCrJ!9E0gOOoDaWjtSIS9GoB0pGvCc2BhRU7rSTNNJbAeUxc
---------------------------
Hello
Many people ask me to make a Tutorial HowTo have a full decrypt phone with full backup working.
Before we start u need to flash the newest Recovery from wzs150 Team https://mega.nz/#!WOZEBCpD!UlyCdDaP-UxuwvzLzDE4yzaqi5qMz-I8iOkseQ5gmP0
Steps to flash recovery should be already known or are available in other Threads on xda
So Now lets begin.
First of all you need to know you need to do format Data through the following process. So Backup your Data on your PC, TWRP NOT working
Lets Start.
1. Boot into TWRP
2. Format Data in Wipe Section (The one you need to type yes) i dont reboot TWRP after that
3. Flash the Rom u want
4. Go Back to the Start Screen of TWRP and Click "Advanced" and "RM Forceencrypt"
5. Uncheck "Remove DM Verity" and check "Remove Forceencrypt"
6. Now youre phone is full decrypted and Backup of all partitions are working
7. If u want Magisk flash it now
Notes:
Dont boot your phone before you did the "RM Forceencrypt" step or your decryption gets lost
If u update ur Rom you ALWAYS need to do Step 4 and 5
If u coming from another Rom and want to restore the Rom u need also to restore "Boot"
If u flashing now another Rom you dont need to do format data,wipe data is enough, but always RM Forceencrypt after Rom Flash
Have a nice day
Greetings from Germany
Nice, thx for that ! =)
Great tutorial thanks. Less frustrated flash rounds.
Verstuurd vanaf mijn MI 9 met Tapatalk
MangoMC said:
If u coming from another Rom and want to restore the Rom u need also to restore "Boot"
Click to expand...
Click to collapse
Was does it mean 'restore BOOT'?
Cheers
Toscha
toscha42 said:
Was does it mean 'restore BOOT'?
Cheers
Toscha
Click to expand...
Click to collapse
Boot is one of the Partitions u can Backup. Its where Ur Kernel is located
I dont uncheck "Remove DM Verity" and working too. I select both. Good guide, thanks.
Thanks for this!
Thanks for the step. I can backup now.
But the next time I update, always need to repeat "Remove Forceencrypt"; otherwise, phone cannot boot.
Assume this is needed until future update twrp version. a bit inconvenient, but ok.
Hello. I now use xiaomi.eu I don't want to format data.
I do a step 4 and 5 and can't backup. When I want to boot system nothing.....
I back to Twrp and make reverse step 5 and flash the same rom I have and system working fine. How to make backup without format data?
Wysłane z mojego MI 9 przy użyciu Tapatalka
Not possible. Maybe only wipe of data works but i didnt tested it. Twrp cant decrypt the data on your Phone it can only prevent the Phone to encrypt it
still no encryption support with twrp beta 10 people call formatting data "decrypt" or "unencrypt" all across board, so it adds to false expectations. would never turn off encryption to get, like, backup?
MangoMC said:
Update May 23 2019
Now with new Twrp wzsx150 u dont need to follow this Tutorial to get full Backup to work because twrp can Auto decrypt your files
For all Who followed the guide already and want a encrypted device. Do a Format and dont use remove forceencrypt.
New twrp
https://mega.nz/#!TG4RwCrJ!9E0gOOoDaWjtSIS9GoB0pGvCc2BhRU7rSTNNJbAeUxc
---------------------------
Hello
Many people ask me to make a Tutorial HowTo have a full decrypt phone with full backup working.
Before we start u need to flash the newest Recovery from wzs150 Team https://mega.nz/#!WOZEBCpD!UlyCdDaP-UxuwvzLzDE4yzaqi5qMz-I8iOkseQ5gmP0
Steps to flash recovery should be already known or are available in other Threads on xda
So Now lets begin.
First of all you need to know you need to do format Data through the following process. So Backup your Data on your PC, TWRP NOT working
Lets Start.
1. Boot into TWRP
2. Format Data in Wipe Section (The one you need to type yes) i dont reboot TWRP after that
3. Flash the Rom u want
4. Go Back to the Start Screen of TWRP and Click "Advanced" and "RM Forceencrypt"
5. Uncheck "Remove DM Verity" and check "Remove Forceencrypt"
6. Now youre phone is full decrypted and Backup of all partitions are working
7. If u want Magisk flash it now
Notes:
Dont boot your phone before you did the "RM Forceencrypt" step or your decryption gets lost
If u update ur Rom you ALWAYS need to do Step 4 and 5
If u coming from another Rom and want to restore the Rom u need also to restore "Boot"
If u flashing now another Rom you dont need to do format data,wipe data is enough, but always RM Forceencrypt after Rom Flash
Have a nice day
Greetings from Germany
Click to expand...
Click to collapse
Is the b17 still good if I want to decrypt ? b17 and follow the rest of the decryption steps you have mentioned ?, or shall I flash b10 if I want decryption ? cheers.
vtec303 said:
Is the b17 still good if I want to decrypt ? b17 and follow the rest of the decryption steps you have mentioned ?, or shall I flash b10 if I want decryption ? cheers.
Click to expand...
Click to collapse
U can use both to decrypt with my tutorial. B17 only can decrypt the Data Partition while its encrypted. So u can Backup All data with b17 without the need of remove forceencrypt
MangoMC said:
U can use both to decrypt with my tutorial. B17 only can decrypt the Data Partition while its encrypted. So u can Backup All data with b17 without the need of remove forceencrypt
Click to expand...
Click to collapse
OK cool, I get it, thanks for the quick reply, cheers
simcold said:
Hello. I now use xiaomi.eu I don't want to format data.
I do a step 4 and 5 and can't backup. When I want to boot system nothing.....
I back to Twrp and make reverse step 5 and flash the same rom I have and system working fine. How to make backup without format data?
Wysłane z mojego MI 9 przy użyciu Tapatalka
Click to expand...
Click to collapse
I've not ried it yet as I don't have the phone yet, but apparently this twrp (mi9-3.3.0-9.0-b17) supports encryption, you can use it to backup your encrypted data partition. Though, I'm probably too late and you've wiped already...
EDIT, just read the rest of the thread, seems I'm a bit late to the party! That twrp is already mentioned!!
I just installed B17 and backed up to SD. Seemed to work fine
picitup said:
I just installed B17 and backed up to SD. Seemed to work fine
Click to expand...
Click to collapse
Is that the twrp full rom backup you are talking about ?, backup has always worked for me its the restore which does't works and always ends up with an error, cheers
vtec303 said:
Is that the twrp full rom backup you are talking about ?, backup has always worked for me its the restore which does't works and always ends up with an error, cheers
Click to expand...
Click to collapse
Ahhh no. I tried to backup with earlier versions of TWRP and they failed with an error message. This version seemed to backup OK, but I've not tried a restore yet.
I'm just playing with Titanium backup so once I've got a good backup with that, I'll try TWRP B17 and report back.
Cheers
@vtec303 I just had a play and restore seems to work fine. My TWRP is:
recovery-mi9-3.3.0-9.0-b17.img by wzsx150.
Here's what I did:
Booted into TWRP and backed up Data, System and Boot to an OTG SD card
In TWRP performed a factory reset.
Booted into System, went through the Android setup (not wifi) and checked that all my 3rd party apps had disappeared, I had no SMS or calendar events.
Booted into TWRP and did a restore of all 3 partitions from the previous backup.
Booted into System and found all my 3rd party apps, SMS, Calendar and could browse the web so wifi was configured.
Hope this helps
Cheers
Just a bit extra....
As we know, TWRP doen't back up media data (photos music etc) but I was interested to spot that a factory reset using TWRP doesn't delete all that data either. Pretty handy for me as I'm testing out some backup packages and I don't have to restore all my media files lol.
Cheers
I have TWRP installed, but when I wipe data, encryption still is active. TWRP is essentially useless if it can't access /data to do a complete backup/restore. Can someone post steps of how to remove encryption?
You need to install a file called TREBLE-Disable-Forceencrypt using TWRP. Here is the link : https://androidfilehost.com/?fid=1322778262904004415
Make sure to FORMAT DATA in TWRP (not a simple /data wipe, a format, where you need to type yes) and then flash your new system and after that this zip.
_cab13_ said:
You need to install a file called TREBLE-Disable-Forceencrypt using TWRP. Here is the link : https://androidfilehost.com/?fid=1322778262904004415
Make sure to FORMAT DATA in TWRP (not a simple /data wipe, a format, where you need to type yes) and then flash your new system and after that this zip.
Click to expand...
Click to collapse
Thanks cab13, that did the trick. Appreciate it. I backed up, and then deleted the /data partition, and TWRP warned "No OS"! Restored my backup, so all is working in both directions with TWRP. Thank You!
No big deal Enjoy your phone.
I've created a thread for the Umidigi One Max modding, check it out : https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/
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.