Ok so i am trying to install the ADB USB drivers and having some issues. i have pluged my mytouch into my VIsta ultimate 64 bit machine before (the day i got it actually) so i could transfer files and of course now that im trying to install the ADB USB 64 bit driver windows wont let me and says i have the latest drivers.
currently im loooking in my Device manager and i see my device under 2 locations:
Disk Drives - HTC Andriod Phone USB Device
Portable Devices - Android Phone
i go into my CMD shell and type ADB DEVICES and it says:
list of devices attached
it is blank instead of showing a serial number
so im assuming that the drivers that windows has assigned to my device are not cuting it.
i have tried uninstalling the drivers but every time i do that as soon as i plug the device back in windows just assigns those drivers to it again and every time i choose UPDATE driver and browse to the AMD64bit driver it says y drivers are already up to date.
any thoughts on how i can get around this?
what i did was download an application called usbdeview and then uninstalled any htc drivers from there. then i unplugged my phone, and plugged it back in, and pointed windows to the drivers in the sdk folders.
momohammed20 said:
what i did was download an application called usbdeview and then uninstalled any htc drivers from there. then i unplugged my phone, and plugged it back in, and pointed windows to the drivers in the sdk folders.
Click to expand...
Click to collapse
that worked like a dream thank you!
now on to seeing i i can root this mytouch lol
sweet!! good luck
momohammed20 said:
sweet!! good luck
Click to expand...
Click to collapse
you wouldnt happen to know what im doing wrong here would you? im mking my gold car and downloded Terminal Emulator but it looks like it was designed for physical keyboard devices so i downloaded Better Terminal Emulator and finally have the soft keyboard and typed in "cat /sys/class/mmc_host/mmc1/mmc1:*/cid " but nothing happens. im supposed to get a code to write down but i hit enter and the terminal does nothing.
am i missing something? even the email feature doesnt work (i assume it means it would email you the results)
i was having that problem too, so what i did was i just typed that command in through adb. so i did it via the computer. and make sure you have the card that you want to make into a gold card inserted into your phone.
so....
1) insert soon to be gold card into your phone
2)open command prompt, and change directory to where your tools folder is from the android sdk
3) type in adb
4) type in the command cat /sys/class/mmc_host/mmc1/mmc1:*/cid , then it should output your CID
momohammed20 said:
i was having that problem too, so what i did was i just typed that command in through adb. so i did it via the computer. and make sure you have the card that you want to make into a gold card inserted into your phone.
so....
1) insert soon to be gold card into your phone
2)open command prompt, and change directory to where your tools folder is from the android sdk
3) type in adb
4) type in the command cat /sys/class/mmc_host/mmc1/mmc1:*/cid , then it should output your CID
Click to expand...
Click to collapse
got it thanks so much again.
i was able to use the hex editor to modify the soon to be gold card with the CID hex info and re saved it. then i removed my SD card and plugged it back in and i was able ot open it no problem via My Computer in windows. i went ahead and copied the SAPPIMG as well and now i assume it is a gold card.
just working on downloading the other files i need from rapidshare probably have to finish this up tommorow as its getting late. this wll give me some more time to do more research and read up as well as decide which ROM i wwant to flash..
thanks man again!
no problem, glad to help. I'm still a noob at this myself, i'm still learning. I currently have cyanogens rom on my phone, it's pretty solid. good luck, let me know how everything goes.
hello. ive been reading on different forums on the best way to sideload apps on captivate on mac. ive read about sideload wonder machine but seems ppl have problems... seems ppl r being more successful on pc.... if i were to run parallels then win 7 and try to use sideload wonder machine on pc will it work? im still reading on how to use commands, and terminals and cmd lines and all that . im new to android but familiar with winmo phones and jailbreaking iphones. so if anyone can help me or point me to the right direction, it is greatly appreciated! on a side note, i use parallel's and ran win 7 and dl droid explorer to try and delete some at&t bloatware but no go. when i try to delete it nothing happens... so i dont know what to do! lol. im rooted and all. i wanna have sideload next! thanks again guys!
1. Install Android SDK for Mac
2. Using Terminal CD to android-SDK/Tools directory
3. place your apk file in the tools directory
4. In terminal type: adb install file.apk <where file.apk is what you want to install>
This is the manual way on windows and this is what sideload wonder does for you. If you want to learn - this is the best way to start. ADB is easy, and it opens up the gateway for everything else.
YOu can probably find a more detailed tutorial on using ADB commands in Mac.
ADB is what lets you copy system files off the phone, change permissions, get access to the systems.db where you can allow sideload from phone, etc.
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!
haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!
bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.
I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid
I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!
Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!
Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work
matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!
thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!
I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box
Has anyone figured out how to connect to their Note with ADB yet?
I turned on debugging but the darn thing still doesn't show up in the devices list.
For reference, I'm using the cable that came with the Note and I can transfer files successfully
Have you installed proper drivers or the Android SDK? If you get Android SDK for your pc, make sure open up the manager in there. Then download platform tools and tools. It should give you needed drivers and support for ADB & Fastboot(not sure if Samsung uses it).
Or you might be able to use Odin to do whatever you trying to do with ADB. Not sure though. Depends on what you trying to do.
demandarin said:
Have you installed proper drivers or the Android SDK? If you get Android SDK for your pc, make sure open up the manager in there. Then download platform tools and tools. It should give you needed drivers and support for ADB & Fastboot(not sure if Samsung uses it).
Or you might be able to use Odin to do whatever you trying to do with ADB. Not sure though. Depends on what you trying to do.
Click to expand...
Click to collapse
I'm trying to play with some app deving, I like the logcat tools Eclipse provides.
I'm also trying to play with sqlite,
I updated my SDK to have the ICS and JB API's, I didn't think that ADB would have been significantly different than the honeycomb one I was using with my GB phone. I'll give it another try when I get back to my office on Thursday. I figured either I was doing something wrong, or I had something wrong on my Note when my Prevail works.
Thanks for the help
Well, I updated everything, made sure I have the latest ADB executable and dll's and still can't get it to work.
I have no idea what I'm doing wrong.
I can connect to my phone just fine, pull logcats, install test builds of APKs with Eclipse, everything.
My Note just doesn't show in the device list. I've made sure that adbd is a running service on the Note. Should I be using a different cable from the one that came with the system?
In case it matters, the only things I've done are to install CWM recovery and rooted using this method: rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Well, turns out I'm a complete idiot.
It helps to have the latest samsung drivers installed
I had given up on getting it to work, then installed Kies to do an update.....
once it installed new drivers, my Note suddenly started showing up in ADB's device list.
Here I thought I already had the latest drivers
I feel like such an idiot
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
JohnCSElwell said:
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
Click to expand...
Click to collapse
Uninstall all other drivers and android sdk.
https://forum.xda-developers.com/showthread.php?t=2788632
Use this guide and all will be fine.