[Solved] Official Oxygen OS 5.0 boot loop problem for rooted users

[MadCow809]

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.

 

[exis_tenz]

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.

 

[Malcol13]

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.

 

[DionysosD]

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.

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?

 

[Malcol13]

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?

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.

 

[fards]

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.

 

[Serris]

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.

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

 

[Javi22]

so...the no verity is only for decrypted users right?

 

[MadCow809]

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.

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.

 

[igoorsoouza]

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.

 

[MadCow809]

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.

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?

 

[sontjer]

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.

 

[null0seven]

I've triyed this. All good till i flash 5.0 & Magisk & no verity....

 

[khalisz]

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.

 

[raboliot]

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,

 

[Gambo_7]

1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?

 

[BenSow]

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?

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.

 

[MadCow809]

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.

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.

 

[fards]

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.

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.

 

[PandaKiller]

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,

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.