Hi
I have my Moto G in 5.0.2.
Wednesday I receive a notification to update to 5.1, so I tried to do it.
The update downloads fine, but then when it comes to install it there's a problem.
The phone reboots and the android logo appears. Then it starts to install the update. However, after a while, a error occurs and the phone reboots again and starts up normally.
I don't know why I can't install 5.1.
I have bootloader unlocked and the phone is rooted.
May this be the problem?
Thanks
I have the same problem with my Boost Moto G XT 1031. Update downloads, reboots, update fails, reboots to 4.4.4. I have tried a factory reset, and changed to ART. Still update fails everytime. Does anyone know if there is a log on the phone?
Joaosacramento said:
I don't know why I can't install 5.1.
I have bootloader unlocked and the phone is rooted.
May this be the problem?
Click to expand...
Click to collapse
OTA updates contain only the differences to the official previous ROM, so yes, a modified /system partition may be the problem.
paulsaz said:
I have the same problem with my Boost Moto G XT 1031. Update downloads, reboots, update fails, reboots to 4.4.4. I have tried a factory reset, and changed to ART. Still update fails everytime. Does anyone know if there is a log on the phone?
Click to expand...
Click to collapse
I don't know much about the stock recovery, but look in /cache/recovery.
You have to be completely stock. Unrooting won't fix the problem. Flash stock firmware before upgrading. This is specific to lollipop updates because they refuse to install on modified system partition. That's why Unrooting wouldn't work.
Sent from my XT1032 using Tapatalk
Related
The new update today for the moto g is causing my phone to be in a boot loop. I really don't know why. It's rooted and I use twrp recovery to wipe the cache and it works again but if I try to install the update it will just cause the boot loop again. Please help I really need this update my internet is slow on my phone! Thanks.
The same thing happened here, with CWM recovery. The update probably expects stock recovery.
Same here
Sent from my XT1032 using xda app-developers app
Nevermind
Doesn't matter. I remember reading somewhere that you no longer get updates from motorola once you root your device. I'll wait for someone to release a flash for it. Thanks.
cillian334 said:
Doesn't matter. I remember reading somewhere that you no longer get updates from motorola once you root your device. I'll wait for someone to release a flash for it. Thanks.
Click to expand...
Click to collapse
Not true. I rooted, flashed custom recovery and all, and STILL received the update. The trick is how to get it into the phone without the bootloop.
Try the suggestions I put in this thread
http://forum.xda-developers.com/showthread.php?t=2663205
A little attention is all that is needed...
Just went to hell and back.
I just reflashed to stock and it turns out it was a bad rom and i couldn't fix it but i think it's ok now.
I have the Indian dual sim version, and my Moto G is having bootloop problem after a month of installing the OTA :\
Can anyone help me out? I have tried reflashing the stock firmware but of no use.
Just the motorola blue logo shows up and then black screen. The recovery also doesn't work
ahank said:
I have the Indian dual sim version, and my Moto G is having bootloop problem after a month of installing the OTA :\
Can anyone help me out? I have tried reflashing the stock firmware but of no use.
Just the motorola blue logo shows up and then black screen. The recovery also doesn't work
Click to expand...
Click to collapse
Did You found any solution?
I have same problem here...
jayrocky11 said:
Did You found any solution?
I have same problem here...
Click to expand...
Click to collapse
Wipe cache, it sabed MY bacon for sure. Use fastboot
Hi, after looking on google and the xda forum I didn´t find a similar question to my problem.
I am on 4.4.4, currently rooted and bootloader unlocked, and I am receiving the OTA update. The first time I tried to update, I got an error because I was on a custom recovery; installed stock recovery and tried again (downloading again OTA). This second time the progress bar started moving and suddenly the phone rebooted to normal and said that something happened and the phone was not updated.
My question is: do I need to be completely stock, even withouht root, to update? I mean, I can´t find a post that says the requirement to update to Lollipop in specific (non english speaker here, sorry).
Hi there! I'm from Brasil. Owner of a Moto G music edition XT1033. I had the same problem with my phone here. Except that I did not use any custom recovery. I think that when I rooted my phone, the proccess I followed has changed the recovery in some way. Even after removing the root access by the option on SuperSU I was unable to install the OTA. I think that if you flash only the recovery of an stock ROM, you might receive the update via OTA. But the solution I used was to flash the entire stock 4.4.4 ROM. After the flashing process I received the OTA again and using 5.0.2 since then... And loving It!
I hope this reply helps you in any way!
Good luck!
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
A few months back I flashed xtrestolite to my g920i and have since flashed odex, deodex and several aroma versions in different combinations. Since the initial flash the scanner has not worked. Currently using the latest unikernal, though was using a different one when I first flashed. TWRP latest too.
I was wondering if someone could give me some in site weather it's hardware coincidence or a driver not loading or something.
When I try *#0* and try the sensor test I see "unfortunately, hwmoduletest has stopped working"
Trying to utilise the scanner will always show "an error has occurred with the fingerprint sensor, if this message appears repeatedly please restart your device" though restarting has never worked.
I have not tried going back to stock as my carrier rom is 5.0.2 still.
Could someone please lend me some in site as to what might be causing this?
Thats because you're using 5.0 bootloader on 5.1 rom. You either have to wait until your carrier releases 5.1 so you can flash 5.1 bootllader or downgrade rom to 5.0.
Where you ever able to fix this problem? I am having the same problem! Thanks
gmata007 said:
Where you ever able to fix this problem? I am having the same problem! Thanks
Click to expand...
Click to collapse
This is a problem associated with not updating bootloader. When you update to 5.1.1, you have to update your model specific bootloader to 5.1.1.
Rakcoon said:
This is a problem associated with not updating bootloader. When you update to 5.1.1, you have to update your model specific bootloader to 5.1.1.
Click to expand...
Click to collapse
Do you mean this?
http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
Because I tried that with no luck.
gmata007 said:
Do you mean this?
http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
Because I tried that with no luck.
Click to expand...
Click to collapse
Can you provide me with more info, country, model?
Hello,
I have a Nexus 5 and installed Android 6.0 OTA and I rooted the phone. I recently got a notice for Android system update (2.5MB) and I have a problem with the update I suppose because of that root.
Update gets downloaded, the device restarts and then on the screen I get an error.
Does anyone know what the problem is and how to make the update?
Thanks!
Yes, I think a great number of people know the answer... I had to ask the same question myself a long time ago.
Since Android 5 (I think) the OTA process looks at the entire system for any changes to the ROM partitions, and it will update only if the ROM is intact and unchanged. Root changes the ROM, therefore no update.
I believe that you can update manually by flashing just the system partition, but you'll then have to re-root the phone.
It was precisely for this reason that I got fed up with root, despite its many advantages, and now run encrypted, unrooted, and with Netguard firewall protecting at least some of my privacy.
NoOne12 said:
Hello,
I have a Nexus 5 and installed Android 6.0 OTA and I rooted the phone. I recently got a notice for Android system update (2.5MB) and I have a problem with the update I suppose because of that root.
Update gets downloaded, the device restarts and then on the screen I get an error.
Does anyone know what the problem is and how to make the update?
Thanks!
Click to expand...
Click to collapse
u should update before making any changes in the system folder or to the recovery.
You should not take the OTA updates while rooted.
One solution would be to download the factory image for the update and fastboot flash system.img from the download, wipe cache, then reinstall supersu.