OP5T with Android 8.1.0 (Oxygen OS 5.1.7) (Security Patch: 1 Oct 2018)
- Rooted with Magisk (Magisk v.18.1 / Manager v.7.0.0)
- TWRP 3.2.3 (bluspark v.9.85)
I received a notification about the latest Android update. After postponing it for very long, this morning I decided to give it a run. Like previously, I expected the phone will be automatically unrooted after the update and of course, I will have my new android version installed. It did not happen as expected: Android booted in recovery mode (TWRP). Once rebooted will show a notification that the update could not be performed.
My suspicion is that I am missing something here. Do I have to manually restore the phone to stock ROM, before performing this upgrade? Do I have to restore the original recovery? Any other steps that I am missing here?
As I'm not doing this things so often (mostly I'm dealing with my phone's os 1-2 times over the life of the phone), it gets quite frustrating when I forget some specific aspects.
Any help much appreciated.
derei said:
OP5T with Android 8.1.0 (Oxygen OS 5.1.7) (Security Patch: 1 Oct 2018)
- Rooted with Magisk (Magisk v.18.1 / Manager v.7.0.0)
- TWRP 3.2.3 (bluspark v.9.85)
I received a notification about the latest Android update. After postponing it for very long, this morning I decided to give it a run. Like previously, I expected the phone will be automatically unrooted after the update and of course, I will have my new android version installed. It did not happen as expected: Android booted in recovery mode (TWRP). Once rebooted will show a notification that the update could not be performed.
My suspicion is that I am missing something here. Do I have to manually restore the phone to stock ROM, before performing this upgrade? Do I have to restore the original recovery? Any other steps that I am missing here?
As I'm not doing this things so often (mostly I'm dealing with my phone's os 1-2 times over the life of the phone), it gets quite frustrating when I forget some specific aspects.
Any help much appreciated.
Click to expand...
Click to collapse
You need to download the full package and install it from recovery, then set up your root and Magisk again
https://www.oneplus.com/uk/support/softwareupgrade/details?code=7
Related
Hello,
I am about to receive a brand new OnePlus5T. It is the first time I have an unlocked phone.
I would like to learn how to root, make full backups and importantly import personal data from a backup of the data from my old phone.
Most importantly, I don't want to break anything! So before playing with (and potentially losing) personal data, I'd like to learn how to update the OS, make full backups and make recoveries.
I am already looking at the 2 following guides, but the amount of information is a bit overwhelming:
[OFFICIAL] OxygenOS 9.0.1 (Android Pie 9.0) OTA for OnePlus 5T (dumpling)
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
OnePlus 5T: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
I plan on using OxygenOS. I don't see a good reason to install LineageOS or another custom ROM.
So I'd like to use the safest way to progressively gain full mastery of my new phone, and import my personal data (phone book, text messages, application settings, etc) into my new OnePlus5T.
I'll have a look again at the above guide, but I am still wondering about where to start.
screen protector.
My new OnePlus5T was actually delivered at my home 10 minutes after posting the above.
Together with the phone, I had purchased a Glass screen protector for the OP5T.
My first question is: do I need to apply it to my new phone, or does the phone already have one (in which case I'd have a spare screen protector)?
System upgrades
I just completed the OxygenOS 5.0.2 / Android 8.0.0 upgrade to OxygenOS 5.1.4 / Android 8.1.0.
Now, the system offers a second upgrade to OxygenOS 9.0.0 / Android 9.0, but apparently some people are having issues with that upgrade.
Before I do the second upgrade, I want to install what needs to be so that I can make a full system backup and be able to revert to it if need be. I have no clue, so it'll take a while to understand how to proceed.
[Edit Jan 8th, 11:19] I have now unlocked the phone. I have not yet upgraded the system to OxygenOS 9.0.0 / Android 9.0.
I am trying to understand how to make full backups and install TWRP.
[Edit Jan 8th, 14:14] It turned out that I had to install TWRP first, then do a full backup. I tried to follow the instructions in the threads above, but I was confused by some steps and I had to perform some of them several times. Anyway, I have TWRP installed, and magisk. I did a full nandroid backup, which I pulled into my computer with the command
Code:
$ adb pull /sdcard/TWRP/ ./
.
I'm now upgrading the OS from OxygenOS 5.1.4 / Android 8.1.0. to OxygenOS 9.0.0 / Android 9.0. I'll have to re-root the phone. If everything goes well, I can the start importing personal data after that.
I have yet to figure out how to import phone numbers, text messages, etc.
I'd like to be able to
Code:
ssh
into the phone, and use
Code:
scp
and such.
Failed upgrade.
Now that I have rooted the phone, have TWRP and made a full backup, I am trying the official upgrade OS from OxygenOS 5.1.4 / Android 8.1.0. to OxygenOS 9.0.0 / Android 9.0.
But my first try failed.
The download takes about 1 hour. After the download completed, I try the upgrade, but upon reboot, TWRP came up instead of the system OS. When I did reboot the system, a message was displayed saying that the upgrade failed. I am trying the download a second time now.
[Edit Jan 8th, 15:16] Tried a second time, with exactly the same results. The upgrade failed after the phone rebooted into TWRP.
augustin.valjean said:
Now that I have rooted the phone, have TWRP and made a full backup, I am trying the official upgrade OS from OxygenOS 5.1.4 / Android 8.1.0. to OxygenOS 9.0.0 / Android 9.0.
But my first try failed.
The download takes about 1 hour. After the download completed, I try the upgrade, but upon reboot, TWRP came up instead of the system OS. When I did reboot the system, a message was displayed saying that the upgrade failed. I am trying the download a second time now.
[Edit Jan 8th, 15:16] Tried a second time, with exactly the same results. The upgrade failed after the phone rebooted into TWRP.
Click to expand...
Click to collapse
Hi, you can't directly upgrade from 5.1.4 > 9.0!
Here the recipe:
https://forum.xda-developers.com/on...xygenos-4-7-2-7-1-1-ota-t3709265/post78558808
PS.:
# TWRP for Oreo: twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
# TWRP for Pie: twrp-3.2.3-x_blu_spark_v9.91_treble-op5_op5t.img
Happy flashing!
OSS 9.0.1
Thanks. I am now on 9.0.1.
I am still figuring many things out (recovering and moving data from previous phone), but I got the most important upgrades and the most important features running now. Thanks again.
I'm hoping somebody can provide this recent, stock firmware for me. It's 8.0 with I believe the February 2019 security patch (but I'm not 100% on which security patch). I have a US variant 1710-01 with the build number listed in the title. However, it's been tinkered with and had other stuff flashed. Now I'm having a few issues. The only way to boot is to boot system from bootloader. Trying from recovery or just a normal restart only boots to stock recovery every time. It will also not take security updates (of course).
I want to just return to a fully clean, stock ROM but the only stock files I can find are out of date and will not flash, or came from another variant and screw things up worse.
I'd also be completely happy with Build 27.76-12-28-20, which is the June security patch.
I did find a dump of the ROM, but I'm not savvy enough to make it flashable (at least the system and maybe some other partitions) in fastboot.
**EDIT** link to dump of current stock ROM https://github.com/AndroidDumps/motorola_albus_dump
Thanks anyone who can help.
Wouldn't you be happy with these links?
Thanks. Those were the files I needed.
However, I flashed my current version and was able to re-lock. During the flash, it did give me the "bad ID" or something message while flashing boot and recovery partitions. But I've seen that error many times while flashing a stock ROM. On first boot, I got the notification of an update available. I took the security patch update, which successfully installed. Upon restart after installing the update , my phone was hard bricked.... like done, toss it or replace it hard bricked. Not your fault, and I'm not sure what went wrong. I've heard of similar issues on Moto phones when sideloading an update, but not when doing an OTA.
Anybody have pointers on what may have gone wrong?
OK... strangest thing I've seen for a while with flashing. This is after numerous little attempts to reboot, factory reset, flash partitions, etc. I turned off the phone in the bootloader just so the battery wouldn't go to 0% in bootloader mode. When I went to power it on again to show my wife how screwed up it was, it booted up fine. It says the update completed and it's completely normal now.... EXCEPT that it always boots in to bootloader now instead of booting to system by default. I'm not sure how to fix that. It's not a huge deal, but still not quite right.
Maybe reflashing the boot/bootloader alone will help. Haven't seen this for all the years I work with android.
If I am in a class of 1 in terms of rank stupidity please feel free to delete this post. :silly:I got sick of the updater nags. With a couple of previous Xiaomi phones I got away with finally saying yes to the OTA update which would inevitably fail after which the nags would stop for a good long while.
Not this time. I now have Miui 11 (which I did not want and which has a completely broken feedback function, btw) but lost root, magisk, and exposed.
I should also note that another Max 3 user posted here that permitting the OTA update bricked their device, so I guess things could be worse.
About to see if I can re root using the same method as before the update.
Sorry if I wasted anyone's time on the blindingly obvious.
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
brasscupcakes said:
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
Click to expand...
Click to collapse
Don't worry about anti-rollback unless you go back to rom that has no anti rollback. I go from miui 10 global to miuieu 11 P beta to miuieu 11 Q beta then back to miuieu 10 P stable. Now I settled on miuieu 11 P stable, yes miui 11 Q is very buggy. A few of my app don't work properly.
[Fix] Root on latest MIUI 11 build !
Just update Magisk Manager to 20.2 !
What's with a screen when charging, it keeps turnin on? Happens after MIUI 10 install...
Since the first version of Android Q, I could never do it Root, I can't make Magisk work, whatever I do.
I install it without problems, but when restarting it is not installed, I never have root.
Try 20.1 and 20.2, it still doesn't work.
I have a Mi Max 3 6/128
I installed the latest Miui 11 OTA update last night - taking a full Orangefox backup beforehand. After reboot, the phone was full of ads suddenly and it took me a while to figure out that root had been removed. I soon discovered that Orangefox had also been removed and replaced with a clunky-looking version of TWRP. I reflashed Orangefox and Magisk - coming back to recovery inbetween-times and it booted fine but the ads were still there so I tried to install Xposed via Magisk and that seems to have pretty much soft-bricked it. I can get into Orangefox where it said 'No Rom' which didn't seem like a good sign. I tried to re-flash the full backup I'd made with Organgefox yesterday (and this not really understanding Orange fox that well) but that hung at 'System image' - so I tried to flash without that and that succeeded but it's still totally bootlooping.
I'd very much appreciate some advice:
1. The Orangefox backup I made was with all the boxes ticked - i.e back up everything. I have the dim idea that trying to simply restore all of this won't work (it certainly doesn't seem to work). What parts of the full backup should I try to restore?
2. If I install the latest Global Miui 10 ROM - which is still Android 9 - using the Miui repair tool, will this brick the phone because of ARB? Or is it safe to do this?
3. Will dirty-flashing the latest Miui 11 rom via OrangeFox likely make something I can at least boot up and get some data (it turns out that 'SMS backup and restore' hasn't been working for weeks so I don't have a pile of work texts that I really wouldn't like to lose)?
4. Any other suggestion most gratefully received. Thanks in advance.
(Thinking about it, this thread is for the OTA breaking the MI Max 3, not my particular woes with restoring an Orange Fox backup - so, with apologies, I'll post in the Mi Max3/Orange Fox thread.)
PS: Flashing the OTA again fixed it, short term: no root is better than no phone.
Hey,
I have to apologize, since I am new in this topic. I assumed it to be a bit easier. However.
I bought a OnePlus 7 Pro and went through some up and downs now. Finally I did the following:
I unlocked the bootloader
I updated to OxigenOS 10.X, X I guess was 3 or so.
I managed to find the right TWRP image that worked perfectly: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
I went into recovery TWRP and installed the zip, additionally magesk or so. Was somewhere suggested to do so.
I rebooted into OxygenOS. So far everything was working.
I rebooted into recovery mode, into the TWRP app.
Now my intention was to install LineageOS, I choose 17 because the OxygenOS 10, I heard was based on Android Q
I wiped out the storage as suggested in the corresponding manuals
I installed LineageOS 17 zip-file via TWRP
I rebooted => Result: Nothing works anymore.
What means Nothing: When I start the phone I come into the FastBoot Bootloader Menu. That's it. No recovery. No TWRP. No OxigenOS and for sure no LineageOS. For sure I can flush img files. But non TWRP image I have chosen worked again like before.
Having spent a day now in this topic as a newbie leavs me a bit weak and disappointed now. Since I probably miss a little bit the appropriate vocabulary I am not able to find something helpful in the net.
So, what am I looking for. I need to bring that phone back into something usable. Maybe into it's original state. Still prefer to have a LineageOS 1X with TWRP installed. It was a great 5 minutes experience. For installing LineageOS 16 I guess I would have needed OxygenOS 9 installed and not 10 (like after my update).
So is there any way to safe my phone?
Hey all,
Just updated my tab S to lineage 14.1. Its really smooth running! See my previous post on this here:
https://forum.xda-developers.com/galaxy-tab-s/help/rooted-t-800-wifi-model-looking-to-t4101571
However I can't seem to install OTA updates at all. I don't even get the device booting into TWRP as others have reported (on different devices) when they try OTA updates to the OS.
(if it is necessary to do this manually via TWRP then that's fine, but just want to see if I can do these updates the conventional way)
I'm running my Tab S with Lineage 14.1 as said above. Not rooted, nano G apps isntalled. TWRP 3.3.1 recovery installed before I updated to Lineage 14.1 (and confirmed it works as of this post)
So 2 questions here:
1) Anything I'm doing wrong for the OTA updates?
2) how often are these updates to lineage OS necessary?
Try updating to the latest twrp version, and clean flash again lineage
I usually updatethr tablet every week once new build comes out.. But didnt see any difference in terms of performance, bugs
Hey @rihui
Thanks for the response! I'm half surprised anyone responded after 2 days
(I know this tablet is at its end-of-life)
I ended up figuring out where the updates are downloading to, and updating via TWRP (wiped dalvik and cache) and it seemed to work fine.
This seems to be an issue with a couple people but I don't know about this tablet specifically.
I figure once a month updates should suffice.
Does it make a difference that I don't have the TWRP app installed?
I don't have the twrp app and ota update worked fine.
I suppose monthly update is fine. Don't think there's much new development for the tablet, so it probably fine even though you don't update. (The only thing i noticed is the security patch version getting updated)
Yeah I'm not too worried about it. The update clearly worked as the other updates disappeared from the menu and there doesn't seem to be any issue with the tablet itself after playing around with it a bit.
What Lineage 14.1 did for me is what I wanted -- access to apps that I couldn't install on my older rooted stock ROM (I believe it was Lollipop still)
In another year or two we'll see if the tablet is still lasting
Thanks again!