I have had an issue where I cannot receive OTA updates. Whenever I check for updates the reply is: Software up to date as of <date,time>
I have rooted my tablet using the fastboot method however I originally accidentally flashed the OS to blank and softbricked my tablet. After installing the 5.0.1 factory image and installing it using fastboot, I then used CWM recovery to install SuperSU.zip to root the device, after doing this I could receive OTA updates. When I went to install them CWM aborted the update. I booted normally and selected "Clear update data", rebooted and now it always says that the device is up to date despite being on the 5.0.1 factory image.
My question is how can I go about getting OTA updates again? Also, will this involve further tweaking of files which may be risky as I have already messed everything up once.
Thank you.
EDIT: I have only just realised the grammatical error in the title but I can't change it now.
Just for clarification, are you trying to flash/sideload the OTA or are you attempting to use the tablet's built-in updater?
Nvidia pulled the 5.1 update. 5.0.1 is up to date.
Sent from my SHIELD Tablet using XDA Free mobile app
You can't get an OTA while rooted .. This is a very basic principle/consequence of rooting. There is no new 5.1 update since it was pulled a few months ago. I'm still waiting for it to get fixed but we might just get M at this rate. Rooting isn't risky if you understand what you are doing and what you shouldn't do. If you are responsible with the "power" of having a rooted device then I wouldn't worry about it.
I am waiting for the ability to flash the new OTA that was pushed on 29th. But yeah cannot pull and download the OTA while rooted.
Good evening, look nere: https://youtu.be/bT82lX40fuc
I just downloaded and installed while rooted with TWRP installed, no problem. I did have to re-flash TWRP and root, but TWRP had no trouble with the auto update.
Sent from my SHIELD Tablet using XDA Free mobile app
Related
Hey Guys,
My N5 is currently running android 5.1 and I want to upgrade to 5.1.1. My phone also shows that the OTA update is available but I am currently rooted and running TWRP. A quick google research showed me that I can´t install an OTA update while being on TWRP. Is there any other way to update my phone to 5.1.1 without losing my data?
Greets
I have this exact same question. I was going to try and use fastboot with the system image and recovery and then take the ota update. Not sure if that will work.
I got impatient, so i downloaded the factory image from the web for the version of my phone (lmy47d). I extracted the system.img and recovery.img and flashed them with fastboot as stated here -> http://forum.xda-developers.com/goo...orial-applying-ota-update-stock-root-t2976556
Rebooted the phone and then applied the OTA update. Phone is updating the apps after boot. So far seems ok.
Thank you I will try it out later
You don't lose data by default? At least not for me
Hi,
today I received a security update in my Nexus 5. I accepted it and when rebooted it got stuck in the multirom menu and it didnt update anything. Last time I have to lock the device and flash the rooted image in order to proceed with the update. this time I would like to do it diferently if possible.
Is there any other way to flash the update without removing multirom and locking back the device?
where is the update.zip stored when the system automatically downloads the update? maybe I could manually flash it using the TWRP.
thanks!
Jose
I'm on the XT1540 and I got my OTA notification and went back to stock recovery (still rooted and unlocked bootloader) but it fails halfway through flashing everytime. I reflashed TWRP and captured the OTA into a zip but get an error about updating binary or something when flashing it. Is there something I need to delete from the OTA zip to allow it to flash in twrp?
Sent from my MotoG3 using xda premium
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
HelpMeruth said:
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
Click to expand...
Click to collapse
This...do a full factory image restore, then adb sideload the ota file. It's signed. TWRP can't install it.
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
nikon120 said:
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
Click to expand...
Click to collapse
This...I can't understand, for the life of me, why everyone is wiping userdata with fastboot....that wipes your android data, and internal storage in one shot. Cache erasing is another totally unnecessary step. All that's necessary, at the most, is a factory reset with TWRP to wipe the android data and both caches....but even that shouldn't technically be necessary for an update like this. It's not like this is the marshmallow update!!
arunhebbare said:
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Click to expand...
Click to collapse
@arunhebbare I've got the APAC version of the G3 as well, which ROMs are you flashing? I could only find images of the India version, did you use those?
Hi,
my P8max is rooted with SuperSU and I had TWRP installed. Now the recent b211 OTA released, and I would like to install it. Since my phone was modified, I won't get an update over EMUI, but I downloaded is elsewhere.
I would love to keep everything setup as it is and avoid the wipe. I flashed back the P8max stock recovery to install the update as local update. Now my question is, will I experience any trouble because I have a rooted phone with SuperSU?
If so, would it be enough to just unroot the phone with the SuperSU settings button "unroot", or is a wipe unavoidable?
Best regards
Sent from my HUAWEI P8max using XDA-Developers mobile app
You have to be on Stock recovery and no root.
if you got an error while installing OTA,
follow this guide to return to full stock unmodified rom http://forum.xda-developers.com/p8max/help/official-rom-download-links-t3206144 then install OTA update.
For those who say that must unroot to see the ota update i say that their rong...i have root and yesterday the ota notification show me that an update is waiting.I will not update because i see that its not stable yet.
Yep, got the notification too, even though I'm rooted and on a custom recovery.
Sent from my HUAWEI P8max using XDA-Developers mobile app
You will get notified, but installing it will fail because recovery checks your system partition if its modified or not.
Ok,
I have fastboot and adb working on my linux mint host. Can someone explain to me how to install ota updates on a rooted pixel phone? I tried installing it via the zip using twrp and that didn't work. It just unrooted my phone so I had to reroot it. I tried using Flashfire and downloading the ota update and then using flashfire to detect the ota update and flash it and everytime it doesn't work... errors and then unroots my phone.
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
bush911 said:
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
Click to expand...
Click to collapse
Ok, I downloaded the ota update via Google's webiste. Flashed it with flashfire. It asked if I would like to overwrite the boot and recovery. (said it would most likely fail if I didn't.) I told it ok. It flashed for a while. Rerooted automatically. It booted back up. It didn't update. Still prompting me to update ota.
I just tried the second method in this article
https://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Which version of SuperSU are you trying to use? Both of the following links discuss verified boot, which is one possible item you could be running into with the latest Pixel updates.
SuperSU v2.82-SR1 is the latest version, and it added boot signing.
https://plus.google.com/+Chainfire/posts/XikxTkhHpiG
If you are using an older version of SuperSU, then you will need to sign the boot image. I installed the latest Pixel update before v2.82-SR1 was available, so I just had FlashFire install the OTA, and then I added the following zip to the list of FlashFire actions immediately after it was set to root the phone again. FlashFire worked without issue to update to the latest release for June by adding the following before rebooting when using a version before SuperSU v2.82-SR1.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I am attempting to flash 2.79. but immediately after, I flash the verifiedbootsignerv3.zip
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
yared1212 said:
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean here...
dorlow said:
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Click to expand...
Click to collapse
That looks like an April update, and there are newer versions, so I'm not surprised the phone would try to update.
https://developers.google.com/android/ota
Three months ago was the first time I tried FlashFire, and I couldn't get it to use the OTA to the phone at that time. Some of the FlashFire instructions made me think I might need to use the backup option to get the OTA to work, but I was actually able to take the May and June OTAs using FlashFire without the backup option. I'm not sure why FlashFire didn't work for an OTA in April, while it did work with an OTA on the phone the past couple months. I think I may have ended up using a download from the Google site with FlashFire in April, so my only guess was that either using the Google download or a newer version of FlashFire is why I was later able to use the phone OTA with FlashFire for May and June.
SuperSU v2.79 SR3 with either the VerifiedBootSigner v3 or v8 has worked for me in May and June, and then I've taken the Play Store SuperSU update to v2.82. I don't have TWRP installed, and I get the impression there could be some extra steps for FlashFire when TWRP is installed, so I don't have to deal with that. Of course the only reason I switched to using FlashFire is because it seems like the quickest method to just take an OTA and update with SuperSU. If FlashFire didn't work so easily, I'd just go back to sideloading, or using one of the other update methods.