Related
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running
Hi folks.
I've just acquired a Xiaomi Redmi Note 3, and I have officially unlocked the bootloader, and installed Redwolf Recovery, Magisk, and the Pixel Experience Oreo ROM, and the phone was working for a few days without issues.
Today however, whenever I boot into my phone, force close errors pop up at three errors per second, and when I try to perform a factory reset and reinstall a ROM, the current, yet corrupt installation remains, and I cannot get rid of it.
Is there any way to solve this issue, as this is the first time I have experienced this?
Thanks.
aha360 said:
Today however, whenever I boot into my phone, force close errors pop up at three errors per second, and when I try to perform a factory reset and reinstall a ROM, the current, yet corrupt installation remains, and I cannot get rid of it.
Click to expand...
Click to collapse
Hi, you need to do advanced wipe in recovery and wipe /system, /data, /cache, /dalvik, /ART before installing a new ROM.
Should your preferred ROM still produce this issue, please try for a quick test https://download.lineageos.org/kenzo
You don't need Magisk to root LOS.
:good:
k23m said:
Hi, you need to do advanced wipe in recovery and wipe /system, /data, /cache, /dalvik, /ART before installing a new ROM.
Should your preferred ROM still produce this issue, please try for a quick test https://download.lineageos.org/kenzo
You don't need Magisk to root LOS.
:good:
Click to expand...
Click to collapse
Thank you very much for that. I actually did that before you suggested this to me, and I'm back up and running now.
However, one thing I have learned is that you shouldn't add any files to internal storage AFTER doing a full, destructive wipe and AFTER installing anything from there, as those files will disappear while the storage gets occupied in the process, so I ended up having to repeat the process, but with the required files ON THE microSD CARD.
Another thing I have learned from this is to not install a custom ROM on encrypted storage and double-check the encryption status BEFORE flashing a ROM as I now know that some stock ROMs automatically encrypt the /data/ and /data/media/ partitions, which is a huge pain in the backside.
Lesson of the day: even if you think you're familiar with custom ROMs and installing them, there are times whereby you'll end up hitting brick wall dilemmas like this one.
aha360 said:
Thank you very much for that. I actually did that before you suggested this to me, and I'm back up and running now.
However, one thing I have learned is that you shouldn't add any files to internal storage AFTER doing a full, destructive wipe and AFTER installing anything from there, as those files will disappear while the storage gets occupied in the process, so I ended up having to repeat the process, but with the required files ON THE microSD CARD.
Another thing I have learned from this is to not install a custom ROM on encrypted storage and double-check the encryption status BEFORE flashing a ROM as I now know that some stock ROMs automatically encrypt the /data/ and /data/media/ partitions, which is a huge pain in the backside.
Lesson of the day: even if you think you're familiar with custom ROMs and installing them, there are times whereby you'll end up hitting brick wall dilemmas like this one.
Click to expand...
Click to collapse
U only need to do format data option if u come from miui rom. Coz miui encrypts the data and internal sd. So format data option is must.
Moving from one custom rom to another u dont need format data. Only wipe data reset is enough.
If u have any important document . keep it in external sd. If something goes wrong or custom rom cant boot then we use format data option which erases ur internal sd too.
No need to encrypt the device. Just install the rom which comes with selinux enforcing which is enough to protect ur userspace.
naik2902 said:
U only need to do format data option if u come from miui rom. Coz miui encrypts the data and internal sd. So format data option is must.
Moving from one custom rom to another u dont need format data. Only wipe data reset is enough.
If u have any important document . keep it in external sd. If something goes wrong or custom rom cant boot then we use format data option which erases ur internal sd too.
No need to encrypt the device. Just install the rom which comes with selinux enforcing which is enough to protect ur userspace.
Click to expand...
Click to collapse
Muchos gracias.
Also, I have a microSD card for that very reason, which is to keep all my files that I want to keep separate and safe from destructive deletion, and I have now learned that stock ROMs like the MIUI ROM encrypt the data and internal shared storage partitions, and that I have to do a full, destructive, internal storage wipe whenever I migrate to a custom ROM FROM a stock ROM.
Also, I frankly don't give a two sh!ts about storage encryption and SElinux policies as they're far too inconvenient for the trade-off in terms of technological security versus technological freedom, so I installed The SELinux Switch app from here, and I intend to leave the device decrypted for the aforementioned reasons.
aha360 said:
Also, I frankly don't give a two sh!ts about storage encryption and SElinux policies as they're far too inconvenient for the trade-off in terms of technological security versus technological freedom, so I installed The SELinux Switch app from here, and I intend to leave the device decrypted for the aforementioned reasons.
Click to expand...
Click to collapse
Exactly. When we unlock bootloaders and root our devices we choose freedom and the remaining constrictions like SElinux and encryption are, in this context, completely useless shackles. Furthermore, encryption contributes to NAND flash wear and premature device failure.
:highfive:
k23m said:
Exactly. When we unlock bootloaders and root our devices we choose freedom and the remaining constrictions like SElinux and encryption are, in this context, completely useless shackles. Furthermore, encryption contributes to NAND flash wear and premature device failure.
:highfive:
Click to expand...
Click to collapse
Not only that - SELinux, when set to Enforcing, restricts certain simple commands and shoves them unnecessarily behind root privileges, like "reboot bootloader", or "reboot -p", or "reboot fastboot", or "reboot recovery", or "reboot". I'm not going to wait 60 seconds for a device to reboot into recovery - screw that.
Hell, even having SELinux set to Enforcing can interfere with or block infrared beam access. Stupid crap I tell ya.
Is there anything way that i can disable data encryption? Both TWRP and orange fox not allow me to install anything and asking for password, i tried both lock password and mi password but nothing. I am trying to root my phone, i also tried to make a patched boot image with magisk manager but not install button was showing up.Any solution?
Stock rom with miui global 10.3.1.0 version
tzagaritos said:
Is there anything way that i can disable data encryption? Both TWRP and orange fox not allow me to install anything and asking for password, i tried both lock password and mi password but nothing. I am trying to root my phone, i also tried to make a patched boot image with magisk manager but not install button was showing up.Any solution?
Stock rom with miui global 10.3.1.0 version
Click to expand...
Click to collapse
Don´t waste your time trying to decipher the password, they´re advanced algorithms that Android uses to make the Encryption-By-Default to protect data user not a personal password that can be easily decoded.
You can flash any zip using adb sideload through Advanced options in recovery, the problem would be trying to boot up due to AVB implementation, I never cared about format data when is needed so my important files I ever have on my external SDCard.
Some members refer that such recovery can decrypt data or not, this is not a problem by its own but the ability to boot. The simple way to decrypt data is formatting it.
As a side note decrypt data will be required just in some cases like when you unlocked for first time, when you are coming back to a Miui upgraded rom then to an AOSP one but most of custom roms based on Miui don´t have encryption like ROS, Xiaomi.eu or Mi-Globe.
SubwayChamp said:
Don´t waste your time trying to decipher the password, they´re advanced algorithms that Android uses to make the Encryption-By-Default to protect data user not a personal password that can be easily decoded.
You can flash any zip using adb sideload through Advanced options in recovery, the problem would be trying to boot up due to AVB implementation, I never cared about format data when is needed so my important files I ever have on my external SDCard.
Some members refer that such recovery can decrypt data or not, this is not a problem by its own but the ability to boot. The simple way to decrypt data is formatting it.
As a side note decrypt data will be required just in some cases like when you unlocked for first time, when you are coming back to a Miui upgraded rom then to an AOSP one but most of custom roms based on Miui don´t have encryption like ROS, Xiaomi.eu or Mi-Globe.
Click to expand...
Click to collapse
thanks a lot , i did not know that i could flash zip files in that way, you saved me thanks again
use the custom TWRP by wzsx150, decryption is working with that one https://forum.xda-developers.com/mi-8-Lite/development/mi-8-lite-twrp-t3850019
borg4571 said:
use the custom TWRP by wzsx150, decryption is working with that one https://forum.xda-developers.com/mi-8-Lite/development/mi-8-lite-twrp-t3850019
Click to expand...
Click to collapse
Is possible to send me the img file through Google drive or anything familiar;its a mess trying yo download from the Chinese site
I have Android pie
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
whats a good backup software/apps for this. i am running pixel experience i get data wipe when i update the os. is there an app to backup pictures, contacts etc
Heimex said:
whats a good backup software/apps for this. i am running pixel experience i get data wipe when i update the os. is there an app to backup pictures, contacts etc
Click to expand...
Click to collapse
I use migrate.
Migrate will work for apps and contacts etc. but not for personal files like photos, videos etc. I don't know of any app which does that. Only backup/copy to PC and restore.
Heimex said:
whats a good backup software/apps for this. i am running pixel experience i get data wipe when i update the os. is there an app to backup pictures, contacts etc
Click to expand...
Click to collapse
I use Google backup to backup my app list installed from Play Store and also contacts etc. Then I use Swift Backup to backup apps with data and apps that isn't available in PS. For photos and videos etc, you can just use SD card or transfer through PC or sync with Google Photos. Or you can just skip wiping internal storage everytime flashing new rom.
MFAR198 said:
I use Google backup to backup my app list installed from Play Store and also contacts etc. Then I use Swift Backup to backup apps with data and apps that isn't available in PS. For photos and videos etc, you can just use SD card or transfer through PC or sync with Google Photos. Or you can just skip wiping internal storage everytime flashing new rom.
Click to expand...
Click to collapse
how do i skip wiping internal storage whenever i flash the update of rom?
Heimex said:
how do i skip wiping internal storage whenever i flash the update of rom?
Click to expand...
Click to collapse
Something is wrong either with your setup or the way you flash. It is not necessary to wipe internal storage everytime you flash a ROM. Looks to be an encryption/decryption issue. Unless you have an incompatible TWRP (which should usually handle encryption/decryption), you should not face this. Wiping/formatting internal storage may be required occasionally like when people try to flash the OOS Pie.
Did you ask in the ROM thread?
tnsmani said:
Something is wrong either with your setup or the way you flash. It is not necessary to wipe internal storage everytime you flash a ROM. Looks to be an encryption/decryption issue. Unless you have an incompatible TWRP (which should usually handle encryption/decryption), you should not face this. Wiping/formatting internal storage may be required occasionally like when people try to flash the OOS Pie.
Did you ask in the ROM thread?
Click to expand...
Click to collapse
yes in the recent update of PE rom, it was an encryption/decryption issue which led to the loss of my data. Is there a way around this?
Heimex said:
yes in the recent update of PE rom, it was an encryption/decryption issue which led to the loss of my data. Is there a way around this?
Click to expand...
Click to collapse
Don't use DFE ever and don't go back to a previous version of vendor-firmware. And possibly TWRP.
guhvanoh said:
Don't use DFE ever and don't go back to a previous version of vendor-firmware. And possibly TWRP.
Click to expand...
Click to collapse
so after each dirty flash, i should let the encryption process continue upon restart of phone?
Heimex said:
so after each dirty flash, i should let the encryption process continue upon restart of phone?
Click to expand...
Click to collapse
So here's the thing. Your fone comes naturally with encryption. You go and turn it off by flashing DFE. Then you make a booboo by forgetting to flash DFE after you update vendor/firmware. And now you're sol. Avoid the problem, don't use DFE. If you want to move to a different from, back up your data to external drive, do your fresh install and restore your data as needed. That's what I do and have never had any problems.
guhvanoh said:
So here's the thing. Your fone comes naturally with encryption. You go and turn it off by flashing DFE. Then you make a booboo by forgetting to flash DFE after you update vendor/firmware. And now you're sol. Avoid the problem, don't use DFE. If you want to move to a different from, back up your data to external drive, do your fresh install and restore your data as needed. That's what I do and have never had any problems.
Click to expand...
Click to collapse
ok thanks for clearing it up. However, if i were to not flash DFE on the next update of pixel experience and subsequent updates, will i lose all my data on the next update upon completion of encryption process?
Heimex said:
ok thanks for clearing it up. However, if i were to not flash DFE on the next update of pixel experience and subsequent updates, will i lose all my data on the next update upon completion of encryption process?
Click to expand...
Click to collapse
If you've already flashed DFE, you need to remember to flash it immediately after flashing vendor/firmware next time. If you only update PE without updating vendor/firmware you should be fine. Note that in many instances these days updating PE requires updating vendor/firmware, therefore you may need to flash DFE if and only if you already use it. In my case I'm encrypted, therefore all I need to do flash vendor/firmware and PE. I don't use DFE.
Hope this clears the air.