HELP!!! i bought my htc butterfly 4days ago, i had rooted it. But today i received a notification about system update, so i tried to get the update. I had referred to another forum by google search telling me to wipe dalvik cashe and wipe system under my twrp in order to get my system update.
but once i wipe it both, i try to reboot my device. it shows that i have no OS anymore......but i just press reboot anyway... then when rebooting my htc butterfly just shows the bootscreen with HTC LOGO and it never run again!!! PLEASE help me how to fix it .... i am freaking nervous right now!!! i just bought my phone a fews day ago!!!
to update ota you need stock recovery
inchigo said:
HELP!!! i bought my htc butterfly 4days ago, i had rooted it. But today i received a notification about system update, so i tried to get the update. I had referred to another forum by google search telling me to wipe dalvik cashe and wipe system under my twrp in order to get my system update.
but once i wipe it both, i try to reboot my device. it shows that i have no OS anymore......but i just press reboot anyway... then when rebooting my htc butterfly just shows the bootscreen with HTC LOGO and it never run again!!! PLEASE help me how to fix it .... i am freaking nervous right now!!! i just bought my phone a fews day ago!!!
Click to expand...
Click to collapse
to update ota you need stock recovery.(just a simple update does not need to relock bootloader)
after the update you can flash a custom recovery
heobanhki said:
to update ota you need stock recovery.(just a simple update does not need to relock bootloader)
after the update you can flash a custom recovery
Click to expand...
Click to collapse
but how to stock recovery in twrp???i am a idiot of android..
inchigo said:
but how to stock recovery in twrp???i am a idiot of android..
Click to expand...
Click to collapse
1. / To your butterfly on fast boot (hold down vol- and power button)
2. / Do flash stock reocvery
Do command [Fastboot flash recovery dlxub1_recovery_X920d.img] (for example dlxub1_recovery_X920d.img is name stock recovery)
3. / Clean cache
Do command [Fastboot erase cache]
4. / Butterfly reboot and update ota
* Your butterfly have stock rom prerequisite to update ota
* Stock recovery HTC Butterfly X920D
https://www.dropbox.com/s/zp2ds59ar18huli/dlxub1_recovery_X920d.img
cant la when i type fastboot flash recovery dlxub1_recovery_X920d.img
the command prompt shows : 'fastboot' is not recognized as an internal or external command,
operable program or batch file.
how???help me please
FINALLY i GOT WHAT U meant
thanks!!!:good::good::good:
but i lost my twrp recovery after the ota update..how can i retain it back????
and there is another newbie question for me :
how to update root????
inchigo said:
FINALLY i GOT WHAT U meant
thanks!!!:good::good::good:
but i lost my twrp recovery after the ota update..how can i retain it back????
and there is another newbie question for me :
how to update root????
Click to expand...
Click to collapse
the same way you did with the stock recovery, but with TWRP recovery img
after your have TWRP recovery you can flash SuperSu through it
* perform after you have unlockbootloader
My link collection -but it was there a few updates to the newer version, please check it on the forum :
https://www.dropbox.com/s/cv33kv0isc6lcup/recovery_TWRP.img?m
https://www.dropbox.com/s/2476ug0cqe3ukbx/SuperSU.zip?m
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)
[Edit] I've a backup saved on the pc, how can i restore that backup? (it was a backup of CM11) shall I zip the whole folder with the img files or shall I copy the whole folder into the phone?
I've tried both but when I choose "restore" from the TWRP nothing shows up
Hi all,
some months ago I've flashed the kitkat 4.2 rom successfully.
Yesterday I've got the message that a system update was available, (kit kat 4.4 the latest one)
I've downloaded it, then the phone rebooted to itself loading the TWRP recovery page therefore not installing the update.
I am now stuck and I don't know what to do.
- If from the TWRP menu I choose to reboot the phone, it loads fine but after a minute it reboot itself trying to install the OTA, rebooting again to TWRP menu
- I've tried to flash the OTA via TWRP from the cache folder but it fails.
Can you help me please?
Andrea :crying:
.
You can apply OTA patch only with full stock (also stock recovery, etc.)
To return to stock, read this thread.
crazypixel said:
[Edit] I've a backup saved on the pc, how can i restore that backup? (it was a backup of CM11) shall I zip the whole folder with the img files or shall I copy the whole folder into the phone?
I've tried both but when I choose "restore" from the TWRP nothing shows up
Hi all,
some months ago I've flashed the kitkat 4.2 rom successfully.
Yesterday I've got the message that a system update was available, (kit kat 4.4 the latest one)
I've downloaded it, then the phone rebooted to itself loading the TWRP recovery page therefore not installing the update.
I am now stuck and I don't know what to do.
- If from the TWRP menu I choose to reboot the phone, it loads fine but after a minute it reboot itself trying to install the OTA, rebooting again to TWRP menu
- I've tried to flash the OTA via TWRP from the cache folder but it fails.
Can you help me please?
Andrea :crying:
.
Click to expand...
Click to collapse
Hi Andrea,
I got the same issue.
You can go into TWRP, then wipe the dalvik/cache and cache partitions (about 4 secs).
then reboot your phone, it will update all your app again but you should be fine.
Hope that helps.
Arsgb said:
You can apply OTA patch only with full stock (also stock recovery, etc.)
To return to stock, read this thread.
Click to expand...
Click to collapse
Hi,
I forgot to mention that it was the stock rom,
how can I apply the ota patch only?
Thanks
mhaxor said:
Hi Andrea,
I got the same issue.
You can go into TWRP, then wipe the dalvik/cache and cache partitions (about 4 secs).
then reboot your phone, it will update all your app again but you should be fine.
Hope that helps.
Click to expand...
Click to collapse
Hi, it worked, thank you very much indeed
hi everyone, good to finally sign up after being a long time reader here, unfortunately I have a problem.
My htc one s is rooted and I am running twrp and wanted to install the latest cm nightly so I downloaded it, googled instructions and used these instructions from a website.
Steps to Install Android 5.0.2 Lollipop on HTC One S via Official CyanogenMod 12 Nightly ROM
Boot into Recovery mode via adb or hardware buttons or use the QuickBoot app if your device is rooted.
In recovery mode, back up data on your current ROM. If using TWRP, select Backup and perform a Swipe to Back Up from the bottom of the screen.
Then select Wipe and do a Swipe to Factory Reset from the bottom of the screen.
Return to the main menu of TWRP recovery and select Install (if using CWM then choose Install Zip from SDcard.
Browse to the file where you saved the CM12 ROM zip file, select it and Swipe to Confirm Flash on the bottom of the screen. Now, wait until the flashing process completes.
After the ROM is flashed, repeat step 8 to flash the Gapps package as well.
Once both the files are flashed, return to recovery's Main menu and select Reboot > System.
I did all that and it installed fine, however, when I restarted the phone, it showed the htc logo then it just went black so I had to go back into twrp.
Instead I changed my mind and tried to install 4.1.1. jelly bean (since I needed to update anyways and couldn't because I'm running twrp and in that whole process I ended up deleting the version of jellybean and basically my phone has no jellybean or lollipop installed at all so my only option is going back into twrp.
After that, I read that my phone has to be S-off so I looked up instructions on how to install it (I'm on a mac) and apparently I'm supposed to flash the boot.img (kernel) via fast boot but in order to do that you need to have jellybean or some kind of rom running to have debugging mode on and I don't so basically this is where I'm stuck.
My apologies for the lengthy explanation but if anyone knows what to do from here that would be amazing thanks.
So I sort of forgot I had rooted my phone and an update to Android 6.0.1 came along so I thought why not?
The problem is that when I tried to update it put me into TWRP recovery mode (a custom recovery) and nothing else happens.
Now whenever I start my phone it automatically reboots to try and update but it just goes back to recovery again and nothing happens,
What's the best course of action?
SUBJUGATOR said:
So I sort of forgot I had rooted my phone and an update to Android 6.0.1 came along so I thought why not?
The problem is that when I tried to update it put me into TWRP recovery mode (a custom recovery) and nothing else happens.
Now whenever I start my phone it automatically reboots to try and update but it just goes back to recovery again and nothing happens,
What's the best course of action?
Click to expand...
Click to collapse
As far as I know, if your phone is rooted then before installing the update phone checks whether it is modified or not. If it is modified (rooted) then it won't install the update.
The best course of action will be reflashing the stock rom and unrooting your device. After updating the device to Marshmallow, root it again. Use titanium backup for apps if neccessary.
SUBJUGATOR said:
So I sort of forgot I had rooted my phone and an update to Android 6.0.1 came along so I thought why not?
The problem is that when I tried to update it put me into TWRP recovery mode (a custom recovery) and nothing else happens.
Now whenever I start my phone it automatically reboots to try and update but it just goes back to recovery again and nothing happens,
What's the best course of action?
Click to expand...
Click to collapse
If you are rooted, you surely have a TWRP backup. Just re-flash your latest backup.
Unroot through your superSU app and flash only the stock recovery. It won't wipe your data