If I try to update Clockwork Recovery on my Nexus S to anything newer than 3.0.0 (using Rom Manager), the phone will not boot into recovery and stays in fastboot mode instead. However, if I reboot and flash back to 3.0.0 then recovery mode works fine. Not a big deal, just curious what the problem is that's preventing me from using the newer versions of Clockwork.
Thanks.
i had a similiar problem with rom manager, i reinstalled clockwork with fastboot on your computure, worked for me.then reinstalled rom manager. I am currently using clockworkmod 3.0.2.4.
Related
Hi,
I got my Huawei U8150 two days ago and I rooted it with z4root . Then I wanted to backup the original ROM before removing some stock apps.
So I installed ROM Mgr 2.5.1.2 and flashed the ClockworkMod recovery 2.5.0.1. When I tried to backup my current ROM, I rebooted to a black screen .
Eventually I found the 1.8.1.4 recovery image should be used in another forum .
Question => How to reflash 2.5.0.1 with 1.8.1.4? I tried in ROM Mgr but got an error.
Many thanks in advance.
Same Problem
Did you find any solution. I also flashed clockworkmod version 2.5.0.7 using Huawei pulse mini option. ROM Manager v3.0.0.7
Now when I go to recovery mode my phone has black screen. No recovery screen.
Please respond how to get my stock recovery back
Flash a stock Ideos Rom. Its recovery will replace yours
Sent from my DJDroid Ideos v0.4 using XDA App
Dear eidolon88.
Thanks for your prompt response. You people are really great. I have found stock ROM on xdadevelopers wiki website.
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS#Official_ROMs
Is this right?
And can you recommend the guide for flashing ROM. Because I don't have access to Recovery menu.
OK. I'm stuck too. I just installed RomManager v3.0.0.9 with ClockWorkMod v2.5.0.7 for Pulse Mini. Now I cannot boot into recovery. Recovery boot just shows a T-Mobile Logo. Actually, I was making a mistake here and booting into the bootloader. When I booted correctly into recovery I got a black screen. I receive an error when I try to install anything under All CWM Recoveries. So far the phone still boots normally.
If I could locate a working CWM version then I could use the following hack to force install it.
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
Anyone know of a working ClockWorkMod version for the U8150?
Update:
I found a fix by installing the modified Koush's Clockwork Recovery 1.8.1.4 for Pulse Mini via Linux Terminal and ADB here:
http://android.modaco.com/content/t...lling-a-custom-recovery-image-on-your-device/
Now I can boot from RomManager v3.0.0.9 into ClockWorkMod v1.8.1.4 or boot into recovery via 'vol up + green send + power' even though RomManager says CWM is v2.5.0.7.
Update:
Using the setup in the previous update I was able to successfully backup the current ROM with apps and data to SD using RomManager v3.0.0.9 and ClockWorkMod 1.8.1.4.
Just flashed ClockwordMod Recovery 3.0.0.8 over 3.0.0.5 to my HTC Incredible... when rebooting to Recovery it loads the bootloader instead and does not give an option for recovery. So I rebooted (CyanogenMod, by the way) and re-flashed older versions until it cleared up... finally went back to 3.0.0.5 to get Recovery to show up in the bootloader again.
Has anyone else experienced this after flashing the latest ClockwordMod Recovery?
Hi Guys,
I have installed paranoid android cm10 last night. I was good but gmail was force closing, so I tried to install latest version thru goo manager app. I have installed recovery which it told me to get it but once i reboot my phone into recovery its no more moving a head. all I see is teamwin wallpaper and system reboots... any help is greatly appreciated.
Thanks
/bin/ said:
Hi Guys,
I have installed paranoid android cm10 last night. I was good but gmail was force closing, so I tried to install latest version thru goo manager app. I have installed recovery which it told me to get it but once i reboot my phone into recovery its no more moving a head. all I see is teamwin wallpaper and system reboots... any help is greatly appreciated.
Thanks
Click to expand...
Click to collapse
It probably didn't flash a kexec recovery. Just boot into recovery and flash a non kexec ROM ...hopefully you have one sitting on your SD card. If not your have to get one there or dd a kexec recovery with adb and reboot with the ROM you currently have installed
I guess he can't even get into recovery, as he said all he sees is wallpaper. He used TWRP recovery, which is NOT Kexec enabled. In order to flash CM, you needed to flash CWM 6.0.1.0. Now, basically your only choice is to either adb the cwm recovery, or just reflash stock using odin (easier option), flash cwm, then reinstall CM.
Vorfidus said:
I guess he can't even get into recovery, as he said all he sees is wallpaper. He used TWRP recovery, which is NOT Kexec enabled. In order to flash CM, you needed to flash CWM 6.0.1.0. Now, basically your only choice is to either adb the cwm recovery, or just reflash stock using odin (easier option), flash cwm, then reinstall CM.
Click to expand...
Click to collapse
It's odd his recovery won't open I wonder if goo flashed the incorrect version.
All,
I'm rooted and unlocked. The weirdest thing I'm experiencing is that in both the EZ Recovery and Rom Manager, when I select to reboot into recovery, I'm not booting into ClockworkMod. I'm booting into stock recovery I think. The only time it would boot into ClockwordMod is when I flash touch clockwork mod then it would boot into the correct recovery.
Do I need to flash the Touch ClockworkMod every time I want to boot into recovery? Thats annoying.
Please help.
Thanks!
If you boot into stock recovery by selecting reboot recovery then CWM is simply not installed. Are you selecting the correct option in ez recovery to install the recovery?
I'm good now. I was on stock, but was rooted and unlocked. Like I said, it would work if I flash the recovery, but if I reboot into recovery again without flashing it would go back to stock recovery.
Anyways, I've flashed to CleanRom 4.0 and tested rebooting into recovery and sure enough it went to the ClockworkMod Recovery. So looks like I"m good.
It will do that on stock rom unless a couple of files are modified I believe. Doesn't do it on custom roms.
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!