yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] JulesJam:
Are you asking if you can get root with mofo and use supersu? If so, yes, that is the whole point of mofo.
[Paid Software Announcement and Discussion] JulesJam:
[MENTION=5697730]maiko1[/MENTION] - [MENTION=2278321]btdownloads7[/MENTION] was able to help me root the ATT XT1097 image and it was successful this time. Again, I have an XT1096 but if I can flash it to the XT1096, I am sure it works fine on an XT1097.

If you need someone to test the image on an XT1097, [MENTION=4049305]G4 Man2[/MENTION] has volunteered to do it. I will upload it tomorrow and send him the link but he needs mofo.exe to be able to test it on his device.
[Paid Software Announcement and Discussion] Moondroid:
Understand totally, just wasn't sure how the functionality of su will come across at the user level. Thanks much for replying.

Edit: I love the fact that CrashXXL's Moto X root even plopped a SuperSU icon in my apps drawer.
[Paid Software Announcement and Discussion] JulesJam:
Are you asking if the Turbo pre-rooted images have SuperSU baked into the images? If so, I would ask on the threads that discuss the images themselves. The links are in the OP. I am sure they do.
[Paid Software Announcement and Discussion] Moondroid:
Yeah, and question answered. Silverlink34 explains his image (and what follow-up is needed) very clearly right up front. Thanks again.
[Paid Software Announcement and Discussion] roman.ramirez.12:
I've got my turbo xt1254 rooted with tether busybox xpose and everything is good except is anyone having trouble sending small video through text messages. Even when I use the stock app it always says that I reached my limit... Any suggestions would be greatly appreciated
[Paid Software Announcement and Discussion] kitcostantino:
Roman!! glad to see you are still at the party!! I've been using messenger (google) but it still has to be pretty short length vids. maybe there is another app that works better, but even on my bl unlocked droid maxx, i have the same issue.

[MENTION=6412386]Moondroid[/MENTION] conputerfreek274 has made some awesome images (system.img) for the turbo as well. the one im running at the moment has super su and also has a symlink to use adaway. his thread is in Droid Turbo Android Development.
[Paid Software Announcement and Discussion] roman.ramirez.12:
Yeah I'm still here. Love my droid. I'm thinking it's part of the rooted IMG. File or something with the phone that I need to tweak because it tried that same messenger and quite a few others and it always ends up with the same results.
[Paid Software Announcement and Discussion] kitcostantino:
what .img are you running, dude? computerfreek274's newest is the best yet. 1.5.5
[Paid Software Announcement and Discussion] JulesJam:
I have never been able to send videos thru texts ever even when I was completely stock. I didn't know that you could do it at all.
[Paid Software Announcement and Discussion] kitcostantino:
the build.prop (located at /system) is probably the only place it would say what .img it is. case and point, my screen says the same thing, but if i go there, i see that it is computerfreek's .img.
[Paid Software Announcement and Discussion] roman.ramirez.12:
Strange mine doesn't show up but I know is the very first one that came out as soon as I rooted my phone I know I don't have the latest one that you showed me
[Paid Software Announcement and Discussion] Moondroid:
Thanks, got it bookmarked & subscribed. The details in his instructions are awesome too. Also thanks for nudging me to head over there and comment, which I haven't done yet.

Speaking of instructions, I am reminded . . . Years ago I had a programmer on my team who thought the history and comments sections in code were for wusses . . . lol . . . . "My coding takes a lot of work and hair-pulling, so why should I make it easy for the next guy by actually documenting what I did?" /snark/ . . . . But in my humble opinion, documentation is half of the product. And sometimes it's

everything

.
[Paid Software Announcement and Discussion] PiousInquisitor:
I've looked at stuff I've written hours earlier and thought "why in the world did I do that?". So well documented code (anything really) can be a benefit to yourself too.
[Paid Software Announcement and Discussion] maiko1:
Great, I'll contact him soon.
[Paid Software Announcement and Discussion] roman.ramirez.12:
Just flashed 1.5.5 all in one... I like it , works nice. Did speed it up a bit.??

