I'd like to encrypt my phone just to try it. But, being cautious I'd like to make sure I can restore the thing if I want to. By, "restore," I don't care about decrypting it, but I sure want TWRP to still be able to restore a previously saved backup.
If, after encryption, TWRP will not be able to restore then I think I will pass on the encryption as it will be too much work to reconfigure a new CM install.
So, the question is, if I encrypt, will TWRP (current version) still be able to restore a saved-backup or would I have to revert to ADB and a new install of CM12.1?
Thanks
Related
I'm using TWRP 3.1.0-1, running Resurrection Remix-N v5.8.0-OnePlus 3T. I want to go back to OOS, I have a TWRP backup of OOS before I flashed RR and I want to restore from that.
So in TWRP -
- Took another backup of RR
- Wiped Dalvik, System, Data and Cache
- Restored OOS
OOS starts and prompts to use my swipe pattern, I swipe my pattern and it's "incorrect", (I didn't forget my pattern, same one I have used for a long time). Ok so back to RR, so I did the same wipes and restored latest RR, now it bootloops. I restored OOS again and wiped. I'm back to OOS, but of course it's "new".
Is there a way to restore OOS successfully or any of RR from my TWRP backups?
Don't know if it makes a difference, but had some issues originally flashing RR, had a bunch of problems, DM-verity and softbricked, I restored to stock using this:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-return-youre-op3t-to-stock-lock-t3569383
After restoring to stock, I successfully removed the default encryption following another guide. I guess I don't know if RR by default encrypts or not, if that matters.
Have you changed your twrp after doing the initial backup
Because twrp before 3.0.4.1 does backups differently and will not restore if restore them by using twrp 3.0.4.1 or newer
kunal1540 said:
Have you changed your twrp after doing the initial backup
Because twrp before 3.0.4.1 does backups differently and will not restore if restore them by using twrp 3.0.4.1 or newer
Click to expand...
Click to collapse
To the best of my knowledge I am using the same version both to backup and restore. I definitely used the same version to backup/restore the latest RR (which bootloops).
RocKKer said:
To the best of my knowledge I am using the same version both to backup and restore. I definitely used the same version to backup/restore the latest RR (which bootloops).
Click to expand...
Click to collapse
Normally, I'd say the backup is just damaged or has some error, preventing proper restore of it. But it's strange that you have two RR backups which won't restore.
If the intent is to get RR working, with your previous user data; maybe try to flash RR, then just use TWRP to restore the data partition?
If you plug your phone in your computer and you computer recognizes your phone, then you can use ADB to wipe everything again. I had the same problem but my phone only charge if I plugged it into my PC so I wasn't able to revive it...
I've got the same problem here. Running TWRP 3.1.0-1, and sultan CM13 20170402. Backed up everything. Tried:
1. restore everything
2. restore only system
3. restore only system and data
None worked. Bootloop immediately after OnePlus splash screen. I also tried the above in combination with wiping everything, wiping system only and wiping data only. File systems are ext4/f2fs/f2fs on system/data/cache.
This is making me go nuts. The only thing I can think of is to try restoring under TWRP 3.0.4.
@RocKKer
try this
go to TWRP Home >> Settings >> tick use rm -rf instead of formatting
and then restore your backup
maybe this helps
cheers
I need root to restore from titanium
Is there a way to upgrade without loosing data when on 7.1 with unlocked bootloader and twrp?
I think you can just use the fastboot process to upgrade. I don't know if you will need to do a wipe before it will boot or not but once it boots, you should be able to flash TWRP again and install Magisk from there. I don't know if the modules will work until the kernel is modified. Keep an eye on this thread. https://forum.xda-developers.com/moto-g5s-plus/development/kernel-resurrected-kernel-t3716267/page16. Once the Kernel is updated, it should pass safety net and the Magisk modules should work. I haven't updated yet because I am waiting on the updated Kernel.
Edit: Be sure to do a full backup including the EFS partition in TWRP before doing anything... I have seen so many people lose their IMEI, including mine. Without the EFS backup, it will be very difficult to restore your IMEI.
Is it just me with this issue? Any known fixes or something? I'm using lineage os version 15.1 with latest update that released today.
i got it too. i always encrypt on lineage OS and omni, today i don't remember what last build i was on but i cleaned my phone and installed latest LOS, after that i can't encrypt my device anymore. even i tried older builds of LOS, NLOS and also OMNI. i can't encrypt my device anymore.
I formatted Data many times and formatted everything but still can't encrypt. anyone can solve this issue?
---------- Post added at 03:45 AM ---------- Previous post was at 03:10 AM ----------
just figured out the problem, problem was in TWRP 3.2.3-1. please install 3.2.3-0, and problem solved
I also have this issue on 15.1-20190127-NIGHTLY-oneplus3, has anybody got a fix yet?
Here's what I would do in your situation:
0. Take a backup of your current rom and internal storage and save it on your PC.
1. Try a different rom to see if it can encrypt your phone, eg Los 16 beta from https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
See: https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post78144505
If that works, you're done and can restore your backup. If not ...
2. Do a clean install of OOS 5.0.8 full zip from https://www.oneplus.com/support/softwareupgrade
Don't flash Magisk or custom kernel. Let the phone reboot normally. Check that the phone is encrypted.
OOS forces the storage to be encrypted. It will also replace TWRP, but you can flash it (use the version mentioned in the next step) after the phone has booted.
If this doesn't give you an encrypted phone then:
3. !!!This step will complete wipe your data partition (including user storage)!!!
Use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112 and tap the Format Data button under the Wipe menu. Do not use the Advanced Wipe option.
This should give you a properly formatted data partition with the correct encryption space.
I would flash stock OOS 5.0.8 at this point and boot it to get a properly encrypted phone (I did this when I was testing this version of TWRP and it works).
You can then restore your data backed up in step 0. Also restore TWRP (the version mentioned above) and restore your backed up rom.
For discussion and info on this version of TWRP see https://forum.xda-developers.com/on...ial-twrp-touch-recovery-t3742894/post78661632
You could just do steps 0 and 3, but that's a fair bit of time and effort, which is why I suggested steps 1 and 2.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Here's what I would do in your situation:
0. Take a backup of your current rom and internal storage and save it on your PC.
1. Try a different rom to see if it can encrypt your phone, eg Los 16 beta from https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
See: https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post78144505
If that works, you're done and can restore your backup. If not ...
2. Do a clean install of OOS 5.0.8 full zip from https://www.oneplus.com/support/softwareupgrade
Don't flash Magisk or custom kernel. Let the phone reboot normally. Check that the phone is encrypted.
OOS forces the storage to be encrypted. It will also replace TWRP, but you can flash it (use the version mentioned in the next step) after the phone has booted.
If this doesn't give you an encrypted phone then:
3. !!!This step will complete wipe your data partition (including user storage)!!!
Use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112 and tap the Format Data button under the Wipe menu. Do not use the Advanced Wipe option.
This should give you a properly formatted data partition with the correct encryption space.
I would flash stock OOS 5.0.8 at this point and boot it to get a properly encrypted phone (I did this when I was testing this version of TWRP and it works).
You can then restore your data backed up in step 0. Also restore TWRP (the version mentioned above) and restore your backed up rom.
For discussion and info on this version of TWRP see https://forum.xda-developers.com/on...ial-twrp-touch-recovery-t3742894/post78661632
You could just do steps 0 and 3, but that's a fair bit of time and effort, which is why I suggested steps 1 and 2.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Appreciate your advice appreciate, not sure what the OP would think but I wish I didn't have to flash different image and/or wipe, will see how I get on though.
da_n said:
Appreciate your advice appreciate, not sure what the OP would think but I wish I didn't have to flash different image and/or wipe, will see how I get on though.
Click to expand...
Click to collapse
At this stage I trust OOS more than the custom ROMs to correctly encrypt my phone. Once it's encrypted I'm happy to use custom ROMs.
Also, this is my personal view, so others may have different views.
You could, if you wanted, just install a custom rom after formatting the data partition and see if that works.
Sent from my OnePlus3T using XDA Labs
Hi there,
I tried to install a ROM on my Mi9T pro. I use Orange Fox and it asked me when I entered the recovery for the password, that decrypted my Data partition. All well so far.I installed the ROM Havoc and Magisk. After reboot into System, there was a bootloop. I entered the recovery again and the Data(internal storage is encrypted. Which is not too bad, because I know the password, but I do not get asked for the password/pattern. It says:
E: Error making /sdcard/fox, unable to wipe Data, unable to format to remoce encryption.
So I cannot install a new rom as the partion is encrypted and I cannot remove the partition.
“E:Unable to decrypt FBE device”
Does anyone have a recommendation on what to do?
Kind regards
berndbrecht said:
Hi there,
I tried to install a ROM on my Mi9T pro. I use Orange Fox and it asked me when I entered the recovery for the password, that decrypted my Data partition. All well so far.I installed the ROM Havoc and Magisk. After reboot into System, there was a bootloop. I entered the recovery again and the Data(internal storage is encrypted. Which is not too bad, because I know the password, but I do not get asked for the password/pattern. It says:
E: Error making /sdcard/fox, unable to wipe Data, unable to format to remoce encryption.
So I cannot install a new rom as the partion is encrypted and I cannot remove the partition.
“E:Unable to decrypt FBE device”
Does anyone have a recommendation on what to do?
Kind regards
Click to expand...
Click to collapse
When installing over MIUI you need to format data. You should still be able to format data, which should allow you to boot into the ROM after.
If Orange Fox won't let you format data at this point, then the issue is with Orange Fox. In TWRP when this happens, even though the data partition is encrypted and TWRP doesn't ask for the password, TWRP can still format the data partition.
If you can format data in OF, then good. If not try installing TWRP then formatting data. If that fails your best option is to restore to MIUI with a stock fastboot ROM, then start again.
thank you for your comment. as a follow up. do you recommend a certain twrp release? i just don't want to **** up the phone. when ich connect the phone to my laptop, I can see the internal data, but neither can i copy, nor make the names of the files any sense (encrypted i guess). is there now way to decrypt the files from the situation as is? i do not mind, as i back upped all the important stuff, but if possible i would do without format.
btw. i came from lineage os. what i did: i wiped data, system, cache and data, then installed the rom ( included gapps) and magisk. then restarted.
berndbrecht said:
thank you for your comment. as a follow up. do you recommend a certain twrp release? i just don't want to **** up the phone. when ich connect the phone to my laptop, I can see the internal data, but neither can i copy, nor make the names of the files any sense (encrypted i guess). is there now way to decrypt the files from the situation as is? i do not mind, as i back upped all the important stuff, but if possible i would do without format.
btw. i came from lineage os. what i did: i wiped data, system, cache and data, then installed the rom ( included gapps) and magisk. then restarted.
Click to expand...
Click to collapse
Use the latest TWRP from here https://forum.xda-developers.com/k2...cial-twrp-xiaomi-redmi-t3944363/post79823568. Go with the latest unofficial as it is the same as the official version, but with some minor bug fixes added.
Orange Fox is only really worth using when sticking with MIUI. Most of it's extra functions are MIUI specific.
When you get into this situation, unfortunately, there is nothing that can be done to recover or decrypt the data partition, as far as I know.
Normally going from one AOSP ROM to another you should be OK and won't need to format data. But occasionally this problem will happen, I've had it happen when going from LOS to AOSiP. Formatting data in TWRP, when this happens, will then allow you to boot into your new ROM. I haven't yet found out why this sometimes happens.
You will just need to backup your data whenever you flash a ROM, just in case this happens again.
Robbo.5000 said:
Use the latest TWRP from here https://forum.xda-developers.com/k2...cial-twrp-xiaomi-redmi-t3944363/post79823568. Go with the latest unofficial as it is the same as the official version, but with some minor bug fixes added.
Orange Fox is only really worth using when sticking with MIUI. Most of it's extra functions are MIUI specific.
When you get into this situation, unfortunately, there is nothing that can be done to recover or decrypt the data partition, as far as I know.
Normally going from one AOSP ROM to another you should be OK and won't need to format data. But occasionally this problem will happen, I've had it happen when going from LOS to AOSiP. Formatting data in TWRP, when this happens, will then allow you to boot into your new ROM. I haven't yet found out why this sometimes happens.
You will just need to backup your data whenever you flash a ROM, just in case this happens again.
Click to expand...
Click to collapse
Thanks man, many thanks. did flash the twrp and it worked out. having some minor problems with the rom, but in general it worked out fine
much appreciated.
On my phones I have always used the backup's function offered by TWRP's recovery .
I've always been able to restore the nandroid's backups without any problems.
However, whenever I try to restore a backup on my Note 9, the phone always goes into bootloop.
I've never had this happen with my other phones (S3 and LG G5).
I wouldn't want to have to do other things to do a successful restore.
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
XTrail02 said:
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
Click to expand...
Click to collapse
Thank you for your reply.
I mean, let me get a better understanding of what you did.
Did you first flash the "Disable_Dm-Verity_ForceEncrypt"'s zip and then restore the nandroid backup?
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
XTrail02 said:
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
Click to expand...
Click to collapse
I already do all this when I install the new rom. So, my phone should be decrypted.
Then after some time I make a nandroid backup. However, when I go to restore the backup the phone goes into bootloop.
So, it means that with the restore the phone comes back encrypted again. That's why it goes into bootloop.
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
XTrail02 said:
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
Click to expand...
Click to collapse
If I understand correctly, before restoring a nandroid backup you flashed 'disable_dm-verity_forceencrypt.zip' and then did the restore.
Right?