yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
xt1096-5.1-mofo-base-v2.img

BusyBox was not working in the new image, thanks to [MENTION=5650433]coldeadfingers[/MENTION] for pointing this out.

Changelog:

Release 3 - 07/10/2015

- Base file name: xt1096_5.1_mofo-base-v2.img
- Fix broken BusyBox installation

Release 2 - 07/09/2015

- Base file name: xt1096_5.1_mofo-base.img
- Correct security context on /system/etc/install-recovery.sh to value
in original ROM instead of value as set by SuperSU installer which
was causing script to not run at boot.
- Make AdAway support the default. Added functionality to create
/data/data/hosts file on boot, if it doesn't exist. (For users who
don't wish to use AdAway ensuring there wil be no problems in
resolving localhost for apps/processes that might use that.)
- Shorten and simplify names of base and patch files.
- Upgrade SuperSU from v2.46 to v2.49

Initial Release - 07/05/2015

- Base file name: XT1096_5.1-tether-root-bb-sqlite3.img

The new base image: xt1096-5.1-mofo-base-v2.img.7z - Base 5.1 image v2 with tether, root, busybox, sqlite3 and AdAway support

You can either download the new base image or use the base-to-base-v2 patch below to patch xt1096-5.1-mofo-base.img which will create xt1096-5.1-mofo-base-v2.img.

All future patches will be based on xt1096-5.1-mofo-base-v2.img so please keep a copy of this image.

Patches:

old-to-newbase-v2 - Use only to upgrade XT1096_5.1-tether-root-bb-sqlite3.img to xt1096-5.1-mofo-base-v2.img

base-to-base-v2 - Use only to upgrade xt1096_5.1_mofo-base.img to xt1096-5.1-mofo-base-v2.img

base-v2-to-base-v2_de - Removes some apps from base image (as listed in post 2)

base-v2-to-base-v2_xp - Adds Xposed to the image

base-v2-to-tobase-v2_xp-de - Adds Xposed, removes some apps (as listed in post 2)

base-v2-to-base-v2_xp-aa - Adds Xposed & Air Audio support

base-v2-to-base-v2_xp-de-aa - Adds Xposed & Air Audio, removes some apps

base-v2-to-base-v2_xp-de-em - Adds Xposed & iOS Emojis, removes some apps
[X 2014 Android Development] jrbmed08:
I'm currently running one of your first set of 5.1 images (tether, root, xposed, bb, sqlite but no adaway or debloat). Working great by the way. Am I correct in assuming I just have to mofo flash your latest base image and I'll have your latest bug fixes plus adaway?
[X 2014 Android Development] RyanBRZ:
Trying to patch with all files in c:\patch folder.
[X 2014 Android Development] Pizzuto:
Unzip image and unzip patch, even though they are already .img they need unzipping! unzip delta and rename!
[X 2014 Android Development] RyanBRZ:
Do you mean unzip again? Both files were extracted from a 7z already and why would he not include this in the instructions?
[X 2014 Android Development] mikeoswego:
You need to first patch base-to-base-v2 patch onto xt1096-5.1-mofo-base.img which will the xt1096-5.1-mofo-base-v2.img.

Then flash base-v2-to-base-v2_xp onto the xt1096-5.1-mofo-base-v2.img image.
[X 2014 Android Development] RyanBRZ:
Thanks. This is safe to do in regards to not losing my mofo patcher, right? I think I read on a previous post that if the bootloader gets overwritten, mofo will not recognize the phone as a paid device.
[X 2014 Android Development] mikeoswego:
I'll definitely update as new versions of Xposed are released. Alpha 4 was just released on the 30th. That one fixed a problem in alpha 3 that was released on the 26th. Alpha 2 was March 8th and the first alpha was February 13. I wouldn't be surprised to see a month or more go by before the next release of Xposed.

