Need some help please!
I recently rooted my Xoom using the one click method and wanted to put a new kernel on but in order to do that I need ADB to work which it doesn't seem to be
I've installed the motorola drivers and my computer can see my Xoom and I can do stuff to it. But when I open a command window and enter and ADB shell, when I type 'adb devices' nothing comes up! and I can't do anything! eventhough the adb will only work when the thing is plugged in!
I've re-installed the drivers and SDK and adb stuff many times and still nothing. Also tried a few things I found on other boards but again nothing. This is reallly starting to get my nerves, please help!
In device manager what does it show? I have:
Android Phone
Android ADB Interface
its just "ADB Devices" not ADB Shell Devices
in device manager my one comes under
portable devices
MZ604
higher up there is also
ADB interface
MOT composite ADB interface
and yeah I type adb shell then adb devices and nothing comes up
ulicquel said:
in device manager my one comes under
portable devices
MZ604
higher up there is also
ADB interface
MOT composite ADB interface
and yeah I type adb shell then adb devices and nothing comes up
Click to expand...
Click to collapse
Well as you can see your device manager and mine say two different things. Mine works. Again its just "ADB devices" I do not type adb shell then devices that works for me yours doesn't seem to. So you might want to try changing to what I have posted and see if it works for you like it works on mine.
right! now I see! and it works lol Thanks alot!!!
don't know why I had to go into adb shell first, anyway one more question for you if you wouldn't mind
I want to put the recovery thing on there so where do I put the recovery.img to push it onto the xoom?
thanks again!
I put it directly in the SDK/Tools folder in other words the same folder as adb.exe
okay cool, thanks again! you're a life saver!!!
ulicquel said:
okay cool, thanks again! you're a life saver!!!
Click to expand...
Click to collapse
No problem man enjoy the rest of your Sunday. Take care..
Related
Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.
Forgive me for asking the obvious, but do you have USB Debugging enabled?
distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.
Fastboot devices gave me this output:
serial# fastboot
kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe
kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).
Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck
Hi everyone, just trying to get ADB working with the Galaxy S2 Skyrocket, anyone want to point me in the right direction? I have android SDK but when I launch adb a command line pops up for a second and closes before I can do anything, and where can I find the ADB drivers? If you could help, that would be great, thanks!
If your using windows. Click start type in cmd hit enter
Open the directory where adb is. You can type adb start-server then press enter
Make sure you have debugging turned on in your phones settings.
So that's how you launch it! thanks, can I run it by just opening it with command line?
saying daemon started, but not doing anything, but my phone is running CWM at the moment, should I try again after?
If its running then abd is running. What are you trying to do with adb theres a ton of dfferent commands
Yea the command is going through but nothing is happening
silver03wrx said:
If its running then abd is running. What are you trying to do with adb theres a ton of dfferent commands
Click to expand...
Click to collapse
No command line is coming up, or something it just goes through
nsilverman15 said:
No command line is coming up, or something it just goes through
Click to expand...
Click to collapse
Oh I got it, use it right in command line
I cant able to use the adb. It's not listing my mobile.
Even though, I've enabled my USB Debugging, It's not listing my device.
Last day it worked well.
Any idea guys? I'm still struggling with this problem.
That's problem in the driver and the custom ROM. I myself solved he problem.
Well
swordfish said:
Well
Click to expand...
Click to collapse
if device is not shown in adb then there will be some possibilties like
you haven't properly installed the driver or older version of drivers
or you haven't have all the binaries files to run adb command
or previous adb server was not killed
to prevent that
install updated drivers,check whether you have all binary files
and for killing adb server try these commands
adb kill-server
adb start-server
adb devices
hit thanks if helped
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Ironcheeks said:
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Click to expand...
Click to collapse
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Lgrootnoob said:
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Click to expand...
Click to collapse
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Ironcheeks said:
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Click to expand...
Click to collapse
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Lgrootnoob said:
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Click to expand...
Click to collapse
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Ironcheeks said:
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Click to expand...
Click to collapse
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Ironcheeks said:
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Click to expand...
Click to collapse
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Lgrootnoob said:
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Click to expand...
Click to collapse
Thank you for all your help!
So I finally undated my PC from Ubuntu 12.04 to 16.04. The good new is I have full MTP access to my G3 now. However, ADB is no longer recognized. ADB and Fastboot are located on a separate drive from the OS, so I am trying to run the same file from the same HD. Any suggestions?
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Tel864 said:
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
I did try that without success even though I successfully ran ADB without root with 12.04. Only Fastboot needed root.
For some reason the file is not recognized as an executable file. Below is a screen copy:
Code:
$ ls
adb fastboot twrp-osprey-3.0.0-r2.img
commands.txt twrp-osprey-2.8.7-r5.img twrp-osprey-3.0.2-r1.img
$ adb
The program 'adb' can be found in the following packages:
* adb
* android-tools-adb
Try: sudo apt install <selected package>
$
Henriquefeira said:
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Click to expand...
Click to collapse
I have not even got that far. See post above, "adb" is not recognized. I would rather not install the adb development package if I can avoid it.
Its fastboot flash recovery not adb flash
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
The commands is not my issue. I have a list of commands I have run successfully many times. My issue is with the new OS (in the same PC) not recognizing adb. When I boot to the old OS, no issue, back to the new OS, command is not recognized..
My list of commands is as follows:
Code:
adb devices
adb reboot bootloader
sudo fastboot devices
sudo fastboot boot twrp-osprey-3.0.2-r1.img
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
Re-reading your reply, I think you mis-read my code box. Next to the dollar sign my command "ls". Below is the OS response. Next $, command is "adb", and below the OS response.
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
MrTooPhone said:
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
Click to expand...
Click to collapse
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
acejavelin said:
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Pretty sure I had multiple 'adb' executables in 12.04.
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
steffano said:
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
Click to expand...
Click to collapse
adb doesn't work in bootloader mode, that is when you use fastboot... I think you should review the process involved in installing recovery.
Sent from my MotoG3 using Tapatalk