Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I have a Nexus S which sadly has a broken power button. This means I cannot do anything in recovery mode. Recently, after downgrading from a Cyanogenmod 10.1 nightly to and experimental build, it got stuck in a boot-loop.

I am trying to install ClockworkMod Touch, I think this would probably be the fastest (and most permanent) option. I have an .img file, but also a flashable .zip file for ClockWorkMod Touch.

The problem is, I am unable to either flash the .zip, or install the .img, because my PC doesn't detect a device in fast-boot mode.

Does anyone know how to install the zip using ADB, with commands that are available through either regular boot or recovery mode?

I could also try and send keystrokes for the power button through ADB but this wouldn't work in recovery.

Thanks for the help in advance!

Update: The phone wont go into Fastboot-usb mode, I dont know why. (I am not using the original USB cable)

Update 2: I managed to fix the bootloop by reinstalling the ROM using

    adb shell
    recovery --update_package=/sdcard/cmupdater/cm-10.1-20130121-EXPERIMENTAL-crespo-M1.zip

Still would like to know how to install CWM touch.

share|improve this question
    
Can you please tell me how were you able to push the ROM without getting into fastboot? I'm stuck in the same situation and I'm getting a device not found error when i try the adb shell command. –  user29036 Feb 24 '13 at 19:01
add comment

1 Answer

Check this out. It's a step-by-step guide on how to load a rom with fastboot. Maybe it helps.

Also, additional info can be found on xda forums.

share|improve this answer
1  
Thanks for your response, but the problem is my PC doesn't detect my phone while in fastboot mode, so i can't send any commands. –  Hihaatje Feb 19 '13 at 20:35
    
Take a look at Universal naked driver. Might help. Please read the thread before doing anything. –  yohlulz Feb 19 '13 at 20:48
1  
The universal naked driver is just a repacked adb drivers, which is pointless because it got stuck in a boot-loop which is defeating your answer! –  t0mm13b Feb 19 '13 at 21:18
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.