yashsingh1/xdaforums huggingface dataset:
[X 2014 General] en_pneumati@netzero.net:
DUDETTE! Mega thanks

i guess you just laid out my weekend plans for me ;)
[X 2014 General] TokedUp:
$20 for someone that can make me a rooted img with BB, SQL, and GOOGLE DIALER! PLEASE! I know im not the only one wanting this.... Im going on vacation next friday and that Google Dialer will come in handy while Im away
[X 2014 General] JulesJam:
Works fine.
[X 2014 General] JulesJam:
YW! I started a thread here:

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
[X 2014 General] JulesJam:
[MENTION=5697730]maiko1[/MENTION] - I tested this image btdownloads7 made with busybox and sqlite3 baked in and it works fine on my device. Please add the download link to the OP of the MoFo thread, thanks!!!!

https://mega.co.nz/#!adtCgZoa!TgnA8GlsWj0sHCpw5y_G8uWkJK2OBKUAAdKVl2Pa7AI
[X 2014 General] JulesJam:
why remove those? Since they are system apps you can't use the space for apps that go on the data partition. I just freeze them with Titanium B/U PRO.
[X 2014 General] JulesJam:
The tutorial for Xposed installation only works for Kit Kat b/c KK uses Dalvik cache not ART. So Xposed 3.0 for Lollipop is very different from Xposed for KK.

For modding the image, this tutorial should work for the 5.0 image:

http://xdaforums.com/droid-turbo/general/tutorial-how-to-modify-turbo-images-t3064595

I would start with [MENTION=2278321]btdownloads7[/MENTION] rooted image with BB and sqlite3 baked in. It has the modified build.prop, too. I don't know much about BB or sqlite3, but apparently, they are good to have and people want them in the image.
[X 2014 General] trottellumme:
Maybe I should rephrase - replace them where I see fit. As an example I can't replace the dialer, I can install an additional one however I can't change the default.
[X 2014 General] mikeoswego:
Works great. Thanks for your work!

---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------

@JulesJam, thanks for the write-up, it was very helpful!
[X 2014 General] JulesJam:
Thanks, that is the exact same system.img that I found on my PC in the folder where MDM stores its downloads. However when I use fastboot or mfastboot to try to flash it I get this error:

load_file: could not allocate -2046660348 bytes

error: cannot load 'system.img'

And when I try to use MoFo to flash it I get the error that it is not an ext4 file.

'C:\MotoX2014\5.0fxz\system.img' does not look like a valid ext4 image

This is bad. Type YES to continue and risk it all:

When I type YES, MoFo will flash it but it doesn't boot. Also, the fxz file is 2,195,613 KB in size whereas the ext4 prerooted system files are 2,834,432 KB in size.

Does anyone know how to convert these fxz files into ext4 files? MoFo needs an ext4 image to flash.

[MENTION=5697730]maiko1[/MENTION] - can you provide any guidance on what needs to be done?
[X 2014 General] maiko1:
Use simg2img to produce a motosystem.img:

simg2img system.img motosystem.img

Then cut out the ext4 part with something like dd. For this specific image, it would be:

dd if=motosystem.img of=system.ext4.img skip=256 count=5668864

The file command should say it's an ext4 image. Try to mount it to make sure it's valid.
[X 2014 General] briosita:
Pre-Rooted Image

Thanks for all of the work and helpful info, JulesJam.

Unfortunately, no Linux here.

Anyone have a rooted 444 image with net.tethering.noprovisioning=true (and hopefully with OTA turned off)?

Xposed baked would be sweet as well, but tether is the grail for those of us with UDPs.
[X 2014 General] TokedUp:
I don't know what u guys are talking about but it sure sounds cool lol! I hope it means there's a 5.0 image coming
[X 2014 General] JulesJam:
Check out the quotes by picowoodworm that I added to the OP - he provides a link to an app that does the same thing wrt tethering.

Also, just down load Ti B/U from the playstore right after you flash. Then open it up, grant it root privileges, click on backup/restore, scroll down to MotorolaOTA 2.0 and click Uninstall.
[X 2014 General] Haxxa:
Just trying to clear things up here, there is no possibly of downgrading to 4.4.4 I assume, due to bootloader restrictions and thus even if we wanted to downgrade to a root image we couldn't right? Furthermore how is the rooting of the stock 5.0 image going, has any progress been made on that front? Sorry if this is obvious - just two of the key questions asked by reddit ATM.
[X 2014 General] JulesJam:
Well I tried downgrading the system and kernel to 4.4.4 after I had upgraded to 5.0 and it didn't boot. No way would I be willing to try to downgrade the bootloader.
[X 2014 General] JulesJam:
I updated the OP - so far we have free WiFi tether by flashing an ext4 image having a modified build.prop made by [MENTION=1576439]Slack3r[/MENTION].

