yashsingh1/xdaforums huggingface dataset:
[X 2014 General] JulesJam:
Yes

well this has permanently tripped the root checker on my phone and my qe = 1/1 now.
[X 2014 General] joshnat:
5.0 root working for me, including TiBu. Adaway not working, though. Thanks a million to all who have helped make this happen!
[X 2014 General] Slack3r:
Flashed it on my phone, everything is working great. Now development can finally open up :)
[X 2014 General] 1upyours:
WOW, good thing i refreshed. I had just finished downloading the stock w/ tethering enabled and was about to flash LOL.

Thanks BT! I'll give this a try and report back later tonight when i'm off work!
[X 2014 General] GatorsUF:
Flashing now, hoping for the best. Couldn't resist the temptation...

It is super easy guys! (assuming my flash goes through ok)

Edit: It works as advertised!! I even uninstalled some VZW apps with TiBu
[X 2014 General] Twistitup:
It will...and it's that easy. :)
[X 2014 General] astaccz:
I just purchased mofo on my moto x 2014 running 5.0. Looks like he opened up the purchases for 5.0 devices. Or am I late?? lol
[X 2014 General] Twistitup:
Just a little. :P

We've all been on this hype train since around 12. Hehe.
[X 2014 General] JulesJam:
maiko1 opened it up yesterday but it is not "officially supported" so he is not announcing that on the paid software forum and I suppose he won't respond if you have questions about 5.0 idk. But he should "officially support" it now that a confirmed, stable pre-rooted 5.0 ext4 image exists.
[X 2014 General] astaccz:
haha well ok. im just hype now that we got root on this great phone. im been watching this thread for that past couple days. Thank you to everyone who worked together to deliver the rooted image for 5.0. greatly appreciate it. :victory:
[X 2014 General] ClydeDroid:
OMG thank you everyone who has worked on this! Getting ready to flash now :)
[X 2014 General] maiko1:
mofo support for Moto X 2014 5.0 is now official
[X 2014 General] trimax84:
Thanks [MENTION=5697730]maiko1[/MENTION]! Couldn't have gotten this far without you!
[X 2014 General] JulesJam:
Awesome!!!! This is great!!!!!

Yipee!! I love my phone now!!! It's like a mini Nexus, lol!
[X 2014 General] opticsguy:
Accept OTA or go from 4.4.4

First thanks for all the effort that has been put in on this. I've been lurking, watching things happen...Now I ready to start.

I have a unused Moto X that is sitting on 4.4.4. Should I allow OTA update and then apply lollipop rooted image or should I just start in it's present state?
[X 2014 General] JulesJam:
I would take the OTA. You could also flash the files using the stock image that is on Root Junky's site but that would erase all of your data/media, you would lose your pictures, apps, settings, texts, etc.

Taking the OTA is the easiest thing to do.

mofo.exe only flashes system. If you don't take the OTA, then your radios, kernel, bootloader and partition table will all be on 4.4.4. Idk what will happen if you do that.
[X 2014 General] shane1:
Just want to say thanks to everyone involved in building and testing you guys and girls rock
[X 2014 General] 1upyours:
The MOFO process was super easy! WOW.. Finished everything in less than 30 mins.. Big thanks everything who created, tested and released files for the rest of us to enjoy. Tether was the only thing I cared about...and I got!

I was very close to purchasing the S6 since its been reported that FoxFi works on that device.. Basically, you all just saved me $800!

EDIT: By the way, is there a way I could disable future OTA now that i'm rooted?
[X 2014 General] Legacystar:
Has anyone baked in xposed yet? The real gem of root is now we can fix that nasty memory bug in 5.0 that's destroying this phone
[X 2014 General] JulesJam:
I do it by uninstalling MotorolaOTA 2.0 using Titanium Backup. With the free version of Ti B/U you can uninstall it; with the paid version you can freeze it.
[X 2014 General] TokedUp:
OK so is its too early to ask someone to make a IMG with Google Dialer, libs for light flow? I'll pay $20 for a rooted version
[X 2014 General] 1upyours:
Awesome! Downloaded TiBu and froze it since I already had a paid copy of TiBu

Thanks!
[X 2014 General] Caketray:
Will app ops work with this, or will the lack of write permission cause issues?
[X 2014 General] trimax84:
[MENTION=2278321]btdownloads7[/MENTION] - How hard would it be to add Xposed for 5.0 through the same method you used to get root on the img file?