Where's adaway at though?
[Paid Software Announcement and Discussion] JulesJam:
FYI - Once the DT gets upgraded to Lollipop, you have to do a couple of things to make Xposed work on Lollipop due to ART - check out the threads on the XT1096 images with Xposed if you want to know more.
[Paid Software Announcement and Discussion] roman.ramirez.12:
Thanks I really appreciate the info... I'm still waiting on that update has your phone receive the update already? And will come through on the new image that I'm on?
[Paid Software Announcement and Discussion] kitcostantino:
ha ha. yup. thank you, meow! I've been keeping up with all the awesomeness.

On a larger scale, thank you [MENTION=5983610]JulesJam[/MENTION] for putting in lots of effort testing and organizing others on the Moto X 2nd Gen. It is good to know Motorola users are still in the fight to get what we want on our devices. #unlockthedroids
[Paid Software Announcement and Discussion] JulesJam:
XT1096 is the Verizon Moto X 2014 - we have been on 5.0 lollipop since late fall 2014. BUT we do not have VoLTE so we can't so simultaneous voice and data. 5.0 is buggy for me so b/t that and no VoLTE, I would have rather stayed on Kit Kat and had VoLTE.

Once on Lollipop using ART instead of Dalvik, you are going to need new images obviously, but also Xposed is different. [MENTION=5849464]mikeoswego[/MENTION] was the one who put Xposed in the XT1096 images so whoever is making images for the DT should take a look at his posts over on the MX14 MoFo thread and his image thread before they try to update your 5.1 image with Xposed. No sense in reinventing the wheel ya know? But now I think you need to use one of the 5.1 Xposed versions - super alpha or something like that.

---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------

Us Verizon and ATT users have to band together to fight carrier tyranny, lol!!!

Wish TMobile was better where I live and hopefully someday it will be b/c Verizon and ATT need to have some competition to keep them in line.
[Paid Software Announcement and Discussion] roman.ramirez.12:
Ok cool thanks this might be a noobish question but am I supposed to get the lollipop update and then flash an image or just flash a lollipop image?
[Paid Software Announcement and Discussion] JulesJam:
Well first off, you have to flash back to stock system to take the OTA.

I would not however take the OTA. What I would do is uninstall or freeze MotorolaOTA. Then when you see that the OTA is being pushed to the DT, flash back to stock 4.4.4 system, put your phone in airplane mode so that it can't connect to download the OTA and then connect it to your computer and run the Motorola Device Manager. Let MDM update you b/c when it is done, it will leave a copy of the 5.1 fxz on your computer and then you will have the 5.1 system.img to root it. Your copy of mofo.exe won't work on 5.1 so maiko1 will have to alter moverify and mofo.exe so that 5.1 will be supported for the DT but he won't do that until someone makes a rooted 5.1 image for the DT. The first step is to get the 5.1 system.img.

[MENTION=2278321]btdownloads7[/MENTION] developed a method to root the images that is easy to use - I used it to root the ATT MX14 XT1097 and I don't even have an XT1097, lol! You do need another phone or tablet with an unlocked bootloader and TWRP installed as the recovery to do it.

