Database Users

[SCRIPTSET v2.6][02/28/2012] Build native GNU/Linux applications: the easy way

New: SANE (USB Scanner backend and drivers) - OTG equipped device needed to work for this - YES, Scanner Access Now possible and Easy with your phone
This can (in combination with tesseract-ocr) be very useful to recognize text from scanned images.
For pictures see also http://forum.xda-developers.com/showpost.php?p=23046120&postcount=187
Update 01/30/2012: Now with a small android app (ScriptStarter) to start services and other shell scripts easily from the GUI. See bottom of the post.
WHAT'S POSSIBLE WITH THIS SCRIPT:
With this bash script your are able to build relatively easy from source a lot of native software (over 90 at the moment) from the GNU/Linux community for your Android phone and you will have
the good experience with free software.
All these tools and programs are not "apps for the GUI" for Android but native running command line tools "under the surface" of your Android GUI like the kernel and other services.
Don't ask me if it makes any sense to install program xy (like MySQL) on a phone. This is your decision. It's possible, so try it and see what you can do with it.
Note: I tested most of the compiled software on a Samsung Galaxy S2 (my phone). I cannot test it on a variety of phones because I have no mobile phone shop...
Currently buildable with this scripts (abstract, see the full list in package_selection.conf):
PHP 5.3.10 (with almost all extensions and XCache)
MySQL 5.5.19 (if you want a full database server on your phone...)
lighttpd 1.4.30
OpenSSH 5.9p1
OpenSSL 1.0.0f
Samba 3.6.3
cURL 7.23.1
bash 4.2
BusyBox 1.19.3
ImageMagick 6.7.4-10
OpenVPN 2.2.2
Python 2.7.2
Node.js 0.6.7
git 1.7.9
Wget 1.13.4
Rsync 3.0.9
TCPDUMP 4.2.0
Midnight Commander 4.8.1
Pure-FTPd 1.0.35
screen 4.0.3
iptables 1.4.10 (without bionic bug "getnetbyaddr()" and with iptables-save/restore!)
BIND 9.8.1-P1
Lua 5.2.0
Ruby 1.9.3-p0
usbutils 004
MTDUtils latest git
GCC 4.6.2 (c, c++)
GNU Coreutils 8.14, Binutils 2.22, Findutils 4.4.2, Inetutils 1.8
QEMU 0.15.1
SANE 1.0.22
tesseract-ocr 3.01
...
a lot of libraries, development tools and other useful programs
...
FEATURES:
automatic download and untar the cross-compilers (if not already done) for cross compiling
automatic download and untar the source packages (if not already done), that you have selected
solve dependences and reserves additional needed packages
apply patches to the sources if necessary
build them, "install" them in a folder for later "ready to transfer" to your phone and stripes the binaries and libraries to reduce the filesize if selected
autogenerate a tar file and adb push the file to device if selected
allows you to use well-known software like PHP, MySQL, OpenSSL, OpenSSH, OpenVPN, bash and lighttpd on your phone (see the full list in file package_selection.conf, see attachement)
scripting and development on your phone
no limits with BusyBox (without want to be derogative, BusyBox is a wonderful tool), full featured tools like Coreutils, Binutils etc.
build scripts are expandable with other or newer packages you eventual want to have
QUESTIONS AND ANSWERS:
Q: Do I need native GNU/Linux programs and what is that?
A: If you do not know what native Linux applications are, then stop here - you don't need them.
Q: What can I do with these tools?
A: Many things. As a developer you can use the libraries to include them in Android GUI apps, as user you can start for example a webserver on your phone and write some HTML or PHP pages
just for fun or replace BusyBox with full featured tools (or only some commands).
Some tools are also very useful to find network errors, check the network traffic and many more.
Q: What do I need?
A: A Linux installation (VM or real), some Linux knowledge and a little bit time to read all instructions carefully. A rooted Android device with enouth free memory (ext2/3/4 formatted)
See README for details.
Q: Costs?
A: Nothing. The scripts are Open Source (GPL v3), the packages are GPL licensed or under a similar license. The cross-compilers are Open Source or free to use for non-profit purposes.
But I would be pleased if I get a donation and/or a press on the "Thanks button", if the scripts are useful for you. It was a long and hard work...
Note: The attachement scriptset-x.yy.zip is double packed (inside .bz2), because I want preserve the right settings of the scripts.
STEPS:
Selected the desired packages in the config file
Adjust the compiler settings for your phone
Run the build script to download and compile the software
Copy the generated TAR files to your phone or let "adb" this do for you and unpack them in the prepared sysroot folder
For more information please read the instructions in "README"
Please let me also know if you have any problems or if you have questions or further suggestions.
Thanks go to the Open Source community and a lot of people/webpages with hints about cross-compiling software.
Thanks
smitna
CHANGELOG:
01/14/2012 First public release v0.9
01/14/2012 Update: Removed unneeded big patch for ncurses
01/15/2012 Release of v1.0
Update: Fixed build of gcc. Note: the header files are not copied automatically with the script.
If you want to compile on your phone, set TAR_HEADERS=1 in configuraton.conf
Typos: some translations corrected in build.sh
01/16/2012 Release of v1.1
Update: Removed building of fsck from util-linux-ng, it's in e2fsprogs
Update: ISC Cron / vixie cron: set correct paths in pathnames.h before compiling
Enhancement: More detailed explanation of device specific compiler settings with list of possible values
Update: Removed dependence e2fsprogs libs from e2fsprogs
01/17/2012 Release of v1.2
Update: Build of zip, zipcloak, zipnote, zipsplit, unzip, unzipsfx and funzip now possible without errors
01/17/2012 Release of v1.3
Update: Added Node.js
Typos: some translations and language errors corrected in build.sh and README (sorry, I'm not a native English speaker...)
01/18/2012 Release of v1.4
Fixed TMP_PATH in PHP extension XCache (mmap.c) to prevent startup warning
Fixed BusyBox problems with static build against glibc ("__getpagesize" segfault with ping, traceroute and other networking parts)
and added some BusyBox patches.
BusyBox is now dynamic linked, so don't replace the system BusyBox with this build, because of missing mount/paths to libraries at phone startup
01/20/2012 Release of v1.5
Update: Cleanup in scripts and separation of configuration and code. Now it's only necessary to edit configuration.conf and package_selection.conf
Update: Added gzip
Update: Added experimental adb push to device if the device is connected and permissions are ok
Update: Check for installed programs. Script now exists on check failure to minimize errors while compiling.
01/21/2012 Release of v1.6
Bugfix: MySQL build could fail if gen_lex_hash could not generate the file sql/lex_hash.h in pass 2
Update: adb push should now work, check for connected device (and possible multiple devices) and check for right permissions to use the device
Enhancement: Even more explanation of device specific compiler flags and some hints to find the right settings.
01/21/2012 Release of v1.7
Enhancement: To eliminate sure a failing MySQL build, with every new run the source folder will be removed before completely
Enhancement: file version is now strictly checked (the host version must be the same as the cross version)
Some minor changes and filechecks (e.g. autoconf)
01/23/2012 Release of v1.8
Bugfix: Python has SQLite dependencies and SQLite must be ready before Python configure/make
Bugfix: In certain circumstances the optimizer settings get lost
Bugfix: Removed --enable-multibyte from bash, no chance to use it with NDK
01/24/2012 Release of v1.9
Update: Added ngIRCd (Please read the comment for this server, because of running as root)
Update: Sorted the links and package names in the config a little bit...
01/26/2012 Release of v2.0
Bugfix: OpenSSH wants to touch /var/empty while compiling, should be fixed --with-privsep-path now set (thanks to member dateno1 for his reports of such warnings/errors)
Bugfix: Removed a wrong CFLAG -I path from NDK config (only useful for me, really useless for others...)
Enhancement: Example for a user db for Pure-FTPd virtual user database in README (please use virtual users, it's the best and easiest solution)
Update: OpenSSH build need ssh-keygen for the generation of the default keys, added this info to README and the package selection
Bugfix: Not really a bugfix, but some installers don't set the right permissions of libraries in the sysroot folder, so set them global in the final task
Bugfix: Removed --with-lastlog=$TARGET_SYSROOT/var/log/lastlog from OpenSSH and added --with-lastlog=no, I don't know why this is not working and throws a warning, but we can live without it...
Enhancement: Added option to choose the sysroot variant from the CodeSourcery libs: v5TE (default), v4T (old), thumb2 (v7, fastest if supported by the phone)
Enhancement: Added option to tar the headers for development on the device with CodeSourcery (hint: always set rpath in LDFLAGS to make use of the CodeSourcery libs)
01/26/2012 Release of v2.1
Update: Added getcap/setcap and libraries from wishlist, needs libtoolize. Note: This is in a testing stage, kernel and filesystem support needed!
01/30/2012 Added a ScriptStarter app
09/02/2012 Release of v2.2
Update: Local compilation of static "tic" from ncurses for buildhost, if ncurses installation is missing
Enhancement: "downloading only" mode without compiling the packages (and force download)
Enhancement: some parameters for starting the script with additional functions (show with ./build.sh help)
Enhancement: more logging and outputs
Enhancement: language specs, all outputs can be changed to other languages in build.sh
Update: Added dosfstools
Update: Added Ruby
Update: Added example configs and starter scripts for Samba and OpenSSH
Update: Use of http-URLs if possible and update of some broken external links since last release
Bugfix: util-linux-ng needs gettext, added dependence
Bugfix: Added parameter to Samba to solve user/group settings and socket_wrapper support to set path vars at runtime
Update: Changed PHP version to 5.3.10, Samba to 3.6.3 and git to 1.7.9
02/11/2012 internal Release v2.3
Bugfix: openVPN patch for /dev/tun and links to ip/netstat/ifconfig/route, see hints for symlinks
02/16/2012 internal Release v2.4
02/25/2012 Release of v2.5
Update: Added LAME
Update: Added experimental CUPS
Update: Changed PNG version to 1.5.9
Update: Added Net-SNMP
Update: Added Netpbm
Update: Added PNG 1.2.47 for Netpbm and phpSANE
Update: Added LibTIFF
Update: Added SANE (USB Scanner backend and drivers) - OTG equipped device needed to work for this - YES, Scanner Access Now possible and Easy with your phone
Update: Split patches for bash (4.1 and 4.2) for better and easier (automatic) inclusion of original patches
02/28/2012 Release of v2.6
Update: Added Cuneiform OCR
Update: Added tesseract-ocr (see hints for more details howto use it)
ScriptStarter
02/03/2012 Added a small ScriptStarter for the GUI. With this app, written with JQuery, PhoneGap and Java (wrapper to execute the shell scripts) it's possible to start for example the lighttpd web server, Pure-FTPd or MySQL from within the Android GUI without a terminal and read the output. If a script needs root access, there is a checkbox to allow this. For this to work, copy the script sush in the script folder. All scripts ending with .sh can be started (please choose after the first start your script folder on the device to add the scripts to the selection, normally your [SYSROOT]/sbin folder).
Three buttons (start, stop and status) are predefined for start-stop-status scripts, there is also a parameter input field for more start values.
Free GPL v3 source code also included (Eclipse project). Please don't expect too much eye-candy. The GUI could be much better, but my CSS skills are very limited...
I added a few example scripts in the zip file, for example a battery stats reader. Before starting these scripts, have a look in the source code to be sure that they are compatible with your device.
Update 0.97 02/03/2012: Now the stderr is also printed in the output window
Update 0.99 02/10/2012: Replaced scrolling api with a much better solution (jScrollPane) for the output window. Not the real Android scroll feeling, but it's usable.

Thanks! I would hit the Thanks button, but I am on my mobile atm.
Sent from MIUI powered phone

Someone tried it? Problems?
Please, I need your feedback...

Sounds interesting, I'll try once I get back home and share feedback here

now i try to all packages for test
i will test on cortex a8 (motolora xt720)
TARGET_MARCH="armv7-a" (not work on armv7 )
TARGET_MTUNE="cortex-a8"
TARGET_MFPU="neon"
TARGET_MFLOAT="softfp"
it make dynamic binarys but i don't want dymanic type (because it difficult to divide one thing and maybe not work on android's libs)
how can i make static type?
ps : oh...it has so many comile error (even can't read or count all)

dateno1 said:
i will test on cortex a8 (motolora xt720)
TARGET_MARCH="armv7-a" (not work on armv7 )
TARGET_MTUNE="cortex-a8"
TARGET_MFPU="neon"
TARGET_MFLOAT="softfp"
it make dynamic binarys but i don't want dymanic type (because it difficult to divide one thing and maybe not work on android's libs)
Click to expand...
Click to collapse
I hope I understand your question. Why not dynamic?
Yes, you have to set the parameters for your mobile phone. For TARGET_MARCH try "armv7", for TARGET_MFLOAT "softfp" and for TARGET_MFPU "vfp" but check this last setting carefully for this phone.
It's very hard to build a full static binary (and sometimes nearly impossible) and it's also hard to build against bionic (with NDK). I had no good experience with it . A lot of compiler runs wasn't sucessful. Edit: I also had for example massive problems with openssl. I couldn't find a way to build it with NDK or static and then build other programs like cURL with openssl support.
Static binaries are also too big and not necessary. For this we have a sysroot environment to be independent from bionic and without the restrictions. The compiled libs and binaries are linked to the CodeSourcery glibc and have set the custom "rpath" for the dynamic loader. That's no problem I think.

that's simple
if someone want to make some binary for all version of android (even same cpu) it will not work well (defend on basic lib(ex : libc) is ok but complex things will not work)
i know make static type binary is very difficult but it valable

dateno1 said:
that's simple
if someone want to make some binary for all version of android (even same cpu) it will not work well (defend on basic lib(ex : libc) is ok but complex things will not work)
i know make static type binary is very difficult but it valable
Click to expand...
Click to collapse
You are right, if you want to build a "portable" binary, you have to set very safe settings, like TARGET_MARCH="armv5", the full list is in the "README". But it's not my main target to offer a solution that is easy portable to other phones, instead you can build the software with optimizations for your phone to "get the best" for it

smitna said:
You are right, if you want to build a "portable" binary, you have to set very safe settings, like TARGET_MARCH="armv5", the full list is in the "README". But it's not my main target to offer a solution that is easy portable to other phones, instead you can build the software with optimizations for your phone to "get the best" for it
Click to expand...
Click to collapse
just i want to add some more function on the phone
thanks for patch files

I want to try this, to install some apps(most interested fro mc), but I don' t wanna change my sd card.
Can I use phone' s /data partition as mysysroot directory? I have 1.5GB space available on data partition, it is 2GB all.
And If yes, I must create the dir: /data/mysyroot? And where to create this dir on pc? On root directory of my linux system?

dancer_69 said:
I want to try this, to install some apps(most interested fro mc), but I don' t wanna change my sd card.
Can I use phone' s /data partition as mysysroot directory? I have 1.5GB space available on data partition, it is 2GB all.
And If yes, I must create the dir: /data/mysyroot? And where to create this dir on pc? On root directory of my linux system?
Click to expand...
Click to collapse
You can use the /data partition. Just create a new folder, for example /data/sysroot. On your PC you have to create the same temporary with full user rights. This is not your working dir for building. Create a new dir in /home/user and unpack the files there. In settings insert the /data/sysroot as TARGET_SYSROOT and change the other settings for your phone and choose mc=yes. Then start the ./build.sh

Thanks for your quick answer.
Just to make clear because my english understanding is not in a high level
I must create the /data/sysroot dir under "/"(root directory) on linux pc with superuser rights?

dancer_69 said:
Thanks for your quick answer.
Just to make clear because my english understanding is not in a high level
I must create the /data/sysroot dir under "/"(root directory) on linux pc with superuser rights?
Click to expand...
Click to collapse
Yes, that is right. But this is the only step you need to do as root or better with root rights. After this work as usual as user.

oh it can't make mysql
package selection : mysql only
target directory (prefix) : /sddata/mysql (on sdext on my system)
armv7-a
cortex-a8
neon
softfp
then run ./build.sh 2> error.txt
it is my error messages
http://pastebin.com/g7Yi4bGz
sorry you can see this link only today (my mistake)
this setting can make some binary and lib run on my phone but fail to make gcc or mysql (when i try gcc it just fail to making gcc only (other things were made) )

dateno1 said:
package selection : mysql only
target directory (prefix) : /sddata/mysql (on sdext on my system)
armv7-a
cortex-a8
neon
softfp
then run ./build.sh 2> error.txt
it is my error messages
http://pastebin.com/g7Yi4bGz
sorry you can see this link only today (my mistake)
this setting can make some binary and lib run on my phone but fail to make gcc or mysql (when i try gcc it just fail to making gcc only (other things were made) )
Click to expand...
Click to collapse
Please notice first, that you should not run this script as root!!
Then there is something wrong with the build of the first needed packages:
ZLIB=yes
OPENSSL=yes
CURL=yes
GETTEXT=yes
LIBXML2=yes
READLINE=yes
NCURSES=yes
- The script cannot find the readline sources. Do you have a subfolder readline-6.2 in folder sources in your builddir? Same for the other source folders. The script first downloads the packages to folder packages, extract the tars in folder sources, repeated for all selections.
(look at line 67 in your log: ./build.sh: 1402: cd: Python-2.7.2: No such file or directory)
- You have no "xz", install it first and make sure, that the other necessary packages are installed. MySQL and gcc are "two pass" compilations and this builds generating temporary binaries, runable on your linux pc. So you need all for a successful compilation of such binaries like gcc, make, python etc. on your linux machine. If you are using Ubuntu, then install the "meta-package" build-essential, look in the README.
Do you have the other unpacking tools like gunzip etc. Please install also "bison"
You should do following steps:
1. First select only the necessary packages (see above), all others to no.
2. If zlib, python, readline an the others are cross-compiled (without errors) and the libraries are in ./sysroot/lib, then deselect them (=no) and select mysql=yes and start a second run with ./build.sh

smitna said:
Please notice first, that you should not run this script as root!!
Then there is something wrong with the build of the first needed packages:
ZLIB=yes
OPENSSL=yes
CURL=yes
GETTEXT=yes
LIBXML2=yes
READLINE=yes
NCURSES=yes
- The script cannot find the readline sources. Do you have a subfolder readline-6.2 in folder sources in your builddir? Same for the other source folders. The script first downloads the packages to folder packages, extract the tars in folder sources, repeated for all selections.
(look at line 67 in your log: ./build.sh: 1402: cd: Python-2.7.2: No such file or directory)
- You have no "xz", install it first and make sure, that the other necessary packages are installed. MySQL and gcc are "two pass" compilations and this builds generating temporary binaries, runable on your linux pc. So you need all for a successful compilation of such binaries like gcc, make, python etc. on your linux machine. If you are using Ubuntu, then install the "meta-package" build-essential, look in the README.
Do you have the other unpacking tools like gunzip etc. Please install also "bison"
You should do following steps:
1. First select only the necessary packages (see above), all others to no.
2. If zlib, python, readline an the others are cross-compiled (without errors) and the libraries are in ./sysroot/lib, then deselect them (=no) and select mysql=yes and start a second run with ./build.sh
Click to expand...
Click to collapse
i'm not edit necessary part
ZLIB=yes
OPENSSL=yes
CURL=yes
GETTEXT=yes
LIBXML2=yes
READLINE=yes
NCURSES=yes
i just edit mysql=no => mysql=yes
ok try to install packages and run as not root

dateno1 said:
i'm not edit necessary part
ZLIB=yes
OPENSSL=yes
CURL=yes
GETTEXT=yes
LIBXML2=yes
READLINE=yes
NCURSES=yes
i just edit mysql=no => mysql=yes
ok try to install packages and run as not root
Click to expand...
Click to collapse
Good luck!
If you can wait a little bit:
In a short time I release a new version with better error and program checks and some small bug fixes. With this version it's not longer necessary to edit the build.sh, it's now all in only two separated configuration files (configuration and package selection).

hmm...fail to compile mysql again
with this error
note: the mangling of 'va_list' has changed in GCC 4.4
full error log on http://pastebin.com/jd1Pw9Xw

dateno1 said:
with this error
note: the mangling of 'va_list' has changed in GCC 4.4
full error log on http://pastebin.com/jd1Pw9Xw
Click to expand...
Click to collapse
Hello dateno1,
first: you have *NOT* changed to a user account as promised
The va_list is only a note, not an error, no problem (but ask the MySQL devs why they haven't adapted the code to gcc 4.6.1).
Your Python cross binaries and libraries are not ok (from you broken first build?). Please start from a "fresh state" (delete the folder sources/Python-2.7.2 and sysroot) or start from a total clean state.
Please use the latest 1.5 version of the script because of the xargs warnings at the end
Delete the complete sysroot folder, there are some folders not in place (data and docs). There is a script remove_all_files.sh
Start this script in your buildroot with ./remove_all_files.sh to remove all files and symlinks in subfolder sysroot.
Edit: delete the sysroot folder complete, there are some other missing folders from your first build!
Start again with ./build.sh and activated packages (the "ALWAYS NEEDED" one and MySQL)

smitna said:
Hello dateno1,
first: you have *NOT* changed to a user account as promised
The va_list is only a note, not an error, no problem (but ask the MySQL devs why they haven't adapted the code to gcc 4.6.1).
Your Python cross binaries and libraries are not ok (from you broken first build?). Please start from a "fresh state" (delete the folder sources/Python-2.7.2 and sysroot) or start from a total clean state.
Please use the latest 1.5 version of the script because of the xargs warnings at the end
Delete the complete sysroot folder, there are some folders not in place (data and docs). There is a script remove_all_files.sh
Start this script in your buildroot with ./remove_all_files.sh to remove all files and symlinks in subfolder sysroot.
Edit: delete the sysroot folder complete, there are some other missing folders from your first build!
Start again with ./build.sh and activated packages (the "ALWAYS NEEDED" one and MySQL)
Click to expand...
Click to collapse
make new account (compile.compile) and use su -c "./build.sh" compile
i think it work (compiled file's owner is changed to compile.compile)
now i delete almost files and folders (exclude android-ndk, readline-6.2, toolchains) and retrying...oh failed (attach new log (full) )
'를 위해 할 일이 없습니다' mean 'no job for~'
'오류' mean 'error'

[Guide][HOW TO]Install a GNU/Linux and tools to make Custom ROMs

HOW to install a distribution of GNU/Linux and configure the necessary tools for the development of ROMs
Autores: TugaPower aka danieldmm e porfirio
Firstly, it is important to say that GNU/Linux is open source software / free, robust, reliable, free and easy installation for any user, even if you have few computer skills.
There are dozens of distributions of GNU/Linux, all available free at: http://distrowatch.com/, so choose that of your choice and according to the hardware capabilities of the machine will be installed where the distribution chosen by you.
The choice of authors this "HOWTO" is based on the distribution of GNU/Linux, Ubuntu 11.10, with the XFCE desktop environment and also the GNOME desktop environment. This is abolished by default the manager's main Gnome desktop environment and in its place put XFCE, to perform the daily tasks of work, which is very lightweight and fast. Or if they want to be more direct, Xubuntu and will soon install from scratch, which will get the same results. Personally, I'm a fan of this graphical environment (XFCE), attending to its lightness, speed, customization, etc..
What will be explained in this HOWTO:
1. Install Ubuntu or any other distribution, such as: Xubuntu, manager native XFCE desktop environment, Kubuntu, manager native KDE graphical environment; Lubuntu, manager native LXDE graphical environment, which uses less hardware resources on the machine all present in this work. Basically, we are always talking about Ubuntu, what changes is only the GUI (Graphic User Interface), where the user goes to work.
2. The process of installation and basic configuration for any of these variants, it is always the same.
3. Do not expect to find in this work, the whole process complete installation and configuration. Only the main roads and where possible, with visual aids. However there are situations so redundant, that does not need that same help. Not the purposes of this HOWTO, other possible configurations, eg setup SAMBA, APACHE, a home FTP server, desktop, etc..
4. Let's begin as follows:
4.1 Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer;
4.2 From the field 16 is a normal installation via live DVD of Ubuntu (Xubuntu, Kubuntu, Edubuntu, Lubuntu).
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU/Linux.
4.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
GETTING STARTED
1. Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer.
1.1 To start this process, you must be made to download an image of the Ubuntu operating system for the machine architecture, or x86 (for CPU 36 bit) or x64 (for 64-bit CPUs).
1.1.1 However, this day, there is some controversy on this subject. Some say that if the machine has 4GB of RAM or more, we always use the 64 bit version, even if the CPU is x86 and also say that if the machine has less than 4GB of RAM, we use the 32 bit version regardless of the CPU is x36 or x64.
NOTE: Rarely, modern computers, whether desktops, laptops, at least have at least 4GB of RAM standard. However, do not relinquish that each CPU (x86 or x64), must have the OS corresponding to your architecture. Therefore it is up to each one choose the best option.
2. ISO Images
2.1 Ubuntu 02.01 11.10 (32bit)
2.2 Ubuntu 02.02 11.10 (64bit)
3.Universal USB Installer
3.1 Now we do download the appropriate version of the distribution, we will have to download the USB Installer: www.pendrivelinux.com/downloads/Universal-USB-Installer/
But what is the purpose of this installation process?
3.2 Firstly, we can be a machine, you have not installed a drive read / write CD / DVD.
3.3 Secondly, avoid using a CD or DVD drive for installation.
4. Run the USB Installer, as Administrator of the OS and this not to happen errors during the copy of the OS to the thumb drive. This procedure is performed as follows:
- Click on the icon of the program with the button on the right mouse button and select Run as Administrator option.
5. After installing the USB Installer, run the program and click on I Agree.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. Now we set the distribution of GNU/Linux, we will be using. I choose Ubuntu 11.10.
7. Now calm down! I hope you remember where it was saved the iso image of Ubuntu! Only then will the USB Installer will be able to recognize and perform the installation on the pen drive. Will normally be in downloads.
8. Insert the flash drive and expect it to be recognized by Windows. In this case explanation, their location is in F.
9. At this point, we select the Format F: Drive to FAT32.
NOTE: If you wish, can create a little more memory to the pen, in case it is likely to change. This is an optional. If your interest, as it is put in the picture.
Now we have everything configured properly, we will click Creat.
10. At this point you will get a WARNING message. All contents of pen drive will be erased. Click YES and continue.
11. Now it is time for a coffee, etc., etc. and wait for the installation process to complete. After this step, we will be ready for installation on the computer distribution.
11.1 While the above task does not end, we can and must perform other actions, such as creating a partition for the Ubuntu operating system.
11.2 Let's Start Menu;
11.3 Clicking the right-click Computer and then Manage;
11.4 Now on the left menu, click Disk Manager;
Arrived here, the C partition, let's click and select Shrink Volume.
12. Let us wait quietly, and very soon we will be faced with the option to reduce the partition chosen. For a minimal installation of Ubuntu, will require approximately 10 GB. However, if we want to later install the updates, music, videos, etc. ... recommend 25 GB. To be closer to the 25GB, 26GB put!
13. The next step is to reduce and click new partition will be marked in black. We will then activate this partition:
13.1 Click on the partition, with the right mouse button and select New Simple Volume.
13.2 Click Next> Next> and choose a letter to the new drive (eg U).
13.3 Now let's change the Volume Label. Put Ubuntu.
13.4 Next Run. We have created the partition and active.
NOTE: Wait now that Universal USB Installer program in the following screen appears indicating that the installation was completed and then click Close.
14. Restart the computer.
15. Immediately press F12 and select USB stick and then press ENTER.
15.1 will appear something like this:
Calm ..... very quiet .... Choose the option Install Ubuntu on a Hard Disk.
16. Now it is like to install via DVD, which I dispense to comment on "How to install Ubuntu 11.10 per DVD." See 4.2 The field from the field 16 is a normal installation of Ubuntu live via DVD.
16.1 After appearing Choose Setup Language, Portuguese choose and click Next. (You pick the language that you anderstand)
Preferably, you must have a fast Internet connection, so that the OS be upgraded soon. In the situation of not being currently available internet connection, do not put the "seen". No problem your installation will proceed smoothly. You can do it later.
17. Then will click on: One more thing, in order to choose the partition for installation.
18. CAUTION ... CAUTION!
18.1 In this field, we have all the possible CARE! The Windows partition can die!
18.2 Should be selected before the partition created in Windows (which is named Ubuntu), and then click Modify. After selecting the partition that was created on Windows (Ubuntu). In the new partition size, and put 21,000 Mount Point select /. After running OK.
The aspect should be this:
19. Now let us take the remaining space in the example 1490MB. Click Modify, and followed by the option Use as we choose and swap area and click OK.
It should be something like this:
20. Next, click Install Now and wait ......
21. Choose the location of the user:
22. Now the installation of the default keyboard ....
23. Enter personal information and click Continue.
24. Installation completed. Reboot the PC.
25. And Behold .....
Choose from the boot menu option Ubuntu .... There is also the option Windows ... Choose!
26. I chose .... Ubuntu with the Gnome GUI!
7. There is a method, also very reliable, to expedite this process, but directed to Mint distribution, which can be obtained here: community.linuxmint.com/tutorial/view/744
NOTE: TugaPower friend and colleague, will use the Mint 12 in the process of compiling ROMs. (In this case S2 i9100 ROM 4.0.3 ICS)
Version used: Linux Mint x64 12 vKDE
Download Links: http://blog.linuxmint.com/?p=1927
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU / Linux.
4.3.1 Installing the JAVA
Open the Synaptic package manager and install the openjdk-7-jdk and mark their dependencies:
Approval for the changes made​​:
Download the required files:
Installation of the necessary files and OpenJDK 7:
Now we have to install JAVA on the machine fully realized, we will proceed to their inspection.
To do so open the command line terminal to write the following command: java-version
4.3.2 Check if the package is installed 7zip more specifically p7zip-full, if not select for installation:
Once this is done we can then proceed with the installation of the Kitchen.
4.4 Installing the Kitchen
4.4.1 Initial Procedures
All information to carry out this section were collected on: forum.xda-developers.com/showthread.php?p=5626292#post5626292
Therefore, our choice falls on dsixda Android's Kitchen (Support Several devices)
(The Custom ROM made in this Guide its based to the Galaxy S2 i9100)
Download link of Kitchen: http://github.com/dsixda/Android-Kitchen/archives/master
Informational Page on Kitchen: http://forum.xda-developers.com/showthread.php?p=5626292#post5626292
After these preliminary procedures have been performed, we proceed to next steps.
By default, you will be allocated in the Downloads folder files.
4.4.2 Click on the file up with the right button of mouse and perform the extraction of the file to the Downloads folder:
4.4.3 Change the file name for kitchen (it's easier to work).
4.4.3.1 Move or Copy to folder or Personal Home:
They should stick with a structure like this:
4.5 Perform download the ROM Stock
NOTE: I personally recommend two sites:
http://forum.xda-developers.com/showthread.php?t=1075278
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regional
Download the ROM to be used in Kitchen, in this case we use the XDA, specifically the XWLP7:
NOTE: The screenshot references XWLP4 because at that time had not XWLP7
4.5.1 Download the kernel corresponding CF-root (This way remains CWM Recovery Busybox and SuperUser GB, if ICS SuperSU depends the kernel used to cook the ROM.
4.5.2 Download the kernels on CF-root: http://forum.xda-developers.com/showthread.php?t=1103399
NOTE: This case will be used the latest available to ICS, the CF-root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip
NOTE: It is already available in the XDA KERNEL CF ROOT XWLP7.
4.5.3 Copy the file from the ROM inside the Kitchen to the folder original_update
4.5.3.1 If the file is in the form *******. Tar.md5 have to remove the. Md5 so that it only ********. Tar
After these steps have been made ​​in all its fullness, then we have all the necessary files to start our cooked
4.5.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
4.5.4.1 In order to run our furnace we have run the Kitchen in a command line also known as terminal or console, for it will open a command prompt within the folder Kitchen:
In order to execute the Kitchen just run the following command as root sudo. / Menu in the terminal:
6. First thing to do is point 1 or set a folder where we work. In this process the Kitchen will get to select and give the stock ROM original_update previously placed in the folder, simply enter the next screen and then select the ROM list:
Therefore, we select the first option because we only have a ROM in the kitchen, so just to enter a default because it's one
6.1 In the kitchen will then ask if we want to keep the name.
This name stock is organized as follows: WORKING_DATA_HORA, this can be changed to whatever you want, the only thing required is to keep the WORKING_
In this case I press the button to change the name ye WORKING_XWLP7_TugaPower:
To continue then just press Enter.
7. The kitchen will start the process of extracting the file from the ROM to the folder with the name we gave earlier WORKING_ ********
In this process we have to decide if we want to use the CSC (NET configuration and applications) that are included with the Stock ROM or NO.
By default this is set to YES ...
Thus, we can, because the Kitchen gives the following list of apks existing CSC and if we add the folder WORKING_ *****
Remember that in most cases, there is no problem in using the CSC Stock ROM, just advise not to use the apks the CSC because they are essentially propaganda NETWORK, which can be set to follow in the next menu to the Kitchen already well default to not add the apks:
Ready to the next step?
8. After the CSC will appear in the information regarding the boot.img, here we select the letter n because for the effect of Custom ROM do not need!
9. Then will come the question if we want to see information about the ROM.
This option is your choice will; default is Y. I personally put n. Now let's return back to the first screen which means that the necessary files are all ready ....
10. In this field, you may want to check whether there is a need to use option 2 and 3.
10.1 In the case of using the KERNEL Stock are advised to do option 2 and 3.
If the kernel you are going to use is for example the CF ROOT or any other that already have root then there is necessary to make the option 1 and 2.
10.2 In this case I will use the CF KERNEL, we will open the zip file of CF ROOT Kernel, find a file ****.tar, opening the file we find the zImage (KERNEL), selecting the zImage we proceed to the extraction process to the working folder of the Kitchen, in this case to the folder: Working_XWLP7_TugaPower
A new window will appear saying that the file already exists, just select and replace the existing ...
11. We will now switch to the Kitchen 7. Kitchen is a default to NO WIPE ROM, option 7 serves to change this ...
12. In this case I do WIPE version, you just will access option 7 in the next field and put y:
12.1 This procedure will eventually lead back to the main menu of the Kitchen. Now we have to think whether we want a ROM or deodexed ODEXED Stock ...
12.2 If we use a version ODEXED we can switch to the option 99 which will be explained below, because I'll use this version deodexed and before passing the option will be option 0 99: ADVANCED OPTIONS
IMG]http://i.imgur.com/XtfZp.png[/IMG]
13. Here I select option 11 to deodexed ROM:
13.1 Now we need one more aspect to consider: what kind of ROM, if GB or ICS.
In this case as I am using a ROM ICS will change the level of API's Kitchen and they default to GB, so I'll use the v
14. Then I confirm that I change the level of the API key y.
In this case I set the API level to 15 which corresponds ROM will be concerned that I'm using ICS 4.0.3:
14.1. Now set the API, I will proceed to the DEODEX ROM for option b, which is advised, because this way, will deodexed the system / app and system / framework.
15. Will be asked if you want a log deodex, this is your charge, if you put y, a file will be created in the root folder of the Kitchen with Deodex process, this log can be used to screen for possible errors that occur in deodexed; I always use the log file because the design is not great and always give way if there are problems in deodexed.
16. After this step made ​​the Kitchen will carry out the relevant technical Deodexed ROM:
17. Now just wait, if you can go for a coffee or a cigarette because it still takes a bit if they do not get any errors and the process goes well deodexed will be presented the following screen:
18. Pressing the Enter, go to the submenu of Kitchen Advanced Menu.
We will then press 0 to return to the main Kitchen; next step we change the name of the build of the ROM (this information that appears in the menu on the About the Phone.
18.1 For this press the key 8 from the Main Menu of the Kitchen, in which case I will change to XWLP7 Stock by TugaPower:
http://i.imgur.com/I6ZXw.png[IMG]
19. Press Enter, then we will change back to the Main Menu Kitchen, now is the time better, create CWM zip file for flashing the ROM :)
19.1 For this we will then press the Option 99:
[IMG]http://i.imgur.com/eYhj4.png
NOTE: Because you are beginning to learn how to make Custom ROMs recommend the first option which is already the default and that the Kitchen, then just do enter in the respective options that appear to the end:
Until we reach the end of file creation can change the name of it, this is the last question that makes the kitchen:
Done this you can find the ROM inside the OUTPUT folder in the Kitchen ...
You only need to copy to the memory of the phone and make the flash.
Have a good cooked and good flash
ROM that was created in TUTU --->
XWLP7 Stock By TugaPower

a hell lot of screenshots, foolproof guide, really great one for beginner

Thanks.. Must have !!

Thanks fool proof, full of screens and has each and every detail.
:thumbup:

randommmm said:
a hell lot of screenshots, foolproof guide, really great one for beginner
Click to expand...
Click to collapse
aditya_7298 said:
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
Click to expand...
Click to collapse
Thanks guys...
Cheers

wow really Great Guide.....................

[Tool] adBeast - CrossPlatform ADB utiltiy (Updated 3/6/13)

Finally, a crossplatform ADB utility.
adBeast (Pronounced: Aye dee beast) is a program I'm developing in java to help automate some of the thing that ADB can do,
some of these things include:
-open web pages on your device
-pull/push files
-send key presses
-port forwarding
-reboot
-boot into recovery
-mute phone
and you'll be able to do all these much easier.
this will be open source, and I'll release the source code after the final alpha build (lots of housekeeping to do)
This is the beta release so a few things may not work all the way...
-------
Using:
Download the Base file for your OS,
Linux users get: adBeast_Base_linux.tar.gz
Windows users get: adBeast_Base_Windows.zip
Mac users:{
(I don't have a mac, so I can't make you a script, sorry)
download the linux base, and copy replace the provided 'adb' file with
your adb file, if your adb file had an extension, like .app or .dmg
then edit os.txt to match the name of your file,
then run the script from within your terminal
}
_________
Updating:
----------------
Once a new version is released,
If you have the Base files already
then all you'll have to do, is download the updated jar file,
and replace your old 'adBeast.jar' with the new one.
____________
Source code:
-------------------
If you want to be ahead of the curve,
you can get the preview version source code,
it may have minor bug fixes, or new features,
that have not been included in the release version yet!
You'll have to compile it yourself though.
https://code.google.com/p/adbeast/source/browse/#svn/src
The source code for the current release is attached to this post.

Release notes:
change log:
March-6-2013
-Push/pull/install APK no longer work (not sure why, should be fixed in the next release.)
+New option to lauch webpage on device
+New (very basic) GUI
+Option to reboot device into recovery
*Fixed port forward
+Enhanced text transfer ability
+Ability to send a string of text to device
+Quit option in GUI/Text mode
+bug fixes
+read adb's stout.
Feb-7-2013:
+source code released.
+Basic text based menu (I forgot a quit option lol)
+push files to device
+ability to reboot device
-removed the "lol lol" print
+Added cross platform ability,( linux version should work on mac, but you'll need to switch out the ADB executable)
Feb-5-2013:
+initial release (tech demo) Linux only.
+Prints "lol lol" to your device

in progress
Done:
-cross-platform (support)
-reboot device option
-basic menu
-provide source code
-push files
-user interface (text based)
-port forwording
-exit program option
Next Release:
-chose text to be sent
-pull file
-Install apk files
-make text type faster
-allow user to set text
-GUI
currently working on:
- translate adb feedback (device offline=ADB cannot connect to your phone)
-Fix adb push/pul
-get feedback from adb (failed/success)
Maybe later:
-Remote file browser, using CD/LS to read files from the device and allow the user to search through them.

Dose anyone out there have a mac?
I need some one to get me the ADB executable,
And I may need them to test some scripts.

[Toolkit][Windows&Linux(Wine)] Already Setup Adb/Fastboot Environment and Installer

[Toolkit][Windows&Linux(Wine)] Already Setup Adb/Fastboot Environment and Installer
First, I take donations.
Second, see the 2nd post about Windows XP compatibilty.(XP requires that the tool be used on a usb drive or a partition that does not contain the current running operating system)
(For the other OSs it works fine on the drive with the running OS) (For Linux see the last post)
Third, XP users that don't have a removable drive available can use the XP-ONLY version on the local drive.
Fourth, read EVERYTHING here on the first and last post.
Fifth, adbClient is a download, unzip, connect to phone package that requires nearly no setup at all allowing you to use the android debugging bridge.
If you want to install adb and fastboot use the "instadb" command.(If you get an access denied error, you must have the administrator password and check your typing)
ANSWERS TO YOUR PROBLEMS:
If you want to update but continue to keep automagically using your work folder: you must copy the Work folder into the folder above the updated bin folder.
Like so: extract the new package. copy the old work folder into the new extracted folder. your work folder should sit right beside the launchadbclient script and the updated bin folder.
This tool can be moved anywhere alongside the work folder
HOW TO USE:
To launch the script extract the zip and run LaunchadbClient by double clicking on it.
Type "xt" without quotes to see a menu for commands.
Check out some package management by typing apk.
To install adb and fastboot to the system without fiddling with environment variables use the instadb command.
DRIVERS:
Visit this link first to enable usb debugging:
To utilize the Google usb driver extract its zip and right click the android_winusb.inf file and hit the install option.
If Google's drivers dont work or you have no drivers or adb doesn't mention any connected devices at the top of the window then you need to visit your manufacturers website for your phone's driver.
Here is the pdanet all purpose adb driver that is pretty much fail proof. if you have any issues with it uninstall it and try another one from below.
If all three of those driver suggestions are not applicable then read the "OTHER DRIVERS" category:
OTHER DRIVERS: The Universal Naked Driver is a good one. Or you can follow this exceptional tutorial for all purpose adb driver installation (I am not responsible for any issues with the tutorial, I just found it.)
I recommend Adb Konnect from the play store if drivers are a problem.
Sometimes your usb cable is keeping you from using adb, so try changing cables.(this actually just happened to me with my samsung usb cable and i ended up using my nexus 7 one instead)
DESCRIBE THE TOOL:
This tool is here to make my life(and your life) with adb easier.
It's the windows command line on steroids.
It is made for being put on a flash drive and being used on different computers.
Especially if you are using someone else's computer but want to keep an environment with your tools and files in it where you could just load it up from a flash drive.
It uses shortcuts for tools including and can autoroot etcetera among other features. This tool is free to use and distribute\modify with my name attached. It contains a presetup adb and fastboot environemnt and has extra binaries\scripts for working with the windows command line and android easier.
Overall it makes interfacing with android over adb much more interesting.
GETTING THE TOOL AND INFO:
1.9.5-XP_ONLY is for the Windows XP desktop only.
Version 3.2.9 is the latest stable release, Use this version please. Thanks for your interest.
If you want to take a snapshot of the latest development go here.

ANNOUNCEMENTS: I now have a donate button if you want to see more development.
I don't support 2.2 or 1.9.5 anymore. Only 3.x.
KNOWN ISSUES: tar might not work.
apklist won't auto exit because of the more pipe. just use control-c for now to unfreeze it
Some of the scripted adb commands stall.
EXTRA INFO:
The only thing that I own in the zip is the scripts. The copyright notice and license for android sdk and included files is included as Notice.txt and Noticeforadb.txt in the LicenseForAdbEtc.zip
With this tool their is no need to install adb or fastboot on your computer just run the script.
If you get an antivirus warning its because of the Zergrush, Psneuter, Framaroot, and ExynosAbuse root exploits.(And the Hstart binary sometimes)
I am not malicious anyway.(You can read my code easily)
You can copy the folder wherever you want. (I made sure it works)
Just don't have anything named bin in the same directory as the launch script.
EXTRA EXTRA INFO:
This tool is meant to be an extension to the command prompt and will pass anything that it doesn't understand over to the command interpreter.
It works in Wine. Extra launching needed. (See last post)
This is a tool for beginners and advanced users however beginners need to learn adb's commands before using this tool.
It will root 2.x and up(Support added for newer android versions). I suggest installing Supersu also.
Tool works on all windows versions: Wndows XP and above.
You are no longer encouraged to use the XP only zips for Windows XP.
For XP: If you use the tool on the local drive it throws errors however if you use it on a usb drive then it works fine
If you need to use it on a local drive then you can use the old win xp only version.
Windows 8 and 8.1 run the tool perfect.
Use the exit command to exit the tool.(It auto kills the adb server)
Links to third party tools used or included:
Recommended download: ApkMultiTool. Another recommended download: Mediatek flashtool
Framaroot
Exynosabuse
strace
Android Sdk
Stahlworks Binaries : Open source
Win32 Busybox Binary(pclouds) REPLACED WITH Tigress busybox
Freac Not in Slim builds.
Stericson Busybox Android Binary
Sqlite3 android
Supersu
Hstart for use with startup sound

This info applies to testing, finals, and anything else.
FUTURE CHANGES:
Code:
add start settings app and browser app command using am start
add intent disabler (Disable an app's MAIN so that it can be hidden from drawer and be unstartable "locked" )
add the ability to make img of a specified size and store it in /data and even loop mount it to sdcard
add the ability to live image the system and data partitions.
remember to make the user specify the filesystem for sdcard image
I need to backport all bug fixes and improvements to 1.9.5_XP-ONLY
use vbscripts to automate key sends (control-c) Not done due to batch sucking.
add su -c sh to start up root shell on device for use with things like strace. Not done due to batch sucking.
add if blank adb devices say you must connect with either cnt or plugging your device in. (But still show the output)
add variable for work folder
Migrate all custom data text files(hist,clr) to config folder in Work\ but keep defaults in regular bin folder.
add adbkiller script to the desktop by question on first startup.(Store info text file in userbin) (User variable then desktop)
clean output on adbp and adbps plus
change all du -smc to du -sm for single push/pull
add ability to do several pushes and pulls with du -smc in one operation
add parameters to adbp and adbps
add if not defined to destination and source file in adb and adbps to allow for hitting enter to quit in the middle of setting up a push or pull
cleanup and organize xt
include some sort of nano for windows binary for command line editing
include a compact notepad++
Remove extra binaries such as zip and unzip to point to busybox linkers (Skim through code to change "zip" to "busybox zip" or "sfk zip")
Pass all inputted commands to a script that can parse arguments before they are sent to they're respesctive scripts or binaries. (Mostly to catch /? and run it without call)
Remember to update adbClient Launcher to point to new folder.
Add first time greeting, explaining commonplace commands and the various folders using java.
add batch snake from [URL="http://www.dostips.com/forum/viewtopic.php?t=4741&mobile=on"]here[/URL] [URL="http://www.dostips.com/forum/viewtopic.php?t=4741&mobile=on"]and here[/URL] for fun
learn some design tips from batch snake.
add adb closer background script for when someone closes adbclient with the windows close button.
add ability to root adbps and adbp or just enable insecure adb debugging
setpass not using admin privileges, add call capability to use instadb privilege elevation code as an elevation module for the rest of my code)
search for commands

CHANGELOG:
This changlog is deprecated for the commits page on my github: https://github.com/lgrootnoob/adbClient_EnvironmentandTool/commits/master
Code:
With 1.3.1 adb/fastboot has been updated from platform-tools to rev. 19(Previously rev. 18.0.1)
Split 1.3.1 into xp only and vista up packages
Add a work command that will send you back to the work folder no matter where you are.
See third post.
Removed a couple of the zips in the post to make the download list easier.
Made license a separate download.
Add unroot function.
Implement extracter with a windows tar exe for extracting images from a tgz.
Make adb/fastboot installer for system. (%WINDIR%\system32) (To install the binaries just type instadb and follow the prompts)
(Installing adb and fastboot to the system makes adb or fastboot dependent applications operate without the need to setup complicated environment variables.)
(Before you would have had to make the environment variable point to the folder conanaining the binaries then you would have to check to make sure its setup properly. this will eliminate that issue)
Add the launch script into the package and update instructions. (JUST added launcher to make starting it easier.)
Issues with my implementations of certain processes inside the script.
Fixed updater typo.
Added sfk binary from stahlworks.(VERY useful tool [URL="http://stahlworks.com/products.html"]http://stahlworks.com/products.html[/URL])
Added zip and unzip binary from stahlworks
Added latest usb driver from google.
Add the launch script into the package and update instructions.
add win32 busybox and remove gnuwin32 tar command.
Apk install from file. And apk uninstall and apk installed lister. pm argument sender. apk command for menu
Version change in updater code. but server on mandatory downtime for a week.
Fixed problem with missing dlls in system32 install for adb and fastboot
^Fixed bugfix in 1.8 Whackamole:)
use nul to detect dirs
everything that is passed to cmd is called.(In 1.8.2+)
Added ls links to busybox and can use params like ls -l
Made links to busybox with batch files and parameters.
Added md5sum binary.
Make attempt at auto pushd popd implementation. To use this feature just cd to wherever then type back to go back.
New XP local drive version. (Remember that XP can run any version from a removable drive or drive that isnt the partition with the running OS on it.)
FIXED - Output cleanup and implementation of code rendering inner shortcuts unuseful)
add extra bin for user binaries in Work\userbin
added addpath command to append the current folder to the temporary path
Fix another bugfix.
testing version released so the version number on my server will not be updated until I have personally evaluated these builds for a couple of days.
implement pushd popd into my code
add windows tools from knife into adbclient.
made repo command.
added bin2hex binary
added deveject binary
move %clrsnd% %clrval% above the doneloop subroutine so busybox's ls command can properly highlight file names.
only use %clrsnd% %clrval% when needed (pretty much the same as I have done with adb devices and fastboot devices)
added zipalign binary
update updating system to live (ON)
add repo style p2p apt-get system called Gridlock(Thought of the name myself) (not p2p yet :( )
moved extended menu out of code and into a file to help clean up stuff.
add bash link for busybox
fixed up repo script address(dynamic)
added mkfloppy
fixed bug in apk installer code.
removed cmdmenusel and trashed the idea of using it for the preffered java dependency setup.
fixed small bug
changed exit for future dynamic handling of shutdown disk operations.
cat command takes over the beginning of the next echo so it has an echo. in its code.
Deprecated every addpath script and moving to modular addpath userspace script.
Also fixed varname bug in addpath script that made it worthless
Commented my info in.
fixed unrooting issue.
piped apklist to more.
Comment code/subroutines etc. and use whitespace to make it easier to read.(Half done, it needs more work)
everything below is for unreleased 2.3 version.
Strace helper
added goo.im opener
added audio converter freac (Freac has source code available freely on their webpage)
Remove just a couple lines from the inital output to make it fit the command prompt screen.
strace installer (chmod 777 adb push and su -c sh) for work with strace.
add data /T to top of script
added frontend for deveject binary because it is too complicated
make cnt a command that will take params so you can type cnt 192.168.1.81
^if no params are given it will ask for ip address
added send command to strace in testing
merged strace bug fixes into testing
fixed another path bug in testing
code now becoming very modular with me using scripted functions as commands in other scripts.
lgctnp always out to work dir now
fixed 'regression' in hist (Accidental reference to deprecated function broke it) (ALSO: fixed in clr)
project no subroutine/if statements: instead of using if statements on the users input on the main loop I will use batch files in my path that have the name of the user's command.
^This eliminates "" crashing.
add hash check for transmitted file. (Needs md5sum binary for android.) (Make it a question)
add busybox installer
add quick fixes menu for things like accidentally deleted launcher, etc.
fixed issue with busybox android binary got deleted.
added: 'mode con:cols=100 lines=50' for big console
fixed up lgctnp and dmsgnp code
add dmesg
quick patch for scroll height (It will be tweaked more in the future.)
[B]3.1.5 will be a temporary bug fix and binary addition in preparation for.......[/B]
make cd freac* point to full path instead
add startup Splash screen for christmas holiday
added Framaroot to rooter
added exynosabuse to rooter
adbsl is accidentally pointing to old doneloop subroutine and needs to be pointed to EOF
move from old pclouds busybox binary to [URL="http://intgat.tigress.co.uk/rmy/busybox/index.html"]tigress win32 busybox[/URL]
update android sdk dependent stuff (platform tools have been updated to 19.0.1)
update su and supersu
change call adbclient to call start adbclient so the intital launcher is exitable
java detector added
[B]3.2 Released![/B]
fix old subroutine pointers in devej
add startup sound
[B]3.2.1 Released![/B]
added screenshots to OP
patch instadb with set "installmaybe="
add size check for pulling/pulled or pushing/pushed files on adbp and adbps like the md5sum checker.'
update busybox/adb/fastboot/freac/anything else/check and update apk versions.
add question to adbp and adbps for redoing the push/pull operation if the user notices the hashes don't match
[B]3.2.4 Slim Released![/B]
change release naming scheme from final to only use final name for final release in 3.2.x, 3.3.x etc.
fix adbp to do you to "Redo pull operation?" instead of "Redo push operation?"
cleanup root.bat output organizing exploits by android version.
change subroutine pointer in ex from doneloop to :EOF
[B]3.2.5 Slim_ Maintenance Released![/B]
Google's usb driver updated to revision 9.
link every busybox applet
store busybox whoami value in variable and then put it into $~: set /p command
pointed launcher directly to bin folder name
updated binary and application dependencies
[I]Made some progress in porting a new xp desktop version: the path names need to have quotes around them.[/I]
[B]3.2.6 Slim Released![/B]
[I]INFO: adbClient is somewhat usable in Wine.[/I]
Framaroot and sfk updated.
Tigress busybox updated.
Fixed qfx mounting issue.
android busybox binary updated
updated supersu apk and su, [B]NOTE:[/B] It is ton of work to support 4.3 rooting but I will do it soon in 3.2.8 I will have to bundle cydiaimpactor somehow.
[B]3.2.7 Slim Released![/B]
2.2 removed(cached locally, so it will be unavailable. leaving the remnants of 1.9.5 even though xp is not supported by microsoft anymore)
[B]3.2.8 Released![/B]
GITHUB REPO: [url]https://github.com/lgrootnoob/adbClient_EnvironmentandTool[/url]
updated to usb driver v10
[B]3.2.9 Released![/B]

Bump:
Bump, any dev can use this tool to have their rom users debug the roms that they make easily if they like.

I have done enough testing to know that this works in Wine on Linux pretty good now.
However, special launch instructions are needed.
cd to the adbclient bin folder(Currently bin-3.2.6-Slim) and use the command:
Code:
WINEDEBUG=-all wine cmd /c adbclient.bat
- all on one line.
Adbclient should be started and you can connect to your phone wirelessly with cnt *.*.*.* (Insert ip address to the left).
Happy Linuxing.
EDIT: Bash port coming soon to a Linux computer near you.

Latest use of this tool as a library/environment for making a rooting package for phones.
http://forum.xda-developers.com/showthread.php?t=2738977

The changelog here will now go unmaintained in deprecation for a github repo: https://github.com/lgrootnoob/adbClient_EnvironmentandTool

3.2.9 released.

Lgrootnoob said:
I have done enough testing to know that this works in Wine on Linux pretty good now.
However, special launch instructions are needed.
cd to the adbclient bin folder(Currently bin-3.2.6-Slim) and use the command:
Code:
WINEDEBUG=-all wine cmd /c adbclient.bat
- all on one line.
Adbclient should be started and you can connect to your phone wirelessly with cnt *.*.*.* (Insert ip address to the left).
Happy Linuxing.
EDIT: Bash port coming soon to a Linux computer near you.
Click to expand...
Click to collapse
I don't like bash. :/

pcwizzy37 said:
I don't like bash. :/
Click to expand...
Click to collapse
bash is necessary for using some build systems to compile android source code. If the OP wishes to donate his time and efforts , I'm sure that an easy installer will be useful to someone. I believe that this tool deserves more response than it has received.
Sent from my LGL15G using Tapatalk

ibub said:
bash is necessary for using some build systems to compile android source code. If the OP wishes to donate his time and efforts , I'm sure that an easy installer will be useful to someone. I believe that this tool deserves more response than it has received.
Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse
I have no idea why I said that back then. I have been dailying Linux for years now and BASH is what I primarily use, also it's wierd because at that time was when I was migrating to Linux.

[SCRIPT] PhoenixOS Installer for Debian based Linux

Hello I've Created installer script for PhoenixOS with help of grub installer script taken from remixos deb package file.
I am not responsible for anything that may happen to your PC/Laptop/Tab as a result of installing and using this script. you do so at your own risk and take the responsibility upon yourself.
Click to expand...
Click to collapse
Note: Backup your custom.cfg file if you are dual booting with other os if not then proceed further.
custom.cfg should be in /boot/grub/custom.cfg if EFI install then /boot/efi/EFI/yourdistroname/custom.cfg
p7zip-full should be installed its need for extracting ISO file.
Script should be placed where desired files or ISO is present.
--> This is tested and working fine in kde neon lts on MBR and GPT disks & EFI is not tested as I don't have that installation so it should work.
--> Other then Debian based distros IDK if my script works on them or not, so please test it yourself and inform.
--> If your home folder is defined on other disk or partition please add insmod part_gpt insmod ext2 OR insmod part_msdos insmod ext2 according to disk partition table to grub entry in custom.cfg
Click to expand...
Click to collapse
Features
Path defined root and home only.
Method defined FILES and ISO & EXE only.
Has Uninstall options.
Data folder is created in os folder
Click to expand...
Click to collapse
Make script executable
Code:
chmod +x PhoenixOS-Installer-Linux
Then Run
Code:
./PhoenixOS-Installer-Linux

reserved

reserved post

Not enough information. Please elaborate on the installation procedure itself. On Ubuntu of course it should install to sda2. I chose the path /dev/sda2/ then used .iso for the install method, and then upon trying to do the install using option 2 it simply keeps bringing me back to the menu where choices 1-4 are present.
I actually got PhoenixOS to install using the USB method, however I cannot find a working boot sequence for GRUB bootloader. I'm kind of at a loss for finding a way to easily switch between Ubuntu and PhoenixOS.

Deucalion29710 said:
Not enough information. Please elaborate on the installation procedure itself. On Ubuntu of course it should install sda2. I chose the path /dev/sda2/ then used .iso for the install method, and then upon trying to do the install using option 2 it simply keeps bringing me back to the menu where choices 1-4 are present.
I actually got PhoenixOS to install using the USB method, however, I cannot find a working boot sequence for GRUB bootloader. I'm kind of at a loss for finding a way to easily switch between Ubuntu and PhoenixOS.[/QUOTES]
I got this done by making different partitions. Sounds like a no-brainer, but it works. My main OS is MacOSX, then I made different partitions of FAT32s using Disk Utility, I created them all in different sizes (to prevent confusion). After that, I just install the other OS one by one (Phoenix will always be the last). And, I made some extra partitions during Linux installation (just in case) and deleted them after.
As for the Phoenix post, Thank you
Click to expand...
Click to collapse

It does not work...
I have placed the script and the iso file in the same home directory, chdir in that place but the script does nothing ... It asks for sudo and the it does not create any directorys.
To complicated to debug for me....
EDIT:
I have managed to install it in home / iso mode
I had to edit the generated schipt for modifying GRUB. It was copiing the whole script and not stopping at EOF ?!

It works great
Setup;
1 - Download Phonix OS ISO image on Phonix OS web site
2 - Create a folder with any name
3 - Copy the Iso file to this folder and extract the PhoenixOS-Installer-Linux.zip file to this folder
4 - Open the terminal and go to the folder you created
5 - Now run "chmod +x PhoenixOS-Installer-Linux" and "./PhoenixOS-Installer-Linux" command
6 - The script will run
7 - Select "Select Path & Method"
8 - Type "home" for path and press enter
9 - Type "iso" for method and press enter
10 - Select "Install Rom" and follow the steps
11 - Run the "sudo update-grub" command using the terminal when the process is finished
12 - Restart the computer and select Phoenix Os
I'm sorry for my bad english

bycoder said:
Setup;
1 - Download Phonix OS ISO image on Phonix OS web site
2 - Create a folder with any name
3 - Copy the Iso file to this folder and extract the PhoenixOS-Installer-Linux.zip file to this folder
4 - Open the terminal and go to the folder you created
5 - Now run "chmod +x PhoenixOS-Installer-Linux" and "./PhoenixOS-Installer-Linux" command
6 - The script will run
7 - Select "Select Path & Method"
8 - Type "home" for path and press enter
9 - Type "iso" for method and press enter
10 - Select "Install Rom" and follow the steps
11 - Run the "sudo update-grub" command using the terminal when the process is finished
12 - Restart the computer and select Phoenix Os
I'm sorry for my bad english
Click to expand...
Click to collapse
it works but when i try to boot it stucks at command shell. any idea ?