Database Develop

Fastboot Troubles

I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?

my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one

I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.

Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...

That was a good idea, but I had no luck with that one either. Thanks though.

Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927

stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?

Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.

Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.

Phone won't connect to HTC Sync or adb

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.

Device not found in adb sideload or recovery trying to install 5.1 otc

So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......

Gage_Hero said:
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Click to expand...
Click to collapse
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I will try wugfish to install the drivers and then see if I can use ADB after that.... I definitely did not have the device show up as nexus 6 in device manager other than the mtp part... pretty hard for that not to show up..... I'll give it a shot on Sunday unless the ota drops to the phone first.

A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app

Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.

tvtodd said:
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
Click to expand...
Click to collapse
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.

z28 justin said:
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
Click to expand...
Click to collapse
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....

Gage_Hero said:
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Click to expand...
Click to collapse
I followed those instructions as well and it still registered as a Samsung Device. However, I did finally get it to work by going through my "Uninstall or change a program list" and removing a "Samsung Driver Installation" program I had installed for my wife's S4. Then I ran back through Wugfish's driver directions and sure enough, it finally registered as a standard Android device and not a damn Samsung.

I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!

Mephisto_POA said:
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Click to expand...
Click to collapse
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app

I don't know if this will solve your issues. When I was side loading the 5.1 update I couldn't get tmy win 7 machine to see the device after rebooting from adb to sideload.
I ended up finding a thread somewhere that suggested a newer version of adb. Once I downloaded the most recent version it installed fine.
I also rebooted into fastboot through adb, went to device manager and found my nexus, manually updated the driver. After all that everything worked fine.
Don't know if that helps or not....

I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.

Intub8 said:
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I found the problem
each mode has a unique hardware ID
when phone is in normal mode with USB debug, when it is at bootloader and then afterwards when it is in recovery mode
the last mode, hardware ID VID_18D1&PID_D001 didn't get any dirvers installed, evne downloading official drivers from google and other parties.
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
lukesdiesel said:
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Click to expand...
Click to collapse
https://www.reddit.com/r/nexus6/comments/2yyfri/nexus_6_not_getting_detected_during/
check this

got it to work
I got it to work by unplugging and plugging back in once I had hit the adb sideload option in recovery. When I was just in recovery it had no effect.
rkshack

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
thanks. this worked

Mephisto_POA said:
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
Click to expand...
Click to collapse
My device needed %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002.

This happened to me too, I just ended up using a different computer: https://plus.google.com/+LoganJonesJ/posts/hrDRAnyrotf

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Click to expand...
Click to collapse
Worked for me as well, thanks!

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Worked like a charm. Thanks!

A2CKilla said:
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much for this! I had tried EVERYTHING trying to get my 6P to connect with no success. This simple fix was exactly what I needed.

device not found in recovery

some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?

melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw

i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..

melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.

Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.

i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.

Windows 10 fastboot drivers not working

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?