yashsingh1/xdaforums huggingface dataset:
[X 2014 General] JulesJam:
Someone would have to make it in ext4 file format and it would need to be re-sized for the XT1096's system partition. The Pure Edition has a different sized system partition from the XT1096.
[X 2014 General] JulesJam:
Like I said, I am sure btdownloads7 had to make that first so he may have a copy of it. People here are volunteers so they can make the images any way they want and don't have to post them if they do. But if you ask him, he may be able to hook you up with what you want.
[X 2014 General] Haxxa:
Thanks for the image seems to be working well, Unfortunately though it still has the stock Verizon Boot Animation :(
[X 2014 General] JulesJam:
Would it be possible to have a symlink where the bootanimation would be stored such that the symlink pointed to the bootanimation on the data partition. That way you could change the bootanimation any time you wanted by changing it on the data partition.
[X 2014 General] Haxxa:
Yes, that sounds like a great idea, really it would be fantastic to have a folder containing build.prop, boot animation and everything else useful that is modified by root say have a folder layout like this - Data>Root-Control>(Boot Animation , Hosts File , Build.prop , Mods , Fonts). That way people can modify it at will. :D
[X 2014 General] trimax84:
Now we're thinking!

Does that mean that you have offered to take the Root/BB/SQL/AdAway/Xposed ROM and make these changes?! ;)
[X 2014 General] JulesJam:
It would constructively disable write protection :D
[X 2014 General] Haxxa:
Unfortunately my Linux knowledge is not the best and when dealing with SELINUX I have had difficulties, I honestly would but I have not created one successful image yet :/ however given the supportive nature of the community so far, I think maybe someone else may volunteer who is able to create a few symlinks and call it a day :) No guarantees, but heres hoping :) In fact it would be no harder than what has been done already in terms of creating images.
[X 2014 General] Slack3r:
Some things early in the boot process like boot animations may not work depending on when the kernel mounts external partitions (I believe it's the init process), but there's only one way to find out :)
[X 2014 General] Haxxa:
Good Point. He's hoping the kernel mounts /data first and can load up the bootanimation :)
[X 2014 General] trimax84:
Confirmed AdAway working, which leads to a better browsing experience and faster page loads. Thanks!
[X 2014 General] tacosrdelicioso:
What did you use for the status bar icons and signal bars??
[X 2014 General] trimax84:
A combination of GravityBox and Flat style Bars Indicators....
[X 2014 General] btdownloads7:
So, you're not crazy - there is definitely a problem with the bootanimation in the last system image that I posted. I'm not sure how it's even possible for it to get messed up, but I can easily change it in the unrooted image that I created, but as soon as I made SuperSU work, pushing new boot animation causes the black Android boot animation come up. I'll try to figure out what's happening, and post a fixed image when I figure it out.
[X 2014 General] JulesJam:
What about the symlink idea? Is that an option?
[X 2014 General] btdownloads7:
Without knowing why it isn't working, no. The problem isn't that we can't set up the correct bootanimation, but that the phone isn't using it with the rooted image (which it does fine before I added root to it, and my original rooted image also worked fine). So, I probably messed something up when re-creating the image, and I'm looking into it now.

Symlinking bootanimation to the data partition will make it much easier to change the boot animation later, though, because you won't need to modify the system image. But I don't think it'll work because boot animation is the first thing to run, and I'm pretty sure that's way before the data partition gets mounted.
[X 2014 General] JulesJam:
Ok, thanks!
[X 2014 General] mikeoswego:
I did nothing special when I took your image and after installing Xposed copied the 5.1 bootanimation.zip file into the image and it is working fine. I actually just used Nautilus to copy/replace over the original and didn't have to change any permissions, ownership, etc. (Though I did check them from a terminal.) I dual boot Win7 and Ubuntu 14.04 rather than a VM setup.
[X 2014 General] btdownloads7:
I can't explain that at all. I have my own custom boot image that I used on the old rooted image (with the broken HDR), but when I tried to load it onto the new image that I posted, all I got was the black Android animation. Haxa had the same problem (and before I tried it myself, I thought that he was doing something wrong). I have absolutely no explanation of how you were wble to get it working on the same image.

I've basically been rebuilding all of my incremental images to see where the problem started, and so far, the tethered-unrooted and tethered-rooted images are fine, I can change boot animation on those without any issues. So it has to be a problem with the final image, where I added busybox and sqlite3. I'm rebuilding it now, and hopefully, it won't have any problems.

