Related
Hi everyone, I have an X10a and managed to get upto step 3 without any drama. Once I try to do step 3 however, it says that the device wasn't found. USB debugging is enabled and everytime I plug the phone in, the windows device manager thing comes up and tells me my phone is an X10i. Then it says there is an error and the new hardware might not function correctly.
I have the latest Pc companion and everything. Any ideas?
Phew never mind.Just needed to let windows do it's thing
Can you elaborate how did you overcome device not found problem in Step 3?
I have the same problem and tried with re installation of PC Companion, SEUPS and doesn't work.
After Step 2 both of my computers can't install proper drivers for the phone even though the SE PC Companion and SEUPS detects device.
For some weird reason Windows detects my phone SO-10B (or X10) as X10i in Device Manager and don't know why. I tried to install manually drivers through Device Manager but it wouldn't let me. I tried Step 3 procedure on 2 Windows 7 computers 32bit and 64bit.
I rebooted, I changed USB ports.
It just doesn't detects it
Help, please. I'm quiet desparate
Install PC Companion then it will work its got some needed drivers
If the device manager pops up and asks you what to do, let it install drivers. Just let it search automatically and as thor said, you need pc companion.
EDIT: What I did exactly was go into control pannel -> Printers and other hardware -> add hardware -> yes I have already connected the hardware. Then let it search for updates. It took a few minutes for me until it managed to find the drivers. I'm on 32bit XP by the way.
Guys I already wrote that I already reinstalled PC Companion and SEUPS.
I do have PC Companion installed and even updated to the newest version.
The device is now detected and installed correctly.
The only problem that Step 3.cmd still can't detected it on both of my computers (win 7 32 and win 7 64).
I even started the whole process from the beginning and I'm again stucked at step no.3
Here is screenshot.
hXXp://img143.imageshack.us/img143/4062/capturehul.jpg
Some other advices?
-USB Debuggining is enabled
-USB Storage is enabled (I tried with disabled)
-Both computers and phone were restarted between tries multiple times.
What should I do?
Mod. edit: There is a sticky for this kind of rooting related issues. Pls use that instead of opening new threads. CLOSED.
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.
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
I'm having the same problem
smithisize said:
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
Click to expand...
Click to collapse
Make sure your SDK is up to date, and that you are opening the command prompt from the proper location. Also make sure that USB debugging is enabled in developer options on the device.
I've had the same issue. I did all of the above and even tried on a Mac and adb still hasn't recognized my phone. Im on win 7x64. Still researching for an answer.
I'm not sure if this will hold true for everyone, but what worked for me was to updat the adp.exe and dlls. Then after I did that, ran the get token script from the toolbox, open the phone to the home screen, and accept the connection request from the computer.
I ended up having to just start the process over again on a different computer, but it worked, so I'm happy lol.
Regards
Smith
You can also try disabling USB Debugging and re-enabling it while the USB is connected. Works for me so far
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.
Hi. First of all I want to excuse me that I' m asking a common thing several times threated in other posts.
I'm working now 2 days on getting another rom on my lemax 2.
I have installed the driver for the phone on my windows 7. system manager shows a propper installation. ADB driver's have been installed. The phone is in developper mode and oem and usb debugging is turned on. I switched to MTP and to PTP to make my device visible for ADB. But when I'm trying to see if my computer shows the mobile phone in CMD with the following command "adb devices" there will never be something listed! I tried already a lot... Uninstalling drvers for ADB, tried different drivers... And so on... Does anybody have an idea to help me??
Same problem here. Phone doesn't show, ADB can't connect. I am starting to get frustrated.
Most likely a problem with the usb driver, did you try another phone? I had the same problems and ended up doining it under linux afther a couple of hours messing in win10.
http://askubuntu.com/questions/659880/ubuntu-15-04-adb-fastboot-impossible-to-install
DeScheep
MOB* said:
Most likely a problem with the usb driver, did you try another phone? I had the same problems and ended up doining it under linux afther a couple of hours messing in win10.
http://askubuntu.com/questions/659880/ubuntu-15-04-adb-fastboot-impossible-to-install
DeScheep
Click to expand...
Click to collapse
Linux definitely is the better choice.
The fastboot drivers are different from the ADB drivers, and in Windows 10 you might have to switch the driver after fastbooting the phone.
It's really really silly and took me hours to find out.
You can change them in device manager, find the USB device there and update its driver. You don't need one from the web, just take the fastboot one from the list that Windows offers.
Sörnäinen said:
Linux definitely is the better choice.
The fastboot drivers are different from the ADB drivers, and in Windows 10 you might have to switch the driver after fastbooting the phone.
It's really really silly and took me hours to find out.
You can change them in device manager, find the USB device there and update its driver. You don't need one from the web, just take the fastboot one from the list that Windows offers.
Click to expand...
Click to collapse
I have no second android phone to test. But I tried already on OS Win 7 & 10 with different drivers on Win 7 as well. On win 10 the driver was already given by Windows, no need to install. I think that the problem has something to do with the phone, but I can't find the problem. It must be something with authorisation, that Win Os will recognize the Leeco correctly to have access.
I finally found a good working driver for WIN 10. I found it from a Chinese chatting group, so use it at your own risk.
Below is the share link.
https://drive.google.com/file/d/0BxNNPNS50QQiUk50YTliT2p5Mmc/view?usp=sharing
You will need to boot your phone into bootloader, connect to computer, manually switch the diver via 'Browse my computer for driver software" -> 'Let me pick fromm a list of device drivers on my computer"-> "Have Disk".
Hi all,
After reinstalling Windows7 32-bit on my laptop, I ran into the same issue as you guys here. What I did was to install pdanet and the adb interface worked. However, I could not get into the QDLoader 9008 and also Diagnostic Driver was not working, simply the drivers could not get installed no matter what I tried. I searched quite a lot of time how to get make it work and looks like there was a zip "QDLoader HS-USB Driver". You can google it and it has 32-bit and 64-bit installations. I am not very sure if I had to install pdanet but that was the first step to make it work, at least to have adb.
I'm sure that you guys found the answer already, but I wanted to help others as well if they run into the same issue.
valy_cta said:
Hi all,
After reinstalling Windows7 32-bit on my laptop, I ran into the same issue as you guys here. What I did was to install pdanet and the adb interface worked. However, I could not get into the QDLoader 9008 and also Diagnostic Driver was not working, simply the drivers could not get installed no matter what I tried. I searched quite a lot of time how to get make it work and looks like there was a zip "QDLoader HS-USB Driver". You can google it and it has 32-bit and 64-bit installations. I am not very sure if I had to install pdanet but that was the first step to make it work, at least to have adb.
I'm sure that you guys found the answer already, but I wanted to help others as well if they run into the same issue.
Click to expand...
Click to collapse
Thanks a lot for sharing it !!! This helped me A LOT !! :fingers-crossed: :fingers-crossed: :fingers-crossed:
I have the same problem. Tried different drivers, two computers, win10 and win7. Nothing helps...
midirt said:
I have the same problem. Tried different drivers, two computers, win10 and win7. Nothing helps...
Click to expand...
Click to collapse
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
is there any solution for this problem........my device le eco letv 2s is not listed in the adb devices.....can anyone help me....
Dhatchina said:
is there any solution for this problem........my device le eco letv 2s is not listed in the adb devices.....can anyone help me....
Click to expand...
Click to collapse
if you're sure it's not a driver issue you can try the following (solved the problem for me):
on your windows machine navigate to "c:\users\<insert your user name here>\.android" and delete the file "adbkey".
either jump directly to the folder or turn on hidden/os files in explorer and navigate there.
now plug in your phone, the rsa-key dialog should pop up.
if not, that wasn't your problem.
btw. i'm using "universal adb installer".
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
It helpded me a lot. Thanx.
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
Great, man.!. It works for me
THIS Method Works For LeEco Le Max2
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
This Method Works Perfectly.... After Enabling the AT port.. the drivers begin installing immediately. Have Patience. They will all install.
LeEco le2 is not showing up under adb devices list... tried damn lot of drivers ...What do I do??
You should post a Screenshot of your devicemanager becsuse that information is not enough.
Gesendet von meinem Le X820 mit Tapatalk
Install ADB Driver installer 2.0
dhankhar13 said:
LeEco le2 is not showing up under adb devices list... tried damn lot of drivers ...What do I do??
Click to expand...
Click to collapse
adbdriver.com/downloads/
Use this above link
1 ) Download adb driver installer software zip file
2 ) Extract the zip file
3 ) Install & Run a adb driver installer.exe file
my le2 doesn't show up in fastboot mode, but shows up once booted into system. Any idea?
Thanks!
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
This worked for me too!!!:good::good::good: