Hi, today I got the notification on my G (India-Dual Sim version) that the 4.4.4 was available to download.
I tried to go back to stock recovery to do the upgrade but for some reason it didn´t work, I was able to flash but the stock recovery never came up. In the end I decided to give a shot and see what happened.
I have the CWM recovery, and it notified me that the file used for the update had not a correct signature, decided to continue, no problems so far. In the end it notified me that maybe root may have some issues (the same warning when you root the phone the first time), told it to fix it and it rebooted.
All smooth and so far no problems, but it did show a warning on the main screen (after being all loaded) that something went wrong, but the phone booted OK and the system version is 4.4.4, maybe something to do with the stock recovery or something, don´t know, but so far, is you have CWM, I believe you can do the OTA update withouth problem.
Will let you know if something comes up.
Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.
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.
Ok guys,
I'm gonna post this knowing that there is probably NO SOLUTION to my issue. Let me attempt to explain EXACTLY my issue and what I did. I found a potential solution here > http://forum.xda-developers.com/showthread.php?t=2582142 however my issues don't exactly match the description in that thread.
So, long story short - I've ended up back on the G2 for now (until I upgrade) - I got the G2 on Amazon brand new. When I got it the other day - I discovered when I attempted to boot into download/fastboot or recovery using ADB - the phone would just reboot. The G2 came with KK 4.4.2. I had it rooted but still couldn't get into recovery or download modes. So, for the hell of it - I decided to take the OTA (after reading the G2 can still be rooted on LP). Halfway thru the OTA update (after it reboots into stock recovery) the device reboots. Did it multiple times. So, I went to LG's website and downloaded the LG Mobile Support tool. Plugged the G2 in - it said there was no update available. So, I tried one of the options I found to update the recovery. So, it starts updating.... and then I realized it flashed Lollipop instead of updating the recovery. So, no I'm on stock Lollipop 5.0.2 and I still can't boot into recovery/download/fastboot to flash a stock KitKat image so I can root, ROM, etc.
Anyone heard of this issue or even possibly know how to fix it WITHOUT using a bootable Linux drive or a virtual machine (I have a Windows 8,1 laptop - 8.1 doesn't support Hyper-V out of the box)? If you know anything related to this - please post. I have no clue what else to do except accept the fact that I have a stock G2 that I will NEVER be able to root. I was going to send it back to Amazon and get another one but I don't feel like going thru all that for a phone I'm probably not gonna end up using too much longer.
I got a notification this morning saying google play services wanted to update. I thought the google play services app itself was wanting to update, so I went ahead plugged in my watch and let it start.
As it turns out, it was the official update from AT&T to android wear 2.0! Finally! I already had android wear 2.0 on my watch, I flashed it using a kdz that someone had uploaded that had already gotten it on a w200L.
Anyway, once I realized what it was doing I was worried it might brick since I had already updated it previously to a different android wear 2.0 version.
I'm happy to report that it updated successfully. I still had stock recovery so that remained the same. I had used TWRP before, but only booted twrp recovery to flash supersu. I never flashed TWRP to my device, I'm not sure if having TWRP recovery installed would've caused the update to fail.
Changes: I lost root access. That is OK because I only rooted my watch so I could add a new APN to use my watch with a Freedompop sim card. Actually it was a good thing because before the update Android pay didn't work because of my root access, and after the update android pay allowed me to add a credit card and looks like it will work, since I no longer have root, even though my bootloader is still unlocked!
Anyways, I just thought I'd bring this up in case someone else has a question about it. My experience may differ from yours, I am not responsible if you have different results.