yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] JulesJam:
Which one is more like the ultra - the mini or the maxx?

---------- Post added at 08:48 AM ---------- Previous post was at 08:45 AM ----------

Of course you can't. Maiko1 has to update moverify to allow someone with an Ultra to purchase.

What version of the Droid Ultra firmware are you on? 4.4.4? Is it available as sparsechunks anywhere?
[Paid Software Announcement and Discussion] nrgyitguy:
I have a system image ready to go for an Ultra (to be tested anyway),kitkat SU6-7.2. I was under the impression that is all I needed. How do you think I should proceed to attempt to get mofoverify to work for the Ultra. The MOFO FAQ states that if mofoverify wont spit out a link then the phone wont work with mofo anyway. I don't want to ask maiko1 for something that has been stated wont work, I don't wish to waste their/his/her time. However if this is feasible then I would think they/he/she would want to make it happen so they can collect $ for ultra/maxx users of MOFO?....Anyone in the community please correct me where Im wrong and/or point me in the right direction to make this happen or verify that it wont:confused:....THANKS TO ALL THAT CONTRIBUTE TO THE DISCUSSION!:highfive:
[Paid Software Announcement and Discussion] JulesJam:
It has to be in ext4 format. If you have the sparsechunks, I can make one for you.

---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------

You cannot get it to work for you. You first need a rooted ext4 system image. Then you contact maiko1 and ask him to open MoFo up for you to test your rooted ext4 system image.

---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------

I need an ext4 image for your phone.
[Paid Software Announcement and Discussion] kitcostantino:
the ultra is literally identical. if wireless charging is present (Maxx) it works. the obake fxzs/files (Maxx and Ultra) are the same. Obakem (note small m) is for the mini. the Maxx is distinguished on the box as Obake M (maxx). nonsensical, I know, but it is how they tag it at Moto.
[Paid Software Announcement and Discussion] nrgyitguy:
I have one ready to go in ext4 format already. The mofo FAQ states that if motoverify won't spit out a link then mofo will not work for my device, am I reading this wrong?...should I still contact maiko1 to ask if he can "open it up" or has he given me the answer in the FAQ that states it won't work for my device if mofoverify doesn't spit out a link?....
[Paid Software Announcement and Discussion] kitcostantino:
he stands to sell several licenses, so honestly, it shouldn't be a hardship to point you in the right direction. ( .02 )
[Paid Software Announcement and Discussion] JulesJam:
Is it rooted? If it is not rooted, he won't open up MoFo for your device.

---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------

That is the only way to get a copy of MoFo for your device.

If your ext4 image is not yet rooted, if you zip it and post it on mega.co.nz for me, I will root it for you. Then you can contact maiko1 and tell him you have a rooted ext4 image for your device and ask him to open up MoFo for your device.

---------- Post added at 04:48 PM ---------- Previous post was at 04:41 PM ----------

I am not sure what is so confusing to you. Maiko1 programmed moverify so that it only works for devices that have a rooted ext4 image available to be flashed. It makes no sense at all for anyone to pay for MoFo if there is not a rooted ext4 image available for them to flash.

If you have a rooted image available for your device, the ONLY way for you to get a copy of MoFo for your device is to contact maiko1, tell him you have a rooted ext4 image for your device that you want to test and ask him to reprogram moverify to include your device.

If you want maiko1 to open up MoFo for your device, you need to post your rooted ext4 image somewhere so that others can download it. I have been posting my rooted ext4 images on mega.co.nz and creating a thread in the Android Development forums of the Moto X 2014 forums. Then maiko1 links to that in his OP.

MoFo will work on any Motorola device running the 4.4.4 through 5.0.2 bootloaders. It will not work on any device running the 5.1 bootloader.

If you link me to your ext4 image, I will root it for you. If it is already rooted, then you can just contact maiko1 directly but before he opens up MoFo for your device, you will need to post your image so that others can download it.
[Paid Software Announcement and Discussion] adildroid29:
how to buy mofo root in the play store...? because they do not have a paypal
[Paid Software Announcement and Discussion] JulesJam:
MoFo isn't in the playstore and it never will be. Google would not allow it. If you don't have a US paypal account, you can create one using any US address and fund it and then buy MoFo. Once you create a paypal account with a US address, you can fund it by sending money to it from an international paypal account. I think you can also link a prepaid VISA or Mastercard to it if they are issued by US banks. If you link a prepaid VISA or Mastercard to it, you may have to register the VISA or Mastercard online to get a PIN for it so that it will be seen as a debit card.

The easiest way to do it is to create a paypal account in your country using your address. Then create a paypal account with a US address. Then send money from your international paypal account to your US paypal account and use the US paypal account to buy MoFo.
[Paid Software Announcement and Discussion] adildroid29:
Thanks instructions..
[Paid Software Announcement and Discussion] JulesJam:
[MENTION=5697730]maiko1[/MENTION] - there is a rooted image for 5.1 for the XT1094 posted in this thread along with instructions on how to flash everything but the bootloader and partition table to 5.1:

http://xdaforums.com/moto-x-2014/development/mofo-img-xt1094-5-1-rooted-image-t3172480

[MENTION=4587327]drlj78[/MENTION] tested it on his XT1094 and it works. Please add the link to the OP!

Also, I have added the rooted 4.4.4 image for the XT1094 to that thread.

[MENTION=4587327]drlj78[/MENTION] - if you get Xposed for Lollipop working in the 5.1 image, please upload it and let me know and I will post it in that thread so others who have an XT1094 and want Xposed can download it. Thanks!

---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------

[MENTION=5697730]maiko1[/MENTION] - [MENTION=5849464]mikeoswego[/MENTION]'s thread now has a rooted 5.1 image in it for the XT1096. Please update the OP, thanks!

---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------

[MENTION=5697730]maiko1[/MENTION] - there is a rooted 5.1 image available for the XT1097 along with instructions here:

http://xdaforums.com/moto-x-2014/development/mofo-img-5-1-rooted-att-xt1097-tether-t3162497

Please add it to the OP!!!
[Paid Software Announcement and Discussion] nrgyitguy:
So you don't think the image will work? What happened with the turbo you tried? Did the backup not flash or did it not boot when flashed? I agree about starting from a "proper" rooted image, which I am, but it would be awesome to make changes on my unlocked ultra, backup, and flash to locked ultra. Much quicker than mounting the image...
[Paid Software Announcement and Discussion] JulesJam:
The image must be the correct size otherwise it won't work.
[Paid Software Announcement and Discussion] kitcostantino:
it simply wouldn't flash it. JulesJam hit the nail on the head, though. I wonder if its possible to manipulate it though.
[Paid Software Announcement and Discussion] JulesJam:
According to maiko1:

If you already have root, then getting a mofo flashable system image from your device should be possible. Simplest way is to make the system block device readable by everyone (chmod 644), and then adb pull the block device to your computer.

I was not able to do an adb pull of /dev/block/mmcblk0p38 (which is where my system image is). This is how I did it instead. I started an adb shell then typed the command su. Then ran this command:

ls -l /dev/block/bootdevice/by-name

For my XT1096 that returns this:

1970-01-03 13:57 system -> /dev/block/mmcblk0p38

Now I know my system is in /dev/block/mmcblk0p38

Then I ran the command:

dd if=/dev/block/mmcblk0p38 of=/sdcard/system.img

Of course, your system file may not be in mmcblk0p38 so you have to find out where it is using the command above.

Then I pulled the image with adb pull command:

adb pull /sdcard/system.img c:\

If you already have an unlocked and rooted Ultra, pull the image following my steps above. Then contact maiko1 and ask that he open up MoFo to the Ultra. Please post your image so that others with an Ultra can use it.
[Paid Software Announcement and Discussion] scififan2715:
Mofoverify won't spit out a link for me, it just gives "version: 0.0.3" I'm on an XT1096 running 5.0. What's the problem?

Edit:running ubuntu fwiw
[Paid Software Announcement and Discussion] entropism:
Edit: Fixed it all. A hassle, and I'm not sure exactly what fixed it, but... At least it's done.
[Paid Software Announcement and Discussion] scififan2715:
I got it to work somehow, I played around in fastboot and toggled all the oem tags, and then it gave me the link. No idea if that's what did it, but if anyone's having the same problem, you might want to (carefully!) try that.
[Paid Software Announcement and Discussion] justinjbaron:
any chance of one of the pre rooted system images being updated w stagefright patch?
[Paid Software Announcement and Discussion] adildroid29:
How to update Lollipop rooted.?
[Paid Software Announcement and Discussion] JulesJam:
What device do you have and what version of Android are you running?

---------- Post added at 07:53 PM ---------- Previous post was at 07:53 PM ----------

