Database Develop

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!

a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.

So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.

RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

How to get back OTA update on N7 2012 mobile

Hi all, yesterday i got an ota notification for 5.1 on my N7 2012 mobile version, but coz i rooted before, the update was not successful. I tried to make a search in the internet for the download but strangely, there is no image uploaded for nakasig over there. Now i already did a full clean install on 5.0.2, and tried to push Check for update many times, but no ota ever happened again. How can i get it back? Anyone knows it, pls let me know. Many thanks!

Also in exactly the same boat. Fresh install of 5.0.2 on N7 2012, rooted. OTA update to 5.1 fails every time. Any advice?

The OTA will fail if you use a custom recovery (twrp or cwm). If you fastboot flash the stock recovery image, the OTA should work. The factory image is available for the wifi version, so you could update to 5.1 using it with fastboot. I don't know if the mobile factory image version has been released, but if not, it should be soon.

[Q] OTA failed to update in rooted phone and will no longer appear

Hi all,
I have a unlocked, rooted Moto G 2014 (2nd gen) US version. I have T-mobile on it.
Yesterday I received an OTA notification to update it to Lollipop version 22.41.19 (described here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105214).
I downloaded it and confirmed the instalation. Phone rebooted to TWRP and I tried to flash the file from the /cache folder, but i received an error.
I rebooted the device and tried the same again, with the same errors. Then I decided to do some research and I learned that OTA cannot be flashed in rooted devices. Damn!
The problem is: I deleted the .zip file on the /cache folder and now the OTA no longer appears on my device. If I go to settings -> about phone -> system updates, all I get is: "Your device's software is up to date", even though I didn't finish the upgrade process.
My question is: how can I get back the OTA notification? it looks like this 22.41.19 version is the most updated I've seen. Perhaps Lollipop 5.1? I am interested in reverting the device to stock, performing the upgrade and rotting it again.

inarush said:
Hi all,
I have a unlocked, rooted Moto G 2014 (2nd gen) US version. I have T-mobile on it.
Yesterday I received an OTA notification to update it to Lollipop version 22.41.19 (described here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105214).
I downloaded it and confirmed the instalation. Phone rebooted to TWRP and I tried to flash the file from the /cache folder, but i received an error.
I rebooted the device and tried the same again, with the same errors. Then I decided to do some research and I learned that OTA cannot be flashed in rooted devices. Damn!
The problem is: I deleted the .zip file on the /cache folder and now the OTA no longer appears on my device. If I go to settings -> about phone -> system updates, all I get is: "Your device's software is up to date", even though I didn't finish the upgrade process.
My question is: how can I get back the OTA notification? it looks like this 22.41.19 version is the most updated I've seen. Perhaps Lollipop 5.1? I am interested in reverting the device to stock, performing the upgrade and rotting it again.
Click to expand...
Click to collapse
Try to flash stock 5.0.2 again, and see if it shows any software update..!! ?
Sent from my Moto G 2014 using XDA Free mobile app

inarush said:
Hi all,
I have a unlocked, rooted Moto G 2014 (2nd gen) US version. I have T-mobile on it.
Yesterday I received an OTA notification to update it to Lollipop version 22.41.19 (described here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105214).
I downloaded it and confirmed the instalation. Phone rebooted to TWRP and I tried to flash the file from the /cache folder, but i received an error.
I rebooted the device and tried the same again, with the same errors. Then I decided to do some research and I learned that OTA cannot be flashed in rooted devices. Damn!
The problem is: I deleted the .zip file on the /cache folder and now the OTA no longer appears on my device. If I go to settings -> about phone -> system updates, all I get is: "Your device's software is up to date", even though I didn't finish the upgrade process.
My question is: how can I get back the OTA notification? it looks like this 22.41.19 version is the most updated I've seen. Perhaps Lollipop 5.1? I am interested in reverting the device to stock, performing the upgrade and rotting it again.
Click to expand...
Click to collapse
If you're rooted with Super SU then just open the Super SU app, go to settings, scroll down to full uproot and choose that. Then after the update, boot to recovery and reflash Super SU if you'd like to root again.
Sent from my GT-P5210 using Tapatalk

