Database Users

Romkitchen on Windows

I got Romkitchen running on W2K/IIS
i did the following:
* Install Cygwin with Base-Tools and Perl
* Install php-4.3.2-Win32
* create virtual directory pointing to Romkitchen files
* make sure, that bin-directories of cygwin and php are in your system path
changes in Romkitchen:
Windows does not support the concept of symbolic links so change it to just copy the files
* processor.php line 480:
@symlink(...);
chage to:
@copy(...);
* Directory "80_How would you like..." must not end with a "?"
* because i have no command line "zip" installed i changed the content
of "outfile" to names without ".zip" at the end
(in RomKitchen\data\80_How would you like your ROM_\20_zipped NK.nb1 (SD-card flashing)\_\cfg)
That's it! (and it works! )
Fidl

Nice. I might try it. Last time i tried to install cygwin, i couldn't get it to work. can u give me little more details on how u isntalled it?
thanks
alex

I did nothing special to install cygwin.
I installed via ftp, selected all of the base installation and made sure that perl (5.8..) is marked for installation.
the only thing i did is that i added c:\cygwin\bin to my system path variable.
when runnin mkrom i didn't do that from cmd.exe but lauched "bash" before that.
try to start ./mkrom.sh from a bash-shell.
sorry, i don't remember if i did anything else important, but if you encounter some problems, let me know.
Fidl

[Tutorial] How to Setup Eclipse 3.5 & Android SDK 2.1

