Hi, i am from Brazil and I am trying to update my Android using Configuration --> About --> Update. It downloads the new version, reboots and when it boots back, the nothing happens, same old version. i dont know if the unlocked bootloader is preventing my mobile to update. Attached ia a acreenshot
lilaum said:
Hi, i am from Brazil and I am trying to update my Android using Configuration --> About --> Update. It downloads the new version, reboots and when it boots back, the nothing happens, same old version. i dont know if the unlocked bootloader is preventing my mobile to update. Attached ia a acreenshot
Click to expand...
Click to collapse
In order to take an OFFICIAL OTA you must have an unmodified system, original unmodded kernel, original recovery and not be rooted, no xposed or any other changes.... aka PURE stock unrooted. If your update isnt taking chances are you have made changes to one of the above. Google how to go back to pure stock
I have the same problem, my phone is only unlocked, no root or system mod or other trick; the phone download the ota then reboot, but after an error message it reboot again and I have the same message (in english Language).
Related
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/
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
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.
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.
After an attempt to upgrade to Lollipop, the phone froze after software installation when it rebooted.
I was able to restore the phone from a cwm backup file to 4.4.3 and at the moment everything is working great except I cannot update to Lollipop now.
I get this error message:
Package expects build fingerprint of htc/brightstarus_wwe/m:4.4.3/KTU84L/356475.2:usr/release-keys; or
htc/brightstarus_wwe/m7:5.0.2/LRX22G/468180.7:usr/release-keys
this device has htc/brightstarus_wwe/m7:5.0.2/LRX22G/468180.21:usr/release-keys
Here is the phone history of the update attempts:
Device is HTC One M7 WWE Developer Edition 2Gb / 64GB
Device is unlocked and rooted
Device had Android 4.4.3
I flashed the stock recovery to the phone then attempted to install the Lollipop update.
Half way through the installation the operation crashed and phone was in-operatable.
I was able to restore the phone to 4.4.3 from clockworkmod recovery backup.
At this point the phone was working, but slowly.
Everything in the About / Software indicated that the software was 4.4.3 / 6.07.1540.2
However the OS from Hboot screen indicated 7.17.1540.2
Left the phone as is for a long time as it was usable, then had a problem with my SMS application, ultimately I did a factory reset and everything fixed, phone working good.
So now I reflashed the stock recovery again (7.17.1540.7) and tried to install the lollipop update again. It worked this time. 7.17.1540.2 working.
I then got the notice that there was another update (7.17.1520.21) so I tried to install this update.
After the install the phone re-booted and it froze at the HTC / Android screen; I left it for one hour and it did not come to life.
After a reboot the phone would come to this screen then go blank and nothing.
I attempted to re install from clockworkmod recovery restore but it would not work this time.
Had several Lollipop backup files - none worked - thought it was dead.
After some time I did get one to restore but none of the lollipop versions restored worked; I had an older file with 4.4.3 which worked. Phone is now back to 4.4.3
OK now with stock recovery flashed again (7.17.1540.7) I tried the update again to lollipop, but a short ways into the install the operation aborts creating error message as above.
So everything in the About / Software indicates it is 4.4.3 /6.07.1540.2
However the Hboot screen is showing OS 7.17.1540.21 now. Obviously from the last upgrade attempt.
It was a similar situation the first time I was successful installing the lollipop upgrade; the phone indicated that it had version 4.4.3 /6.07.1540.2 but the Hboot OS indicated it had OS 7.17.1540.2 (from the crashed update attempt I guess)
So could someone advise on best coarse of action to try and update this software now to Lollipop?
Could I re-flash something like the kitkat version of boot image? Would this correct the OS version reported by HBoot?
Other options I have found would be to install the RUU factory file:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
But I'm concerned that if this fails due to operating system modifactions the phone may brick, as warned at the site.
Also I have found a TRWP backup file from lollipop upgrade which I could install TRWP recovery and attempt a restore from this file?
Any suggestions?
Just use the RUU, you CANNOT OTA to Lollipop+ if you have rooted the phone without RUUing back to total stock..
Reggi747 said:
So everything in the About / Software indicates it is 4.4.3 /6.07.1540.2
However the Hboot screen is showing OS 7.17.1540.21 now. Obviously from the last upgrade attempt.
Click to expand...
Click to collapse
You must understand here that these 2 numbers are indicating 2 different things. The number you'll find in About/Software is the software version (your rom version). The number you'll find when booted in hboot is the firmware version. In order to install ota updates, everything must be 100% stock and the firmware installed must match the software version (because the firmware is also updated during an ota).
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
But I'm concerned that if this fails due to operating system modifactions the phone may brick, as warned at the site.
Click to expand...
Click to collapse
Flashing this file is the best solution, doesn't matters if your system is modified, it will revert everything back to stock and you'll be on the latest version.