Database Develop

Help!!!! My htc wont connect to fastboot

Hey guys my htc is stuck on a boot loop so i try to connect fast boot to flash a new boot.img but my fastboot just says usb device not recognized please guys i really need help
My symptoms
Stuck on htc boot logo
Cannot access Recovery
Fastboot wont connect

Locky123 said:
Hey guys my htc is stuck on a boot loop so i try to connect fast boot to flash a new boot.img but my fastboot just says usb device not recognized please guys i really need help
My symptoms
Stuck on htc boot logo
Cannot access Recovery
Fastboot wont connect
Click to expand...
Click to collapse
Put the stock ROM on your sdcard and rename it from ROM.zip to ph39IMG.zip and go to bootloader.

mohamed_moscow said:
Put the stock ROM on your sdcard and rename it from ROM.zip to ph39IMG.zip and go to bootloader.
Click to expand...
Click to collapse
No luck it just goes through and says no image found

U got the HTC USB drivers?
Sent from my Vivid 4G using Tapatalk 2

ZeRo2o9 said:
U got the HTC USB drivers?
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
ok yes i can acess it but no matter what rom i install it is just stuck on the htc logo but i can access recovery

Locky123 said:
ok yes i can acess it but no matter what rom i install it is just stuck on the htc logo but i can access recovery
Click to expand...
Click to collapse
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.

rewen said:
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.
Click to expand...
Click to collapse
Are you using Windows 8? I found it does the same with my Sony phone. It sucks!

rewen said:
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.
Click to expand...
Click to collapse
Yea I fixed it I ended up flashing the kernal then flashing the rom then flashed the kernal once again and it works fine after that but i dont know how i could help any other way

Locky123 said:
No luck it just goes through and says no image found
Click to expand...
Click to collapse
Remember to put all letters in capital and also to relock your bootloader before using the zip file.

My 'USB Device Not Recognized' issue turned out to be Windows 8. I originally flashed my boot.img using Windows 7 at work and forgot that I'd done it from there, so I'd been under the impression that it worked once for me on Windows 8 so it should work again. But in fact, it never worked on Windows 8.
I installed Windows 7 on a second partition at home and it worked without issue. FYI I wasn't using USB 3.0 or anything and I tried a couple of Windows 8 PCs before resorting to installing Windows 7. It's also worth noting that the error in Windows 8 seems to happen before the actual drivers are installed/loaded, so it's not just a matter of picking the proper driver afaik. I did have the proper drivers and HTC Sync Manager, and tried forcing the driver install, but it didn't help. This also means you can't use a virtual machine to work around the issue.
Hope this helps others who run into the 'USB Device Not Recognized' error on Windows 8...
---------- Post added at 11:45 AM ---------- Previous post was at 11:45 AM ----------
Locky123 said:
Yea I fixed it I ended up flashing the kernal then flashing the rom then flashed the kernal once again and it works fine after that but i dont know how i could help any other way
Click to expand...
Click to collapse
Did you wipe data/factory reset after flashing? I didn't see you mention that anywhere. Also, are you sure you're using the right ROMs for the One XL (evita) and not the regular One X? Or the other way around in case you're in the wrong forum?

Fastboot USB not detected

When I try to flash the boot.img by running the phone in Fastboot USB it does not connect with my PC. I have installed the latest version of SDK and the necessary files that need to be installed such as fasboot.exe, etc.
I had successfully flashed a boot.img before reformatting my PC but now the phone disconnects when in Fastboot USB mode although it can connect and is shown in Device Manager when inside the phone OS.

reeper250 said:
When I try to flash the boot.img by running the phone in Fastboot USB it does not connect with my PC. I have installed the latest version of SDK and the necessary files that need to be installed such as fasboot.exe, etc.
I had successfully flashed a boot.img before reformatting my PC but now the phone disconnects when in Fastboot USB mode although it can connect and is shown in Device Manager when inside the phone OS.
Click to expand...
Click to collapse
install htc sync for htc drivers... Check my sign... U can find ADB and fastboot drivers with list of commands...

shiromau said:
install htc sync for htc drivers... Check my sign... U can find ADB and fastboot drivers with list of commands...
Click to expand...
Click to collapse
I have already done all of that but the phone still disconnects when on Fastboot USB mode

