Develop Bugs

How do I flash a ClockworkMod recovery image via ADB?

I installed the latest CM6 nightly, but I kept getting bootloops. I figured I'd restore my nandroid, but I needed to flash ClockworkMod recovery to get it to work. I went in ROM Manager, told it to flash the recovery, got confirmation that it worked, but when I reboot it only goes to fastboot. I tried flashing AmonRA again, but it doesn't stick either. Please help me remedy this!
Edit: I was finally able to restore using ROM Manager. I just had to delete the /system one and restore it using Titanium Backup before it would flash. Delete this.

[Q] ClockworkMod and ROM Manager

I have a ROM Manager Premium license, which is still telling me that ClockworkMod 2.5.0.7 is the current version. However I've found from the Desire Index in the Dev forum that the latest is 3.0.0.5. I'm running the AlphaRev S-OFF bootloader so I've used fastboot to flash the latest recovery to my recovery partition.
If I boot into recovery manually then all is well and good, I get 3.0.0.5. But if I use ROM Manager to either boot into recovery, or to take a Nandroid backup, then this happens using 2.5.0.7 (I assume the phone must boot into the 3.0.0.5 from the recovery partition, and then fake-flash 2.5.0.7 from the update.zip). However I've deleted the update.zip from my SD card so where is 2.5.0.7 coming from?!
I have two questions regarding this:
1) Is it possible to make it so that ROM Manager doesn't fake-flash, and just uses the recovery system which is already in place on my recovery partition?
2) If not, should I be concerned that my backups are being taken with 2.5.0.7, but if I ever had to restore one then I'd have to use 3.0.0.5 as that's what's on the recovery mode and if I can't boot into ROM Manager I can't fake-flash 2.5.0.7 to restore?
Cheers!

I've read yesterday another topic, because I also wanted to update mij Clockwork.
What I've read was that the update.zip in the recovery mode is only for the time you are in recovery mode. If you boot and come back later into Recovery mode then it's the old version again.
You have to Root again, because only then the new version will be Flashed on your phone.
I'm not the expert, but I would be surprised if you can not restore a backup with a newer Clockwork version later on.
Good Luck

[Q]Bootloop into recovery

So after i flashed a rom on my P5200 i always bootloop to TWRP
and i tried to wipe all data but no use
so please someone help me
oh and i can access download mode

TWRP causes problems...at least it did mine.. Restore the backup (hopefully you made one) with TWRP and flash a different recovery, like clockwork mod (CWM).

ReeceWyld said:
TWRP causes problems...at least it did mine.. Restore the backup (hopefully you made one) with TWRP and flash a different recovery, like clockwork mod (CWM).
Click to expand...
Click to collapse
i did not do a backup !!!
what should i do?

Power it off completely boot up in Download mode. Then connect it to the PC and use Odin to flash CWM on it.
For future reference, always make a backup before you do ANYTHING.

Secure booting error after flashins backup

hello guys i got twrp 2.8.4.0 bumped to the phone but when i try to restore my backup after it flashes it pops up saying secure boot error boot certification verify
and when trying to flash any other roms twrp is saying zip is corrupt,can anyone help me?,ive tried flashing it stock to 10b with no luck

Boot loop issue

Hey guys, I just recently got some parts for my old One X to start playing with it again (bored with ios). I was running an older version of ViperXL and wanted to get lollipop so my goal was to put CM12.0 on my phone. My recovery was twrp but a version that was older so I had to update it. The in app update wasn't working so I updated cwm instead. When I did this I tried to boot to recovery and it would attempt to go to recovery but then boot back to the os.
Then I was trying to flash the recovery using fastboot which resulted in the same problem. Somewhere in there I flash the recovery.img as my boot image (sudo fastboot flash boot recovery.img) This made my phone repeatedly try to boot into recovery. I tried flashing new ViperXL boot.img as well as a couple others but none let me get into my os again. Now it is just a bootloop trying to start my phone up.
When I try flashing a .zip I get the error 'FAILED (remote: not allowed)'. Flashing recovery and boot images work though.
I've tried a lot and done a lot of searching but nothing can get me into recovery or even out of any sort of bootloop.
I'm using Ubuntu and my phone is S-On if that means anything.
Thanks!

Try restoring any backups of old roms from the recovery. Make sure Recovery is written properly in recovery partition. If this works fine , the appropriate boot.img shud be automatically flashed , i guess.
If u dont have a backup , try finding another one x user using a custom recovery, create a backup from his mobile and copy it to ur sd card by mounting it thru recovery and restore it.
If it doesnt work , wipe all the partitions - System , cache, boot and recovery.. then try flashing a Recovery and then a Boot.img and a rom.
I havent faced such a situation. Just my suggestions as no experts have responded.
Cheers if u have already sorted it out !!!