yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] JulesJam:
Ah, yeah not sure why anyone ever wanted those anyhow. They were nothing but trouble from the beginning. I think the guy who requested those is now on Fi with a Nexus 6.
[X 2014 Android Development] mikeoswego:
AdAway image

Here is an image for AdAway users with a symlink for the hosts file: XT1096_5.0-tether-root-bb-sqlite3-XposedV65-DeBloat-AdAway.img.7z

Set AdAway to use /data/data/hosts for the hosts file location.

The current AdAway is here: AdAway-release_Build-Apr.09.2015.apk

If you're not already running an image with Xposed, see the first post for instructions. The apps debloated are listed here: Post 169
[X 2014 Android Development] redwings73:
Awesome. I'll try it as soon as I can!
[X 2014 Android Development] rhpot1991:
The google dialer is pretty nice, does a lookup of whoever is calling you.
[X 2014 Android Development] mikeoswego:
Yes, that is one of it's features but it doesn't actually work on Verizon because there is no data while a voice call is in progress (including while it is ringing.)

The upgrade to VoLTE enables data during a voice call but we don't have that.
[X 2014 Android Development] rhpot1991:
Works for me on Verizon. I wonder if I was on wifi at the time.
[X 2014 Android Development] mikeoswego:
I'm very sure that it did work on my 1st gen Moto X (RIP) but it doesn't on this 2nd gen model. Without VoLTE, voice calls go out over one radio and LTE is on another. I've heard that Verizon asked the vendors to disable the ability for both radios to be active at the same time in order to push people into VoLTE.

Being on WiFi would allow the Google dialer lookup to work.
[X 2014 Android Development] RyanBRZ:
Does anyone know if xposed would allow an app such as Trigger to allow hotspot auto toggle?

What are the key cool factors of xposed on the moto x?
[X 2014 Android Development] mikeoswego:
I doubt that Xposed would make any difference in Trigger functionality.

I want Xposed mostly to use Gravity Box. A partial features list of Gravity Box for Lollipop are listed here: http://xdaforums.com/xposed/modules/app-gravitybox-v5-0-0alpha-tweak-box-t3037566

The QS tile addition/reordering, ascending ringtone, quick unlock, cursor control keys, reboot menu are among the things I'd miss without having Gravity Box for Xposed on my phone.
[X 2014 Android Development] RyanBRZ:
Ok, I have gravitybox installed and it does offer some nice options. I was hoping to add toggling hotspot because I have an android radio in my car and I want it to enable the hotspot when I leave my home and work wifi (trigger app does this), but it clearly states in market that hotspot toggle is not currently working for lollipop.

Another thing I want is a toggler bar for wifi/bluetooth/gps etc when I drop-down the status bar. My galaxy s3 had this and I really miss it. I know if I 'double' drop down my status bar I get the full-screen toggles, but I like the thin bar that stays right under the status bar. Any recommendations?
[X 2014 Android Development] contesauce:
Hotspot toggle works for me on lollipop give it a try. Someone might be able to chime in on the quick settings you're talking about, if there's not an option in gravitybox there may be an xposed module precisely for that.
[X 2014 Android Development] jrbmed08:
I can't find a Q&A thread for this image, so I'll post my question here:

I'm currently on the original version of TotalX and have Xposed and AdAway running perfectly. Because of the 911 dialing concern on TotalX (I'm not sure if it's even an issue on my image but assuming it is), I'm considering flashing the latest image here. Since I already have Xposed and AdAway, can I just flash it and be good to go, or do I have to take any other steps to make sure they work? Thanks all!
[X 2014 Android Development] contesauce:
You may have to delete dalvik and data folder before you flash or your dialer and messenger app will crash when you flash the new image. Other than that the new image should flash without trouble.
[X 2014 Android Development] RyanBRZ:
What I meant by hotspot toggle is an automated toggle (not physically clicking a button).

Trigger is an app that can change settings when connecting/disconnecting from named wifi and bluetooth networks. It's really useful for switching stuff on and off when I arrive/leave work, arrive/leave home.
[X 2014 Android Development] contesauce:
Oh gotcha, I'm tracking now. You could use tasker in conjunction with auto input app.
[X 2014 Android Development] jrbmed08:
Thanks - I'll do that!
[X 2014 Android Development] contesauce:
what worked for me was erase your cache and delete all the things in /data/dalvik-cache then reboot to get the original dialer to work again after having had the Google dialer installed. if you are still having trouble. try deleting /data/dalvik-cache/arm/system@priv-app@Dialer@Dialer.apk@classes.dex only and erasing cache to see if that fixes the problem<br />