reeper250 said:
I have already done all of that but the phone still disconnects when on Fastboot USB mode
Click to expand...
Click to collapse
Well anyways it could be multiple things. It could be
1. You dont have proper drivers (but u said above you do with latest SDK and HTC Sync installed)
2. Broken USB port on computer
3. Broken mini HDMI port on your phone
4. Broken Cable.
You wouldnt by any chance be using PACman are you? I actually had some problems where my computer would not detect PACman in fastboot. If thats the case reflash PACman and try again. If that still doesnt work, then flash another ROM with full wipe, then see if it connects.

072665995 said:
Well anyways it could be multiple things. It could be
1. You dont have proper drivers (but u said above you do with latest SDK and HTC Sync installed)
2. Broken USB port on computer
3. Broken mini HDMI port on your phone
4. Broken Cable.
You wouldnt by any chance be using PACman are you? I actually had some problems where my computer would not detect PACman in fastboot. If thats the case reflash PACman and try again. If that still doesnt work, then flash another ROM with full wipe, then see if it connects.
Click to expand...
Click to collapse
I was running PACman but after I installed the latest update for it my phone kept bootlooping so I am currently running CyanVivo X. It connects fine using the USB cable but it just doesn't connect when going into Fastboot USB.

I can also connect through the recovery menu with Clockwork Recovery.

You have to make sure whether your USB port is broken or the cable itself.
Enviado do meu Incredible S

thiagofbrito said:
You have to make sure whether your USB port is broken or the cable itself.
Enviado do meu Incredible S
Click to expand...
Click to collapse
It is not the USB port or the cable because it works 100% fine when not in Fastboot USB. The phone connects perfectly fine within the ROM and in Clockwork Recovery but not in Fastboot USB. I am thinking that re-unlocking the phone may help.
EDIT: I was using a USB 3.0 port and that was the issue... For some reason it didn't like the USB 3.0 in Fastboot USB << Heads up for anyone else having this issue.

reeper250 said:
It is not the USB port or the cable because it works 100% fine when not in Fastboot USB. The phone connects perfectly fine within the ROM and in Clockwork Recovery but not in Fastboot USB. I am thinking that re-unlocking the phone may help.
EDIT: I was using a USB 3.0 port and that was the issue... For some reason it didn't like the USB 3.0 in Fastboot USB << Heads up for anyone else having this issue.
Click to expand...
Click to collapse
Is there any fix for this? My ultrabook only has USB 3.0 ports...

Yeah i've been having this same issue exactly for 3 days already but clueless. Shall there be anyone who had figured it out, plz kindly share the solution ok.
Thanks in advance
reeper250 said:
It is not the USB port or the cable because it works 100% fine when not in Fastboot USB. The phone connects perfectly fine within the ROM and in Clockwork Recovery but not in Fastboot USB. I am thinking that re-unlocking the phone may help.
EDIT: I was using a USB 3.0 port and that was the issue... For some reason it didn't like the USB 3.0 in Fastboot USB << Heads up for anyone else having this issue.
Click to expand...
Click to collapse

blackbird2394 said:
Is there any fix for this? My ultrabook only has USB 3.0 ports...
Click to expand...
Click to collapse
Denim Guy said:
Yeah i've been having this same issue exactly for 3 days already but clueless. Shall there be anyone who had figured it out, plz kindly share the solution ok.
Thanks in advance
Click to expand...
Click to collapse
No fix unless you want to replace your USB 3 ports with USB 2 ports.

[Q] No 'FASTBOOT USB' HTC One Developer Edition

I have searched for the last couple weeks with little success finding an answer.
Recently I tried to install boot.img using FASTBOOT but was unable to get FASTBOOT to go to FASTBOOT USB after connecting to MacBook Pro with USB.
To see if drivers were an issue I tried to do the same to my HTC One X (Evita) and had no problem getting FASTBOOT USB.
Both units have Android Debugging USB checked.
Both units are using CM11 ROM and latest TWRP recovery.
I had flashed, via TWRP, a Google Edition ROM but did not like it so installed my CM11 backup from TWRP
I tried a different USB cable
Am I missing something? One X does FASTBOOT USB and One does not?
Perhaps going to S-OFF but I think I need to be able to use FASTBOOT USB?!
Any ideas are very much appreciated.
Thanks
David

dkonkin said:
I have searched for the last couple weeks with little success finding an answer.
Recently I tried to install boot.img using FASTBOOT but was unable to get FASTBOOT to go to FASTBOOT USB after connecting to MacBook Pro with USB.
To see if drivers were an issue I tried to do the same to my HTC One X (Evita) and had no problem getting FASTBOOT USB.
Both units have Android Debugging USB checked.
Both units are using CM11 ROM and latest TWRP recovery.
I had flashed, via TWRP, a Google Edition ROM but did not like it so installed my CM11 backup from TWRP
I tried a different USB cable
Am I missing something? One X does FASTBOOT USB and One does not?
Perhaps going to S-OFF but I think I need to be able to use FASTBOOT USB?!
Any ideas are very much appreciated.
Thanks
David
Click to expand...
Click to collapse
When the phone is in fastboot mode, try pressing the volume down key. For me, the volume down key gets it into Fastboot USB

