Related
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
RotesMeerJogger said:
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
Click to expand...
Click to collapse
I have a detailed thread already running on how to update here
http://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
I shall keep it up to date with further releases
Sent from Funk Tuned 3T
okay, i have searched in the wrong category thanks a lot for the link!
this thread can be closed.
how can i receive the updates when i root my phone?
and is there anyway to change the emoji without root?
a7mad-911 said:
how can i receive the updates when i root my phone?
Click to expand...
Click to collapse
You should still receive OTA notifications with root. And it should detect you have root, and will download the full update zip, and it will install with TWRP.
Otherwise, you can manually download the full zip update from Funk WIzard's thread which he linked in Post #2 above (which also has detailed instructions on how to update when rooted and TWRP installed).
Works like a charm with magisk 13.6
I just did it with my OP3t and was super easy.
1) download update.
2) go to hidden folder .Ota
3) move zip file to another folder
4) put Magisk in the folder, too
5) reboot to recovery, flash ROM, then Magisk
6) wipe dalvik/cache and reboot
Edit: updated following testing of redpoint73's correct advice
LeighR said:
4) put twrp and Magisk in the folder, too
5) reboot to recovery, flash ROM, then twrp, then Magisk
Click to expand...
Click to collapse
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
redpoint73 said:
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
Click to expand...
Click to collapse
This means I will keep all apps/settings/files?
Thank you.
JayDz said:
This means I will keep all apps/settings/files?
Click to expand...
Click to collapse
Yes.
Although I will caveat that with my rule of thumb: "hope for the best, prepare for the worst". In that a "dirty" flash of an update is often possible (saving your a lot of work setting up the device again). But you should still be prepared to wipe and do a "clean" install if you run into any problems. So back up your data, by your method of choice, before you try to update.
In particular, for a major update (such as OOS 4.x to 5.x) a clean install (default wipe in TWRP - data, cache and Dalvik) is typically advised.
Shall?? You used the word 'shall' properly in context? Kudos to the school system (I here assume India's) you attended, and to you for paying attention, using the 'King's English' in it's most proper form.
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
serifle said:
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
Click to expand...
Click to collapse
Try flashing this 6.0.1 stock-based ROM:
Computerfreek274_MM_1.0.6 Marshmallow 6.0.1
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's debloated, tweaked version of 6.0.1 Verizon stock firmware.
Yes, you may lose root temporarily. Just re-flash this version of SuperSu, found in this post. On stock 6.0.1 or stock-based 6.0.1 ROM ONLY that version of SuperSu (BETA-SuperSU-v2.62-3-20151211162651) will work for initial root. After you re-root, THEN you can update to newest version of SuperSu.
Also, not sure why you don't want to update to newer TWRP. You don't have to... but I always do. You just flash newer TWRP within TWRP. You install it like any other file in TWRP. Choose install, then "image", then "recovery".
What version TWRP are you using. Our official TWRP maintainer @bhb27 has released TWO newer versions just in 2017 alone.
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
Note:
This is a pre released of 3.0.3 when all the changes are finalized I make and released a new one or when important bugs fix are released
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Any problem found report and use a old version.
Click to expand...
Click to collapse
Just wipe the cache in TWRP.
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.
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.
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
You could flash the zip rom through the recovery, but keep in mind this. Let the phone boot with the new update, then go back to recovery (if you get the stock recovery, reflash it with fastboot), then flash magisk
So it is overwriting twrp and magisk even if i install it directly from twrp?
meezy5 said:
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
Click to expand...
Click to collapse
You will loose Magisk/root but not Magisk Manager app and all Magisk data like modules, apps granted root, etc - once you re-root, everything will be there again.
I only suggest that you first un-hide Magisk Manager (if hidden for you), at the end you can hide it again
If you update via OTA, you will loose TWRP. If you don't want to flash TWRP again, then download the same full MIUI 12 zip package you got OTA notification for, and flash it from TWRP (without wiping, formatting or so), and immediately thereafter reboot first back to TWRP, and only then to MIUI 12
If you would like to update truly by OTA, you would have to flash the stock recovery back before starting the OTA.
Hence the way as described above, you save first on flashing stock recovery, and later on flashing TWRP back
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
meezy5 said:
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
Click to expand...
Click to collapse
See posts #933, #935-#937 in the TWRP thread:
https://forum.xda-developers.com/showpost.php?p=82945031&postcount=936