Related
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?
So I got carried away with trying to get rid of that three dot menu button at the bottom of the screen and I've slowly managed to work myself into a really bad problem. I'm not necessarily new to this, I've rooted my Droid 2, Droid 3, and GS3, but this has been more complicated for me.
Anyways, my problem is, I was trying to wipe my phone so that I could flash a ROM. This is because I couldn't access my settings (I overwrote the original in an attempt to get rid of the multitask button). But while I was in CWM I factory reset it but I also accidentally deleted the system. My bootloader is unlocked, but now my phone is on and I can't get into recovery, and I'm assuming it's because the whole system is gone so there's nothing to boot.
Another problem I had (while my phone was able to boot up completely), Android File Transfer wouldn't work, I downloaded a rom for the settings.apk but it wouldn't let me transfer files between my computer and phone. I emailed the .apk to myself but since I couldn't access settings I wasn't able to pick my usual email (although now I'm thinking I should have just used the email I first signed in with). Not as much of a concern but input is still welcome.
I've looked up RUU but it looks like it's not available yet for Verizon. Any possible solutions would be MUCH appreciated.
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I'm stuck on the green HTC logo screen and the red warning about the bootloader. I can't boot into recovery anymore. By the way I'm using a Mac but I do have a PC running Windows 8 if there's solutions I could try
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
xerhoffx said:
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
Click to expand...
Click to collapse
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
n1234d said:
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Click to expand...
Click to collapse
I only have Windows 8 I believe...
xerhoffx said:
I only have Windows 8 I believe...
Click to expand...
Click to collapse
Try a different PC, worked for another guy whose pc wouldn't detect his phone. See if a pc with XP works..
ndulian increase
jingles98 said:
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
Click to expand...
Click to collapse
Where could I find a nandroid for Verizon? I feel like Verizon is the most difficult to find.
FIXED
I was finally able to boot into recovery and thank goodness had a CWM backup. Thanks for your input guys.
Was running stock 5.0.1 with a decrypted boot.img. Rooted, unlocked, modified build.prop, TWRP, Franco kernel. Lost ability to connect to a PC, so I can't update manually (that's for another conversation). So I need the 5.1 OTA. I unrooted through SuperSu, flashed stock recovery and stock kernel. Did a factory reset. For some reason, my build.prop stayed modified.
The OTA will download, but fails to install...simply saying "error." Any advice on what could be preventing the OTA from installing?? I was hoping this update would fix my device-to-PC connection.
Thanks
ryan4a said:
Was running stock 5.0.1 with a decrypted system.img. Rooted, unlocked, modified build.prop, TWRP, Franco kernel. Lost ability to connect to a PC, so I can't update manually (that's for another conversation). So I need the 5.1 OTA. I unrooted through SuperSu, flashed stock recovery and stock kernel. Did a factory reset. For some reason, my build.prop stayed modified.
The OTA will download, but fails to install...simply saying "error." Any advice on what could be preventing the OTA from installing?? I was hoping this update would fix my device-to-PC connection.
Thanks
Click to expand...
Click to collapse
Flash system.img and userdata.img and reboot.
gee2012 said:
Flash system.img and userdata.img and reboot.
Click to expand...
Click to collapse
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images without a PC or root access? Through stock recovery? Where do I find those files?
ryan4a said:
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images with a PC or root access? Through stock recovery? Where do I find those files?
Click to expand...
Click to collapse
Extract the Google factory image and flash both img`s in fastboot/bootloader, here is a guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
ryan4a said:
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images with a PC or root access? Through stock recovery? Where do I find those files?
Click to expand...
Click to collapse
You can't. You're pretty screwed to be honest, you'll need to have that other conversation about your USB connection now.
gee2012 said:
Extract the Google factory image and flash both img`s in fastboot/bootloader, here is a guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Thanks again. But this tutorial says
"Boot it in fastboot(bootloader mode) by pressing and holding Power Button + Volume Down at the same time.
Connect your phone to your PC through your USB cable."
Again, my device is not recognized by any computer, even in fastboot mode. Anyway to do this without a PC?
ryan4a said:
Thanks again. But this tutorial says
"Boot it in fastboot(bootloader mode) by pressing and holding Power Button + Volume Down at the same time.
Connect your phone to your PC through your USB cable."
Again, my device is not recognized by any computer, even in fastboot mode. Anyway to do this without a PC?
Click to expand...
Click to collapse
No, not possible without a pc i`am afraid.
gee2012 said:
No, not possible without a pc i`am afraid.
Click to expand...
Click to collapse
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
ryan4a said:
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
Click to expand...
Click to collapse
Does the phone boot-up? If yes enable usb debugging and you should get connected and the phone is recognised.. Test if the device is recognised in adb with cmd terminal: adb devices and in fastboot/bootloader: fastboot devices.
Try downloading the latest fastboot drivers, I had the same issue and until i installed the latest ones, it wasnt being detected.
ryan4a said:
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
Click to expand...
Click to collapse
Root modified system in a way that only reflashing the system image will fix. This was changed when lollipop launched.
---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------
Oh and if you decrypted, you'll have to flash boot img too.
gee2012 said:
Does the phone boot-up? If yes enable usb debugging and you should get connected and the phone is recognised.. Test if the device is recognised in adb with cmd terminal: adb devices and in fastboot/bootloader: fastboot devices.
Click to expand...
Click to collapse
Yes, phone boots up and runs fine. USB debugging is enabled, but still not recognized. At best, I'll get an "unknown device" in device manager. I can't get the Nexus Root Toolkit to recognize it either, even after using the USBDeview.
fkofilee said:
Try downloading the latest fastboot drivers, I had the same issue and until i installed the latest ones, it wasnt being detected.
Click to expand...
Click to collapse
Where would I get the latest fastboot drivers?
ryan4a said:
Yes, phone boots up and runs fine. USB debugging is enabled, but still not recognized. At best, I'll get an "unknown device" in device manager. I can't get the Nexus Root Toolkit to recognize it either, even after using the USBDeview.
Where would I get the latest fastboot drivers?
Click to expand...
Click to collapse
I use the Google usb drivers, they are in the /android-sdk/ Extras/Google/usb_drivers/ folder
Or, try this:
http://forum.xda-developers.com/showthread.php?t=2588979
gee2012 said:
I use the Google usb drivers, they are in the /android-sdk/ Extras/Google/usb_drivers/ folder
Click to expand...
Click to collapse
Thanks. That was one of the first things I tried. I downloaded the updated drives, but not sure I "installed" them. Still not recognizing my device on any PC or Mac. I'm hoping it's not hardware, because it charges fine when connected to a PC.
ryan4a said:
Thanks. That was one of the first things I tried. I downloaded the updated drives, but not sure I "installed" them. Still not recognizing my device on any PC or Mac. I'm hoping it's not hardware, because it charges fine when connected to a PC.
Click to expand...
Click to collapse
Try a different USB cable
cam30era said:
Try a different USB cable
Click to expand...
Click to collapse
That was one of the other things I first tried.
ryan4a said:
That was one of the other things I first tried.
Click to expand...
Click to collapse
Connect the device to the pc, if the phone shows up in device manager uninstall the device, disconnect and the reconnect the phone and choose manual usb driver install and choose the Google usb drivers and all should be ok.
ryan4a said:
I'm hoping it's not hardware, because it charges fine when connected to a PC.
Click to expand...
Click to collapse
Doesnt indicate anything. Data connection uses more USB pins than charging.. Double check your USB port to check for obstruction or pin damage.
Thanks everyone. I've tried multiple cables and multiple computers. Still nothing. At best, I can only get my phone to show up as an "unknown device" in device manager. Then when I manually install the Google drivers, it says "drivers already installed." Or it will install the drivers in like 1 second and finish. But still no connection. I'll keep trying. Otherwise, I'm screwed and will need to keep my non-rooted device on 5.0.1.
Anyone with the same issue ? I am stuck at the bootloader since I wiped out my system image I can get to the recovery but I don't have a way to transfer new ROM since phone wont detect USB (MTP).
I didn't have any image backed to restore to. Tried OTG cable/USB nothing worked
What are my options ?
rocco24 said:
Anyone with the same issue ? I am stuck at the bootloader since I wiped out my system image I can get to the recovery but I don't have a way to transfer new ROM since phone wont detect USB (MTP).
I didn't have any image backed to restore to. Tried OTG cable/USB nothing worked
What are my options ?
Click to expand...
Click to collapse
Hi... Is data mounted and MTP enabled in TWRP?
Is your phone detected while in bootloader?
Try: fastboot devices
If phone is recognized, download stock firmware of your choice and flash it...
5.1 said:
Hi... Is data mounted and MTP enabled in TWRP?
Is your phone detected while in bootloader?
Try: fastboot devices
If phone is recognized, download stock firmware of your choice and flash it...
Click to expand...
Click to collapse
MTP is enabled but phone is not detected at all
I can access the terminal in recovery mode but it doesn't support ftp command to download any firmware.
I guess I am doomed
rocco24 said:
MTP is enabled but phone is not detected at all
I can access the terminal in recovery mode but it doesn't support ftp command to download any firmware.
I guess I am doomed
Click to expand...
Click to collapse
Wait... I don't get it...
Are you stuck in recovery? Or bootloader?
Also you can't use ftp commands either in bootloader or recovery... I suggest you start by reading this thread to learn a few basics about Android commands and how-to :
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5.1 said:
Wait... I don't get it...
Are you stuck in recovery? Or bootloader?
Also you can't use ftp commands either in bootloader or recovery... I suggest you start by reading this thread to learn a few basics about Android commands and how-to :
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Sorry to confuse you I can get to the bootloader and the recovery no problem but when I try to reboot to the system it kept saying no OS installed. I don't have any ROM installed and I can't use USB cable since phone won't detect it. So I am stuck at back-end.
rocco24 said:
Sorry to confuse you I can get to the bootloader and the recovery no problem but when I try to reboot to the system it kept saying no OS installed. I don't have any ROM installed and I can't use USB cable since phone won't detect it. So I am stuck at back-end.
Click to expand...
Click to collapse
So...
What operating system is installed on your computer?
Did you already install adb/fastboot drivers?
In device manager, while being in bootloader, is your phone detected when you plug your USB cable?
Did you try different cables, USB ports?
5.1 said:
So...
What operating system is installed on your computer?
Did you already install adb/fastboot drivers?
In device manager, while being in bootloader, is your phone detected when you plug your USB cable?
Did you try different cables, USB ports?
Click to expand...
Click to collapse
I tried different cables/PCs nothing worked. I think my phone USB port is defected but what confuses me more is that it can be charged just fine but no USB connectivity
It is still under warranty but not sure if it will be honored since I have the bootloader unlocked.
rocco24 said:
Sorry to confuse you I can get to the bootloader and the recovery no problem but when I try to reboot to the system it kept saying no OS installed. I don't have any ROM installed and I can't use USB cable since phone won't detect it. So I am stuck at back-end.
Click to expand...
Click to collapse
Nothing happens in device manager when.you plug your phone? Even not recognized as an unknown device?
5.1 said:
Nothing happens in device manager when.you plug your phone? Even not recognized as an unknown device?
Click to expand...
Click to collapse
Nothing like said it is dead. I have another nexus 6 can connect easily to the PC I am pretty sure it is a phone issue.
Well, if you're 100℅ sure the USB port is damaged, there's nothing else than a repair that could bring your phone back to life... Good luck..!
5.1 said:
Well, if you're 100℅ sure the USB port is damaged, there's nothing else than a repair that could bring your phone back to life... Good luck..!
Click to expand...
Click to collapse
thanks for your time and help.
So the nexus 6 gets old now, may just check to clean your port
coremania said:
So the nexus 6 gets old now, may just check to clean your port
Click to expand...
Click to collapse
Tried that already it didn't work
Might be a driver problem.
Connect it your windows pc and check the Device Manager if it is detected as "Android" device. If so uninstall it and disconnect and reconnect it to the pc. Let windows install the MTP drivers.
aliinbox said:
Might be a driver problem.
Connect it your windows pc and check the Device Manager if it is detected as "Android" device. If so uninstall it and disconnect and reconnect it to the pc. Let windows install the MTP drivers.
Click to expand...
Click to collapse
This has already been discussed if you read the "few" previous posts ... Device isn't detected at all...
[EDIT: It's all good now... A stupid mistake of mine]
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Moischen said:
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Click to expand...
Click to collapse
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Mooatreides said:
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Click to expand...
Click to collapse
Yeah, good question... But it's too late for that now
Try another pc
emprazol said:
Try another pc
Click to expand...
Click to collapse
same thing
Manually install adb driver
Moischen said:
same thing
Click to expand...
Click to collapse
One time, I had such an issue with drivers, what I did is use a free VM machine software on Windows to install a Linux distro (or you could dual boot it), and from Linux it worked to detect my device.
On the other hand, there are really probably easier ways to fix your issue, but who knows, it may help and does not take too long.