I was reading here: http://xdaforums.com/showthread.php?t=3034811 and there is a zip that can be installed via a custom recovery that should make everything much easier than doing it by hand. Then we would just have to install the apk and it should work.
[X 2014 General] JulesJam:
So does this mean click on Mount and then uncheck the box by system?

I have TWRP 2.8.0.1. When I type adb devices while I am in TWRP and connected to my computer, it does not recognize my device but it did when I was booted into Android. Also adb shell does not open an adb shell.

Do I have a driver problem?
[X 2014 General] JulesJam:
I am currently trying that using btdownloads7's method but I think I may have a driver problem as I cannot open an adb shell while in TWRP.

So once I have the zip installed (assuming I can get my driver problem fixed), what do I do with the apk?
[X 2014 General] Twistitup:
You should just install Xposed apk and it will recognize the system changes you flashed and be good to go.

---------- Post added at 02:45 AM ---------- Previous post was at 02:44 AM ----------

Each Xposed module is an individual Apk that uses the Xposed framework.
[X 2014 General] JulesJam:
Meaning what, download the apk to the sd card and then do what? Run the Xposed Installer and it will install it?
[X 2014 General] Twistitup:
My complete understanding was that you flash the zip they had for Xposed in recovery and then you install the Apk like any other app through the OS. I may be wrong.
[X 2014 General] btdownloads7:
Yes, you uncheck the system partition in TWRP. And yes, you have a driver problem. If you had the ADB drivers properly installed, it would work in TWRP the same way as it does when the device it booted up.
[X 2014 General] Caketray:
So are you saying that you can install xposed through recovery after already flashing the prerooted image, or are you talking about how to bake it into the image?
[X 2014 General] JulesJam:
OK, but pretty much all of my apps come from the playstore so I just click on install in the playstore after I download them.
[X 2014 General] JulesJam:
Crap, I HATE driver problems!!!!!
[X 2014 General] trimax84:
This is how I interpret it as well....install the .zip via recovery and then boot into Lollipop and just install the .apk as normal. Then when you open the app, the system files will already be in place (since you put them there via the zip you installed in recovery) so it will work.

So many permutations, though I think this will work!
[X 2014 General] JulesJam:
I am talking about how to bake it into the image.
[X 2014 General] trimax84:
Is there an Xposed module to do this? I've been out of the Xposed loop since giving up my 1st gen X for this new one.
[X 2014 General] no3no3:
we can use twrp??with xt1096

we can use twrp??with xt1096? now?
[X 2014 General] trimax84:
No no (3 3)....we're talking about using TWRP on a different device (as long as it is an ARMv7 device) to load the Moto X 2014 system image, flash various zips, and then pull the image to load back onto our devices. Just an easier way than manually placing files and changing permissions/context
[X 2014 General] Aroch925:
So I flashed the rooted image and now my phone is really laggy. Does anyone why??
[X 2014 General] Twistitup:
What's laggy about it? Load speeds or the network?
[X 2014 General] Aroch925:
No just ui stuff like opening the app drawer and stuff like that
[X 2014 General] JulesJam:
no, mine is fine. Try booting into recovery and wiping the cache.
[X 2014 General] JulesJam:
Mofo.exe only flashes the system partition, not the recovery partition. You need an unlocked bootloader to flash a custom recovery.
[X 2014 General] en_pneumati@netzero.net:
all this activity is making me excited to get the OTA and then get a rooted LP installed... yeah!

so, just a little OT.... i bought full Titanium Backup several years ago on my old phone... i am not even sure if i can get my old phone to boot up now if my license is on it ... is there some way to get the full version again without having to pay up again ?
[X 2014 General] Twistitup:
Its all based off of your play store account. You'll have it if you are using the same account/email.
[X 2014 General] Legacystar:
Yes there is a module that patches the bug. What we need is a system image with xposed built in and write access to USB otg memory sticks.
[X 2014 General] JulesJam:
Well when I am in Mount, I have to hit Enable MTP to get my PC to see my phone. Then everytime the screen dims and shuts off, my computer stops seeing my phone.

c:\MX2014>adb shell

~ # ←[6nrm -r /system

rm -r /system

rm: can't remove '/system': No such file or directory

~ # ←[6nmount -t ext4 -o loop /sdcard/XT1096.img /system

mount -t ext4 -o loop /sdcard/XT1096.img /system

mount: mounting /dev/block/loop0 on /system failed: No such file or directory

