• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Help I think I bricked my phone!

Prinny said:
If you've never gone S-Off and changed the H-Boot...

http://androidforums.com/evo-v-4g-a...evo-v-4g-ruu-flashing-guide-unroot-guide.html

Try this. Revert to stock with the RUU...lock the bootloader again...and see if you get a booting ROM
Click to expand...


I think you are on the right track about the Boot.img Prinny. Unfortunately the RUU is going to fail because the phone is s-on and the bootloader is unlocked. The bootloader has to be re-locked before running the RUU.... So there's the dilemma... He needs fastboot to be able to re-lock the bootloader, and really to run the RUU as well....
 
JustBenny2k, can you try flashing the boot.img again and take a screen shot and post it so we can see what your command prompt looks like? I will keep peeking in when I can. I have a busy night.
 
Brian706 said:
I think you are on the right track about the Boot.img Prinny. Unfortunately the RUU is going to fail because the phone is s-on and the bootloader is unlocked. The bootloader has to be re-locked before running the RUU.... So there's the dilemma... He needs fastboot to be able to re-lock the bootloader, and really to run the RUU as well....
Click to expand...

I cannot thank everyone enough for all this help but I think what everyone is forgetting is that fastboot isn't letting me connect via usb. All of these suggestions are expecting me to type stuff into the command prompt which gets me nowhere. Fastboot commands just say < waiting for device > and that's where it stays.

Is there a zip or something I can install via recovery? That might be the best solution. Otherwise, my phone just shuts down after the white HTC splash screen.
 
justbenny2k said:
I cannot thank everyone enough for all this help but I think what everyone is forgetting is that fastboot isn't letting me connect via usb. All of these suggestions are expecting me to type stuff into the command prompt which gets me nowhere. Fastboot commands just say < waiting for device > and that's where it stays.

Is there a zip or something I can install via recovery? That might be the best solution. Otherwise, my phone just shuts down after the white HTC splash screen.
Click to expand...

This is why I wanted to see your command prompt. Are you sure you're running the commands from the proper directory? And your phone says fastboot in red letters? Man if you were s-off we would have more options to recover. Try new cable. Disable any software that can interfere such as htc sync, iTunes....
 
Brian706 said:
This is why I wanted to see your command prompt. Are you sure you're running the commands from the proper directory? And your phone says fastboot in red letters? Man if you were s-off we would have more options to recover. Try new cable. Disable any software that can interfere such as htc sync, iTunes....
Click to expand...

Yes the drivers are installed and it says FASTBOOT but not FASTBOOT USB. I"m running Win7 and the software is in a directory called ADB which I am running fastboot from. I've tried 2 different cables, too.
 
Did you try what I mentioned with

adb killserver

adb devices

while in the fastboot menu?
 
Brian706 said:
This is why I wanted to see your command prompt. Are you sure you're running the commands from the proper directory? And your phone says fastboot in red letters? Man if you were s-off we would have more options to recover. Try new cable. Disable any software that can interfere such as htc sync, iTunes....
Click to expand...

Does this help?
 

Attachments

  • screen grab of fastboot.jpg
    screen grab of fastboot.jpg
    322.1 KB · Views: 162
justbenny2k said:
Yes the drivers are installed and it says FASTBOOT but not FASTBOOT USB. I"m running Win7 and the software is in a directory called ADB which I am running fastboot from. I've tried 2 different cables, too.
Click to expand...

Where did you get this version of the sdk? From the Android Developers website? Or is it some form of a mini-sdk package? Is adb the name of the folder that houses the adb.exe and fastboot.exe applications? You want to be issuing the fastboot commands from that directory unless you have input an environmental variable to adb/fastboot globally on your machine.

So if it were the full blown sdk and following the majority of install guides on the net, the location is often:

c:\android-sdk-windows\platform-tools

...that could be entirely different for you depending on what package you used and how the file structure is laid out. Just trying to make sure we're on the right jumping off point here.
 
Brian706 said:
Hmm I hope you don't have a bad usb port on your phone. It looks like you're doing things right but it is definitely waiting for device because fastboot usb isn't working. Other than faulty usb port, the only thing I can think of is if your computer is usb 3.0
Click to expand...

Everything is up-to-date and current. The USB port on my phone worked just fine this morning before I flashed a rom that caused this problem in the first place.

The ADB/FlashBoot is from the mini SDK that I got from the forum here on turning the EVO V into an EVO 3D.
 
I don't believe you'll have much luck running any adb command from the fastboot option in the bootloader. adb commands should be run from inside a custom recovery as they are packaged with an adb deamon.

Also, I think our problem may be either an incorrect download or an incorrect path when issuing commands. Is this the thread you downloaded your sdk package from:

http://androidforums.com/evo-v-4g-a...ing-evo-v-4g-roms-kernels-using-fastboot.html

Because if so, there are a couple options in there concerning adb/fastboot and I believe the last one MAY be adb only. So is that the one you installed because that would explain things and it'd explain why the folder you're issuing commands from is called adb.

If you installed the mini-sdk from that link, your path would be:

c:\ sdk-tools

...assuming you installed it on the root of the c drive and not on the desktop or similar. So, in any event, let's figure out exactly which package you have, then we need to drill into the folders (possibly your adb folder) and make sure that it contains both an adb.exe AND fastboot.exe.
 
iowabowtech said:
I don't believe you'll have much luck running any adb command from the fastboot option in the bootloader. adb commands should be run from inside a custom recovery as they are packaged with an adb deamon.

Also, I think our problem may be either an incorrect download or an incorrect path when issuing commands. Is this the thread you downloaded your sdk package from:

http://androidforums.com/evo-v-4g-a...ing-evo-v-4g-roms-kernels-using-fastboot.html

Because if so, there are a couple options in there concerning adb/fastboot and I believe the last one MAY be adb only. So is that the one you installed because that would explain things and it'd explain why the folder you're issuing commands from is called adb.

If you installed the mini-sdk from that link, your path would be:

c:\ sdk-tools

...assuming you installed it on the root of the c drive and not on the desktop or similar. So, in any event, let's figure out exactly which package you have, then we need to drill into the folders (possibly your adb folder) and make sure that it contains both an adb.exe AND fastboot.exe.
Click to expand...

Yes, that's the one and I renamed the folder ADB because I was tired of typing SDK-TOOLS. Too many letters. Are you saying I should rename the folder?

Sure enough, I just renamed the folder and now the fastboot menu says USB. Odd!
 
I'm glad it was sorted out! I can't believe it was just a name issue xD I'm glad its fixed though!
 
You must log in or register to reply here.
Back
Top Bottom