[MENTION=4649539]slogar25[/MENTION] is working on a pre-rooted ext4 image I believe. As soon as he can upload it I can test it.

[MENTION=5697730]maiko1[/MENTION] - can you provide any guidance on what needs to be done to pre-root the ext4 image? Also can you please open up MoFo to XT1096 running 5.0? Slack3r will post the images he made in this thread so that others can take a stab at pre-rooting the ext4 images. I think lots of people would be interested in the image with the modified build.prop so that they can have free WiFi tether. Thanks!!!!!
[X 2014 General] Slack3r:
I'm glad to help out where I can, I'd like to see a working root on 5.0 as much as you guys. Thank you to maiko1 for the instructions, slogar25 for the image, and JulesJam for testing them.

These are the images I created based on the fxz upladed by slogar25 in case anyone wants to give rooting them a shot (or just wants tethering). You can mount them to edit in linux with the following command:

sudo mount -t ext4 -o loop [path to]system.img [path to]/mount

Stock:

https://mega.co.nz/#!Dc9W3SrB!Xt2albnCaOxPv1hwFsETwD0x0RPam4Zvc1qYirAkCZU

Stock w/ Tether:

https://mega.co.nz/#!CdsgDQLD!eUJl8Kwnc1QCc8wu4yMvqMLoCKapMEFIs0jrotI1NCU
[X 2014 General] trimax84:
Thanks [MENTION=1576439]Slack3r[/MENTION]!

I went through the steps of installing VirtualBox with Ubuntu tonight and plan on learning how to do some editing based on your files. I appreciate you sharing them (and all the work the others are doing on this!)
[X 2014 General] Caketray:
Can anyone make/find/teach me how to make a Lollipop image w/ xposed baked in? Dying to try it out!
[X 2014 General] JulesJam:
I am going to try this too as soon as my 128GB flash drive gets here. Unfortunately, I have a space problem on my computer but I read on the Ubuntu site that I can run it from a flash drive.

Can't wait for root!!!!

Idk if it is just my imagination or not but my MX2014 WiFi tether seems faster than my MX2013 WiFi tether. I have to put my MX2013 in the drawer now alongside his GNex older brother. Awww, I am going to miss my little guy! Him and his cute wood back. But my leather backed MX2014 sure is handsome and feels really good in my hand, too!!! LOL!
[X 2014 General] JulesJam:
We need root first. But if you go to the MoFo thread on the paid software forum, in the OP there is a link to a thread on how to mod these images - you need to use linux.
[X 2014 General] Haxxa:
Just mounted stock image on my Linux Server and began removing Verizon bloatware, changed boot animation to stock animation and plan on creating a close as stock image as possible. Continued by enabled tethering, I prefer a stock image so when MOFO comes out with 5.0 support I'll be ready! Exciting times :)
[X 2014 General] JulesJam:
XT1097 and Moto G

If anyone has the fxz for the XT1097 MoFo should work for the XT1097 too.

I found a copy of the system.img on my PC where Motorola Device Manager stores the firmware - c:\ProgramData\Motorola\SUE\Firmwares. It is the same file that slogar25 uploaded in the fxz he posted.

If someone can get that system.img for the XT1097 and follow maiko1's instructions a few posts back, they should be able to turn it into an ext4 file that MoFo can flash. Once that is confirmed to work, then it can be pre-rooted.

Same for the Moto G.
[X 2014 General] trimax84:
Ok, yeah, adding root seems like more than copying a few files to the image and repackaging.

Hopefully someone is gracious enough to put the effort in and share it here. In fact, [MENTION=2576071]Haxxa[/MENTION] and all others that put effort into this, please share your modified systems (once they are ready) to help keep up the development and community for this device!

These are the tutorials I have been looking at (many of which have been posted by JulesJam or others throughout various threads)....

Using this tool: https://www.virtualbox.org/wiki/Downloads

With this Ubuntu: http://virtualboxes.org/images/ubuntu/

And this .iso: http://www.ubuntu.com/download/desktop

With [MENTION=1576439]Slack3r[/MENTION] Stock+Tether Rom: https://mega.co.nz/#!CdsgDQLD!eUJl8Kwnc1QCc8wu4yMvqMLoCKapMEFIs0jrotI1NCU that he posted HERE