There are many ways to develop for Android and because of all the options it is sometimes a little daunting getting your environment setup. I found myself bouncing from web page to web page, not really sure if I had the right tools and if they were setup correctly. I wanted to document the process that worked for me.
Goal: Step by step instructions to install and configure your Android development environment for Windows.
Environment/tools: Here is the setup I have chosen to use.
* Windows (I'm using Windows 7, but any flavor of windows will do)
* Eclipse IDE for Java Developers (v3.5 Galileo)
* Java Platform (JDK 6 Update 18 )
* Android SDK Tools, Revision 4
Step 1. Install Eclipse IDE
I chose to use the Eclipse IDE for Java Developers (v3.5 Galileo). You can download the it here
* Download "Eclipse IDE for Java Developers (92 MB)"
* This is a zip file and does not require installation. Just copy the eclipse folder into your programs directory
* Download the installation file from Sun
* Select your platform
* Now run the JDK installation. I did not change any of the default installation options. When complete continue to step 3.
Step 3: Install the Android SDK Tools, Revision 4
* Download the install package "android-sdk_r04-windows.zip"
* This does not require installation. Just unzip and copy the files. You can install the package anywhere but remember where you put as you will need to reference it in Eclipse. I happen to install it inside my eclipse folder.
Step 4: Configure Android SDK
* Launch "SDK-Setup.exe" located in the Android SDK install folder"
* If you receive the following "Failed to Fetch Error" we need to change the link to not use SSL. Close the error dialog.
* Press "Cancel" on the "Choose Packages to Install" Dialog
* Select "Settings" in the left pane
* Check "Force h t t p s://.. sources to be fetched using over h t t p://"
* Press "Save and Apply"
* Select "Available Packages" in the left pane
* Select "Documentation" (at the top of the list)
* Select "Usb Driver Package, rev 3 (at the bottom of the list)
* And then select any platform you want to develop. You can select all (be prepared for a long download) or you can select only the platfrom for you phone. The Nexus One uses 2.1 and the Droid for Verizon uses 2.0.1.
* Check "Accept All" and Press "Install Accepted"
* When done press "Close"
* Now we are going to create a virtual device (AVD)
* Select "Virtual Devices" in the left pane
* Select "New..."
* Create the following new Android Virtual Device
o Name: Android2.1
o Target: Android 2.1 API Level 7 (Or which ever API you installed)
o SD card Size: 4000 MiB to 32000MiB (16000 MiB shown)
o Leave the rest at the default settings
* Press "Create AVD". Be patient it may take a few minutes to create your new AVD.
* Close the SDK setup.
Step 5: Configure Eclipse
(These instructions are for Galileo version of Eclipse. Please see this page for instructions if you downloaded the Ganymede version of Eclipse)
* Launch Eclipse for the first time. You will be asked where you want to your workspace folder to be located.
o I used the default location.
o Check "Use this as the default and do not ask again" so you don't have to answer this question every time.
o Press "OK".
* Select "Help > Install New Software..."
* Press "Add..."
* Fill out the Add Site information
o Name: Android
o Location: (URL blocked)
o Press "OK"
If you get an error don't use SSL. change location from "(URL blocked)" to "(URL blocked)"
* After a connection is made and available tools are retrieved expand "Developer Tools" and select "Android DDMS" and "Android Development Tools"
* Press "Next"
* Press "Next" again.
* Check "I accept the terms of the license agreements"
* You may receive a Security Warning about unsigned content. Press "OK"
* Done. Now you should restart Eclipse.
* After rebooting we need to tell Eclipse where we copied the "Android SDK" in step 3.
* Select "Windows > Preferences"
* Select "Android" from the left pane.
* For the SDK Location, browse to where you installed the SDK.
* Press "OK"
* A dialog box will appear. If you want to send usage data to Google leave it checked, other uncheck it and press "Continue".
* Close Eclipse
You are now ready to build your first application.
I have this entire tutorial (with screen captures) and others on my blog AndroidCodeMonkey.

What do you mean by this?
" Just copy the eclipse folder into your programs directory
* Download the installation file from Sun
* Select your platform
I am a "noob" but I want to learn and do things right the first time so I can put time into quality work and not time into trying to figure out how to work the system, etc... Can you be a tad more specific please? Thank you

cgingermany said:
" Just copy the eclipse folder into your programs directory
Click to expand...
Click to collapse
By this I mean you open the zip file and copy the contents of the zip file into your programs directory. If you visit my blog you will see some screen captures that might help you.
cgingermany said:
* Download the installation file from Sun
Click to expand...
Click to collapse
Follow the link to Sun's website and download JAVA JDK.
cgingermany said:
* Select your platform
Click to expand...
Click to collapse
Select *Windows* if you using Windows.

[Guide] YALG2: Yet Another Linux GNU Guide

Hi All,
I'm a long time GNU Linux user and I really dis-like rebooting to windows to play with my GalaxyNote.
The xda forum has all the info needed to play with the GNote using only Linux, BUT the information is scattered around and often buried in some very-deep replies within each thread.
I thought I might summarize my findings in this thread AND in the wiki page [http://forum.xda-developers.com/wiki/Samsung_Galaxy_Note/GT-N7000/Linux] .
I'd like to have any discussion in the thread, while relevant content "summarized and digested" in the wiki page.
So let's begin:
1) a Linux system (I personally use Fedora 16 64bit, but do as you please)
2) I only use/describe command line tool
3) It might work under Mac OS X, but I don't own one
4) You must either be '''root''' or have '''sudo''' properly configured
( for clarity I'll assume you are using a terminal windows with a '''root''' shell)
The tool:
* Heimdall (the Odin ''alter-ego'', fully opensource and multi-platform)
** you can download it from http://www.glassechidna.com.au/products/heimdall/
** Heimdall uses Download mode (VolDown+Home+Power)
*** CAVEAT: it will increase the ''reset-counter'' i.e. the taint-firmware counter by samsung.
*** CAVEAT: YOU WILL LOOSE YOU WARRANTY BY SAMSUNG
*** Luckily: You can reset counter using several methods (see relevant threads in Development Sub-Forum)
* Android ''adb''
** download latest android sdk (currently android-sdk_r16-linux.tgz)
** extract it
** launch tools/android
*** click enough to install platform-tools
** at this point if everything went ok, you should find a ''platform-tools/adb'' binary
*** the binary is ELF 32 but it works ok provided you have the proper 32bit libs available in your system
=== Guide 1: Extracting PIT from my GNote using Linux AND command line tools ===
* Put phone in Download mode (VolDown+Home+Power)
** CAVEAT: it might increase the ''reset-counter'' i.e. the taint-firmware counter by samsung
* as '''root''' in a terminal-window:
#> heimdall download-pit --output MyNotePit
* In my case it is perfectly identical to the one you find in the Development Forum except for trailing '\0' to pad it to exactly 4Kb
=== Guide 2: Rooting my GNote using Linux AND command line tools ===
* Since I updated my GNote using OTA the initial firmware version for my GNote is ''LA6'' version (check yours ... and use proper files)
* Put phone in Download mode (VolDown+Home+Power)
** CAVEAT: it will increase the "reset-counter" i.e. the taint-firmware counter by samsung (see above)
* Flash ChainFire Kernel for proper firmware version (in my case: ''LA6'')
** Download CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.rar (see relevant post by ChainFire in Development Sub-forum)
** Extract it somewhere and "cd" there
** you will find a file in zImage/zImage
** as '''root''' in a terminal-window:
#> heimdall flash --kernel zImage/zImage
=== Guide 3: Rooting using NON-tainting method ===
I haven't tested it, but see this post: http://forum.xda-developers.com/showpost.php?p=19596038&postcount=154
=== Guide 4: How to remove yellow triangle on any firmware with JIG View Single Post ===
From this post http://forum.xda-developers.com/showpost.php?p=22751275&postcount=120
I tested it, it worked for me.
In a nut-shell:
- extract file Sbl.bin from 1.tar AND from 2.tar in two different directory
- wherever you should use Odin, substitute with 'heimdall flash --secondary-boot Sbl.bin'
Changelog:
- 06 Mar 2012 First Post
- 07 Mar 2012 Added 'Guide 4'
- 09 Mar 2012 Added link to wiki page [http://forum.xda-developers.com/wiki/Samsung_Galaxy_Note/GT-N7000/Linux]

Reserved for the future
Reserved for the future

Yes please took me ages to find the rooting method for Linux.

I do appreciate your effort including us linux users with G notes. I've always used linux and heimdall with my samsung captivate, can't be happier.
As a suggestion, why not include heimdall front-end GUI in this guide. I don't mind helping putting up pictures and writing short tutorials.
Sent from my GT-N7000 using xda premium

[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.