As for feature requests, I haven't thought that far ahead. The idea of symlinking various things sounds like it has some merit but would add complication in that there would have to be another set of files for people to download and place in /data to fully set it up. Without a custom recovery that can't be easily automated so people might have to manually set ownership, permissions, etc. and many have trouble with that sort of thing.
[X 2014 Android Development] Haxxa:
Yes, certainly it will be a challenge as people would expect to just copy and paste a file - linux permissions may be a lot for people to grasp and furthermore given its data partition and it would be easy to delete file by mistake. Finally it might cause instability if the system cannot find a particular vital file i.e if Build.prop suddenly goes missing. Still I reckon the benefits outweigh the downsides, rooting a device is not for the weak of heart and as long as this is outlined clearly, I think it will be fine. Regardless depends on what direction you would like to take this Rom now, in any case- Thanks for your work, a kid in Australia now has a phone hes happy with ;)
[X 2014 Android Development] Legacystar:
Is there an xposed module that enables USB otg write access. As it stands now we can view thumb drives but can't write to them
[X 2014 Android Development] JulesJam:
But as long as you can get into bootloader mode and have the fxz, you can flash back to stock.
[X 2014 Android Development] Haxxa:
Try Stickmount : https://play.google.com/store/apps/details?id=eu.chainfire.stickmount&hl=en
[X 2014 Android Development] Legacystar:
Ya I guess that is an option. Its kind of janky compared to the integrated option.
[X 2014 Android Development] GatorsUF:
I installed this IMG and it boys fine, but when I try to run gravity box lp it says
[X 2014 Android Development] GatorsUF:
Disregard the last post, a reboot fixed it.
[X 2014 Android Development] mikeoswego:
ES File Explorer writes to my USB without any problem.
[X 2014 Android Development] Haxxa:
^^ This just used ES on my Phone and worked well. Thanks :)
[X 2014 Android Development] tjohnstone3:
Yeah, I know for sure I don't have it...I downloaded the image around 9:45 central time yesterday which I think was after you posted but perhaps I jumped the gun (XT1096_5.0_LXE22.46.11_rooted-sqlite3-busybox-Xposed.rar is the file I downloaded).

Quick question, will flashing a new image with xposed force me to re-apply any xposed module changes I've made?

Thanks for your work on this!
[X 2014 Android Development] mikeoswego:
Yeah, I copied the post from the other thread and thought I changed the link to point to the newest file but it didn't stick (or I forgot to save it out.) :p

Your Xposed config is saved in /data as are the modules you've installed. Updating the image in /system via mofo won't affect the Xposed modules or the settings you've made for individual modules.
[X 2014 Android Development] fakieskr8333:
Hey could you replace the status icons with the AOSP ones? I hate to Verizon LTE icon and can't find a module that will change it.
[X 2014 Android Development] mdmogren:
Thank you!

First of all, I just wanted to say thanks for creating this image!

I have been staying on 4.4.4 until now for 2 reasons.

1) Heads up notifications.

Heads up sucks for just about everything but phone calls. They are intrusive and ruin everything that was wonderful and elegant about android notifications. Google copied Apple here, when they really really shouldn't have. This image has allowed me to use this Xposed module: http://repo.xposed.info/module/com.mohammadag.enablenotificationtickeronlollipop It works great, highly recommended to everyone. Even if you don't realize you need it, trust me, you do.

2) That damn memory leak. I know it's not totally fixed in this image yet, I have added the Xposed module that seems like possibly a partial fix, I'm not sure if it does anything, but I understand that it has been fixed in the latest CM 12.1 nightly, so I am confident that an image will come soon enough with a fix and I won't be stuck with this horrible annoyance of rebooting every 12 hours forever (I listen to a lot of audiobooks and podcasts, and this leak is especially bad for me)

A few other things to note:

-If this is your first time flashing a mofo image, until you delete the two folders from dalvic cache, your phone will run like garbage and even deleting them is a pain/very slow. I had to turn SuperSU default to "Grant" since I wasn't getting prompted, delete the folders, after rebooting and a long wait for app optimization everything was good and I could move back to "prompt" with no problem.

