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 am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....
Issue resolved, thread closed, thanks.
i thought, i might just do a separate topic, as it gets overseen easily in other threads...
What i did:
had b140 working fine. Wanted to Update to b312 Lollipop, worked well. Then, i had some problems with Google Play Services and such. Wanted to downgrade.
First, flashed stock recovery, worked fine.
Next, Transfer Package b300: No Problem
After that, b137 as KK Rom: Updates to 90% then doesn't move.
What i already tried:
- b127, b137, b141, b312 all won't either start update or get stuck at 90%. All tried with and without previous Transfer Package.
- boot and recovery .img from Stock 4.4 and 5.1 to no avail.
- Unpacked b137 and flashed boot, system, just and recovery. No boot, no downgrade
- flashed twrp 4.4 and 5.1 both 2.6 and 2.7. One did work, throws message about not being able to mount /emmc.
- tried flashing the one custom rom EMUI based for L09, script runs perfectly, before reboot: "No Rom Installed". Won't boot
- tried CM11: Won't flash properly.
I'm pretty much out of options now. I'll take anything workable. KK or LP or what ever, as long as i'm able to recover that phone. Any ideas guys?
OMG, got it working. After two days of flashing anything i found, o went back as far as i could.
1. Bootloader, flashed boot and recovery from 5.1
2. Transition Package for LT09 fro here :Huawei Rollback LT09 (Had to boot 3 Button method with SD-Card not Inserted, then after huawei logo push sd-card in)
3. b120SP03 fro here: Huawei b120SP03 (again, three button method with sd-card not inserted, then after huawei Logo push sd-card in)
This was the first firmware that booted for me. Now i need to setup and see if i can get OTA...
I can't tell you how happy am :laugh:
Excellent well done.
Hopefully this helps someone else too.
bricked
i have a MT7-L09 it does not boot other then a vibration showing the logo the turning off straight away any fix for this ?
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
I've come across this today (my OPO was rooted and I had TWRP installed), I was able to install the OTA via returning the OPO back to an unrooted stock build. You can easily do this via getting the 'Fastboot' zipped version of your current .....1NO build.
Once you have this, you only need to fastboot flash the following: - boot.img, recovery.img and system.img
After flashing just these three images, yes you'll loose root but you'll be able to OTA update to the ......2QL build via the normal phone method - hten if you want, you could then reflash a TWRP recovery and re-install a supersu.zip
One thing I forgot to add, which maybe helpful to others as it took me a moment to realise, both boot.img and recovery.img flash without issue, but due to it's size to flash the large system.img you'll probably need to brake it down into flashable chunks, notice the change in fastboot commands: -
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot -S 512M flash system system.img
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
OTAs can only be flashed through stock recovery..applicable to all devices
Hello,
on the same subject, I am looking for explanations on how to create twrp flashable files for ota updates. Do you know where I could find any resources?
Thx
I had the same issue while installing the incremental update (I got root and TWRP); I solved it simply installing the signed zip of ...2QL version which was pulled out yesterday afternoon. My only concern was about root that could be wipe away with the new installation, so I directly installed SuperSU via zip. Everything works fine till now
Sent from my A0001
Hi guys. I rooted my phone after purchase about two years ago using https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
I am still running the same version now
Twrp
Model: MHA-L29
Build: MHA-L29C567B183
EMUI: 5.0
Android Version: 7.0
Any one got suggestions and steps to get to a newer version. I think I need to switch back to Erecovery etc but if someone had some exact steps and a good version to move to would be great. I had thought about installing magisk but my main concern is being able to run games like Pokemon go or Mario kart and they seem to be detecting my root. Not even sure having root is worth it anymore.
I installed stock recovery and did ota updates.. working like a champ!
mpencexda said:
Hi guys. I rooted my phone after purchase about two years ago using https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
I am still running the same version now
Twrp
Model: MHA-L29
Build: MHA-L29C567B183
EMUI: 5.0
Android Version: 7.0
Any one got suggestions and steps to get to a newer version. I think I need to switch back to Erecovery etc but if someone had some exact steps and a good version to move to would be great. I had thought about installing magisk but my main concern is being able to run games like Pokemon go or Mario kart and they seem to be detecting my root. Not even sure having root is worth it anymore.
Click to expand...
Click to collapse
Did you really flash TWRP to eRecovery? It is possible but people usually (specially if not installing Magisk on EMUI 9) flash TWRP to (EMUI) Recovery - which is not the same as eRecovery
So, do two tests:
- switch off
a) disconnect any USB
- press and keep pressing Vol+
- boot by Pow
In test b), do the same but with the phone connected to charger.
If it boots to TWRP in case a), then you flashed TWRP (as usual) to EMUI Recovery.
But if it boots to TWRP in case b), then you really flashed TWRP to eRecovery
If you have stock eRecovery, then in case b), once booted to eRecovery, do not accept Install latest or Factory reset, just Reboot or Shutdown
---
If you rooted by SuperSU, find an option like Full Unroot, or google for and find a zip for TWRP for unrooting - do unroot
Maybe, there are similar options for unrooting from phhSuperUser
Do not accept any OTA yet - if it comes
---
Install Firmware Finder app (from Playstore or from its thread on XDA).
Open, it will show firmwares for your MHA-L29C567
Scroll to the bottom to find your b183. Must be FullOTA-MF or FullOTA-MF-PV (2017.03.22)
Download its update.zip file, copy to PC, unzip to get update.apk - open it by Huawei Firmware Extractor (find its thread on XDA, read how to use it)
Extract Recovery.img (if you need to restore stock Ramdisk) or Recovery2.img (if you really need to restore stock eRecovery)
Extract also Boot.img
Flash Boot.img to Boot and Recovery.img to Recovery (if restoring Recovery), from TWRP or from Fastboot (similarly as you flashed TWRP from Fastboot back then)
Or, flash Boot.img to Boot and Recovery2.img to eRecovery, if you need to restore eRecovery
Now you should have stock Recovery and stock eRecovery - both tests a) and b) must not boot to TWRP
Also, you should have stock Boot - boot to system, check with RootChecker - there must be no more root
----
Have a proper SIM card and WiFi connection, go to Settings, System, Update, go to its menu and take the option to get Full OTA package
If it doesn't give you OTA update, boot to eRecovery (option b) as above, phone connected to the charger) and take Install latest firmware and recovery. Follow by Factory reset, only then boot to system
If eRecovery also fails to update from b183, you can try to update by HiSuite - it has also an option to choose installing a firmware
---
If it still fails to update, you can download by Firmware Finder b190 FullOTA-MF-PV (2017.10.31)
Download both zip files, do not unzip, copy them as downloaded to DLOAD folder on SD card (not Internal memory)
Switch off, press and keep pressing both Vol+ and Vol-, then boot by Pow
It should update to b190, and hopefully you will start receiving OTA updates for Oreo and Pie (must have SIM card)
If not - to be cont.