dkonkin said:
I have searched for the last couple weeks with little success finding an answer.
Recently I tried to install boot.img using FASTBOOT but was unable to get FASTBOOT to go to FASTBOOT USB after connecting to MacBook Pro with USB.
To see if drivers were an issue I tried to do the same to my HTC One X (Evita) and had no problem getting FASTBOOT USB.
Both units have Android Debugging USB checked.
Both units are using CM11 ROM and latest TWRP recovery.
I had flashed, via TWRP, a Google Edition ROM but did not like it so installed my CM11 backup from TWRP
I tried a different USB cable
Am I missing something? One X does FASTBOOT USB and One does not?
Perhaps going to S-OFF but I think I need to be able to use FASTBOOT USB?!
Any ideas are very much appreciated.
Thanks
David
Click to expand...
Click to collapse
I had tried that recommendation from another site with no luck! Thanks for responding.
With the little response to my query I am thinking more and more it is a hardware issue. Read something about a Kernel change but nothing definitive.
If I can get this rectified I will go to S-OFF immediately
Thanks again.
David

dkonkin said:
I had tried that recommendation from another site with no luck! Thanks for responding.
With the little response to my query I am thinking more and more it is a hardware issue. Read something about a Kernel change but nothing definitive.
If I can get this rectified I will go to S-OFF immediately
Thanks again.
David
Click to expand...
Click to collapse
kernel shouldn't affect bootloader. maybe the phone's USB port has debris in it? try cleaning it, and also try different cables, USB ports.

I have tried the different cables. Works with Evita but not with the M7.
Cleaning the USB port is on the agenda but short of compressed air, which I was going to pick up today, I am not sure what else I can do!
Thanks
D

No FASTBOOT USB or ADB 'Flashing Mauve screen!'
dkonkin said:
I have tried the different cables. Works with Evita but not with the M7.
Cleaning the USB port is on the agenda but short of compressed air, which I was going to pick up today, I am not sure what else I can do!
Thanks
D
Click to expand...
Click to collapse
Since my last post I tried to access device using ADB.
./adb devices did not give me the HTC One serial #. I had no problem getting serial # when I plugged in my One X.
Is there anything I am missing? I have compared the two with what is checked off in the DEVELOPER OPTIONS and both look to be the same.
Tried to connect HTC One to Mac using ANDROID FILE TRANSFER. Now I get a rapidly flashing pink/purple overlay occasionally?!?!
Anybody have a suggestion?
Thanks
David

dkonkin said:
Since my last post I tried to access device using ADB.
./adb devices did not give me the HTC One serial #. I had no problem getting serial # when I plugged in my One X.
Is there anything I am missing? I have compared the two with what is checked off in the DEVELOPER OPTIONS and both look to be the same.
Tried to connect HTC One to Mac using ANDROID FILE TRANSFER. Now I get a rapidly flashing pink/purple overlay occasionally?!?!
Anybody have a suggestion?
Thanks
David
Click to expand...
Click to collapse
Oh yeah, and I was not able to connect to HTC One using Android file transfer!
Am now flashing another ROM to see if that will make any difference.
I will get some compressed air tomorrow. Perhaps there is some crud in the phones USB port preventing contact?
As always, I appreciate the support from all.
David

Fastboot won't recognize USB.

So I'm getting into fastboot mode but it just says FASTBOOT not FASTBOOT USB even thought it's plugged in. When USB is plugged in I can't even get into fastboot mode. Any ideas?

Ephemera said:
So I'm getting into fastboot mode but it just says FASTBOOT not FASTBOOT USB even thought it's plugged in. When USB is plugged in I can't even get into fastboot mode. Any ideas?
Click to expand...
Click to collapse
Follow here

yatindroid said:
Follow here
Click to expand...
Click to collapse
Tried following it but had no luck. Plus I'm on HBOOT 1.57, S-OFF, Bootloader unlocked, and using Window 8.1. I tried Ubuntu and followed the steps, but the phone still doesn't read FASTBOOT USB.

