Well for some reason my android does not show up when I do adb devices command with the sdk in cmd. So is there any other way to do this? I had no problems doing the location commands on a GB or froyo rom. And yes I did have debugging on.
This is on 4.1.2
Come on guys I really need some help here. My phone doesn't show in any devices on ADB and even with the baseband updater it doesnt show on ports. This only happens on jelly bean rom. Using cm7 it always shows up.
i think you'll have to install usb driver's
for the device to show up
i guess cm9 cm10 have a modified set of drivers
I had usb drivers installed. After GB it wouldnt detect it in anything ADB but usb mode works perfect. I did however get it to change from the internal terminal program with the commands SU then set-install-location 2. Now I just wonder why it wont see the device in ADB.
Related
I have a droid x2, and im using the same computer I used for my fascinate/charge. I themed on my fasc/charge and adb worked fine, I could push pull remount, you name it. Now with this x2 everything but adb pull doesnt work. I am rooted, im running a custom rom, I have all the updated drivers, My paths are correct cuz im using the same computer, everytime I adb push I get permission denied, and if I go to adb remount I get Operation not permitted. Im not sure what the problem is.
Uninstall drivers, install easytether/pdanet drivers, plug phone in and let install. Try the micro sd adaptor that came with the phone.
Possible fix
I ran in to a Bionic where even the drivers from Moto and the ADB related ones ALL INSTALLED EVERYTHING was good adb devices picked up the phone but anytime I tried to push or pull I got permission denied. I even tried running adb shell then su then running adb push still to no avail.
MY QUICK FIX...
I rebooted the phone in to recovery adb reboot recovery [if it will take the command].
WAIT as it will need to install drivers again when recovery loads [I am using the official Open Source CWR].
Those all installed again with no issues.
Then you need to go to either mounts and storage or advanced>mounts and storage [forgert off hand]. I chose to mount EVERYTHING, but you prolly only need the sdcard-ext [top option not bottom USB mount]
Then when I ran adb push low and behold it went through with no issues.
Once that was done I restarted [this time bootloader per pathsaver steps] and proceeded to flash via RSD.
When this completes and I am able to test I will see how it reacts when I load in to OS after re-flash [via default RSD image not a custom ROM] and I get everything running.
problem
I can not istaliram, where can I find a detailed explanation?
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
I believe you need the android usb drivers supplied by google to get it to connect. They can be downloaded using the sdk package manager. Also I'm not sure it will work having the Samsung drivers installed and you may have to uninstall them first.
they are installed already since i installed the whole sdk manager pack
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
ringnutz said:
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
thx for answer but I already done that..any other suggestions?
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
What drivers are showing up when you plug in the device? If it says Samsung then you don't have the android drivers installed. And I believe you can't have both installed only one or the other as only one will load when you plug in the device not both.
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
tzacapaca said:
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
Click to expand...
Click to collapse
When you plug the device in, under Device Manager in Windows, there should be listed Android Composite ADB Interface under the device. If not the Google USB drivers were not installed properly.
yeah I dont think my theme is the culprit, there are many reasons why ADB wouldnt show devices. Also Heimdall>Zadig is good for drivers.
run sdk manager and install latest google drivers as well.
are you on Windows OS?
nope,not your theme its the culprit..cuz i didnt install it and i cant install it cuz of no adb connection which is required by a tool named AutoDEOTool1.0.3
I installed latest google driver via sdk manager too..
yes,on Win 7 64 bits
*pulling hair*
I didn't have my usb cable yesterday to check it out but adb actually works with the Samsung drivers. Device Manager>Android Phone>SAMSUNG Android ADB Interface. And when I type the command "adb devices" it shows up. This works both if you plug the tablet in wihtout powering it up and when its turned on so I'm not sure what your problem is. I do have Kies installed on the laptop too so yours should be working if you installed the sdk and drivers correctly.
Which Tab do you have? I have the 6210 unlocked wifi only, it could be other models work differently. Not sure if you have a locked bootloader that you can access the tab through adb.
GT P6200 European
and here is what i get on cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tavi>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Tavi>adb devices
List of devices attached
C:\Users\Tavi>
EDIT:SOLVED!
Thank you all for answers
How did you solve this?
I input in cmd adb fastboot reboot and suddenly the device got the command and then recognized my tab..(pretty strange i know)
make it done
tzacapaca said:
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
Click to expand...
Click to collapse
do this steps:
1) remove battery
2)insert battery
3) connect the phone via usb will turned off and leave it till usb android phone installed
4) turn ur android phone on
5) wait for full boot
6) install Motorola usb driver .zip attached down there
7)select charge only mode
8) then write the commands of tacoroot.bin
9) when all is done hit the thanx button
ADB wireless
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Unitedforlife said:
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Click to expand...
Click to collapse
What do u mean adb wireless?
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!
Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH