I was installing revolver 4 rom and my restore wasn't working I was using titanium back up pro it was saying something bout su and to reboot and I did like a few times so I reinstall the rom and now I can't get out of recovery when I reboot it takes me right back I tried installing a new recovery and it still on this recovery the recovery am using is clockwork mod v5.5.0.4 I need help can some one help me
the thing about titanium backup does not matter you can just skip past it or hit cancle it works either way. the official CWM 5.xxx by Kouch is bugged and does not work. use team rouge's recovery it is also based on 5.xxx but it works.
baconspaceman said:
I was installing revolver 4 rom and my restore wasn't working I was using titanium back up pro it was saying something bout su and to reboot and I did like a few times so I reinstall the rom and now I can't get out of recovery when I reboot it takes me right back I tried installing a new recovery and it still on this recovery the recovery am using is clockwork mod v5.5.0.4 I need help can some one help me
Click to expand...
Click to collapse
You need to go here to solve your recovery boot loop problem.
http://forum.xda-developers.com/showthread.php?p=23256536
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
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)
Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.
Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.
O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs
Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!
Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.