I had a lot of trouble getting the adb drivers on my work Win7 x64 laptop working. Here's what seems to have done the trick.
1. Pull up a commandline, go to Documents and Settings\username\.android directory, and do
Code:
echo 0x04e8 >> adb_usb.ini
if you haven't done so already.
2. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
3. Set device in adb mode (Settings | Applications | Development | USB debugging(x)).
4. Plug device into computer. You will get a tray icon with stuff spinning. Click on it. If things go fine, you'll eventually see a list of drivers with "Ready to use" and green checkmarks.
If all the drivers have checkmarks, you're done--you had it easy. This guide is for cases like mine where you find that two drivers, "CDC Serial" and "SAMSUNG_Android" are labeled "No driver found" and adb doesn't work.
5. Right-click on My Computer, choose Properties, then "Device Manager". Expand "Other devices".
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).
Man, thank you so much. I was going crazy with this. Worked for my T-mobile SGS3. :cyclops:
One thing that's not mentioned, after I fixed the ADB and the CDC driver, it threw an error in the MTP device, I just let Winblows install that one automatically and it worked fine.
There is less steps needed,i got my ADB working in Windows 8 64bit RC1 developer preview flawlessly.
Just disable driver signature,install sdk,add sdk folder to windows environment and you are done.
nice. I didn't have any problems with mine, just sayin. Its always nice to see people help each other.
Sent from my SPH-D710 using xda premium
Worked perfectly on my PC and the Kies could see the phone as well (GT-I9100).
Thanks again !! :good:
Longest ADB guide I've ever seen.
Sent from my sph-d710 using xda premium
Thanks for this!
Great guide man! Helped solving some driver issues with Windows 8.1 and Note 3, particularly installing the SAMSUNG_android adb device manually!
Thank you very much!
I thought I would never find a tutorial like that, it saved my life lol. Thank you so much!
Related
This is outdated and doesn't work! Go here for new one.
This is a quick guide for users who are unsure about how to switch between ADb & HTC Sync without risk. New sections will be added as new drivers are made aware to me.
It is tested using Windows 7 64-bit but should be easily applicable to Windows Vista and similar to Windows XP. Includes 32-bit & 64-bit version support.
Before you do anything download the Android SDK and extract the files: http://developer.android.com/sdk/index.html
Contents
I. [NEW] Assumes that no driver is installed for you're HTC Hero
II. [HTC Sync] For when the "My HTC" driver is installed > ADB
III. [ADB] For when the "Android Composite ADB Interface" device is installed > HTC Sync
IV. Bootloader Driver Procedure
I. New Users
1. Plug your phone into your PC via the USB cable
2. Let windows install any drivers it wants, and it should fail on the last driver "adb"
3. Download the "HTC Hero Sync Drivers.zip" file attached and extract the folder to the android sdk folder.
4. Left Click "Start"
Right Click "Computer"
Left Click "Manage" from the menu
5. Choose Device Manager from the list on the left and you should have a warning ! over a device called ADB
6. Right click on that and choose "Update Driver Software"
7. Select "Browse my computer..." > "Let me pick from..." > "Next" > "Have Disk..." > "Browse"
8. In the browse window, navigate to the folder that you extracted from the rar earlier and pick either the "Vista_7_x64" folder (64-bit users) or the "Vista_7_x86" folder (32-bit users) and select the driver file from inside that folder. Then click "OK".
9. "My HTC" should show in the "List of compatible hardware" now, so select that and click "Next" to install the driver.
10. You now have your HTC Hero set up for HTC Sync.
II. HTC Sync Users > ADB
1. Plug your phone into your PC via the USB cable
2. Download the "HTC Hero ADB Driver.zip" file attached and extract the folder to the android sdk folder.
3. Click "Start" > Right Click "Computer" > "Manage" > "Device Manager"
4. Expand "Android USB Device" and right click "My HTC" > "Update Driver Software"
5. Select "Browse my computer..." > "Let me pick from..." > "Have Disk..." > "Browse"
6. In the browse window, navigate to the folder that you extracted from the rar earlier and pick "android_winusb" > "OK"
7. "Android Composite ADB Interface" should show in the list of "compatible hardware" now, so select that and click "Next" to install the driver.
8. You now have your HTC Hero set up for an ADB connection.
III. ADB Users > HTC Sync
1. Plug your phone into your PC via the USB cable
2. Download the "HTC Hero Sync Drivers.zip" file attached and extract the folder to the android sdk folder.
3. Click "Start" > Right Click "Computer" > "Manage" > "Device Manager"
4. Expand "Android USB Device" and right click "Android Composite ADB Interface" > "Update Driver Software"
5. Select "Browse my computer..." > "Let me pick from..." > "Have Disk..." > "Browse"
6. In the browse window, navigate to the folder that you extracted from the rar earlier and pick either the "Vista_7_x64" folder (64-bit users) or the "Vista_7_x86" folder (32-bit users) and select the driver file from inside that folder. Then click "OK".
7. "My HTC" should show in the list of "compatible hardware" now, so select that and click "Next" to install the driver.
8. You now have your HTC Hero set up for HTC Sync.
IV. Bootloader Driver Procedure
(thanks to janhol)
1. Turn off your phone and load into fastboot by holding the Back button and pressing Power with the hero plugged into the computer
2. "Start" > Right Click "Computer" > "Manage" > "Device Manager"
3. Check that you have your Hero on the "My Hero" Drivers, not "Android bootloader drivers" (those don't work).
4. Right click "Android bootloader drivers" > "Update Driver Software"
5. Select "Browse my computer..." > "Let me pick from..." > "Have Disk..." > "Browse"
6. Download the "HTC Hero Sync Drivers.zip" file attached and extract the contents
7. In the browse window, navigate to the folder that you extracted from the rar and pick either the "Vista_7_x64" folder (64-bit users) or the "Vista_7_x86" folder (32-bit users) and select the driver file from inside that folder. Then click "OK".
8. "My HTC" should show in the list of "compatible hardware" now, so select that and click "Next" to install the driver.
Windows 7 64bit
I get an error message "AdbWinApi.dll is missing from your computer"
Where do I get it & where do I put it when I get it
Interesting, it should be in the driver package, are you sure you extracted it all & picked the x64 folder?
O and which guide are you following? 1, 2 or 3?
any love for 32 bit?
btdag said:
Interesting, it should be in the driver package, are you sure you extracted it all & picked the x64 folder?
O and which guide are you following? 1, 2 or 3?
Click to expand...
Click to collapse
Extracted both rars to desktop
Tried all three
No luck
mercuryhayes said:
any love for 32 bit?
Click to expand...
Click to collapse
32-bit drivers are included as well - it is detailed in the guide.
Archie The Leper said:
Extracted both rars to desktop
Tried all three
No luck
Click to expand...
Click to collapse
Found the files it is asking for, I had no idea it needed that folder too. I'll edit the guide asap.
Edit: can you try it again? i have updated the guide
Bang on tutorial,... yet again!
Had to do my first logcat today,... Wouldn't have been able to if it wasn't for you.
Thanks again bruv!!!
cheers btdag, spot on man, can't go wrong with a tutorial as simple as this.
got my htc driver accepted by windows vista,moving on to next step.
thanks again,
many thanks btdag,great tutorial for us noobs
backedup all my apps to a 16gb card cos some of them i paid for. and then used a 2 gb card for the procedure.
-1st step: failed backup recovery image, followed the tuto...gold card,worked nicely.downgraded the hero using goldcard nice. many thanks to you and all the devs in here.
as for the roms, i don't know which one, too many roms are customed for different things from what i've read in the forum.
can you please advise, and can i take the 2 gb card that i used for rooting and put my 16gb and reinstall the backedup apps i have on it and then put in the new roms i hope you'll advise me on.
maybe too much to ask for, i thought having a 16gb class2 card to put everything on it(apps,music,......) bit too late i bought this one last week, hopefully in the future i get a higher class one.
from what you quoted the radio did improve your network signal,that will be great too. i'm with t-mobile uk.
cheers again for all the great work you've put in
may I add: after downloading necessary files i disconnected from the internet, then uninstalled ADB driver. Update driver with downloaded files and now driver used is MY HTC. It was very important to be offline as Windows 7 was very quick at downloading wrong driver for the phone.
I'm now back in business, rooting and flashing
for some reason it won't let me use the adb drivers, it simply says android_winusb isn't a suitable driver
don't get me wrong, it's not the first tem I mess with drivers, but it's like these drivers are not for my device.
I even tried the newer ones which by villain team.
I really don't get it
poddo said:
for some reason it won't let me use the adb drivers, it simply says android_winusb isn't a suitable driver
don't get me wrong, it's not the first tem I mess with drivers, but it's like these drivers are not for my device.
I even tried the newer ones which by villain team.
I really don't get it
Click to expand...
Click to collapse
+1 I get exactly the same, following guide to the letter - Do I need to force windows to accept unsigned drivers. I forget how but is that the case?
I love the ways you followed the guide to the letter but missed the HUGE announcement at the top that it is outdated and probably doesn't work any more....
See the adb guide in my sig now (by ante0)
This thread has been locked by OP request as it is out of date.
See http://forum.xda-developers.com/showthread.php?t=757233 for the new guide.
P
I try to unlock my My galaxy nexus bootloader but every time i connect my phone to pc in fastboot mode, it appears nothing. I had tried many google usb driver yet it didn't help. Can anyone suggest me solutions?
In fastboot mode it said:
Product name - tuna
variant - maguro
HW Version - 9
Bootloader version - PRIMEKK15
Baseband Version - SC04D0MLE3
Carrirer Info - None
Serial Number - 0146B0000E01701C
Signing - production
Lock State - Locked
There is number inside this device: SC-04D <Titan Silver>
It's currently running adroid 4.1.1
Build number: androidME_v1.2_GNexus-build_cdtdroid
Are you in windows, linux, or mac? I had a problem getting it to install the fastboot driver for my GalNex on my Asus G73 laptop in windows so it might be a similar problem. What I did was download and install the android sdk including the optional google driver, and then manually install it from the device manager. If you've installed drivers from different sources windows caches them and when you connect a new device it may use the old driver even if you've uninstalled it.
To install the driver manually make sure the phone is connected and in fastboot mode
then go to control panel -> system -> device manager
then select whatever the galaxy nexus is listed as. probably samsung phone or something along those lines.
right-click and select "update driver software
click "browse my computer for driver software" then "let me pick from a list of driver software on my computer" and finally click "Have disk..."
this will open a window for you to select the driver so hit browse, and in the explorer window go to the android-sdk folder where you installed the sdk and find the %android-sdk%\extras\google\usb_driver folder. then select the "android_winusb.inf" file. After clicking ok and ok it should list 3 drivers. I can't remember which one it is but I think one of them is a fastboot driver (If I remember correctly they're adb, composite-adb, and fastboot).
After it's installed open a command prompt and put in "fastboot devices". if there's a device id listen then it's working.
edit: the driver I refer to can be acquired here: http://developer.android.com/tools/extras/oem-usb.html
it says "The Galaxy Nexus driver, however, is distributed by Samsung (listed as model SCH-I515)." but that refers to the Verizon version.
it's working
Thank you I followed you instruction and it's amazingly working :victory:
This may help... it worked for me...
The reason the driver isn't being recognized by Windows, is that you need to edit the android_winusb.inf file. Let's now go through some simple steps to show you how to enable the Android Composite ADB Interface.
1. Download and Install Google USB Driver (yes, the generic Google USB driver, even though the Galaxy Nexus uses the Samsung USB driver in normal USB mode)
2. Next go to Device Manager and right click on Android 1.0 driver and click Properties
3. On the 'Property' drop down look for 'Hardware ids'; you should see two values like this:
USB\VID_18D1&PID_4E30&REV_0100
and
USB\VID_18D1&PID_4E30
Write down the USB\VID_18D1&PID_4E30 you will need to copy this to android_winusb.inf
4. Go to the USB driver folder and open android_winusb.inf with notepad and create a new line under 'Google Nexus (generic)' adding the above PID as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E30
*Note: There are two sections where 'Google Nexus (generic)' is found; add this line under both the "Google.NTx86" section and the "Google.NTamd64" section if you are uncertain.
Now save the file to same location
5. Next, go to Device Manager (Computer Management) > Other devices > Android 1.0
Right click on Android 1.0 driver and click 'Update Driver'
Browse to the USB drivers folder and open android_winusb.inf (Use Browse my computer for driver software)
6. Windows will present you with a pop up saying "Windows can't verify the publisher of this driver software"; click > Install this driver software anyway
7. You should now see a message "Windows has successfully updated your driver software"; make sure the driver description looks like this > Android Composite ADB Interface; then click > close
8. Device Manager will now label the device driver > Samsung Android Phone > Android Composite ADB Interface
my galaxy nexus is'nt showing in pc...its charging...but cant connect in download and fastboot mode...even not showing in device manager...tried diiferet usb cables...plzzz help me...sorry for bad english
Thanks for instructions. It worked.
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
This guide can be helpful. It clears out 'ghosts' of past device connections.
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
Also Wugs toolkit has a really good guide to cleaning out drivers. Then stop short of installing drivers. Then Windows should auto configure MTP drivers when You plug in the device.
I also make sure that I have deleted any drivers in uninstall programs in the Windows control panel.
Its a lot of steps, but it can save time over try this, try that. It returns your computer to like an Android device had never been plugged in before. Now any routine to install drivers (after the device is recognized as an MTP device) should go smoothly.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
My Device Manager shows NO Nexus devices of ADB interfaces, so I'm stumped at step 1.
I love CM11 but I'm just not having great service anymore like I did with the Fire OS... Now here is the question... I have the At&t version with 464 installed... Then installed the CM11 now is it possible to install 463 OS from the unlocked version so that I can install the play store and Google services... Amazons app store lack a lot of apps I currently use... If so how do I go about doing that?
1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
4. If you have trouble getting your device recognised after entering recovery / ADB sideloading mode:
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) ADB, Fastboot and Drivers
It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Bingo,
Thanks for the guide, but I cannot get my computers to recognize the Phone in recovery ADB mode. It shows the device description as SD4930UR. It only shows as unknown. The hardware IDs are VID_1949&PID_0800. I tried the linked tool (both the 1.4.2 and 1.3 version he had) and the google drivers.
What is the exact driver that works for you?
wats2u said:
What is the exact driver that works for you?
Click to expand...
Click to collapse
I used the "15 seconds ADB Installer" v. 1.3, so the OS used the drivers from there (on Win 7 x64). Use a USB 2.0 port, just to be sure.
The drivers that work on my system might not work for your configuration...
Are you using Win 10? If so, have you tried updating the drivers with the integrated update function?
g0tNoodles said:
It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one, which also needed updating which I have just done and appears to now let the CMD see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now.
Click to expand...
Click to collapse
I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
powerlocked said:
In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface
powerlocked said:
I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface
Click to expand...
Click to collapse
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.
Bingo Bronson said:
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.
Click to expand...
Click to collapse
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
EDIT: For anyone that struggled as much as me to finally get drivers to work, this method ultimately worked as posted by @hijax2001
4) I also grabbed the Kindle Fire ADB drivers from here for convenience in Step 7 (below) https://docs.google.com/file/d/0B1Z1J6LQic8PQjFjS0FpVGVia2M/edit
7) For me, ADB did not initially detect my phone. I ended up having to go into Control Panel in Windows, to Device Manager, find the Fire phone, choose Update Drivers, then Browse My Computer, Let Me Pick, Show All Devices, Have Disk, then find the folder from Step 4 (above) and add Android Composite ADB Interface by hand. Once I did that, I unplugged and replugged the USB to the phone and then typed "ADB devices" again at the ADB command prompt, like in Step 6. There it is! Ok, next step...
ElQuixote said:
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
Click to expand...
Click to collapse
I'm not familiar with adbdriverinstaller, but which ever you use, make sure you are running the installer as admin (right-click on the installer). Also, if you extract the 15 second installer exe with 7zip you get access to the drivers installers separately. Maybe try manually installing them.
DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface
Click to expand...
Click to collapse
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.
Bingo Bronson said:
1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I tried this method, to install 4.6.3 unlocked over my ATT (now carrier unlocked) 4.6.4. After I sideloaded, I get the following lines in Recovery, indicating that this didn't work. Any thought? Is there something else I need to do to be able to install the GSM on the ATT version?
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted
EDIT: Determined that the file I originally downloaded may not have been complete and sure enough a second version is larger...
powerlocked said:
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.
Click to expand...
Click to collapse
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
Those steps are for Google USB driver. For Amazon Kindle Fire USB driver, use the following steps:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.
jack9955 said:
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.
Click to expand...
Click to collapse
Ohhhh okay thank you for explaining this. After finding KindleFire down the list I was able to update my drivers. I've now installed the update to both of my ATT Fire phones, and both are now 4.6.3 and working great with working playstore options.
Thank you jack9955 and everyone else for the tutorials.. much appreciated!
How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.
DePingus said:
How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.
Click to expand...
Click to collapse
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.
jack9955 said:
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.
Click to expand...
Click to collapse
I've also noticed some people using the Amazon drivers. But they're not included with "15 Seconds ADB".
Works seamlessly too on any linux terminal
Just, so you know, your method works very well too on any linux computer. I had the same issue and now it is fixed. I can write a tutorial complimenting this if needed.
hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks
csx21 said:
hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks
Click to expand...
Click to collapse
We can't do CM12 because the Fire Phone's bootloader is still locked and the current FireOS 4 is based on KitKat. Unless Amazon unlocks the bootloader or releases FireOS 5 for these phones, we are stuck in KitKat (CM11).
Will applying update from adb format the phone..hopefully it will
I have my new Nexus 5X with Android 6 on it. I am trying to unlock and root.
I have enabled USB debugging and OEM unlock.
I have downloaded and installed the SDK package with Platform-Tools and drivers in the 'Extras' folder.
When first plugging in the phone I install the drivers with the 'Have Disk' and browse method.
Every time, installing the driver returns an Error 'Code 10 - device cannot start. 'Android ADB interface' shows up in device manager when I plug in the phone but with an exclamation point.
I have uninstalled, downloaded fresh drivers from other sources, reinstalled, tried plugging the phone in while in 'recovery' mode (starting by pressing all 3 hardware buttons).
I uninstall every time and reboot both the computer and the phone. The drivers simply won't work.
What is going on here? Is the phone/Android 6 still too new to unlock and root?
P.S. I should also say that I go into Developer options and change the Select USB Configuration between PTP and MTP (between which, I have not seen mention of the correct choice. Does it not matter?) - I cannot chose the others RNDIS, Audio Source, or MIDI; it seems to want to default to 'Charging' when I try to change to these choices.
Having the same issues on Windows 8.1. Can't get my 5x to connect to transfer files or to show up in adb.
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
bsinc1962 said:
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
ahunter said:
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
Click to expand...
Click to collapse
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
rgerrans said:
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
Click to expand...
Click to collapse
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
ahunter said:
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
Click to expand...
Click to collapse
Sorry. I should have been more specific. Part of it is I did so many different approaches they've bled together in my head and I was on my way out the door yesterday when I fired off the reply.
To try to break it down from memory (going to throw in a couple of different options since I can’t seem to fully uninstall / reinstall so please provide any corrections once you get it to work or let me know if anything doesn’t match what you find and I’ll try to remember from there):
Phase I (phone on and connected to computer):
Open Device Manager. My phone shows as Android Device | Android Composite ADB Interface or Android ADB Interface.
If it is the Composite version, I believe I had to update it to the straight “Android ADB Interface to get Phase II to work)
If you don’t see that, look to see if you have any uninstalled devices by scanning for new. If so, then right click on that device, and choose “Update Driver”
Choose “Browse my computer for driver software”
Choose the “Have disk” option and browse to your USB Driver folder
From there, choose “Google | Android ADB Interface”
Phase II (phone in recovery connected to computer)
On phone, choose “Update device from ADB”
Open Device Manager and you should see the Nexus 5 under Other Devices with the yellow triangle.
Right click on it and “Update Drivers”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list….”
Choose “Android Device”
Choose “Android ADB Interface”
Now you should be able to push the update over
Simple method: What I did was plug it in and wait for it to show up in device manager. Then I deleted the device (the one that shows adb) from device manager. Then I unplugged the device and plugged it back in... Then waited for drivers to install on it's own. Everything was good after that.
I have no trouble other than on Windows 10. Windows 10 doesn't even show the drivers from a list to install.
Sent from my Nexus 5X using Tapatalk
I followed this to get my Nexus 5X detected on my Windows 10: http://stackoverflow.com/questions/...ould-we-use-for-the-nexus-5/19839812#19839812
I have no trouble with Fastboot or adb. It only happens when I try and sideload. I end up have to use my Macbook Pro to sideload.
Sent from my Nexus 5X using Tapatalk
bsinc1962 said:
Just need the right drivers. Download the driver files from here:
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I wish it were that easy. But, no, this does not work. Nor do I believe my issue is the same as you others here, as I have Windows 7 and not the 8.1 and 10 issues that you are having.
No, no matter what driver I use, including any from your kind link, bsinc1962, they return an error, code 10 when trying just to install the drivers. I cannot go further.
What is this Code 10 error preventing drivers from installing?