Related
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hello,
I hope that I am not asking a already existing question again, if so, please send me the link and I will follow the instructions there.
I could not find anything, so far, but I am nearly going mad after a day of trying to unbrick my phone.
So, I had CM 11 Snapshot M10 installed, the current clockworkmod, bootloader unlocked through htcdev.
Today I wanted to do a full wipe (including /sdcard, because there were tons of files which I didn't know, lately).
I don't know why, but i ended up wiping /system and /sdcard at the same time.
Now I don't have any system on the phone in order to boot and get adb or mount the phone as a USB drive, and no firmware on the phone which I could flash. I really have no idea how I can get any rom onto the phone, now...
I tried official RUUs ("Please download the RUU which fits your phone), ADB sideload with CWM ("no devices found"), ADB sideload with TWRP (same as with CWM), and now I am running out of ideas...
Does anyone have an idea how to or get ADB sideload working (USB drivers are installed on my PC, but it doesn't seem to work), or how to get a RUU wiorking (I would like to go back to the stock rom anyway, I miss sense by now), or any other way how to revive my phone?
I do have access to the bootloader, fastboot is working, and so is the recovery. Is there any information you would need?
It is an enrc2b international, no branding. CID is HTC__102.
fastboot getvar version-main outputs 2.18.401.3
I really hope that someone can help me out...
Moritz
Adb sideload needs up to 5min to recognise the device.
Or you flash twrp recovery. Which has mtp support (access via windows explorer)
If crusader's suggestion didn't work then:
Try to use a different USB port. If USB 2.0 use USB 3.0 and vice versa.
If that doesn't work too, try running cmd as admin.
Last resort : install Ubuntu or any other Linux distro, and install dev tools on it (check for guides ) .. I have a similar issue to yours when it comes to windows, restarting to Linux always works for me
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
elektrobastler said:
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
Click to expand...
Click to collapse
Someone posted his backup files somewhere here on the forums...
First look at your CID (found at the top of the boot loader)
And secondly you can just install sense-based ROMs like viper or revolutionHD (I think that's what it was called) .. RevolutionHD is just stock sense basically with a few performance improvements.
Thank you very much!
You really saved my day
I was able to install CM11 now, it booted.
I instantly shut it down again, though, because I will now try RevolutionHD.
Stock sense (especially the gallery and camera app, never found anything comparable so far) with a few improvements sounds just awesome.
Exactly what I was hoping for, but I never imagined someone had actuall done it!!
Downloading it now, I think this will stay my ROM for the next year(s), depending on how long my X+ will keep on working...
hello.
i think i have already tried everything to get fastboot on my pc find my device, but no luck.
I've got an old laptop with usb 2.0 + windows 8.1 x64 Pro and the same OS on my PC with usb 3.0 (according to some of threads, my CPU is i7 4770k and my MOBO is MSI Z87-G45).
I use my HTC Desire X every day and it is simply slow. I cannot try every ROM cause of need to flash boot.img. And i Dont have any idea how to get the fastboot recognize my device....
Maybe someone have some time to help mi wlak through this 'issue' idiot friendly? I'm really confused and i dont have any idea what to do.
my hboot is 1.25.** JB. S-ON. I have installed TWRP recovery.
:crying: halp
EDIT:
SOLVED. Windows 7 FTW.
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Will_Xda said:
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Click to expand...
Click to collapse
So,what did you do ?:d
evnee said:
So,what did you do ?:d
Click to expand...
Click to collapse
Installed a HTC sync like program named PDAnet, and updated the drivers from that program, once in fastboot mode device is recognized in pdanet and in a command prompt (adb). this only worked on a usb2.0 port though.
(didn't bother replacing usb3.0 drivers as suggested elsewhere as this has caused big issues for me before.)
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
matee89 said:
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
Click to expand...
Click to collapse
The device doesn't get recognized by Windows, it doesn't even show up on the connected devices list. The funny thing is that the phone actually charges, so it is not a dead usb connection...
I think that I'll have to replace the USB PCB...
Hello,
i tried to flash twrp to my i9100.
I had cm12.1 with cyanogen recovery and tried to apply update for :
"recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)"
and
"kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100"
but know my phone is not starting anymore.
I already know that i used 13 kernel for 12.1 system and that was wrong.
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
i9100cm said:
Hello,
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
Click to expand...
Click to collapse
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Now my S2 is getting recognized again.
But i geht the error code 43.
The device description is failured.
Kevin3014 said:
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Click to expand...
Click to collapse
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Abdullah Yusoff said:
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Read this thread, it has the answer to your question.
Hey, OP here.
So just updating my status, I bought and replaced the Micro-USB connector and everything is working now, the device is recognized by the OS and I'm able to use use Odin/ADB normally.
If anyone out there is having the same issue, I recommend buying a new Micro-USB PCB. This phone is from 2011, batteries and connectors might stop working...
Thanks everyone for helping me out!
Thyrr said:
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Click to expand...
Click to collapse
hey..if no method works for you i have simple way..to turn on usb debugging and for odin (means from this way odin will recognose your mobile)...just flash the new simple custom rom with lower android versions and then turn on usb debuging mode....thats all ...i also strucked in this problem but i did this and all works fine...sry for my bad english and typing
Hello,
I am currently in a dead end with my Poco F1, and would like to check with you before throwing it away.
I was using my Poco in version 12.0.3.0 with TWRP installed and root with Magisk. Due to the last days errors of apps that shut down when opened, I decided to reinstall the system using TWRP, but I made a mistake and installed version 12.0.2.0.
I don't know what installing this version did, but now the mobile isn't starting MIUI anymore, it's starting by default TWRP. Furthermore, something has been changed in the TWRP version installed that touchsreen it's not responding, so I can´t use.
The problem is worse since, for a long time the transfer of files to a PC via USB cable isn't working on my Poco, so Windows is not able to detect the mobile in fastboot mode either. I tryied reinstalling drivres in many ways, and still not working. The poco charges perfectly, so I don't think the problem is the USB conector, maybe is a motherboard related issue, so changing the connector I don't belive will solve the problem
Recap:
- I can't start MIUI (the version has been corrupted).
- I can't use TWRP (it has been corrupted and the touch screen does not work).
- I can't install from fastboot (Windows isn`t detecting the Poco with the cable connected).
- I don't think changing USB connector solve de USB data transfer problem.
Any ideas or should I throw away the smartphone?
For me it's a real pitty, because I don't like the new Poco F3 or others phones on the market, most of them don't have 3.5mm jack or microsd card slot, and are bigger, heavier and more expensive than the Poco F1.
Thanks to everyone.
slumpp said:
Hello,
I am currently in a dead end with my Poco F1, and would like to check with you before throwing it away.
I was using my Poco in version 12.0.3.0 with TWRP installed and root with Magisk. Due to the last days errors of apps that shut down when opened, I decided to reinstall the system using TWRP, but I made a mistake and installed version 12.0.2.0.
I don't know what installing this version did, but now the mobile isn't starting MIUI anymore, it's starting by default TWRP. Furthermore, something has been changed in the TWRP version installed that touchsreen it's not responding, so I can´t use.
The problem is worse since, for a long time the transfer of files to a PC via USB cable isn't working on my Poco, so Windows is not able to detect the mobile in fastboot mode either. I tryied reinstalling drivres in many ways, and still not working. The poco charges perfectly, so I don't think the problem is the USB conector, maybe is a motherboard related issue, so changing the connector I don't belive will solve the problem
Recap:
- I can't start MIUI (the version has been corrupted).
- I can't use TWRP (it has been corrupted and the touch screen does not work).
- I can't install from fastboot (Windows isn`t detecting the Poco with the cable connected).
- I don't think changing USB connector solve de USB data transfer problem.
Any ideas or should I throw away the smartphone?
For me it's a real pitty, because I don't like the new Poco F3 or others phones on the market, most of them don't have 3.5mm jack or microsd card slot, and are bigger, heavier and more expensive than the Poco F1.
Thanks to everyone.
Click to expand...
Click to collapse
Hello,
The issue with error of apps was probably due Webview which Google pushed an update and fixed it. For more infos read here.
Now, to the current problem...how did u flashed previous version? Clean installed or Dirty installed?
What Desktop system do you use? AMD or Intel? Your PC can detect the device while you are on TWRP? Do you have twrp.img on ur device so you can reflash it via TWRP?
Check my POCO F1 Ultimate Collection & Guides
Retrial said:
Hello,
The issue with error of apps was probably due Webview which Google pushed an update and fixed it. For more infos read here.
Now, to the current problem...how did u flashed previous version? Clean installed or Dirty installed?
What Desktop system do you use? AMD or Intel? Your PC can detect the device while you are on TWRP? Do you have twrp.img on ur device so you can reflash it via TWRP?
Check my POCO F1 Ultimate Collection & Guides
Click to expand...
Click to collapse
Thanks for your answer.
I noticed that the issue with the apps is due to webview after breaking my phone, next time I'll think things twice before flashing anything.
I did a dirty installation, I thought I was installing same version (12.0.3.0), but I was flashing 12.0.2.0 on top of 12.0.3.0 without cleaning.
I tried both desktop systems: my laptop with an Intel CPU, and a PC with AMD Ryzen 9 3900X. I also tried 5 diferent USB-C cables that are working perfectly with others Android devices. When I look for new devices in the device manager of windows I can't tell any diference on listed devices with or without connecting the Poco. As I said, maybe I have some hardware issue in the phone, because file transfer was not working for many months.
I can't install anything via TWRP because touchscreen don`t respond to mi fingers... I remerber that this happend to me years ago when I installed a wrong TWRP version, but don't know if that is the problem.
slumpp said:
Thanks for your answer.
I noticed that the issue with the apps is due to webview after breaking my phone, next time I'll think things twice before flashing anything.
I did a dirty installation, I thought I was installing same version (12.0.3.0), but I was flashing 12.0.2.0 on top of 12.0.3.0 without cleaning.
I tried both desktop systems: my laptop with an Intel CPU, and a PC with AMD Ryzen 9 3900X. I also tried 5 diferent USB-C cables that are working perfectly with others Android devices. When I look for new devices in the device manager of windows I can't tell any diference on listed devices with or without connecting the Poco. As I said, maybe I have some hardware issue in the phone, because file transfer was not working for many months.
I can't install anything via TWRP because touchscreen don`t respond to mi fingers... I remerber that this happend to me years ago when I installed a wrong TWRP version, but don't know if that is the problem.
Click to expand...
Click to collapse
Are you able to to connect your device while u are on TWRP? Your PC recognize it?
Retrial said:
Are you able to to connect your device while u are on TWRP? Your PC recognize it?
Click to expand...
Click to collapse
I tried to connect the device with TWRP opened, and in fastboot mode, PC don't recognize in any case.
slumpp said:
I tried to connect the device with TWRP opened, and in fastboot mode, PC don't recognize in any case.
Click to expand...
Click to collapse
Well, somehow you need to manage to flash MIUI again via TWRP or Mi Flash Tool.
Perhaps if you redownload latest twrp.img and latest official miui 12.0.3.0 and transfer them to USB OTG or external SD Card and then put ur OTG or external SD Card to your phone and flash it from TWRP. Since you was able to wipe system as u said before you will be able to flash twrp.img into "Recovery" make Clean Install (according my guide) and flash MIUI.
I'll try if connecting something via OTG make the phone responds, but the main problem with TWRP is that appears to be corrupted or something. I cann't use it because touchscreen don't responds to me, and nothing happens either if I try to use it with volume+ and volume- buttons, I see TWRP but I can`t interact with it.
Thanks again for your patience.
Retrial said:
Well, somehow you need to manage to flash MIUI again via TWRP or Mi Flash Tool.
Perhaps if you redownload latest twrp.img and latest official miui 12.0.3.0 and transfer them to USB OTG or external SD Card and then put ur OTG or external SD Card to your phone and flash it from TWRP. Since you was able to wipe system as u said before you will be able to flash twrp.img into "Recovery" make Clean Install (according my guide) and flash MIUI.
Click to expand...
Click to collapse
I tried using OTG cable in TWRP and nothing hapens, TWRP don't respond.
Seems that I'm in a dead end, I ordered an USB PCB spare part to try if is posible to repair the USB data transfer connection replacing it, becuase looks like is the only way I have of flashing a new clean rom.
slumpp said:
I tried using OTG cable in TWRP and nothing hapens, TWRP don't respond.
Seems that I'm in a dead end, I ordered an USB PCB spare part to try if is posible to repair the USB data transfer connection replacing it, becuase looks like is the only way I have of flashing a new clean rom.
Click to expand...
Click to collapse
If you have AMD system try the AMD Fix in my guide. Also try this guide to install drivers.
Finally I could solve the problem.
I bought a new part of the USB port PCB from aliexpress, I ordered one that claims to be original for around 15€, not the 2€ ones.
I replaced it and the data transfer is working again, so I could install the ROM via fastboot from my PC.
I don't beleive that the PCB I replaced is original, but works like it is, phone charges properly and seems that didn't loose signal.
Thanks to everyone.