Also, as a side note, I did test symlinking bootanimation.zip to the data partition (on an image where it works if I just replace the zip), and that doesn't work.
[X 2014 General] JulesJam:
There was a poster who was requesting this image if you can upload it somewhere to be downloaded. They didn't want BB or SQLite, but did want an image w/o the HDR camera bug.
[X 2014 General] btdownloads7:
I just finished testing the new image (root, tether, busybox, sqlite3), and it has no problem with changing boot animations. So, I'm uploading it now, and I've already uploaded the rooted-tether image. Once this one is finished uploading, I'll start a thread in the dev forum (as maiko1 asked) with the links to both images.
[X 2014 General] mikeoswego:
I noticed that the bootanimation.zip and bootanimation-encrypted.zip have different resolutions. The bootanimation.zip is 1080x1920 and bootanimation-encrypted is 720x1280.

The 5.1 demo bootanimation.zip that I put in is 1080X1920 like the original. Just wondering if you are trying an animation with a different resolution and if that would cause a problem.
[X 2014 General] JulesJam:
With my MX13, when I was changing the logo.bin to get rid of the bootloader unlocked screen, if you flashed one with a different resolution from the one for the Verizon XT1060, it wouldn't load - it was as if you hadn't flashed it.
[X 2014 General] btdownloads7:
That's possible, but it still doesn't explain why it worked on the image before I loaded busybox, but not after. And once I rebuild thjat image, bootanimation works fine on it. I have 2 different version of my bootanimation -- one that's purely 1280x720, which works, but doesn't fill the whole screen, and another one that's exactly the same, but the desc.txt file in it has the resolution changed to 1920x1280 (without changing the actual images). And that works perfectly as well, it just stretches the animation to fill the screen.

---------- Post added at 01:31 AM ---------- Previous post was at 12:41 AM ----------

I started a thread in the dev forum, which is where I'll be posting any updated system images. There are currently 2 links there, with updated versions of the rooted & tether image and rooted, tether, busybox, and sqlite3 image.
[X 2014 General] Haxxa:
OMG you don't know how frustrating that conversation last night was I was absolutely certain I was doing everything right and I was getting really annoyed it didn't work, anyway glad to here it wasn't just me. I gave up on making Images based of the knowledge I might have being messing something up... Now I might go back to making them again knowing, I wasn't causing Issue...
[X 2014 General] en_pneumati@netzero.net:
THANK YOU SO MUCH! i really appreciate the extra effort.
[X 2014 General] IkeBiker:
Hey is this based off of Maiko's image with the new boot animation?
[X 2014 General] tjohnstone3:
So I would enjoy getting AdAway but I have a quick question.

I'm currently running a version w/ xPosed installed and I've got a bunch of mods already made. I'd prefer NOT to redo them (but will if I need to). If I flash this image w/ AdAway supported will I need to reapply all of my xPosed module changes?

Want to edit to say thanks to all of you for your hard work, it's great having all of these features back that I thought would be gone.
[X 2014 General] ClydeDroid:
Nope, sorry, still stock :( I could try to redo the image with the new boot animation if people are interested.

Nope! I flashed it with Xposed modules already installed and my settings were retained :)
[X 2014 General] IkeBiker:
If you could it would be awesome, if that's not too much
[X 2014 General] JulesJam:
How do you do this?
[X 2014 General] JulesJam:
mofo.exe only flashes the system partition. All of your Xposed modules, apps and settings are stored on the data partition so those don't get overwritten when you flash a new system partition.
[X 2014 General] JulesJam:
maiko1 didn't make any images. Mikeoswego made the image with the new boot animation.
[X 2014 General] joshnat:
I would love that too. Let us know if you think you can do it. Thanks for all your work!
[X 2014 General] ClydeDroid:
Open Preferences in AdAway, scroll down to "Target hosts file," and select /data/data/hosts. Be sure to reapply after that and reboot.

Just built an image that has everything my last image had plus the new boot animation and Google Dialer since [MENTION=3391399]TokedUp[/MENTION] wanted it. Testing now, will upload if it works!
[X 2014 General] Twistitup:
You are awesome. I'd kiss you if I could. :P
[X 2014 General] ClydeDroid:
Can't seem to get the Dialer working. Trying to figure out how to alter system apps in an image, is just copying the apk over not enough?
[X 2014 General] mikeoswego:
I haven't tried with the 5.0 image to add the Google dialer but remember it didn't work right with 4.4.4 on the 2013 Moto X. Also, I think the Google dialer everybody talks about adding is just the outgoing dialer, it isn't the Google incoming UI with Open White Pages Caller ID, etc. (Of course, Verizon wants us to pay monthly for their Caller ID service. so they don't include that as a default.)