You have to ask the devs who make the images. Maiko1 doesn't make the images.
[Paid Software Announcement and Discussion] raze5115:
Does mofo work on the 5.1 ota for verizon droid turbo yet?
[Paid Software Announcement and Discussion] scififan2715:
First make sure you get a device id from fastboot devices. If you do, try mofoverify again. If you don't, or it still doesn't work, make sure you're running both fastboot and mofoverify with admin permissions. If it still doesn't give you a link, try one of the commands under fastboot oem help. If it's a toggle, be sure to do the opposite one too. Then try fastboot devices and mofoverify again.

Disclaimer: Be careful in fastboot!! I was just playing around and mofoverify happened to work the next time I tried this, so no guarantees this affected it, but it might be worth a shot.
[Paid Software Announcement and Discussion] kitcostantino:
it probably never will. but [MENTION=5697730]maiko1[/MENTION] might be able to build in that "unlock" feature now. ;) idk. I just read stuff on twitter.

http://xdaforums.com/showthread.php?t=2927958
[Paid Software Announcement and Discussion] maiko1:
Done, thank you.
[Paid Software Announcement and Discussion] kitcostantino:
sunshine will soon support turbo, aleady supports Moto x 14. any chance a similar feature will come to mofo for the turbo?
[Paid Software Announcement and Discussion] LatencyXXX:
Need mofo.exe

I can't get my device verified. I know it is a XT1254 and I have ran mofoverify to give me the URL to post, but it is coming back with device not supported.

NOTE: I accidently did the OTA upgrade to 5.1 already and my phone is locked. I am thinking if I can just get the util to flash a rooted image it will work just fine.

I can pay the $20 but I can't even get to the payment / download sections.

Any body have any ideas or suggestions in what I need to do here?

version: 0.0.3

Found device: XT1254 ZX1F22R3ZJ
Visit the folowing link to verify your device:

https://mofo.disekt.org/verify/MC4wLjMvWFQxMjU0L2dpdD1NQk0tTkctVjcwLjg2LTAtZzg4YmZkZmQvODQ4MGRlZDY4YmYzNjczMWVlNWRlOTY0MTNhMjZlNTc2NjI5ZGU4Ni81ZDJlZDhjY2MzNzA2OWRlNWRkYjExNWZlMjgxNjAxZWQ4MjM5ZjYw
[Paid Software Announcement and Discussion] raze5115:
Your in the same boat I'm in which is totally screwed for mofo cause the mofo exploit was patched in the 5.1 bootloader. Which sucks for those of us that did the 5.1 ota update. You can try to get a replacement droid turbo sent to you & hope to god that it will still have 4.4.4 KitKat on it cause there isn't too many of those still around. Mofo only works on 4.4.4 KitKat on the droid turbo cause the droid turbo went straight to 5.1 from 4.4.4 & mofo works on 5.0 & 4.4.4
[Paid Software Announcement and Discussion] JulesJam:
I would try kingroot - if you can get temp root with kingroot, then you can pay for Sunshine unlock as soon as it supports droid turbo.
[Paid Software Announcement and Discussion] raze5115:
How much longer do we have to wait for sunshine to support the droid turbo?
[Paid Software Announcement and Discussion] JulesJam:
Idk and I would not ask the devs - they have asked that people not ask for ETAs, it just slows them down. I suspect that the DT is next.
[Paid Software Announcement and Discussion] LatencyXXX:
RE

I tried Kingroot. Doesn't work. I wasn't able to get it to work from the app itself.

