I am looking for anyone who can help me with installing adb on Ubuntu I've posted a topic in Q&A but received no response so I'm asking here I partition my hard drive and installed Ubuntu I've downloaded the sdk and I've gotton as far as placing the tg file in my home directory but still no go I think I'm missing something but don't know what I'm native to windows and I have adb working on that just fine but Ubuntu is all the way different like I said I'm really new to Linux so I'm asking for a step by step guide to install adb on Ubuntu and a list of commands for adb on Linux as well also I've been asking for a while now and still no answer does anyone know how to disable the force In call touch UI in CM6 its checked and blackend out the setting I'm speaking of can b found in setting /call settings I would like to b able to uncheck it also I'm very fond of the bx theme was wondering if anyone could help me to get it to work on CM6 stable any help with any of these would b greatly appreciated thanks
Root-Hack-Mod-Always™
what happens when you execute adb?
if your getting something like "can't execute blah blah" make sure that adb has execute permissions.
#chmod +x adb
its been awhile since I been on ubuntu you may have to sudo to execute chmod on ubuntu.
Wen I plug in my phone it does not recongize it also wen I hit adb says no command adb found did you mean then gives me a list of commands for something I'm not familiar with lol
Root-Hack-Mod-Always™
laie1472 said:
Wen I plug in my phone it does not recongize it also wen I hit adb says no command adb found did you mean then gives me a list of commands for something I'm not familiar with lol
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
first are you executing adb from the folder its in. If so and it says that the command is not found then make sure that the abd executable has executable perms on it.
Sorry if if I'm not precise on the instruction as I'm trying to do it from memory, I haven used linux in about a year or so and most of my nix time is solaris lately.
But you should by able to #chmod +x adb so that its has execute perms.
if you gets errors trying to run chmod try typing sudo first so that you can switch into root.
I'm not sure on running it threw the window its in I opened up terminal its the only thing open besides a search window on how to install this and when I did type in a command I hit sudo didn't try the other commands u gave yet I'm mobile and to my dismay ill b for a few hours but as soon as I get to my laptop I will and post results anything else you can think of is more than welcome to I don't shun knowledge thanks in advanced
Root-Hack-Mod-Always™
this might help getting adb and your phone working in ubuntu, if you need any more assistance pm me and i'll try my best to help.
http://forum.xda-developers.com/showpost.php?p=7874321&postcount=11
codejunkie78 said:
this might help getting adb and your phone working in ubuntu, if you need any more assistance pm me and i'll try my best to help.
http://forum.xda-developers.com/showpost.php?p=7874321&postcount=11
Click to expand...
Click to collapse
This will work. That was posted in the thread I started with the same question. Been running Ubuntu for over a month and use adb all the time.. Thanks again codejunkie!
Man I knew u guys would come threw I love Google but love xda more ill b home in less than an hr can't wait thanks a million
Root-Hack-Mod-Always™
Thought I had posted this here well unfortunately I ripped out a USB port on my laptop. Besides that I had to pop out my hard drive and send it in to HP because of a warranty repair. I should have it back by Friday and I'll post and let you guys know if I got it thanks again for the info
Root-Hack-Mod-Always™
Update
Got it installed and I posted a thread on how we did it in case anyone needs it thanks for the responses and I started a thread about anything hero so feel free to post and check it out all knowledge on heros is most definitely welcomed and encouraged by
Laie1472
Thanks in advanced
Root-Hack-Mod-Always™
Related
im trying to set up a adb so i can use my g1 as a webcam:
http://forum.xda-developers.com/showpost.php?p=4975656&postcount=17
however when i plug in my g1 it says everything was installed except the adb.
Do you have ADB setup on your computer in the first place? If not, http://forum.xda-developers.com/showthread.php?t=532719.
I installed the adb with the sdk as it was mentioned and my computer still doesnt show my phone as an adb device
Did you install the drivers for adb?
i cant find out how!
85Mario85 said:
i cant find out how!
Click to expand...
Click to collapse
a little search and VOILA!!!
http://forum.xda-developers.com/showthread.php?t=446274&highlight=64bit+usb
this works if you are running windoze 7 x64
i dont get how im supposed to put windows 7 on test mode =S
im getting this aswel "When running the command prompt adb install I receive an error dialog stating:
"This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.""
im getting so frustrrated with thiss
bump! i dont get this =[
Search for pdanet and install it. That's how I set up adb for Windows. (Btw - get rid of Windows. Finally did my switch to ubuntu today - ahahahahahahaha I'm sad I ever even used Windows.)
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
evilkorn said:
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
Click to expand...
Click to collapse
adding it to the path just saves time. instead of having to cd all the time you can just run adb. i highly suggest it. and i agree - ubuntu is a ***** about permissions all the time. i love it, but i have to learn to use it. however, i'll probably always have a copy of windows in case i can't find out how to do something and have to have it done. better safe than sorry. =]
Can u belive it ... i just got done doing a 2.1 ruu and reroot to try to fix a problem with not being able to get adb with certain roms including zens .9.6 builds ..kangslayer..newest buffed.. SO i figured let me ruu to take care of this ...WRONG...... I only can get adb from zen.9.5 and < fresh 2.12< does anybody have any input..YES DEBUGGING is enabled
Not having any issues with adb using stock or darch.
Can you run adb shell?
no that is the problem
Error device not recgonized
Trouble shooting would say to check you hardware first:
Comp usb port
Usb cable (broken bent or missing pins or torn wires)
Phone usb port
But sense you can access adb shell on other roms its not any of those.
Soo next up would be to check the roms them selves.
Maybe redownload the roms and do a full wipe before flashing ( don't forget to back up)
And see I'd the problem persists
thanks for the input but i have stressed all those options... I might be ebaying the hero earlier than expected... This is a asurion issued phone..my orginal was stolen 2 months ago
Sorry about the theft.
It'd be a shame if you sold your phone and there was a simple fix ):
Hmmm...
Do you have the sdk located in c?
What recovery are you running?
I think i'm having the same issue, but it could just be that i am very novice with the command line in general. I haven't tried to push anything through adb since i did the initial root a few months back. Now if i type in "adb shell" at the C:\ i get the error "adb is not recognized as an internal or external command, operable progam or batch file" What am i missing? Fresh 2.1.2
Okay
Your suppose to be in C:\android-sdk-windows\tools\
Just cd to the above mentioned
Thank you. That was quick and easy.
Your very welcome.
Enjoy the awesomeness that is adb shell
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
now im thinking that this is only a problem with overclocked kernals....
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
damiandarkwater said:
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
Click to expand...
Click to collapse
Yes again because everything works with other roms..i think there is a problem on my end with the phones hardware and the OC kernals..
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
mickdubs said:
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
Click to expand...
Click to collapse
I'm having the same problem. I believe (a somewhat educated guess), the boot process is locking before the adb software on the phone is loaded. if someone can help to get a console output on the screen during boot rather than the green/white htc screen would help.
tkirton said:
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
Click to expand...
Click to collapse
Yes i have tried that with no luck...
Somewhere in the boot process adb is lost like this was said above.
Im just keeping my fingers crossed for adb with the newsest fresh that should be released shortly
so i just flashed the newest (old) version of damage control. NON OC kernal and i got adb access.. So im convinced that this phone is a lemon becuase it was asurion issued and i loose adb with OC kernals. I did have OC kernals running fine on my previous hero that was stolen.
**UPDATE 3:34AM
so after testing out dc.. i tried to flash the newest OC kernal made for DC. Right after flash i lost adb...
Why is the phone loosing ADB on OC KERNALS.. Where phones patched!?
damiandarkwater said:
Your very welcome.
Enjoy the awesomeness that is adb shell
Click to expand...
Click to collapse
Orrrr. You can download and install Regaw's toolbox and it'll make it so you can run abd commands from ANY directory in command box... pretty sweet
But yes, otherwise you need to be in the c:\android-sdk-windows\tools\ folder to run adb commands (or where ever you saved the sdk at)
I didn't really know where to put this question, but since it involves my Nexus One I put it here. I put Ubuntu 10.04 on a old Compaq V2000 laptop that I resurrected from the dead, and it's running beautifully. I spend more time on my Ubuntu machine then my new Toshiba/w/ W7. Anyway I need things working like I have on my Toshiba. I set up ADB after getting bits and pieces of information here and there, I just could never get fastboot to work for my N1, except when I'm in fastboot and I plug in my usb it changes from fastboot to fastboot usb, so it's recognized in fastboot, well sorta. But, when I run fastboot devices the terminal just hangs on >>waiting for device<<. Now I have another problem, adb works just fine, but yesterday I used it and where the number of your devices appears is blank now, no number shows up, but I can still run commands. I've done just about everything and I'm at a loss here. Some real help here, no snide remarks, and no [email protected], I need dev help or someone familiar with Ubuntu 10.04, or if you've had this problem lend some help. Once again I already have adb setup, but my number isn't showing anymore, and I need fastboot working, and yes I gave it executable permissions, I exported my path, I created my android rules, I edited my .bashrc file. Thanks much in advance. Long Live Linux!!!!!!
I'm good, found a executable script that solved my problem.
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Read Read Read!!!!!!!!!!
evilkorn said:
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Click to expand...
Click to collapse
I said in my post that I used a executable script, I mean thats all you should need to know. I read about it somewhere, that's all I needed to know, and I found it on my own. They have nuff post on how to setup your adb, but none are 100%, so you have to take bits and pieces from them, and kinda wing it from there. I don't sudo adb on my system, sudo adb =can't be found. It would be senseles to have to type sudo every time you wanted to run adb, I have my to autostart as root as soon as I run adb. If someone needed help all they have to do is ask. Since this post I've had to re-install ubuntu 3 times and I've gotten my adb & fastboot working with the same method I used the first time. I have my adb setup where I can push and pull from any directory, so I don't fill up my tools directory with too many files, and so I don't have to move files, I can just push & pull to & from anywhere.
Perhaps you can share the script you found?
Dude, chill out. The guides are fine and 100%. I don't need to know ****, I know how to setup adb. How the hell is someone going to find that script when you didn't link it.
First, you have to tell sudo where to look for adb, you obviously didn't link it init.d or some other way to tell the software what to do with adb. You have to do 'sudo /home/name/sdk/tools'.
google query: somewhere executable script ubuntu adb
rm -r -f /
Hope this helps
prettyboy85712 said:
Perhaps you can share the script you found?
Click to expand...
Click to collapse
Here's the links, the script isn't mine to give, and I think that would be against the rules. Go to the first link to get the installer, and the next one to get the fastboot exe. I would follow the instructions in the second link. Once you finish that, run the adb script, If nothing pops out of the script when it starts to run , run it again, or try running (in terminal) command. If you need detailed instructions PM me, it's a little process, you have to edit some files.
http://www.droidforums.net/forum/hacking-help/38186-linux-sdk-adb-autoinstaller-script.html
http://forum.xda-developers.com/showthread.php?t=537508
Good for you.
flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!
FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?
Questions don't belong in the Development section <---please click link and read....moved to general...
TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.
@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.
No it still wont execute the command
If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"
Thanks il Duce. If I get adb running Ill try it and post back.
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)
TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.
Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow
When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
what operating system are you using
smoshism said:
what operating system are you using
Click to expand...
Click to collapse
I am using windows 7
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
smoshism said:
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
Click to expand...
Click to collapse
im not sure, im not very familiar with ADB
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
SrulDog said:
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
Click to expand...
Click to collapse
i am using the one in the SDK, i have it on my c drive in the correct spot but it still closes itslef
Are you clicking it like an icon or running it from a DOS prompt? It is to be run from the command line as it is a dos/command line program..
Ie.. at the c:\android-sdk-x86\platform_tools\ prompt you type adb and what you want to do.
Adb push or adb pull or adb shell, etc. Just adb will give some command options
Sent from my Xoom
d7benjamin said:
When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
Click to expand...
Click to collapse
First you have to open an elevated command prompt. Do this by clicking the start icon, then typing in "cmd" (without the quotes of course) and then right clicking the only thing that pops up and choosing Run As Administrator. After doing this, you need to know where you folder that contains ADB is at. To find this easily, click Start and then click Computer and in the explorer window that just popped up, type in "adb.exe". That will show you where your adb files are at.
Continuing on, for an example, my adb stuff is in C:\root stuffz. So in the command prompt I would type in "cd c:\root stuffz" and then hit enter. After that, I can then do my adb commands, such as "adb shell", "adb push", "adb pull", etc...
Edit: Make sure you have your drivers installed for the phone. Also, make sure the phone is in debug mode and charge only. This should just about cover most of the absolute basics of getting your phone recognized by adb. I'm not too sure if I missed anything, and one of the other more experienced peeps on here can prob give you more detailed information lol.