Modifying a Droid Turbo image: http://xdaforums.com/droid-turbo/general/tutorial-how-to-modify-turbo-images-t3064595

Unpacking/Repacking ROMs: http://xdaforums.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239

Embedding SU: http://su.chainfire.eu/#embed

And eventually will be checking out the Xposed Module one: http://xdaforums.com/droid-turbo/general/guide-getting-xposed-t3066084

Edit: Oh yeah, for those trying through VirtualBox like me....Ubuntu went from sluggishly unusable to snappy by increasing the allocated RAM and checking "Enable 3D Acceleration" under the Display section of Settings.
[X 2014 General] Haxxa:
Thanks for all the info, I'll have a go at embedding SU + Xposed - later tonight -I have to go to work for now. Also removed app that causes "This Sim is not from Verizon" so when you use the phone in another country like me (live in Australia) or for travel there will be no more annoying messages or pop ups.
[X 2014 General] JulesJam:
Idk if this is helpful or not but there are rooted files you can check out here:

http://rootjunkysdl.com/?device=Moto X 2014&folder=Root Firmware

Now obviously the 5.0 version had something wrong with it b/c it wouldn't boot, but the 4.4.4 rooted image worked fine.
[X 2014 General] Haxxa:
Umm... I will make changes by only adding SU using instructions, run MD5 sum comparison and see if the images are identical. If they are then the device might not play ball with root, if not I will upload it and maybe you could test on your device? Not at home yet, so if its easy enough feel free to do so or I will try later tonight.
[X 2014 General] JulesJam:
It is 2:30am my time so going to bed soon, but I will test any images people make.

Hopefully, maiko1 will open MoFo up for XT1096 running 5.0 soon.

Also, if anyone can figure out how to make that horrendously ugly white search bar transparent, I would be eternally grateful!!!!! I would rather not remove it; just want it transparent.
[X 2014 General] maiko1:
Added, thanks.
[X 2014 General] trimax84:
But you can use the space for other user apps which will subsequently free up space on the data partition* :)

(*if you know how to modify the ROM in Linux before loading it onto your phone via MoFo.exe)
[X 2014 General] JulesJam:
OK so you could put regular apps that don't need to be on the system partition onto the system partition and they will work as they normally would?
[X 2014 General] trimax84:
Haven't tried it, but someone mentioned it in the Turbo thread. I don't see why it wouldn't.

Planning to get Xposed first! Trying something new tonight!
[X 2014 General] contesauce:
So it looks like the work is mostly done for Google dialer. It would have to be included in an image but appears to be apks that need to go into sys priv apps

http://xdaforums.com/moto-x-2014/themes-apps/mod-google-dialer-messenger-pure-edition-t2982408

By the way, tested busybox SQL img and all's working great so far. Root intact, busybox dependent apps working fine.
[X 2014 General] GatorsUF:
I too would like the Google dialer
[X 2014 General] PiousInquisitor:
No voodoo coding is done for the Verizon apps and other bloatware to be on the system partition.

TibBu gives you the option to install regular apps as system apps.

Thanks for the thread and instructions. It will be nice to tether again.
[X 2014 General] Haxxa:
The Good: I got a booting Image with Xposed and Google Dialer created in Ubuntu.

