Related
Ok so I've been looking around all over google and XDA for the correct way to install the usb drivers for adb and fastboot from sdk manager(r11) and there are no updated guides out there for the latest r11 sdk program... so here is my quick guide just to clearify how this is done on (Windows Vista/7) PC with Sdk r11!!!
Install Java and SDK
First Install Java jre, jdk... http://www.oracle.com/technetwork/java/javase/downloads/index.html
install programs and restart if required...
Now go visit the SDK site and download latest version (r11).zip... http://developer.android.com/sdk/index.html
Now unzip file directly to C: drive.. and rename folder to 'android'..
open 'android' folder and run 'sdkmanager.exe' install updates and packages than restart if neccessary..
ADB Driver install...
Now go to your device and enable 'usb debugging' located in settings>applications>development...
Now plug device into computer via usb and DO NOT mount device (storage) to computer!!
Now press START button on computer desktop..
Right-click on 'computer' and select properties..
Now select 'Device Manager' on upper left corner of newly opened window..
Look for device named 'Android' and open selection.. right click on under-link and select 'install drivers' or 'update drivers'...
Now select browse and go to this location than press ok..
C:/(sdk folder)/extras/google/usb_drivers
Now should say driver has been installed correctly..
Test method: Open CMD
cd/
cd (sdk folder)/platform-tools
adb devices
Should see device and number pop-up...
(ADB is located in Platform-tools folder now along with 2 .dll files needed for fastboot to work)
Fastboot Drivers Install
First powe off device, than power on holding (Back+Power)
Now plug usb cable from computer into device..
Do same exact method as 'ADB Driver Install' method..
(Fastboot drivers are located in same folder as ADB drivers)
Now to run fastboot mode in cmd prompt enter this..
cd C://
cd (sdk folder)/platform-tools
Should see device and number pop-up...
Alt method is to copy the 2 .dll files located in 'platform-tools' folder and paste them into 'tools' folder, than fast boot will run correctly off this in cmd prompt...
cd/
cd android/tools
fastboot devices
Should see device and number pop-up...
Also you could just go to ..
C:/android/extras/google in 'windows explorer'
and move the 'usb_drivers' folder to root of sdk folder (android) so then all the older guides out there for installing the drivers would actually kinda make sense.. lol
if i missed anything please feel free to add a comment!!
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
MarcAntonyy said:
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
Click to expand...
Click to collapse
well to install the fastboot driver you need to be in fastboot mode on your device... for the G1 it is back+power...
Ok, I tried it again and I left out a detail (sry). When I power on with pwr+left vol it gives me two icons. One is an Android in a box, which takes me to recovery. The other is an icon that says 'Downloading'.
This time I went to it and now I'm at a screen which says
ODIN3 Download Mode
(Protocal v2)
Reason: Force Key
Secure Mode: Nonsecure
Check Signature: Check
Waiting USB Cable.....
Click to expand...
Click to collapse
And then it has a big Android in the middle of the screen with
Downloading.....
Do Not Turn Off Target!!
Click to expand...
Click to collapse
written under it.
Ok, I hooked up the USB and went through the steps and typed in the first two commands and am now in CMD at:
C:\Android\platform-tools>
But when I type in the "..\tools\fastboot.exe devices" command it says its not recognized as an internal or external command, operable program, or bath file
Btw, after I connected the USB, I got an additional line of text under "Waiting for USB" that says "===> Connected! Press the [Start] of Odin3!!"
***Update
Ok, so I copied the .dll files into Tools and ran CMD again and this time I at least did not get that error message, but it displayed no output at all, other than to begin another prompt at:
C:\Android\Tools
And that's where I'm at now.
wel uhhmmm this guide is for the G1... lol im not really sure what downloading mode is... if that is your version of fastboot than just follow the B. Instructions for the ADB driver install... the directions are the same exact for both..
Heh. Yeah its all good. I was able to install CWM and Root it, but I would like to get ADB/Fastboot working. Thanks for your help and patience with me
yeah no problem.. sorry if i couldnt help but the only thing i know is how to get it workin on G1 lol
i see many people on the G1 thread with sdk, adb and fastboot issues... FOLLOW THIS GUIDE!!! It is instructions for latest sdk Vr11... i promise this helps..
Thanks for the guide. Been trying to get ADB up & running on Vista with no success. I'll give this a try.
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
ldrifta said:
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
Click to expand...
Click to collapse
i do all waht you said but i can t see the number of my device i just got
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
ldrifta said:
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
Click to expand...
Click to collapse
Hi,
I have the same problem:
I manually install the drivers choosen located in extras/google/usb_drivers on device manager
then it say cash: "windows did fond no driver for your device.
I tried with XP SP3, Vista, Seven: always same problem
What is your device, this guide is for the dream but the same steps can be used for other devices, but you need the proper drivers for your device
Sent from my Nexus 4 using XDA Premium 4 mobile app
I followed this guide from LG optimus 3d fourm
Step 1: Download SuperOneClick here http://www.megaupload.com/?d=IKMS0QN3 then extract it.
Step 2: On the phone goto settings > Applications > Development > Turn USB Debugging on also turn on unknown sources.
Step 3: connect the phone to your pc make sure mass storage is turned off once connected wait for the drivers to install
Step 4: Run SuperOneClick as admin and click on Root, sometimes it can take a few minutes once it's done restart the phone now you should have superuser app on the phone.
Click to expand...
Click to collapse
MY ERROR
~~~~
when running superoneclick and hitting root.
the follow device does not have drivers installed:
android phone USB\VID_1004&PID_618E
Would you like to me forcefully install an Android ADB Interface driver for this device?
If I hit "no" it begins the root and the program freezes after step 2.
I haven't hit yes because I don't know if I this is a good thing.
Unplug your phone from your computer. Download a program called usbdeview. Open the program and it will allow you to see all of the drivers installed on your computer. Delete everything associated with your phone. Make sure USB Debugging is checked and plug your phone back into your computer. This will do a fresh install of all drivers and should also include the drivers for ADB. To check this, open up a CMD window in platform-tools in your SDK folder and type in "adb devices". A serial number for your phone should come up, and if it does, you are good to go.
Have you got lgs drivers installed on pc? I had same problem and had to reinstall driver.
Dave
Sent from my LG P920 using Tapatalk
lowandbehold said:
Unplug your phone from your computer. Download a program called usbdeview. Open the program and it will allow you to see all of the drivers installed on your computer. Delete everything associated with your phone. Make sure USB Debugging is checked and plug your phone back into your computer. This will do a fresh install of all drivers and should also include the drivers for ADB. To check this, open up a CMD window in platform-tools in your SDK folder and type in "adb devices". A serial number for your phone should come up, and if it does, you are good to go.
Click to expand...
Click to collapse
device driver was not successfully installed.
I uninstalled both the LG usbs in usbdeview.
umirin said:
device driver was not successfully installed.
I uninstalled both the LG usbs in usbdeview.
Click to expand...
Click to collapse
http://www.t-mobilephone.org/t-mobile-lg-optimus-3d-usb-driver-download.html/
Try this
lowandbehold said:
http://www.t-mobilephone.org/t-mobile-lg-optimus-3d-usb-driver-download.html/
Try this
Click to expand...
Click to collapse
thank you very much worked.
Hi,
I just extracted the latest USB driver (USB_Acer_1.0_USB_A700 A701), but there are Windows XP, Vista and 7 drivers inside only.
i tried to install the Windows 7 driver on Windows 8 64-bit, but had no success...
The one that isn´t working is the "USB composite device" driver.
I need any Acer Windows 8 USB 64-bit drivers for Android 4.0...
Will Acer release a Win 8 driver for the A700 in near future?
Hi,
You should try installing the Android SDK, which has general Android drivers inside them.
Connect your Acer device onto your computer.
Install the Android SDK and once the program has started, it'll (down)load and show you all the Android versions and tools.
Make sure you have only selected the checkboxes "Android SDK Platform Tools" and "Google USB driver". Now click on the right bottom button labeled: "Install packages".
Select the radio button: "Accept All" and click "Install".
Now click with the right mouse button on Computer, click Manage. Go to Device Manager. Right click Acer A700, click update driver software.
Choose "Browe my computer for driver software". Choose "Let me pick from a list".
Click all devices or/and Have disk..
Go to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\ and click the file under the 2 folders (android_winusb.inf)
Click on the first one and install.
Good luck and let me know if you succeed.
Edit:
You can skip the first part and download the Google USB driver I uploaded:
http://www55.zippyshare.com/v/1434863/file.html
Thank you very much it worked for me!
Thanks for the re-upload but there appears to be a problem with the contents of the zip file. When I try to extract it, I get this message: " the archive is either in unknown format or damaged". Could you download it yourself, or anyone,& see if you get that message.
Cheers.
EDIT: Thanks Tom for re-uploading again. It extracted OK this time. Unfortunately, I have had to send my A510 tablet in for repair, the charge light stopped working. I must admit to some ignorance in what to do with the unzipped files, as there is no installer for it, unlike a typical install of a USB driver. Perhaps you, or anyone, could educate me a bit?
theoldfarter said:
Thanks for the re-upload but there appears to be a problem with the contents of the zip file. When I try to extract it, I get this message: " the archive is either in unknown format or damaged". Could you download it yourself, or anyone,& see if you get that message.
Cheers.
EDIT: Thanks Tom for re-uploading again. It extracted OK this time. Unfortunately, I have had to send my A510 tablet in for repair, the charge light stopped working. I must admit to some ignorance in what to do with the unzipped files, as there is no installer for it, unlike a typical install of a USB driver. Perhaps you, or anyone, could educate me a bit?
Click to expand...
Click to collapse
Sure thing,
I explained it a little in my previous post, but I will try to explain it a little better this time.
1. Click with the right mouse button on Computer.
2. Click Manage.
3. Go to Device Manager.
4. Right click Acer A700 (or A510, OR anything that looks like an unknown android device), click update driver software.
5. Choose "Browe my computer for driver software". Choose "Let me pick from a list".
6. Click all devices or/and Have disk..
7. Go to the (extracted) folder you used from my upload in the previous post (usb_driver) and click the file under the 2 folders (android_winusb.inf)
8. Click on the first one and install.
Now Windows will recognise your tablet.
If you still don't get the hang of it, check out this video I found on Youtube:
https://www.youtube.com/watch?v=RbXatmo4QBU
The video may seem a bit dull, but it's actually useful if you really can't find any of the things I explained.
In the video, the "woman" explains on how you can find the Device Manager, on another way I explained.
Follow the instruction in the video until Step 8, which means you shouldn't follow step 8 but continue from my instruction from step 5.
Good luck!
Ps. If you really really don't get to install it, I would like to offer to do it for you (no charge, if that even was a question), if you trust a complete stranger on the internet (but you can abort any time). Just PM me.
Thanks. I will do this when my A510 returns from repair. It is waiting for a part to arrive from overseas, so don't know when it will return.
theoldfarter said:
Thanks. I will do this when my A510 returns from repair. It is waiting for a part to arrive from overseas, so don't know when it will return.
Click to expand...
Click to collapse
The A510 has returned. I have tried to install your driver but have no success.
At step 6, I get presented with "Show All Devices". I am shown a list of Manufacturers & Models. I choose nothing & click "I Have Disk".
I navigate to your folder & click on android_winusb.inf
I then click on "Install From Disk" button. I am then shown the option "Select The Device Driver You Want To Install For This Hardware".
There are 3 items shown: 1. Android ADB Interface, 2. Android Bootloader Interface, 3. Android Composite ADB Interface.
I choose number 1 as that is the one I beleive you mean in your option 8.
I click "Next" & get a warning about "Installing This Device Is Not Recommended Because Windows Cannot Verify That It Is Compatible With Your Hardware". I continue the install & after about a minute, I get this message "Windows Found Driver Software For Your Device But Encountered An Error While Attempting To Install It"... and..."Android ADB Interface".... and...."This Device Cannot Start (Code 10)".
The Device Manager now shows Unknown Device as "Android Phone".
Await your reply but am thinking about reinstalling Windows 7 & leaving Win 8 until I get a touch screen laptop & Acer Tablets get a USB driver for Win 8. Acer say they are on the way but can't/won't give me a date.
Windows 8 is an annoyance on my 4 year old Asus N50Vn laptop.
Without drivers, can you still access the SD?
@theoldfarter
That's odd, but can you try choosing the third option: 3. Android Composite ADB Interface.?
Maybe the drivers I uploaded are out of date in Windows 8 and you should try installing the Android SDK.
Install the Android SDK and once the program has started, it'll (down)load and show you all the Android versions and tools.
Make sure you have only selected the checkboxes "Android SDK Platform Tools" and "Google USB driver". Now click on the right bottom button labeled: "Install packages".
Select the radio button: "Accept All" and click "Install".
Click to expand...
Click to collapse
(android_winusb.inf) will be available at the following location:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\
troun2000 said:
Without drivers, can you still access the SD?
Click to expand...
Click to collapse
Yes, you can. I just tried it with my freshly installed Windows 8 machine.
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
Mmm... you lost me there.I have no idea what you mean.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
Googled it & now know what you mean. That option is for Windows 7.
I use windows 8 & Google tells me this about it:
"7) Disable driver signature enforcement
The Disable driver signature enforcement option allows non-signed drivers to be installed in Windows 8.
This startup option can be helpful during some advanced driver troubleshooting tasks."
I will try this but when I tried installing the driver as per Tom's instructions, the driver in question said it was digitally signed.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
That won't work 'cause the driver can be installed, only it's not starting.
Do you have USB Debugging turned on in the Developer Options?
TomONeill said:
That won't work 'cause the driver can be installed, only it's not starting.
Do you have USB Debugging turned on in the Developer Options?
Click to expand...
Click to collapse
Did not have that turned on. Done so but makes no difference. I have just discovered that my built-in camera is not working with Win 8, Skype says there is no camera installed. It worked with Win 7. I am thinking that the "unknown" device in Device Manager is the camera, not my tablet.
No wonder I can't install the driver to it. lol.
With the tablet not connected, I uninstall the "unknown" device & then scan for changes & it shows it again.
It looks like the A510 is not recognised by Win 8 as anything, period.
I have had enough of Windows 8. It is causing more problems than it is worth. In a couple of days, I will reinstall Windows 7 & start over.
Will report back when all has finished, which may be in 6 days time.
Thanks for your help so far.
A700, mass storage and Windows 8
Hi
I have installed the USB drivers aa told here, an device manager shows my A700 under Android Phone.
But i cant see the storage.
How can i access both internal storage and SD card on my tablet??
theoldfarter said:
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
Click to expand...
Click to collapse
I would like this link as well. Since I've updated my a510 to JB 4.1.2, my computer doesn't detect it when I plug it in via USB. I can plug a USB stick into the tablet and it sees that, but when connecting to PC, nothing at all. USB debugging is also turned on. Would love some assistance with this.
http://www55.zippyshare.com/v/1434863/file.html
This is the USB driver.
When clicking on start and entering "device manager", a new screen will pop-up showing you all the connected devices. Somewhere you should see Unknown, Fastboot, ADB, Android device/phone, A700 or Acer. Install it with the USB driver.
Note for everybody:
If it is NOT working, try to find Android Phone in the categories list when installing the driver. That one might work too if my solution doesn't work.
dis method helped me...!
theoldfarter said:
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
Click to expand...
Click to collapse
try this link... http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
install the drivers with signature verification off
i too had the same problem on my xperia device
its solved now. :good:
This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"
Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe
:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working
hey thanks!!
will give it a try tonight!
Will this work on 4.3?
Sent from my GT-I9505G using xda premium
Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.
ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.
ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.
Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks
Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0
I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver
warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.
Correct.
Etched in blood by a katana
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!
MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?
MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?
MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder
Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.
Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)
Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.