Develop Bugs

[Q] Help with setting up adb shell

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?

ADB

I'm trying the rage root method after reading up on all the stuff. I managed to get adb installed and connected, but i can't use adb actions.
I type in c\androidsdk\tools\adb shell
$ su
$ SUermission denied
even without su, if i try to type "adb push su /sdcard/su" it says adb permission denied.
I have kept my phone screen on as per another thread, but i do not get a prompt that asks for adb permissions. Am i missing an app or something? I do have debugging and screen awke both on.
I have placed the g2 root folder in the androidsdk\tools\ folder, both just the files and the entire folder just to be sure.
Obviously I'm new to adb, so If i'm doing something completely wrong just let me know.

as long as you're not rooted (temp or perma) you can't use "su" in adb-commands... If you tell a little more about what you're trying to push, then I can help some more

Im just trying to root the phone with rage since visionary seems unreliable.
Im trying to adb push the su/ sdcard/su as per the first line of instruction in the rage temp root guide

hehe... I used the visionary root, and it have worked good for me btw, I think you should've posted in the rage-thread instead of opening a new topic, but now it's already opened so here it goes
firstly... are you sure you're in the right folder, and have the folder "su" in there?
If so, don't go into "adb shell"... use the lines exactly as stated in the OP. adb inside an adb shell won't give the results you want... Post back if it doesn't work
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse

I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.

Ok, my adb stuff is in c:\tools .. so when I first open command prompt, I have to type this:
cd c:\tools
That puts me into the correct folder. If yours is in C, then you'd probably have to do this:
cd c:\androidsdk\tools
Then type:
adb devices
It should at least give you SOME sort of output, either with your device number (if it's connected, and adb is working properly), or just say devices, with no numbers (incorrectly)

dwang93 said:
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Click to expand...
Click to collapse
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
FYI you will not see the $ symbol. that just indicated the next line you have to enter in commnad prompt. Each time you see $ just mean you type that line then press enter. Wait to see a result of transfer from prompt then enter next line and so on.

rsxtypes72 said:
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
This!! I'll be kind though.
Make your life easy. Unzip the contents of g2TempRoot, to your tools folder, in sdk. So, unzip the g2temproot to your desktop. Go into that folder. Copy all, and move them to c:\androidsdk\tools. Now, once that's done, go into command prompt. cd c:\androidsdk\tools. Then, do as follows, as per that link
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
(Sorry I couldn't be of more help, as I used VisionaryR12 and it worked fine for me.)

One more word of advise...
I would recommend you try temp root first.
Become used to using adb then try to get full root.
When you use temp root everything you do is temporary only.
Rebooting will reset everything back to stock so its good practice.

thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.

dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
any tips on going onto the perm root?
Click to expand...
Click to collapse
Read .. research .. double check .. triple check .. and right before you do it .. check again. As you're doing it, go over every letter, space, and character to make sure it's as it should be.

On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?

Daughain said:
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Click to expand...
Click to collapse
Upload a screen shot of your command window
with the error

dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
Click to expand...
Click to collapse
dude..I think I am doing something like you...could you please post what you did....I think is an issue of directories..but I'm not that familiar with adb and i have not been able to figure this out.....
Thanks!!!

Having problems rooting

ADB is not friendly to me. I was able to root my g1 with pure ease. I cant get started with adb, I dont know why I cant get $, I've read several guides and I'm just about to give up. I'm running 2.2 on my g2.
I do have a couple of questions:
Are rooting with rage or visionary 14 the only way to root?
Are there any root guides out there that dont require ADB?
ADB is a ****ing pain in the ass to me, especially since I've tried everything and cant get it to work. Also, the drivers that go on Win7 64bit just dont work.
Also when I do have root, can I get android updates?
Any help would be thankfully appreciated. Sorry if I'm a pain in the ass, but I'd like to know if there is an easier way.

I think you need the q&a section
Sent from my HTC Vision using XDA App

This will help u get adb working...
http://forum.xda-developers.com/showthread.php?t=865685

If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.

dictionary said:
If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.
Click to expand...
Click to collapse
while my knowledge of adb isnt stellar, I have run into problems using it. I'm going to try this new link to the guide and see if it works.
Still if anyone knows other solutions, chime in.

Try the guide linked above. The drivers in the HTC Sync package (see the guide) definitely do work on Win 7 64-bit.

Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?

sorry about the ****ty pics

cwis said:
Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?
Click to expand...
Click to collapse
Did you definitely add it to your path as it is suggesting in that window ? If so, I think you may need to reboot to pick that change up.

I did that just in case.
Actually, that path field was empty. So, I added it as is.

look up droid explorer

I made some leeway:
C:\Program Files (x86)\android-sdk-windows\tools>adb shell
$
$ adb push su /sdcard/su
$ adb push su /sdcard/su
$ adb: permission denied
good grief!!!!!!!

I've completely removed visionary before starting this procedure. Did I need temproot before attempting this?
Downloading and installing Droid Explorer. Thanks!
Also, I'm using this guide: http://forum.xda-developers.com/showthread.php?t=834228

No matter what I've done, permission denied.

The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.

ianmcquinn said:
The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.
Click to expand...
Click to collapse
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).

steviewevie said:
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).
Click to expand...
Click to collapse
I did run the commands from my pc. But still permission denied.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
"permission denied" is a message from your phone, not your PC.
The $ prompt that you copied and pasted up shows that you were running the commands on your phone. As soon as you do "adb shell", then any commands you are entering after that are going on your phone, even though they're physically being typed on your PC - because your PC has started a command prompt on your phone, as shown by the $ prompt.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
Basically, don't start by typing adb shell. The instructions you are trying to follow don't even say to do that anywhere. I highly recommend you reread the instructions very carefully and follow them exactly. Rooting this phone is actually pretty simple if you just do exactly as the guide states. If you don't know what you are doing and mistype something in some of the later steps though, you can seriously screw up your phone...

I think part of the confusion is that the commands listed on the guide all have "$" at the beginning of them, probably because whoever wrote that was using a Linux PC or maybe a Mac. You are actually executing these commands from your Windows command shell so they will look more like:
D:\Android SDK\platform-tools>adb push su /sdcard/su
Click to expand...
Click to collapse
(depending on where you have the SDK installed)
instead of:
$ adb push su /sdcard/su
Click to expand...
Click to collapse
but of course you only need to type:
adb push su /sdcard/su
Click to expand...
Click to collapse
Again these are typed from your windows command shell.

Rooting with Gfree HELP!

Okay, I'm a complete noob and I'm following these instructions (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) using Gfree I believe.
I finished downloading the SDK File Manager and all the .zip folders that were mentioned on the site. However, I am stuck at the first temp root step. It says I can either enter in the command via cmd window or a different terminal. I chose a cmd window because I already have that and know how to use.
I run Windows 7, so I simply type cmd in the search bar to pull up a cmd window. I then "cd desktop" and then "cd gfree_temp-root" because it says to navigate to that folder. However, when I enter in the first command, my cmd window tells me this "adb is not recognized as an internal or external command, operable program or batch file". Does anyone know what I have to do?
Also, do I have to install Eclipse and an ADT plug-in to root my phone? And is anyone available right now to chat and walk this complete noob through this????

You're fine, just make sure your android sdk with adb is in your system path, in Win7 find it in ctrl panel/sys and security/system -> advanced system settings on the left, then advanced tab, environment variables at the bottom. In there in the bottom text window, find Path, edit it, go to the end of the path line and if there isnt already add a ; to the end of the line then paste in the full path to your android sdk where adb is - for me someandroidsdkpath\platform-tools

Alright, bumping into a new problem. I found an alternative way to run adb through another guide on the forum. Downloaded adb.exe and this is what I do.
Pull up a cmd window and then cd to the folder that contains the adb.exe, and then I copied all the files that needed to be push on the wiki page that needed to be push into that same folder. Howeverr, I am getting permission denied.
I got adb to recognize my device and all, but don't understand why permission is being denied.
EDIT: While I am waiting for a reply, I went ahead and did what the previous user told me to do. Now I can use adb through my cmd window. I navigate to the window of the file but I still get permission denied. What's going on?

LGS1231 said:
Alright, bumping into a new problem. I found an alternative way to run adb through another guide on the forum. Downloaded adb.exe and this is what I do.
Pull up a cmd window and then cd to the folder that contains the adb.exe, and then I copied all the files that needed to be push on the wiki page that needed to be push into that same folder. Howeverr, I am getting permission denied.
I got adb to recognize my device and all, but don't understand why permission is being denied.
EDIT: While I am waiting for a reply, I went ahead and did what the previous user told me to do. Now I can use adb through my cmd window. I navigate to the window of the file but I still get permission denied. What's going on?
Click to expand...
Click to collapse
Hmmm, are you in adb shell running the commands? ie a $ prompt?
the prompt at the point you send the push command would look like (for Windows): c:\myrootfileshere> adb push somefiles /sdcard/wherever