The Bad: The image has no boot animation - (not sure why didn't touch it), it constantly crashes, google dialer is not present in app drawer and oppening via activity causes FC. Xposed seems to show installed but the image is literally freezing to an unrecoverable state every minute after boot.
[X 2014 General] Mocha_Bean:
Hey, it's progress. :P
[X 2014 General] Haxxa:
I think I can fix the Dialer Issue which may fix the rest of the issues I am having - will have to wait to morning though its late in Australia. :P
[X 2014 General] JulesJam:
Thanks, did you see that Xposed Alpha 4 was released?

http://xdaforums.com/showpost.php?p=60454533&postcount=9
[X 2014 General] Legacystar:
Anyone else's HDR mode on camera cause force close on the rooted busybox image
[X 2014 General] Mayze23:
Yep mine FC's when using HDR.

I never tried it on the original rooted image to see if it did the same..

Edit: Also FC's when using HDR with the Google camera app
[X 2014 General] contesauce:
I'm not having fc on the busy box image with hdr on auto or on.
[X 2014 General] JulesJam:
yeah that is what is happening to me. I tried uninstalling the camera update and reinstalling and rebooting but same problem. Doens't happen with HDR on auto.

I wonder if this is due to the memory leak? HDR likely uses a lot of memory.

I always keep HDR on auto so idk what was happening b/f I flashed the rooted image. You would need to flash back to stock to know if the problem was on stock too. If so, then this is a memory leak issue.

Edited - just did some search/reading and this looks like it is due to the memory leak. You could confirm that by flashing back to stock and seeing if it still happens.
[X 2014 General] Haxxa:
Quick Update:

I ended up messing up my Linux Installation and after 7 Hours of work, I really can't be bothered to try all that I tried again, I must have flashed my Phone at-least 20 times. In the end I could not get Xposed working and I was messing stuff up like crazy. Simply put though it shouldn't be too hard to mount the system image and run all the commands as defined in the Xposed Installer (zip file).

The only annoying aspect is that the Xposed Installer defines commands at the start of the file like (install_override) which requires you to refer to top of the file and understand what each command is doing. In fact the xposed Installer is probably the most complex zip Installer I have ever seen simply due to defining commands at the beginning of the file. (still it is just a shell script at the end of the day)

But in any case, I can't afford to spend any more time on it. I tried my best to get somewhere but I am now leaving it to someone smarter than me, any person who uses Linux religiously should be able to do this. Its just time is all... Furthermore whenever I changed my boot-animation file and set the right permissions it would still display the stock android image like it could not load it, so maybe using "sudo chmod 644 file" is not a enough and I am missing something when defining permissions.

btdownloads7 seems to have a good grasp of this process and knowledge so maybe he might be able to do it given he has the ambition and time? But it's now beyond my scope, so still no Xposed :(
[X 2014 General] JulesJam:
I think it is install_and_link that is the tricky part. It is clear to me that it is a symlink but then you have that zygote thing goin' on.

Thanks for trying!!!!!
[X 2014 General] JulesJam:
I don't think he is interested in Xposed.
[X 2014 General] Mayze23:
It's not due to memory leak issue. I used hdr before we were able to use mofo root and it never FC. I'm not sure if it's root that's breaking it or if it's specifically the busybox image. I rarely take pictures so it doesn't bother me in the least but I may flash the original root image to see if it works.
[X 2014 General] ClydeDroid:
I have Ubuntu on my laptop, I will be able to give it a go sometime tomorrow. I know how to mount the image and make changes, but how do I actually find the commands in the Xposed installer? Should I just look around in the zip file?
[X 2014 General] Haxxa:
Yep its in the Zip File under the folder META_INF - UPDATEBINARY - just open this file in your FAV text editor and get to work, there's a lot to go through, so be prepared...
[X 2014 General] en_pneumati@netzero.net:
i only flashed the pre-rooted 5.0 image with tethering (no busybox, etc.).

choosing to turn HDR to ON with the built in camera causes a FC.

maybe it was just unstable in the stock LP 5.0, too? anyone on 5.0 that hasn't flashed a pre-rooted image willing to check it out?
[X 2014 General] JulesJam:
From what I am reading it seems it could be due to the memory leak, but yes, you would need to flash back to stock to test that theory out.
[X 2014 General] btdownloads7:
I'm having the same issue with both the stock camera, and Google Camera from the market. I'm positive that this never happened with the original Motorola ROM, but since it's happening with the pre-rooted image that;s the base for all of our mods, then there must be something messed up with that image. If I remember correctly, that image came from the FXZ, so it's possible that it's some kind of a problem with the ssystem image in the FXZ, but we'll need to flash that original image to test that theory (and I might have some time today to do that).

And for the record, I tried clearing the data and cache for both camera apps, clearing the cache partition and running the "fix permissions" script on the data partition. None of that worked, so something is defeintely messed up in the original image.

---------- Post added at 02:36 PM ---------- Previous post was at 02:12 PM ----------

I just flashed the original system image from the FXZ, and the camera works fine there. So the problem must be with the image conversion from the original one in the FXZ to the ext4 one that we all used as the pre-rooted base. I'll go through the conversion prosess myself, and see if I have any issues with the resulting image.
[X 2014 General] JulesJam:
And I flashed the system.img that is on my PC from MDM and camera works fine on it.
[X 2014 General] mikeoswego:
I made an image with Xposed included. It sticks at the red Verizon screen for a long time. It then says upgrading apps and goes through 217 of them in just a few seconds (obviously not really doing anything.) When it gets to the home screen, it complains that System is full. I tried making an image with NFL football removed and it still said the system was full even though it had over 512mb free. Root was intact. Xposed said it was installed but when downloading a module, it would not install it. So I'm stuck for the moment and thinking that maybe Xposed requires write access to /system.. :p
[X 2014 General] JulesJam:
Thanks for trying!!! I will ask on the Xposed support forum.
[X 2014 General] mikeoswego:
I just looked over there and this post http://xdaforums.com/showpost.php?p=60511753&postcount=6196 describes the issue about system being full just like I saw previously. I did not wipe cache and I'm not sure how to wipe dalvik only inside /data from the recovery menu. In that post he mentions that the wrong set of apps are having their dalvik/art cache rebuilt and that is the 217 number I saw previously. When I put back the busybox image, it did the upgrading dialog and there were only 60+ apps getting new davlik/art entries.
[X 2014 General] JulesJam:
I saw that too and asked the guy about lollipop not having a dalvik cache - that is the whole reason that there was such a huge delay in getting Xposed for Lollipop - AFAIK Lollipop does not have a dalvik cache, it uses ART.
[X 2014 General] JulesJam:
But is there a dalvik cache once you are on Lollipop?

Edited - he responded: http://xdaforums.com/showpost.php?p=60512734&postcount=6203

I think you could erase your data partition by typing fastboot erase data but then you would lose all of your apps and settings. But I am not sure if we can do that with a locked bootloader, I think we can.
[X 2014 General] slogar25:
The camera issue I believe started with the busybox and sqlite image. I am pretty sure I did not have any issues with the root alone image.
[X 2014 General] JulesJam:
I will flash the pre-rooted w/o bb and sql in a bit and then I can tell you for sure.

Edited - I get the same camera errors in the pre-rooted image that does NOT have BB or SQLite3 installed. So it is a problem with the pre-rooted image. The problem is not in the original fxz.
[X 2014 General] mikeoswego:
Yes, ART uses a cache and they put into /data/dalvik-cache directory (this way all the recovery tools still work!)

I've got it working thanks to reading that post I linked to! I cleared the dalvik/art cache by simply erasing both directories within /data/dalvik-cache. Then did an adb reboot-bootloader, ran mofo with my image, went into recovery and cleared the cache there.

On reboot, it took a bit at the red Verizon screen, then started optimizing 216 apps. This time it took about as long as the normal optimizing 60+ apps that it should be doing. Once booted up there were/are no more memory errors. Xposed was able to download Gravity box for LP and that works great. I've now added XGels and that also works perfectly (or at least as far as I've tested it.) :highfive:
[X 2014 General] JulesJam:
Awesome!!!!! Did you do this using linux?

