Develop Bugs

How do I enter command when in fastboot mode (Desire)?

Hello.
I'm pretty sure i bricked my HTC desire yesterday when trying to flash LeeDroids Mod. My phone hangs at the three green HTC letters and it has been like this the whole night. I've tried taking out the battery and things like that but it still hangs. Even when triyng to do a recovery. So i searched the forum to find out how to unbrick the phone and i found a nice thread that explains how to get acces to the SD again and then how to unbrick the USB connection. But I havent been able to try this out yet since i cannot find out how to enter commands when in fastboot. I know I need to be connected with a USB-cable to the PC, but what else do I have to do?
Hope someone can help 'cause I would really love to have my HTC Desire working again so that i can try out more cool FroYo mods from this lovely forum.
- Czepluch

czepluch said:
Hello.
I'm pretty sure i bricked my HTC desire yesterday when trying to flash LeeDroids Mod. My phone hangs at the three green HTC letters and it has been like this the whole night. I've tried taking out the battery and things like that but it still hangs. Even when triyng to do a recovery. So i searched the forum to find out how to unbrick the phone and i found a nice thread that explains how to get acces to the SD again and then how to unbrick the USB connection. But I havent been able to try this out yet since i cannot find out how to enter commands when in fastboot. I know I need to be connected with a USB-cable to the PC, but what else do I have to do?
Hope someone can help 'cause I would really love to have my HTC Desire working again so that i can try out more cool FroYo mods from this lovely forum.
- Czepluch
Click to expand...
Click to collapse
you have to use adb, google the android sdk and start there

All you need to do is boot into FASTBOOT, plug in your USB and run an RUU to get back to stock (assumg one is available for your phone) and then root again, had to do it myself the other day

you do not have to do ANY of this
if you are using clockworkmod or any custom recovery then there is the option to mount USB storage in which you can put on a backup or any other rom onto your sd card, unmount usb storage, and flash it, all in one.

cgrec92 said:
you do not have to do ANY of this
if you are using clockworkmod or any custom recovery then there is the option to mount USB storage in which you can put on a backup or any other rom onto your sd card, unmount usb storage, and flash it, all in one.
Click to expand...
Click to collapse
How do I do that when my phone doesnt boot? As i wrote in the first post it is stock at the 3 green HTC letters. I was using clockworkmod to flash, but as I wrote i cannot boot into andoid atm.
@AndroHero: Can you please give me a link or something? I have tried a lot of things, but i doesnt seem to work, so I would like to be certain that the link and guide im using is right.

czepluch said:
How do I do that when my phone doesnt boot? As i wrote in the first post it is stock at the 3 green HTC letters. I was using clockworkmod to flash, but as I wrote i cannot boot into andoid atm.
@AndroHero: Can you please give me a link or something? I have tried a lot of things, but i doesnt seem to work, so I would like to be certain that the link and guide im using is right.
Click to expand...
Click to collapse
Do you have the fake-flash zip file renamed as update.zip and at the root of your SDCard?

dnlgee said:
Do you have the fake-flash zip file renamed as update.zip and at the root of your SDCard?
Click to expand...
Click to collapse
yes i do

czepluch said:
yes i do
Click to expand...
Click to collapse
Have you booted the phone while holding the volume down and then selecting recovery, then when recovery boots, press volume up and power then select "apply update.zip" ?

The problem is that when i choose recovery it freezes aswell. The screen with the phone and the little red triangle freezes, so i cannot choose recovery.

EddyOS said:
All you need to do is boot into FASTBOOT, plug in your USB and run an RUU to get back to stock (assumg one is available for your phone) and then root again, had to do it myself the other day
Click to expand...
Click to collapse
So do what I said here...to get into FASTBOOT hold back and power it on

What is RUU?
Edit: Maybe I need someone to make a step by step noob guide? Im totally lost. Ive flashed my Desire lots of times before and ive never had a single problem, but right now i really dont know what to do and how to do?