Ephemera said:
Tried following it but had no luck. Plus I'm on HBOOT 1.57, S-OFF, Bootloader unlocked, and using Window 8.1. I tried Ubuntu and followed the steps, but the phone still doesn't read FASTBOOT USB.
Click to expand...
Click to collapse
Is your usb cable a data cable or only a charging cable? Make sure its data capable, not only charging cable, try another cable, try another port (usb 2.0).
What is your version of htc drivers?

alray said:
Is your usb cable a data cable or only a charging cable? Make sure its data capable, not only charging cable, try another cable, try another port (usb 2.0).
What is your version of htc drivers?
Click to expand...
Click to collapse
Latest HTC drivers, tried 4 cables, multiple USB ports along with other computers. It is not a driver issue because the phone doesn't say FASTBOOT-USB nor is it shown in device manager.

Ephemera said:
Latest HTC drivers, tried 4 cables, multiple USB ports along with other computers. It is not a driver issue because the phone doesn't say FASTBOOT-USB nor is it shown in device manager.
Click to expand...
Click to collapse
SO it might be a defective usb port on your phone. Does usb-otg works?

alray said:
SO it might be a defective usb port on your phone. Does usb-otg works?
Click to expand...
Click to collapse
I can't get into to recovery, it boot loops. So how would I be able to test it? Plus I don't think I have an OTG cable.

Ephemera said:
I can't get into to recovery, it boot loops. So how would I be able to test it? Plus I don't think I have an OTG cable.
Click to expand...
Click to collapse
I guess that if your phone isn't detected both in windows and ubuntu its maybe a bad usb port on the phone or maybe a corrupted bootloader.
What caused the bootloop?

alray said:
I guess that if your phone isn't detected both in windows and ubuntu its maybe a bad usb port on the phone or maybe a corrupted bootloader.
What caused the bootloop?
Click to expand...
Click to collapse
CM12 was installed then about 2 months later the screen was replaced (Phone was apparently completely drained), is there a way to fix a corrupted bootloader?
Have stumbled upon this https://www.ifixit.com/Answers/View/167884/iPhone+5s+-+Infinite+boot+loop+(after+screen+replacement
Hmmm this guy seems to have the same issue. I'm guessing a screw in the wrong spot causes some kind of short? Even though each screw had a different size and thread.
What do you think?

My device is broken - need help

I tried to flash a rom (Grapheneos) with fastboot, i tried with the newest plattform-tools und flashed with a flash-all.bat, so nothing should go wrong. after flashing boot.img and other files the device reboots in fastbootd and my windows computer doesnt recognize my phone.
This happens even if i try to flash the original FW for the Pixel 4 XL
Can someone help me pls?

erryKing said:
I tried to flash a rom (Grapheneos) with fastboot, i tried with the newest plattform-tools und flashed with a flash-all.bat, so nothing should go wrong. after flashing boot.img and other files the device reboots in fastbootd and my windows computer doesnt recognize my phone.
This happens even if i try to flash the original FW for the Pixel 4 XL
Can someone help me pls?
Click to expand...
Click to collapse
Could be a driver issue. Try plugging into another port, then go into device manager. Look for exclamation points.

erryKing said:
I tried to flash a rom (Grapheneos) with fastboot, i tried with the newest plattform-tools und flashed with a flash-all.bat, so nothing should go wrong. after flashing boot.img and other files the device reboots in fastbootd and my windows computer doesnt recognize my phone.
This happens even if i try to flash the original FW for the Pixel 4 XL
Can someone help me pls?
Click to expand...
Click to collapse
USB debugging enabled? Could be a driver/cable issue. Use a known good USB-A data cable, not USB-C to USB-C.
Flashing stock boot image to both slots usually gets you back into System.
All else failed? Try full OTA image in Recovery via ADB.

v12xke said:
USB debugging enabled? Could be a driver/cable issue. Use a known good USB-A data cable, not USB-C to USB-C.
Flashing stock boot image to both slots usually gets you back into System.
All else failed? Try full OTA image in Recovery via ADB.
Click to expand...
Click to collapse
Ive tried with different cables and also with windows and linux on my notebook so i dont think its a driver issue.
I also tried to flash boot image on all slots, this was succsefull but after reboot it starts in the Fastboot Mode with the Enter reason: no valid slot to boot.
I dont know what to do... Do you think some Smartphone Repair Stores can fix this?

Chance Ill said:
Could be a driver issue. Try plugging into another port, then go into device manager. Look for exclamation points.
Click to expand...
Click to collapse
Also check Windows Event Viewer to see if any errors are reported.
Sometimes reinstalling the driver does the trick.
And reboot Windows...