When in adb shell typing: adb devices, my device isn´t showing up. Am I missing something?
You can fix that by following this guideline: https://edwardsamuel.wordpress.com/...-found-with-nexus-5-devices-in-recovery-mode/
Basically the steps are the same.
Related
I'm using Cyanogen Mod 6, the most recent nightly build. I want to push the Sense UI notification sounds to the android notifications folder. I attempted to do this via terminal emulator via the following:
Code:
$ adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
When I did that, I get a "not found" error. I was thinking I didn't have permissions, so I did:
Code:
$ su
# adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
I got the same error.
Then, I decided to copy the files I wanted to push into the tools folder on my computer, in the Android SDK. I did the adb devices command, and I saw my device listed. I did the same code as above, and still get the "Not Found" error. I'm sure it's something very simple that I'm missing. I made sure the directories are correct, even making sure everything was case-sensitive.
tokuzumi said:
I'm using Cyanogen Mod 6, the most recent nightly build. I want to push the Sense UI notification sounds to the android notifications folder. I attempted to do this via terminal emulator via the following:
Code:
$ adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
When I did that, I get a "not found" error. I was thinking I didn't have permissions, so I did:
Code:
$ su
# adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
I got the same error.
Then, I decided to copy the files I wanted to push into the tools folder on my computer, in the Android SDK. I did the adb devices command, and I saw my device listed. I did the same code as above, and still get the "Not Found" error. I'm sure it's something very simple that I'm missing. I made sure the directories are correct, even making sure everything was case-sensitive.
Click to expand...
Click to collapse
You're entering the wrong command(s).
Place your notification sound into your AndroidSDK\tools folder, then run:
Code:
adb push name-of-soundbite.mp3 /system/media/audio/notifications/
This will place a .mp3 called "name-of-soundbite" into your notifications folder. You then need to reboot your phone in order for it to work.
Thanks for the help. I was still having the "not found" error, after your instructions. I figured it out, though. I had to run the "adb remount" command, to make the system partition writable. After I was finished, I ran the remount command again, to make it read only.
So, for anyone who has this error later here's the code I used (I did not need to go into the adb shell to do this):
Code:
adb remount
adb push name-of-soundbyte.mp3 /system/media/audio/notifications/
adb remount
tokuzumi said:
Thanks for the help. I was still having the "not found" error, after your instructions. I figured it out, though. I had to run the "adb remount" command, to make the system partition writable. After I was finished, I ran the remount command again, to make it read only.
So, for anyone who has this error later here's the code I used (I did not need to go into the adb shell to do this):
Code:
adb remount
adb push name-of-soundbyte.mp3 /system/media/audio/notifications/
adb remount
Click to expand...
Click to collapse
Oh? I apologize, I thought you already knew to run that.
pseudoremora said:
Oh? I apologize, I thought you already knew to run that.
Click to expand...
Click to collapse
It's fine. I'm a newb/noob, so my adb skills are almost non-existant, but I when I saw the error about the system partition being readonly, that triggered something I read in the adb wiki. I found the remount code there, which paved the way for my success.
Need lil help with adb... reinstalled all drivers and reinstalled android sdk and install all tools/updates.. still giving me same no adb errors.. Im nand unlock with engineering bootloader.
wasd321 said:
Need lil help with adb... reinstalled all drivers and reinstalled android sdk and install all tools/updates.. still giving me same no adb errors.. Im nand unlock with engineering bootloader.
Click to expand...
Click to collapse
Your problem is that you're entering adb commands inside shell.
Once you see the # sign, after typing adb shell, that means that the adb commands will no longer work. So, your commands that begin with adb will NOT work if you see the # sign..
Also, for commands like adb devices and remount, they need to be run outside of shell or rather from your AndroidSDK\tools PATH directly.
This will work:
Code:
C:\android-sdk\tools:
adb remount
adb devices
adb shell
This won't work:
Code:
C:\android-sdk\tools:
# adb remount
# adb devices
# adb shell
Notice the # sign (this happens when you type adb shell), this means you're now root and now using shell -- you cannot run the adb commands inside shell, you have to instead use Linux commands, or specifically commands from BusyBox.
Just to clarify: Some commands can be sent outside of the shell, but they have to be preceded by "adb". For example:
Code:
adb reboot recovery
Others will only work inside of the shell, like ls, mv, cd, and so forth. Search for an adb command listing (you do have a Google phone, after all) and it may help to familiarize yourself with basic Linux terminal commands as well - a lot of them are accepted by adb.
SilverZero said:
Just to clarify: Some commands can be sent outside of the shell, but they have to be preceded by "adb". For example:
Code:
adb reboot recovery
Others will only work inside of the shell, like ls, mv, cd, and so forth. Search for an adb command listing (you do have a Google phone, after all) and it may help to familiarize yourself with basic Linux terminal commands as well - a lot of them are accepted by adb.
Click to expand...
Click to collapse
Yea, I was aware of this, just decided not to mention it. Thanks for pointing it out though.
I must be stupid or something cause I'm stuck on getting this to work. Can someone help me finalize setting up adb shell?
This is where I am so far:
I have installed phone driver and Android SDK. In SDK have installed packages API 2 through 8, usb driver package 3, etc.
What do I need to do when opening SDK manager? My phone is in tether mode but it just sits there. What am I not doing?
Thanks.
No love from the community on this one??
I'm a little confused.
When you set the evo to usb debugging and open a command prompt, cd to your sdk/tools dir, enter "adb devices" does your evo show up? It should be listed as a serial #.
Yes.....an HT### serial comes up which I am assuming is the phone. Guessing I can now just run the commands I need and it will communicate with the phone?
My confusion was that I was running the SDK Manager.exe and expecting it to find my phone and produce the adb shell.
Ok! You should be good to go. Just enter "adb shell" and you are set.
Good deal....thx.
Ok....thought I had this working. However, when in adb shell any commands I put in tells me "adb: not found".
What do I need to do from this point?
Let me clarify this.....
When I list devices it does find my phone. But, when issuing the adb shell command and trying to enter anything from the "#" prompt it always says "adb: not found".
I must be missing a step or something.
I'm kind of confused, mostly because I don't know what it is you're doing in a shell, but once you're in the shell and you get the # sign, there's no need to type in adb before your commands, for example, from the command line you would navigate to your tools folder. For me it would be
cd AndroidSDK/tools
./adb shell
Some jibber jabber about daemon starting
#
From then on I could run whatever command I planned on running in the shell like
echo 1 > /sys/class/leds/flashlight/brightness
And not
./adb echo 1 > /sys/class/leds/flashlight/brightness
CCallahan said:
Let me clarify this.....
When I list devices it does find my phone. But, when issuing the adb shell command and trying to enter anything from the "#" prompt it always says "adb: not found".
I must be missing a step or something.
Click to expand...
Click to collapse
What exactly are you trying to accomplish? Then we can determine what's going on.
I'm running Myn's RLS4 and am trying to change the power bar in the notifications.
Trying to follow the instructions in this link: http://forum.xda-developers.com/showthread.php?t=836721
OK. What part are you getting stuck at?
Edit: for this code, you do not need to be in the ADB shell:
Code:
adb remount
adb push widget.txt /system/customize/
adb reboot
You just need to cd to your tools folder of the SDK in your command prompt.
CCallahan said:
I'm running Myn's RLS4 and am trying to change the power bar in the notifications.
Trying to follow the instructions in this link: http://forum.xda-developers.com/showthread.php?t=836721
Click to expand...
Click to collapse
The commands he has given here
Code:
adb remount adb push widget.txt /system/customize/ adb reboot
do not require you to be in an adb shell, you just open up the command window do an adb remount then type in his commands one by one and male sure you have the .txt file that specifies what widgets you're going to use is in the tools folder of your AndroidSDK folder so that adb can locate and push it to its respective directory.
Ok...that worked.
Knew I was doing something wrong. Was trying to run those commands from the adb shell....makes sense that it could not find adb.
Thanks.
i have no adb shell at all can anyone help?
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..
I was reading through the methods of rooting and just figured out none of them works for me.
I can't seem to make my phone visible in adb while in the bootloader. No commands work because of this and when I do adb shell getprop, I see that ro.debuggable is 0.
How can I root my phone when I can't see it in the bootloader?
You mean you executed the command ”fastboot devices” and got nothing? Then you should probably chech if the adb driver is installed properly. Sometimes it gets little tricky during the driver installation.
I am using linux, when my device is booted, adb or fastboot devices returns it. When I'm on the bootloader, they don't show my device. That's the problem.