I will make a post on the DT forum about this so it will get the attention of those in the know who would be making the images.
[Paid Software Announcement and Discussion] kitcostantino:
speaking of Tmobile, they definately are aiming to sway many Vze customers. (I was amazed dude said BS, mind you I am pretty foul-mouthed myself. *xda has helped me* I agree, though, but the coverage is nothing compared to what VZW has in the foothills/mountains of Upstate SC.

as far as Mofo goes, is there any plan to make it do more (for instance, the "Unlock" option), in the future, [MENTION=5697730]maiko1[/MENTION]?
[Paid Software Announcement and Discussion] aashadow15:
mofoverify not printing link (or much of anything at all)

So, I follow all instructions, run mofoverify_gui, and it just says:

version: 0.0.3

C:\Users\Walrus\Desktop\windows>

What did I do wrong?
[Paid Software Announcement and Discussion] fakieskr8333:
nothing yet, you now have to type mofo.exe then drag and drop your img file into the command prompt window and hit enter. be very certain you drag the correct file. if you drag the wrong one that is when you do something wrong.

EDIT: whoops, just saw this was for mofoverify. not sure on the steps for the initial verification. follow RootJunky's video linked in the OP. Should help a bunch.
[Paid Software Announcement and Discussion] roman.ramirez.12:
Don't take me the wrong way but if you have an xt1254 which is a Verizon variant should work so you may not have done everything according to the directions. This is the type of phone I have and I have it rooted... I do know you shouldn't have to have it in fastboot mode just have your phone turned on and plug it into the computer. Keep in mind this is info from someone who is definitely not a developer just an Android enthusiast.
[Paid Software Announcement and Discussion] JulesJam:
What phone do you have and what version of the OS is it running?

I would watch Root Junky's video again and if you are sure that you are doing everything right and that you have a model that is supported by MoFo, then I would email maiko1 at the email that is on the mofo web page.
[Paid Software Announcement and Discussion] Moondroid:
COOL. I just caught the idea of that possibility (OTA via PC) the first time I plugged an LG G3 into my laptop. I had already refused the OTA on the [new] phone itself but had to say no again on the comp. THANKS for that potentially very helpful clue.

Another reason why it can pay big to read an entire thread.

Same here (at the risk of too much off-topic), I'm just "North" (and east) and definitely in VZ country. Some years ago I tried switching to 2 other carriers for a few months, but sadly the coverage just wasn't there. If you look just north and west of Raleigh (NC), that long irregular east-west string of lake area. Totally sucks for coverage, or used to, for anything but VZ.

Just to route back to topic, same question from me. :rolleyes:
[Paid Software Announcement and Discussion] JulesJam:
[MENTION=4049305]G4 Man2[/MENTION] is still willing to test the XT1097 image. Can you get him a copy of mofo.exe for his device so he can do it? Until you open up MoFo to the XT1097, no one can start working on adding Xposed and other useful features to the pre-rooted image. Thanks!
[Paid Software Announcement and Discussion] BigTSetter:
I'm getting the same stop point. Gone through the exact steps and even did a system restore before all the installs. Device Manager is showing "OTHER DEVICES/ Fastboot Quark S" as a device not recognized. Any suggestions?

Windows 8.1 Pro. Fully updated as of 5/16/15. Droid Turbo 21.44.12.quark_verizon.verizon.en.US

Thanks.
[Paid Software Announcement and Discussion] cadenmiller60:
I can't get your method to work! What am I doing wrong?
[Paid Software Announcement and Discussion] roman.ramirez.12:
After downloading all the files where are you extracting them? And I'm guessing at this point you've already been verified and trying to flash now?

I'm only asking because I couldn't get mine to flash right away I had trouble too. And I know it's really important on where exactly you are extracting your files for it to work or to recognize your phone.
[Paid Software Announcement and Discussion] JulesJam:
You have a driver problem. Did you download and install the motorola drivers from root junky's site?

http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola

---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------

It doesn't work.
[Paid Software Announcement and Discussion] BigTSetter:
The extraction point should not matter, according to the video... Just as long as the files are extracted, which they were/are.
[Paid Software Announcement and Discussion] foxdog66:
I read that this should work on XT1096 (second gen moto x) but I dont get any link after running mofoverify, it just prints version: 0.0.3 and exits. Sense there is no OSX version, im using an old laptop running fedora. Android SDK is updated and adb/fastboot are recognizing the phone just fine. Any suggestions?
[Paid Software Announcement and Discussion] soopervoo:
I initially held off on root b/c my work uses MobileIron app for email, which does not work with root.

The IT team recently allowed the Microsoft Outlook app (thank God!) to check email. Can anyone confirm that the Outlook app will work with root? I just want to make sure that I can still check my work emails after paying for MoFoRoot. Thanks in advance!
[Paid Software Announcement and Discussion] JulesJam:
Idk about Outlook but I do know that there is an Xposed module RootCloak that works to cloak root with some apps:

http://repo.xposed.info/module/com.devadvance.rootcloak

http://xdaforums.com/xposed/modules/mod-rootcloak-completely-hide-root-t2574647
[Paid Software Announcement and Discussion] n4ogl:
I'm using Microsoft Outlook for both email and calendar instead of the despicable native Email/Calendar apps. It ran both under the stock rooted Image, and also under Computerfreek274's image (which I am now running).
[Paid Software Announcement and Discussion] JulesJam:
[MENTION=5697730]maiko1[/MENTION] - would you consider opening up MoFo for those with the Brazilian XT1097 to use to fix their locked bootloader devices in certain circumstances when they soft brick? They are able to unlock their bootloaders but now in 5.1, you have to actually enable OEM unlock in settings and if you soft brick before you do that, then you can't unlock. And there is no 5.1 system.img yet, just the soak test, and with a locked bootloader, they can't flash the 5.0 image even if it signed b/c the locked bootloader won't allow the downgrade.

For instance what happened on this thread to [MENTION=5935767]Christian Correia[/MENTION]:

http://xdaforums.com/moto-x-2014/help/unlocking-error-bootloader-t3111924

As long as the person can get into bootloader mode, if they have mofo.exe for their device, then they could flash anything they want to the system partition despite their locked bootloader. It could also help those who relock their bootloaders and then soft brick. I know people have done that even on the Nexus 6 when on 5.1. They relock b/c they feel it is more secure then they soft brick and then they can't unlock again b/c they can't get into the settings to re-enable OEM unlock.
[Paid Software Announcement and Discussion] xlightwaverx:
I'm having the same exact issue in Arch Linux as well. And I have the latest USB drivers, along with the correct Python. I'm not a windows guy and I'm assuming this would be easier for linux users as Android is Linux. The only difference is that it brings me back to the linux prompt, and not a windows one.

X

Edit: If someone has managed to get this working on Arch, feel free to add me on hangouts (same name as here) as I will gladly take some pointers. I've even used a factory cable in fastboot mode as well, and tried every USB port available on this Asus FX 8300.

Edit2:

[xlightwaverx@AsusFX8300 mofo]$ adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
[xlightwaverx@AsusFX8300 mofo]$ adb devices
List of devices attached

[xlightwaverx@AsusFX8300 mofo]$

Edit3:

[xlightwaverx@AsusFX8300 mofo]$ dmesg | tail
[211042.721974] usb 1-2: new high-speed USB device number 5 using ehci-pci
[211277.261541] usb 1-2: USB disconnect, device number 5
[211292.734567] usb 1-2: new high-speed USB device number 6 using ehci-pci
[211297.710662] usb 1-2: USB disconnect, device number 6
[211301.130583] usb 1-2: new high-speed USB device number 7 using ehci-pci
[xlightwaverx@AsusFX8300 mofo]$
[Paid Software Announcement and Discussion] PiousInquisitor:
Is USB debugging checked in developer options?

You also should type 'adb devices' first. When you do, you will get a prompt on the phone to allow adb access. Make sure you allow it.

Are you using the factory cable? Or a cable that has worked for data transfer before? If not find one. Some cables are for charging only.

Check that stuff. If it doesn't work you will need to edit some files related to the SDK.
[Paid Software Announcement and Discussion] xlightwaverx:
I'm in Fastboot mode, so I am not sure how USB debugging would do anything for me.

I'm not sure what I did differently but now I get this when I plug in and run 'adb devices'

[xlightwaverx@AsusFX8300 mofo]$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
????????????	no permissions

I tried the process as root and still get the same thing:

[xlightwaverx@AsusFX8300 mofo]$ su
Password:
[root@AsusFX8300 mofo]# adb devices
List of devices attached
????????????	no permissions

Thanks for the help so far.

X
[Paid Software Announcement and Discussion] JulesJam:
Once you enable USB debugging, then plug your phone into your computer and type

adb devices

a pop up should come up on your phone that you have to authorize your computer to access the phone. And you can revoke that at a later time by hitting revoke usb debugging authorizations.

I don't know if this has anything to do with what you are experiencing with MoFo, but it could explain that error message you got when you typed adb devices.
[Paid Software Announcement and Discussion] maiko1:
mofo now supports ATT XT1097 Moto X 2014 on 5.0.

Thank the people at this thread for testing/creating images.
[Paid Software Announcement and Discussion] acquire_spondulicks:
Hey [MENTION=5697730]maiko1[/MENTION] thanks for working on rooting my phone :good:

I'm considering buying your root, please excuse me if this is a dumb question. But with the news that Lollipop is coming out for the Droid Turbo I'm wondering if this would allow me to block Verizon's OTA update? I want to prevent them from further locking down my phone with the hopes that maybe eventually I can flash my ROM later down the road

My previous phone the Note II got locked down with a Verizon update and ruined my flashing fun. I'd settle even for semi-rooted 4.4.4 if that means I can remove or quarantine Verizon's stupid crapware. (Already can do that with this, thanks for that.)

So is OTA inevitable or preventable?
[Paid Software Announcement and Discussion] JulesJam:
If you are rooted and have the paid version of titanium back up installed, you can freeze MotorolaOTA and stop the updates.

If you know how to modify the images using linux, you can simply remove MotorolaOTA from the image.
[Paid Software Announcement and Discussion] heath223:
I am looking at selling my rooted turbo. what happens if I do a FDR? would the phone still be rooted with all my data gone or would it unroot it or would it lock it up or maybe even brick it?
[Paid Software Announcement and Discussion] Moondroid:
FDR won't touch your root status. As for data, yes it will all be gone, all the way back to the first google email address you entered at initial setup.

FDR = factory

data

reset, nothing to do with system.

EDIT: Just make sure you have plenty of battery to survive a heavy 10-minute process.
[Paid Software Announcement and Discussion] ahaynes42:
I'm coming up on 24 hours. I'm doing my best to be patient, but I just really need wifi tethering and Titanium backups back. Hope to hear from someone soon. Keep up the good work, I'm thankful to even have tethering and backups to get back to.

Edit: I've been taken care of. Thanks!
[Paid Software Announcement and Discussion] acquire_spondulicks:
Thanks! Nice, I use linux already, so that option works great for me.
[Paid Software Announcement and Discussion] JulesJam:
I would not do a factory reset with a MoFo image on your system partition. Flash back to stock system, wipe cache, boot and then do a factory reset.

Then if you want to sell the device as MoFo rooted, reflash a MoFo image.
[Paid Software Announcement and Discussion] timofcourse:
Any chance someone can confirm if AirAudio works with this? Specifically if system audio can be used. This is really the number one reason I've missed root and would love to have confirmation before purchasing mofo.

Thanks so much!
[Paid Software Announcement and Discussion] JulesJam:
By your question, I don't think you understand what MoFo gives you. It simply gives you the ability to flash unsigned system files but does not disable write protection.

If Air Audio works, then it can be baked into an ext4 image and the image flashed with mofo. But someone who knows how to bake it into an ext4 image using linux has to do that if you want Air Audio on your device.
[Paid Software Announcement and Discussion] timofcourse:
I've scanned through several of the first few pages of posts here and I was confused as to what this does and doesnt allow you to do. I saw several that seemed to indicate system files can be modified, but that they'd be reset upon next reboot. If thats the case, then I believe AirAudio would work as I believe it updates (one? many?) system file(s) to pipe system audio to supported devices at the time you run it, so the changes don't necessarily need to be permanent.

For those unfamiliar, it allows you to stream any audio from your device to a bunch of supported devices (ChromeCast, Roku, Sonos, AirPlay). The free version provides full functionality; it just limits the amount of time you can stream to 5 minutes. I'd be super appreciative if someone could do a quick test this and report back their findings. I have nowhere near the skills required to include this app into an existing image and not sure the likelihood of convincing someone here to do so for me, so hoping it works as is.

Thanks again!
[Paid Software Announcement and Discussion] G4 Man2:
The original post states that system files cannot be modified while the device is running. Therefore AirAudio does not work. However, I believe one system image maintainer for the Turbo is working on implementing support for it as stated in his original post. I don't use the Turbo so I don't remember who it was but I'm sure you can find that thread and ask if any progress was ever made towards implementing it.
[Paid Software Announcement and Discussion] JulesJam:
It's not the case. You didn't read the subsequent posts about that.

---------- Post added at 06:22 PM ---------- Previous post was at 06:17 PM ----------

I don't know if you have a DT or a MX, but you may be able to pay one of the people who have modded the images to bake it in for you. ClydeDroid was considering adding it to his image for the MX, but I think he is a college student and was in finals. He hasn't posted an update in awhile.
[Paid Software Announcement and Discussion] funtax:
Hi there, I'm the dev of AirAudio.

I can confirm a Mofo-user (Nick) contacted me two weeks ago and I told him what file has to be included in the image.

He had a problem implementing it and sadly I haven't got a feedback yet from him.. just sent him a reminder.

If someone of you is familar with the Mofo-tool, feel free to contact me at AirAudio's official support-address from http://play.google.com/store/apps/details?id=eu.airaudio .

Should be a manor of minutes, it's just 1 file which has to be placed at the right position :fingers-crossed:

Cheers & happy coding,

Martin