Database Info

[Q] Clockworkmod Recovery may be corrupted.

I have a T-mobile G2 android phone. I recently rooted the phone. Installed different roms, and attempted to install a different rom. Currently have ClockworkMod Recovery v2.5.1.3 installed. After restarting phone, if I don't load the ClockworkMod, the phone will freeze at the "HTC" screen. I can get into the Bootloader or into the ClockworkMod, but cannot get beyond that. What's the easiest thing to do in this situation?

Wipe data and cache and reflash either your ROM, or a Nand backup. That happened to me trying to ROM my Nook Color's emmc. If wiping data and cache doesn't help, you'll need to format data, cache, boot, and system and reflash. (Hopefully you've backed up)
Note: It's most likely your boot that's a little wonky, not CWM. IMHO CWM is one of the best things to ever happen to us Droid geeks

Ok honestly, Clockwork doesn't work on my Dream 32a. It doesn't boot up into the recovery. It's not compatible with some phones. Hopefully you did a nand backup..

I didn't do NAND backup. Is there an alternative.

Reflash whatever ROM you want, but format the 4 listed above. It's your boot that's messed up, so overwriting it with another one will confuse it... My nook boot-looped for about two weeks straight when I first tried installing to it's internal memory. I just stuck to it and read the forums over and over and never lost hope or gave up.
Sent from my ADR6300 using XDA Premium App

[Q] A little help ... STUCK !!

My phone G2X wasn't working at all, I've managed to get it into Recovery (by using the One Click flasher) and have then since loaded a CM7 Nightly on it. Everything goes ok until it gets to the little "Touch the Android to begin" and there the Google DRM process dies and I can't go further. I can by using the status bar get to wireless and such. But that's it.
Help!?

You try installing the rom again?
Sent from my LG-P999 using xda premium

Try doing a FULL wipe.
Boot into recovery, and select "Mounts and Storage".
From there, format /data, /system, and /cache.
After that. Wipe Dalvik-Cache, and reinstall your ROM. Be sure to Fix Permissions before you boot into the ROM.
After that's done, boot into the ROM, and perform a Factory Data Reset... At least, that's what I do, and I've never had an issue with installing ROMs. It's a long process, but works flawlessly.

[Q] Help needed - stuck on CM10 boot-up animation

Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie

maybe yall need to "fastboot flash boot boot.img" now

robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.

Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!

[Q] Is my Nexus 5 damaged?

So, firstly I'd like to explain a bit about my device.
It's currently Rooted, has CWM installed and it's on Cataclysm Rom.
When in recovery mode, it usually takes longer than it used to when clearing the cache. It takes 4 mins???
When in recovery I install roms for this device, they usually don't work. I wipe data/cache. and install the .zip.
It boots, sometimes it doesn't. Sometimes it loops.
Then when restoring the backup I had made. I boot into recovery mode, and go in restore backup it says. E: Cannot mount Storage.
I leave the Nexus for a day whilst switched off, then go into recovery it mounts storage... Sometimes it doesn't detect it, sometimes it doesn't.
So my question is, is my phone damaged in any way?.

Try twrp
Sent from my Nexus 5 using Tapatalk

Yeah try twrp, I haven't had any issues with it..
Sent from my Nexus 5 using xda app-developers app

If you want the CWM UI, go for Philz Touch!

KrishXDA said:
So, firstly I'd like to explain a bit about my device.
It's currently Rooted, has CWM installed and it's on Cataclysm Rom.
When in recovery mode, it usually takes longer than it used to when clearing the cache. It takes 4 mins???
When in recovery I install roms for this device, they usually don't work. I wipe data/cache. and install the .zip.
It boots, sometimes it doesn't. Sometimes it loops.
Then when restoring the backup I had made. I boot into recovery mode, and go in restore backup it says. E: Cannot mount Storage.
I leave the Nexus for a day whilst switched off, then go into recovery it mounts storage... Sometimes it doesn't detect it, sometimes it doesn't.
So my question is, is my phone damaged in any way?.
Click to expand...
Click to collapse
Nopes it is not damaged
Just reflash the latest zip recovery of recovery and try again
Sent from my Nexus 5 using Tapatalk

Maybe your partitions are screwed up somehow. If you keep having issues, grab all your stuff off your internal SD and back it up one of the times it does boot, then use the factory image from Google to flash back to 100% stock. Factory reset in stock, then redo everything from scratch and try using TWRP. A hint to, in TWRP in settings check "Use rm -f instead of format". Tends to give me less issues.

[Q] Boot loop problem after restore to stock 2.3.5 backup from custom ROM 4.3.1

Hi,
First time posting Reasonably Nooby...-ish to hacking around with android but pretty techy in general and have done a lot of reading to try and fix this myself before posting.
Setup: HTC Desire S, ClockworkMod ver 5.8.1.5, HBOOT 2.00.0002 S-ON Unlocked bootloader
I have been running the stock firmware Gingerbread 2.3.5 from new (rooted by me) running CWM Recovery ver 5.8.1.5. I took out my SD card and put a blank one in (possibly stupidly, didn't re-format first), I took a nandroid backup of the phone. Rebooted then changed a few phone settings/apps and restored the backup to test it was okay, and it worked fine.
I then flashed a custom rom (Carbon_4.3.1_1114_saga.zip) and (gapps-jb-20130813-signed.zip) from the same sd card, cleared all cache, dalvik, data etc which boots and works fine except that I have major issues with the sound in that it doesnt ring, no notification sounds and terrible in call audio, so have restored my backup through CWM.
As soon as I restored my backup and reboot, the phone goes into a boot loop where by it tries to boot showing the white HTC screen, the screen then goes black it then boots into ClockworkMod Restore. I tried clearing all data, cache, dalvik cache but it made no difference. I have tried a number of things including;
I then tried flashing boot.img to the phone from my nandroid backup in fastboot but again that made no difference.
I read through and followed the boot loop post on here but that made no differnce either.
I tried copying all data off sd card, formatting (through windows) and copying data back, no difference (more of a desperation attempt).
I can flash the custom ROM back to the phone and it boots again into that rom fine
One thing to note which may or may not have anything to do with this at all, is that when I originally wiped the dalvik cache before installing the custom ROM: from my memory, it did so with no errors. Now as soon as I select wipe Dalvik cache in CWM before even confirming to wipe, I get an error: "E:unknown volume for path [/sd-ext]", however when I do a "wipe data/factory reset" in CWM it shows it wipes /sd-ext. (this part is something I have not much knowledge on).
I cant help thinking theres something I've missed or can do that will get this to suddenly boot. Any help would be really appreciated as I've put a lot of hours/late nights into this so far and would now really like a fully working phone back.
As a side note; I believe from reading, putting a stock RUU update back on will solve the problem but after devoting a lot of hours trying to find one for my phone, I've not had much luck as nothing on HTCdev any more and cant find one for UK on Orange (now EE). And a lot of old links are now dead. As a side question does it have to be the firmware that my carrier sent out exactly for my country, I've read you can extract the rom.zip file from the RUU.exe so could I flash one that is world wide or a uk from another network provider or my network provider from another country, and then restore my backup to my own one, would that actually work/make any difference or just fail?
Thanks for any help