Database Info

soft brick, no recovery...

Hello. I am new to this forum so bare with me lol. Recently I rooted my G1 using the following guide.
http ://forum.xda-developers. com/showthread.php?t=727688
Everything was working perfect. I went to Rom Manager app and updated recovery image and my phone was rebooting fine. Today I could not send text messages so I rebooted my phone and it gets stuck on G1 screen. Home+power doesnt work but camera+power works. What can I do?? I searched for 3 hours already and I only read that people fixed it but no one gave step by step instructions

radekkacz07 said:
Hello. I am new to this forum so bare with me lol. Recently I rooted my G1 using the following guide.
http ://forum.xda-developers. com/showthread.php?t=727688
Everything was working perfect. I went to Rom Manager app and updated recovery image and my phone was rebooting fine. Today I could not send text messages so I rebooted my phone and it gets stuck on G1 screen. Home+power doesnt work but camera+power works. What can I do?? I searched for 3 hours already and I only read that people fixed it but no one gave step by step instructions
Click to expand...
Click to collapse
Does it only get stuck on the splash screen when you try to boot into recovery? Or does it not boot into the ROM at all?

Same thing
I have the same thing happening to me but there is no ROM. So I am able to get into FASTBOOT but it wont flash anything but I have no ROM or RECOVERY IMAGE

In fastboot you can flash, either download the original RC29 DREAIMG.NBH, or get the fastboot executable on your PC (mostly in PATH in sdk/tools/ with adb) and flash recovery with fastboot:
Code:
fastboot flash recovery recovery.img
In the Cyanogen Wiki there is a link for both recoveries (RA and CWM).

fonix232 said:
In fastboot you can flash, either download the original RC29 DREAIMG.NBH, or get the fastboot executable on your PC (mostly in PATH in sdk/tools/ with adb) and flash recovery with fastboot:
Code:
fastboot flash recovery recovery.img
In the Cyanogen Wiki there is a link for both recoveries (RA and CWM).
Click to expand...
Click to collapse
When I go into fastboot which I suppose is camera+power, I dont have any options to flash. I have 4 options...
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
To clarify, my phone does not boot at all and no recovery.

radekkacz07 said:
When I go into fastboot which I suppose is camera+power, I dont have any options to flash. I have 4 options...
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
To clarify, my phone does not boot at all and no recovery.
Click to expand...
Click to collapse
The fastboot command is entered on the computer , Windows command line for example
http://android-dls.com/wiki/index.php?title=Magic_Rooting
Is good guide to show you the basics, just download a dream recovery instead of sapphire/magic recovery image

radekkacz07 said:
When I go into fastboot which I suppose is camera+power, I dont have any options to flash. I have 4 options...
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
To clarify, my phone does not boot at all and no recovery.
Click to expand...
Click to collapse
Are you able to go through the root process again. Sounds like your only option to me.

I have absolutely no clue how to get the fastboot to load. My adb doesnt turnon on pc nor the fastboot. Im a noob to this stuff.

"Java not found in your path" .

radekkacz07 said:
"Java not found in your path" .
Click to expand...
Click to collapse
You need to have a java jre/jdk within your classpath.
Sent from my Htcclay's Superfly G1 using XDA App

? Im so confused with this lol

There is a Guide for ADB and Fastboot in the Q&A section. Please read there how to set up an appropriate environment.
Sent from my Htcclay's Superfly G1 using XDA App

Thank you for the link but I cant run sdk setup because it doesnt detect my java although I installed it. Also I will not be able to put my phone in debug mode since I cant boot it.

How can I put java in my classpath? could you clarify?

radekkacz07 said:
How can I put java in my classpath? could you clarify?
Click to expand...
Click to collapse
In Linux you have to enter:
export PATH=$JAVA_HOME/bin:$PATH
On the shell, where JAVA_HOME points to the directory where java is installed.
In Windows you have to open your settings, and to find the PATH configuration. There you have to add the bin-Directory of your Java-Installation. But you have to separate by a ';' instead of ':'.
Hope that will help you ...
Sent from my Htcclay's Superfly G1 using XDA App

