Hi guys !
I've got a problem to install Pixel C fastboot driver. i followed this thread : [GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016) but i still doesnt work.
I try to install adb and fastboot driver with Wugfresh's Nexus Root Toolkit, then with the Google Drivers. I also intall the android SDK. But it's still not working! My device works with adb, i can see it, but not with fastboot, im stuck on the pixel c screen "Waiting to fastboot command", and when i try to do something, the program loop (search for devices). I even try to install ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3, but it's not working too.
Of course, EOM is unlocked and USB debbuging is active. I'm on windows 10 64bits. I'm running out of solution.
Thank for your help guys, ans sorry for my english !
If you're running Windows, make sure the drivers for fastboot are installed, for some reason they don't automatically install for me on Windows 10 and I have to manually install them.
Sent from my Nexus 6 using Tapatalk
I had the same issue. I had to disable driver verification in advanced startup.
I had many troubles unlocking and rooting the device, too.
Finally, this worked for me...
(My system is Windows 7 in a Parallels VM, why shouldnt this work on Win 10 too.)
First, I had to edit the driver files (used that from SDK), so Windows recognize it as Pixel C.
Here the link to the guide I found:
http://stackoverflow.com/questions/34775508/where-is-adb-driver-for-the-pixel-c
Now ADB is working.
The next problem was, that the Pixel C wasnt recognized in fastboot mode.
So there was an unknown device with a yellow triangle, in Windows Device Manager.
After awhile of "research" I found out, that I had to assign the driver manually.
What I did was (my Windows is in german, so dont know the exact english labels):
right click on the device
update driver
search for driver on the computer
now you dont point to the driver directory, instead choose "choose from a list of device drivers" (hope this translation is roughly right =) )
from there choose "Android Device" and then "Android Bootloader Interface".
This worked for me.
The last troublemaker was root.
The root guide in the General section worked, except for copying su.img to /data.
In TWRP ADB didnt work, so i had to copy it with the TWRP file manager (if another one has problems with this)...
Now everythings seems to work...
Try just the SkipSoft tool within XDA Pixel C forums. They have a driver section which may help. I had to use PDANet to get ADB to work.
Hi guys, im back again !
Just wanna thank you all for your help, especially WhatZitT00ya who find out how to resolve this (assign the driver manually).
Thanks guys !
Related
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed
Hi
ADK is working fine with my other devices, but my PC can't seem to install the drivers for Huawei Watch. The devices is in the device manager, but a little yellow triangle at the side, which means the device drivers are not installed.
I have tried Google, but the guides just say install the devices drivers but clicking update in Device manager with the xx file I downloaded, but windows can't see the file.
Thanks in advance
only pdanet drivers works for me for adb but in twrp i cannot connect to pc . how have you solved the issue i have same problem in device manager. tried more than 6 ways after googling pc
i've tried pdanet drivers 64bit on my win7 64bit version.
but the installation cannot continue.. did u success installing pdanet ? what version of your windows u have ?
why is this marked as solved because i dont see the solution. i just received my watch today and cant seem to get device manager to recognize any drivers.
PDAnet doesnt fully install because i cant install drivers
Minimal ADB and fastboot dont recognize any devices attached
Universal Naked driver 0.73 doesnt work even after modifying the android_winusb file
I even installed the Google USB driver from the SDK Manager, but i dont see anything on my machine.
ive had this watch for 2 hours and already frustrated as hell lol. can someone provide assistance?
thanks!
PS. im running this on Windows 7 64 bit and the watch is at LCB43B already
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
hendry said:
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
Click to expand...
Click to collapse
i was trying all day on my work computer which runs windows 7 x64 with no luck, but the watch was detected immediately on my windows 10 machine at home. strange.
Success!
I fixed my issue! I had the same issue everyone here mostly had. I could unlock the bootloader, but I couldn't get the Fastboot recovery to work because the drivers were not detected by Windows 10, or my other Windows 7 machine. Both machines installed a standard version of Google Android device drivers and boot loader drivers, but they were not detected by ADB commands once in the bootloader.
First I went here to download all the drivers, but got stuck:
http://www.thecountrycaller.com/37260-how-to-unlock-huawei-watch-bootloader-and-flash-twrp-recovery/
So what I did was ran the commands to reboot to bootloader, then flash commands for the recovery, left my device plugged in. Then I went into the Windows Device manager, and looked for the Android or Adb drivers loaded. I double clicked the driver, and clicked on uninstall driver, and told windows to delete the drivers. I then unplugged my device (still in bootloader mode), plugged it back and in windows instantly detected the ADB flash commands and boom, TWRP recovery completed.
Hope this helps some of you.
this did not solve my issue ive installed the drivers and nothing over and over can someone help me with the drivers please
thanks
running windows 7
tried to install every driver possible
Weird as it may be, I managed to get Hwatch to connect to ADB via USB by installing the watch as a Motorola Android Sooner Composite ADB Interface - in device manager-update driver-select from PC-select from device list-android usb device-motorola
Is there anything what i can do when my classic watch is NOT recognized on both pc and notebook? I hear no sound, i can´t see anything in device manager...any help?
Hi I`m using the huawei 2 LTE version - can I take the same driven from here or will that cause problems ?
---------- Post added at 08:11 AM ---------- Previous post was at 08:09 AM ----------
Is this may be a real help https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
MrHaPpY66 said:
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
Click to expand...
Click to collapse
Have you enabled oem unlocking from developer options?
I'm having the same problem. After going back to Oxygen OS (now 3.5.4) from MIUI 8 fastboot just doesn't work anymore. ABD works just fine (tried on Minimal ABD and Fastboot on Windows and ABD installed over Android Studio on Ubuntu. Fastboot did recognize the phone on Ubuntu but flashing TWRP resolved in a bootloop (tried the old and the new recovery image).
All drivers are installed on both Windows and Ubuntu (I even removed all drivers on Windows and added them again) and just to make sure everything gets installed I disabled driver signature verification on Windows, but as I said - still no luck.
Edit: Of course USB Debugging and OEM Unlocking is enabled (my bootloader is also unlocked since I already had tried out multiple roms)
Had the same Problem, Win10 is the Problem + the old OP Drivers + the new Update to Win10 etc.
Nothing worked, tryed everything. Created a Thread last week here also...
After that i created a new Partition and installed Win7 on it. All works fine, only thing is while Boot ur System u have to pick ur OS or it waits 30sec to boot up but thats ok.
Now i have Win10 for everything and i reboot to win7 for Fastboot/OP3
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Didnt tryed the last Tip.
KornY10 said:
Win10 is the Problem
Click to expand...
Click to collapse
Can't solve your problem, but OP3 fastboot does work in Windows 10. I did have to disable driver signature verification to install the driver in the first place, and you'll have to leave it off for the driver to stay functional, but it definitely works on Win 10.
I dont tryed ur Way, so yes after disable Driver sign. it works like u Said but i did not Test it.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
Same here
It's driving me crazy. I've updated from a rooted stock OS (incl TWRP) via full OTA directly to 3.2.7, which removed TWRP and root.
I now cannot enter a Fastboot mode which detects the USB connection. Thus I can't flash TWRP again and can't root my phone, making lots of apps unusable.
I've tried every suggestion on every thread but nothing works...
Sent from my ONEPLUS A3003 using Tapatalk
Also got kedacom on my device manager after automatic driver update but my phone still isn't recognised in adb devices, does everyone else's serial number show up?
You guys still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
Good that you found the solution..
Sent from my Xiaomi Mi 5 using XDA Labs
Well I didn't really solve the problem on win 10 so i just decided to use Ubuntu instead. Worked well
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
I tried that too, but didn't work. What driver did you select in Device manager?
superiscch said:
I tried that too, but didn't work. What driver did you select in Device manager?
Click to expand...
Click to collapse
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
SgtIcetea said:
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
Click to expand...
Click to collapse
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good ?
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Yeah that one. After disabling the driver signature verification you have to re install it, when it's not disabled windows just doesn't install it although it says it does. After I disabled it Windows actually showed a completely new window during installation to install the driver properly
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Man, had to just do it through my Ubuntu VM. Tried Win 10 Win 7, all gave me troubles.
Started Ubuntu, setup ADB and unlocked in a breeze
i have same problem
Hi friends,
I recently installed a fresh windows 10 latest build (16299).. I have 64 bit windows 10.. The problem is i cant install moto z play drivers on this build. I was able to install drivers on the previous build of windows 10 but on this build i failed... Motorola Device Manager is stuck at step 2 (Installing USB drivers)... I waited for hours but it is stuck... I tried closing and opening the app but still no luck... Tried restarting and then installing drivers but still no luck.. Everything else is installed perfectly including adb but i am unable to install moto drivers.... Can someone help... Without drivers i wont be able to even flash my device
Anyone??? I need to flash my device...please help
1) Install drivers from this topic https://forum.xda-developers.com/showthread.php?t=2588979
2) After that you will be able to manually assign Android ADB Interface driver to your phone in Device Manager
freeman_g said:
1) Install drivers from this topic https://forum.xda-developers.com/showthread.php?t=2588979
2) After that you will be able to manually assign Android ADB Interface driver to your phone in Device Manager
Click to expand...
Click to collapse
I already have adb installed and it worls fine...its just i am unable to install moto drivers on my pc... I even tried after disabling driver signature bull**** that was introduced in windows...
Those pack also contains proper ADB driver. You do not need separate Moto drivers, original ADB driver from Google will work fine too.
After installation connect your phone in fastboot mode to PC and go to Device Manger. Then update the driver of your phone in manual mode (when you have to choose from the drivers already installed on your PC) and choose Android ADB driver from the list.