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.
Please help me. I can't seem to understand what exactly I need to do in order to install a custom ROM on my K20 Pro (Global 10.3.5.0.) I have tried following this (https://forum.xda-developers.com/k20...0-pro-t3953844) post thoroughly and others as well, but can't seem to exactly understand what I am required to do. Most custom ROM's state [Raphael], but as I purchased this device in India, it would most probably be [Raphaelin], after unlocking the Bootloader and installing TWRP, am I supposed to flash a Custom ROM (for ex. Lineage OS) directly or would I have to install a ROM which would make my device [Raphael]? Vendor and Firmware have gone over my head, I do not understand what I need to di. If someone could help me out, It would be mean a lot. Thank you.
Platinum_Pyth0n said:
Please help me. I can't seem to understand what exactly I need to do in order to install a custom ROM on my K20 Pro (Global 10.3.5.0.) I have tried following this (https://forum.xda-developers.com/k20...0-pro-t3953844) post thoroughly and others as well, but can't seem to exactly understand what I am required to do. Most custom ROM's state [Raphael], but as I purchased this device in India, it would most probably be [Raphaelin], after unlocking the Bootloader and installing TWRP, am I supposed to flash a Custom ROM (for ex. Lineage OS) directly or would I have to install a ROM which would make my device [Raphael]? Vendor and Firmware have gone over my head, I do not understand what I need to di. If someone could help me out, It would be mean a lot. Thank you.
Click to expand...
Click to collapse
If you're running stock MIUI and haven't moved to any custom MIUI's till date then you can straight away flash LOS. Moreover, most of the custom roms work on multiple vendors irrespective of whether it is a China Vendor or India or Global. It doesn't matter till the time the developer specifically asks you to be on a particular vendor.
Vendor isn't a dreaded thing. It's just the drivers needed to run the various components in the device (BT, WiFi etc). Till the time you don't wipe the vendor partion in twrp, you would always be good to go. You could carry on flashing custom roms w/o careing about the vendor.
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
If you're running stock MIUI and haven't moved to any custom MIUI's till date then you can straight away flash LOS. Moreover, most of the custom roms work on multiple vendors irrespective of whether it is a China Vendor or India or Global. It doesn't matter till the time the developer specifically asks you to be on a particular vendor.
Vendor isn't a dreaded thing. It's just the drivers needed to run the various components in the device (BT, WiFi etc). Till the time you don't wipe the vendor partion in twrp, you would always be good to go. You could carry on flashing custom roms w/o careing about the vendor.
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Platinum_Pyth0n said:
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Click to expand...
Click to collapse
Go back to the Lineage instructions and read immediately below that. It starts P.S.
It explains exactly proper vendor and firmware means.
No you won't need to install anything for this step
Platinum_Pyth0n said:
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Click to expand...
Click to collapse
Nope ! You don't need to flash vendor + firmware as you already running an untouched stock MIUI build. That is for people who are coming from either modified MIUI builds (EU, Miroom etc) or custom roms with a different vendor (India device running on China Vendor)
Custom roms don't carry the Vendor Firmware files and you can only modify the existing Vendor when you move to other region stock or custom MIUI roms.
Back up your data on Internal storage to a safe place either on a PC or OTG. Skip this step if you have nothing important.
Boot In TWRP
Wipe System, Data , Cache , Dalvik
(Don't reboot at this point, Not Even a Recovery reboot)
Flash LOS
Flash GApps
Go to Advanced Wipe and Format Data by typing Yes
Reboot
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
Nope ! You don't need to flash vendor + firmware as you already running an untouched stock MIUI build. That is for people who are coming from either modified MIUI builds (EU, Miroom etc) or custom roms with a different vendor (India device running on China Vendor)
Custom roms don't carry the Vendor Firmware files and you can only modify the existing Vendor when you move to other region stock or custom MIUI roms.
Back up your data on Internal storage to a safe place either on a PC or OTG. Skip this step if you have nothing important.
Boot In TWRP
Wipe System, Data , Cache , Dalvik
(Don't reboot at this point, Not Even a Recovery reboot)
Flash LOS
Flash GApps
Go to Advanced Wipe and Format Data by typing Yes
Reboot
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I'm trying to install a custom rom in K20 pro raphaelin. But it is getting stucked at recovery. Then I have to install stock ROM using MIFlash. Any help on this issue?
Custom ROM is successfully flashed in TWRP.
MyNameIsAbey said:
I'm trying to install a custom rom in K20 pro raphaelin. But it is getting stucked at recovery. Then I have to install stock ROM using MIFlash. Any help on this issue?
Custom ROM is successfully flashed in TWRP.
Click to expand...
Click to collapse
Did you do FORMAT Data (not just Wipe) when you installed your custom ROM, and before rebooting?
So finally there's MIUI 11 officially announced in China. XDA recently provided the links to download recovery ROM based on MIUI 11 for certain devices here- https://www.xda-developers.com/download-miui-11-beta-now-for-13-xiaomi-devices-changelog/amp/
These ZIPs are chinese beta builds and my question as a xiaomi.eu 's ROM user is-
HOW CAN I FLASH A CHINESE BETA ROM USING TWRP WHILE CURRENTLY I'M USING XIAOMI.EU ROM?
Thanks in advance ;p
u don't. I tried them. they have anti-rollback feature. u will be stuck in them. u won't be able to flash twrp. fastboot will reject everything saying anti rollback hszghsjcklsj........ like something. I tried. my phone got bricked. but somehow fastboot was on and I unlocked bootloader then in edl mode flashed stock ROM. I must say that I was not able to access even recovery.
in short, the way to go back to using custom ROMs/recoveries are destructive and could brick ur device and u may not be able to recover it anytime soon.
So, I risked my phone and tried (that was the only option I had). Here's how to flash Chinese beta (or official MIUI) when your Xiaomi device is running unofficial MIUI like xiaomi.eu's MIUI or even a custom ROM-
Again HOW TO FLASH OFFICIAL MIUI CHINESE/GLOBAL ON A XIAOMI DEVICE THAT IS CURRENTLY ON A CUSTOM ROM
DISCLAIMER: THE BELOW MENTIONED METHOD IS WHAT WORKED IN MY CASE, I thought to help if someone needs help in this case because I didn't get any
Step 1. Make a backup of your data and wipe every partition (except Internal storage, USB OTG & SD card)
Step 2. Since MIUI has anti-rollback, you've gotta flash the recovery ROM with a lazyflasher like tool. (Lazyflasher didn't work at all in my case. So use Dm-verity disabler, Force encryption by @Zackptg5).
Note: You don't need this tool while flashing xiaomi.eu ROM or custom ROM. YOU DON'T!
Step 3. As mentioned above flash both zips and reboot to system.
Hey guys I was wondering something I haven't installed the latest update yet and my phone is rooted and has TWRP on it soo not sure if i can just update with all that or like i should restore the phone to its original state then update
Last version of TWRP I tried (3.4.0-0) did not work properly with Android 10, don't know about the new 3.4.0-1 because I switched to OrangeFox which can decrypt Android 10 without issues.
As for the update process, you need to get the Recovery ROM update package, you can download it from the official xiaomi site, put it, Magisk and your kernel if you use a custom one either on the phone's internal storage or even better your SD card and flash from recovery in this order:
1. ROM
2. Kernel
3. Magisk
4. Wipe Dalvik\cache
5. Reboot to system
I did it exactly like this a few times now, granted it was with xiaomi.eu instead of stock but the process should be the same.
This should just update the phone without wiping anything and with maintaining root, just make sure to do it from a recovery that can decrypt the phone.
Maranex said:
Last version of TWRP I tried (3.4.0-0) did not work properly with Android 10, don't know about the new 3.4.0-1 because I switched to OrangeFox which can decrypt Android 10 without issues.
As for the update process, you need to get the Recovery ROM update package, you can download it from the official xiaomi site, put it, Magisk and your kernel if you use a custom one either on the phone's internal storage or even better your SD card and flash from recovery in this order:
1. ROM
2. Kernel
3. Magisk
4. Wipe Dalvik\cache
5. Reboot to system
I did it exactly like this a few times now, granted it was with xiaomi.eu instead of stock but the process should be the same.
This should just update the phone without wiping anything and with maintaining root, just make sure to do it from a recovery that can decrypt the phone.
Click to expand...
Click to collapse
Well I have a few questions
By recovery ROM you mean from here https://c.mi.com//miuidownload/detail?device=1900376 the full ROM? like I just flash the ROM file using TWRP well OrangeFox version right and it will keep all my apps and data
Yes, you flash the rom from mi.com.
Don't "just" flash it or you'll loose root and OrangeFox, flash in this order:
1. ROM
2. Kernel
3. OrangeFox (I added this step because you are on official MIUI and the update will replace your custom recovery unless you re-flash it after the rom.)
4. Magisk
5. Wipe Dalvik\cache
6. Reboot to system
Before flashing make sure you are flashing the right rom for your variant and region.
Other than that, you should be good, I updated like this three times and had no data loss.