I've decided to make all these new useful tools a lot easier to access.
How to use:
1. Download python (Version 2.7)
2. Download androidtools.zip from below
3. Unzip to wherever you'd like
4. You'll need to update tools the first time you run
5. Then just select which tool you'd like to use
Updates:
You can find the source HERE that shows all updates for all these apps.
The "Update Tools" option pulls straight from git, so you can have the latest version at all times!
NOTE: It will create a tools folder (which contains all of the tools) in the directory that androidtools.py is in.
Fore More info on what each tool does, visit their thread:
Boot Script Generator
(This has been added to the current kernel's source, so if you're using the latest nbh/zImage, it should work fine)
Key Mapper
NBH Editor
If you have any questions or problems with those programs, please post in those threads. If you have issues with the Android Tools program itself, please ask in this thread!
Thanks to l1q1d for the TONS of help over the past few weeks.
Hopefully this helps someone...
If something doesn't work here let me know and I'll add it and make corrections. I will gladly accept recommendations and input from anyone. Also Mac and Linux users please post your info and I'll gladly add your pieces to my guide as well.
Step 1:
Some files are needed such as the SDK and USB driver. Note: Some devices require Windows drivers provided by the manufacturer we will have to play around and see what works with Adam...
System Requirements
USB Drivers
Android SDK
- Download the zip file
Step 2:
Extract the zip and run the exe to install. It should check for JAVA dependencies and get you all setup.
Copy the SDK folder to the root of your C: drive or where ever you want. Plug in the device (Adam in this case), DO NOT MOUNT ANYTHING, and when prompted install the USB driver. NOTE: I'm not sure yet if the drivers in the link will work with Adam or not so play around and see what works. You can always go into Device Manager and remove the driver.
Step 3:
Create environment variables for ADB by right-clicking on "My Computer" and select Properties. Then go to Advanced tab (or Advanced Settings in Vista) and select Environment Variables. Add the following:
Variable name: adb
Variable value: C:\android-sdk-windows\tools
Note: that variable value may change if you do not run the sdk from the root of your C: drive and depending on the name of your SDK folder...
Step 4:
Code:
adb [COMMAND]
If you replace "[COMMAND]" with an adb command, the above should work for you. Go here for a listing of ADB commands...
A simple command to test with is:
Code:
adb shell
"adb shell" should return one of two values, "$" or "#". And this should be the shell prompt from the device, not your local terminal window.
If that code didn't work, put in your full SDK folder path and try again. If it works that way, look into the environment variable and make sure its the same as the path to your SDK folder.
References:
The first is the sweet guide from XDA member VanillaTbone and is widely used here at XDA.
The second is one I wrote over at NotionInkHacks. This one is only for Windows at the time being, but once people with other OSs leave feedback I will update to include those other OSs as well.
Thanks for the links!
They were helpful to me and I am sure they will be to others.
Thank you, stickied! This is useful to people unfamiliar with ADB.
Updated the OP so this is now a full guide. I also updated the title to reflect tutorial.
webs05 said:
Updated the OP so this is now a full guide. I also updated the title to reflect tutorial.
Click to expand...
Click to collapse
Excellent work. This will help all the first time Androiders here!
How to get your Adam detected in Windows
After following this.. you can follow this next to now make sure windows detects your Adam.
http://forum.xda-developers.com/showthread.php?p=12022670#post12022670
it would be more uniform if people installed the .exe and have 2 paths for step 3 depending on 64 bit or 32 bit
for 64 bit when installing the exe the path is
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools
and for 32 bit I believe its (not sure on this one because I have 64 bit)
C:\Program Files\Android\android-sdk-windows\platform-tools
Also might be wise to mention that if you do not define a push or pull path way when you start up the command prompt it will look in C:\users\"UserName"
edit: fixed: http://developer.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
thanks for your help
howdy,
I have previously installed the adb driver for my sgs and sgs2. When I plug in my adam, the mass storage components come up, but nothing shows up with regards to android devices which will allow me to update the driver for.
Debugging is enabled on my adam (it is a PixelQi/Wifi version running beast+clemsync v3) and shows up in the notifications. USB Mass storage works fine.
ADB also works fine for my SGS2 when I plug it in and run adb shell/devices. When I plug my adam in, adb does not see anything related to it.
Where should I go from here to get windows to like this thing?
edit:
When I plug it in I can see these things:
If the nvidia harmony device shows up in the device manager I don't know where
Click to expand...
Click to collapse
Al Credits Goes TO Perceval from Hyrule
Perceval from Hyrule said:
** Currently writing this, please wait !
Hello there,
here is a new tutorial I'm sure you'll like. As usual it took me LOTS of work to get all info and make this to work, so now I share it with you and show how to run custom ROMs within Android SDK Emulator.
Please note it's mainly for XPERIA X10, but process is the same for other Android-powered devices. It will show you the process for Linux.
1. Download the latest Android SDK.
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
3. Go to the SDK folder, then in the folder Tools/. Double-click on Android and choose Run.
4. Go to Available packages, and choose to install (choose at your will !)
Android SDK Tools, revision 8
Android SDK Platform-tools, revision 1
SDK Platform Android {VERSION(S) YOU WANT} (!) You need at least one Platform. For X10, you can download 1.6, 2.1. You can also add 2.2, 2.3.
Once it's done, close the window.
5. Download Xperia X10 add-on for SDK. (?) Read the PDF add-on guide, it is helpful !
Copy the folder (from the archive) XPERIA-X10_r1 inside the folder add-ons of your Android SDK folder ({androidsdk}/add-ons/).
6. Run terminal, go to your Android SDK folder, then in tools folder, and run
Code:
./android list target
.
Note the id number of the Android you want to develop (ie for me, Android 2.3 is
Code:
id: 3 or "android-9"
). (?) You might also want to note the name ("android-X") as it might be useful later.
7. Now, create AVD (a profile for emulator). Usual command (assuming you are INSIDE the /tools/ folder !) is
Code:
android create avd -n NAMEYOUWANT -t {ID}
So, for us, it will be
Code:
./android create avd -n myx10 -t 3
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 160 (correct if I'm wrong ?)
DPad support : no (?)
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 66 (?)
Audio playback : yes
Trackball : no (?)
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 32
RAM : 280
GSM Modem : yes
(?) I recommend you to create one profile for each Android version you want to run (so : you just have to change the ID, and create same profile). If you don't, you won't be able to run custom ROMs using other versions of Android (ie your AVD profile is 2.3 and you run a 2.1 custom ROM).
9. Done ! Take your custom ROM (downloaded, compiled... In this case, files are in {YourAndroidRepoFolder}/out/target/product/generic/. It comes with about 3 files, including a file called system.img. Copy this file into the folder (hidden) .android/myx10{In fact, the name you've chosen earlier "NAMEYOUWANT"}.avd/
10. Run terminal, go to Android SDK folder/tools/ (if you didn't close your current terminal, you're already in and run this command to run emulator WITH your custom ROM :
Code:
./emulator -avd myx10{again the "NAMEYOUWANT" you've chosen before}
Wait and enjoy !
(?) First boot is long - it's NORMAL. Just like on a real device, the OS will be cached and will work faster and faster.
Click to expand...
Click to collapse
Can you please make a video tutorial? I don't have terminal i use Windows
terminal on windows
TodorSRB said:
Can you please make a video tutorial? I don't have terminal i use Windows
Click to expand...
Click to collapse
in windows 7, press the start button, type in cmd, hit enter and viola! you are in a terminal
Great tutorial but the point that confuses me is: If we're creating AVD why do we need and where/how do we used device add-on for SDK?
Thanks
LastStandingDroid said:
Al Credits Goes TO Perceval from Hyrule
Click to expand...
Click to collapse
thanks
Thanks for this tutorial! Thanks +1 for you! :good:
there is a new version of ADT out since this tutorial was written. I am able to run a virtual machine but how can I get a custom rom on it? Please help.
thanks
mrdoc151 said:
there is a new version of ADT out since this tutorial was written. I am able to run a virtual machine but how can I get a custom rom on it? Please help.
thanks
Click to expand...
Click to collapse
You need to download more than one api, it creates the directory for addons and continue from there :beer:
thanks for the tutorial
A question, ¿how to compile a rom? :S
jomigp01 said:
thanks for the tutorial
A question, ¿how to compile a rom? :S
Click to expand...
Click to collapse
A Linux environment is best, and there are a million tutorials all over xda:beer:
Slithering from the nether regions of a twisted mind and tarnished soul
jacobmacek said:
in windows 7, press the start button, type in cmd, hit enter and viola! you are in a terminal
Click to expand...
Click to collapse
That is not terminal. If you need terminal in windows download CYGWIN. http://www.redhat.com/services/custom/cygwin/
Silly post *Removed*
I want to make it to this process for one x. in addition to those for xperia Where can I find one x
I have a flashable zip of the custom rom i need to test. Is there any way i could use that here?
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
* I can't see any archive.
TodorSRB said:
Can you please make a video tutorial? I don't have terminal i use Windows
Click to expand...
Click to collapse
Download cygwin from HERE
It should help you
---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------
OzoGaming said:
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
* I can't see any archive.
Click to expand...
Click to collapse
Here the archive means the flashable custom rom :laugh:
Need a windows tutorial.....
This tutorial looks like for linux......please make a windows version tutorial
Black Screen here, any suggestion?
I saw that the ramdisk.img is also needed, but I dont know how to generate it
You can use fastboot / ADB to pull ramdisk.img for the device brand model you are trying to cook for. Tutorial on youtube- I have to watch it again guy is not a natural instructor - oh well grateful for the seeds and the few Linux tutorials: I want to try setup a profile for Doogee Mix due to little support for it. Think its worthy of a few custom options. [email protected] 'LastStandingDroid" Thank U - I was looking for how to unpack stockmix.rar to fastboot flash for a restore, Can I use those same basic files to create a skeleton profile for custom rom? I'm just frankensteining
Here the archive means the flashable custom rom :laugh:
Click to expand...
Click to collapse
in my "archive" i have only md5 files no folders pls help
Hello Everyone.
Let me just start by saying I AM NOT a developer and do not take credit for this information. Just did some Googling and came across it and I haven't really seen this in the forum here and I really found it useful. It is a link to an article with instructions on how to set up ADB without the massive developer download that comes packaged with the standard Android SDK. Written by Lalit Indoria on the "Hack My Android" site.
Basically it allows you to easily run ADB commands without ANY complicated set up. Remember you will still need the proper drivers for your device and always follow instructions so you don't bork anything up. I followed this to both flash the new 4.4 image and also root my Nexus 4. With it being the weekend I don't suspect we will get any OTA until Monday at the earliest so for those of us that are growing ever impatient.. here you go. Enjoy. :good:
http://www.hackmyandroid.com/use-adb-fastboot-commands-without-installing-android-sdk/2479
Also on recent debian distributions (currently debian jessie - testing - and debian sid - unstable), or ubuntu quantal and newer, you can simply install adb and fastboot by installing a few packages:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
jcnbama said:
Hello Everyone.
Let me just start by saying I AM NOT a developer and do not take credit for this information. Just did some Googling and came across it and I haven't really seen this in the forum here and I really found it useful. It is a link to an article with instructions on how to set up ADB without the massive developer download that comes packaged with the standard Android SDK. Written by Lalit Indoria on the "Hack My Android" site.
Basically it allows you to easily run ADB commands without ANY complicated set up. Remember you will still need the proper drivers for your device and always follow instructions so you don't bork anything up. I followed this to both flash the new 4.4 image and also root my Nexus 4. With it being the weekend I don't suspect we will get any OTA until Monday at the earliest so for those of us that are growing ever impatient.. here you go. Enjoy. :good:
http://www.hackmyandroid.com/use-adb-fastboot-commands-without-installing-android-sdk/2479
Click to expand...
Click to collapse
Mini-adb comes with adb.exe, fastboot.exe and two adb .dlls needed to run adb in windows. So basically to run adb all that is required is 3 files. Also fastboot doesn't require anything except the executable. Mini-adb has been out there for about 2 years that I know of on androidforums.
fredericve said:
Also on recent debian distributions (currently debian jessie - testing - and debian sid - unstable), or ubuntu quantal and newer, you can simply install adb and fastboot by installing a few packages:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
If you do that, you also need to do step 1 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
You can install the Wugs nexus toolkit. It has all the features you need.
eksasol said:
If you do that, you also need to do step 1 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
That was not necessary on my debian Sid install. Yesterday I simply installed the packages, Co nected my nexus 7 and used adb sideload to flash the kitkat ota.
The steps seem to apply to Ubuntu precise. Maybe it is not necessary in newer versions.
REMOVED
abhimortal6 said:
Got Broken Screen ??
Need To Backup Data or Still Want To Use Your Phone As a Zombie Machine??
Here's The Solution.
Now Fully Control Your Zombie Android's Touch Screen Without Installing Crappy APK.
Or Configuring Your PC Network To Work It Out.
Debugging Must Be On In Order To Use This
Directions To Control Broken Screen. Please Read Very Carefully.
Download .zip Given Below
Extract .zip
Double Click On "RUNME.bat"
Yes That's it ....!
Note : Java Is Required To Run This Program.
For Windows
For Android 2.2+
Download
For Android 4.0+
Download
For Mac/Linux
For Android 2.2+
Download
For Android 4.0+
Download
Mac/Linux Users : Start adb Manually
Hey Don't Forget To Hit Thanks
More Info.
Whats This Program?
Its Android Screen Cast Developed By Unknown Developer Very Long Ago.
But Android Screen Cast Was OutDated And Very Buggy
But After Hours of Tweaking With Source . I Managed To Work It On Latest Java
Bugs Fixed
Issue Fixed Causing Error In Java7+
Android 4.0+ Support Added
Standalone Jar (Still Needs To Run ADB Before Jar Execution)
Click to expand...
Click to collapse
You don't bring anything new except ADB supplied in ZIP
It's simple copy of https://code.google.com/p/androidscreencast/ project (and developers are pointed there)
And even don't open sources...
xSAVIKx said:
You don't bring anything new except ADB supplied in ZIP
It's simple copy of https://code.google.com/p/androidscreencast/ project (and developers are pointed there)
And even don't open sources...
Click to expand...
Click to collapse
*HATER*
Do You Even Read!!
abhimortal6 said:
Got Broken Screen ??
Need To Backup Data or Still Want To Use Your Phone As a Zombie Machine??
Here's The Solution.
Now Fully Control Your Zombie Android's Touch Screen Without Installing Crappy APK.
Or Configuring Your PC Network To Work It Out.
Debugging Must Be On In Order To Use This
Directions To Control Broken Screen. Please Read Very Carefully.
Download .zip Given Below
Extract .zip
Double Click On "RUNME.bat"
Yes That's it ....!
Note : Java Is Required To Run This Program.
For Windows
For Android 2.2+
Download
For Android 4.0+
Download
For Mac/Linux
For Android 2.2+
Download
For Android 4.0+
Download
Mac/Linux Users : Start adb Manually
Hey Don't Forget To Hit Thanks
More Info.
Whats This Program?
Its Android Screen Cast Developed By Unknown Developer Very Long Ago.
But Android Screen Cast Was OutDated And Very Buggy
But After Hours of Tweaking With Source . I Managed To Work It On Latest Java
Bugs Fixed
Issue Fixed Causing Error In Java7+
Android 4.0+ Support Added
Standalone Jar (Still Needs To Run ADB Before Jar Execution)
Click to expand...
Click to collapse
Hi ^^
i can see my Oneplus One with KK 4.4 but i can't control it with my Windows 8 with Java 8.45. I'm root.
Any idea?
Thx in advance ^^
OP removed information
Thread closed