Also did you use the BB/SQLite3 image?
[X 2014 General] ClydeDroid:
:D Do we get to try it? :D
[X 2014 General] mikeoswego:
Yes in Ubuntu and I used the BB/SQL image with the HDR problem. I've attached a script. This script is mildly modified from the update-binary script within the xposed-sdk21-arm-20150430.zip file.

You must mount the image that you want to install Xposed to /system on your Linux box (or edit the script some more.)

Make the script executable (chmod 755) and then run the script like this:

sudo [full path to script] [full path to zip file]

On my system it looks like this:

sudo /home/mike/InstallXposed /home/mike/xposed-sdk21-arm-20150430.zip

There will be some chcon errors but it still sets the permissions correctly.

On reboot, it will take a little longer at the red Verizon screen, then it will upgrade/optimize apps claiming a very large number of apps to process but most of them go by very quickly. On subsequent reboots it upgrades/optimizes one app each time. Otherwise I've not noticed any other problems or side effects.)

As usual, you are responsible for your own stuff; if something breaks I'm not responsible!
[X 2014 General] mikeoswego:
Forgot to mention that you do need to install the matching APK from your file manager. That APK is here: http://xdaforums.com/attachment.php?attachmentid=3200857&d=1425849071
[X 2014 General] JulesJam:
Install it by downloading it and then clicking it?
[X 2014 General] mikeoswego:
Yes!

I'm uploading that image file now, a bit less than an hour to go..
[X 2014 General] JulesJam:
FYI - I flashed the original fxz system.img and it is fine. The problem started with the first pre-rooted ext4 system.img w/o BB or SQLite3 - the original pre-rooted ext4 system.img has the camera HDR problem too.
[X 2014 General] en_pneumati@netzero.net:
so, does this mean there IS something wrong with the pre-rooted system img posted in the Mofo thread, the one i assume most of us are using, and that we need to re-flash a new/repaired img?

is the problem more than just the HDR camera not working?
[X 2014 General] mikeoswego:
I created a new thread here for the image with Xposed included:

http://xdaforums.com/moto-x-2014/development/img-xt1096-victara-mofo-image-root-t3100145