I'll be glad to be proven wrong about any of this, though!
[X 2014 General] GatorsUF:
I would think that the nexus 6 dialer should work if anything.
[X 2014 General] Twistitup:
Thank you everyone for the hard work. Xposed is the bomb.com!
[X 2014 General] TokedUp:
Yes by google dialer I mean working search feature built in without a FC when choosing the number
[X 2014 General] Haxxa:
Interesting Question: Given that the changelogs have appeared for the AT&T version for the Moto X (Gen 2) its highly likely over the next month or so, the Verizon model will too receive an update - When this comes out we should still be able to modify the Image Motorola releases but 2 questions remain... Will a updated bootloader be required to boot the image? And will the 5.1 Update patch the bootloader exploit for new MOFO Users? Thoughts?
[X 2014 General] JulesJam:
IME with MX13, you can update everything BUT the BL and partition table and it will all still work.

Given that we don't know what the exploit is, it is hard to say. BUT since 5.1 has been out since March and MoFo was released after 5.1, there is no way that Motorola could have targeted the exploit. Of course it could have coincidentally been patched. Seems unlikely though as I am sure that the 5.1 upgrade is targeting the memory leak and bringing HD calling to the phones - not securing the BL.
[X 2014 General] ClydeDroid:
Got my image to flash! New bootanimation and Dialer working :) uploading it now!
[X 2014 General] trimax84:
Even if 5.1 patches the exploit (unlikely), we should all be able to stay on 5.0 and then flash 5.1 images. From my Droid Incredible to my Moto X 2013, a slight variation on bootloader version hasn't effected being able to load an updated ROM.

The problem would be, if the exploit is patched and then you take the OTA upgrade... So I recommend everyone blocking or not accepting any updates going forward until reports of MoFo success are reported.

And thanks Clyde!
[X 2014 General] ClydeDroid:
Here's the thread for my new image: http://xdaforums.com/moto-x-2014/development/img-totalx-root-tether-busybox-sqlite-t3101853

Hope y'all like it!
[X 2014 General] frozex:
great!!!
[X 2014 General] JulesJam:
[MENTION=5697730]maiko1[/MENTION] - can you please add ClydeDroid's thread to the OP of the MoFo thread? Thanks!!!!!
[X 2014 General] IkeBiker:
Amazing Job!
[X 2014 General] maiko1:
Added.
[X 2014 General] IkeBiker:
hey this img is amazing but the lag im getting is killing me
[X 2014 General] JulesJam:
did you uninstall the gapps updates, reboot then reinstall them?
[X 2014 General] en_pneumati@netzero.net:
i got around to flashing the "just pre-rooted and tether" img that btdownloads7 made and posted http://xdaforums.com/moto-x-2014/development/img-xt1096-victara-lollipop-images-mofo-t3100601

sad to say, when i turn on HDR function of camera, i get the same "unfortunately the Camera has stopped" error and a FC. camera seems to take the first photo in the exposure set (and saves it), then FC's while taking the second photo.

for TiBU, when i navigate to Menu>About> and click on Titanium Track support team link, it still gives a FC error, too. i tried uninstalling and re-installing and still get same error. I am using the free version of TiBU. does anyone else get this error on the free version?

but i'm still lovin' the wifi hotspot, so thanks again!!!!! :D

-mark
[X 2014 General] a1exus:
Did you do clear cache?
[X 2014 General] en_pneumati@netzero.net:
yep, first thing i did before full normal boot up

i just wiped cache again... still FC in camera HDR mode
[X 2014 General] a1exus:
I wonder why this is happening, can you check your catlog?
[X 2014 General] JulesJam:
I would delete the camera data, then uninstall the camera app update then reinstall it.
[X 2014 General] IkeBiker:
No I didn't, but my phone is snapping back to normal thanks for the advice though, you're always helpful lol
[X 2014 General] en_pneumati@netzero.net:
thanks. just tried this. still no difference. in HDR mode, it snaps first capture, then freezes on the second capture before FC.