If you're asking questions about RUU's then maybe rooting wasn't for you. It's basic stuff. You need a grasp of the basics before trying something advanced!
Basically it's the official ROM file from HTC/your phone vendor...

Okay. Thanks. I thought that RUU was something like that but I just couldnt see how i should be able to acces any files right now. As i wrote before the phone freezes at the picture of a phone with the red triangle, and i am not able to get any further that that. I would really appreciate if anyone could tell me how and what to do next?

I had the same problem a few days ago. For me it worked to just go through the rooting process again, you can find the steps on modaco (just step 1 of r6), I can't link them at the moment I'm at work and it seems I can't open modaco from here.
Anyways if you follow step 1 you can access the recovery again and the phone will boot past the HTC logo screen.
Also these steps are well documented on modaco.
Try this first since it will save you the step of running the RUU, which I wasn't able to (somehow the software complained my battery was below 30%, which it wasn't)
Good luck hope this solves it for you.

czepluch said:
Okay. Thanks. I thought that RUU was something like that but I just couldnt see how i should be able to acces any files right now. As i wrote before the phone freezes at the picture of a phone with the red triangle, and i am not able to get any further that that. I would really appreciate if anyone could tell me how and what to do next?
Click to expand...
Click to collapse
You don't need to go into recovery! boot into FASTBOOT and then leave it at that. Plug the phone in and it will then say FASTBOOT USB. Then run the RUU your phone came with originally. You don't need to go anywhere near Recovery

I am pretty certain that ive found a solution now. I deserve a fist in the nuts for being so stupid not to press volume up + power when trying to get into recovery mode. But fortunately dnlgee asked if i had remembered this. Now that ive gotten this far i should be able to solve the rest. I will however return if im still unable to solve it.

czepluch said:
I am pretty certain that ive found a solution now. I deserve a fist in the nuts for being so stupid not to press volume up + power when trying to get into recovery mode. But fortunately dnlgee asked if i had remembered this. Now that ive gotten this far i should be able to solve the rest. I will however return if im still unable to solve it.
Click to expand...
Click to collapse
Ah I missed that part, I couldn't access recovery either. Only thing left working was fastboot for me. All other options would hang on the HTC logo screen.

[Q] Help! I think I've bricked my phone.

I think I have bricked my phone. I followed the instructions listed here:
http://forum.xda-developers.com/showthread.php?t=834228
but have when i restart the phone, it is just stuck on the words HTC
doesn't load into anything else.
What should I do?

Well as your phone powers on its not a proper brick, when it powers on and gets to the first boot screen like you say there is usually like a 99% chance it can be recovered.
Edit: stupid thanks button!
How long do you leave it on the htc bit before you power down again? maybe your just not waiting long enough.

left it on for 10 minutes.
all it says is "HTC" in green...

Are you able to get into hboot? Try holding the volume down key while you turn on the phone.

One easy thing to try would be to flash an RUU, make sure you find the correct one for your phone (Z or G2) and make sure its the latest one around.
That will return your phone to stock so you can attempt to root again.

yes, yes i can get into HBOOT.

my phone is a g2. How do I flash a RUU?

yukei said:
my phone is a g2. How do I flash a RUU?
Click to expand...
Click to collapse
my mistake, wasn't aware there appears to be no way to flash a new firmware on a g2 unless its by ota.... sucks
edit: just bare with us we will have an answer for you soon.

What about recovery? There should be a recovery option in the hboot menu.

Thank you so much!!

Have you got a custom recovery?
If so, flash a new rom

I tried recovery. It turns into a blackscreen with a phone in the middle and a read triangle with a ! on top of it.
I dunno if that is telling me to not turn off the phone.

MacaronyMax said:
Have you got a custom recovery?
If so, flash a new rom
Click to expand...
Click to collapse
I do not think I have a custom recovery.
How do I check?

yukei said:
I do not think I have a custom recovery.
How do I check?
Click to expand...
Click to collapse
no, from your description above, you just have stock.
I have an idea that you should be able to fasboot install a new recovery, then from there you will be able to flash a new rom.

