Develop Bugs

ADB driver vs. USB driver

Hello,
Before I proceed using doomlord's rooting script. It says that the ADB driver needs to be installed.
Is the ADB driver the same as the USB driver?

Yes. I installed the drivers from the 'How to Root' thread (the one that uses Odin), and I was able to use ADB no problem. Assuming you are running Windows, of course.

funeralthirst said:
Yes. I installed the drivers from the 'How to Root' thread (the one that uses Odin), and I was able to use ADB no problem. Assuming you are running Windows, of course.
Click to expand...
Click to collapse
I think that's incorrect. In order to use adb you have to download and install the android sdk, and within the sdk manager download adb if not included in the sdk by default which includes the drivers.
Sent from my SGH-T989 using Tapatalk

iLeopard said:
I think that's incorrect. In order to use adb you have to download and install the android sdk, and within the sdk manager download adb if not included in the sdk by default which includes the drivers.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Obviously you need ADB installed, but it's going to use the same driver (for the phone) as the USB driver from Samsung. ADB is not a driver.
To use ADB you need both ADB from the SDK and the Samsung driver for the phone. ADB is not included in the SDK by default, you need to get it in the platform-tools package.

Can't install drivers.

Ok, this isn't my first rodeo as I've owned many android devices including the old nexus 7. I'm trying to unlock and root this but I can't install the drivers. I tried the device manager method and when I search it can't find anything and I tried a website to manually do it by downloading a zip and choosing it to no avail. Any one have the link to the drivers as that website may not of been accurate or anyone have any other suggestions?

You need to unzip it first.

Username invalid said:
You need to unzip it first.
Click to expand...
Click to collapse
Yes I did that and it only had two folders that showed up while browsing in the update drivers part in device manager. One was AMD86 and the other was i3 something and neither of those matched the picture in the steps but I used the link given within the same tutorial.

http://developer.android.com/sdk/win-usb.html

Username invalid said:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Ok I still cannot install the drivers. When I downloaded the file provided in that link, there are no driver options at all. There are only two folders in which I described in my previous post and neither have drivers in them. I'm no noob and have done this plenty of times, I even tried to adb reboot bootloader and it says device not found and yes USB debugging is on so I'm assuming I can't do anything until I some how install the drivers.

Which website guide are you looking at?

Username invalid said:
Which website guide are you looking at?
Click to expand...
Click to collapse
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-

C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
If nothing else works, you might consider partitioning your hard drive and installing a secondary OS. Both Windows 8.1 and Ubuntu worked for me no problem.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads

C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...

I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.

C-4Nati said:
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
Click to expand...
Click to collapse
Fastboot is all you need to root your device.

C-4Nati said:
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
Click to expand...
Click to collapse
I'm having a similar problem with drivers, why don't you post how you solved it? I am trying on 2 different windows 7 machines. google drivers don't load, asus drivers don't load. Device manager just says "windows could not find driver software for your device."
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
I figured it out, have to turn MTP on, then install drivers - then you can turn MTP back off if you want.

[Q] Stuck at CWM, USB mounting doesn't work, Can't copy ROMs over to the phone.

So, someone went and did something to my phone, I guess he deleted everything, and formatted the SD card, system folder, etc.
Now, I don't have any of my ROMS on my phone, and I'm stuck with just CWM. I cannot mount the USB storage using CWM, so I can't transfer any files over.
I'm using Windows 8.1, and I've tried installing the drivers using Flashtool. Installation of drivers was successful, but Windows still detects the phone as a "Xperia S" with an exclamation mark. Running Flashtool tells me I need to install the drivers from the driver folder. I installed the 3 drivers with Xperia S in its name, and the fastboot and adb drivers. Still doesn't work.
Any advice? Basically I just want to be able to copy a ROM over to the phone to install it, as I don't have any OS(?) on the phone right now.

You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.

pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app

monivan said:
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.

pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks. I'll try and see if I can find a Windows 8 or 7 machine. Not possible to do this in Mac, I suppose? Would a virtual machine work, you think?

markiemice said:
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.
Click to expand...
Click to collapse
Maybe u could try Sony Update Service, so that the fastboot driver might install properly through official software from sony.
Sent from my SGP321 using XDA Premium 4 mobile app

