Related
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 unlocked the bootloader with no problem and loaded Clockworkmod custom recovery without a hitch. When I downloaded the nightly of CM11, it failed halfway through installation. I tried using other builds and two different custom recoveries. Open recovery didn't fail, but the phone just stayed at the blue CyanogenMod screen and never booted.
Now, I have no idea what to do, and I don't know how to just return to stock. I honestly rooted just so I could WiFi tether in infrastructure mode, and now I can't even make a phone call. What can I do?
So to return to stock, see this thread.
As for your issue, did you make sure to do a factory reset in recovery before booting?
Also, when you saw the blue CM screen, how long did you wait? The first boot can take quite some time.
Older versions of CWM won't flash CM11... same with other recoveries, older won't flash CM11. The latest OpenRecovery should work fine. I'm not sure how up-to-date our CWM build is.
Latest Open Recovery
Okay, I was finally able to return to stock. This may sound stupid, but it was really hard to charge it. The phone would come on everytime it got a little bit of juice in it, and then in a few minutes, the screen being on for too long killed the battery faster than it would charge it. I was finally able to get a wall charger to make it stay at the blue battery charging screen long enough for it to charge to 100%.
I didn't know an older Clockworkmod won't flash Cyanogenmod 11, and I actually didn't do a factory reset in recovery before flashing Cyanogenmod 11. I honesty waited about 20 minutes for the phone to boot until I gave up. Where can I find the latest open recovery?
Still fails
I got the instructions how to install CyanogenMod 11 from their website, and hxxp://wiki.cyanogenmod.org/w/Install_CM_for_xt897c is where you can see it. They do recommend to use Clockworkmod, so I used 6.0.1.3, which is the latest that hxxp://clockworkmod.com/rommanager shows. I did select the option to wipe data/factory reset, and it still fails.
Code:
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-11-20131210-NIGHTLY-xt897c.zip
(Status 7)
Installation aborted
Before you ask, yes, it even fails when I use the stable build instead of the nightly.
Taric25 said:
I got the instructions how to install CyanogenMod 11 from their website, and hxxp://wiki.cyanogenmod.org/w/Install_CM_for_xt897c is where you can see it. They do recommend to use Clockworkmod, so I used 6.0.1.3, which is the latest that hxxp://clockworkmod.com/rommanager shows. I did select the option to wipe data/factory reset, and it still fails.
Code:
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-11-20131210-NIGHTLY-xt897c.zip
(Status 7)
Installation aborted
Before you ask, yes, it even fails when I use the stable build instead of the nightly.
Click to expand...
Click to collapse
Again, this version of CWM is not going to flash CM11. Use the latest OpenRecovery or TWRP.
TWRP 2.7
Okay, I flashed openrecovery-twrp-asanti_c.img using fastboot. I did a factory reset in TWRP. I installed both cm-11-20131210-NIGHTLY-xt897c.zip and gapps-kk-20140105-signed.zip files. It appears like it went successfully. It was 9:43AM when it booted, and it's now 9:48AM, and I'm still waiting, watching the blue cyanogenmod logo with the spinning arrow around its head.
Nada
It's now 10:05. It's really supposed to take over 20 minutes to boot up?
40 min, no luck
Okay, after waiting 40 min for it to boot, I'm sure at this point it wasn't working. Any ideas?
You are installing an oddly old nightly... Maybe you didn't know, the builds are now 'unified'. Look for moto_msm8960.
But yes, let it boot. It may take some time.
Gave up
Yeah, I had no idea they were unified. In any case, I gave up. If it takes over 40 min, I'm sorry; it's not working.
I did use TWRP to root my phone, and I found a tether unlocker that allows me to use both infrastructure and USB tethering, which is all I wanted in the first place.
Well whatever works...
Did you ever encrypt your data partition?
If so, see this thread.
I tried to update to the latest firmware 4.4.4 Kitkat today.
The phone downloaded the update okay, but when I tried to install it the phone restarted and took me to CWM Recovery. The Recovery asked if I wanted to "install untrusted file" or zip, something like that. I chose yes, and in a matter of seconds it told me that the install was aborted. After that it asked me if I wanted to fix my root? which I also pressed yes to. The phone rebooted, and loads fine, but after about 30 seconds of the phone being powered on the phone powers off and repeats this.
How do I fix this? I don't mind losing root, I just want to be updated and not lose any of my files (they arent backed up)
Thanks,
Barky02
You need the the stock recovery. Flash the stock firmware of your device without doing mfastboot erase userdata.
I used philz recovery advance that worked fine
Sent from my XT1032 using XDA Premium 4 mobile app
Hi folks,
My NEW (RMA) Shield is rooted / TWRPed / 3.1 / and I applied the noOTA process to it so that they couldn't force-push some future undesirable OTA (or accidental bricking) at me.
Of course, as soon as I get settled in to the new unit with all apps and data where I want them, they do this new OTA.
What's the process for applying the latest OTA, given a rooted, TWRP recovery system? Do I just boot to TWRP, flash the full OTA, reflash noOTA, and be done? But wouldn't the full OTA kill TWRP, so I should reflash it?
Before I mess up this thing I want to make sure I get it right. I've got a PC so I can ADB/Fastboot sideload stuff if need. My main interest is in not messing up my data and apps.
Thanks
:highfive:
Frankenscript said:
Do I just boot to TWRP, flash the full OTA, reflash noOTA, and be done? But wouldn't the full OTA kill TWRP, so I should reflash it?
Click to expand...
Click to collapse
that's correct. this update in particular doesn't upgrade the recovery too, so TWRP won't be affected, but if you have an unlocked bootloader, you can just reflash TWRP at any time. for root, you might also want to flash SuperSU from TWRP (it will ask before rebooting if you don't install it yourself)
Thanks Bogdacutu.
I copied the full US LTE OTA 3.1.1 over to the internal memory (I used the downloads folder), rebooted to TWRP, and flashed it from TWRP. Before rebooting, to be safe I also flashed nomoreota.zip and then supersu.zip. On first boot I got the typical post-OTA "android is updating" thing where it optimizes the apps. Any idea what this app optimization is? I've always wondered... This app optimization process actually took longer than flashing the OTA and stuff.
After finishing the first boot, SuperSU told me it needed to update the binary, which failed. It suggested a reboot.
I rebooted normally (not going into recovery or anything first). This boot stayed on the NVIDIA boot up screen a lot longer than usual. after about 10 minutes like this I turned it off. After it was all the way off I turned it back on again. This time I let it go about 20 minutes. Still nothing past the NVIDIA boot screen. Crap.
I turned it all the way off. Rebooted with volume down button and was relieved to see it give the usual options (continue, recovery, fastboot, etc.). I let it go into recovery and got to TWRP in short order.
At this point I turned it off, as the battery was getting a bit low and I have to take my kid to a soccer game. I'm charging it in powered off mode until I get home.
Any ideas what to do next to get this thing booting into Android again?
Thanks
Marc
After it charged all the way up, when I got back from my kid's game, I booted back to TWRP and reflashed the OTA update.
I then told TWRP to reboot... it said something about should it reflash SuperSU script to preserve root. I agreed and let it reboot. It came back up in Android. I'll explore the situation and report back.
All seems well at this time.
According to rootcheck my root is preserved. SuperSU successfully updated binaries in normal (non-twrp) mode. Checked for system update. It said I was up to date. I booted back to TWRP, flashed nomoreOTA.zip again. Rebooted again, no problems. Back to normal, fully updated. Phew.
I'm not sure what went wrong the first time, but it seems OK now.
Not really sure where I should have put this but have a weird issue. I have a droid turbo xt1254 that I have rooted and flashed many times. The most recent, today, I accidentally did a full system wipe and when I went to reflash the rom already in twrp, it gave me an error.
I then tracked down cm13 for my phone, which had worked previously and reinstalled it but every time I reboot the phone, it goes straight into twrp.
I have found that If I reboot into the bootloader, I can choose factory and whichever rom I have installed works until I reboot.
Can anyone help me stop this and get it to boot straight into the rom?