i am having this same problem.
i can get into the "android system recovery" menu, but i dont know what to do from there...if anything.
nandroid restore gives me an error.
do i need to put the ROM and update ZIPs back on the SD for a restore to work?

rdub202 said:
i am having this same problem.
i can get into the "android system recovery" menu, but i dont know what to do from there...if anything.
nandroid restore gives me an error.
do i need to put the ROM and update ZIPs back on the SD for a restore to work?
Click to expand...
Click to collapse
So you dont have the same problem because you can get into the recovery and I cant...

If anyone lives around chicago land area, I am willing to pay for someone to help me out withthis problem.

there have been a load of issues flashing recovery from within a rom when running CM5 or 6....unfortunately, most of the "clear warnings" are far from that....
if you are having trouble setting up fastboot, have a look at this guide, it may be of benefit to you....you only really need to follow the fastboot instructions (note. the guide is for ubuntu 9.10 and 10.04)
http://www.lineardroid.co.uk/2010/04/how-to-set-up-adb-in-ubuntu/

i have the same problem but when i try to flash a new recovery img i get MTD: a bunch of numbers and it keeps on telling me that i dont have enough memory.. is there anyway i can fix this?

[Q] Frozen on boot screen after 2.3.3

Hi All,
I have a Nexus S with a strange problem. It was originally stock, with no ROM mods at all, I then applied the SU patch get root happening - all worked fine for months.
I then manually applied the 2.3.3 update about 1 week ago. All working fine with no issues.
Today however, i've come to check my phone to find it 'frozen' on the boot screen.
Thinking it was just another lovely OS glitch, I battery pulled, to find it turned into an endless Nexus S boot loop. I booted into recovery, wiped the cache. Same Issue. I Booted into recover a gain, did a factory data reset. Same issue. I booted in recovery again and re-applied the 2.3.3 update which was on my memory from the previous update. Same issue.
The phone seems to either freeze during boot, or go into and endless loop.
Ideas? - The only other thing that i thought would be to do a bootloader unlock to wipe EVERYTHING... but im not sure if its worth it.

Why not? You can lock it back with fastboot oem lock command.

If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.

distortedloop said:
If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Click to expand...
Click to collapse
Sadly, it was a locked bootloader, so had no luck with that
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
distortedloop said:
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
Couldn't get in as i had no ADB access.
In any case, i did a OEM unlock, and still had similar boot issues. The OS would boot, but despite flashing a custom clockwork recovery, it wouldn't get from BootLoad thru to Recovery. It also still had random hangs on boot.
I performed a fastboot flashall and also a fastboot erase boot and recovery. Leaving the phone totally empty.
I then re-loaded a rooted 2.3.3 with latest Clockwork and all worked fine. I've also updated radio to B3 - seems to work flawlessly.
I can only think something was screwy with the boot/recovery sections - very weird but all appears to work fine now.
Many thanks for the help.

g33k84 said:
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
Couldn't get in as i had no ADB access.
Click to expand...
Click to collapse
You don't need recovery access to use adb. We might be miscommunicating, and it doesn't matter much since you've already nuked the phone, but what I was suggesting was a regular boot while trying to adb logcat the phone. I've used this technique to document the startup process in the past. Adb access loads up fairly soon in the process. If your phone wasn't even getting that far, of course it wouldn't work, but wanted to clear up what I was suggesting with that particular paragraph.

[Q] Nexus S not working...

I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!

callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.

Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!

callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium

callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.

Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.

One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...

callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.

Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.

Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.

callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip

callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).

irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.

krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.

irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.

More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...

callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.

callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.

Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.

by the way...if we can get this working, I'll post a picture of me holding the fixed phone!

Please help, I've spent hours trying to fix this..

Rooted my Nexus S with a rom that is buggy.
-Google Wallet pops up an error that it stopped every few seconds
-Android Market crashes as soon as I open it.
-As of now, it won't go into recovery. It did a couple days ago. Sometimes after I reboot, it remains loading, and I have to take the battery out and try again
restoring to factory settings within the phone didn't work, it rebooted, got stuck, took battery out, and everything was back like before. All I want is a clean, stable rom..
Any help would be greatly appreciated! I am at wits' end.
Thank you so much, I love the XDA site and community, I hope to become a part of it when I am ready to contribute myself.
Edit: I used Titanium Backup Pro to back up my apps, but copying and pasting the DCIM folder to the computer via USB takes forever.. is there a simple solution for backing up photos and videos? Google+ has a feature that uploads it all, but it just said uploading for many minutes, and I saw not a single picture on google+..

