[Q] adb not working!?!?!?!? - Vibrant Q&A, Help & Troubleshooting

ok i know i have most things set up right but for some reason my phone isnt being recognized for adb use. i just updated my sdk and adb runs in command prompt as it should but my phone still isnt recognized, and yes i do have it in debugging mode. ive searched already to find nothing. im currently running franken-twiz (which is awesome by the way) my phone previously would work with adb when it was stock but now nothing happens and i have no clue whats going on. droid explorer never finds it and neither does the computer, but putting it into mass storage mode seems to work fine... nothing i do seems to work any ideas or solutions would be amazingly helpful. thanks in advance

I am having the same issue. Any help??

Are you sure that you have the correct drivers installed? (check TGA_Gunnman's thread)
Sent from my SGH-T959 using XDA App

Oniyuri said:
Are you sure that you have the correct drivers installed? (check TGA_Gunnman's thread)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah I'm sure like I said before it worked but now that I'm not stock Rom it doesn't seem to work I used the Samsung drivers.exe for 64 bit machines and it worked but after leaving stock Rom it seemed to quit on me Idk what the deal is

Related

[Q] Sideload Wonder Machine

So I been trying to use the Sideload Wonder Machine for my Xperia x10 and for some reason the SWM is not recognizing my phone is just doesn't display the device number, I'm pretty sure I have the right drivers I don't know what else to do ? I am getting so frustrated help? why wouldnt SWM reconigze my phone? but the computer does
I had a problem at first and I reinstalled the drivers a couple of times and also used ADB directly and it started working. It's definitely driver and ADB related.
Also, be sure you have debugging turned on in the phone. Once you get it working it should work from that point on.
naplesbill said:
I had a problem at first and I reinstalled the drivers a couple of times and also used ADB directly and it started working. It's definitely driver and ADB related.
Also, be sure you have debugging turned on in the phone. Once you get it working it should work from that point on.
Click to expand...
Click to collapse
Yea I have the debbuging on , and sorry for been so slow lol but mmm I did the same thing unistall and reinstall and it just doesnt work, but what do you mean by the ADB directly? I think thats the one I am using, I mean isnt that the one when you plug your usb cable for the first time it installs itself?
Ladiablae said:
Yea I have the debbuging on , and sorry fo:r been so slow lol but mmm I did the same thing unistall and reinstall and it just doesnt work, but what do you mean by the ADB directly? I think thats the one I am using, I mean isnt that the one when you plug your usb cable for the first time it installs itself?
Click to expand...
Click to collapse
Exact same situation here. Looking forward to the solution.
charlyee said:
Exact same situation here. Looking forward to the solution.
Click to expand...
Click to collapse
Yeah i read your other post, I think it has something to do with the phone, have you try installing and reinstalling the drivers? I have try everything , is getting me upset lol
Ladiablae said:
Yeah i read your other post, I think it has something to do with the phone, have you try installing and reinstalling the drivers? I have try everything , is getting me upset lol
Click to expand...
Click to collapse
Yes I did a few times and no luck.
I read that the Captivate had the same problem and one fix was installing generic Samsung drivers, I am not finding any such thing for Sony. I am convinced it is a driver problem.
charlyee said:
Yes I did a few times and no luck.
I read that the Captivate had the same problem and one fix was installing generic Samsung drivers, I am not finding any such thing for Sony. I am convinced it is a driver problem.
Click to expand...
Click to collapse
Yeah I think so too, I been looking for more drivers and I cant find any.
Have you guys tried killing the PC Companion process (the one that runs on startup) and then trying to reinstall the drivers?
No i have not..but i unistall and reinstall the drivers a lot of times already. I am even lookin for different drivers but they all the same ..or when I try to update it it says that it has the right driver already. I can't think of anything else. I guess. Would never be able to use it
Sent from my X10a using XDA App
I am pretty sure I closed it out, but I will check again.
Thanks.
Same issue with me but doesn't work.
@naplebill - How do you use ADB directly?
Sent from my X10a using XDA App
sopdogg said:
Same issue with me but doesn't work.
@naplebill - How do you use ADB directly?
Sent from my X10a using XDA App
Click to expand...
Click to collapse
You need to download the Android SDK. Once that is setup, ADB is located in the installed folder under the tools folder.
This is a DOS command interface. You will need to run CMD and then from the tools directory type:
ADB shell
This should show the following:
* daemon not running. starting it now *
* daemon started successfully *
If your device is recognized it will show it there as well, if not the last line will be this:
error: device not found
When I download the sdk i need to only installed for the 1.6 version right? I dont need to installed all that crap? Or should i install everythin? I know u hate me am so annoyinnn lol. But am a girl and slow for this kind of things : )
Sent from my X10a using XDA App
Ladiablae said:
When I download the sdk i need to only installed for the 1.6 version right? I dont need to installed all that crap? Or should i install everythin? I know u hate me am so annoyinnn lol. But am a girl and slow for this kind of things : )
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Don't worry, I've been employed in IT for 20 years. It's not because you are a girl, it's because you just don't have the xperience (see what I did there? Lol).
You can just install 1.6, it doesn't matter because you aren't going to use that part of it.
Ohh that's why u know so much about this .... lucky u ...well and about my problem with the swm ..it just doesnt work ...but im tired of tryin everythin so i am gonna wait for the update of 2.1 ..i think with the update would work ....well i hope so hehe
Sent from my X10a using XDA App
Ladiablae said:
Ohh that's why u know so much about this .... lucky u ...well and about my problem with the swm ..it just doesnt work ...but im tired of tryin everythin so i am gonna wait for the update of 2.1 ..i think with the update would work ....well i hope so hehe
Sent from my X10a using XDA App
Click to expand...
Click to collapse
If you decide you can't wait or if it still has issues after the update, I can probably walk you through getting it working via chat or a phone call.
It is definitely an issue with the driver not working with ADB properly. Also, are you killing the process PCCompanion.exe? You can kill this process using Task Manager and clicking on the Processes tab.
Ok, so I've been going back and forth with this too. I had it working, installed SEUS, then it wasn't working, did a system restore, and started over. It was working again. I formatted my phone and noticed it wasn't working again. This is what I did to make it work:
1)Completely uninstall the PC Companion. It's virtually useless now anyway
2)With the phone connected go into the device manager (right click my computer-->Manage and select device manager), and uninstall the device driver windows shows for the phone. As soon as you do that unplug the phone.
3)Go into the C:\Windows\System32 folder and delete these three files (if they are there):
WdfCoInstaller01007.dll
WinUSBCoInstaller.dll
WUDFUpdate_01007.dll
4)If you had the android sdk already just delete the entire folder and download the latest version from here: http://dl.google.com/android/android-sdk_r07-windows.zip
5)Install the packages shown in the attached pic. You only need the 1.6 files and a couple of other packages.
6)Once you get all of this done, plug in your phone with debugging turned on and you should be good to go.
Ladiablae said:
When I download the sdk i need to only installed for the 1.6 version right?
Click to expand...
Click to collapse
See my sig.
Thanks so much SPIDERTECH !! Everything works now!
@Jmercy09 you're quite welcome. I may have to do this again myself. My computer is now, again, not seeing the phone
I actually had to redo these steps and was back up and running. I found the best way to test this after doing the steps is by using the android screencast (attached). If screencast runs and shows your screen, it worked. If it doesn't, then it obviously didn't work as screencast has to see the phone in the same way SWM has to see it.

