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
Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.
Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...
As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs
I have flashed Nitrogen OS, Colt OS and NLOS OS. All pie based ROM on my 3t.
While switching from one ROM to other I always take the nandroid back up and save it to my PC.
My device is decrypted, and I was using NLOS 16.
Last night, I tried to flash to flash baikal OS but unfortunatley I got bootloops so I decided to restore the latest nandroid back up of NLOS 16.
While restoring ,I was aware that NLOS is 5.0.8 fw based ROM as of now, so I first flashed the firmware then I started restoration, after hitting reboot system; phone went to bootloader mode. I again tried but in vein.
So I decided to take the nandroid back up of COLT OS with similar steps but again the phone showed the bootloader screen.
Now, finally I tried Nitrogen OS nandroid back up. It booted successfully.
So I want to know, what is causing the trouble in NLOS and COLT OS nandroid back which force the system to go to bootloader screen. I recall when I was on oreo ROM but encrypted, I could restore the nandroid back up easily by just flashing the recommended firmware first and then restoring.
Is it due to the fact that my device is decrypted and I am taking nandroid back up of sellinux enforcing builds of NLOS and COLT OS .
afaik Nitrogne OS use the sellinux in permissive mode while others are all enforcing.
I'm pretty sure you took Nitrogen backup with latest TWRP and the other two backups with the second-last TWRP which had problems backupping and restoring. Nothing to do with encryption.
mvalda01 said:
I'm pretty sure you took Nitrogen backup with latest TWRP and the other two backups with the second-last TWRP which had problems backupping and restoring. Nothing to do with encryption.
Click to expand...
Click to collapse
No, I used the same TWRP 3.3..0-1 for all ROMs.
I was using NLOS which I did flash through TWRP 3.3.0-1 and took the back up first then I proceeded to flash other ROM but restoration of the same NLOS ROM was unsuccessful.
sandeep_kumar said:
No, I used the same TWRP 3.3..0-1 for all ROMs.
I was using NLOS which I did flash through TWRP 3.3.0-1 and took the back up first then I proceeded to flash other ROM but restoration of the same NLOS ROM was unsuccessful.
Click to expand...
Click to collapse
So mvalda was correct. You are using the version of TWRP that couldn't restore /system from your backup. (The System Image option would have worked). The latest build, 3.3.1-0, fixes that issue.
Another way to get the backup working on the old build was to restore the backup and immediately dirty flash your ROM again.
Update your TWRP to latest and take a backup.
Edit: Flashing Firmware before restoring a backup is pointless. The backup will immediately overwrite it.
TWRP
I can't seem to get TWRP to install on my pixel 5 I boot it then use the installer and it just loops to fastboot mode and I'm in an awwl of why,I've done this many times on my pixel 1 and 2.,also I have bugs with it in the Lineage 19.1 official builds and I can never get TWRP to get pass the splash screen with lineage as lineage has it's own recovery.
idk ive been having real issues with twrp since i put droid 13 on my pixel 5 keep in mind ive thrown almost every custom rom on here once with twrp as my recovery bro idk think it may have to do it droid 13
TWRP isn't offically out for Android 12 or Android 13 for Pixel 5.
However Android 12.1 support is coming soon with A13 WIP,
see here
Aside from custom ROMs, TWRP isn't really necessary on Pixel devices due to the ability to flash partitions directly.
It's also worth noting that the recovery kernel lives in the boot image, which also contains the system kernel, so any time /boot is flashed, TWRP would be wiped out.