Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
retfeg said:
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
Click to expand...
Click to collapse
same problem here! brand new phone, 4.4.2 o2 UK.
the mismatched partition size error is not important i know that.
have tried Philz (got it to work once, but after rebooting, had gone again. ever after letting it fix the rom rewrite on exit!). also tried stock CWM 6046 and 6047.
have tried entering recover immediately after flashing.
have tried flashing multiple times.
have tried different usb ports.
ideas please?
i've never had this much trouble with any phone (have experience over 3 years with Blade, G300, Xperia range etc.)
edit: tried using fastboot -S 0 parameter also, seems to make no difference. phone won't boot into recovery. this is slightly different to the problem i had with old phone, that one would boot Philz but not boot any ROMs. this one is booting stock ROM. if i can get Philz to "take" again i could try flashing CM, but i wanted to stay on stock, and just root it..
edit2: just started working! bizarre.. hope this doesn't jinx it. i wrote two recovery images with -S 0 and it works, not sure if because of that or something else. btw Philz won't backup the stock rom, odd - it just errors out, CWM standard works though.
hurrah! i rebooted normally, went back to fastboot and recovery still there. this is with recovery-clockwork-6.0.4.7-falcon.img
now i can hopefully root it..
wonder if my 3rd moto g will get any easier! this is a huge PITA of random non-workiness so far.
Background, I downgraded my firmware to 23.0.a.2.93, rooted with locked bootloader using giefroot v3, then installed NUT's Z3-lockeddualrecovery2.8.3-RELEASE.installer, after which I flashed 5.0.2 to preserve root.
Now my phone refuses to boot into TWRP (skips it altogether, I've tried booting into recovery from app like Flashify, TWRP manager and also using adb command). Phone restarts, but never boots into recovery, and goes straight to the android system. I know I have it installed because TWRP manager shows that it is installed, but when I try to flash a .zip file phone just restarts and nothing happens. I wanted to flash xposed's .zip file, otherwise it won't work.
So my question is, what could be the problem? I reinstalled NUT's dualrecovery several times, still no results.
Seriously, have you been on another planet lately? Sorry for sounding a bit harsh.
It's a known issue that Dual recovery isn't still available for Lollipop.
Weirdest problem, and not one that I've ever encountered after playing around with Android since the G1 days!
My Boost Moto G 2013 will only boot into the recovery, no matter what I do. I've searched and searched through Google and on XDA and found nothing that matches my problems exactly.
I can get into the bootloader (am running version 41.1A) and flash a new recovery. I've got TWRP on there right now, but I've tried CWM as well -- same problem. I've actually installed Android 5.1 from the stock flashable zip, and it says it flashes fine, but still won't boot into it. No matter how I restart the phone, it just goes straight into recovery.
Any ideas?
I'm assuming that you've tried different ROMs? I had a weird problem where I could no longer flash any ROM's without getting an error. Only after I did a complete wipe of everything (including internal storage which was the key) was I able to properly boot up. Not quite the issue you're having but worth a shot, make sure you can access the phone on your PC so that you can copy over the ROM after the wipe.
I have had this problem recently. I believe I had to fastboot flash stock recovery, then an older, smaller CWM to avoid partition mismatch problems. Then flash the TWRP you want with a zip with CWM.
Sent from my XT1031 using Tapatalk
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Aaaaaaannnnnd.... I've also completely lost my WiFi. Says that it's on, but it's got the slash through it in quick settings & doesn't find any networks.
t-readyroc said:
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Click to expand...
Click to collapse
1) the twrp you linked to is for lollipop, states that in the notes section half way down the page.
2) to get root with this method you also have to install phh superuser
3) that dead Android IS the stock recovery
Now for help: flash this recovery(there are two here read and find the one for MM)
https://r.tapatalk.com/shareLink?ur...share_tid=2877117&share_fid=3793&share_type=t
[RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]
Sent from my SHIELD Tablet K1 using Tapatalk
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
t-readyroc said:
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
Click to expand...
Click to collapse
Ok, from here just flash the supersu.zip and you should be good. I can't remember if 2.65 works or not but I know you can find a copy of 2.71. someone else has a problem with 2.72 so it may or may not work.
As for twrp it has touch screen lag issues, I don't think any of the mm compatible versions have been able to fully fix this. I've had the same problem with dalvik cache and cache wipe, it is slow as molasses but will complete eventually. Once you have root I would suggest using a program called flashfire to flash zips and do things like cache wipe. It works like a charm.
https://r.tapatalk.com/shareLink?ur...share_tid=3075433&share_fid=3793&share_type=t
[Android 4.2+][ROOT][2016.05.11] FlashFire v0.33 - Play BETA
Sent from my SHIELD Tablet K1 using Tapatalk
Thanks again, Exile. I actually had to re-flash TWRP, oddly, but after some searching, I found a mirror for su2.71, & adb pushed it. Once I had TWRP back in order, I was able to then flash it & my root is back together.
Glad you got it working. Have fun and be safe
Sent from my SHIELD Tablet K1 using Tapatalk