So I'm trying to get a better understanding of the things I am reading here and on other Android websites. I keep reading about ADB - which I've gathered stands for Android Development Bridge. I did a search on this site and found the "easy ABD tutorial" that actually confused me even more. So my question is, could someone please explain to me in laymans terms what exactly is ABD? I've successfully rooted my D3 and created a nandroid and would l iike to try the Steel Droid Rom however, it talks about using ADB to push the BlurEmail.apk to system/app/.
I think I've successfully installed the Android SDK but I have no clue as to how to install the ABD "drivers" that are referenced in the the following post: http://www.xda-developers.com/android/adb-easy-tutorial/
Is there a difference between the SDK application and ADB or are they part of the same thing?
Is there a way to verify if I have the ADB drivers/application/whatever that I need so that I can push the BlurEmail.apk to the system/app/ file location?
As always, thanks to those that provide a response to this thread.
Related
What is the simplest way to send commands to my phone (HTC Hero CDMA Sprint) through my computer (Mac OS)?
I haven't explored Android SDK yet. I rooted my phone through Terminal and bash_profile file. I'm interested in:
- how to push .apk's to the device
- how to install a recovery image if my phone can't reboot and there is not a recovery image present
Thanks!
Android sdk is the easiest
-------------------------------------
Sent via the XDA Tapatalk App
What I do is use terminal and cd to the Android sdk/tools folder. After that use the ./adb commands, which there are several tutorials for and own your phone. Hope this is clear, doing it on my phone
-------------------------------------
Sent via the XDA Tapatalk App
What I do is use terminal and cd to the Android sdk/tools folder. After that use the ./adb commands, which there are several tutorials for and own your phone. Hope this is clear, doing it on my phone
Click to expand...
Click to collapse
Sweet. Thanks. I've searched the Android SDK site and it seems that I need other software or plunging such as Eclipse and Java. I'm not ruling these out eventually but know I'm not ready to get in this deep yet to start developing apps or customizing roms. Also, after a Google search all the queries came back with options for rooting your device which I've already done. If there's a good easy tutorial, would you mind posting a link?
-------------------------------------
Sent via the XDA Tapatalk App
When I get home from work I'll find something for you.
-------------------------------------
Sent via the XDA Tapatalk App
joshuaharp said:
Sweet. Thanks. I've searched the Android SDK site and it seems that I need other software or plunging such as Eclipse and Java. I'm not ruling these out eventually but know I'm not ready to get in this deep yet to start developing apps or customizing roms. Also, after a Google search all the queries came back with options for rooting your device which I've already done. If there's a good easy tutorial, would you mind posting a link?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Just download the 2.1 SDK, cd to Android/SDK/tools, and use ./adb, I think it can tell you some commands too.
I made an app to put my phone in recovery using ./adb so I wouldn't need to go through the trouble everytime, I just go to spotlight, type "recovery", and it puts it into recovery.
I might make an app/interface for Mac OS later for ADB commands (recovery, push files, etc)
derekwilkinson said:
Just download the 2.1 SDK, cd to Android/SDK/tools, and use ./adb, I think it can tell you some commands too.
I made an app to put my phone in recovery using ./adb so I wouldn't need to go through the trouble everytime, I just go to spotlight, type "recovery", and it puts it into recovery.
I might make an app/interface for Mac OS later for ADB commands (recovery, push files, etc)
Click to expand...
Click to collapse
That would be awesome dude...
joshuaharp said:
That would be awesome dude...
Click to expand...
Click to collapse
Don't hold your breath though, I have been working a lot, but I might make it in the next few weeks.
The only main problem is that I'm having trouble getting variables to run in the shell script. I think it might be possible with Automator (or AppleScript), but I will keep trying
Well, even though it may not be useful anymore, here are the links, as promised
Rooting guide for mac (What I used and a great way to get familiar with adb on the mac ) http://forum.xda-developers.com/showthread.php?t=581686
And here's an adb tutorial that was put together at the request of toast on the EVO 4G forum. http://forum.xda-developers.com/showthread.php?t=694250
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.
It seems a lot of mods these days require knowledge of running adb. Can anyone give me a link to a thread that explains how this works?
Is it the command prompt we use in Windows or on the phone
Start here [HOW-TO] ADB for Dummies(How-To Learner's Guide)
Then search some more and read, read, read. Good luck!
I've been looking for something like that to give to everyone who's been asking me for help lately but couldn't find that. And yes, I did search! xD
Hey all,
I rooted my CN using autonooter and the instructions available at the nookdevs wiki (I'd post a link but I'm not allowed, yet). I also enabled adb over usb following instructions at the same site.
However, today I signed up as a developer on nookdeveloper.barnesandnoble.com and found that there is an official nook development kit which also provides adb access and a nice nook virtual machine to test stuff on.
My question is, if I use the official nook development kit as opposed to the drivers provided at the nookdevs wiki, do I lose any functionality? I'm guessing adb access is adb access no matter what, but then we all know what happens when one makes assumptions =P
I guess I'll know for sure when I try it out later, just thought maybe someone has been down this road already.
adb is part of the tools in the android sdk package. The Nook Color virtual machine is also a part of the sdk that can be downloaded (along with lots of other things). They are both part of the sdk and you would not get a 'different' adb.
Cheers
For those having issues with Revone S-OFF for their One (as I did)
A little googling and I managed to resolve the issue but cant post it in that specific forum until I make 10 posts (rules are rules eh?)
Applies to Windows Machines as that's what I'm running and haven't tried my Linux box yet
Update your ADB Drivers and files using this link: "dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip" - direct copy of the platform-tools from the SDK but sometimes you don't need all the additional stuff that comes with the SDK
As an 'Old Skool Droider' I simply unpacked to 'C:Andriod' and ran my Command Prompt in there: 'adb devices' comes up clear as does pushing files to and fro etc etc etc.
Probably the simplest thing in the world tbh but I noticed that some folks were still running into issues, since its been a while since I last did some faffing with Android my drivers were older then the Ark
-H
p.s Cant post direct Links either