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.
Related
Ok so I just received the OTA here in the UK. I downloaded it and when I finally did it wouldn't work. It said I needed a "victara" version and that I have a cm_victara version. That's because I have a custom recovery right?
So I installed multi-tool to restore my phone to stock and also installed the stock recovery. Full wipe and all. I then proceeded to install the OTA again but no luck it said that it had a problem.
Any ideas guys?
So far after using multi tool my phone is KXE21.187-42 and the system version is "21.21.42.victara_tmo.tmo.enUS retgb"
Now when I actually download the OTA the version it's downloading is the ".US" version.
Would really appreciate the help guys, been stuck on this for a whole day now. Also wiped my phone repeatedly lo
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/
I am not sure why it is happening with but i am not able to install 5.0.1 (12 MB) update on my Moto X 2014. I have unlocked bootloader and phone is rooted running on 5.0 Lollipop firmware.
Baseband Version:
MSM8974BP_4125.184.08.27.01R
VICTARA_EMEA_CUST
System Version
22.21.19.victara_reteu.retailuall.en.EU retin
It downloads the update file.
Reboot the device.
Goes into recovery and show me that it's installing the update. Half way on the progress bar the phone reboots.
After booting I see message which tells me that System update installation is failed. It does not give an error message or reason.
I tried installing it multiple times but same results. Any help will be appreciated.
To add Motorola Device Software updater shows me that my firmware doesn't have any available updates. Whereas i am getting regular notifications to run system update.
I attached screenshot of Motorola Device Software updater.
You should be happy, i had exact same config, and had soft brick when trying to upgrade. I believe you can't do the update if you are rooted. So you must flash stock back and then update.
Sent from my XT1092 using Tapatalk
remma said:
You should be happy, i had exact same config, and had soft brick when trying to upgrade. I believe you can't do the update if you are rooted. So you must flash stock back and then update.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
My phone keeps displaying that i have pending system update. What is the right way to get the update without bricking your phone?
After your update i am not going to try any workaround methods to force upgrade. But this is something that should be well explained by Motorola or Android community somewhere on internet. I think need to wait till the time more helpful resources are available.
gaggid said:
My phone keeps displaying that i have pending system update. What is the right way to get the update without bricking your phone?
After your update i am not going to try any workaround methods to force upgrade. But this is something that should be well explained by Motorola or Android community somewhere on internet. I think need to wait till the time more helpful resources are available.
Click to expand...
Click to collapse
i think just flashing back the stock system partition using fastbot should do it. I haven't done this myself though, i needed to completely reflash stock
gaggid said:
To add Motorola Device Software updater shows me that my firmware doesn't have any available updates. Whereas i am getting regular notifications to run system update.
I attached screenshot of Motorola Device Software updater.
Click to expand...
Click to collapse
I am facing the exact same problem.
I am currently on 22.21.19.victara_reteu.retailuall.en.EU and the update notification I am getting is for 22.121.1
I have an unlocked bootloader but the phone is not rooted.
I do not agree that OTA update doesn't work when phone has an unlocked bootloader and is rooted. The Android 5.0 update got installed on my phone when it was already rooted (I lost root access after the update).
Still looking for solution for "OTA installation failed" problem though...
gaggid said:
I am not sure why it is happening with but i am not able to install 5.0.1 (12 MB) update on my Moto X 2014. I have unlocked bootloader and phone is rooted running on 5.0 Lollipop firmware.
Baseband Version:
MSM8974BP_4125.184.08.27.01R
VICTARA_EMEA_CUST
System Version
22.21.19.victara_reteu.retailuall.en.EU retin
It downloads the update file.
Reboot the device.
Goes into recovery and show me that it's installing the update. Half way on the progress bar the phone reboots.
After booting I see message which tells me that System update installation is failed. It does not give an error message or reason.
I tried installing it multiple times but same results. Any help will be appreciated.
Click to expand...
Click to collapse
please post link of xt1092 5.0.2 en.EU ota zip (+/-12MB) tnx
Please for the love of god be a legend and post a link of this OTA i cannot find it anywhere! Copy paste it off of your phone when it downloads and upload it to dropbox or something. Please. Without this I cannot update to 5.1 :'(
aleckz999 said:
Please for the love of god be a legend and post a link of this OTA i cannot find it anywhere! Copy paste it off of your phone when it downloads and upload it to dropbox or something. Please. Without this I cannot update to 5.1 :'(
Click to expand...
Click to collapse
So far My 5.0.1 update never got downloaded and i was not able to update the phone using Motorola update. Therefore i flashed Cyanogenmod 12.1 which has latest Android build. This way i stopped annoying alerts of system update on my phone.
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
You cannot apply Google OTA updates with a custom recovery. Replace your recovery with the stock version and try again.
Not just custom recovery - any system change such as root will stop the OTA. Depending on how you rooted, you might be able to unoot using the built-in SuperSU function (I'm guessing Supersu?) but more likely than not it still won't work.
The simplest thing to do is forget about the OTA entirely. Download the full ROM from Google, unzip it, unzip the zip inside the zip, and there you'll find system.img, which you can flash in Fastboot, then reroot. Done.
sonic2kk said:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
Click to expand...
Click to collapse
How did TWRP ended on your phone in the first place?
istperson said:
How did TWRP ended on your phone in the first place?
Click to expand...
Click to collapse
I installed TWRP.
Thanks for the suggestions everyone!
sonic2kk said:
I installed TWRP.
Thanks for the suggestions everyone!
Click to expand...
Click to collapse
Oh, then as other people said, if you want OTA then totally unroot it, then reflash system of the current version, and flash stock recovery. But it's much better when a new version arrives, just download it, flash system and boot, reroot it, clear cache and dalvik. This way you'll have your updated Android days or even weeks before the OTA.
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.