backup and restore moto g6 play rooted - Moto G6 Play Questions & Answers

moto g6 play oreo rooted
how can i make a complete, data / system / boot image backup that wont break root or boot.. now that i have my device setup and debloated can i use fast boot adb
adb pull /system.image ???
adb pull /boot.image ????
will this give me a complete backup of my device as it is now ??
or can i do it with twrp as normal seems like i read twrp wont backup internal data? and maybe not a good choice for boot image?

dotzip. said:
moto g6 play oreo rooted
how can i make a complete, data / system / boot image backup that wont break root or boot.. now that i have my device setup and debloated can i use fast boot adb
adb pull /system.image ???
adb pull /boot.image ????
will this give me a complete backup of my device as it is now ??
or can i do it with twrp as normal seems like i read twrp wont backup internal data? and maybe not a good choice for boot image?
Click to expand...
Click to collapse
Twrp can back up and restore, data, system, oem, vendor, boot, and cache without any issues. If you are encrypted twrp will not be able to backup /data, but that's it. Twrp also does not backup the internal sdcard if that's what you're curious about. That's because if you don't have an external sdcard, twrp will create the backups on your internal sdcard instead.
For a full backup you'll want everything but cache selected in twrp. Cache isn't needed.

Related

[Q] more elegant way to wipe and then restore EVERYTHING

Hi-
If i want to not only wipe system, data, cache but the /data/media partition as well before installing a new ROM, what's the least onerous method for restoring all my data after flashing the new ROM? currently all i know to do is backup my data, wipe everything, then restore factory image via adb, then copy zips to the device, flash desired ROM, then copy back data via adb or from dropbox after installing app
Is there an easier way?
titanium backup is the easiest way.
just dont restore system apps.
1. Run a backup in titanium backup
2. Copy the contents of your /data/media partition to your PC via adb or MTP (this should include your TiBu backup)
3. Wipe System, Data, Userdata, and the caches via method of your choice
4. Copy the contents of your /data/media backup back to /data/media via adb
5. Use adb to push a ROM of your choosing to /data/media (assuming you didn't have one in your /data/media backup, and assuming you're not using fastboot to flash a stock image)
6. Flash away (Recovery, if needed, and System via either fastboot or CWM/TWRP)
7. Download TiBu from the Play Store
8. Restore non-system apps/data in TiBu
However, if you're going to make a backup of /data/media and then restore it immediately after wiping it, I have to ask why? It's a time consuming process (transferring gigs via adb is very slow) and would provide no benefit to your device.
Also, if you're going from Android 4.1.x to 4.2.x, make sure your /data/media backup goes back in /data/media/0, or the OS will not see the files as being on your "external" storage.
Zepius said:
titanium backup is the easiest way.
just dont restore system apps.
Click to expand...
Click to collapse
Oh im definitely using titaniumbackup to restore apps, but i was mostly referring to restoring the contents of the sdcard
Thanks!
jackbane said:
Oh im definitely using titaniumbackup to restore apps, but i was mostly referring to restoring the contents of the sdcard
Thanks!
Click to expand...
Click to collapse
Using twrp I wipe cache, davlik, factory reset, and system and my sdcard is untouched. I was told by a dev to also delete the android folder in my sdcard using the twrp file manager.
No need to flash stock image when wiping everything just fast boot flash the rom you want and adb is the best way to restore your sdcard
Cilraaz said:
However, if you're going to make a backup of /data/media and then restore it immediately after wiping it, I have to ask why? It's a time consuming process (transferring gigs via adb is very slow) and would provide no benefit to your device.
Click to expand...
Click to collapse
I know, I know...I have this idea of after flashing many different ROMs and finding my keeper, that I would totally wipe the device and then install a super clean ROM, and start with a virgin /data/media partition, bringing back only what I want. I recognize that this is probably unnecessary and says more about my desire for neatnes than anything else.
But thanks for the detailed instructions. Until now, I have been using the GNex Toolkit downloaded from the sticky in the dev forum to handle all pushes and pulls and adb duties. I thought that to push a file to the device, it had to be in Android mode. This is why I found myself having to flash the stock rom just to copy back the contents of /data/media. It sounds like, from the posts in this thread, that I don't need to, that I should be able to copy the files from fastboot mode? Or do I temporarilty boot into an image to push files, then flash the ROM from TWRP. (I'm using TWRP 2.4.1.0, btw).
If I could avoid installing the factory ROM, just to copy back /data/media/, that's what I'm looking for. Do you know if this is possible using the GNex toolkit?
Thanks again!
you have full ADB access within any custom recovery. toolkits not required.
Zepius said:
titanium backup is the easiest way.
just dont restore system apps.
Click to expand...
Click to collapse
I always wondered about this. Does the stock browser qualify as a system app? Should i not use titanium to restore any of the gapps?
jackbane said:
I always wondered about this. Does the stock browser qualify as a system app? Should i not use titanium to restore any of the gapps?
Click to expand...
Click to collapse
The best option for titanium, is to select BATCH, RESTORE MISSING APPS+DATA
Go down the list and deselect anything you DONT want restored. everything else should be OK on that screen.
Also, make sure you have the pro license, otherwise batch jobs are a PITA
There is also an option in the MENU button - BACKUP TO XML
This option allows you to backup call logs, wifi networks, mms/sms, bookmarks separately from the other backups and works 100% going rom to rom.
Everybody is recommending TiBU, and I concur, but OP is talking about all the other contents of the sdcard..
I actually just did this today. I had been on cm10.1 but went back to cm10 for a while, getting the extra /0/ folder and all. I was going to just copy EVERYTHING over to my comp, but ended up just copying a few music folders and a few backup folders. After flashing cm10.1 and gapps, I formatted the sdcard. Now I'm transferring those few folders back. I had a FULL sdcard before, so it feels good to have some space, that is until I think of something I wanted that I didn't copy lol..