However, I did turn on development mode, and enable debugging + USB + update bootloader (which isn't supported by MFG) and RK says it installed.

Yet, when you go back to the phone to do a root verify with any of the tools, it is not rooted.

I tried to flash it from bootloader mode also, but RK appears to just hang when connecting because I think the bootloader is locked.

Just going to have to wait I guess for sunshine.

Maybe there is a way to rollback the firmware to an earlier date and use the rooted img posted on rootjunkyssl.

Let me know if you are able to get it for DT!
[Paid Software Announcement and Discussion] JulesJam:
Sunshine requires temp root to work. If your bootloader is on 5.1, mofo won't work to give you root. If kingroot won't give you root, then you aren't going to be able to use Sunshine.

---------- Post added at 12:09 AM ---------- Previous post was at 12:07 AM ----------

There is no way to downgrade the bootloader. The only bootloader that I read was downgradable was one of the 5.1 Soak bootloaders.

---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------

That is an unsigned file. If your bootloader is locked, the only way to flash an unsigned file to /system is to use MoFo. But MoFo doesn't work if your bootloader is 5.1 bootloader. Only if your bootloader is on 4.4.4 and 5.0 and 5.0.2 can you use MoFo.
[Paid Software Announcement and Discussion] LatencyXXX:
RE: Bootloader for Droid Turbo

Okay, so if I understand correctly, since the bootloader is locked there is no way to put a different one back on?

Would I be able to fastboot flash an earlier version of the bootloader and if so where can I obtain these?

(I think you answered this as NO)

If NO, are the devs working on a fix for this or is it pretty much game over?
[Paid Software Announcement and Discussion] raze5115:
I hope it's not game over but I guess I shouldn't care because I'm going to get the note 5 by November 29th maybe sooner
[Paid Software Announcement and Discussion] JulesJam:
What version of the bootloader are you running - go into bootloader mode and it will tell you.

---------- Post added at 01:07 AM ---------- Previous post was at 12:54 AM ----------

If you took the 5.1 OTA and kingroot will not provide you with temp root, then hopefully kingroot will be updated in the future b/c w/o temp root, you cannot use sunshine. And MoFo doesn't work on the 5.1 bootloader and there is no way to downgrade your bootloader.
[Paid Software Announcement and Discussion] LatencyXXX:
RE: Bootloader for Droid Turbo

Android Version: 5.1
API Level: 22
CPU ABI: armeabi-v7a
MFG: Motorola
Baseband: MDM9625_104651.11.05.16R QUARK_CUST
Bootloader: 0x7086 / moto-apq8084-70.86 (4/06/2015)
Radio: Unknown
Board: APQ8084
Device: Quark
Display/ID: SU3TL-39
Model: XT1254
Product: quark_verizon
User: hudsoncm

Device is LOCKED. Status Code: 0
Software status: Official
[Paid Software Announcement and Discussion] JulesJam:
I can't find a listing of the bootloaders for the DT anywhere but if you took the 5.1 OTA then 70.86 must be the 5.1 bootloader. You can't downgrade the 51. bootloader and MoFo won't work on 5.1 bootloader. Hopefully Kingroot will be updated to provide temp root for the 5.1 bootloader.
[Paid Software Announcement and Discussion] cadenmiller60:
Jcase says that root for turbo on 5.1 should be "trivial" so it shouldn't matter.
[Paid Software Announcement and Discussion] JulesJam:
Where did he say that?
[Paid Software Announcement and Discussion] cadenmiller60:
On his twitter account and this has also been mentioned in the turbo section.
[Paid Software Announcement and Discussion] JulesJam:
This is what I see on rootninja:

Unfortunately Droid Turbo support is going to take a lot of work, much more than expected. We will not comment on ETAs for it, sorry.
[Paid Software Announcement and Discussion] cadenmiller60:
That's not jcase's twitter. Search for Justin Case or just Jcase. And yea I've seen that too but it sounds like there is still hope, if not for unlocked bootloader then for root. Also it may take awhile to find as he posted this a few days ago.
[Paid Software Announcement and Discussion] JulesJam:
Rootninja = jcase + beaups. It is their Sunshine twitter account.
[Paid Software Announcement and Discussion] maiko1:
Make sure you copied the link correctly.
[Paid Software Announcement and Discussion] detonation:
Actually it seems like people like you expect devs to put in countless hours of work and cover the cost of new/bricked devices for nothing. Just because previous root exploits have been offered free doesn't mean future ones have to be...the community owes you nothing.
[Paid Software Announcement and Discussion] TokedUp:
Any chance of this working for Moto X 2014 VZW XT1096?
[Paid Software Announcement and Discussion] bmdhacks:
I suppose we have to wait for somebody to craft a system image with supersu and xposed on it then?

Or is it relatively simple to put those on a stock image?
[Paid Software Announcement and Discussion] ProfessorStein:
I'm with you (even commented on this before)... but as I browsed back through the forums, I remembered that there was actually a bounty posted for root, as well. It does seem marginally disingenuous to take the bounty and charge the community for the root. But I have no idea if Maiko took/will take the bounty, either... so that's as far as I'm going to go with that.

{head slap} Really? You're being sarcastic, right?

From Root Junky's video, it would appear that SuperSU gets installed or is on the recommended image already. So you'd only need to get xposed on there.
[Paid Software Announcement and Discussion] dmginc:
I guess I'm confused. What does/doesn't survive root? Can I install xposed modules? Will adaway work?
[Paid Software Announcement and Discussion] n00b1269:
I agree.

My only thoughts are if you are charge for the root, shouldn't get the bounty.

But either way, I'm thankful its out and will pay for it
[Paid Software Announcement and Discussion] ptcfast2:
$20 well spent. Have to start somewhere!
[Paid Software Announcement and Discussion] Harry44:
Did you find one?
[Paid Software Announcement and Discussion] 123421342:
Correct me if I'm Wrong but this seems like a poor man's unlock? Can basically flash any system image that works?
[Paid Software Announcement and Discussion] Character Zero:
Its not like the bounty is sitting in an escrow account or anything. I am sure most people will take paying $20 as thie "bounty". Others are free to give them more money if they choose.
[Paid Software Announcement and Discussion] speedfreak228:
If I do this can I installed exposed and its modules? That's my only concern
[Paid Software Announcement and Discussion] detonation:
Since the bounty pledges are on the honor system, I'm assuming most people who pledged consider this purchase their bounty payment. Looking at the thread, the average root pledge was around $25, so if anything, those people are getting off cheaper. Not to mention if this was free, I'd be surprised if the bounty collection reached even 10% of what was pledged.
[Paid Software Announcement and Discussion] JGoldz75:
We as a community are very thankful for the root exploit! From purely a marketing perspective, it may be best to give out licensing codes for the first day or two at least so people can find any bugs with the program instead of paying and having nothing. Once the root method has been cleaned up of bugs and questions have been answered, that's when the masses will start rolling in, and also when your profits will start rolling in.

But hey, that's just my 2 cents (or in this scenario, 2,000 cents)
[Paid Software Announcement and Discussion] ProfessorStein:
Very true. :svetius:
[Paid Software Announcement and Discussion] Coronado is dead:
Well, I assume most people would not have paid with write protection still on.
[Paid Software Announcement and Discussion] golgothagecko:
Who would pay a bounty for this crippled root? You can't even use Adaway with it.
[Paid Software Announcement and Discussion] twinkyz1979:
So am I correct in saying if you change the system image OTA updates won't work? If I am right please keep this in mind as it is a double edged sword.
[Paid Software Announcement and Discussion] jasoraso:
If that is correct, you would merely need to flash back an original system image.
[Paid Software Announcement and Discussion] rgerrans:
To add two items to the discussion.

1) I have my phone encrypted and it didn't have any problem updating (just in case there were any concerns by others)