[Q] usb device not recognized. help!

When I plug my phone into my computer, it is no longer recognized by windows. It used to... now it doesnt...
I have googled this
I have checked the forums
I have NOT found a solution that works
I have tried booting my phone while it's plugged in.
I have tried reinstalling kies.
The phone comes up as "uknown device" in the usb section of device manager, when i specify the 64bit drivers(I'm running win7 pro 64) it says drivers are up to date! and then proceeds not to work.
I have also tried setting my phone into usb debugging mode.
I have tried all my computers usb ports.
If anyone knows how to help me I'd really appreciate it.... and if I've blindly missed something feel free to call me a moron so long as you successfully help me
chaosthebomb said:
When I plug my phone into my computer, it is no longer recognized by windows. It used to... now it doesnt...
I have googled this
I have checked the forums
I have NOT found a solution that works
I have tried booting my phone while it's plugged in.
I have tried reinstalling kies.
The phone comes up as "uknown device" in the usb section of device manager, when i specify the 64bit drivers(I'm running win7 pro 64) it says drivers are up to date! and then proceeds not to work.
I have also tried setting my phone into usb debugging mode.
I have tried all my computers usb ports.
If anyone knows how to help me I'd really appreciate it.... and if I've blindly missed something feel free to call me a moron so long as you successfully help me
Click to expand...
Click to collapse
Rom? etc.
Sent from my GT-I9000 using XDA Premium App
Stock with a voodoo kernel, do I need to turn voodoo off?
chaosthebomb said:
Stock with a voodoo kernel, do I need to turn voodoo off?
Click to expand...
Click to collapse
I have noticed that some ROM's will enable debugging, I personally run a MAC. But you may want to check those settings to see if its enabled/disabled. But if your charging on it you should be good. Have you tried to odin back to stock and seeing if that helps?
Other thing: do you have the samsung drivers installed on your PC? even if you don't you should still see the external storage just not the internal.
lovemysgs said:
I have noticed that some ROM's will enable debugging, I personally run a MAC. But you may want to check those settings to see if its enabled/disabled. But if your charging on it you should be good. Have you tried to odin back to stock and seeing if that helps?
Other thing: do you have the samsung drivers installed on your PC? even if you don't you should still see the external storage just not the internal.
Click to expand...
Click to collapse
Reinstalk drivers as he said
Sent from my GT-I9000 using XDA Premium App
I should have listed this before... I reinstalled the drivers first before reinstalling kies or checking out device manager
chaosthebomb said:
I should have listed this before... I reinstalled the drivers first before reinstalling kies or checking out device manager
Click to expand...
Click to collapse
Any other devices recognize it?
Sent from my GT-I9000 using XDA Premium App
What rom are you using? If you are running one of the test CM7 builds you have to download the Google drivers from the Android SDK.
Does your phone show up when you mount it as external memory? Did you install the drivers and kies as an administrator?
exact same scenario!
I am having the exact same issues as the OP! Except that i have the unbranded gt-i9000. My galaxy s is completely stock, no custom firmware or launchers. Heck, after the last factory reset, not even any apps!
I have tried every suggestion on every search i could do. I have 4 computers with xp sp3, win7 sp1, ubuntu 10.04.1, and mac os x 10.5.8. Nothing is working on any of them. I've even tried different usb cables, just to rule that out.
Could it be a samsung hardware issue?

[Q] How to enable adb on the phone.

How exactly do you enable ADB i was doing the whole root this morning and tryed the webtop mod and i was going to push the commands through adb but i couldnt get it to work so what exactly do i need to do to enable this
Settings, applications, development, usb debugging. That's it
Make sure you have drivers installed on your computer
Sent from my atrix
I have tried that, and it does not work.
When you say doesn't work, what exactly do you mean? What happens when you try to use the adb command?
Sent from my MB860 using XDA App
ScuroRaven said:
I have tried that, and it does not work.
Click to expand...
Click to collapse
Ummm. It does work because that's the only way to enable usb debugging on the phone. Sounds to me like you need to read up on what ADB is and how it works.
Sent from my HTC Vision
or you need to get the required drivers, I found windows update installed most of them without issues but I installed the one from the rooting tutorial for safe measure.

Am I really rooted? Hope you guys with Samsung Experience can explain..

There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
SysAdmNj said:
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
Click to expand...
Click to collapse
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Entropy512 said:
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Click to expand...
Click to collapse
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
SysAdmNj said:
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
Click to expand...
Click to collapse
if you are on CM7, i think you need to install the nexus S drivers, which are included in the Android SDK. you will need to run the emulator and run the update in SDK
Since you mentioned this has happened on two different computers, I doubt my advice will help. With that said, whenever I've had issues like this, I've found that USB ports tend to be the culprit. Have you been using ports on the front of a tower? Have you tried the ones on the back as well? Again, just taking a shot at a possible fix...

I have tried everything please help

Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
brandi1693 said:
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
smalk said:
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
Click to expand...
Click to collapse
I tried that, it is still not seeing it like it is supposed to. I was able to get Odin to recognize it so that I could flash the rooted stock again but I can't get Casual Jailbreak to work. I'm not sure if it is because the drivers or not but I am guessing it has something to do with it. Every time I plug it in, it starts searching for drivers and then always switches from usb debugging mode to media mode. The checkmark is still in usb debugging but I don't think it actually is. You can watch it go from device as installer to media.
Are you using the driver install app (zadig i think its called) to install the heimdall driver on top of "gadget serial". Looking at your other post it seems like a driver issue. One thing ive noticed is, if odin can see the device then heimdalll cant and vice/versa. So if odin can see it you have the wrong driver, if you are infact installing the heimdall driver my second question is, does windows xp x64 use driver sig enforcement like win7 x64 does? if so you probably need to disable it. Just throwing my $0.02 out there.
Are you using the official USB cable? I had an aftermarket cable that had worked for months, then decided to quit working. It works with other devices just not the Note2. Changed to my original cable and all is well.
nunyazz said:
Are you using the official USB cable?
Click to expand...
Click to collapse
Also try plugging it in to the PC and not through a hub/keyboard/monitor port
Sent from my SCH-I605 using xda app-developers app
If it sees the device in the dumb verizon cd mode thing and ptp than it can see adb. Its not the cable. however i would try setting the usb debugging first than set it to camera mode. adb should still be able to pick it up
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
brandi1693 said:
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
Click to expand...
Click to collapse
How? Fixing to unlock my spanking new note also. I had the drivers issues late last night. When installing drivers through the Z app I never could get it to install Samsung usb drivers nor did I see serial gadget option. Running Windows Vista 64bit. I know I have Java.
Sent from my SCH-I605 using xda premium

Categories

Resources