The first one should work for you, when you boot up again its going to optimiZe all your apps again so be patient.
[X 2014 Android Development] jrbmed08:
Did you delete those before or after you flashed?
[X 2014 Android Development] contesauce:
The first time I did it I forgot to do it so when it booted I was getting dialer and messenger crashes, so lesson learned. You can do it either way but I'd suggest doing it first and clean cache through fastboot before and after flash to be safe.
[X 2014 Android Development] mikeoswego:
In Gravity box in QuickSettings management, you can set quick pulldown. With that, you just swipe down at the right edge of the status bar and the QS tiles shown with one swipe. Not exactly what you are asking for but maybe better than the double swipe.

I don't have an answer for you on the automatic hotspot, aside from what [MENTION=5122731]contesauce[/MENTION] said about trying tasker or one of the other automation apps that are out there. Can you install the hotspot toggle app and then call that from your automation app?
[X 2014 Android Development] Haxxa:
So Mike,

Given we are now able to successfully flash 5.1 images using MOFO do you plan to use 5.1 as your base for future images? JulesJam and I have both being able to upgrade to 5.1 using Mofo with this image - https://mega.co.nz/#!rJFk2QLS!K4cdxJ-4rSIbAewYx1fSKCkGVGf-6XvXzg5E92qA8M0 . So far all we have is tethering, would be nice to have root and xposed plus 5.1 features. Is this something your interested in?
[X 2014 Android Development] mikeoswego:
I'm now running 5.1 and have a full set of mofo images ready to upload:

XT1096_5.1-Base - Just the files from the full image that need to be flashed before flashing a mofo 5.1 image. (34 MB)

XT1096_5.1-tether-root-busybox-sqllite3 (1.11 GB)

XT1096_5.1-tether-root-busybox-sqllite3-Xposedv65 (1.11 GB)

XT1096_5.1-tether-root-busybox-sqllite3-Xposedv65-DeBloat (782 MB)

XT1096_5.1-tether-root-busybox-sqllite3-Xposedv65-DeBloat-AdAway (782 MB)

Unfortunately, my internet provider is having some kind of malfunction (actually, I'm pretty sure I'm being throttled) and I'm getting like 512k down and 2k (or 0k) up during the daytime hours. I can't get anything pushed up right now. Later today I'll be somewhere that uses a different provider and I'll try from there. Otherwise, it might be after midnight when things have consistently sped up dramatically for my connection during the last few days.. I'll push the AdAway image first since that seems to be the most wanted.
[X 2014 Android Development] Haxxa:
NICE!! (Quick Request: Not sure if you have or not but could you replace the default Verizon Bootanimation with either the stock animation by simply replacing bootanimation with bootanimation-encrypted or with any other snazzy animation - plenty in the themes and apps section of the Forum?).
[X 2014 Android Development] mikeoswego:
Interesting that you mention that.. When I first ran the 5.1 image, I noticed the boot animation was the same as before. I did some things and then rebooted; the boot animation was different, it was a spool of thread and needle stitching the moto logo. I looked and the bootanimation.zip file in /system/media had not been changed and still had the old animation. Looked some more and found a new bootanimation.zip in

/data/local/moodle
permissions rwx rwx rwx (chmod 777)
owner:group u0_a40:u0_a40
chcon u:object_r:moodle_data_file:s0