Lennyuk said:
no, from your description above, you just have stock.
I have an idea that you should be able to fasboot install a new recovery, then from there you will be able to flash a new rom.
Click to expand...
Click to collapse
Oh ok. I think I'm a bit more calm now. So is there anything you need to know? In regards to the blackscreen with the red triangle warning sign in the middle. Can reset my phone?

yukei said:
Oh ok. I think I'm a bit more calm now. So is there anything you need to know? In regards to the blackscreen with the red triangle warning sign in the middle. Can reset my phone?
Click to expand...
Click to collapse
I take it you know how to use adb (based on the root process you were trying to do)?

Lennyuk said:
I take it you know how to use adb (based on the root process you were trying to do)?
Click to expand...
Click to collapse
I know some. But not everything. Only the very basics. I have had a rooted hero before. I have had some experience with it.
I am not able to use adb tho. (As in, can't get it to work currently)
when i type "adb remount"
it says "error: device offline"
I have plugged in the USB cable.

basically all you need to do is find the clockwork mod recovery image file
put it in your adb folder
turn phone on hboot, and select fastboot
then type the following into your pc
"fastboot flash recovery [recovery.img]"
obviously replace [recovery.img] with whatever your recovery is called (and no [])
then you should be able to boot into clockwork mod recovery and from there you can install a new rom.

before I really do anything wrong here, would you be able to direct me to an image file?
http://forum.xda-developers.com/showthread.php?t=834731&highlight=cwm+recovery
i have found this thread. however, there is no option to download the recovery file.

yukei said:
before I really do anything wrong here, would you be able to direct me to an image file?
Click to expand...
Click to collapse
use this one for now, you can update with a newer one after your booted back to a rom
http://forum.xda-developers.com/showthread.php?t=834731

HELP-Is MY Phone Bricked - Can't Get into Recovery

I'm a bit of a NOOB, so bear with my terminology. My phone was rooted and Nand unlocked (S=off), running Fresh 3.4. It will not accept calls so I have to take it to Sprint. I ran the latest RUU to get it unrooted, but I could not use Titanium Backup to restore my apps. I ran Universal AutoRoot.zip http://forum.xda-developers.com/showthread.php?t=838448 and went through what seemed to be the complete process. At the end I was left with the bootloader menu to boot into the recovery but my EVO will not go into recovery. When I try I get I get Recovery the screen shows a phone with a red triangle. I have tried everything I know (I'm a bit of a NOOB), and I cannot get to recovery or Nandroid. I did a Nandroid Backup but can't get to it. My phone no longer communicates with my computer. I have just moved and need my phone to set up appointments. Please help, I'm desperate.

posted in the wrong section. however
does your bootloader show S-OFF now?
all you may need to do is flash a custom recovery to it.

If you unrooted your phone you'll no longer have a recovery, unless I'm misunderstanding you...

tonwarr.the.incredible said:
If you unrooted your phone you'll no longer have a recovery, unless I'm misunderstanding you...
Click to expand...
Click to collapse
from my understanding, he unrooted & then tried to root again. but i may be wrong lol

If you can get into bootloader, you can fix your phone.

get to the bootloader with the usb plugged in so it says fastboot usb in RED at the top. On your pc download the android sdk, goto the tools folder, copy over a custom recovery.img (ra or cm) to the tools folder, type cmd in the address bar, in the command prompt type:
Code:
fastboot flash recovery recovery-RA-evo-v1.8.0.img
and press enter (you can replace recovery-RA-evo-v1.8.0.img with the img of your choice). select bootloader again from the menu, select recovery, enjoy!

