Root Stuck on Clockworkmod Recovery!!

I am having the same issues at Erik917. I followed all the steps of unlocking the bootloader, putting on CWM, and then once I backed up my phone and restarted I am stuck in the CWM.

I tried restoring to the file I had just created but it does nothing but put me back in CWM.

What do I need to do??????!!!!!!!!!!! God this is so frustrating. My HTC G2 gave me nothing but problems and had to give up on that, now I finally decided to try this with my HTC One S ville and this. fml

I notice that my phone stuck in CWM wont allow the USB mount but if I selecte mount SD Card it will appear to work but on my Win7 PC I do not hear any notification or see any new drives popup in My Computer....AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHh

OH SNAP! Held the power button for 10 seconds and it got me out of CWM!!!! HURRAY!!!!!

Now I'm going to see if I can get my Win7 machine to recognize the phone as a drive and that way I can load a ROM.

Ive been having a very similar issue. I cant for anything access the hboot screen, tried auto boot into the button hold down nothing. still stuck in cw. I noticed that a green line flashes whenever the device is restarted but the screen stays black and then goin into recovery. I was able to install a rom but from what i could tell it didn't change anything

just to be sure were on the same page, selecting the reboot system in recovery just takes you back to recovery?

have you tried accessing hboot/fastboot in this manner:
hold power for 10 seconds. the phone should power off,and try and reboot. when it starts rebooting,let go of the power button . it may boot,or it may hang at a splash screen. if it boots,then hooray! :smokingsomb:

if not, then hold power again till the phone shuts off. this time,hold volume down as well,and keep holding them both until hboot appears.

failing that,do you have adb/fastboot set up? if so,plug in the phone,in recovery,open a cmd window,and try:
adb devices

if youre in your adb/fastboot folder,and drivers are working correctly,you should get back "htcxxxxxxxx recovery"

if you get the proper response,then try:
"adb reboot bootloader" and that should take you to fastboot.

if you can get to fastboot,you can try flashing the boot image from the rom that you tried to install. might not hurt to go back to recovery and do a full wipe afterward,and install the rom again. now try and reboot the phone.

alternately to flashing a new rom and boot image,you could restore a stock backup,or flash a stock rom. if your phone is not booting due to an imcompatible kernel,then restoring or flashing a compaitble rom to your current kernel bay allow it to boot.

scotty85 said:

just to be sure were on the same page, selecting the reboot system in recovery just takes you back to recovery?

have you tried accessing hboot/fastboot in this manner:
hold power for 10 seconds. the phone should power off,and try and reboot. when it starts rebooting,let go of the power button . it may boot,or it may hang at a splash screen. if it boots,then hooray! :smokingsomb:

if not, then hold power again till the phone shuts off. this time,hold volume down as well,and keep holding them both until hboot appears.

failing that,do you have adb/fastboot set up? if so,plug in the phone,in recovery,open a cmd window,and try:
adb devices

if youre in your adb/fastboot folder,and drivers are working correctly,you should get back "htcxxxxxxxx recovery"

if you get the proper response,then try:
"adb reboot bootloader" and that should take you to fastboot.

if you can get to fastboot,you can try flashing the boot image from the rom that you tried to install. might not hurt to go back to recovery and do a full wipe afterward,and install the rom again. now try and reboot the phone.

alternately to flashing a new rom and boot image,you could restore a stock backup,or flash a stock rom. if your phone is not booting due to an imcompatible kernel,then restoring or flashing a compaitble rom to your current kernel bay allow it to boot.

Click to expand...

adb detects my phone and it says its in recovery but if i type to get to the bootloader it just turns off then boots back into recovery. i never get a splash screen or anything just black and 2 or 3 times and green line flashes across the screen

i cant quite think of another way to get into hboot to do anything

Jayster06 said:

i cant quite think of another way to get into hboot to do anything

Click to expand...

unfortunately,i cannot either... im not 100% sure if there is a hardware issue with your phone,or if the prollem is this recovery.

if you could do a couple things for us,it may help think of a solution:
put the phone in recovery,open cmd,then:

adb devices

then
cat /proc/emmc

and copy/paste that output here

then
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3

exit

adb pull /sdcard/mmcblk0p3


that should put a file or image on into your adb/fastboot folder. if you can upload this image and pm me a link,or email it to me,there may be a couple things we can try.

one other thing comes to mind... if you select a power off from recovery option,does the phone turn off? if so you might leave it off a couple hours,then hold power with it off,and see if that triggers the hard reset. you could also try power/vol down from powered off.

Here is the output i get. I dont think im doing something right

""Android Debug Bridge version 1.0.29

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)

adb restore <file> - restore device contents from the <file> backup
archive

adb help - show this help message
adb version - show version num

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.""