2nd OTA lollipop update failing

I recieved the first OTA update for lollipop and it installed correctly. Now I went to download the large 700+mb 2nd OTA update and after the download completes my phone resets. It goes into installing the update, however about 1/4 of the way through the update, i get the dead droid screen flash on my screen and then my phone reboots back to 4.4.4 and tells me that the updated was unsuccessful. I have a moto x XT1060 dev ed, build KXA21.12-L1.26-4 on system version 212.166.4.
I'm stumped on what to try next. I have already returned everything back to stock and downloaded all updates and I get to the same point and get the same results. I've wiped all data, system, cache, and davlik, installed stock recovery and still get the same results. i've removed super user rights to see if that would work but it did not. I'm at a lose at what to try next. Anyone have any other ideas?

[email protected] said:
I recieved the first OTA update for lollipop and it installed correctly. Now I went to download the large 700+mb 2nd OTA update and after the download completes my phone resets. It goes into installing the update, however about 1/4 of the way through the update, i get the dead droid screen flash on my screen and then my phone reboots back to 4.4.4 and tells me that the updated was unsuccessful. I have a moto x XT1060 dev ed, build KXA21.12-L1.26-4 on system version 212.166.4.
I'm stumped on what to try next. I have already returned everything back to stock and downloaded all updates and I get to the same point and get the same results. I've wiped all data, system, cache, and davlik, installed stock recovery and still get the same results. i've removed super user rights to see if that would work but it did not. I'm at a lose at what to try next. Anyone have any other ideas?
Click to expand...
Click to collapse
I was having this same problem, but here is the process I went through to get through the full update to 5.1:
I saw this post this morning and started with it: http://forum.xda-developers.com/moto-x/general/help-lollipop-update-unlocked-bootloader-t3201426 I had previously downloaded the version of 4.4.4 referenced in it.
I don't have RDSLite installed so I moved on to this post: http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and used Option #5 since I already the Android SDK tools on my computer. After going through all the steps I have successfully stepped through all three updates, rebooting the phone after each whether it helps or not. My phone is currently optimizing apps after the second 5.1 update.
For reference I was on the most current version of 4.4.4, rooted with TWRP with no modifications to any system/bloatware apps. I originally tried Option #6 in the above thread which allowed me to take the first 5.1 update but the second update failed in the same way you described.
Hope this helps, and good luck!

Thanks for the post. I was reading through that post late last night and I was going through option #2. I didn't read further down to option #5, but that worked perfectly. My phone is optimizing apps as we speak.

pblem with restart's and stuck device

hi
all, i have nexus 6 device with 6.0 MRA58R and open bootloader and it was update by the device from google,still before that i try to do root and didn't succeedwith 5.1, so i go back to 5.1 and it was update as i said but the device is stuck by the start or just by regular use...something is wrong and i don't know what, there is also sound when it stuck like A screech sound and it stuck
what to do next?
thanks

If your bootloader is unlocked, as mentioned in your other thread, download a stock image from Google and flash its components (except userdata.img) using ADB. As a result of your tinkering, something got messed up on the device, and flashing the stock image should resolve that.

tried these ...didn't help,it stuckes even after good flash with adb cause with OTA it stucks at the middle

You flashed MMB29Q from the shamu section of the page here? That is the absolute latest factory image available. There should be NO OTA update available.

first of all i tried to download the OTA cause i was with root and did unroot and i want to saw thet it get's the OTA's correct ,then i installed the version as you write, but still when i start the wifi or in regular use the device can be stuck and restart.
any idea to solve it? even in safe mode it stucks

No, not really. Like you mention in your other thread, it appears to be a hardware problem.
For the record, downloading the OTA updates is a waste of time when the latest factory image is available. When you get your replacement device, assuming it's not already on 6.0.1, install the image from the link I gave you, as it already includes in the image all the updates Google has released for Android 6.0.1.