I wiped and unmounted system like you said to do, but I am getting that error above when I try to mount the ext4 image (which I named XT1096.img).
[X 2014 General] btdownloads7:
I didn't have the problem with the Nexus 7 shutting off -- the screen would go dark, but the connection to the PC would stay on. And I'm sorry. but there is nothing I can tell you to fix it, except to keep tapping the screen to keep it awake.

And as far as the /system errors go. I'm going to add an extra step in the original instructons to fix this. Basically, you've deleted the /system folder in step 7, and need to recreate it before step 8. Sorry, but on my Nexus 7, it din't actually delete that folder. The command you need to run is "mkdir /system", and then move on to step 8.
[X 2014 General] ry_t:
Thank you everyone for making this happen.Can't wait til I get home to flash.
[X 2014 General] JulesJam:
That worked - but when I went to install the Xposed Installer 3.0 (the correct one for lollipop) it said wrong SDK version, expected 21 - 21, please download the correct package for your platform/ROM.

Is that b/c my Moto X 2013 is still on Kit Kat? I wiped the system partition but everything else is intact. I suppose it is detecting that the phone has a Dalvik cache.
[X 2014 General] trimax84:
I've gotten this far, but currently held up at trying to flash the xposed zip file....

It mounts /system, extracts files, but when it checks the SDK version it fails and prints "Wrong SDK version - expected 21-21"

Yet, Lollipop is 21, so I don't know why it fails. I'm using your stock + root version that you posted.

Tips?

---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------

Haha...we're simultaneously doing this. I'm working on my Nexus 7 though. The SDK version it is reading should be based off of the system img that is loaded...in this case 5.0, which is 21! Kinda frustrating, kinda fun....
[X 2014 General] JulesJam:
I think it is detecting that we have a dalvik cache, which lollipop obviously doesn't. I think we would need the dev who created Xposed to remove that check from the zip.
[X 2014 General] JulesJam:
Oh, so is the N7 on Lollipop already?
[X 2014 General] btdownloads7:
I'm sorry, but I don't know what Xposed installer looks for. It's very possible that it's checking the hardware that it's running on (as opposed to just checking the system partition, as the SuperSU script does). You'll probably want to ask this question in the Xposed thread, and it's very possible that this won't work on any other hardware, except an unlocked Moto X 2014 that's already been upgraded to 5.0.
[X 2014 General] Aroch925:
Does app ops not work with this? Ive been trying but it doesn't seem to work
[X 2014 General] JulesJam:
OK I will ask.
[X 2014 General] trimax84:
Mine is (was before I wiped the system) via CM12.1

When I do "grep ro.build.version.sdk= system/build.prop" in adb shell it returns that the file is not found....so maybe this is why it isn't working? Xposed also can't find the build.prop to check the SDK version?
[X 2014 General] JulesJam:
I will ask on the Xposed thread and see if there is any interest in helping us.
[X 2014 General] JulesJam:
I asked for help. Let me know if you think I didn't explain something correctly.

http://xdaforums.com/xposed/official-xposed-lollipop-t3030118/post60397390#post60397390
[X 2014 General] trimax84:
I'll take a look at that in a bit [MENTION=5983610]JulesJam[/MENTION].