Encrypting or Decripting!

Hello everyone, it's very much time that I want to know the speech about decrypting my Nexus 5X. Now I'm stay with PureNexus and ElementalX, but if I go on Security > Cryptography, my phone is encrypted even if when I flash TWRP 3.0.0 , appeared decrypted.
Now I don't know if my device is decrypted or not. There is a detailed guide that I can follow so that I can permanently unlock my device?
Thanks to all
If you see in settings - security that your device is encrypted, it is... If you want to decrypt it you have to format /data and your internal storage.
1. Backup all your data
2. Dowload FED Patcher here and copy the zip to your device
3. Reboot into recovery
4. Wipe system
5. Reflash your rom, gapps and the fed patcher.zip
6. Do a factory reset and (!) format /data.
Reboot your phone, et voila, you are unencrypted.
Be sure to reflash fed patcher every time you update your rom, otherwise it will be encrypted on first boot without fed patcher.
Donald Nice said:
If you see in settings - security that your device is encrypted, it is... If you want to decrypt it you have to format /data and your internal storage.
1. Backup all your data
2. Dowload FED Patcher here and copy the zip to your device
3. Reboot into recovery
4. Wipe system
5. Reflash your rom, gapps and the fed patcher.zip
6. Do a factory reset and (!) format /data.
Reboot your phone, et voila, you are unencrypted.
Be sure to reflash fed patcher every time you update your rom, otherwise it will be encrypted on first boot without fed patcher.
Click to expand...
Click to collapse
When you flash ROM , gapps and patcher , and then do a system reset and format / data , the system does not start or not? But then formatting / data is getting through TWRP ? Thank you