No, I am in a cmd window.
This what is looks like:
C:\User\XXXX\Desktop\gfree_temp-root> adb push su /sdcard/su ... I would then get "failed to copy 'su' to '/sdcard/su': Permission denied
Even if I wanted to use adb shell, I would get this:
C:\User\XXXX\Desktop\gfree_temp-root>adb shell
$ adb push su /sdcard/su
adb: permission denied

LGS1231 said:
No, I am in a cmd window.
This what is looks like:
C:\User\XXXX\Desktop\gfree_temp-root> adb push su /sdcard/su ... I would then get "failed to copy 'su' to '/sdcard/su': Permission denied
Even if I wanted to use adb shell, I would get this:
C:\User\XXXX\Desktop\gfree_temp-root>adb shell
$ adb push su /sdcard/su
adb: permission denied
Click to expand...
Click to collapse
Alrighty then try adb devices (not in the shell) and just verify it actually shows your phone, it won't show 'PHONE' but it's either going to show something or not.
Next, make sure the sdcard is mounted for the phone and not usb disk mode for the pc
Another thought, make sure there isnt a loose 'adb.exe' in the folder, we want to use the one ref'd from androidsdk\platform-tools
All of that failing, mount the SD card.. copy/paste the file(s) to to SD card.. unmount SD card.. continue as if you pushed it to the SD card

WHOOHOOO! I am rooted! I had to turn off the USB transfer thing and it all worked!!!! THANKS SO MUCH!

Nice bro! If I helped at all and if you wouldn't mind, hit the thanks

No problem!

thanks and happy flashing!

[Q] How do I use adb in a linux terminal?

Hello all,
I want to know how to use adb.
It seems pretty easy but I just can't get it to work. I'm using Ubuntu... I've already installed the android sdk.
So where do I go from here.
## WHAT I WANT TO KNOW IS THIS: ##
I want to (among other things) push a new boot animation to my phone from my Ubuntu laptop...
____Of course I could flash it but I want to learn how to push____
I have the "bootanimation.zip" on the root of my SD card.
NOW WHAT? In terminal?
Thanks

generalExpert said:
Hello all,
I want to know how to use adb.
It seems pretty easy but I just can't get it to work. I'm using Ubuntu... I've already installed the android sdk.
So where do I go from here.
## WHAT I WANT TO KNOW IS THIS: ##
I want to (among other things) push a new boot animation to my phone from my Ubuntu laptop...
____Of course I could flash it but I want to learn how to push____
I have the "bootanimation.zip" on the root of my SD card.
NOW WHAT? In terminal?
Thanks
Click to expand...
Click to collapse
First, put bootanimation.zip in the same directory as ADB
su
cd <enter directory with ADB here>
./adb remount
./adb push ./bootanimation.zip /system/media
And you should have your new boot animation.

EndlessDissent said:
First, put bootanimation.zip in the same directory as ADB
su
cd <enter directory with ADB here>
./adb remount
./adb push ./bootanimation.zip /system/media
And you should have your new boot animation.
Click to expand...
Click to collapse
Ok, after I enter "su" it asks for my pass and then says "su: Authentication Failure"
Is there another way like with sudo perhaps?

Ok, I did "sudo su" to become root... I think..
Then did "./adb remount" and it spit out "error: insufficient permissions for device"
Then i did "./adb devices" and it said "???????????? no permissions"
Any Ideas?
My EVO is connected via usb and I have usb debugging on and USB storage ON.

when you do the "su" command, you will need to allow superuser permission on your phone

"sudo su" first in ubuntu

in fact, ive pushed many files to my phone using ubuntu without running as root. if you are new to linux though, be advised the characters will not show as you enter your password, but dont worry, they're there... oh and what he said, you need to be rooted and make sure you can gain root access on the phone, type "./adb shell" and you should see a # sign; meaning you have root. if you see a $ sign you do not have root access. also you can type "./adb devices" to see if you device is 'online' with your computer