i am using Camera ver 5.0.11.7... it is just listed as Camera, but i had to search Motorola Camera to find it in the Play Store

i can likely live without the HDR function, but it concerns me that there may be some deeper issue at play...
[X 2014 General] JulesJam:
I will flash it later today and see what happens for me.
[X 2014 General] GatorsUF:
So with Moto announcing 5.1 for the MotoX it begs a few questions....and I am well aware that we (vzw) might not see it for another couple months.

What happens if the OTA comes with a new bootloader or something? Can we get the OTA still? I assume there is a risk that they patched the Mofo exploit...
[X 2014 General] Haxxa:
Refer to Page 55 - we had a brief discussion on this.
[X 2014 General] trimax84:
That crazy boot image was too much for me. Too busy, too bright, too intense!

So I modified Clyde's ROM that he posted here with the following edits....

Changed boot animation to this:

Credit to [MENTION=4542140]raishiro[/MENTION] here for a ton of great bootanimations.

Few mods on the build.prop for some mild performance/battery enhancements:

windowsmgt.max_events_per_sec=150

ro.telephony.call_ring.delay=0

wifi.supplicant_scan_interval=200

ro.HOME_APP_ADJ=1

debugtool.anrhistory=0

profiler.debugmonitor=false

profile.launch=false

profiler.hung.dempdobugreport=false

ro.config.nocheckin=1

ring.delay=0

ro.ril.enable.amr.wideband=1

Because it is basically just a lightly moddified version of [MENTION=2821926]ClydeDroid[/MENTION] excellent image, it maintains root, Xposed, AdAway (/data/data symlink) adblocker, busybox, tether, Google Dialer, and SQLite3.

Download Link: Here
[X 2014 General] Caketray:
So no one's had any luck symlinking the boot animation?
[X 2014 General] IkeBiker:
Thanks for the update! My phone is running smoother already. Would you mind making this image with the gif below from raishiro?
[X 2014 General] koftheworld:
Anyone try http://www.kingroot.net
[X 2014 General] na2rboy:
I just downloaded kingroot, ran it, and got root. I lost root at reboot. I can't read any Chinese language so I don't know what is going on with it. Will keep messing around with it. Moto X 2014, Verizon.
[X 2014 General] na2rboy:
Upon reboot and re-root, started getting force closes. Rebooted and I was bricked. Had to reflash stock images. :(
[X 2014 General] JulesJam:
Not sure what you did wrong, but I wrote up a noob guide here:

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375

You should always wipe cache after flashing a new system image.
[X 2014 General] na2rboy:
Sorry for not being clear, I was talking about using rootking. And I did wipe cache. :)
[X 2014 General] JulesJam:
Ok well this is a MoFo thread, if you want to discuss kingroot, please start a new thread. Thanks!
[X 2014 General] IkeBiker:
My phone is still being a little buggy, you think if i restore to factory and flash all this over it'll go smoother?

---------- Post added at 12:57 PM ---------- Previous post was at 12:50 PM ----------

I just mmean if i restor to stock factory without flashing a stock image will i have to the the whole xposed process again?
[X 2014 General] JulesJam:
I would flash back to stock, wipe cache, check to see the bugs are gone and then start the whole MoFo process over.
[X 2014 General] neh4pres:
So what does this mean for us when tying to use a root app?
[X 2014 General] JulesJam:
As long as the root app doesn't need to write to system it will work fine. If it needs to write to system, like AdAway with its host files, a symlink may work to deal with that.

Also, as someone else has suggested on another thread, it may be possible to remount the system and then make changes to system while running Android. Then have a script save those changes to the data partition on power down. Then on power up, the script can remount system and rewrite the changes.
[X 2014 General] TokedUp:
I have some questions I hope someone can answer. With this method can I:

1) Install Google Dialer with search feature. It needs to be in system/app

2) Remove bloat and unwanted apps.

3) Enable notification light

TIA
[X 2014 General] Slack3r:
I'm going to attempt to build a rooted system.img based on the instructions in the SuperSU update binary, will send it to JulesJam for testing afterwards.

The first two are almost definitely possible, the notification light may be difficult though as IIRC it's only accessible by the system firmware and not the kernel. If it's been done on the pure edition though then it should be possible to use the same method.
[X 2014 General] slogar25:
Yes you can remove the bloat, Google dialer most likely but you may have to add the support libs in their proper places and not sure about the notification light. And all of this has to be baked in the image before you flash it.
[X 2014 General] trimax84:
The green led could potentially be controlled, although it's functionality is like limited much like it was on the 2013 X.