Well, first of all, lets get this straight. It seems that you messed something up while installing both the rom and the recovery.
If I were you, I would start from scratch by following to the letter the guide at this link http://forum.xda-developers.com/showthread.php?t=1007782
This way you will have a proper unlocked bootloader, a proper recovery installed, and your phone properly rooted.
Then, after you have assured that your phone is rooted, just try and reflash your rom via recovery. Don't know what you did wrong, but if I were you I would try downloading again the rom .zip file, just to be sure that the previous wasn't corrupted.
EDIT: BTW, for a clean and stable rom, check Pete's AOSP ICS rom, it is exactly what you're looking for (Link: http://forum.xda-developers.com/showthread.php?t=1488100)

It was working fine in a previous rom, and the Android Market used to not crash.. But I will get on that link and follow it word for word - thank you.

Re flash? try a popular ROM like Buglesspete by wiping errything

irizwan said:
Re flash? try a popular ROM like Buglesspete by wiping errything
Click to expand...
Click to collapse
I can't get into recovery - when I try, the Google logo comes up and it is stuck on that forever.. :\

ame85 said:
Well, first of all, lets get this straight. It seems that you messed something up while installing both the rom and the recovery.
If I were you, I would start from scratch by following to the letter the guide at this link http://forum.xda-developers.com/showthread.php?t=1007782
This way you will have a proper unlocked bootloader, a proper recovery installed, and your phone properly rooted.
Then, after you have assured that your phone is rooted, just try and reflash your rom via recovery. Don't know what you did wrong, but if I were you I would try downloading again the rom .zip file, just to be sure that the previous wasn't corrupted.
EDIT: BTW, for a clean and stable rom, check Pete's AOSP ICS rom, it is exactly what you're looking for (Link: http://forum.xda-developers.com/showthread.php?t=1488100)
Click to expand...
Click to collapse
Please see my screenshot - it failed
http://i.imgur.com/oKai5.png

i had this problem
first make sure you didnt freez
Wallet or NFC
than reflash the correct gapps throw recovery

Can you go into bootloader? (turn off the phone, then press Volume up + Power)
If so, just download CWM recovery image for your phone model, put it somewhere easy to access e.g. C:\
Then open Command Prompt, type in the following:
Code:
C:
cd \
fastboot boot your_recovery_image_file.img
I guess you can handle the rest by yourself

kοng said:
Can you go into bootloader? (turn off the phone, then press Volume up + Power)
If so, just download CWM recovery image for your phone model, put it somewhere easy to access e.g. C:\
Then open Command Prompt, type in the following:
Code:
C:
cd \
fastboot boot your_recovery_image_file.img
I guess you can handle the rest by yourself
Click to expand...
Click to collapse
http://i.imgur.com/2uVlM.png
C:\>fastboot boot recovery-clockwork-5.0.2.0-passion
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

here is an easy way to set up the sdk and adb properly http://forum.xda-developers.com/showthread.php?t=1474895
let this video guide you on fastboot flashing recovery(4:24 of video) http://www.youtube.com/watch?feature=player_embedded&v=4AHucGBZHMQ#!

Couple things.
1. Passion is the nexus one. Do not flash that.
2. That is all wrong. Go to the directory that HAS fastboot in it. Its in the platform tools folder of the sdk. If you don't got that and the drivers installed just stop. Fix that and actually read a guide and learn wtf you're doing before you really screw something up.

albundy2010 said:
Couple things.
1. Passion is the nexus one. Do not flash that.
2. That is all wrong. Go to the directory that HAS fastboot in it. Its in the platform tools folder of the sdk. If you don't got that and the drivers installed just stop. Fix that and actually read a guide and learn wtf you're doing before you really screw something up.
Click to expand...
Click to collapse
I have all the drivers installed, I've read over the guides several times, and I tried different things over and over.
I just finally managed to fix everything - previously, rom manager didn't respond or gave me a network error when trying to use it to re-flash CWM, but this time it finally worked. That enabled me to once again use recovery, and I flashed it with Bugless Beast by Peter Alfonso. Thanks everyone.

If you read over everything and understood it you would not have tried to run a fastboot command trying to flash the wrong recovery from the root of your c drive.
Glad you apparently got the phone working but you have no idea what your doing.

albundy2010 said:
If you read over everything and understood it you would not have tried to run a fastboot command trying to flash the wrong recovery from the root of your c drive.
Glad you apparently got the phone working but you have no idea what your doing.
Click to expand...
Click to collapse
I was trying to follow these instructions:
kοng said:
Can you go into bootloader? (turn off the phone, then press Volume up + Power)
If so, just download CWM recovery image for your phone model, put it somewhere easy to access e.g. C:\
Then open Command Prompt, type in the following:
Code:
C:
cd \
fastboot boot your_recovery_image_file.img
I guess you can handle the rest by yourself
Click to expand...
Click to collapse
I put it in C:\, opened CP and typed in what it said above. I must have accidentally gotten the wrong img, but I thought I was doing the rest right.. as per what it says above.

albundy2010 said:
If you read over everything and understood it you would not have tried to run a fastboot command trying to flash the wrong recovery from the root of your c drive.
Glad you apparently got the phone working but you have no idea what your doing.
Click to expand...
Click to collapse
I forgot that not everyone has the path to fastboot.exe and adb.exe in their PATH environment variable

[SOLVED] No OS and can't switch off to reboot into recovery

Hi there,
I had my HTC One S rooted, S-OFF, unlocked, with SuperCID running MaximusHD and I wanted to reinstall a fresh version of it to give it to my father. However, I went too fast and wiped absolutely everything. So now, I'm stuck on the startup screen (with the warning message in red) with no OS and I can't reboot into recovery (wether using hard keys or fastboot) as I can't switch off my phone. What do I need to do in this case? It's plugged to my computer but, of course, as it's stuck on the startup screen, it doesn't recognize it.
Thanks in advance.

Small update: I managed to turn it off but I still can't get it recognized by my computer. I will try to uninstall all drivers for now, I'll get back here as soon as I have time to do that. Hopefully someone will have an idea by then

Flash the recovery from my signature. It will enable USB mounting in recovery mode for hboot 2.16. Just be sure to flash the dm version.

The thing is I can't flash anything since I can't transfer anything to my phone.
Right now, what I've done is reinstalling drivers properly (I get the mention "FASTBOOT USB" in bootloader) but I can't do anything with One S toolkit v4 for example. I managed to get adb commands working and tried to push Maximus ROM through ADB but I got a protocol failure message
Edit: oh wait, it's been transferred anyway.

Do you still have the folder from the install package archive? If yes, open the cmd console and go to the package folder. If it's like in my case "D:\Root" you got to type
Code:
d:
and press enter. Then you got to type
Code:
cd
hit space, repeat pressing tab until it says
Code:
cd Root
and hit enter, again. Then plug in your phone, put it into fastboot usb mode and type
Code:
fastboot devices
into the cmd console and hit enter, once more. If everything is working you should get a list with attached devices which shows your phone.
If your phone isn't listed try another usb port or another cable or if nothing else works another computer.
Next download the TWRP version from my signature, rename it to recovery.img an put it into the install package folder. Then enter
Code:
fastboot flash recovery recovery.img
into the cmd console and press enter for one last time.
TWRP 2.8.0.1-dm should be installed now and you should be able to mount your phone as mtp in recovery mode.

It's all good now! I could get ADB/Fastboot working and could reinstall a fresh Maximus on my One S. I can now safely give it to my father and enjoy my new Z3 Compact. I'll probably install your TWRP anyway though.
Thanks for your help!

Your welcome. Actually it's not my work so it's not "my" TWRP. I've found some mistakes in my last answer cause I'm in a little hurry right now. Going to correct it later for the case that someone else has a similiar problem...
Edit: My previous answer is corrected now.