Is it save to assume that you have experience flashing ROM? Just asking coz sometimes we missed some obvious step.

Yes, I do. I've flashed using CWM. Mostly it's pretty easy, just copy the ROM onto the phone, and install it using CWM after clearing caches.

pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks for the idea to do a sideload! I used a virtual Windows XP, and was able to install a ROM onto my phone!
Thanks very much.

[Q] Need driver help for my KF - ADB is not detecting the device when in TWRP Mode

My KF is having some problems. I followed the tutorial from Cyanogen for the installation, and I got to the point where I finished flashing the recovery (twrp (don't know which version, it's from this site). I have a bootable device that will go into recovery, but when booting into standard Kindle OS, the device is unable to boot, and gets stuck on the KF logo. I am unable to use ADB to push the rom onto the device for flashing, and I cannot copy it manually because I cannot boot. My fastboot drivers are working, but when I go into Device Manager on Win7, my kindle shows up with the triangle + exclamation point. I can't update this driver as nothing works, and I've literally tried every possible solution on the internet.
thanks in advance

shameless self bump

Have you tried the drivers in my signature? You right click the device and hit update drivers and point it to where my drivers where extracted to use them.

I have tried your drivers - I tried that before coming here. When I extracted the driver files and pointed the install to the directory, it didn't give any install. It said drivers were not found and that's where I got stuck. Does the mounting of the internal storage not work in TWRP?

No it does not, you have to adb push them or adb side load them. If you tell me the vid and pid listed in the devices hardware id's on the details tab of its properties in the device manager maybe I can update my drivers to help you.

okay let me see:
do you want the pid and hid in TWRP mode or fastboot mode
in the hardware IDs these are listed:
USB\VID_1949&PID_0008&REV_0216&MI_00
USB\VID_1949&PID_0008&MI_00
Those are the two when booted into TWRP. If you need anything else like fastboot hid then I'll provide those as well.

shadowblade2652 said:
I have tried your drivers - I tried that before coming here. When I extracted the driver files and pointed the install to the directory, it didn't give any install. It said drivers were not found and that's where I got stuck. Does the mounting of the internal storage not work in TWRP?
Click to expand...
Click to collapse
You may be having a driver install problem. Windows 8/7 64bit must disable security enforcement. This is for Windows 7.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers the next time you restart your computer. Follow steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Now restart your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
You may be having a driver install problem. Windows 8/7 64bit must disable security enforcement. This is for Windows 7.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers the next time you restart your computer. Follow steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Now restart your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply but
I don't have drivers installed at all The kindle fire in the device manager shows with a little yellow triangle and exclamation and it says no compatible driver found. Fastboot still works though. Can anyone link me to the stock kfOS for me to reflash back to stock kindle fire?

shadowblade2652 said:
Thanks for the reply but
I don't have drivers installed at all The kindle fire in the device manager shows with a little yellow triangle and exclamation and it says no compatible driver found. Fastboot still works though. Can anyone link me to the stock kfOS for me to reflash back to stock kindle fire?
Click to expand...
Click to collapse
Fastboot is not gonna work if you don't have your usb drivers set up and your tablet recognized. Your tablet has to be recognized and that yellow triangle says it's not.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
Fastboot is not gonna work if you don't have your usb drivers set up and your tablet recognized. Your tablet has to be recognized and that yellow triangle says it's not.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
nonononono it's quite weird
In fastboot mode, the device is easily recognized by the computer. i can flash and have no problems whatsoever. When I try to use TWRP to copy the image to the device, that's where I get the issue.

shadowblade2652 said:
nonononono it's quite weird
In fastboot mode, the device is easily recognized by the computer. i can flash and have no problems whatsoever. When I try to use TWRP to copy the image to the device, that's where I get the issue.
Click to expand...
Click to collapse
If you want, copy and paste your environment path here. Let's check and make sure it looks good.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
If you want, copy and paste your environment path here. Let's check and make sure it looks good.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
And what do you mean by that? What is the environment path?
I know it can be flashed in fastboot as the computer recognizes it and fastboot detects it as a device. It's just that in twrp the computer is unable to find any drivers for it.

shadowblade2652 said:
And what do you mean by that? What is the environment path?
I know it can be flashed in fastboot as the computer recognizes it and fastboot detects it as a device. It's just that in twrp the computer is unable to find any drivers for it.
Click to expand...
Click to collapse
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
m8 I have no idea what you are talking about.
I started the cyanogen mod tutorial that they have on the wiki, and I got to flashing the custom bootloader and the twrp recovery mode. After that, the device wasn't recognized during TWRP mounting so I wasn't able to mount and copy over the CM image for installation. That's why I am stuck now. Could you please link me to or attach the kindleOS stock rom so I can flash it and go back to stock kindleOS. Right now I have an expensive brick and it's seriously bugging me.

LinearEquation said:
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Do you mean the windows path? If you do, I used the installer I found on this website along with the kindle fastboot drivers found from amazon and it was already added to the path.

another shameless self bump.

bump?

im facing the same problem here, i restored my kf hd 8.9 back to stock using this thread: http://forum.xda-developers.com/showthread.php?t=2468988
however, i just cant connect to the device via adb. fastboot is working, so the drivers are fine. adb has been enabled on the device's settings panel.
i need adb to root the device and reinstall the 2nd bootloader for custom roms.

It might actually be a driver problem, switching between twrp, fastboot, and a android os have caused issues for me before where I NAD to uninstall the driver and reinstall it, and sometimes it would have a USB composite USB device I'd have to remove to fix it(had a bird of 1949 so I new it was the kindle).

surprisingly restoring back to stock and then doing it again worked. I'm now running 4.4.4
Thanks for the help stunts, sjj, and linear

Question Pixel 6 pro drivers

Okay I got a problem I just got mine finally today in the mail. my Windows 10 recognizes it in ADB but as soon as I go to fastboot no matter what I do it's like it doesn't see the drivers anymore. Anybody have an idea how to get around this so I can unlock the bootloader?
Edit:. Nevermind I finally found a driver package that worked. What a deal

Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb

You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools

DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?

Flippy125 said:
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
I finally figured it out. Found the right drivers. Took me forever

DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked

mac796 said:
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
Click to expand...
Click to collapse
Please could you share the driver pack that worked for you?

Then just let us know which driver you installed so that the Pixel 6 was recognized. And a download link wouldn't be bad either - that helps others with the same problem.

Try Download Minimal ADB and Fastboot Tool it should work
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
After you install it ensure you update SDK Platform Tools the file name " ADB "
/c/adb

cd993 said:
Please could you share the driver pack that worked for you?
Click to expand...
Click to collapse
Yet Another Universal ADB Driver Package and adbupdater for Windows
I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before. While at it I added those two tools usually used, that is adb and fastboot. Based on batch scripts, so it's open source. Self Signed, not...
forum.xda-developers.com

Sorry took me a bit to find it again

mac796 said:
Sorry took me a bit to find it again
Click to expand...
Click to collapse
Thanks will give this a try later on!

On Windows 11 the official r13 Google USB Driver pack worked - but only after booting into an alternative mode that allows unsigned drivers. For some reason Google's drivers are not signed, and Win11, with TPM+SecureBoot refuses to load those drivers in normal mode.

cd993 said:
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Click to expand...
Click to collapse
It sounds like you're talking about accessing the phone's storage via MTP. When you plug the phone into the computer, you may need to choose the new notification regarding charging and switch it to the mode to be able to access the storage. Probably defaults to "Charging this device via USB", and you need to click on it and select something like "File transfer/ Android Auto". This won't require any new Windows drivers.
Please correct me if you're not talking about accessing the phone's storage.

mac796 said:
I finally figured it out. Found the right drivers. Took me forever
Click to expand...
Click to collapse
Would you mind saying WHICH drivers? Thanks...

wsalopek said:
Would you mind saying WHICH drivers? Thanks...
Click to expand...
Click to collapse
I posted it in this thread. Read it. There's a link

mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
OK...thanks...got it.

mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
wsalopek said:
OK...thanks...got it.
Click to expand...
Click to collapse
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.

roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).

My problem ended up being that my USB Hub went bad... Was getting Yellow Exclamation in Device Manager and an error when going into Fastboot. Once I plugged directly into the PC, no issues. New hub ordered!