Related
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.
It's been a year and a half since last time i had messed around with custom roms.
I am currently on stock 8.0 Oxygen OS. What would be the steps to install OmniROM 8.1?
I'm thinking the following.
1. unlock bootloader
2. Flash TWRP
3. Root
4. Wipe/format
5. flash OMNI rom 8.1?
Do I first need to update to 8.1 somehow?
You may want to update to the latest Open Beta firmware, which you can get the standalone files from here ( https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166)
Flash this before flashing the ROM.
Also you may want to flash the Root method after flashing the ROM. Your best choice is Magisk, since it's getting ready updates and it has many extra features. SuperSU is old and not done by chainfire anymore, so don't flash SSU.
Also remember to wipe these specific partitions:
System
Data
Cache
Dalvik Cache.
I'm not sure by what you mean by "Updating to 8.1" as OOS is still on 8.0, even the Open Beta's. Flash the latest Firmware from Recovery and you should be good go.
Also, don't forget to grab NezorFlame's unofficial GAPPS, since OpenGAPPS still hasn't been updated to 8.1.
(https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/)
Also just keep in mind, unlocking your bootloader will wipe your internal storage. This is a security feature and cannot be bypassed.
IMO, there are better ROMs than Omni. You should try Z-Unleashed or Resurrection Remix 6.0.0. They're the best ROMs with the best customization and usage per user for now.
Good luck, and happy flashing!
You don't need to wipe data if you're going to unlock bootloader, since as mentioned earlier, unlocking BL deletes all of yor data.
Dalvik Cache isn't used anymore (we are on ART now), so no need to wipe it separately, it even reside in /data partition.
Also no need to flash firmware files if you're on OOS 5.
ROM, GApps and Magisk will be enough.
przemcio510 said:
Also no need to flash firmware files if you're on OOS 5.
Click to expand...
Click to collapse
Well, most of the ROMs recommend Open Beta 22 firmware, since this is the FW the developers build the recently updated ROMs on. He may experience issues if he's on OOS 5.0 fw.
Dear all,
I've rooted my phone in July 2018 with the latest stock build from that timeframe. I'm getting notifications of OTA updates for the past 6 months that I've been swiping away and putting off. Obviously I cannot update OTA.
What are my options to update my phone if I want to maintain root? Is there a full build somewhere that I can install via twrp and flash SU or magisk over? Are there fully functional ROMs that I can periodically flash via TWRP to stay up-to-date and rooted? Or am I forced to revert to stock, update via OTA, then re-root?
I'm familiar with rooting but the G6 pathways have confused me compared to my previous OnePlus and Nexus phones. Thanks for your help.
You should only have to re-flash
OEM
Vendor
Boot
Recovery
to be able to apply the OTA.
Afterwards you just need to boot the twrp and install Magisk again, and maybe use the dmverity patch to disable forced encryption. <-- This has to be done BEFORE the first boot of the upated system, otherwise the phone will be encrypted again.
At least this is how it works on the G6 Play.
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
You can do that without loosing your apps/userdata.
Best bet would be to find the latest full image for your make/model and flash everything via fastboot. Just skip the part "fastboot erase userdata" or something like that, and you are good to go. Just remember the dmverity thing, if that is important/applicable for you.
Re-root is necessary either way, but that takes like 5 minutes, that shouldn't hold you up.
tintn00 said:
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
Click to expand...
Click to collapse
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
HueyT said:
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
Click to expand...
Click to collapse
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
tintn00 said:
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
Click to expand...
Click to collapse
If u want to backup data partition on TWRP, u have to be unencrypted for Moto G6 as TWRP can't decrypt data.
Rooting is just Magisk 18.1 and has nothing to do with encryption.
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
HueyT said:
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
Click to expand...
Click to collapse
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
tintn00 said:
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
Click to expand...
Click to collapse
Unlocked is safest guarantee against bricking. Don't worry about "uncertified" in Play store
Hello,
as we know, if you have unlocked bootloader and you flash OOS Pie 9.0.2, your data partition will get corrupted. I'd like to ask if this will happen again if Im already on 9.0.2 and will try to flash 9.0.3
anyone been through this? Will my data partition be corrupted again or it will work as it shoud?
thank you for reply
Krustak said:
Hello,
as we know, if you have unlocked bootloader and you flash OOS Pie 9.0.2, your data partition will get corrupted. I'd like to ask if this will happen again if Im already on 9.0.2 and will try to flash 9.0.3
anyone been through this? Will my data partition be corrupted again or it will work as it shoud?
thank you for reply
Click to expand...
Click to collapse
I'm on an unlocked bootloader with TWRP and I came from HavocOS (decrypted) to theOne3TOS version 9.0.2, which is basically an OOS version with additional options. I wanted to remain decrypted so I just did a clean flash following the instructions of the main post, flashing the "Force Encryption Disabler For OOS Pie v1.zip" after flashing the rom, the I rebooted and everything worked fine. To update I just dirty flashed the 9.0.3 of theOne3TOS without even needing the encryption disabler and again everything worked fine. Hope this helps.
TWRP + LOS 16 + 9.0.2 firmware & modem + unlock bootloader + encryption
No problem at all to update from 9.0.2 to 9.0.3 with this https://forum.xda-developers.com/showpost.php?p=79696659&postcount=611
good luck
First of all, i fu**ed up.
So, I was on MIUI.EU 9.8.22 running Android Q.
I tried to install Syberia Rom.
Full Wipe, flashed image vendor, rom, gapps and then magisk.
Rebooted to system. Didn't work, so I went to recovery mode to fix it. It was everything encrypted so I couldn't find a way to go back to miui.eu or install another rom.
I tried to install a twrp that supports encryption via fastboot.
Now I can't go anywhere but fastboot. Any ideas?
Forgot to say, BL is Unlocked
Thanks in advance
SlugUnchained said:
First of all, i fu**ed up.
So, I was on MIUI.EU 9.8.22 running Android Q.
I tried to install Syberia Rom.
Full Wipe, flashed image vendor, rom, gapps and then magisk.
Rebooted to system. Didn't work, so I went to recovery mode to fix it. It was everything encrypted so I couldn't find a way to go back to miui.eu or install another rom.
I tried to install a twrp that supports encryption via fastboot.
Now I can't go anywhere but fastboot. Any ideas?
Forgot to say, BL is Unlocked
Thanks in advance
Click to expand...
Click to collapse
Use xiamoiflash to go back to stock and you'll be fine.
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
this is the latest one i think
SlugUnchained said:
First of all, i fu**ed up.
So, I was on MIUI.EU 9.8.22 running Android Q.
I tried to install Syberia Rom.
Full Wipe, flashed image vendor, rom, gapps and then magisk.
Rebooted to system. Didn't work, so I went to recovery mode to fix it. It was everything encrypted so I couldn't find a way to go back to miui.eu or install another rom.
I tried to install a twrp that supports encryption via fastboot.
Now I can't go anywhere but fastboot. Any ideas?
Forgot to say, BL is Unlocked
Thanks in advance
Click to expand...
Click to collapse
You use Mi flash 2018.5.28 https://drive.google.com/uc?id=1fGtVqNIPooDlxa-PAXBhJ4W85RPJ-Aaz&export=download
and Flash rom dev Global 9.6.27 https://mega.nz/#!CooF0CQS!qms2GwgiGq0ao9JThMUinTJVxwcJdlwnORl2S64mxrg
maybe this will help you: https://xiaomi.eu/community/threads...ck-to-global-rom-and-relock-bootloader.52257/
So, thanks to all for your answers. I managed to fix the issue using @bijandoroudian suggestion.
I don't know if i should delete this thread, maybe can be helpful for other users having the same issue