For now I made a little progress here and just have to extract the img then load it onto my X.....
[X 2014 General] JulesJam:
Awesome!!! If this works, I can remove my novel of a post from the Xposed forum, lol!
[X 2014 General] trimax84:
Haha...looks like a good post. What I did to get it to flash was pulling the build.prop from the system.img that was contained in the rooted+tether stock ROM (in the /system folder) and copy/paste it into the system folder of the Moto X ROM that I was working on in TWRP on my Nexus 7 (for some reason, it wasn't there...?). So it flashed successfully.

However, in pulling the image together with my variant of "dd if=dev/block/loop0 of=/sdcard/new_image.img" the file that was created is only 650mb! Clearly this cannot be the proper Moto X ROM, so I hesitate to even flash it with MoFo.

Try a similar method and see what you get! It's getting late and I have to be up tomorrow, so I'm gonna call it a night. Good luck!
[X 2014 General] JulesJam:
I don't understand. I have mounted the pre-rooted 5.0 image and copied it the /system folder of the Moto X 2013 I am using. I see the build.prop file in there.

I will give up on this too for tonight :(
[X 2014 General] trimax84:
I see you mounted the pre-root version whereas I was using the rooted version that [MENTION=2278321]btdownloads7[/MENTION] created. I imagine it should function the same way though.

Needless to say, the 650mb Moto X image the I pulled from TWRP on my Nexus 7 (after flashing Xposed) just bootlooped. So now I'm installing btdownloads7's to get back to a functional ROM before bed.

Looking forward to the progress we'll make tomorrow!
[X 2014 General] JulesJam:
I used the same one you did. "Pre-rooted" is a term that maiko1 coined to mean an image that has been rooted PRIOR to flashing with mofo.exe.
[X 2014 General] JulesJam:
Any app that requires root and a reboot to install WILL NOT WORK WITH THIS BECAUSE WRITE PROTECTION IS NOT DISABLED. An app that requires root and a reboot to install is making changes to the system partition that if write protection were disabled would become effective on reboot. But write protection on our devices is NOT disabled so those changes to system are lost on reboot.

That doesn't mean you can't get them to work - you can but you have to install them in the pre-rooted image BEFORE you flash the image.

Now with Xposed modules, those require reboot to install but they are not making changes to the system partition - they are being loaded in memory (RAM) on reboot so those will work.

IMO since we have free WiFi tether, the NUMBER ONE priority is to get Xposed baked into the pre-rooted 5.0 image.
[X 2014 General] Haxxa:
In terms of the error "wrong SDK version, expected 21 - 21" for Xposed simply delete the section

"XVALID=false

if [ "$ARCH" = "$XARCH" ]; then

if [ "$API" -ge "$XMINSDK" ]; then

if [ "$API" -le "$XMAXSDK" ]; then

XVALID=true

else

ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"

fi

else

ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"

In the update-binary - being a shell script all it does is copy files and set permissions so this might work by ignoring the sdk version entirely by simply removing this section from the zip file - its located under - xposed-sdk21-arm-20150426.zip\META-INF\com\google\android
[X 2014 General] trimax84:
I attempted something similar last night but I must have deleted too many variables bc it wouldn't even run in twrp. Hopefully this will be more effective!
[X 2014 General] tacosrdelicioso:
im trying to fastboot flash the rooted system but it gives me a cannot load error. Idk what im doing wrong
[X 2014 General] Mayze23:
Are you typing "moto.exe flash (root image)" *no parentheses* I got the same error when i didn't have a space between the word flash and the image file
[X 2014 General] tacosrdelicioso:
i was trying to use fastboot to flash like it says in the op. i don't have a moto.exe
[X 2014 General] Mayze23:
I'm pretty sure you have to have Mofo root tools, which includes moto.exe, to flash the image
[X 2014 General] slogar25:
Correct regular fastboot will not flash the rooted or any modified image
[X 2014 General] JulesJam:
It doesn't say to use fastboot to flash the rooted system in the OP. You are not understanding a basic point here - fastboot CANNOT flash unsigned system images when your bootloader is locked. Mofo.exe CAN flash unsigned system images when your bootloader is locked.

That's the whole point here - if fastboot could flash unsigned system images when your bootloader is locked, why would anyone pay $20 to buy mofo.exe?

The pre-rooted image is an unsigned system image. If you want to flash it, you have to buy a copy of mofo.exe for $20. There is a thread on how to buy mofo.exe in the paid software forum.

http://xdaforums.com/general/paid-software/mofo-root-turbo-t3064404

If you don't want to spend $20 to buy a copy of mofo.exe, then you won't be able to get root access on your phone.
[X 2014 General] JulesJam:
I deleted this section using Wordpad and then resaved the file:

XVALID=false

if [ "$ARCH" = "$XARCH" ]; then

if [ "$API" -ge "$XMINSDK" ]; then

if [ "$API" -le "$XMAXSDK" ]; then

XVALID=true

else

ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"

fi

else

ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"

fi

else

ui_print "! Wrong platform: $ARCH, expected: $XARCH"

fi

and rezipped using 7-zip. When I follow the instructions in this post

http://xdaforums.com/showpost.php?p=60389310&postcount=177

and get to the part where I install the zip, it just fails this time as if there is something wrong with the file - it just says error flashing zip. Should I use Notepad to edit instead?
[X 2014 General] ry_t:
Do I still have to run the mofoverify before purchasing mofo?Or am I good to go?
[X 2014 General] JulesJam:
If you want to understand this at a lower level, you can read this:

https://github.com/android/platform_system_core/blob/master/fastboot/fastboot_protocol.txt

It tells you what the fastboot command is doing. When your bootloader is locked (i.e., secured), then this step happens when the fastboot command is executed:

"verify:%08x"

Send a digital signature to verify the downloaded data. Required if the bootloader is "secure" otherwise "flash" and "boot" will be ignored.

So when your bootloader is locked, if the digital signature is not sent with the system image or if it is not the proper digital signature, the system image will not be flashed.

Mofo.exe is a piece of software that does everything that the command "fastboot flash system" does EXCEPT it somehow bypasses the signature check. How? Idk.
[X 2014 General] JulesJam:
Yes you have to have a link generated to do the purchase. Then you use the link to go to where you purchase.

maiko1 opened mofo up to XT1096 running 5.0 a couple of days ago.
[X 2014 General] ry_t:
I tried running the motoverify yesterday and it couldn't find my device and I restarted it a couple of times, what should I do from there?Can you shoot me a PM,don't want to post anything else that isn't related to the thread.
[X 2014 General] JulesJam:
I am not affiliated with maiko1. I am just a random person with an XT1096 and a Verizon UDP line who needs root to WiFi tether for free, lol!

maiko1 answers MoFo support questions on the MoFo thread in the Paid Software forum here:

http://xdaforums.com/general/paid-software/mofo-root-turbo-t3064404
[X 2014 General] ry_t:
Thanks
[X 2014 General] JulesJam:
FYI

MotorolaOTA 7.0.0, which is the OTA updater app, is stored on the system partition. If you uninstall it, it comes back on reboot b/c write protection is not disabled.

If you buy the paid version of Titanium Backup, which is Titanium Backup PRO for $5.99, you can freeze apps stored on /system and on reboot, they stay frozen.
[X 2014 General] TokedUp:
So if you flash the rooted system img then reboot does root go away?
[X 2014 General] Caketray:
As I understand it, you will keep root because it was built into the image you flashed. Anything that requires write access that you add post-flashing will get removed, but if it's built into the image, it stays.
[X 2014 General] trimax84:
When your 2013 Moto X is in twrp with the pre-rooted ROM, can you run the following in ADB shell to see what returns....

grep ro.build.version.sdk= system/build.prop

(basically right after you mount the system file and before you try to flash the xposed module)

I'm curious to know if it recognizes build.prop on your system and what version prints out.

---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------

What Caketray said.... It's a fundamental principal of what we're doing so I think it warrants reiteration to help everyone understand. So the Mofo tool allows us to flash any image we create. Because we don't have write protection turned off, any system changes maybe within lollipop (or kk) will not stick after the phone is rebooted. However, any change we build into the image file before it is flashed with the Mofo tool will remain since it's baked in.

Good question... Hopefully I explained it well ☺
[X 2014 General] JulesJam:
OK, I will try that in a bit.
[X 2014 General] JulesJam:
Yes. This is how I understand it works - when you unlock your bootloader, 2 things are disabled:

1) system partition write protection; and

2) image signature check on flash.