-Some xposed modules work (Ticker notifications, app settings), others seem not to (Youtube Background Playback, EDIT: Power Menu does work! I just didn't realize you have to hit "power down" before you see the options) I'm guessing some of them need to write to system.

If you have been on the fence about spending the $20, I'd say go for it! The advantages are big enough and you don't even lose any of your apps, data, settings, or anything at all as far as I can tell (of course do a backup of the stuff you really care about just in case) so this is very low risk and costs less than 2 fancy cocktails.

---------- Post added at 01:05 PM ---------- Previous post was at 12:52 PM ----------

mikeoswego do you have a tip jar? Bitcoin or Paypal?
[X 2014 Android Development] tacosrdelicioso:
I second this I want them so bad
[X 2014 Android Development] mikeoswego:
There is an Xposed module called SignalIconsAOSP that works to change the icon. It changes the signal strength meter to the smooth AOSP look and defaults to showing 4G when connected at that speed. You can set it show LTE instead. I think this is probably what you are looking for.
[X 2014 Android Development] mikeoswego:
Hopefully there will soon be a way to unlock the bootloader and then we can use CM or other ROMS if we want!

It is known that many modules don't work yet on the alpha version of Xposed for Lollipop. Some of those module devs are probably waiting for a non-alpha/beta version to come out before re-working their modules.

No, I don't have a tip jar but thanks for the thought. Really, though, it is [MENTION=2278321]btdownloads7[/MENTION] who deserves something; he is the one who came up with the original images that convinced me to give mofo a try and a base for me to work with in adding in Xposed!
[X 2014 Android Development] tacosrdelicioso:
About the memory leak there's an xposed module that fixes one of the big ones

---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------

I also can't find the signaliconsaosp module. I find the aosp signal icons module but that is old
[X 2014 Android Development] mikeoswego:
I found it by downloading it from within the Xposed installer.
[X 2014 Android Development] tacosrdelicioso:
Not showing up here
[X 2014 Android Development] mikeoswego:
All these patches do is patch the base system image for use with mofo to one with more features (or the first two in the list patch previous versions of the base to the current v2 version.)

If you have not already upgraded from Android 5.0 to 5.1, you need to follow the instructions in post 2, these patches are all for 5.1 images.
[X 2014 Android Development] RyanBRZ:
Yes, I was already running 5.1. Thank you for the support and all of your work! I was able to patch the image. You should add this detail to your how-to.
[X 2014 Android Development] mikeoswego:
You will not have AdAway, only support for it. You need to patch your base image up to xt1096-5.1-mofo-base-v2.img before using the next patch to add Xposed. Which patch(es) you need are determined by what you have on your system now.
[X 2014 Android Development] jrbmed08:
Hmm, I'm completely lost with all this patching stuff. I'm fine without adaway (it blocks too many Google links anyway) but just want xposed, which I already have in my current image. Maybe I'll just stay on that for now. Unless someone writes a noob guide about patching.
[X 2014 Android Development] mikeoswego:
Here is what is in post 2 at the moment. If you could say where you're getting lost it be helpful for writing that noob guide.
[X 2014 Android Development] gunit25:
Good morning,

I flashed this image yesterday ( previously on total x). Followed the instructions, deleted cache, flashed files for 5.1 and then used mofo to flash the image.

My battery life has been awful. I will post pictures once my phone is back up, but Android OS sucked up 10% of my battery. When I check battery life, it appears the phone is awake almost all the time, without screen on. I did not have this problem on total x.

Anyone else experiencing this or have any clues for fixes?

http://imgur.com/iQsL0tE

http://imgur.com/CpQfTHC
[X 2014 Android Development] Aroch925:
Can you make better battery stats a system app by any chance? or does it need to be added to the .img?
[X 2014 Android Development] jrbmed08:
Thanks, actually I hadn't seen your updated post #2 and had no idea what to do with the patches. This explains a lot and is the noob guide I'm looking for. So since I'm running the older base image with xposed (but not debloat, airaudio, emoji, etc), I should just have to apply the xposed patch and then flash? And then if I want adaway, install it and change the hosts file as you described earlier.

The problem now is that even after following your instructions on where to install xdelta3.exe, I can't get it to work. I double-click on it and it opens for like a fraction of a second, puts up some text too fast to read, and closes itself. I'm using the 64 bit windows version on a 64 bit AMD laptop., Any idea what is going on? And if I can't make the patch work, any way you could upload the patched image with xposed?

Thanks again for all you've done for us, by the way.
[X 2014 Android Development] drewski_1:
Don't double click on Xdelta3. Run it from the command prompt.

Navigate to the directory, and type the whole line per the Post #2 ('xdelta base patch')

Sent from my Lollipop TF700T
[X 2014 Android Development] mikeoswego:
I'm working on a new version that I'll post for beta testing later. I'll add Better Battery Stats XDA edition to it.
[X 2014 Android Development] mikeoswego:
It depends on what image you have right now:

If you have XT1096_5.1-tether-root-bb-sqlite3.img, you would xdelta the old-to-newbase-v2.patch file to create the latest base image, xt1096-5.1-mofo-base-v2.img

If you have xt1096_5.1_mofo-base.img you would xdelta the base-to-base-v2.patch file to create the latest base image, xt1096-5.1-mofo-base-v2.img

Once you have xt1096-5.1-mofo-base-v2.img (or if you already have it),then you would xdelta the patch for the version you want. If you wanted the latest version with Xposed you would enter this command:

xdelta3 -d -s xt1096-5.1-mofo-base-v2.img base-v2-to-base-v2_xp.patch

This would create the file xt1096-5.1-mofo-base-v2_xp.img and you would flash that with mofo.

If you wanted the latest version debloated and with Xposed, you would enter this command:

xdelta3 -d -s xt1096-5.1-mofo-base-v2.img base-v2-to-base-v2_xp-de.patch

This would create the file xt1096-5.1-mofo-base-v2_xp-de.img and you would flash that with mofo.

Except for the patches that update one base version to another, the patches always apply to the base image, not one that has already been patched (unless specifically stated otherwise.)

And for AdAway, you are correct, download the apk, install it on your phone, go into the AdAway settings and change the location of the hosts file.

I think I'll create some batch files that will automate some or all of the process of patching and flashing.
[X 2014 Android Development] mikeoswego:
I presume that you also deleted everything in /data/dalvik-cache?

I've been happy with the battery life. In the attached screen shots, the steep drops are when tether was on.
[X 2014 Android Development] gunit25:
I did delete everything. I did a total battery drain and it looks like it's going better currently (I also froze ad-away).

Will keep you posted.
[X 2014 Android Development] Aroch925:
Is that gonna be the 5.0 version or the 5.1 version?
[X 2014 Android Development] mikeoswego:
5.1, 5.0 is old news!
[X 2014 Android Development] jrbmed08:
Thanks. Wouldn't it just be easier to download the new base and patch it for xposed rather than patch my current image twice though? Or is there something I'm missing?

An automated process would be awesome. Especially considering xdelta3 isn't playing well with my system. Another consideration would be to add xposed to the base image since I can't imagine there are many people who don't want it. For a lot of us, xposed is the whole point of rooting.
[X 2014 Android Development] Aroch925:
This is probably a really stupid question but in the instructions for 5.1 it says to type in the listed fastboot commands. Where am I typing these in?
[X 2014 Android Development] mikeoswego:
Using xdelta to patch an older base to the newest one takes a couple seconds. This is not image or audio editing where you lose something each time you edit, nothing is lost in the patch process. Downloading the newest base at 1.2 Gb takes however long with your connection speed and consumes lots of bandwidth. That part is up to you.

Some people just want root for programs like CallRecorder by skavelex, to freeze apps in Titanium Backup, etc. and don't want Xposed. Yes, it would be possible to have the base with Xposed and then have a patch to remove it.

The new batch file setup will look and see what base you have (if any.) Patch that to the current one if needed. Run the patch to create the version you want. Run mofo for you if you want.

I can't spend the time on tether to upload all these full images. If someone calls or texts, the upload aborts. I can't leave my house. When conditions are good, it takes 15-20 minutes for each image. I'm not going to spend 2 hours or more on a regular basis uploading all the various images. Where the full set of patches is just a little over 30 mb and trivial to deal with. If someone else wants to post the various versions of the patched images somewhere, that is fine with me.
[X 2014 Android Development] mikeoswego:
Put all the files into the same folder where you run mofo from. Open a command window window in that folder and type in each command there.

I could add the upgrade from 5.0 to 5.1 process to the new batch file to automate that process without to much extra effort if that would be helpful.
[X 2014 Android Development] RashaMatt:
I've been running 5.1 for a few days now, everything is pretty much working as it should.

But I am getting one or two spontaneous soft reboots per day.

Any suggestions on how I could capture helpful diagnostic info about the reboots, to share here?
[X 2014 Android Development] mikeoswego:
After one of the reboots, see if there is a file /proc/last_kmsg. (There are a lot of folders in /proc, so you have to scroll down quite a ways.) If so, copy it to your downloads folder and you can examine and/or upload it.
[X 2014 Android Development] Aroch925:
yeah that would be really helpful if it's not too much trouble. I'm new to this so this is kinda confusing to me
[X 2014 Android Development] jrbmed08:
Oh no worries, you've already gone above and beyond to help us out. I understand why uploading patches is better for you than uploading images; it's just frustrating that I can't seem to make the patching program work. I'll try another computer. (Edit: Rebooted and got it to work!)

I had actually already downloaded the new base when I asked about doing that vs patching the old image twice. Makes sense to just patch the old one if you haven't downloaded the new one yet.

---------- Post added at 09:14 PM ---------- Previous post was at 09:04 PM ----------

I just used mofo to type them in. I opened mofo, did the commands first for the base files, then mofo flashed the image. For me that was easier than opening a command window and then mofo.
[X 2014 Android Development] jeremy702:
Does alogcat not work in 5.x roms? Since finally getting root I went to check out something and noticed that it doesnt read any logs. that and an odd Bluetooth error are the only problems o have right now. great work Mike.
[X 2014 Android Development] mikeoswego:
It looks like aLogcat hasn't been updated since 2012. Maybe try Catlog which has been updated this year. My Jawbone, LG headset and OBDII reader are working well with the 5.1 Bluetooth.
[X 2014 Android Development] Aroch925:
I just used mofo to type them in. I opened mofo, did the commands first for the base files, then mofo flashed the image. For me that was easier than opening a command window and then mofo.[/QUOTE]

But when i tried to enter the fastboot commands it said "fastboot" is a not a recognized as an internal or external command
[X 2014 Android Development] Aroch925:
But when i tried to enter the fastboot commands it said "fastboot" is a not a recognized as an internal or external command[/QUOTE]

nevermind. I figured it out
[X 2014 Android Development] Aroch925:
I flashed the original 5.1 image onto my phone and the went fine, but when i went to flash a patched image, mofo just working. It just shows the version number and nothing else. Any ideas on whats wrong?
[X 2014 Android Development] mikeoswego:
Try unplugging the USB cable and plugging it back in when that happens.
[X 2014 Android Development] RadOD1:
In the middle of upgrading from 5.0 and mofo is not detecting my device.

First I did this stuff:

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot flash recovery recovery.img

All successful. Then patched 5.1 img with xdelta3, no problem.

Went to run mofo on patched img and I get "no devices found, must be in fastboot" which I am.

fastboot devices returns xxxxxxxx fastboot so I am in fastboot mode. Android screen says USB connected. Done the mofo thing before with no driver problems or anything.

Anyone have an idea why mofo can't see my device?

---------- Post added at 08:05 PM ---------- Previous post was at 08:03 PM ----------

PS - I tried that too

---------- Post added at 08:20 PM ---------- Previous post was at 08:05 PM ----------

PPS: Python still installed and in PATH

E:\mofo\windows>mofo
version: 0.0.3

No devices found. Device must be in Fastboot mode.

To enter Fastboot:

adb reboot bootloader

or

Hold down the power and volume-down buttons together while
turning on the phone.

E:\mofo\windows>python
Python 2.7.9 (default, Dec 10 2014, 12:24:55) [MSC v.1500 32 bit (Intel)] on win
32
Type "help", "copyright", "credits" or "license" for more information.
>>>
[X 2014 Android Development] mikeoswego:
You've probably already tried rebooting your computer? If so, then try powering down the phone as well and starting it up again in bootloader mode.
[X 2014 Android Development] RadOD1:
Rebooted the computer. No help.

Shut down and started in bootloader mode. Still not detected.

(Also, did delete /data/dalvik-cache and /cache first, if it matters)

Here's the urgent question: I flashed boot.img, NON-HLOS.bin, fsg.mbn, etc... What happens if I reboot into Android rather than bootloader? Am I in some sort of halfway state beween 5.0 and 5.1 thats going to lock up my phone?

---------- Post added at 09:08 PM ---------- Previous post was at 09:01 PM ----------

Changed USB ports on PC. Flashing. Damn!
[X 2014 Android Development] mikeoswego:
Crazy windows drivers! Glad you got it working!
[X 2014 Android Development] jeremy702:
Hey.. nice suggestion, thanks. I hadn't had root for a year or two and never thought to check for a new tool. Logs are coming in great.

As for the BT, it seems to drop my connections after a period of time and seems to be picking about bringing them up again. I'll do some more testing.

Thanks again for the hard work.
[X 2014 Android Development] amd_h4x0r:
this might be a dumb question, but what is preventing us from using a system.img from a custom rom? couldn't someone with an unlocked XT1095 on Verizon dump a system.img while running a custom rom?
[X 2014 Android Development] Aroch925:
I'm trying to change my boot animation, and I did everything the 5.1 post said except when I try to change the owner and group options, there's no option for u0_a40 for either of them. It was just skips from u0_a39 to u0_a41