jminor4326 said:
I'm a bit of a NOOB, so bear with my terminology. My phone was rooted and Nand unlocked (S=off), running Fresh 3.4. It will not accept calls so I have to take it to Sprint. I ran the latest RUU to get it unrooted, but I could not use Titanium Backup to restore my apps. I ran Universal AutoRoot.zip http://forum.xda-developers.com/showthread.php?t=838448 and went through what seemed to be the complete process. At the end I was left with the bootloader menu to boot into the recovery but my EVO will not go into recovery. When I try I get I get Recovery the screen shows a phone with a red triangle. I have tried everything I know (I'm a bit of a NOOB), and I cannot get to recovery or Nandroid. I did a Nandroid Backup but can't get to it. My phone no longer communicates with my computer. I have just moved and need my phone to set up appointments. Please help, I'm desperate.
Click to expand...
Click to collapse
DUDE. think man. in order to get into recovery, YOU HAVE TO FLASH A RECOVERY IMAGE. DUH!

Hope you don't ever get a job working with people... How about a helpful answer instead of belittleing him? He already admits to being a novice. He came here for help, not to have someone dish him a steam pile of #$% instead.

oshizzle1991 said:
DUDE. think man. in order to get into recovery, YOU HAVE TO FLASH A RECOVERY IMAGE. DUH!
Click to expand...
Click to collapse
Definitely another situation where saying nothing would've been much more productive!

Sengfeng said:
Hope you don't ever get a job working with people... How about a helpful answer instead of belittleing him? He already admits to being a novice. He came here for help, not to have someone dish him a steam pile of #$% instead.
Click to expand...
Click to collapse
he should expect to get these types of responses if he posts in wrong sections and doesnt search for his answer first. its called tough love. if you have a problem with it, why dont you post a productive answer? i posted a productive answer, just in a way that belittled him to get my point across.

oshizzle1991 said:
he should expect to get these types of responses if he posts in wrong sections and doesnt search for his answer first. its called tough love. if you have a problem with it, why dont you post a productive answer? i posted a productive answer, just in a way that belittled him to get my point across.
Click to expand...
Click to collapse
how bout saiying . "posted in the wrong section " then point the guy in the right direction.
no need to beat anyone up.. Grow up
tim

Stuck in Boot Loop

I'm currently stuck in a boot loop, with no way to access my rom or recovery. I can only access bootloader. The boot loop began happening soon (around 2hrs) after flashing MIUI; The rom was running, and out of nowhere it just began cycling. Any ideas on how I can get out of this boot loop?
Edit: I'm no longer in a boot loop after installing a different full system PC36IMG.zip. Instead after the initial splash screen my evo goes black and vibrates 5 times, then my green LED starts flashing. It stays this way until I remove the battery.
So far I have tried:
Flashing RA's recovery image using fastboot. (The flash was successful)
Using RA's recovery PC36IMG.zip. (The installation was successful)
Using an RUU file renamed to PC36IMG.zip (The installation was successful)
Using a Sprint Lover's file renamed to PC36IMG.zip (The installation was successful)
For all of these the process of installing and flashing went fine. Yet when I would turn on my phone it would just go right back into the boot loop.
*I've been editing this post as I've tried new things, so you don't need to read through the thread to help me.
Anyways I'm at my wits end here, pretty worried, and phoneless, so any help would be amazing.

Have you tried ADB from bootlaoder or fastboot. May be able to get recovery that way.

I'm trying to do a bit of research, but am a little confused on what adb is. It's part of the android sdk? I can't seem to find it, or know how to launch it. Is there a thread somewhere that covers it? I'll keep doing my research, thanks for the tip.

Its a command terminal but if you are not familiar with it you probably wont get it right away! I am just starting to learn this myself. VERY VERY useful tool though! Here a link.......
http://forum.xda-developers.com/showthread.php?t=502010

I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!

thanamesjames said:
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
Click to expand...
Click to collapse
Jeez sounds like you have a better grasp on this than me already! LMAO

haha, well i'm not too sure. Have you gotten you're evo to be found? Right now while using adb, I'm just told "device not found." All my drivers should be properly installed because I had to install them when I used unrevoked. So I choose fastboot on my evo, and then it shows up on my computer as "android 1.0" under devices and printers... but adb doesn't find it.

