Related
Hello Community,
I am using a custom recovery (TWRP) and my phone is rooted. Can I update this build update in an official way (like in the picture) or do I need to flash a complete ROM? And if I need to flash a complete ROM, has someone the ROM from the new build update? Wasn't able to find it until now.
Sincerely PIPT
You need to do some reading before trying anything more, because you're likely to brick your phone and then you'll really be in trouble.
Yes, you can download and apply updates without having your data wiped and starting from scratch, but there's a very specific process to do this. Failing to follow the proper steps will result in a bricked device. Save yourself some trouble, and learn more about what you're doing before you make a mistake that you can't fix.
I had the same situation as you. I first tried update with OTA, it downloaded and rebooted and failed.
When it booted again, and ran the OTA updater it downloaded the full ROM package, rebooted and installed fine in twrp.
You should flash full rom over your system like dirty flash, just wipe dalvik and cache after flashing completed, then reboot.
This is safe way if you have root and twrp
Keep in your mind you will lose root and twrp after upgraded, flash them again ?
chazarss said:
You should flash full rom over your system like dirty flash, just wipe dalvik and cache after flashing completed, then reboot.
This is safe way if you have root and twrp
Keep in your mind you will lose root and twrp after upgraded, flash them again
Click to expand...
Click to collapse
You also have to flash supersu after dirty flashing the rom. Also I personally wipe Dalvik and cache before flashing the rom. I've never had any issues with the procedure I follow.
---------- Post added at 17:19 ---------- Previous post was at 17:17 ----------
olskar said:
I had the same situation as you. I first tried update with OTA, it downloaded and rebooted and failed.
When it booted again, and ran the OTA updater it downloaded the full ROM package, rebooted and installed fine in twrp.
Click to expand...
Click to collapse
If you have a custom recovery or you're rooted never install an OTA. you need to have official recovery to install an OTA. Dirty flashing the full rom is the best way to update.
PIPT said:
I am using a custom recovery (TWRP) and my phone is rooted. Can I update this build update in an official way (like in the picture) or do I need to flash a complete ROM? And if I need to flash a complete ROM, has someone the ROM from the new build update?
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
In addition to the needed files, the thread has detailed instructions on how to update (stock phone vs. rooted with TWRP) in Post #3 of the thread.
Based on this, you must flash the full ROM zip (as opposed to the partial OTA "patch"), if you are rooted. But you should still be able keep your data. But I would still back up what is important to you, before updating. Just common sense to have your important data backed up, especially before large OS updates.
I'm actually about to do this myself today (rooted OOS 4.0.3 to 4.1.1), so I'll let you know how that goes.
bonham1988 said:
If you have a custom recovery or you're rooted never install an OTA. you need to have official recovery to install an OTA. Dirty flashing the full rom is the best way to update.
Click to expand...
Click to collapse
You can flash full OTA packages through TWRP. You can't flash the smaller patches, but if it's the full firmware, then TWRP 3.0.4.1 will work just fine. Just be sure to flash SuperSU or Magisk before booting to retain root.
redpoint73 said:
See here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
In addition to the needed files, the thread has detailed instructions on how to update (stock phone vs. rooted with TWRP) in Post #3 of the thread.
Based on this, you must flash the full ROM zip (as opposed to the partial OTA "patch"), if you are rooted. But you should still be able keep your data. But I would still back up what is important to you, before updating. Just common sense to have your important data backed up, especially before large OS updates.
I'm actually about to do this myself today (rooted OOS 4.0.3 to 4.1.1), so I'll let you know how that goes.
Click to expand...
Click to collapse
Can I install stock recovery too to make OTA updates and then after the update install TWRP and flash root again? I only ask because I want to do the smaller updates (bug fixes and improvements) too and won't wait for OS and Firmware updates to update my build, because not every little update is listed to get installed manually.
But all in all thx for so many answers
I updated officially with stock recovery and full it's zip, DM Verity has been triggered. It's annoying, anyone else?
edit: fixed it, still annoying that a stock rom tripped it tho.
Hello,
I was wondering, I'd like to root my OP3T , following the guide w/e here or on OnePlus forum. But will be my flashed update as stable as if I keep it on stock recovery ? ( Since people w/e they have OTA on stock or flashing new update on custom recovery )
Besides, I'm already on Nougat 7.1.1 if I root, I won't lose it right ?
And I looked for the right TWRP and the right SuperSu but on their guide are for MM 3.5.1 and not on N 7.1 so where can I find the right version ? on their Website ?
So thank you very much for your help !
If you root your phone, the System Update app will detect it and download the full ROM for each update rather than the partial update. This occurs regardless of the status of your recovery. Since root modifies partitions that the user generally does not have access to, the updater will always overwrite all non-/data partitions during the update. Plus, when you flash an update, it removes root anyways.
My advice is keep TWRP as a custom recovery. When an update is released, you can still go into the Update menu in Settings and download the full ROM (it will do so automatically if it detects root). Then just flash the full ROM in TWRP, flash whatever you used to root, wipe cache, and you're done. If something goes wrong, you can always use TWRP to restore a prior backup. The same can't be done for the stock recovery.
Ok thank you very much for those informations !
Still, do you know which version I should download ? Since I'm on 7.1.1 , thread only shows for 7.0
I searched and I found : SuperSU 2.79 and for TWRP it's the 3.0.4-1 ? Are they right ?
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.
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
MagikGab said:
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
Click to expand...
Click to collapse
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Robbo.5000 said:
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Click to expand...
Click to collapse
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
i have the same question too..
MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
P12AV33N said:
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
Click to expand...
Click to collapse
I would just add to this that, although this is all that is required, I would still backup things, just in case.
It's always good practice when flashing things to backup what you can, even when it's not needed should things go smoothly. It only takes an absent minded moment of stupidity in TWRP to do some serious damage. As many people, myself included, can vouch for.
Thank you everyone!
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
macanovic88 said:
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
Click to expand...
Click to collapse
Flashing a minor update is fine to do as a dirty flash in TWRP.
Doing a major update is 50/50 (going from 10.3.x to 10.4.x as it's s change from Android 9 to 10, or going from 10.x.x to 11.x.x). You may be fine, you may have issues. It might be a better option to try using the 'save data' option in the Mi Flash Tool, which is the same as a dirty flash, but will still update vendor and firmware files, should they have changed between the versions.
You might be guided by what the OTA would do. Occasionally when an OTA provides a major version change, it will perform a clean flash and give you big warnings that this will happen first. If an OTA tells you this will happen, then I would definitely use the Mi Flash Tool and use the 'clean all' option.
As for the compatibility zip, it depends on the TWRP you are using. Just try as is first and if your get an error about the wrong device, then remove it and try again.
Thanks a lot, your answers are very helpful in this thread! ?
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
cgdams said:
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
Click to expand...
Click to collapse
You need to confirm if orangefox is actually ready for OTA by checking in its settings.
Sent from my Redmi K20 Pro using Tapatalk