Script is standalone : you can download latest version without upgrading from previous version
v1.6 > Big update on 3G+ tweak addon, more powerful and much faster
Build.prop Worktool - A powerful but safe build.prop manager/editor
Hi !
Okay guys, since I know how powerful the build.prop can be, I love to play with it.
But I was bored to edit using Root Explorer, or using ADB command-line...
So... Let me present you my outrageously complicated (internally) script to manage your build.prop right from your computer, with ease, fun and safety !
GENERAL :
For any Windows NT kernel (Developped under Windows 7 x64... so should work everywhere )
Portable and ready to use - No installation required, all files included (ADB with drivers also)
Lightweight (<3Mb unzipped, because of ADB very big lol)
Tested on XPERA x10i but should work on ANY Android powered device (if your ROM uses a build.prop located into /system/)
KEY FEATURES :
Easy open/edit your build.prop in your default text editor
Backup creation/management
Save backup on your computer and/or on your device
Safe (Automatic backup generator - Manages up to 2 backup files, exhaustive log file)
Automatic permissions management
Add-on capability : possible to add automated installation scripts to tweak your build.prop
List of present add-ons : 3G+ enhancement tweak
Very clean : deletes all temporary files, auto start/stop ADB server and kills the process when useless
Convenient : direct access to this thread, easy to use
v1.6+ : (beta) Build.prop XPlorer, to check with ease your build.prop
I based the main script on my 3G+ enhancement script, available on the official thread.
** As usual... Use at your own risk **
Test, comment, criticize, if you find anything, just drop a comment or PM
FAQ
FAQ- Supported devices
It is first developped for Sony Ericsson XPERIA x10, but it should work on any Android device with these requirements :
* Rooted
* File system is mounted Read/Write.
* Build.prop is located into /system/ and named "build.prop"
Sony Ericsson XPERIA x10 : fully working
Samsung Galaxy S2 : half working (file system is read-only...)
- How it's working ?
The script works generally in this way :
It downloads from your device your build.prop and creates two temporary backups.
Then, it opens one of the temporary backup into notepad, to let you edit all you want.
Once file closed/saved, the file is reconfigured automatically, then sent back to your device.
The script allows you next to keep, on wish, the remaining backup and to reboot your device.
- Is this safe ?
The script makes a backup of your build.prop every time you try to access it. There's also human-friendly log file to help you identify problems with ease.
There is also NO automatic upload to your device : the script will always ask you before if you want to upload the new build.prop to your device. Even if you upload it, backup is stored and can even be stored safely on your device for future use.
- Is this all automatic ?
Yes. The script makes backups by itself, reboot your device for you (if you wish), and of course change permissions. But don't worry : it will ask your approval for any important process
- The 3G tweak makes my connection unstable !
The Manager is based on my 3G+ enhancement script, using "Full Mode". In the original script, there is also a "Lite Mode" for some networks (like AT&T) I included in v1.3.
To make your network stable, the script will disable the two lines below :
ro.ril.enable.dtm=1 (will be turned to 0)
ro.ril.enable.a53=1 (will be turned to 0)
To get full details about the 3G+ tweak, check the thread :
http://forum.xda-developers.com/showthread.php?t=951765
Why is there "so many" different batch files ?
It's easier for me to improve/maintain the batch by splitting it into different functions. There's a main script, and subroutines called when needed.
Of course, all the subroutines, including addons, are programmed to be run only from main script. You can run any subroutine separately, but it will mostly crash and create useless files not being deleted. Always run the main script, and do no try to run separately subroutine - not dangerous, but 100% useless/buggy.
- It's not working.
* Make sure your device is :
** ROOTED,
** Full external access to system (su command) [if not, will drop errors like "Operations not permitted" or "file system is mounted read only")
** USB Debugging is enabled,
** Connected using USB and all USB drivers are installed/working.
* You might need administrative privileges in Windows to fully run the program.
* If you're running your device from recovery, you may need to mount /system/ folder before running the script (Partition tools > Mount /system).
- It's still not working.
* Drop a message in the official thread.
* If you get errors about file system Read only, try to run your device in Recovery mode, and fix permissions.
- Will the script create lots of files/make a big drive footprint ?
I hate programs creating lots of temp files. So, the script was developped to create files AND to clean/remove them all once everything is done. Even if it crashes without removing files, you just need to restart the script - it will clean all previous temporary files.
If ADB is run, it WILL be fully closed once everything is done. Server will be killed, then ADB process (named adb.exe) will be killed. Your system will be as clean as it was before running the script.
The script is of course fully portable : there's no installation needed. You can put the script where you want, but you just need to keep all script files/folders in the same folder.
In a future release, I'll add something to purge the log file.
- Which OS is supported ?
It's developped in Windows 7 x64. You should be able to fully run it on any 2000+ Windows NT OS.
As it is NT script, it will work only on Windows computer. It will also not work properly on pure DOS (it's using NT commands and Windows-related commands not included in older Windows NT systems, like NT4).
Report if you tested it on other Microsoft OS (NT 4, Windows 95, 98 or 2000, Dos 6.22...)
- I wanna contribute.
Just right click the .cmd/bat files, edit them with Notepad or anything you want
You can also send me a message (thread or PM) if you notice some piece of code I can improve with other commands (I don't know DOS commands enough )
v1.0 (11/5/2011) = initial release
v1.1 (13/5/2011) = removed BFC tags, updated error 2 (ADB get-state, to help you identify problem), removed 3G tweak returns error 3 if not present (addon = not necessary), added template.bat to create add-ons, improved launcher.bat (add-on primitive detection), added add-on installation detector (displays backup/reboot options only when add-on was installed), corrected folder "\" bug
v1.2 (13 may formely 14/5/2011) = added automated deleter/file checker for 3G+ tweak. Still early stage but looks to work. Automated batch thanks to http://www.dostips.com
v1.3 (16/5/2011) = added 3G+ enhancement lite mode (for networks like AT&T) and removed 1 step on auto deletion, fixed bug of false error when trying to download from device a build.prop.bak not existing, added management options to Backup (send local backup to device, delete backup on device), solved backup internal error
v1.4 (29/5/2011) = fixed window console size, enhanced menus, faster script closing, log file generator, several bugs fixed, enhanced help (readme in Notepad, direct open XDA thread in Firefox), added adb.exe process killer
v1.5 (6/6/2011) = added console title, fixed some menu bugs, updated Readme, weblinks now open in the default user browser, build.prop will now open in default notepad editor, improved interface, fixed unexpected exit bug, added contact me using default email (still experimental)
v1.6 (15/6/2011) = improved ADB process killing, deeply improved 3G tweak script with sed and no more TXT file, readme opens in your default editor, improved interface, updated template, unified common subroutines into BAKengine.bat, user-friendly explorer of build.prop (not great for now), deleted Substengine (deprecated), "0" in menues now refers to Go Back/Exit, improved missing engines detection, added general temp/log file purger/deleter ** To celebrate The Legend of Zelda series 25th Anniversary, my script is now tagged "Powered by Hyrule DOS"
DETAILLED 3G Addon update :
- detects presence of previous installation and files
- Sed command : fastest detection and subtitute of lines
- Optimized for fastest operation and fully clean build.prop file
- Several stuff...
External SED support thanks to GNU Utilities for win32 @ http://unxutils.sourceforge.net/
v1.7 (26/7/2011) = fixed no deletion of TEMP folder/files, fixed ADB command not found, new entries for XPlorer
Known bugs :
* (Main) Will not detect if build.prop.bak and build.prop.old are the same (not very important, I'll improve this later)
* Report anything you find
Developper/Advanced user addendum
(Write in progress)
Backup management
The script creates up to two backups, localed in main directory :
- build.prop.bak
- build.prop.old
Build.prop.old is generated if the script detects there's an existing build.prop.bak, to avoid accidental loss of it.
Build.prop.old is the final backup, and WILL BE DELETED if detected. The script manages backups like this :
1. If an existing build.prop.bak is present...
>> Script will detect for build.prop.old presence - if it exists, it will be deleted,
>> the build.prop.bak will be renamed to build.prop.old.
2. If there is no build.prop.bak detected...
>> Script will generate a build.prop.bak.
ADB Error detection
Error 2 (device not connected) works using a trick - it's not really related to device state.
In fact, the script will attempt to connect your device to download your build.prop. Once it is done - or not - the script checks if a local build.prop file was created. If it's not present, it means ADB encountered an error - about 90% because device is not connected - and will display error 2.
Keep in mind then there is small chance that your error does NOT come of device not connected : administrative privileges missing (don't allow the script to create the file), drivers buggy, ...)
Hi,
I cant use your WorkTool V1.6
It says ADB cmd not found.
v1.7 out, sorry for delay, I prepared it few days ago then I forgot to upload ^^
Really good work
Perceval from Hyrule said:
FAQ- Supported devices
It is first developped for Sony Ericsson XPERIA x10, but it should work on any Android device with these requirements :
* Rooted
* File system is mounted Read/Write.
* Build.prop is located into /system/ and named "build.prop"
Sony Ericsson XPERIA x10 : fully working
Samsung Galaxy S2 : half working (file system is read-only...)
- How it's working ?
The script works generally in this way :
It downloads from your device your build.prop and creates two temporary backups.
Then, it opens one of the temporary backup into notepad, to let you edit all you want.
Once file closed/saved, the file is reconfigured automatically, then sent back to your device.
The script allows you next to keep, on wish, the remaining backup and to reboot your device.
- Is this safe ?
The script makes a backup of your build.prop every time you try to access it. There's also human-friendly log file to help you identify problems with ease.
There is also NO automatic upload to your device : the script will always ask you before if you want to upload the new build.prop to your device. Even if you upload it, backup is stored and can even be stored safely on your device for future use.
- Is this all automatic ?
Yes. The script makes backups by itself, reboot your device for you (if you wish), and of course change permissions. But don't worry : it will ask your approval for any important process
- The 3G tweak makes my connection unstable !
The Manager is based on my 3G+ enhancement script, using "Full Mode". In the original script, there is also a "Lite Mode" for some networks (like AT&T) I included in v1.3.
To make your network stable, the script will disable the two lines below :
ro.ril.enable.dtm=1 (will be turned to 0)
ro.ril.enable.a53=1 (will be turned to 0)
To get full details about the 3G+ tweak, check the thread :
http://forum.xda-developers.com/showthread.php?t=951765
Why is there "so many" different batch files ?
It's easier for me to improve/maintain the batch by splitting it into different functions. There's a main script, and subroutines called when needed.
Of course, all the subroutines, including addons, are programmed to be run only from main script. You can run any subroutine separately, but it will mostly crash and create useless files not being deleted. Always run the main script, and do no try to run separately subroutine - not dangerous, but 100% useless/buggy.
- It's not working.
* Make sure your device is :
** ROOTED,
** Full external access to system (su command) [if not, will drop errors like "Operations not permitted" or "file system is mounted read only")
** USB Debugging is enabled,
** Connected using USB and all USB drivers are installed/working.
* You might need administrative privileges in Windows to fully run the program.
* If you're running your device from recovery, you may need to mount /system/ folder before running the script (Partition tools > Mount /system).
- It's still not working.
* Drop a message in the official thread.
* If you get errors about file system Read only, try to run your device in Recovery mode, and fix permissions.
- Will the script create lots of files/make a big drive footprint ?
I hate programs creating lots of temp files. So, the script was developped to create files AND to clean/remove them all once everything is done. Even if it crashes without removing files, you just need to restart the script - it will clean all previous temporary files.
If ADB is run, it WILL be fully closed once everything is done. Server will be killed, then ADB process (named adb.exe) will be killed. Your system will be as clean as it was before running the script.
The script is of course fully portable : there's no installation needed. You can put the script where you want, but you just need to keep all script files/folders in the same folder.
In a future release, I'll add something to purge the log file.
- Which OS is supported ?
It's developped in Windows 7 x64. You should be able to fully run it on any 2000+ Windows NT OS.
As it is NT script, it will work only on Windows computer. It will also not work properly on pure DOS (it's using NT commands and Windows-related commands not included in older Windows NT systems, like NT4).
Report if you tested it on other Microsoft OS (NT 4, Windows 95, 98 or 2000, Dos 6.22...)
- I wanna contribute.
Just right click the .cmd/bat files, edit them with Notepad or anything you want
You can also send me a message (thread or PM) if you notice some piece of code I can improve with other commands (I don't know DOS commands enough )
v1.0 (11/5/2011) = initial release
v1.1 (13/5/2011) = removed BFC tags, updated error 2 (ADB get-state, to help you identify problem), removed 3G tweak returns error 3 if not present (addon = not necessary), added template.bat to create add-ons, improved launcher.bat (add-on primitive detection), added add-on installation detector (displays backup/reboot options only when add-on was installed), corrected folder "\" bug
v1.2 (13 may formely 14/5/2011) = added automated deleter/file checker for 3G+ tweak. Still early stage but looks to work. Automated batch thanks to http://www.dostips.com
v1.3 (16/5/2011) = added 3G+ enhancement lite mode (for networks like AT&T) and removed 1 step on auto deletion, fixed bug of false error when trying to download from device a build.prop.bak not existing, added management options to Backup (send local backup to device, delete backup on device), solved backup internal error
v1.4 (29/5/2011) = fixed window console size, enhanced menus, faster script closing, log file generator, several bugs fixed, enhanced help (readme in Notepad, direct open XDA thread in Firefox), added adb.exe process killer
v1.5 (6/6/2011) = added console title, fixed some menu bugs, updated Readme, weblinks now open in the default user browser, build.prop will now open in default notepad editor, improved interface, fixed unexpected exit bug, added contact me using default email (still experimental)
v1.6 (15/6/2011) = improved ADB process killing, deeply improved 3G tweak script with sed and no more TXT file, readme opens in your default editor, improved interface, updated template, unified common subroutines into BAKengine.bat, user-friendly explorer of build.prop (not great for now), deleted Substengine (deprecated), "0" in menues now refers to Go Back/Exit, improved missing engines detection, added general temp/log file purger/deleter ** To celebrate The Legend of Zelda series 25th Anniversary, my script is now tagged "Powered by Hyrule DOS"
DETAILLED 3G Addon update :
- detects presence of previous installation and files
- Sed command : fastest detection and subtitute of lines
- Optimized for fastest operation and fully clean build.prop file
- Several stuff...
External SED support thanks to GNU Utilities for win32 @ http://unxutils.sourceforge.net/
v1.7 (26/7/2011) = fixed no deletion of TEMP folder/files, fixed ADB command not found, new entries for XPlorer
Known bugs :
* (Main) Will not detect if build.prop.bak and build.prop.old are the same (not very important, I'll improve this later)
* Report anything you find
Click to expand...
Click to collapse
Hey mate...
lovely piece of work..!
saved me hours at my work...
thanks a lot works flawlessly on
sony xperia tipo dual with cm 10
Ur da bomb
As you probably already know, you are DA BOMB, BABY!
I just [snicker] used your tool to save my rather idiotic...er, 'brain' from suffering through a dumb, hard night re-flashing SlimKat 4.4.2 back onto my LG Optimus G e970 just to fix something I should've never done to begin with (change screen density to make it easier to read, of course, but without really knowing what I was doing)...
aherm...well, anyway, here I sit at a pre-midnight hour thanking you profusely, sir, because, as I said at the start...
UR DA BOMB!!!
Here's hoping you get bored a lot more often...it's a keeper, fer sure.:victory:
Good work dude... Nice toolkit, loved it very much... I am integrating your tool into my new upcoming toolkit. Dont worry i am not gonna steal it, will just use it. Will surely give you proper credits for that
Does this work with the stock recovery without root?
My device: Xperia XA2
thanks for this useful helper. i know how to modify build.prop - thats not the reason why i came here. what i don't know is the meaning of all this different entries in build.prop for example ro.expect.recovery_id - which there was a catalog with information about included in a build.prop Tweak GUI
sorry but the program cant detect/ acces build.prop
my device is rooted, has debugging on and is connected via USB
plz help
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.
ADB Master helps you manage and monitor multiple Android devices using ADB (Android debug bridge). One click to switch adb to wireless, perform actions, commands or view and compare installed apps, running processes with cpu usage or browse logcat data for multiple selected devices… At the same time. Without root!
Updated November 2015
Download ADB Master 1.61 for Windows, Mac or Linux.
Quick start
1) Make sure ADB is installed on the PC
- http://developer.android.com/sdk/
OR
- http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
OR
- http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
2) Install and run ADB Master for your operating system.
3) Set the ADB location in the “Control” tab of ADB Master by browsing to the folder containing the “adb” binary. The background will turn green when the correct folder is selected.
Notes:
- For an Android device to appear in the list, enable "Settings > Developer > USB Debugging" on the device and connect it to the computer with a USB cable.
- In ADB Master, select one or more devices from the list of USB or WiFi connected devices to perform actions or view information on them...
Windows Users: You will need to install the Android ADB drivers if your device is not detected.
Automatic updates under Windows: If you get an error updating an older version using the built in update feature, try running the app as an administrator (right click and select "Run as administrator"). You only need to do this to update the app - not every time you run it.
Mac users: If you get an error that the app is corrupt or cannot be opened, try right clicking it and select open to allow it to run (you only need to do this once).
Linux users: The new 1.5 linux version includes a run script and has some special permission set as follows:
(Thanks to Craig D) if you want to run ADB-Master via its icon, the .jar permissions need to be set to 'executable'... This can be done by opening a Linux terminal and typing: chmod +x ADB-Master.jar.
Without setting the permission to +x you can only run it from terminal by typing: java -jar ADB-Master.jar.
If you like the app and want to support it, please purchase the paid version in the Google Play Store (search for 'ADB Master').
Using the ADB Master GUI
Device lists
View attachment 2670819 At the top of the application are the device lists. These lists provide a way to list and select devices to work with.
There are two lists:
1) USB connected devices with a button to switch the selected devices to WiFi (tcpip) mode. This will install “Helper.apk” to display adb state on the device and enable the device to be discovered and connected to by ADB Master.
NOTE: The device(s) and the computer must connected to the same WiFi access point for a successful ADB-Over-WiFi connection.
NOTE: Unfortunately, some android builds do not have the ability to use ADB-Over-WiFi without root.
2) WiFi connected devices which has a button to switch the selected devices to USB mode. This will uninstall “Helper.apk” and set the device back to USB mode.
Control tab
View attachment 2670799 This section allows you to perform actions or commands on all selected devices.
- Shutdown, reboot, reboot to recovery or reboot to bootloader by selecting the devices and then pressing the desired button.
- Press power, back, home or volume up and down buttons on all selected devices at the same time.
- “Identify” a device installs and runs a small utility to wake the device and display the same information that appears in the device list as well as the IP address.
- Execute any custom ADB command in the ADB Command box and hit enter or press “Execute” to run that command on all selected devices. NOTE: This function treats spaces as command separators so it may not work for all possible adb commands at the moment. View the results of the command in the “ADB Log” tab.
Applications tab
View attachment 2670866 This section allows you to compare and manage applications (packages) on all selected devices using the adb commands “adb pm list packages -e”, “adb pm list packages -d” or “adb pm list packages”.
- Install an APK from your pc
- Enable (requires root and su to be installed on the device)
- Disable (requires root and su to be installed on the device)
- Uninstall multiple apps on all selected devices with one click.
- Pull selected apk's
- Pull screenshots
- Start apps
- Force-stop apps (Only works with Android 3 and above)
- Clear app data and cache
App listing color key:
- Green: The app is installed and enabled on all selected devices
- Black: The app is installed and enabled on some selected devices
- Orange: The app is installed on some or all devices, but is disabled on one or more
- Red: The app is installed on some or all devices but is disabled on all installed instances
Processes tab
View attachment 2670801 This section uses the command “adb shell top -m 20” to list the top 20 processes running on the device. It lists all selected devices in one view making it easy to monitor multiple devices at the same time. Future features include the ability to terminate processes and use custom top commands.
Logcat tab
View attachment 2670802 View live Logcat data from all selected devices in one list making it easy to monitor multiple devices at the same time. Future features will enhance this section with the use of filters and colors.
- View and save Logcat messages to files
ADB Log tab
View attachment 2670803 View a log of commands executed by ADB Master. It logs the device, commands and their responses.
V1.1-BETA Changes:
- Fix for incorrect process display in Windows
- Removed the extra blank lines in logs on Windows
- Fix for device name not set correctly in Windows
V1.2-BETA Changes:
- Added tcp reset/disconnect button
V1.32 Changes:
- Added adb sideload feature (useful for ROM developers)
V1.33 Changes:
- Renamed Log tab 'Console'
- Moved ADB custom command fields from Command to Console tab for better context and visibility of command responses
V1.41 Changes:
- Added ability to pull selected apk's
- Added ability to save Logcat messages to files
- Added ability to pull screenshots
- Added ability to start apps
- Added ability too force-stop apps (Only works with Android 3 and above)
- Added ability to clear app data and cache
- Added time stamp to Logcat messages
- Fixed connect command to include the port for some versions of ADB
V1.51 Changes:
- Fixed some delays on the UI when connecting to a device
- Added buttons to open pulled screenshots and apk file locations
- Added installer for Windows users
- Added Mac .app package
- Added Linux version with required permissions set and a run script
V1.60 Changes:
- Added drag and drop to install applications (drag APK's to the application list on the applications tab)
- Added ability to select and execute a file containing ADB commands or drag and drop adb command files onto the console tab
- Added ADB Master automatic updates. Get notified when an update is available then download and install it.
- Added some useful buttons in the control tab that open various control panel items on all selected devices (all buttons may not work on all Android platforms).
V1.61 Changes:
- Improved handling of multiple commands in a single line to allow complex scripts to execute successfully.
- Fix for the way commands are handled in Windows related to line feed characters.
Execute adb commands from a file:
Command file(s) must contain valid ADB commands, one per line and may also contain comments. The starting keyword "adb" is assumed for each line and is optional in the file.
To comment a line, start the line with any of the following (common) comment delimiters: ";" "//" or "rem" as well as ":".
When selecting file(s) using the browse button, you will be prompted with a message containing the commands to be executed before they are executed. Drag and drop command file(s) onto the console tab to execute them without a prompt.
WARNING: ADB Master exposes powerful and advanced tools for working with your Android devices and misusing it can result in the device malfunctioning... REALLY.
Disclaimer: Although great care has gone into creating it, this software is provided AS-IS and you use it completely at your own risk. All rights reserved.
Download ADB Master 1.61 for Windows, Mac or Linux.
The above download links provide the recommended latest versions. Previous versions of ADB Master are also available below.
Note on automatic updates under Windows: If you get an error updating an older version using the built in update feature, try running the app as an administrator (right click and select "Run as administrator"). You only need to do this to update the app - not every time you run it.
XDA:DevDB Information
[APP] [TOOL] [Win | Mac | Linux] ADB Master: A multi-android ADB graphical interface, Tool/Utility for the Android General
Contributors
extremewing
Version Information
Status: Stable
Created 2015-03-07
Last Updated 2015-03-22
Seems Good...! (Y)
I saw a device today that was not completing loading of the apps list and a few other strange things including strange numbers for the processes cpu percentages. I will be looking into this a bit more so you can expect an update soon.
Today, I uploaded a new version that fixes some issues under Windows.
Please see the original post for the download link!
Thanks
Adrian
A new version is in the OP.
It includes a new "Reset" button for tcp connections that have stopped working, particularly useful when waking the PC or changing access points and the old connection is no longer working.
New feature in V1.3: ADB Sideload
I had a request to add ADB "sideload" capabilities to the app (useful for rom developers) and here is the first version to test out that includes this feature. I will update the OP soon if no one has any problems.
V1.31 Increased timeout for sideload
This version has an increased timeout for the adb sideload feature. It is possible the execute thread was not waiting long enough for the upload to complete?
good work, thanks
it's hard to remember the command for me,
V1.32 is now available from the first post
New feature: adb sideload - upload and install updates to a device in one step.
Sideload mode is a special option in the Android's recovery. It was introduced in Jelly Bean (4.1) and higher.
Please see your recovery's instructions on starting sideload mode.
Some small changes in V1.33 on first post.
After some positive feedback, I have published this new 1.33 version on the play store too.
This is a wish list of features to add to ADB Master and I will be working on implementing them.
- Add ability to pull selected apk's from the selected devices
- Add ability to save logcat messages to files
- Add ability to pull screenshots
If you have any other requests, please post here!
Hi, a suggestion: can you make possible to connect to a device with a known ip? I don't want to install those apks...
vipervault said:
Hi, a suggestion: can you make possible to connect to a device with a known ip? I don't want to install those apks...
Click to expand...
Click to collapse
Ok let me figure out what would make sense in how to do that.
Just out of interest, why do you not want to install the apk's (I assume you mean helper.apk)?
vipervault said:
Hi, a suggestion: can you make possible to connect to a device with a known ip? I don't want to install those apks...
Click to expand...
Click to collapse
Just so you know, executing the connect command at a command prompt when you know the IP is quite easy too. The command would be "adb connect <IP>". The good thing with the helper.apk with ADB Master is that it will take care of this for you and even re-connect when a connection is broken for some reason.
Anyway, still waiting to see why you do not want to install the apk's? You could uninstall them straight away from the Applications tab too.
.jar won't open
I double-click on the jar, but nothing happens. Anyone know why this could happen?
Aidoboy said:
I double-click on the jar, but nothing happens. Anyone know why this could happen?
Click to expand...
Click to collapse
You need to have Java installed and then the file type ".jar" should be associated with the java runtime correctly.
Best tool ever!
Vingadero said:
Best tool ever!
Click to expand...
Click to collapse
Thank you! Your feedback makes it worthwhile.
If you have any suggestions or special requests, please feel free to post them.
extremewing said:
This is a wish list of features to add to ADB Master and I will be working on implementing them.
- Add ability to pull selected apk's from the selected devices
- Add ability to save logcat messages to files
- Add ability to pull screenshots
If you have any other requests, please post here!
Click to expand...
Click to collapse
Great tools! Any progres with
- Add ability to pull selected apk's from the selected devices
???
Hi,
This kind of script probably exists, but I share you mine that allows filtering traces easily.
It firstly show a window providing the list of connected devices, and when you click on a device, it opens the logcat trace reader window.
This log trace reader automatically detects all tags (with type). You can filter by:
- new detected types
- selecting/unselecting tags in list of already detected tags
- selecting/unselecting all
- selecting/unselecting tag by partial name or type
- preselecting by setting directly the ADB filter command
Logs have colors according to type. You can start and stop log capturing, and clear log.
To run it, you MUST:
- have adb correctly installed
- have Python 3.x (not working on python 2.x)
License: GPLv3
Update 2015/04/02: busy cursor correction
Nais Script! But i can't run this with python 3.4
Code:
~/scripts/python$ python3 LogReader.py
Traceback (most recent call last):
File "LogReader.py", line 493, in <module>
app=WindowDevices(master=root)
File "LogReader.py", line 140, in __init__
self.config(cursor='wait')
File "/usr/lib/python3.4/tkinter/__init__.py", line 1271, in configure
return self._configure('configure', cnf, kw)
File "/usr/lib/python3.4/tkinter/__init__.py", line 1262, in _configure
self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
_tkinter.TclError: bad cursor spec "wait"
What did i wrong?
€dit: using Ubuntu 14.04
Hi,
Thanks for your feedback.
On version 1.1, I have replaced the 'wait' cursor by 'watch' cursor. So it should work now.