When using "normal" ADB, it works just fine, i can push and pull files from sdcard and everything.
But when i try to use any form of ADB Shell, it starts acting weird.
I can connect to ADB just by plugging my phone in and using cd to the adb folder. I can see the device ID with "adb devices".
But when i type "adb shell", it suddenly says that "daemon not running. starting it now on port 5038", then immediately says it started successfully, but yet it shows "list of devices attached" and there is none. No matter what i try and do, it simply won't show when using adb shell..
I can type "exit" to simply exit adb shell and still be in adb, and it will immediately start working normally again..
I've tried to flash my rom again, mount and unmount system (that was the location i tried to use adb shell to get to, to pull some system files), rebooting my computer, restarting my phone, did a battery pull.
Can anyone help me? :S
Related
Hello all,
I have a problem with the adb shell.
I rooted my HTC Hero, the superuser permission app is well installed, my ROM is MoDaCo Custom ROM 3.0 core.
I can push/pull files with adb, no problem.
When I go to shell mode (adb shell command), I am in root by default. When I type ANY command (ls, mount, cat, cd, trythismyfriendyoullgetitrepeated...), the shell repeats my command in the output and does nothing, EXCEPT for reboot or exit (they work after repeating themselves in the output)...
What's the point? I am totally lost...
Thanks in advance.
I made a new install of the rom, and like magic it fixed everything... Well, no problem anymore, although I don't understand what happened.
Hi, i install cannot turn on debbuging usb mode in my Defy 2.2 froyo movistar argentina.
Does anyone have any idea why? i turn on but when connecting to the PC no (!) icon shows.
Thanks!
btw, i belive is a device problem because before i install froyo work fine. And my drivers worked fine till i install froyo
Any idea? please help
Can you post the link/thread from where you downloaded the froyo ROM. Also ignore the ! icon, just check in ADB if debugging is working or not. Enable USB debugging in Settings and after plugging in the USB select "Charge Only" mode.
Open adb and type "adb devices"
if it shows one device, then you're all good.
PS: make sure you have Moto Driver v4.9 or above.
bikerabhinav said:
Can you post the link/thread from where you downloaded the froyo ROM. Also ignore the ! icon, just check in ADB if debugging is working or not. Enable USB debugging in Settings and after plugging in the USB select "Charge Only" mode.
Open adb and type "adb devices"
if it shows one device, then you're all good.
PS: make sure you have Moto Driver v4.9 or above.
Click to expand...
Click to collapse
Hi i'm using argentina movistar from http://and-developers.com/sbf:defy
I have tried what you 've told me and this is my cmd:
C:\Users\MaryPau\Documents\samsung\root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015F13B80600D025 device
C:\Users\MaryPau\Documents\samsung\root>adb shell
$ adb push Superuser.apk /sdcard/Superuser.apk
adb push Superuser.apk /sdcard/Superuser.apk
adb: permission denied
There's nothing wrong with USB debugging or your cell. It's just that you're using the wrong command syntax.
once you type "adb shell" you DO NOT have to type adb before every next command because you're already inside adb prompt.
Just write "push Xyz.apk /sdcard/Xyz.apk"
or
write this command when inside windows prompt , i.e when not inside "adb shell"
C:\>adb push xyz.apk /sdcard/xyz.apk
(notice it's C prompt)
Skip writing 'adb' before each command once you are inside adb shell
also, are you trying to root your Defy?
bikerabhinav said:
There's nothing wrong with USB debugging or your cell. It's just that you're using the wrong command syntax.
once you type "adb shell" you DO NOT have to type adb before every next command because you're already inside adb prompt.
Just write "push Xyz.apk /sdcard/Xyz.apk"
or
write this command when inside windows prompt , i.e when not inside "adb shell"
C:\>adb push xyz.apk /sdcard/xyz.apk
(notice it's C prompt)
Skip writing 'adb' before each command once you are inside adb shell
also, are you trying to root your Defy?
Click to expand...
Click to collapse
it worked tks a lotttttttttttttttttt
RSD Lite recognize my phone, but after connecting no other options in Phone....No portal, No mass storage...Nothing.... Can anyone help..
Tried searching for anything remotely like this issue, but have come up empty.
Apologies if this forum isn't the appropriate place for this - not sure if this is specific to my Sprint device, or not.
Using v16.0.1 of the Android SDK Platform-tools, I'm able to establish a connection to the device with "adb shell". After issuing a single command (any command it seems) the command completes successfully and drops me back to the adb bash shell prompt.
When I attempt to issue a second command, the shell hangs - no activity, prompt appears to be waiting for something. Attempting additional commands results in the same thing. I can break out of the shell with Ctrl+c, and try again, but same behavior occurs.
Anyone seen anything like this before? Any tips on allowing a shell session to complete multiple commands until I gracefully exit?
Thx
Sent from my CM 10.1 (4.2.1) SGS3
Here's my issue. Trying to put an updated CM on my kindle. Put when I open up cmd prompt from my ADB file location from my desktop it won't let me push files.
I'm able to put in the cmd; adb devices. and can see my device is listed in recovery mod. but every time I run the cmd, adb push filename.zip /sdcard/ filename.zip....It doesn't send instead the cmd prompt returns a bunch of lines of code explaining the different commands that are available.
I've reinstalled the USB drivers for my kindle and am running TWRP v2.6.3.1.
Any help is appreciated
Edit: solved my own issue, sorry
Hello,
My wife forgot her phone on the roof of her car and drove off. Result: the phone fell 5 kilometers away and the screen was broken. However Phone health seems like ok.
I would like to recover the photos stored on the internal memory. USB debugging is not enabled.
I am a noob but after somes search :
I installed ADB and managed to put the phone in recovery mode.
When i use command: adb devices result is:
518cc4c3 sideload
When I want to recover the files using the command adb pull "sdcard" then nothing happens as if there were no files.
So I wanted to check the contents of the internal memory by doing "adb shell" and I got following error : "error: closed"
I tried : adb kill-server adb start-server ... But the error persists. Can a specialist help me?
Thanks