Maybe you could try putting another boot animation in that location, if so, then we will be able to change them at will! (I've also left Moodles in the debloat image since it apparently works with root now.) It would also be interesting if someone still on 5.0 would try this as well.
[X 2014 Android Development] mikeoswego:
I've had a chance to test and it works to copy your desired bootanimation.zip file into /data/local/moodle, check your permissions are 777 (rwxrwxrwx) and set both owner and group to u0_a40 using your root file explorer. No need to worry about chcon. Choose your boot animation of choice and be happy!

Would someone test this and see if this works on 5.0 just for general knowledge?
[X 2014 Android Development] JulesJam:
Did you run into any issues with your rooted 5.1 image when you flashed it using MoFo? Mine causes the dead android to blink in recovery and I have to boot back into bootloader mode and then into system and do a factory reset to clear the issue.

I may have rooted my image incorrectly.

If yours works fine, then no need for me to do any more work on mine. I was simply rooting the 5.1 image as a starting point for those of you who know how to use linux, but it looks like you already did too. Thanks so much for this!!!!

---------- Post added at 07:49 PM ---------- Previous post was at 07:36 PM ----------

This is why I tether my computer to my phone. My Verizon upload speeds are so much faster but I have UDP so it doesn't matter how much data I use on Verizon.
[X 2014 Android Development] mikeoswego:
I thought you had trouble due to not flashing the recovery.img file? I flashed everything except gpt.bin and motoboot.img. Recovery works fine as does everything else I've tested.

I try to be coy about it, but Verizon is my provider and for the last 4-5 days, things have been terribly slow except during the late night hours. Still brutally slow at the moment.
[X 2014 Android Development] JulesJam:
I did too then I flashed it and went back completely to stock 5.0 and then started again from scratch flashing everything from 5.1 but the bootloader and PT. Then the rooted 5.1 using MoFo. It is possible I did something wrong in making my rooted image. If yours work, there is no reason for me to redo mine. So I will flash yours when you upload them.

My Band 13 towers were like that but once they lit up Band 4, it is quite speedy on the uploads. But I can't control whether they put me on Band 13 or Band 4.

There was a testing period before the Band 4 became fully operational and during that time there were slow speeds. I use LTE Discovery app to know which band and tower they have me on and that is how I know. You might want to install it and see if they are switching you back and forth b/t Band 13 and Band 4 and if they are, they may be testing new Band 4 towers in your area right now and things may improve. At least that is what happened with me.
[X 2014 Android Development] mikeoswego:
Here is a basic 5.1 image. It is full stock with tether, root, and busybox & sqlite3 installed for root use. This a basic image and one to make other images from.

XT1096_5.1-tether-root-bb-sqlite3.img.7z

Full info in Post 2
[X 2014 Android Development] neh4pres:
anyway you can add the adaway simlink on the non de-bloated images also? assuming there are no issues with it, it would be useful if it was on every image then we can chose to use the app or not. thanks for everything man
[X 2014 Android Development] mikeoswego:
And 2 more:

XT1096_5.1-tether-root-bb-sqlite3-Xposedv65.img.7z - 5.1 image with root and Xposed

XT1096_5.1-tether-root-bb-sqlite3-Xposedv65-DeBloat.img.7z - 5.1 Image with some bloat removed

Full info in Post 2
[X 2014 Android Development] mikeoswego:
I'll consider it but am not sure I see the logic. Which of the debloated apps that aren't updated/available in the Playstore would someone who is ad averse want to have?
[X 2014 Android Development] mikeoswego:
The other issue with having the symlink in all the images is that people would be required to create a hosts file in /data/data if they weren't using AdAway. Maybe this group wouldn't have trouble with that but many just want to install and go. I'm not noticed any problems with having the symlinked hosts file pointing at nothing but never tested it thoroughly and there must be some reason for the localhost entry to be in the default hosts file.
[X 2014 Android Development] rhpot1991:
The host file is typically empty, so a symlink to nowhere is the same thing. That was his logic. I'd also like to see a symlinked standard image, but I'll make my own if need be.
[X 2014 Android Development] neh4pres:
I wasn't sure of the reason to remove a bunch of things then download them all over. And I think I would lose my chrome data and bookmarks
[X 2014 Android Development] mikeoswego:
The host file is not empty but I don't know if its contents matter.
[X 2014 Android Development] mikeoswego:
You have already downloaded the newer versions of those apps. You will download the newer versions if you haven't already. You will not lose your bookmarks or other Chrome data.
[X 2014 Android Development] neh4pres:
It's cool. Don't want you to make a special build, it's not that important to me. But just thought if it didn't do anything if you didn't use it, that it could be put in every img. Which would technically reduce the images you upload by 1. Anyway, thanks for all you do for us.
[X 2014 Android Development] trimax84:
This is great! Thanks so much [MENTION=3142142]mikeos[/MENTION]wweg!
[X 2014 Android Development] jrbmed08:
Flashing this right now! I haven't had the greatest experience with AdAway, so this is perfect. Can't wait to try out 5.1 and be able to multitask again! Many thanks to you and JulesJam for the files and instructions.
[X 2014 Android Development] trimax84:
Up and running with the 5.1 Adaway debloated img. Everything seems good so far. I'll give it some time to settle in. Any app present before flashing on my device, despite being in the debloat list (YouTube, Google drive), remained. So it worked out perfectly for me.
[X 2014 Android Development] JulesJam:
Just flashed this, no problems like I was having the rooted image I made. I think the key was to delete the /data/dalvik-cache and /cache folders BEFORE flashing the MoFo image. Thanks so much for doing this [MENTION=5849464]mikeoswego[/MENTION]!!!

---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------

I see YouTube and Google Drive on mine but none of that Verizon crap like NFL Mobile and Navigator.
[X 2014 Android Development] mikeoswego:
Patch files for images

Making these images is relatively trivial for me. It is the uploading of these huge files that is a major hassle. So, I've figured out a way to create patch files for the images which will ease things immensely!

There are two files attached to this message:

rootfull-adaway.patch.zip - adds AdAway to XT1096_5.1-tether-root-bb-sqlite3.img

xposedfull-adaway.patch.zip - adds AdAway to XT1096_5.1-tether-root-bb-sqlite3-Xposedv65.img

Here is how to use these patch files:

First, you need to have the Xdelta3 program:

xdelta3 for Windows x86

xdelta3 for Windows 64-bit

xdelta3 for Linux

For windows extract the .exe file from the zip and put it into the folder where you work with your images; rename the exe to xdelta3.exe

For Linux, extract the files from the archive, enter the folder with the extracted files and run "./configure && make && make install" (without quotes.) This will install xdelta3 to your system.

Extract the patch file from the zip along with the image file from the 7zip into you working folder. Windows users should have the image, the patch file and the xdelta3 program all in the same folder. Linux users just need the image and patch file in the same folder.

For windows, enter a command prompt in your working folder. In later versions of Windows, you can click on the line showing the path and enter "cmd" (without the quotes) to open a command window in that folder. Keep in mind that you can complete the names of filenames by using the tab key.

For both Windows and Linux users enter the following cmd while in the working directory:

xdelta3 -d -s imagefile patchfile

In other words, to patch the full image with Xposed to have AdAway, your command would look like this:

xdelta3 -d -s XT1096_5.1-tether-root-bb-sqlite3-Xposedv65.img xposedfull-adaway.patch

The patched image will be created and you can then flash that like normal.

Make sure the new image is the exact same size as the original image. If a patch for another image is applied to the wrong image, there will be an error message displayed. Even if there is an error, a new file will be created but it will usually not be the same size as the original.

I've tested these patches but would appreciate feedback from others.
[X 2014 Android Development] tyleras3:
[MENTION=5849464]mikeoswego[/MENTION]

Wait, we can request imgs :D ? Is it possible to get Emoji Switcher (from the play store) working? Currently when I apply it and reboot, it only replaces some emojis (the rest are blank) and the ones that show up don't work anyway. I'm assuming it's because of write protection and a workaround like AdAway would have to be utilized.
[X 2014 Android Development] mikeoswego:
You're correct that it is the write protection issue causing the problem. With AdAway, we put the hosts file in a location that can be written to and the symlink caused the system to read it from there.

It probably would be possible to symlink the font file but there would have to be an option in the Emoji Switcher app to write to the alternate location like AdAway has.

It would be possible to place the desired emoji font file into the image and create a patch to apply the change. I don't want to have a bazillion requests, :p ,but tell me the image and which font file you want and I'll make a patch for you to test. The font files used in Emoji Switch are listed in the first post here: http://xdaforums.com/showthread.php?t=2618523
[X 2014 Android Development] RyanBRZ:
When I send a text, it gets stuck at 'SENDING... ' and never changes to the sent time. The checkbox still appears when a sent receipt comes through. Has anyone else experienced this?

Disregard, switched texting app and its working fine.
[X 2014 Android Development] tyleras3:
Wow, amazing dev, thanks! It would be the iOS emoji style and the img would be root "XT1096_5.1-tether-root-bb-sqlite3-Xposedv65-DeBloat-AdAway.img"
[X 2014 Android Development] mikeoswego:
Update method for distribution of images

I've updated Post 2.

From now on, there is going to be the base rooted 5.1 image and then a set of patch files to apply against that image. The patches are available in Post 2.

The current patch files make the following changes to the base 5.1 rooted image:

AdAway.patch - Adds AdAway support (symlink hosts to /data/data/hosts)

Debloat.patch - Removes some apps (See Post 2)

Xposed.patch - Adds Xposed to the image

Xposed-AdAway.patch - Adds Xposed & AdAway support to the image.

Xposed-Debloat - Adds Xposed, removes some apps (See Post 2)

Xposed-Debloat-Adaway - Adds Xposed & AdAway support, removes some apps
[X 2014 Android Development] mikeoswego:
Ok, your my guinea pig.. Attached is a patch file for use against the XT1096_5.1-tether-root-bb-sqlite3-Xposedv65-DeBloat-AdAway.img. Follow the instructions in the earlier post (or post 2) to apply the patch. Let us know it works!
[X 2014 Android Development] tyleras3:
Testing now, will report back!
[X 2014 Android Development] dxl880517:
Just a quick question, if I have already OTA to 5.1(which i believe the bootloader may have updated...), can I still use Mofo to flash the rooted image or do i have to wait a new version of mofo?

Thanks!
[X 2014 Android Development] tyleras3:
Sadly Mofo no longer works if you've taken the OTA because you've upgrade the bootloader which makes Mofo incompatible :c
[X 2014 Android Development] dxl880517:
Ok, noted..

Shouldn't have clicked the upgrade.. anyway, thanks for your answer!
[X 2014 Android Development] tyleras3:
Absolutely amazing, worked flawlessly. Patching was incredibly easy and straight forward, flashed without a problem, emojis are working perfectly.
[X 2014 Android Development] mikeoswego:
Excellent, thanks for the feedback!
[X 2014 Android Development] kjack999:
Wanted to report a success. I started with a stock Moto X running 4.4.4. OTA'd to 5.0. Followed the procedure in this post using mofo to try to upgrade to 5.1. I admit that I forgot to delete cache and data before I started the procedure.

During the reboot, I was getting a brief flash of the dead Android with "No Command" followed by a black screen, then the Android again, black, etc. Rebooting didn't help. Re-doing the procedure didn't help. I could still get into the bootloader, but going to recovery produced the same result (dead Android flash, then black, repeat).

I was able to recover by flashing the 5.0 OTA recovery.img. That let me get into recovery again. Then I wiped cache and did a factory reset. Flashed to 5.1 recovery, which worked! Then followed the entire procedure again. I am now happily on 5.1 with root.

Thanks for the hard work on this, looking forward to using the new phone!
[X 2014 Android Development] mikeoswego:
Thanks for your report!
[X 2014 Android Development] JulesJam:
That is what I was getting too when I was flashing my rooted image. So it looks like this occurs when you don't delete /data/dalvik-cache BEFORE you upgrade to 5.1.
[X 2014 Android Development] rhpot1991:
Same exact results for me.
[X 2014 Android Development] joshnat:
Long story, but I successfully flashed from 5.0 to 5.1 patched by the method in the OP. Things were working well for a while, but then I started having Xposed problems, where I was getting toasts saying Xposed wasn't installed. I did a factory reset and reflashed the necessary 5.1 files and then a re-patched img. Now I've got a non-functioning home button and settings is crashing and there's no pull down quick settings. Is there a way to flash to 5.1 stock (safely), then re-mofo?
[X 2014 Android Development] mikeoswego:
First, try deleting everything in /data/dalvik-cache and /cache with your root file explorer and then reboot.

If that doesn't work, mofo flash the base 5.1 image. If you can get into settings then, go into apps and uninstall the Xposed Installer app. Then, flash back to the Xposed image if you want to try it again. Then, making sure you have the correct version as listed in post 2, reinstall the Installer app, enter the app and make sure there are no modules enabled, reboot. If things continue to work, try installing modules one at a time (making sure first that all of them are supposed to be compatible with 5.1)

If your still down you could flash back to 5.0 and start all over again but what is most likely is that somehow your Xposed Installer files in data got corrupted causing problems for the Xposed framework that is in the patched mofo image.
[X 2014 Android Development] joshnat:
Thanks, Mike! I did try flashing the base image, and it didn't help with the home button on the nav bar, settings, etc. How would you suggest I flash back to 5.0? Just flash my previous mofo image?
[X 2014 Android Development] jrbmed08:
I'm also getting toast popups that xposed framework is not installed but it works just fine. Flashed with no problems but for some reason I couldn't find the /cache folder to delete before flashing so I just wiped cache from recovery. Am I doing it wrong? I did delete data/dalvik-cache.

I'm coming from TotalX if that matters. Everything else works great. Did not try a factory reset. I'll try deleting the folders and rebooting. I think I was looking in /data for the cache folder rather than the root maybe.