Write protection refers to your ability to make changes to the system partition while running Android. If your bootloader is locked then write protection is enabled. If write protection is enabled, while running Android you can attempt to make a change to your system partition, but on reboot, the changes to the system partition will not be saved. An unlocked bootloader has write protection disabled and changes to the system partition will be saved on reboot.

Image signature refers to the manufacturer's digital signature. IOW, a signed image is "certified" digitally to be sourced from the manufacturer. A locked bootloader has the ability to detect whether or not an image has a valid manufacturer's digital signature. If you modify a manufacturer's image, the image will fail the locked bootloader's signature check. Thus a locked bootloader will not flash a modified (aka unsigned) system, kernel or recovery image. An unlocked bootloader will flash an unsigned system, kernel or recovery image.

So for #1, once you unlock your bootloader you can make changes to the system partition while running Android and the changes will be written to the system partition and thus survive a reboot. And for #2, once you unlock your bootloader you can flash unsigned system, kernel and recovery images.

Our bootloaders are locked. What mofo.exe gives us is some of #2 - the ability to flash unsigned system images.

We can get root access because we can modify a system image in ext4 file format to have the su binary and SuperSU installed (i.e., what maiko1 calls a pre-rooted system image) and then flash the unsigned pre-rooted system image using mofo.exe.

We have no way to disable write protection. That either requires an unlocked bootloader or an exploit must be found to bypass/disable the locked bootloader's write protection. No one is working on finding a way to unlock our bootloaders or an exploit that would bypass/disable write protection on our phones AFAIK.

And we can only flash unsigned ext4 system images, not unsigned boot.img or recovery.img so no modded kernels or custom recoveries.