Upgrading from 3.2.8 to 4.0.1 while keeping data, root and encryption.

Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Vitriol_Drinker said:
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Click to expand...
Click to collapse
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
let92 said:
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
Click to expand...
Click to collapse
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
All right, I'll try this weekend and will post here the result
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery and update through the official OTA Then flash the recovery and root again :good:
Click to expand...
Click to collapse
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
hiredantispammer said:
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
Click to expand...
Click to collapse
It seems more simple the @Viper The Ripper's method: in that way I only need to flash the stock recovery, boot the phone (I think the phone will boot on OOS 3.2.7, my actual version), then download OTA (using a VPN to Germany because the update hasn't begun in Italy ), factory reset (will the phone keep Nougat or come back to manufacturer Marshmallow version?), flash recovery by @eng.stk and root phone.
Correct?
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
Click to expand...
Click to collapse
Will this work for me ? Applying the OTA won't relock bootloader will it ?
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
sahed01 said:
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
Click to expand...
Click to collapse
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
let92 said:
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
Click to expand...
Click to collapse
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Only suggestion that i will give is what worked for me. So here is what i did and successfully upgraded from 3.2.8 to 4.0.1 OOS without losing data and keeping encryption on ext4 /data.
1. Keep full OTA zip, and SuperSU latest in the folder or Stable, whatever you want, and the latest recovery by eng.stk v11.
2. Remove security from your phone (pin/password/fingerprint), and Go to recovery flash v11 recovery by eng and reboot to recovery.
3. Wipe system, cache, and dalvik.
4. Flash full OTA, flash TWRP recovery img again. If on rebooting, you find stock recovery, just flash v11 from fastboot again.
5. Don't reboot into system, reboot into recovery again, flash SuperSU zip and make sure SuperSU flashes properly. You need to read the installation process and determine that it flashed properly.
6. Reboot to system, you will have all of your data safe and the way it was in MM.
7. Be careful, the moment you assign pin/pattern/fingerprint security to your device, TWRP would ask for a pattern in recovery and it won't decrypt your data. (Works fine if you are on f2fs). If you are like me and don't flash zips that oftenly, it's good to go.
I hope this method helps. Be sure to remove security from phone before flashing and rebooting as recovery won't work if you have security applied. It's a cheap workaround but it works nevertheless.
sahed01 said:
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Click to expand...
Click to collapse
Maybe Titanium wants the storage permission even if it doesn't ask for it
Try to give it, delete app cache and restart the phone.
Then try to restore one app.
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Go to Supersu apk and choose the option in settings to unroot completly your phone
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Will this work for me ? Applying the OTA won't relock bootloader will it ?
Click to expand...
Click to collapse
If you apply the official OTA you won't lose nothig from your current rom
Yes it'll work and nope, applying the OTA won't relock your bootloader :good:
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Click to expand...
Click to collapse
People that want F2FS will lose their data converting their filesystems unless they back it up; no method listed in this thread gets around this. All the options listed keeps the users on ext4 because the official OTA does not convert your /data partition to F2FS as shown in the updater script code below from official 4.0.1 full firmware and update file.
Code:
getprop("ro.display.series") == "OnePlus 3" || abort("E3004: This package is for \"OnePlus 3\" devices; this is a \"" + getprop("ro.display.series") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 10);
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
set_progress(1.000000);
You can see that all it does it overwrite the system partition with the new changes, writes the radio file, and flashes the extra firmware to bring you up to speed with nougat. If you want to do this right and be on F2FS you have to do it manually.
Viper The Ripper said:
Go to Supersu apk and choose the option in settings to unroot completly your phone
Click to expand...
Click to collapse
Thank you! I'll try your method so!
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
I've managed to do all this and end up wit 4.0.1 with F2FS and no encryption. If I encrypt the phone, it changes the format of the data partition and TWRP won't decrypt it. If I understand this thread, this is to be expected. There is no way to end up with encrypted F2FS that TWRP can decrypt?
Revolised123 said:
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
Click to expand...
Click to collapse
I didn't. Just boot back to recovery after flashing everything. With this TWRP data can be decrypted.

Twrp backup restore problem

When I try to restore stock backup it bootlop and didn't complete boot until I do hard reset
What should I do and which partitions should I restore
I am on 64bit twrp
ahmedAZ said:
When I try to restore stock backup it bootlop and didn't complete boot until I do hard reset
What should I do and which partitions should I restore
I am on 64bit twrp
Click to expand...
Click to collapse
System - rom
Data - app data & settings
Boot - kernel
It's best practice to restore a backup with the recovery version to which the backup was made
You may want to format data first (will delete everything on internal storage)
Wipe
Format data (option on right)
Restart to recovery then restore backup
If you don't restore data make sure you wipe it in advanced wipe
You must restore at least system & boot
Don't restore anything other than system data & boot unless you are doing it to solve a problem specific to other partitions
ahmedAZ said:
When I try to restore stock backup it bootlop and didn't complete boot until I do hard reset
What should I do and which partitions should I restore
I am on 64bit twrp
Click to expand...
Click to collapse
Flash no-verity-opt-encrypt-6.0 zip file (link here https://build.nethunter.com/android-tools/no-verity-opt-encrypt/) immediately (before rebooting into the system) after restoring your TWRP stock backup .

Twrp showing weird name of internal storage folder

hi,
I bought a new redmi note 8 phone, unlocked the bootloader, installed TWRP .
Everything worked fine, until now. Now I want to backup my current modified stock ROM, but TWRP failes.
I got the problem very fast: TWRP can read all files and folders on the microSD car, but not in the internal storage folder.
Everything can be read by TWRP, except the sdcard folder.
Here he only shows strange names
something like:
Quote:
2h8P9lGY8I1A884LMsBjaA
2u+nb0LdBNopRSa5LehsvB
75aTrCvYkWG+R+lrcRz6WA
DcwYkwSKokq8Rm5lYc4YYC
Please help me
Reboot to recovery again and decrypt phone
eric00x said:
Reboot to recovery again and decrypt phone
Click to expand...
Click to collapse
How to decrypt permanent without losing data?
Ahmad5544 said:
How to decrypt permanent without losing data?
Click to expand...
Click to collapse
to decrypt phone :
Make sure you have a backup of your data copied in PC.
- In TWRP go to Wipe and select Format Data(don't go to advanced). Type yes and format data. [This process will format all your internal so make sure your data is backed up].
- Go back to TWRP home and Reboot > Recovery (Don't reboot system).
- Flash this zip.
- Reboot > System.
unfortunately there's no way to decrypt without losing data. Also if you're on a decrypted device then you have to format data everytime you flash any rom or update your current miui rom..I suggest using orangefox recovery to prevent this in future. Follow this guide for orangefox recovery.

Categories

Resources