I am having issues with my Nexus 6. I am unable to get it to connect to any computer. Windows says the device is malfunctioning, but it charges okay. Windows gives the error "Device descriptor request has failed." It doesn't matter if I'm booted, in fastboot, or have the phone off, it gives that error.
What I have tried:
Toggled USB debugging, MTP, and PTP.
Nexus Root Toolkit to try to install the drivers
15 Second ADB Installer by Snoop05
Alternate drivers (Naked, Generic, PDA).
Each time I have tried new drivers, I have checked to uninstall anything using USBDeview.
Tried "Updating drivers"
Tried three different Windows machines.
Tried different USB cables
USB 2.0 and USB 3.0 ports
Cleared cache partition
I think I am down to two things: Factory reset or draining my battery all the way and letting the hardware reset itself. I am not confident that factory resetting it will work since this same message pops up in the bootloader.
I have researched the hell out of this and one person in this section was having similar issues but got it working when plugging it into their USB 3.0 port. If those last two things do not work, then I don't know how the hell I'm going to lock the bootloader to get it worked on--that's the only thing I have done to it as far as modification wise (/system is stock, no root).
Any help is greatly appreciated. This is so frustrating since using USB is our way of working on these damn things. If I could get root without having to use USB, then I could easily lock the bootloader back.
Does anyone know how to re-lock the bootloader without root or using USB? At least I could have it locked so I can RMA it.
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
bluh5d said:
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
Click to expand...
Click to collapse
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
dijit4l said:
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
Click to expand...
Click to collapse
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Tiptonian said:
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
Click to expand...
Click to collapse
Thanks for your reply. However, I have a hard time thinking that three Windows machines are experiencing the same thing. I have successfully gotten it connected before the 5.0.1 update to transfer ringtones. I even booted into Linux Mint and couldn't get it to connect either. It's like the controller is bad but it can still charge.
Also, I have followed every direction on your link at least twice already.
bluh5d said:
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Click to expand...
Click to collapse
Thanks for your suggestion. I have tried this and Windows refuses to use the proper drivers. It argues they aren't for 64-bit OS, but they have worked in the past. I almost got it to use some Samsung drivers, but after it installed, no change. The device is not reporting the details it needs to convey to the computer to start a proper driver setup.
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
HotInEER said:
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
Click to expand...
Click to collapse
To me, it sounds like you have a glimmer of hope. Have you tried a different computer? If you don't have a different computer handy, boot Linux from a flash drive and install fastboot and adb.
Related
Ok I spent a few days searching and I just can't seem to find anyone with the same problem!
I got a used T-mobile G1, can't bypass the activation screen (touching the 4 corners in the a certain order doesn't work, believe me i tried!) so I thought of installing the recovery through adb, except adb doesn't see it!
The only thing i see in Device manager or usbdeview is "HTC Android Phone Device" "K:\" under Portable Devices. I cannot update it to the Google drivers, not from here or from the SDK. I tried un-installing it, from device manager and from usbdeview.
I thought it might have been the data cable, so I ordered another one from a different seller off of ebay.
I think i should note that when in fastboot mode, pluging in the usb does not change where it says Serial0 to anything else. I would of thought it change to USB if cable is connected like the older HTC devices.
What am I doing wrong? You're help is appreciated.
Follow this guide, it should help you fix your problem.
Thanks for the reply. But I already tried this guide, every step.
First, this phone doesn't have a custom recovery, so I can't do any fastboot updates.
Second, windows does not accept replacing the HTC Android Phone USB Device with the usb drivers from the guide. It just says "The folder you specified doesn't contain a compatible software driver...". I'm using 64bit Win7 so obviously I'm using the 64 bit drivers. I tried 3 different downloads from different sites just to be sure the drivers weren't corrupt. The other odd thing is that the HTC ANdroid Phone USB Device is under Disk Drivers in the device manager...
Third, I tried uninstalling using USBDeview, but still Windows automatically installs drivers back as soon as i replug.
Fourth, I cannot bypass the Activation screen, so I can't set USB to debuggin mode.
I know it's hard to suspect that it could be the cable, but I ordered another one from different site just in case.
Most peeps say I should see 3 HTC devices in the device manager, but I don't. Only thing that pops up in there is HTC Android Phone USB Device under Disk drivers and "K:\" under Portable Devices.
Got another cable today and it still doesn't show any other device other then the one in Device Manager... I ran of out of things to try. Anyone can advise? It's possible that my device is defective even though it boots normally.
After playing around for a few days, ended up somehow rooting and flashing Amon's latest recovery and then BAM windows detected new device and install the ADB interface.
Hey guys, flashed Sinless 5.1.1 last night and ever since installing this particular ROM I'm unable to access my phone's folders via MTP or anything. I've tried re-installing drivers on my PC, rebooting phone and PC several times, trying to access my phone in ADB and fastboot... I can't even push or sideload a new ROM so I really don't know what to do!
Anyone got any idea what to try next and/or how to solve this?
Did you enable Developers options USB debugging?
If not go to about phone and click on Build number a
bunch of times. If that doesn't work install latest HTC
drivers.
Armeniandave said:
Did you enable Developers options USB debugging?
If not go to about phone and click on Build number a
bunch of times. If that doesn't work install latest HTC
drivers.
Click to expand...
Click to collapse
Tried both, to no avail.
EDIT: It was working fine yesterday on Insertcoin 4.3 ROM, so I'm copying that back to my phone via WIFI transfer, gonna flash that and see if I get USB access back.
rpalmer92 said:
Tried both, to no avail.
Click to expand...
Click to collapse
I'm actually running that exact ROM and my phone is seen on both my Mac and Windows 7.
Did you try a different USB port? Does a message pop up on your phone asking to trust your
computer? My computer wouldn't see my phone until I accepted that pop up.
If you've tried all that then give a little more info on your PC so we can diagnose it.
Armeniandave said:
I'm actually running that exact ROM and my phone is seen on both my Mac and Windows 7.
Did you try a different USB port? Does a message pop up on your phone asking to trust your
computer? My computer wouldn't see my phone until I accepted that pop up.
If you've tried all that then give a little more info on your PC so we can diagnose it.
Click to expand...
Click to collapse
I never saw any message pop up. I've tried 4 different USB 2.0 ports. My USB 3.0 ports aren't usable.
I am runnings Windows 7 x64 Ultimate with latest HTC drivers installed.
rpalmer92 said:
I never saw any message pop up. I've tried 4 different USB 2.0 ports. My USB 3.0 ports aren't usable.
I am runnings Windows 7 x64 Ultimate with latest HTC drivers installed.
Click to expand...
Click to collapse
Kinda stumped then! Only thing I can think is that you don't have the very latest drivers.
Can you ADB and see the phone? Check the following thread on how to do this.
(Sorry if you already know how)
http://forum.xda-developers.com/showthread.php?t=2365506
If I do "adb devices", nothing shows up. Simple commands like "adb reboot" respond with "error: device not found".
I've just flashed ARHD 31.6 (Android 4.3) and re-installed drivers and my phone still isn't recognisable. I'm lost!
Okay, big trouble now!! I just read elsewhere that it could be an internal storage corruption problem, so without thinking I formatted internal storage along with data and system in recovery and attempted to ADB sideload a new ROM and was going to start over. Stupid idea! ADB still isn't working so now I can't even sideload or push a ROM. All I have to work with now is fastboot and recovery, and my PC isn't recognizing either of them. Any ideas?
YOU AREN'T GOING TO BELIEVE THIS!!!
Girlfriend stayed over the weekend and happened to swap our USB cables over. She left and took my OTG cable and left me with her identical looking USB charge only cable.
Just tried my mother's Nokia cable and voila! Installing device drivers.
Now to sideload a ROM and start from scratch -.-
I know this thread is old but if someone stumbles upon it this is what I did.
New USB worked.
***While using the USB cord that wouldn't connect like it usually does, I re-installed HTC Sync Manager and it immediately recognized it.
www.htc.com/hsm
Got my phone about a week ago & got pretty bored of it so I wanted to root it and get a different ROM going. For some reason, I can't get the phone to connect to HTC Sync Manager though I updated the drivers. Any time the phone is switched into USB debugging, My HTC drivers fail to install. I have no idea how to solve this problem. Also when trying to get the Token ID using the command prompt, the device doesn't show up after using the command adb devices either. Need help please.
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
bigdaddy619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
HurtMeSole said:
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
Click to expand...
Click to collapse
Windows 8.1?
bigdaddy619 said:
Windows 8.1?
Click to expand...
Click to collapse
No, Windows 7, 64-bit.
HurtMeSole said:
No, Windows 7, 64-bit.
Click to expand...
Click to collapse
Check PM
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
HurtMeSole said:
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
Click to expand...
Click to collapse
Same problem here with an HTC One Mini. Its driving me mad!:silly:
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
Strangely enough, I literally just tried it on a different computer and everything worked exactly as it was supposed to. I had 3 computers in my home, none of which worked but got to work and the laptop they gave me worked just fine. Then I got on my gf's Mac and it went mostly smooth (even though it was difficult not being as familiar with the OS). My advice is do everything you're doing on a different computer until you see it without the ! in the device manager.
Boblud said:
Same problem here with an HTC One Mini. Its driving me mad!:silly:
Click to expand...
Click to collapse
Should try using a different computer. Worked for me after trying several computers.
BD619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
My experience may be helpful. I had no ADB driver, but Composite USB seemed to work. However, the driver install crashed. I needed to open my phone and answer the dialogs on my phone while the driver was installing. After that, everything is hunky-dorry (I know, showing my age).
I was having the same problem until I UNCHECKED the USB debugging mode and reconnected the phone to the computer. Drivers reinstalled and HTC Sync Manager (not HTC Sync--different program) recognized the phone. I had to answer dialogue on phone and then the USB debugging mode status changed itself to enabled. It's all working now, after hours of fiddling.
So basically I searched everywhere and found many people with this issue.
I tried everything everyone said.
From installing the drivers, to turning on developer mode.
Also fastboot mode is not working.
I hope my is not a hardware issue. I tried a new cable with the same results.
Anything else I can try?
I have been using FTP to transfer files but I want to root my phone and I can't.
MagilsugaM said:
So basically I searched everywhere and found many people with this issue.
I tried everything everyone said.
From installing the drivers, to turning on developer mode.
Also fastboot mode is not working.
I hope my is not a hardware issue. I tried a new cable with the same results.
Anything else I can try?
I have been using FTP to transfer files but I want to root my phone and I can't.
Click to expand...
Click to collapse
Did you enable USB debugging in Developer mode?
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Did you enable USB debugging in Developer mode?
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Yes, that didn't help either
MagilsugaM said:
Yes, that didn't help either
Click to expand...
Click to collapse
The last time I read about someone having a similar problem it was resolved by using an original cable. But I can't find the thread where this was discussed.
Sent from my OnePlus 3T using XDA Labs
Just to rule it out, after you connect your cable are you seeing the Notification with USB options and have you selected 'Data Transfer', (or whatever it's called)?
If you are seeing the Notification and the PC still can't see the device, uninstall whatever Drivers and ADB packages you currently have installed. Download the ADB package from Google and, when prompted, say 'yes' to installing the Drivers.
Make sure you try all your available USB ports.
Are there any Yellow exclaimation marks in Device Manager? Do you have the most recent Motherboard drivers from your Manufacturers website?
Dirk said:
Just to rule it out, after you connect your cable are you seeing the Notification with USB options and have you selected 'Data Transfer', (or whatever it's called)?
If you are seeing the Notification and the PC still can't see the device, uninstall whatever Drivers and ADB packages you currently have installed. Download the ADB package from Google and, when prompted, say 'yes' to installing the Drivers.
Make sure you try all your available USB ports.
Are there any Yellow exclaimation marks in Device Manager? Do you have the most recent Motherboard drivers from your Manufacturers website?
Click to expand...
Click to collapse
Yes, I updated the drivers too.
I tried uninstalling the google drivers and everything you mentioned.
No the notification doesn't show up and my device doesn't show up on device manager.
I am running windows 10 latest update.
MagilsugaM said:
Yes, I updated the drivers too.
I tried uninstalling the google drivers and everything you mentioned.
No the notification doesn't show up and my device doesn't show up on device manager.
I am running windows 10 latest update.
Click to expand...
Click to collapse
If you have a can of compressed air, try blowing out the USB port. There may be debris up there. It does sound like a Hardware problem. You really need to try it on another PC to know for sure.
You don't have any issues when charging?
Dirk said:
If you have a can of compressed air, try blowing out the USB port. There may be debris up there. It does sound like a Hardware problem. You really need to try it on another PC to know for sure.
You don't have any issues when charging?
Click to expand...
Click to collapse
The phones charges perfectly, I already cleaned out the port.
So, I still have this issue and I wasn't able to solve it. Pretty much the phone only charges, doesn't get recognized by any computer. I also tried my laptop and same thing happens. How do I find out if it's a hardware issue?
Is there any way to save the phone?
i got this too , stuck in recovery and fastboot because i cant connect my device in any pc
MagilsugaM said:
So, I still have this issue and I wasn't able to solve it. Pretty much the phone only charges, doesn't get recognized by any computer. I also tried my laptop and same thing happens. How do I find out if it's a hardware issue?
Is there any way to save the phone?
Click to expand...
Click to collapse
You can connect your PC to your phone without cables using ADB over wifi provided your phone is rooted and on the same wifi network as your PC.
I know this won't solve your hardware problem but it does allow you to move files between your PC and your phone using ADB.
Note that this doesn't work in recovery or fastboot modes.
Here's how:
On the phone using Terminal
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
On the PC in a command terminal
adb connect xxx.xxx.xxx.xxx:5555
...
adb disconnect xxx.xxx.xxx.xxx:5555
where xxx.xxx.xxx.xxx is the phone's IP address
To set the phone back to normal (optional)
On the phone
su
setprop service.adb.tcp.port -1
stop adbd
start adbd
Sent from my OnePlus 3T using XDA Labs
I fix using a old PC that a have connected and installed drivers before but was a windows 7 , I delet all drivers content about phones and USB and re installed again using the unbrick tools and drivers , plugged the phone in fastboot and magically was recognized again ..
MagilsugaM said:
So, I still have this issue and I wasn't able to solve it. Pretty much the phone only charges, doesn't get recognized by any computer. I also tried my laptop and same thing happens. How do I find out if it's a hardware issue?
Is there any way to save the phone?
Click to expand...
Click to collapse
You could also try using flash drive via OTG. This won't help you connect to PC/Laptop in any way, but could at least progress a bit that the phone hardware is okay for data part.
This problem start again , fortunelly im in nougat so if i go to dev options and change the usb charging to mtp his comes to charging again . I think this is the problem , the phone dont comes to mtp so dont "have" a device in windows to connect , with this im unable to make root and do anything in fastboot because my phone lock to usb only for charge
Hi guys,
I need to unroot my RP2 to send it in for repair, but I can't for the life of me get my fastboot drivers working in Windows 10 2004. I've tried various versions of the stock Google USB drivers (bootloader, of course), but the phone still shows up as "Android" in "Other devices".
Thanks in advance for any suggestions, fellas.
-edison
Try Samsung USB Drivers. Sometimes theirs work when Google's doesn't.
FQuimson23 said:
Try Samsung USB Drivers. Sometimes theirs work when Google's doesn't.
Click to expand...
Click to collapse
I downloaded their driver pack, but couldn't find any Android-specific ones. Any idea which one would work?
edison said:
I downloaded their driver pack, but couldn't find any Android-specific ones. Any idea which one would work?
Click to expand...
Click to collapse
https://developer.samsung.com/mobile/android-usb-driver.html
The issue is with the newest version of windows. I haven't tried the Samsung drivers. What worked for me was making a live usb install of FWUL. Then I could boot from the USB and everything worked.
I have Windows 10 Ver 20H2 installed and can confirm I have gotten ADB and Fastboot drivers WORKING, following the original installation instructions from Razer. It's not very clear, but be SURE to EXTRACT the files AFTER downloading from Razer. Follow the instructions CAREFULLY. I can't tell you how many times I've had to go back and re-read the directions to get it right. I went so far as to reinstall Windows 10 v.1909 on an external drive and issued commands that way, as a work around. Today, I decided to take a chance, and got everything working again.
MoPhoMike said:
I have Windows 10 Ver 20H2 installed and can confirm I have gotten ADB and Fastboot drivers WORKING, following the original installation instructions from Razer. It's not very clear, but be SURE to EXTRACT the files AFTER downloading from Razer. Follow the instructions CAREFULLY. I can't tell you how many times I've had to go back and re-read the directions to get it right. I went so far as to reinstall Windows 10 v.1909 on an external drive and issued commands that way, as a work around. Today, I decided to take a chance, and got everything working again.
Click to expand...
Click to collapse
i treid this with no luck
dokibull said:
i treid this with no luck
Click to expand...
Click to collapse
What errors are you seeing? No communication in fastboot mode? If so, your driver is not properly installed. Your phone MUST be in fastboot mode when installing the driver. If your phone is booted up, you;ll only be able to install the ADB driver.
Additionally, I should have gone back and edited this post. The issue I was facing "back then" was that I didn't follow the driver installation directions EXACTLY. It's a bit confusing, but if you follow it step-by-step, it'll get you there. Also DO NOT use a USB C to C cable or a USB-C port. USB-A 3.0 or slower is a must with this phone. Fastboot mode is VERY picky about which USB protocol and cable you use. Recently found this out with my Surface Pro7 and had to use a regular usb a-c cable going through a 4-port hub to communicate properly and get the correct fastboot driver to install.
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
MoPhoMike said:
What errors are you seeing? No communication in fastboot mode? If so, your driver is not properly installed. Your phone MUST be in fastboot mode when installing the driver. If your phone is booted up, you;ll only be able to install the ADB driver.
Additionally, I should have gone back and edited this post. The issue I was facing "back then" was that I didn't follow the driver installation directions EXACTLY. It's a bit confusing, but if you follow it step-by-step, it'll get you there. Also DO NOT use a USB C to C cable or a USB-C port. USB-A 3.0 or slower is a must with this phone. Fastboot mode is VERY picky about which USB protocol and cable you use. Recently found this out with my Surface Pro7 and had to use a regular usb a-c cable going through a 4-port hub to communicate properly and get the correct fastboot driver to install.
Click to expand...
Click to collapse
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
dokibull said:
so i turn off the phone. plug in to the pc, power on then volume down. i downloaded the drivers from the link, but if i trie to install the drivers(browse in the folder where thr driver is) windows says there are no drivers found for this device.
Click to expand...
Click to collapse
Open "device manager" with the phone in fastboot mode. Scroll down to "other devices" and you should see "Android" or something of that nature. Right click it and select "update driver" follow the steps on PG 3 of the PDF I sent you and follow them exactly. NOTE where it says to click "Have Disk". Most people click "Android Bootloader Interface" then click "NEXT" at the bottom, DON'T do that. You must click "Have Disk" and then follow the prompts that follow.
Also, did you make sure to set your "environment variables" in "windows adv. system settings? This is so windows knows where to find adb.exe and fastboot.exe to execute commands.
MoPhoMike said:
Open "device manager" with the phone in fastboot mode. Scroll down to "other devices" and you should see "Android" or something of that nature. Right click it and select "update driver" follow the steps on PG 3 of the PDF I sent you and follow them exactly. Or hit me up in chat to walk you through it over the phone. Also, did you make sure to set your "environment variables" in "windows adv. system settings? This is so windows knows where to find adb.exe and fastboot.exe to execute commands.
Click to expand...
Click to collapse
e
yes ,im that point where i browse for the drivers, i select the dowlnloaded drivers and windows says there are no drivers for the device
dokibull said:
e
yes ,im that point where i browse for the drivers, i select the dowlnloaded drivers and windows says there are no drivers for the device
Click to expand...
Click to collapse
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Tsuchimursu said:
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Click to expand...
Click to collapse
win7 did the trick
dokibull said:
win7 did the trick
Click to expand...
Click to collapse
welp. I'll try getting the fastboot drivers to work on my win10 for a whoile longer, I only have one PC and installing win7 would be a huge pain jsut for rooting a device... ^^;
thanks for the swift reply anyhow. Will keep that as an option in mind.
Tsuchimursu said:
I'm having the same issue with my Sony Pro-I (just here scrounging the webs for clues in other forums)
Got adb to work but windows refuses to recognise my sony driver folder as a valid driver for the device. Did you get past this point or give up? If you solved the issue, what helped?
Click to expand...
Click to collapse
Okay, simple mistake. Just had to follow the installation instructions more carefully, and not click "next" here, but go to a device list. I think this is where some of us think they know what they're doing and click forward
Tsuchimursu said:
Okay, simple mistake. Just had to follow the installation instructions more carefully, and not click "next" here, but go to a device list. I think this is where some of us think they know what they're doing and click forward View attachment 5708435
Click to expand...
Click to collapse
this didn't work for me
i tried on multiple windows 10 computers and mine just won't recognize, the driver just doesn't work. i tried on linux and i was able to get fastboot devices to recognize phone but when flashing, it just gets stuck on "sending boot", any ideas?