Hi,
I'm currently trying to use adb to pull some data from my phone but i always get "error: closed". Im running it from cmd.
When I use the command "adb devices" to see if my phone is connected, I get something different from the others is i am getting
List of devices attached
XXXXXX sideload
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Related
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..
Before i was able to use abd. A fewdays back i was using adb to push some files onto an evo. Ever since then whenever i try to do "adb bugreport" or any other command it gives me back "device not found" is there any solution to fix this?
Hello
I am trying to flash stock recovery, since then I have gotten a few problems, but not there is a new one mad. I am using this thread. Whenever I enter "adb devices"
This comes up:
emulator-5554 device
(my phones serial number) device
And that is why I can't do anything because if i try "adb reboot bootloader", it says one to many devices or emulators are running.
I would be grade full if somebody could help me.
Either remove your virtual device from the emulator or issue every adb command with the -d option if you want to target your only usb connected device and -e if you target the command at the emulator virtual device.
In your case adb reboot bootloader will become adb -d reboot bootloader
Note that this options only apply if you only have a single device of each type, if you have more of the target type (usb or emulator) you will need to identify the devices by their serial numbers using "-s <serial>" option.
Thanks for the answer But magically the emulator despaired when i was about to do it.
Won't go away
How did you get it to go away I'm trying to unlock my Nexus and I could use the -d command but I want to just get rid of this ghost AVD anyway! Thanks
thank you so much!! finally is he installing ! First I needed to install the adb drivers manually from android_winusb.. then he saw mine device in cmd.. bu then there was also that emulator.. when you sais 'adb -d......... it worked al ou on my nexus 10!! thanks mate
easy way
i did a "adb -e reboot" and the emulator never showed up again
shreyas1122 said:
i did a "adb -e reboot" and the emulator never showed up again
Click to expand...
Click to collapse
thanks.... i tried what you did and it works... :good:
shreyas1122 said:
easy way
i did a "adb -e reboot" and the emulator never showed up again
Click to expand...
Click to collapse
i know this forum is so old but i tried that and it didnt work
sawdu said:
i know this forum is so old but i tried that and it didnt work
Click to expand...
Click to collapse
It happens
Hi All,
I am a newbie here. I issue following "adb shell getprop" adb command to retrieve device properties. This just hang out no output printed on the terminal or no prompt appears.
I then kill it at send "adb shell getprop ro.build.version.release" but it also just hang out.
I am working on ubuntu12.04. adb devices list one device which is connected.
Please help, how can I read device properties from adb (such as OS, model, manufacturer etc..)
My device is not rooted.
Many thanks!
IUA
My genius self decided to delete the home launcher and replace it with Nova, and then I thought "Hey, why not make Nova a system app?" without giving second thought that maybe.... just maybe..... Nova would break and it would all go to crap. Lol.
My phone in question here is a LG Realm, rooted. I'm on Command Prompt, ready to push Picoo to it as a temp launcher, but I can't seem to do anything. Command Prompt acknowledges the device's existence, but upon giving commands to push the apk, reboot the phone into recovery, or just to reboot at all, it spits back the error message:
error: device unauthorized. Please check the confirmation dialog on your device.
I know of what confirmation dialog it's talking about, but I can't get to it because the phone freezes on the boot screen. How do I work around this? Can I force authorization?
Listen friend you don't need to reboot to recovery..
Just boot into fastboot then push whatever you want..
Hope it will help you...
If yes then click thanks
shyampandey said:
Listen friend you don't need to reboot to recovery..
Just boot into fastboot then push whatever you want..
Hope it will help you...
If yes then click thanks
Click to expand...
Click to collapse
Tried this, followed step by step instructions and it still says error:device unauthorized. Please check confirmation dialog on your device.
I launched minimal ADB and fast boot, typed adb devices (and it shows my device is connected and recognized), then entered the command line:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install PICOO.apk
zombunny said:
Tried this, followed step by step instructions and it still says error:device unauthorized. Please check confirmation dialog on your device.
I launched minimal ADB and fast boot, typed adb devices (and it shows my device is connected and recognized), then entered the command line:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install PICOO.apk
Click to expand...
Click to collapse
Bump? Anyone who can help?
Bump
Come on guys, I know someone out there has gotta know something about this. Even if this is a dumb question, don't assume I could just 'find my answer with a Google search'.... I've been searching all over. I would appreciate some help.