2) The first time I ran mofo flash it quit at 7% and put me in a bootloop. I was able to just get back into fastboot and rerun mofo and it worked the 2nd time. Didn't loose any data either so didn't have to go back to stock image to get it running.
[Paid Software Announcement and Discussion] cadenmiller60:
Oh ok. Well the post I saw is on jcase's personal account then. Sorry for the mix up.
[Paid Software Announcement and Discussion] Yonnor:
So I downloaded the latest version of mofoverify

from the disekt site

and apparently the it's outdated....
[Paid Software Announcement and Discussion] Joeywhat11:
Anyone have this issue: My copy of Mofo no longer works, says "no more valid purchases" when I try and flash. I can't even buy a new copy as the link it generates just takes me right to the download page. It appears I have the right copy of the software for my phone, but for whatever reason it doesn't seem to think so.

Any help on this? I'm in the middle of flashing a rooted 5.1 image and I'm screwed without mofo to finish up. Would kinda enjoy having an operation phone this weekend. Email already inbound to the developer, but I imagine I won't get a reply until Monday rolls around.
[Paid Software Announcement and Discussion] kitcostantino:
Let's back up. What Mofo Version are you on? (1, 2, 3?) Well, most recently. I would delete all mofo files and start over. (I did this myself). Download a fresh copy of mofo verify, then do it all over. If you are stuck without a functional phone, and somehow have to have one for mofo verify, I would fxz back to 21.15.15, do the 2 otas to 22.44.8 and 22.44.12, and then start over. Sucks, I know, but it may be what ya have to do. Make sure when you set it up again that python is right. (Details on 1st page) it is odd it would stop working unless you somehow changed or modded your imei or something like that. I hate that for ya though. I had to do a mofo reset similar to yours around v2, and did it again of my own volition to update to v3. Good luck.