I cant seem to connect my phone to my computer for use with ADB since switching to ICS. I know that this is a problem but i cant figure out how to fix it, even after searching.
I have heard that i need the nexus s drivers>?
I am just not sure what to do, so your help is greatly appreciated
AlwaysDroid said:
I cant seem to connect my phone to my computer for use with ADB since switching to ICS. I know that this is a problem but i cant figure out how to fix it, even after searching.
I have heard that i need the nexus s drivers>?
I am just not sure what to do, so your help is greatly appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571
http://www.4shared.com/office/ewdIWux2/usb-connection-issues-mtp-devi.html
It's a problem driver when you use ICS rom,
You must use this driver:
http://ics.samsung-updates.com/addons/usb_driver.zip
Go in start--->Control Panel---->System--->Device manager
find your device with problem and update the driver with this new usb driver.
Related
Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
having trouble with ADB
i sold my nexus one, so my computer is setup for ADB devices but for some reason it doesn't find the vibrant...also tried to root using method in android developement and it didn't work
any ideas?
Going to assume that your phone is rooted. Go into settings -> applications -> development and make sure that USB debugging is enabled as well as Allow mock locations
then try it in ADB and it should detect your Vibrant.. make sure that drivers for the phone are also installed
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
fordstang99 said:
phones not rooted yet...does it need root to use adb? which phone drivers u talkin about the usb for androidsdk or is there something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=728929 Those drivers.
And uhm.. I don't know if it needs root to use ADB but it would make sense to be rooted so you can have ADB without any restrictions.
Was USB debugging enabled?
ok well i put the update.zip file on the root of the internal memory and hold down the volume up and down and it just boots normally
ok adb is working....i didn't see those drivers thanks
now just the update.zip, cant seem to get into recovery, i geta Downloading....Do not turn off target !!!
ok got everything working
thanks
Same Problem USB DEBUGGING
I just want to be able to use the USB Debugging feature. Is this something that is unly available with root? If so then I have no problem, if now I am not able to have the pc detect my Vibrant when in USB Debugging mode. It will connect without it so I'm curious as to my first question. I am not rooted, but plan to soon.
Thanks for any help
CRX
[EDIT]: Phone rooted and still have same problem!!!
Any help would be appreciated!!
Crx
bump for assistance
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
crxforya said:
Is there no one who is not having trouble connecting to ADB. I have seen many posts of those who have ADB working flawlessly. I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
lqaddict said:
Why would you use winblues os to run adb? Use the real OS that underlines your Android phones!
Click to expand...
Click to collapse
I dont know what ur talking about. Nobody on this thread said anything about winblues???
ISprayCandy said:
I had a few issues getting adb to work also. Turns out my adb server was out of date. Once I downloaded the sdk all over again it works fine. If you haven't done that try it because I was stuck and could connect to my other phones, but not this one.
Click to expand...
Click to collapse
Thank you for this info, ill give it a shot
crxforya said:
I dont know what ur talking about. Nobody on this thread said anything about winblues???
Click to expand...
Click to collapse
crxforya said:
I am running xp pro and have connected both my G1 and Mytouch through this machine, but I was able to use the ADB Debugging option. I cant seem to get this working.
I would greatly appreciate a little help.
Crx
Click to expand...
Click to collapse
you need winblues drivers for sammy, search for samsung kei software
The updating of my SDK made the difference. I was able to install the correct driver and now ADB is working smoothly again. Thanks for all your help.
Crx
Hello, I was wondering if someone could help me. My computer no longer recognizes my tablet and says it is an unknown device when I connect it via USB. It won't detect it in odin either. I have the correct drivers installed and have tried reinstalling them and have tried it with different usb cords and different computers with the same result. USB debugging is enabled. I am not sure where to go from here. If someone could please point me in the right direction I would sincerely appreciate it. I would be able to restore functionality to be able to transfer files between my tablet and computer through USB once again.
ROM: BinDroid (Previous was CleanROM and had same issue)
If I download roms through tablet I can install them normally through CWM, and my tablet boots up okay so I am not really "bricked" But I am kind of bricked in the way that I can no longer use odin to flash anything..which is not very good.
bump
am i the only one with this problem.....
caaznkid said:
am i the only one with this problem.....
Click to expand...
Click to collapse
No, it is one of the big problems when loading ROMs, bootloaders, etc. Most of the time it is better to fully de-install the driver and then reinstall, as the change of the ROM also changes the perceived device-id by USB (on Windows I presume). I have even seen this happen between HC Stock and ICS Stock...
Odd but true. So, try to de-install the driver (or Kies, including driver) and reinstall (Kies, or just driver). Most of the time that should be enough, but do not hold it against me if that did not solve it.
Just_Another_N00b said:
No, it is one of the big problems when loading ROMs, bootloaders, etc. Most of the time it is better to fully de-install the driver and then reinstall, as the change of the ROM also changes the perceived device-id by USB (on Windows I presume). I have even seen this happen between HC Stock and ICS Stock...
Odd but true. So, try to de-install the driver (or Kies, including driver) and reinstall (Kies, or just driver). Most of the time that should be enough, but do not hold it against me if that did not solve it.
Click to expand...
Click to collapse
Here is a possible solution, disconnect device tab/phone, disable your firewall connect device, mine worked, disconnect again restart firewall reconnect device.
this worked for me and also with my s3.
I even tried it with a new computer that has not recognized the device before. I am afraid to use mobile odin as well and I can't backup all my stuff like my pictures and videos. I guess i could use upload to dropbox.
Sent from my GT-P7510 using xda app-developers app
please help i cant get my computer to even recognize my g2 it also wont even go into download moad. Wth is wrong did i actually brick the thing
Your really need to give more detail for help here. Look in development for returning to stock for drivers and such
Sent from my LG-D800 using Tapatalk
no download mode
[email protected] said:
Your really need to give more detail for help here. Look in development for returning to stock for drivers and such
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Hello, I have the same issue.
I rooted the phone and unlocked the bootlader, it had cwm 6.0.4.5 installed. the phone took an owa update. the symptoms are as follows:
the phone only boots to the cwm recovery.
I can not get into download mode trying the up or down volume. My pc refuses to install the driver for the d800 even though i can see it as a device in device manager. I have installed lLGMlauncher as well as the LGUnitedMobileDriver.
Thank you for any ideas you may have
jflash101 said:
Hello, I have the same issue.
I rooted the phone and unlocked the bootlader, it had cwm 6.0.4.5 installed. the phone took an owa update. the symptoms are as follows:
the phone only boots to the cwm recovery.
I can not get into download mode trying the up or down volume. My pc refuses to install the driver for the d800 even though i can see it as a device in device manager. I have installed lLGMlauncher as well as the LGUnitedMobileDriver.
Thank you for any ideas you may have
Click to expand...
Click to collapse
Have you gone to device manager, update drivers on your device, let me choose and then pick the ( I cant remember the exact name but it has to do with media, maybe mtp driver. It will then mount you phone
download a Rom along with gaps and flash
This is the basics, as I am away from my PC right now, there are many guides in the general area, I believe.
Sorry I cant be of more help at the moment
easiest would be to go to the dev section and download one of the many kits to get you back on track though.
Sorry. Was traveling and in cebu now. When I get my internet running I will try to check the driver. I still can not get into downliad mode on the phone however. I think it isn't PC dependant