Related
I know many of us are new to the whole rooting thing. I'm coming from the Windows Mobile world of custom ROMs, kitchens, etc., but I do have some linux experience. However, I can't for the life of me figure out how to do a lot of what comes "standard" in MoDaCo's ROM. Obviously it would be easier to simply install Paul's ROM and be done with it, but I'd really like to learn how to do it on my own too.
So, that being said, maybe we can pull together some tutorials, guides, and/or links to existing guides which explain how to go about setting up our Rooted phones manually. Here are some of the built-in mods the MoDaCo ROM comes with which would be nice to be able to do manually or on a one-off basis:
Included in MoDaCo 1.1 'core':
Rooted with 'adb remount' permission and superuser APK
A2SD included (fully automatic thanks cyanogen!) create a EXT2 partition as your second partition to use. dalvik-cache remains on device.
Added Jbed Java
Added Dropbear SSH running by default, check 'About' screen for password (port 2222). You can now remove this by running /system/bin/removedropbear.sh
Added Notes app from Dragon
Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
Added android-wifi-tether 1.60 pre3 (props to the developer, this is a great app!)
Added WiFi Status indicator, with kind permission of Andrew Schwimmer
Added busybox 1.15.2 tweaked such that 'get information' in Swapper now works as desired
Added nano 2.09 text editor for use in shell mode
Added parted and sqlite tools
Added terminfo and settings to boot.img to allow nano etc. use
Added files required for Debian linux including loxley's updated bootdeb script
Moved Quickoffice to data partition to allow easy uninstall
Moved Google Maps and Google Voice Search to data partition to allow easy update
Silenced boot sound (it's still there and can be reactivated with a file edit)
Click to expand...
Click to collapse
*********
*********
!Working!
Wireless Tethering:
http://android-wifi-tether.googlecode.com/
Go to the "Downloads" tab and download version 1.61-pre
!Not Working!
Superuser Whitelist App
I found two threads here that describe how to install Superuser.apk.
http://forum.xda-developers.com/showthread.php?t=582140
http://forum.xda-developers.com/showpost.php?p=4897587&postcount=5
Using the first one, I was able to get the files onto the phone and I used the chmod commands found in the second file in the hopes this would work; however, whenever I try to use it, nothing happens. The ES File Explorer, in particular, used to work with MoDaCo. When I'd try to browse as root, Superuser would pop-up and ask if I wanted to grant the app permissions. Now it just hangs there (black screen) and ES File Explorer says I don't have root access. Other Root apps work fine though, it's just they don't seem to be dependant on Superuser Whitelist.
'adb remount' permission
This requires that the default.prop file be edited from ro.secure=1 to ro.secure=0. Unfortunately, I can't seem to get this file to stick. If I use the mv command using adb shell, I get some kind of permissions error. If I use the cp command when booting into the recovery menu and using adb shell, the file reverts to the original on boot. Or maybe it's simply not being overwritten, but not throwing any errors either
I think I may have found a thread that will help with the default.prop changes. Looks like this has to be done in the recovery.img which apparently overwrites any modifications in the root of the device on each reboot. I'll post an update if/when I figure it out.
HOWTO: Unpack, Edit, and Repack Boot Images
http://forum.xda-developers.com/showthread.php?t=443994
The adb remount permission issue is driving me crazy. Please keep us updated if you figure out a way of resetting that without installing a new ROM.
I ended up modifying one of the MoDaCo update scripts to set up ADB Remount, Superuser.apk, and Busybox. It's been working fine for me, but be sure to do a backup before you apply the update. Check it out here:
http://forum.xda-developers.com/showthread.php?t=593952
If this is the wrong thread I'm sorry and mods please move it.
My nook is currently rooted...
I have tried all the 3rd party e-readers different launchers.
I'm really over the idea of being rooted with the exception of "Current book cover screensaver + custom shutdown image" hack and possibly resizing my partitions.
Is it possible to replace the Uramdisk with one that had adb enabled and then just manually push over the modded files?
or am i going to need to install busybox, su, and superuser.apk?
I would like to keep it as close to original firmware as possible...
Can anyone shed some light on this?
Ok so i'm guessing busybox is required to be able to run the Current Book Cover Screensaver.
1st i turned on adb wireless.. installed the files per the instructions over ADB
rebooted and I was stuck in a boot loop
2nd restored to a fresh firmware.
Installed adb wireless, superuser, su, and busybox.
Then installed the files per the instructions over ADB
rebooted and everything works great.
Now i just wonder if i can uninstall Superuser or busybox...
persichini said:
Ok so i'm guessing busybox is required to be able to run the Current Book Cover Screensaver.
1st i turned on adb wireless.. installed the files per the instructions over ADB
rebooted and I was stuck in a boot loop
2nd restored to a fresh firmware.
Installed adb wireless, superuser, su, and busybox.
Then installed the files per the instructions over ADB
rebooted and everything works great.
Now i just wonder if i can uninstall Superuser or busybox...
Click to expand...
Click to collapse
hi,
while i'm not totally sure, i suppose you can definitely uninstall both superuser and busybox.
In any case, the modified ramdisk with ADB enabled (either WiFi or USB) is enough to allow you to push/pull files to Nook, and to open a shell (as root).
Busybox is just convenient if you plan to use shell sessions since it includes commands like cp to copy files, and others, but you can live without it (using ADB push to copy files, or using command dd, for instance).
Superuser, if you refer to android application (APK) it's just used by all other applications requiring root privileges (like RootExplorer, for instance), but if you don't plan to use them, then it's not needed.
In any case, you have practically my same configuration (as close as possible as stock firmware): after all, i use Nook just to read books, so don't need custom launcher and google apps! I would just mention XorZone modification that is really useful for me, since it's can act as a sort of launcher, and can deal with useful features like button remapping. The only other application i have installed is this PDF reader, since the stock one is really poor, while this one has a better zoom management, and also has specific features for e-ink devices and expecially for the Nook (like partial refresh).
Of course, to install the applications, i just use ADB.
traycold said:
In any case, you have practically my same configuration (as close as possible as stock firmware): after all, i use Nook just to read books, so don't need custom launcher and google apps!
Of course, to install the applications, i just use ADB.
Click to expand...
Click to collapse
Ok so something must have gone wrong when I installed your screen saver mod if i was stuck in a boot loop. Because I assuming you have it installed on yours with out superuser, and busybox... i just i can just install them now and then it should still work.
I also just use the nook to read EPUB book, i have a very nice android tablet that i use for anything and everything else. I would much rather have a high battery life on the nook then bells and whistles i don't ever use.
If you're running linux or have access to a linux box, you could just grab noogie and it should show all partitions. With this you could make the changes without ever having to touch the uRamdisk or ADB or needlessly installing anything to actually root the device.
As it is if you were to try this your way you'd have to first root it using like Minimal Nooter or TouchNooter then remove everything you don't want afterwards (su/superuser/busybox/gapps/etc).
Personally what I did was I installed touchnooter and because I like my devices to appear stock I left all the buttons unmodified while leaving a very faint button savior icon on one side that'll allow me access to android launcher the app drawer etc. This way I can use it like a proper android device without having it appear as anything more than a basic reader.
GabrialDestruir said:
If you're running linux or have access to a linux box, you could just grab noogie and it should show all partitions. With this you could make the changes without ever having to touch the uRamdisk or ADB or needlessly installing anything to actually root the device.
As it is if you were to try this your way you'd have to first root it using like Minimal Nooter or TouchNooter then remove everything you don't want afterwards (su/superuser/busybox/gapps/etc).
Personally what I did was I installed touchnooter and because I like my devices to appear stock I left all the buttons unmodified while leaving a very faint button savior icon on one side that'll allow me access to android launcher the app drawer etc. This way I can use it like a proper android device without having it appear as anything more than a basic reader.
Click to expand...
Click to collapse
Hmm interesting...
What i did was i restored to stock... so my nook was completely unrooted...
Switched the uRamdisk using noogie then ADB the following files over and set the permission...
android.policy.jar [needed only for "current book cover screensaver"];
services.jar [needed only for "current book cover screensaver"];
Settings.apk [needed only for "current book cover screensaver"];
framework.jar [needed only for "custom shutdown image"];
What your saying is just use noogie and linux to replace the files and set the permissions.
I plan on Dual Booting my G-Tablet with linux so i can resize the partitions on the nook, I'm going to try your suggestion and see how it goes..
There is an interesting discussion on the Russian forum the-ebook.org (paste this link into Google and select the translation; item is on page 2) regarding those annoying invisible menu options in many apps. Although the translation is a little rough around the edges, the gist seems to be that the default text and background colors for the app menus are not exactly what the e-ink display has in mind, often resulting in light or near-white text on a white background--hence, invisible text.
The "solution" used is to change some background color settings in framework-res.apk. I have no idea what the outcome looks like but it seems like a really good idea, although beyond my abilities, and the example used is 1.10 firmware. I'm using 1.21. Any attempt I have made to modify apk files has always failed
Does anyone have a fool-proof set of steps for doing this?
I remember reading about what you're talking about somewhere on the forums but I could never get it to work either...
Here's what I'm talking about:
http://forum.xda-developers.com/showthread.php?t=1356514
http://forum.xda-developers.com/showthread.php?t=1512846
OK, well.....I've got the adjusted background images extracted from the framework-res.apk file that I got from the Russian site (I'm working with the lighter background option at this point). And...I've found the setting in WinRar to simply "store" (not compress) the updated png files. So far, so good. My altered apk file is the same size as the original.
The clincher is to get it back on the Nook without disaster ensuing. I'm going to follow Renate's method for pushing back framework-res.apk via ABD (from this thread):
C:\>adb shell
# stop
# mount -o rw,remount /dev/block/mmcblk0p5 /system
# ^C
C:\>adb push framework-res.apk /system/framework
C:\>adb shell
# reboot
Keep your fingers crossed. If it works, I'll report back with step-by-step and files.
[Report: in concept this "works". On reboot I could see the slightly grey background color in menu options and going to a few apps where I knew the menus were invisible, I could see white text on the slightly grey background. BUT...almost no apps will work. The B&N side seems to function OK, but the App drawer is useless. Back to the drawing board. The Russian site has a method for installation using RootExplorer. I'll try that next.]
OK...day 2. Here's what does NOT work:
1. method in post above using ADB
2. method using RootBorwser as adapted from Russian site and detailed below:
a. Change permissions in /system, /system/etc and /system/framework folders so that all users have write access
(note this is my kludge to get around not knowing how to "mount" the /system partition as r/w--maybe it's wrong?)
b. Use ADB wireless to move modified framework-res.apk into /system/etc
c. Use RootBrowser to check ownership of modified framework-res.apk (should be and was already owner: 0-root, group: 0-root)
d. Use RootBrowser to change permissions on modified framework-res.apk to rw-r--r-- (664)
e. Use RootBrowser to move (cut/paste) modified framework-res.apk into /system/framework (overwrite)
With Superuser permission, this all went off without a hitch.
f. Use RootBrowser to reset permissions of folders listed in (a)
g.Shut down Nook and restart.
The result is the same as the ADB-only method described before. The Nook starts up just fine. You can see that the background color of menus is slightly gray. Those changes have obviously worked. But the vast majority of apps will not run (ADW Launcher is an exception). At one point while I was fiddling with things the Nook spontaneously rebooted.
I guess that's better than spontaneously combusting
SIGH. Clearly, despite my best efforts, something I did in handling the framework-res.apk has damaged it in some subtle way, OR, my inability to properly "remount" the /system as R/W is causing the problem, although using ADB this is accomplished without difficulty and since the result is the same...it must be the modified apk file.
And this is why I have a dedicated SD card backup......
Method 3 that does NOT work:
1. Install Ninjamorph and BusyBox from Market
2. Follow instructions for altering framework-res.apk found here.
Two ways to Finish Project, with zip-align and without. Both yield the same result which is the same as the other methods above, i.e., the B&N stuff mostly works and the desired contrast of the menus is achieved so you can actually see what used to be invisible, but most apps will not run. Really frustrating.
I have to say that while this method seemed promising it is tedious in the extreme as each of the 28 png files must be replaced individually and that means each must be located in a much larger list (which reverts to the top after each replacement....). Ugh.
I simply don't believe anyone who says they can make these modifications with the instructions they have provided. It must be that people who are more familiar with this stuff are leaving out information which is so obvious to them that they don't even think to mention it
framework-res.apk is an apk and therefore it must be signed.
It's a system apk so it must be signed with the system signature.
Modifying a few things doesn't annoy the signature matching, other stuff does.
When you have problems, please quote from logcat because that tells you exactly what the problem is.
Using ADB:
Code:
logcat
Whatever.9.png are special files.
The are usually created thusly:
http://developer.android.com/guide/topics/graphics/2d-graphics.html#nine-patch
When they get packed into an apk they are turned into a PNG graphic with alpha channel.
aapt handles this.
If you take a PNG with sidebars and just zip it, it will not work.
Renate NST said:
When you have problems, please quote from logcat because that tells you exactly what the problem is.
Using ADB:
Code:
logcat
Whatever.9.png are special files.
The are usually created thusly:
http://developer.android.com/guide/topics/graphics/2d-graphics.html#nine-patch
When they get packed into an apk they are turned into a PNG graphic with alpha channel.
aapt handles this.
If you take a PNG with sidebars and just zip it, it will not work.
Click to expand...
Click to collapse
I just tried again and this time after pushing the amended framework-res.apk file (yes, all 28 amendations are nine-patch files) I typed in logcat before rebooting.
Whoosh!!! Lines of information went streaming by faster than I could follow, so much that some of the earliest disappeared from the top of the console window. I have no clue how to extract the text from the console window
The top-most complaint I saw was a reference to system error 1248 in association with the CleanMaster app. Then there seems to be a periodic (15 second) dhcpcd renewal. Eventually there is a section that says "Framework disconnected, eof, failed to read size, closing connection". Then comes a long list of notifications from the Service Manager about all the services that have just died. After that it just continues with the 15-second dhcpcd renewal cycle. Then I gave up and rebooted.
The result is the same as before. The new image backgrounds have been incorporated into the system, but most of the app drawer is just pretty icons. ADW runs--at least the drawer and home page appear. The B&N Home and Library pages load but you can't access any of the books shown. Wi-Fi can be accessed but no apps that use it will run. Occasionally the CleanMaster app throws up an error message.
Here's what I've learned so far:
1. In the original amended framework-res.apk file (for FW 1.10) viewing the archive reveals that the files which have been changed all have an "archive " attribute. None of the original files show any attribute. I don't know whether that is important. I've searched on this topic and have come up with nothing.
2. In moving the amended *.9.png files from the original Russian example for FW 1.10 into a copy of my own framework-res.apk for FW 1.21, those "archive" attributes came along for the ride and the resulting amended file does show "STORE" for the method so I think I got that part right and didn't recompress any files when moving from one apk to another (I dragged the files from one instance of WinRAR to another--I tried 7zip as well...).
But I have no idea why people report that this procedure works just fine. For me, it is predictable, but not successful.
I've just completed yet another restore from backup. I'm going to uninstall CleanMaster and try again. Perhaps it's background activities are driving the process into the ground. I have no clue.
Here's the logcat session file (learned how to get that done!) after a re-try, having removed CleanMaster first.
No change in the outcome but no bleating from the Nook about CleanMaster errors.
I wonder--is it the modified apk that is causing the system to malfunction, or....is it the way it is being pushed back to the Nook?
So..an experiment: I pulled a copy of the stock framework-res.apk from my Nook. I didn't do anything to it at all. Then I pushed it back to the Nook via wireless ABD:
C:\>adb shell
# stop
# mount -o rw,remount /dev/block/mmcblk0p5 /system
# ^C
C:\>adb push framework-res.apk /system/framework
C:\>adb shell
# reboot
This is supposed to work, yes? It does not. It leaves me in the same condition that all of the other attempts by this and other methods have. The Nook boots normally and displays Home but you can't access the "currently reading" book. I can get to the app drawer via the quicknav buttons, but very few apps will work (including ADB). There is no way to examine the file system because RootBrowser will not work (although ES File Explorer does, but it doesn't have root access).
So....whether the modified apk is OK or not, I would never know because all of the methods I have tried to get the framework-res.apk back onto the Nook have been unsuccessful.
That procedure should work fine.
Have you checked using the stock framework-res.apk ?
Renate NST said:
That procedure should work fine.
Have you checked using the stock framework-res.apk ?
Click to expand...
Click to collapse
Yes, that's what I just tried. Just pulled it via ADB and then pushed it right back. I also installed a copy of Root Explorer (I generally used Root Browser) because that's what was used in the original thread on the Russian site where I got started with the whole project. That also yields the same results. The Home screen loads but you can't access the book currently being read from it or from the little button at the top left. You can access any of the QuickNav options. The Library "functions". But you can't access books from their covers and the double-tap does not work.
In the app drawer, ADW seems to work fine but you can only run a very few apps, and none that require wi-fi (although wi-fi works). Too much fiddling around and the Nook spontaneously reboots.
When I have tried to move in the modified apk with the slightly gray background 9.png files I can see that the new image backgrounds have been used in the drop-down menus. This suggests to me that the problem is not in how the 9.png files have been moved from the FW1.10 apk obtained from the Russian site into my FW1.21 apk but rather in the integration of the modified apk into the system. I've checked permissions, etc. Everything is OK but the system is just screwed up.
I'm running FW1.21 which has been rooted using Nook Manager with Gapps added. I've done the multi-touch modification and have swapped in a modified internal.db file which seems to have solved the confusion of the "reading now" button. I have some apps that run along in the background, like Tasker and Clean Master (probably others that I don't realize). Do I need a completely clean system to make this change?
I saw the logcat and it showed that it's unhappy and killing the Android.
I couldn't see exactly where the problem is.
I think that you are doing too many things at once.
If there are specific things that do not work, a logcat when you do that should show.
Renate NST said:
I saw the logcat and it showed that it's unhappy and killing the Android.
I couldn't see exactly where the problem is.
I think that you are doing too many things at once.
If there are specific things that do not work, a logcat when you do that should show.
Click to expand...
Click to collapse
Yes, I was probably a little unclear. The ONLY thing that I did when I produced the logcat was attempt to push the modified framework-res.apk file back to the Nook. All those other things mentioned have long ago been successfully accomplished and included in my current backup (which I've had to use dozens of time in the last week or two as I struggle with this framework issue).
The ONLY change to the stock framework-res.apk is the overwriting of 28 *.9.png images with ones copied from another framework-res.apk which, unfortunately, is from FW1.10 (or I'd just use it "as is" without the copying). However, even pushing back an unmodified stock apk results in the same mess.
Like I say, based on what functionality remains when the modified apk file is pushed over, it is clear that the new images are being used, but the system function is severely degraded.
I don't know much about the process, but from what I've read I'm wondering if it would be better to use a zip via CM to deliver this modified file? That way the Android system is not even running (right?) during the replacement procedure.
When you say "stop" Android is no longer running.
Try clearing the cache:
Code:
rm -R /data/dalvik-cache/*
Renate NST said:
When you say "stop" Android is no longer running.
Try clearing the cache:
Code:
rm -R /data/dalvik-cache/*
Click to expand...
Click to collapse
Before pushing? After, but before rebooting?
Anytime that Android is stopped you can clear the cache.
I tried this with a copy of the stock apk:
Code:
C:\>adb shell
# stop
# rm -R /data/dalvik-cache/*
# mount -o rw,remount /dev/block/mmcblk0p5 /system
# ^C
C:\>adb push framework-res.apk /system/framework
C:\>adb shell
# reboot
It put me in an very long chase of the black and white dots that I almost thought would be endless but eventually it finished booting and is in the same condition as all the previous methods. Very crippled.
I can't figure it out
First, get the 1.2.1 update off B&N's website and unzip.
Get framework-res.apk out of that and push it.
The stuff in /system/framework should all be chmod 644.
An ADB push probably leaves it with wider access.
None of this should make any difference.
I'd guess that you are either missing a resource in your fw-r or else you modified something else.
Find an app that crashes. Get a logcat of just that crashing.
Renate NST said:
First, get the 1.2.1 update off B&N's website and unzip.
Get framework-res.apk out of that and push it.
The stuff in /system/framework should all be chmod 644.
An ADB push probably leaves it with wider access.
None of this should make any difference.
I'd guess that you are either missing a resource in your fw-r or else you modified something else.
Find an app that crashes. Get a logcat of just that crashing.
Click to expand...
Click to collapse
I got a copy of the FW 1.21 zip from B&N and extracted the framework-res.apk. I didn't try to push it yet. Instead I got the checksum for the current file on the Nook and compared it to the newly minted file. They were identical. I don't think there is any point in trying yet again with the same procedure. If my reasoning is incorrect, I'm certainly game to try anyway.
All files in /system/framework are chmod 644. The Framework folder itself (and the system folder) are something else, but the contents are all 644.
The only modifications I have made after rooting with Nook Manager are the installation of Google Apps, the implementation of multi-touch (I have to go back and look that up to see what all I did, but surely nothing with framework-res.apk or it never would have worked....), editing settings.db to relabel the QuickNav buttons after programming with NTMM, and pushing a modified copy of internal.db to fix the schizo "reading now" button. As i say, these are all long-established changes and the Nook has been stable with them. I think Google apps may modify framework.jar, but I'm not sure.
[I checked on multi-touch. I flashed a new kernal image and added one line to /etc/permissions/required_hardware.xml in order to enable multi-touch...have no idea what "flashed a new kernal" actually did, but it worked]
Two really noob questions: 1) how can I get a logcat of an app crashing when ADB will not run once a copy of framework-res.apk has been pushed? 2) if the Android system is actually stopped when I type "stop"in ADB shell, how does ADB continue to function?
And, actually, apps do not so much "crash" once I've attempted to put in a "new" framework-res.apk--most just refuse to run. But maybe there is something going on in the droid brain while the screen flickers a little and nothing else happens.
ADB runs under Linux, not the Android subsystem.
You should always be able to access ADB.
If ADB isn't running continuously and reliably you have problems.
If some app does not run, give the specific section in logcat where it doesn't run.
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
???
Source code to an alpha tool in Python-QT, if you guys are python savvy show some love <3
https://bitbucket.org/dylanmulrooney/android-launcher/src
In this thread you will finally be able to remove Amazon's terrifying FireLauncher for good, and replace it with your choice of a launcher.
Prerequisites:
Install ADB
Install Nova Launcher / launcher of choice
BACKUP YOUR FIRELAUNCHER.APK
You do not need to corrupt the firelauncher as I have, but it eats system resources and I never want to see it pop up. I have attached a modified version of the firelauncher APK. You will need to download and install it as an update via ADB.
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Now we need to run a single line of ADB code every time you reboot your device:
Code:
adb shell
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
Code:
exit
This is designed (in combination with destroying firelauncher) to allow you to set any launcher, by default I have it set to am start Nova Launcher.
Once you paste that line of code in adb, you can unplug your device and use it with your new custom launcher!
Please feel free to contact me for detailed instructions!
Cautiously optimistic. Waiting for field evidence before recommending. As always reputations are earned.
First I'd love to thank you for your continuing support to give more launcher choices to the Amazon Fire.
Where can I find and back up the original fire launcher? So if, in the future, we want the fire launcher back, we just install the backup? Any script to run to undo?
About this "Now we need to run a single line of ADB code every time you reboot your device:".
So it cannot be automatically executed?
while trying to adb intall the apk, it shows error: https://www.dropbox.com/s/syyggde0ie7sf4t/Screenshot 2016-09-24 21.58.03.png?dl=0
UPDATE: I got it installed now. The issue above because I ran adb shell first. Anyway, it doesn't seem to shut down the Fire Launcher as I can still see briefly when pressing Home button; and it doesn't allow to set another launcher as default beside Nova. (Fire HD 10 - 5.3.1)
Let's say we want to set a different default launcher to this one: https://play.google.com/store/apps/details?id=com.citc.asap&hl=en
What should we type? Can you try with the above launcher cz' it cannot be launched till it's set as default?
FYI, as we cannot root this 5.3.1, so using the above launcher 'ASAP Launcher' will be awesome as it has built-in widgets. One more is Arrow Launcher by Microsoft.
The other one is Buzz Launcher: https://play.google.com/store/apps/details?id=com.buzzpia.aqua.launcher&hl=en
it's pretty heavy with built-in widgets and themes.
---------- Post added at 03:58 PM ---------- Previous post was at 03:01 PM ----------
I used your previous code from another post for Windows manually: http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 , and it allowed to select any installed launcher as default, the issue it doesn't stick when restarted:
Code:
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
ttcontributor said:
First I'd love to thank you for your continuing support to give more launcher choices to the Amazon Fire.
Where can I find and back up the original fire launcher? So if, in the future, we want the fire launcher back, we just install the backup? Any script to run to undo?
About this "Now we need to run a single line of ADB code every time you reboot your device:".
So it cannot be automatically executed?
Click to expand...
Click to collapse
I do not have a working firelauncher, and honestly I do not want it. That step is optional and the only purpose of removing it is so I never accidentally see it for a second.
I am still working on improving this, please feel free to request features!
Yes, it can be automated just not easily.. You would need to install an app and then paste the command in the apps etc. I never reboot my device so it's not a priority for me. Let me know if you have any ideas. It works flawlessly right now, speeds up the tablet.
ttcontributor said:
while trying to adb intall the apk, it shows error: https://www.dropbox.com/s/syyggde0ie7sf4t/Screenshot 2016-09-24 21.58.03.png?dl=0
UPDATE: I got it installed now. The issue above because I ran adb shell first. Anyway, it doesn't seem to shut down the Fire Launcher as I can still see briefly when pressing Home button; and it doesn't allow to set another launcher as default beside Nova. (Fire HD 10 - 5.3.1)
Let's say we want to set a different default launcher to this one: https://play.google.com/store/apps/details?id=com.citc.asap&hl=en
What should we type? Can you try with the above launcher cz' it cannot be launched till it's set as default?
FYI, as we cannot root this 5.3.1, so using the above launcher 'ASAP Launcher' will be awesome as it has built-in widgets. One more is Arrow Launcher by Microsoft.
The other one is Buzz Launcher: https://play.google.com/store/apps/details?id=com.buzzpia.aqua.launcher&hl=en
it's pretty heavy with built-in widgets and themes.
---------- Post added at 03:58 PM ---------- Previous post was at 03:01 PM ----------
I used your previous code from another post for Windows manually: http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 , and it allowed to select any installed launcher as default, the issue it doesn't stick when restarted:
Code:
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
Click to expand...
Click to collapse
I love you for being so helpful in the development of this project. You simply change the code to whatever launcher you want, you just need the package name/activity. I also think it would be wise to reboot when running the command since two instances may cause glitches without killing the nohup process.
I will make a tool that simplifies your life, drag and drop launcher of choice apk and it'll set it as default & remove amazon ****ware.
I have released the source code to my alpha project, should work cross platform (need testers who know Python!)
https://bitbucket.org/dylanmulrooney/android-launcher/src
nyln said:
I love you for being so helpful in the development of this project. You simply change the code to whatever launcher you want, you just need the package name/activity. I also think it would be wise to reboot when running the command since two instances may cause glitches without killing the nohup process.
I will make a tool that simplifies your life, drag and drop launcher of choice apk and it'll set it as default & remove amazon ****ware.
Click to expand...
Click to collapse
Great, after reboot and re-run the command I didn't notice the Fire Launcher no more when pressing home, but sometime just a blank screen breifly before going to the set launcher. And it's a wonderful news for "drag and drop launcher of choice apk and it'll set it as default & remove amazon****ware"
FYI, currently I'm combining your method by 1# install your attached .apk to corrupt the Fire Launcher, and #2 use the previous code above to be able to select any launcher installed. It's better because it can detect a new launcher installed from PlayStore and provide the option to select it as default: https://goo.gl/photos/qQzohRJNMEifCkyw6
ttcontributor said:
Great, after reboot and re-run the command I didn't notice the Fire Launcher no more when pressing home, but sometime just a blank screen breifly before going to the set launcher. And it's a wonderful news for "drag and drop launcher of choice apk and it'll set it as default & remove amazon****ware"
FYI, currently I'm combining your method by 1# install your attached .apk to corrupt the Fire Launcher, and #2 use the previous code above to be able to select any launcher installed. It's better because it can detect a new launcher installed from PlayStore and provide the option to select it as default: https://goo.gl/photos/qQzohRJNMEifCkyw6
Click to expand...
Click to collapse
Very interesting. I finished a rough alpha version of drag and drop, I posted the source code but no compiled binaries yet. I will make an option to select the launcher of your choice.
Give me the app name and I'll write a special code for you since nova sucks
nyln said:
Very interesting. I finished a rough alpha version of drag and drop, I posted the source code but no compiled binaries yet. I will make an option to select the launcher of your choice.
Give me the app name and I'll write a special code for you since nova sucks
Click to expand...
Click to collapse
Nova is good if rooted. In this case, ASAP Launcher is unbeatable: https://play.google.com/store/apps/details?id=com.citc.asap&hl=en
OR EVEN BETTER > TOTAL LAUNCHER: https://play.google.com/store/apps/details?id=com.ss.launcher2
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.citc.asap; done &
nyln said:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.citc.asap; done &
Click to expand...
Click to collapse
Awesome.
I have been testing a lot of launchers to find one that is customizable with widgets without root, and found Total Launcher: https://play.google.com/store/apps/details?id=com.ss.launcher2
Now settling for this as it has internal / built-in widgets which can be added to Fire OS WITHOUT root and converting the launcher to system app. What is the package code for this one then?
UPDATE:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.ss.launcher2; done &
It'd be completed if it can be autorun after system restart of packed to an app to tricker this in Amazon Fire itself.
ttcontributor said:
Awesome.
I have been testing a lot of launchers to find one that is customizable with widgets without root, and found Total Launcher: https://play.google.com/store/apps/details?id=com.ss.launcher2
Now settling for this as it has internal / built-in widgets which can be added to Fire OS WITHOUT root and converting the launcher to system app. What is the package code for this one then?
UPDATE:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.ss.launcher2; done &
It'd be completed if it can be autorun after system restart of packed to an app to tricker this in Amazon Fire itself.
Click to expand...
Click to collapse
I may have a temporary workaround for auto restart. I just don't see how this makes or brakes it. You can paste that command in Terminal Emulator if you don't want to use a computer on reboot.
nyln said:
I may have a temporary workaround for auto restart. I just don't see how this makes or brakes it. You can paste that command in Terminal Emulator if you don't want to use a computer on reboot.
Click to expand...
Click to collapse
Think it depends on the user. For many launching Terminal Emulator and pasting in a command is a PiTA that offsets the benefit of a custom launcher. Technical enthusiasts don't mind so much but they are the minority of the Fire user community ime - even on XDA.
nyln said:
I may have a temporary workaround for auto restart. I just don't see how this makes or brakes it. You can paste that command in Terminal Emulator if you don't want to use a computer on reboot.
Click to expand...
Click to collapse
Well, at least we don't need to rely on the computer no more! And it will be a set-it-and-forget-it if we input the command to the Terminal Emulator to auto execute?
And about the ppl using Fire OS, there are still many out there. Once they know it can be customized to their liking, they will pop up!
ttcontributor said:
And about the ppl using Fire OS, there are still many out there. Once they know it can be customized to their liking, they will pop up!
Click to expand...
Click to collapse
FireOS is a solid alternative to more 'traditional' Android presentations once ads, bloat and other Amazon cruft is tamed. The ability to toggle launchers on non-rooted devices will be welcome by many if it can be made largely transparent once implemented.
Thanks for your feedback guys. I am working on an update that will simplify your lives.
nyln said:
Thanks for your feedback guys. I am working on an update that will simplify your lives.
Click to expand...
Click to collapse
Which code can I paste to the Terminal Emulator to not use the pc then? Then we can have the Emulator auto run the script when reboot?
Back to Firelauncher
nyln said:
Source code to an alpha tool in Python-QT, if you guys are python savvy show some love <3
https://bitbucket.org/dylanmulrooney/android-launcher/src
In this thread you will finally be able to remove Amazon's terrifying FireLauncher for good, and replace it with your choice of a launcher.
Prerequisites:
Install ADB
Install Nova Launcher / launcher of choice
BACKUP YOUR FIRELAUNCHER.APK
You do not need to corrupt the firelauncher as I have, but it eats system resources and I never want to see it pop up. I have attached a modified version of the firelauncher APK. You will need to download and install it as an update via ADB.
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Now we need to run a single line of ADB code every time you reboot your device:
Code:
adb shell
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
Code:
exit
This is designed (in combination with destroying firelauncher) to allow you to set any launcher, by default I have it set to am start Nova Launcher.
Once you paste that line of code in adb, you can unplug your device and use it with your new custom launcher!
Please feel free to contact me for detailed instructions!
Click to expand...
Click to collapse
How do I revert back to Firelauncher?
imblogr said:
How do I revert back to Firelauncher?
Click to expand...
Click to collapse
Recommend you reload FireOS via stock recovery as it is not clear how to fully revert the changes. Sure, you could read through the instructions and figure it out...starting from scratch will probably be quicker with better outcomes. The OP has not posted for awhile; not sure he/she is still around.