See this post to get started: http://xdaforums.com/showpost.php?p=55779644&postcount=8

Tasker integration for led: https://youtu.be/V90bFkEq92I
[X 2014 General] en_pneumati@netzero.net:
i am so glad to see this root, even for KK moving forward with custom images being built.

i do have a question, though. i keep seeing people mention you have to use Titanium BU to turn of OTA upgrade to LP?

in my case, i bought the phone and it came with KK. and soon as it was tunred on, it strted to download the LP update and gave me a notification that an update was ready.

i just went to Apps in settings and forced stopped the MotoOTA app and no update happened. if i go to Settings>About Phone>System Updates is says a system update is available, but otherwise has not completed the download to triggered nag screen to uodate.

am i missing something? or could it be that since i have also not fully powered down my phone and rebooted sinced i first turned the phone on back in January, that the updater app is just waiting to pop back into action on reboot?

if the latter is true, does the system still ASK you if you want to update, or will it complete the download and install without asking?
[X 2014 General] JulesJam:
I don't know that you have to do it with Ti B/U, I just know you can do it with Ti B/U. It is what I am used to doing so that is why I did it that way.

gtk! Thanks!

Maybe someone else can answer this as idk. I wasn't using my Moto X 2014 due to no root so I didn't try to research how to stop the OTA.
[X 2014 General] trimax84:
You can decide whether to install or not after it is completely downloaded. It will not install the OTA update without your permission. And if it starts to install, hold POWER + Vol Dwn to reboot your device and disrupt the install. Sounds dangerous, but worked for me...
[X 2014 General] joshnat:
Hey Slack3r, sounds like your 5.0 image is working. Can you share?
[X 2014 General] Interflop:
So with this root would I be able to install something like Viper4Android?
[X 2014 General] Slack3r:
I was referring to what would be possible with a rooted image, not saying that I had made a working one. I built one and sent it to JulesJam for testing but I'm not sure if it will work given the complexity of embedding root and my lack of experience doing anything like this.
[X 2014 General] trimax84:
[MENTION=5983610]JulesJam[/MENTION] - I attempted rooting the system + tether via this method (only more manual typing involved due to system limitations in my virtualbox). It has an hour left of uploading, but could you test it when it's available?

Ah, just saw Slack3r made one too....could you let me know if his works and then I'll nix my efforts? It was a good learning experience though!
[X 2014 General] joshnat:
Understood, but JulesJam reports that it's working in the OP.
[X 2014 General] JulesJam:
He posted links to the stock 5.0 ext4 system image and 5.0 ext4 system image w/modified build.prop to allow free WiFi tether here:

http://xdaforums.com/showpost.php?p=60337214&postcount=29
[X 2014 General] JulesJam:
5.0 stock and 5.0 w/modified build.prop are working. Links above.
[X 2014 General] trimax84:
Stock/Stock + Tether, but not a rooted version (yet).

Exciting times :) Is MoFo available for us on 5.0 yet?
[X 2014 General] JulesJam:
I am flashing the rooted image now. MoFo takes a long time to flash presumably b/c of whatever it is doing to bypass the signature checks.
[X 2014 General] joshnat:
Ah, I get it. Stock modded but not rooted yet. Fantastic progress, thanks!
[X 2014 General] JulesJam:
It's up to [MENTION=5697730]maiko1[/MENTION] to modify moverify to allow for XT1096 running 5.0 to purchase mofo.exe.
[X 2014 General] JulesJam:
I am flashing Slack3r's now. PM me a link if you want me to test yours. It is best to zip the files so they are smaller for the upload/download as they do take awhile to download and then MoFo takes awhile to flash too.
[X 2014 General] JulesJam:
Ok that didn't work for root. It boots and free WiFi tether is enabled but no root.

If anyone else wants to take a shot at it, just PM me a link to where I can download the file and I will test it out.

Hopefully [MENTION=5697730]maiko1[/MENTION] will be around today and can let us know about opening up MoFo to those with an XT1096 running 5.0. And also provide some guidance on rooting the ext4 system image.
[X 2014 General] PiousInquisitor:
Did a bit of editing this afternoon... Trying to build my layers theme for my X. Its a pia to flash the whole system every time I make a change.