scotty85 said:

one other thing comes to mind... if you select a power off from recovery option,does the phone turn off? if so you might leave it off a couple hours,then hold power with it off,and see if that triggers the hard reset. you could also try power/vol down from powered off.

Click to expand...

i cant find just a shutdown option and if i hold or push the power button it resets and goes back to recovery

Jayster06 said:

Here is the output i get. I dont think im doing something right

Click to expand...

yuo are correct,thats not the output we were looking for

make sure your prompt changes to # when you enter
adb shell

then copy/paste the line to make sure the spacing and such is correct

it should look something like this:


if any of ya see where im going with this,feel free to take over... i wont be home till about 9:00 this evening

ok i got this now when i ran it. Sorry i am really bad at programming.

dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"


here is that file you requested as well:
http://dl.dropbox.com/u/80123914/mmcblk0p3

first of all,sorry for the delayed reply... i was going to have you attempt to re-write your recovery from recovery,but its been a busy couple days and i havent had a chance to research and find a different image,since i dont own one of these(yet )

but since you sent a pm that you got to hboot somehow,sounds like youre somewhat out of the woods. please try and recall how you got to hboot,and then describe what you did once you got there.

now for your other question(hope you dont mind i bring it here):

Jayster06 said:

i was finally able to get to hboot somehow i dont know what i did. i got viper installed but foujnd out wifi will not work. i came across this thread and is there any easier way to explain and do this: http://forum.xda-developers.com/showthread.php?t=1990043

Click to expand...

no,not really. im not very proficient in lunux,wich is an important aspect of that. you cant do it with windows. are you wanting to downgrade? i would prolly recomend against that unless your very good with linux and manipulating your phone with it. otherwise wait until they come out with a live cd/tool that automates it all... and even then its a risky operation. understand that you are casuing a pretty hardcore soft brick with that process,and it is possible you might not be able to recover from it.

first thing i would do is replace CW with twrp,ext 4,or some other recovery that is available for your phone.

second,your wifi is likely not working due to a simple kernel/module mismatch. you prolly need to simply flash the roms boot image,and then reflash the rom with a cache/dalvik wipe.

*change recovery
-put viper boot image into folder with adb/fastboot
-open cmd window,plug in phone
-boot to recovery. wipe cache/dalvik. reflash rom
-boot to fastboot. most recoveries have an option to boot to bootloader. alternately,you can adb reboot bootloader in a cmd window.
-flash boot image with this command:
fastboot flash boot bootimagename.img
i.e.,if its named "boot" then the command is:
fastboot flash boot boot.img
-you should see very fast status bars on the phone,and then an 'ok' in the cmd window when its done. at thit point you can reboot with:
fastboot reboot

that should sort your wifi. if not,try again with a full wipe(cache,dalvik,data/factory reset). if it still doesnt work,try the above process again,but with a different rom and a full wipe.

again,sorry for the delay,i wasnt intentionally letting you hang

agentc13 said:

Hold power + Volume down until it shuts off, then hold them both down again and you should be on the hboot screen. From there you can select Fastboot, then Reboot (Use volume to go up and down, and Power to select). I have had mine get stuck in recovery and that has fixed it for me.

If you did a factory reset via CWM you won't have an OS to boot to though, so you will need to flash something else via recovery. You can mount the sd card via recovery like sdrawkcab25 was mentioning.

I would recommend flashing TWRP2 recovery, while in fastboot (like you did for CWM) the specific instructions are here: http://androidforums.com/one-s-all-things-root/543328-how-unlock-bootloader-install-recovery-root-your-htc-one-s.html#post4777154. Then you need to flash a ROM if you wiped your previous one.

Click to expand...

You have saved my life!

coolj7 said:

You have saved my life!

Click to expand...

Ha! Mine too! Thank you so much agentc13 for this I was about to go crazy!

Installing goomanager from the market on my Ville fixed my issue with being stuck on CWM screen ever time I turned my phone on.


download goo manager and install twrp thru its menu.

I had the same problem, but I got it fixed after a long research, I did the same way with coolj7.I Tried to hold down both power button and down button at the same time, kepting hold down until it go back to boot loader page. At this point, I went back to my computer and flashed back a newest recovery twrp, my is twrp 2.7.[fastboot flash recovery openrecovery-twrp-2.7. .
Then I got out of it and went to installed a new ROM.I think recovery cwm 6.0.2. has bugs. That why so many people get stuck with the boot loop

i know how to fix it.
You need:
micro usb to usb slot adapter
flash drive

1.load rom+gapps(if needed)to flash drive
2.put into adapter then into phone
3.go to mounts+storage
4.mount usb storage
5.flash rom from flash drive

its no very complicated so it should work easily