I was told to get rid of my drivers and re install the recommended ones before starting. It recognized mine right away. YouTube also has nice how to videos on ADB.

Is there any way you can point me to the recommended drivers? I think that second link you gave me is the same as the first also.
Edit: Every single guide I see on the internet about adb, says use debug mode within the actual rom. However I'm obviously not in a rom, i'm in bootloader, and for the life of me can't get adb to find my phone.
Edit2: Ok, so maybe I can only use fastboot. Right now when trying fastboot it just says "waiting for device," even if it didn't say that, what would i need to do to get on the road to recovery?

So I'm starting to get scared. At first I figured this was something I could fix... and now I'm not positive it is. I've used fastboot from terminal, trying to flash recovery and it says "FAILED (remote: not allowed)" I'm starting to get desperate, does anyone have any ideas?

I'm sorry to bump this, but I'm really struggling here... because I'm phoneless and all , I worked at this for 5 hours last night from 9-2, and now I'm at it again... and very worried. I've read that theres almost no way to completely brick your phone, but I'm starting to feel like I did. It seems like no matter what I flash it just keeps boot cycling. Thanks for the help.

go to the bootloader and ruu it

I have... I took the ruu file and renamed it PC36IMG.zip, went into bootloader and it went through all the steps with "OK"s, rebooted, and went right back into the boot loop.
Specifically I used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip" from here,
http://goo-inside.me/evo/stock/RUU/
Is there a specific number version of RUU I should try? I just tried the most recent.

You have to use the ruu that matches your radios/software etc. How did this boot loop start? Give us all your phone info, rom, hboot version, radios etc.
Sent from my iphone slayer 4G

I flashed a CM7 nightly, from CM, about 2 weeks ago. Yesterday, still using the same nightly (build 1 or something) my phone seemingly out of nowhere rebooted - I wasn't even using it at the time. When it went back into CM7 it acted as if I had never linked a google account to my phone. The first thing that came up was the android google apps screen. Anyways, I decided I wouldn't stick with CM7 until at least an RC was out, so I wiped data, cache, and davlik and flashed MIUI. I used it for about two hours, didn't do anything out of the ordinary, and once again seemingly out of nowhere it rebooted... except when it did it went into a cycle and never reached MIUI, and wouldn't go into recovery, I could only access bootloader.
Anyways, I'll tell you what bootloader says my phone versions are, but I do believe the info all changed this morning when I flashed the ruu file.
SUPERSONIC EVT2-3 SHIP S-off
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00

Check your pm
Sent from my iphone slayer 4G

Are there any other thoughts on how to get on my feet?
In addition to booting an RUU file as PCIMG36 I've also tried a Sprint Lover's image as PCIMG36. Even though both installed properly, my phone still staid in the boot cycle afterwards for both.
I've been suggested, and have seen other users suggest on other threads, to try adb commands, but I don't know if i can access adb while the phone is in bootloader. I have however accessed fastboot, are there any commands that might help me? If not, can I use adb while in bootloader? Thanks.

Well I tried a new PC36IMG.zip file and I'm no longer stuck in a boot loop... instead as soon as the HTC EVO 4G splash disappears my phone goes black and vibrates 5 times, and my green LED flashes.
Good? Bad?

This would be the 300th something thread I've read on this subject and this is exactly were I'm at with my EVO minus the last post... I was using warms2p2 with the hdmi kernal everything working fine then I went to change my notification ringtone and bam went into boot loop and never came out. SOOO! it would be nice to save this unit... any help forum members would be great I've tried every RUU out there from fastboot from sd card nothing.
Very intesting that this thread ended this way... please share if you think you got this whooped. Thank you in advanced.

Love the revival of old threads...but did you try changing the kernel?
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip 3.70 RUU, just rename to PC36IMG and flash in the bootloader if you want to run the RUU.

[Q] Recovering from unusual boot loop

Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.

jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.

RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?

jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there

I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.

This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719

RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.

jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.

jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.