I had this issue last week I believe and it happened again last night. The only reason I can even use my device is that I'm using xtended TWRP. I was using Resurrection Remix Nougat with the December security patch and decided to see if MSM Xtended could come close to matching the battery life I get from RR7.1. I got through the setup and quickly decided I preferred Havoc, so I flashed Havoc and set it up. I realized I didn't backup my apps so I tried to restore my RR backup on TWRP. Before it booted it came to the screen telling me encryption was unsuccessful and to factory reset to use my device.
Now, in no ROM have I encrypted my device. I didn't try to encrypt anything, no app data, pictures, no zip archive, no encryption of ANYTHING. I have no clue what did it, but each time I was using RR and did a fresh install of a Pie ROM. The only difference between this time and last time is that last time I attempted to use the official version of TWRP that doesn't have the encryption capabilities as Red Wolf or TWRP Xtended.. when I flashed the official TWRP last time I was locked out as if I did unsuccessfully try to encrypt. Last time, after flashing official TWRP, I was able to recover my files by using fastboot to flash TWRP Xtended.
Like last time, I have full access to my files in recovery, and as long as I use a Pie ROM, I can flash at will with no issues. Restoring a backup or attempting to clean flash anything other than a Pie ROM results in encryption unsuccessful.
Has anyone else encountered this? And outside of fastboot format userdata, is there any way to fix it? Any idea of what could be causing this? I mean, I'm about to fix it the only way I know, but I'm wondering for future reference.....
I tried something just now before wiping everything... I've kept it unencrypted for no real reason, so I decided to try something after backing all my stuff up.. I did a clean flash of the latest OOS, didn't use a patched boot image or the encryption disabler and allowed OOS to encrypt my device.. I booted into OOS and completed the setup; all my files and everything was still there, settings->security said I was encrypted. I rebooted to recovery and I still had TWRP xtended, restored my Resurrection remix backup, and booted right up. I'll just keep it encrypted, since it works and I have no real reason NOT to be encrypted..
One of the problems with switching ROMs on this phone is that some ROMs use Full Disk Encryption (FDE) and some use File Based Encryption (FBE). As these are quite different and incompatible with each other, it's important to switch to ROMs only using the same encryption type.
Skickat från min ONEPLUS A3003 via Tapatalk
pitrus- said:
One of the problems with switching ROMs on this phone is that some ROMs use Full Disk Encryption (FDE) and some use File Based Encryption (FBE). As these are quite different and incompatible with each other, it's important to switch to ROMs only using the same encryption type.
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Although I've resolved it satisfactorily enough for me, I'm still curious as to what exactly changed. I say that because up until, I think the 20181211 build of havoc I could switch between my restores with no issues. Sometime after that build is when I encountered that encryption issue. Mind you, up until I encrypted my device yesterday, I religiously kept my device unencrypted, avoiding any sort of encryption. I just found it odd that because I haven't attempted any sort of encryption that it would tell me that encryption was unsuccessful on restores and clean flashes of Resurrection remix nougat, yet no problems at all with either havoc or xtended Pie... like I said, it's just more of a curiosity now that it seems to be resolved.
Related
Hi guys,
I was going to update by dirty flashing tesla rom on my 3T, after booting to TWRP it wiped itself. I rebooted and a welcome screen appeared. I red some posts of people having this problem. Do You have any fix for this? I was using TWRP 3.0.3.1. I then updated to the latest 3.0.4 but the issue was still there. I red that formatting data in ext4 fixes the issue. So I did it and the issue was fixed.
Is there a way to keep data in f2fs and rebooting to TWRP without losing DATA?
I should have the nougat firmware since i updated to official 4.0.2 OOS and then modded my 3T.
Some time ago, I met a similar problem. I updated twrp but Data partition always lost something after rebooting whether in ext4 or f2fs.
And then I ①flashed stock recovery ②relocked bootloader ③unlocked bootloader again ④flashed twrp.
I believe I tryed several times, and it worked and works well in f2fs now.
95先生 said:
Some time ago, I met a similar problem. I updated twrp but Data partition always lost something after rebooting whether in ext4 or f2fs.
And then I ①flashed stock recovery ②relocked bootloader ③unlocked bootloader again ④flashed twrp.
I believe I tryed several times, and it worked and works well in f2fs now.
Click to expand...
Click to collapse
If i stay in f2fs and boot to recovery it asks me to swipe right to allow modifications. Using ext4 it doesn't ask it to me...It's an annoying bug cause I can't flash anything without losing data every time....
phoenixita said:
If i stay in f2fs and boot to recovery it asks me to swipe right to allow modifications. Using ext4 it doesn't ask it to me...It's an annoying bug cause I can't flash anything without losing data every time....
Click to expand...
Click to collapse
Oh , I remember that TWRP was also reset after I converted Date partition at that time.
May be you can try the ①②③④ if you have enough time.
Everything was working great yesterday after I flashed the new 5.0 OOS through TWRP.
But this morning it was like my device suddenly decided to act funny. First it started FCing different apps all the time.
Then it got into a continuous restart loop.
Finally when it settled, I discovered all these problems:
- Home and recent buttons not working
- Developer options were empty
- Factory reset not working
- When I tried to reboot into recovery, I was asked for a password for decrypting data under a Mount title. I entered my pin and continued with some info for updating partition. I reflashed the stock 5.0 rom and the bluespark v.8.54 recovery, wiped cache, but nothing changed.
Any ideas?
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
thes3usa said:
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
Click to expand...
Click to collapse
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Everything looks fine now? Because when you said the device couldn't finalise the setup process, it may have been a corrupt flashable package. But since it's fixed now, that doesn't seem like the issue.
Sorry I was misinformed about the TWRP version, I thought there was only one version of TWRP by blu_spark that can be used. Turns out, there is another. Sorry about that.
Cheers!
Yee I hope the clean install did the trick.
Although 2 days ago everything was also running great before the catastrophic behavior.
And the worst part is that I have no clue what caused this. I didn't mess with root settings or new apps, had stock kernel installed and no new apps were installed recently.
Sent from my ONEPLUS A3003 using Tapatalk
While trying to go from a custom ROM to the official global stable, I'm having issues. I used Mi Flash to install the rom with no issue, but when I boot into TWRP with fastboot, it tells me the data is encrypted. I have no lock screen on and I can't decrypt it because default_password didn't work. I'm going to try to explain to the best of my ability exactly what I was trying and what I did to get here.
Starting point: Epic Rom
I used mi flash tool to install official Nougat Global Stable ROM.
I accidentally lock my bootloader doing this, but no big deal, I unlock it again with the tool xiaomi provides.
I guess the official ROM has it's own recovery, since it overwrote TWRP.
I reflash TWRP, and use fastboot to boot into it.
I wanted to install magisk, so I boot the phone, download it, and boot back into TWRP from the command line.
Here's where I notice the data is encrypted and I can't access internal storage to install magisk.
I start over and reflash the global rom and twrp, this time not setting a lock screen at all.
Still encrypted.
Wipe userdata and repeat.
Still encrypted.
I'm lost at this point. I can't even flash a custom ROM because I again can't get into my internal storage in TWRP to install it. Does anyone have any ideas? I'm a bit desperate at this point
After a little bit more searching, it seems it automatically encrypts if supersu isn't installed. Is there a way around this for magisk?
I recently had the same issue with the global stable rom, twrp wouldn't show anything in my internal storage. How I fixed it was miflashing the latest global stable developer rom instead an then twrp , an that did it..... I was able to see internal storage. For some reason the global stable doesn't allow you to see the storage. Hope that helps
kjm2323 said:
I recently had the same issue with the global stable rom, twrp wouldn't show anything in my internal storage. How I fixed it was miflashing the latest global stable developer rom instead an then twrp , an that did it..... I was able to see internal storage. For some reason the global stable doesn't allow you to see the storage. Hope that helps
Click to expand...
Click to collapse
Brilliant, this worked! My issue now is that, as far as I can tell, developer ROM isn't on MIUI9? That seems strange, but I guess I may go back to a custom ROM in this case.
master565 said:
Brilliant, this worked! My issue now is that, as far as I can tell, developer ROM isn't on MIUI9? That seems strange, but I guess I may go back to a custom ROM in this case.
Click to expand...
Click to collapse
I know I'm on the latest an it is miui8, which I'm fine with... The device runs great an has everything I need. Just a heads up I didn't shut the updater off an left my phone on wifi. When I woke up in the morning it auto updated to the newest rom an I lost twrp, SU, xposed.... Had to re-do all that. Everything worked but just a pain. You don't get that auto update running a custom rom.
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