yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] koftheworld:
Right now we just have the dumps here http://xdaforums.com/showthread.php?t=3147455 thank you very much [MENTION=5983610]JulesJam[/MENTION]

The ota is located on rootjunky's dl page but no fxz exists yet.
[Paid Software Announcement and Discussion] JulesJam:
What are the dumps? Are they ext4 images?
[Paid Software Announcement and Discussion] koftheworld:
There are a few versions. Honestly I'm not sure what these guys did.
[Paid Software Announcement and Discussion] weaver11b:
I just did an adb pull /system to get the system dump. That's what someone wanted me to do for computerfreek
[Paid Software Announcement and Discussion] JulesJam:
try to find out what these are. I need ext4 images.
[Paid Software Announcement and Discussion] koftheworld:
Looks like these are straight pulls off the system folder for 5.1 (one being a zipped version). I've asked that a ext4 version is made for you, but we'll see.
[Paid Software Announcement and Discussion] dmbtech:
Depending on the way the OTA was constructed, if someone has the raw ota zip itself, if you extract it the system.img should be an ext4 image.
[Paid Software Announcement and Discussion] JulesJam:
The OTA is a patch, not a full image. It is much smaller file than the fxz. The full images are 1.3GB even compressed. They are not going to push those size files OTA so instead they push patches.
[Paid Software Announcement and Discussion] xMIChael91x:
So I can update my phone to the new 5.1 and then when the img is created for the new 5.1 with root and stuff and can still flash that
[Paid Software Announcement and Discussion] raze5115:
I want to know the answer to that question too so I can have root on my phone since I already updated to the new 5.1 img.
[Paid Software Announcement and Discussion] xMIChael91x:
Right I don't want to update my phone to 5.1 from the OtA unless I know I can flash a img later
[Paid Software Announcement and Discussion] raze5115:
I'm just impatient. I got to have everything new as soon as it comes out as far as operating systems go at least. Whether it's windows or android.

---------- Post added at 05:47 PM ---------- Previous post was at 05:41 PM ----------

Well I won't have this phone for very much longer cause on november 29th I'm upgrading to the note 5 which is easier to root for me at least. at least I hope it will be easier to root then the turbo and less chance of softbricking it.
[Paid Software Announcement and Discussion] JulesJam:
I need the 5.1 ext4 system image from the AT&T XT1097. I can't find it. Do you know if one exists?

---------- Post added at 12:30 AM ---------- Previous post was at 12:28 AM ----------

No, you cannot take the 5.1 OTA if you want to use MoFo. You cannot upgrade to the 5.1 bootloader if you want to use MoFo. MoFo won't work on the 5.1 bootloader.

What we have done on the XT1096 is to manually flash the 5.1 kernel/ramdisk, recovery and radios , then flash a pre-rooted 5.1 system image using MoFo. That way we don't upgrade to the 5.1 bootloader or partition table. We stay on the 5.0 bootloader (motoboot.img) and partition table (gpt.bin) so that MoFo will still work.

---------- Post added at 12:33 AM ---------- Previous post was at 12:30 AM ----------

If you took the 5.1 OTA, you have upgraded your bootloader to the 5.1 bootloader and MoFo will not work on the 5.1 bootloader.

---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------

You need to stay on 5.0.2 if you want MoFo to work.

I need the 5.1 system image in ext4 format for the AT&T XT1097 in order to root it.
[Paid Software Announcement and Discussion] ahaynes42:
Does anyone have an idea of what this means for us with Turbos? We never got a 5.0.x version. Jumped from 4.4.4 straight to 5.1. To me it sounds like 5.1 is totally incompatible. Doesn't look good for us. I don't know how long I'll be able to sit and wait on rooted 4.4.4.
[Paid Software Announcement and Discussion] JulesJam:
It all depends on how similar the partition tables are b/t 4.4.4 and 5.1. You can tell that by the size of the files. I have asked about this for the DT but no one has answered. Compare the sizes of the boot.img, system.img, etc b/t 4.4.4 and 5.1 and that will give you an idea of whether or not you can flash the 5.1 files while staying on the 4.4.4 bootloader and partition table.

There may be additional issues with the bootloaders idk, someone will have to try it to know.
[Paid Software Announcement and Discussion] ahaynes42:
Thanks for the response. I will try and look into it. We are having a little trouble getting detailed info about the 5.1 update because it seems most of the people who are knowledgable about this kind of stuff stayed on 4.4.4 for fear of losing a root path.
[Paid Software Announcement and Discussion] JulesJam:
Someone leaked the XT1096 5.1 fxz otherwise we wouldn't have it yet. I don't know where it came from, someone posted a link in the MX14 General forum to a site that had a bunch of Moto X images for various devices.
[Paid Software Announcement and Discussion] koftheworld:
Exactly. I would look into it but lollipop isn't essential to having a working phone so I stood still on the ota.
[Paid Software Announcement and Discussion] JulesJam:
Well the good news is that it is now clear that you have to delete the contents of BOTH /data/dalvik-cache and /cache before you boot into bootloader mode to upgrade to 5.1 (everything but the bootloader and partition table that is) and that resolves all of those weird issues with recovery. Then you flash the 5.1 files for logo, kernel/ramdisk, recovery, modem and basebands. Then you use MoFo to flash the modified 5.1 image and boot into system.

If anyone can get the system.img_sparsechunks for the AT&T XT1097 I can root it for you.

---------- Post added at 05:41 AM ---------- Previous post was at 05:37 AM ----------

Stay on 4.4.4 - I think there are people working on getting the 5.1 droid turbo ext4 image rooted and it looks like it may be the same size as the 4.4.4 ext4 image so it should be flashable by MoFo if you don't upgrade your bootloader and partition table.

On the MX14, you need to delete the contents of /data/dalvik-cache and /cache BEFORE you upgrade to 5.1. And of course you need to flash the signed 5.1 logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn too. We have Xposed for Lollipop in our image and that may have something to do with having to delete the contents of those folders, idk, but I do know that when I didn't do it, all kinds of weirdness happened.
[Paid Software Announcement and Discussion] aviwdoowks:
How is it that KingRoot works identically on the Turbo and Droid Ultra

, yet Mofo does not work on the Ultra?

On both phones root last from 15 min for Ti BU to days for gravity box and other Xposed modules.

Thanks
[Paid Software Announcement and Discussion] JulesJam:
MoFo will work on the Ultra but you need a pre-rooted image for maiko1 to open it up to you. What version of Android are you running? If you are running 5.1 it won't work, but if it is lower, then it will work. I can teach you how to make a pre-rooted image.

What version are you running? Where is the fxz?
[Paid Software Announcement and Discussion] kitcostantino:
ultra/maxx aren't on 5.1 yet. I have a dev maxx if you guys need an image pull. note, not ext4 img. be more than happy to give a willing recipient a stock twrp backup to work from it. well, actually system. [MENTION=4789347]chuck864[/MENTION] sound good?
[Paid Software Announcement and Discussion] aviwdoowks:
444 su 6-7.2.
[Paid Software Announcement and Discussion] JulesJam:
Do you have the fxz? Sparsechunks are preferred.
[Paid Software Announcement and Discussion] ilia3367:
I am willing to pay again! Please, make MOFOROOT for 5.1 TURBO! :crying: :(
[Paid Software Announcement and Discussion] JulesJam:
The exploit is closed in 5.1. Hopefully maiko1 can find another exploit.
[Paid Software Announcement and Discussion] ilia3367:
I hope so too! Without this TURBO it is meaningless to me ...
[Paid Software Announcement and Discussion] kitcostantino:
this sucks. didn't you make our unbrick?
[Paid Software Announcement and Discussion] ilia3367:
But this theme not about it.
[Paid Software Announcement and Discussion] xt1080 brick:
system version: 24.13.2.obake-maxx_verizon.Verizon.en.us

Android version : 4.4.4

build number: SU6-7.2
[Paid Software Announcement and Discussion] JulesJam:
Ok, I think I found a single file system.img. It is the same as for the Droid Maxx. The only thing is that it is not in sparsechunks so I am not sure if it is in ext4 format or not. I will need to figure out how to find out if it is or not.
[Paid Software Announcement and Discussion] aviwdoowks:
Do we need a donor from an unlocked ultra?
[Paid Software Announcement and Discussion] kitcostantino:
I'll be your Huckleberry
[Paid Software Announcement and Discussion] kitcostantino:
Also. I just flashed my unlocked mini to 7.2 today as well.

Here are the system.img files pulled from TWRP along with the md5. If that is what you were needing at least, [MENTION=5983610]JulesJam[/MENTION] or whoever may need them

edit: droid maxx: https://drive.google.com/file/d/0B5at-W4JhbXDWGkzQXR5RlFUX2s/edit?usp=docslist_api

Edit 2: Droid mini: https://drive.google.com/file/d/0B5at-W4JhbXDYTF6a1dsUlVNMzg/edit?usp=docslist_api
[Paid Software Announcement and Discussion] aviwdoowks:
So is the twrp img format usable in this case?

How can we use that to flash an locked Droid?
[Paid Software Announcement and Discussion] kitcostantino:
Jules had asked for an ext4 system img for possible use for Mofo. On my unlocked Droids, TWRP backs up sysyem. Img in that format. I figured if not her, then someone else might want to expand Mofo to the obake. So to answer your question, with Mofo, of course. :)
[Paid Software Announcement and Discussion] marksibert:
Sorry for the public post. I've sent maiko a few emails/pms over the past few weeks about my warranty-replaced Turbo, but haven't gotten a response. (So I have no idea if he is seeing my messages or if they're getting lost en-route.)

I bought mofo for my old Turbo, which had to be replaced because the screen cracked. I would like to use mofo on my new Turbo. Has anyone been able to transfer mofo to their new device in this situation, or are people just biting the bullet and buying mofo a second time? Thanks!
[Paid Software Announcement and Discussion] aviwdoowks:
LP, when it comes to the 2013 Droids, might be subject to the same workaround as the Turbo http://xdaforums.com/showpost.php?p=61846026&postcount=5.

If so getting root without the risky bricking & and many other error prone steps of our present permanent free method would be great.

Many are hoping for the best of LP with sure root.
[Paid Software Announcement and Discussion] nrgyitguy:
He was quick to respond to me. he told me to purchase again if it was within 90 days since first purchase he would refund first purchase when I sent him a copy of the new link and the original payment account id. I was refunded in 24 hrs of sending the required materials.

---------- Post added at 11:43 PM ---------- Previous post was at 11:35 PM ----------

are you saying I can flash a pre rooted image, which I could possibly obtain through TWRP from my unlocked rooted Ultra (as long as it is the at the same level software, i.e. SU6-7) :confused:on to my locked ultra with a new purchased copy of mofo?...
[Paid Software Announcement and Discussion] kitcostantino:
Not exactly. The only criteria asked for was a EXT4 image. I pulled it in hopes that works. If it did, it would make life way easier.

For instance, if that were the case, you could tell me "hey, I need ______ (apps that require wp off + root)" then, I could set that up, make a backup and send you the img. I am sure it cant be that simple.

Oddly enough, I asked a question by making an offer.

I will say this, though, if you tried, I don't think it could hurt. Mofo is set up to flash whatever. Worst case, it would be fxz time. What do you think [MENTION=5697730]maiko1[/MENTION] ? Any viability to that?
[Paid Software Announcement and Discussion] redwings73:
Does anyone know how a Moto Care replacement phone is handled with MOFO? Am I able to transfer the license I purchased to the replacement phone or will I need to purchase again?
[Paid Software Announcement and Discussion] nrgyitguy:
Once I have my pre-rooted img what do I need to do for "maiko1 to open it up" for the Ultra?

---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------

Post 694 right above your post a couple....
[Paid Software Announcement and Discussion] redwings73:
So, that's what they mean by "search", huh?.... Sorry about that.
[Paid Software Announcement and Discussion] marksibert:
Some people have had success transferring their license. I have sent multiple emails and have yet to get a response.
[Paid Software Announcement and Discussion] JulesJam:
Does anyone have the firmware in ext4 form for this device? If someone has the sparsechunks then those can be coverted to a single image ext4 using SparseConverter.exe utility.
[Paid Software Announcement and Discussion] nrgyitguy:
will what kitcotantino posted work? or is that not the full firmware? If I can help I will. Im not sure what I need exactly to get the fxz but I will keep researching. I have an unlocked ultra, its currently on su4.21 though, I havent updated it. I wonder if I can download the nagging update and pull it off the phone. Willing to do what I need but I need to educate myself a little more...Thank you for your help JulesJam...:good:
[Paid Software Announcement and Discussion] JulesJam:
Idk if that is in ext4 format or not.. I am sure there is some linux command that will tell you but I don't know how to do that. I know how to do it if you have the system files in sparsechunks.
[Paid Software Announcement and Discussion] redwings73:
I tried contacting maiko.... No luck yet in a reply from him/her.
[Paid Software Announcement and Discussion] kitcostantino:
it is for sure an ext4 format. at least thats what twrp says it is. the $20 question is if it is flashable by mofo.
[Paid Software Announcement and Discussion] kitcostantino:
TWRP

you may have to play the rename game, but literally, that used to be the instructions to make a rom from a backup. pull system.ext4.win, rename win to img amd profit
[Paid Software Announcement and Discussion] nrgyitguy:
I cant seem to get the links to download anything...:confused:
[Paid Software Announcement and Discussion] JulesJam:
If it is ext4, it is flashable by MoFo. The issue is if there are any headers/footers, etc. and will it boot.
[Paid Software Announcement and Discussion] redwings73:
I posted this on the Moto X General, too... Thought I'd give it a shot here.

Has anyone received a moto care replacement phone recently? Curious if it came with 4.4 (unlikely), 5.0, or 5.1. Asking because I'd like to continue to use MOFO.
[Paid Software Announcement and Discussion] kitcostantino:
ya gotta press the little white arrow (center, top)
[Paid Software Announcement and Discussion] kitcostantino:
like this:
[Paid Software Announcement and Discussion] nrgyitguy:
They keep downloading 0kb zip files
[Paid Software Announcement and Discussion] kitcostantino:
yup. odd. gotta pull again. apparently, the mini one works. gotta get the maxx back to stock. any requests? lol
[Paid Software Announcement and Discussion] nrgyitguy:
The links keeps downloading a 0kb zip file

---------- Post added at 06:54 PM ---------- Previous post was at 06:47 PM ----------

I got "network failed" after a few moments with the mini link. I would like root(obviously), tethering and xposed, if we can get this to work Ill make the $20 commitment!....Thanks for your help:good:
[Paid Software Announcement and Discussion] kitcostantino:
its going. no md5. direct file not in a folder just to make crap easier.

edit: also, i went ahead and renamed it .img. hopefully this works. backup your data before trying, just in case.
[Paid Software Announcement and Discussion] kitcostantino:
https://drive.google.com/file/d/0B5kIFKwbboYYckdhTXg4UjFIejg/view?usp=docslist_api

to whomever tests this TWRP backup image theory, if it works, and you want something specific, lmk.
[Paid Software Announcement and Discussion] kitcostantino:
I wish I could find someone with a Moto Maxx CDMA variant that is rooted to test the theory. I guess the system from the gsm xt1225 might work since radio is unaffected. [MENTION=3250376]ChazzMatt[/MENTION] ya got a few min to upload a sys.img from a stock TWRP backup?
[Paid Software Announcement and Discussion] nobreak1970:
Think we may be able to use mofo or a derivative to root the Verizon Moto E 2015?
[Paid Software Announcement and Discussion] ChazzMatt:
All my TWRP backups from stock 4.4.4 are here, from both Mexico and Puerto Rico XT1225 phones:

http://xdaforums.com/droid-turbo/development/moto-maxx-moto-turbo-xt1225-factory-t3078274

This one below is to "pure" Mexico stock...

I booted to ADB, booted TWRP using one-time method. Made a back-up.

__________________________________________________ ____________

MOTO MAXX IMAGES (XT1225) - MEXICO

SYSTEM VERSION: 21.11.9.quark_retla.retla.en.01 retla

BASEBAND VERSION: MDM9625_104335.118.0254R, QUARK_SINGLELA_CUST

http://www.mediafire.com/download/nro3q9vdveb7k0z/MOTO_MAXX_XT1225_MEXICO_FACTORY_IMAGE.zip

MIRROR: https://onedrive.live.com/?cid=ef2f93777d6101b5&id=EF2F93777D6101B5!128

This is pure Mexican Moto Maxx Kitkat 4.4.4 XT1225 Factory Image -- unrooted, no TWRP residing in recovery.

_________

Other TWRP images on that page do include root and permanent TWRP, but this one was made from "temporary" TWRP backups with no root.

These are the contents of the TWRP backup zip file:
[Paid Software Announcement and Discussion] AlienZombieEater:
I mofo'ed a 5.0 image successfully and verified root access but I can't seem to delete the /data/dalvik-cache/arm directory, my file manager attempts then says that it can't be deleted. It successfully deleted the other folder there. Any pointers?
[Paid Software Announcement and Discussion] kitcostantino:
[MENTION=3250376]ChazzMatt[/MENTION] you are awesome, brother. thank you. I'm going to test the theory later tonight. ;)
[Paid Software Announcement and Discussion] raze5115:
So can we root a droid turbo running the ota 5.1 lollipop update
[Paid Software Announcement and Discussion] tslovejoy1969:
Not at this time. Maybe never. The exploit used by MOFO no longer exists after the 5.1 update.
[Paid Software Announcement and Discussion] aviwdoowks:
[MENTION=5697730]maiko1[/MENTION]

Can you or others help me (or others) with the steps needed to make this image? Which would be KK 444.

Or are we nearer than I know?
[Paid Software Announcement and Discussion] GeoFX:
Windows 10 compatible?

Microsoft just rolled out Windows 10 today. Is MOFO compatible with the new OS?
[Paid Software Announcement and Discussion] beefytr:
blinking recovery icon after mofo root flash

thanks for all the tutorial mate.

a simple question...

everything went well and the mofo flash completed.

when i try to enter into the recovery i get nothing but a blinking dead android icon every 4 seconds.

the system does not boot at all.

any remedy as i am stuck with non responsive gadget?

cheers,

edit: problem solved!

the dead android icon was blinking every four seconds and the gadget was letting me do nothing.

then I went thru BP TOOLS and booted the phone.

then I did a factory reset and that's it!

the phone is back and alive.
[Paid Software Announcement and Discussion] raze5115:
So just for clarification if I already took the ota 5.1 update mofo will not work right?
[Paid Software Announcement and Discussion] JulesJam:
Can you delete your mega quote of the OP? It is unnecessary and bogs down the thread.

---------- Post added at 08:40 AM ---------- Previous post was at 08:36 AM ----------

Yes if you read the threads on the on the Moto X 2014 forum regarding MoFo and 5.1, you can't boot into recovery first.

---------- Post added at 08:41 AM ---------- Previous post was at 08:40 AM ----------

There is a thread on the Moto X 2014 General Forum with instructions on how to root and modify an ext4 image. I am the OP of that thread so if you search for threads I started, you will find it.

Maiko1 has never made a single image so I doubt he would be making one for the Ultra.

---------- Post added at 09:06 AM ---------- Previous post was at 08:41 AM ----------

As long as you are running the 4.4.4, 5.0 or 5.0.2 bootloader and partition table, yes.

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

Not if you took the 5.1 OTA.

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

What is the difference b/t the Droid Maxx and Droid Mini firmware? Is this stock 4.4.4?
[Paid Software Announcement and Discussion] tslovejoy1969:
Right.
[Paid Software Announcement and Discussion] kitcostantino:
the mini and maxx have subtle differences. audio, for one is a hair different for no good reason. also, the mini has an led indicator where the maxx does not. the TWRP img flash theory didnt work for me. perhaps someone else had better luck. ultimately, i think one could perhaps utilize a twrp image, but it is beyond my scope.
[Paid Software Announcement and Discussion] nrgyitguy:
I finally got around to attempting to purchase mofo for an Ultra to attempt to flash the image you so kindly provided. I cannot get motoverify to spit out a verification link...bummer. Thanks for your help anyway...
[Paid Software Announcement and Discussion] kitcostantino:
the image likely will not work. a few posts up, i had tested said theory on my turbo with a XT1225 backup. im not saying one couldn't mount it in linux and mod it, *perhaps* (a la eekoria's tutorial), but if you are going to do all that, you may as well make a full image from a proper system.img;) as far as mofo verify, it can be tricky to get python set up. make sure you use the exact version specified. [MENTION=5697730]maiko1[/MENTION] has been really good about support. just shoot an email, and they should get it sorted. in all honesty, it took me a couple times of going through the setup steps to realize i was not adding python to my path. small nuance/detail, but missing that step = no dice.
[Paid Software Announcement and Discussion] nrgyitguy:
My turbos have no problem with motoverify. The Ultra though doesn't want to spit out a link...I'm happy to make an image but I don't think I can get motoverify to get me a link for my Ultra. What image did you provide exactly? Was it su6-7.2 rooted from a twrp backup?...
[Paid Software Announcement and Discussion] kitcostantino:
yes. im currently running the same, but with exposed and several modules. (ad away, gpte, holo themer, hk theme manager, you tube adaway, and a few more.) they all afaik, write to /data. im more than happy to make a backup w/ xposed if needed. the other TWRP backup may have exposed, it may not. it is rooted, though, and i *believe* has nothing stripped. (bloat). if you can get it to work (twrp image) i am more than happy to set up whatever you want before i do a backup.
[Paid Software Announcement and Discussion] nrgyitguy:
Thanks man. I just tried a couple ultras and I couldn't get either one to spit out a verification link with moto verify. I can unplug the same cable and plug in one of my turbos and moto verify spits out of link no problem. I believe I have the correct drivers I can do anything I need to do with the Moto ultra except use moto verify. fast boot works and adb work. I know that doesn't necessarily mean that I do have the correct drivers installed however the FAQ for mofo states that if I don't get a link return than it won't work for my device, and that's exactly what happens...
[Paid Software Announcement and Discussion] kitcostantino:
No problem, man. I hate to say, someone had to be the first monkey shot into space. i guess the Ultra/Maxx are not compatible. I use both a Mofo'd Turbo and a "Dev" maxx (sunshine) as my DDs. If the new Moto X Pure (2015) is bl unlockable, my Employee Edition Turbo is hitting Ebay. lol. i appreciate mofo, but its nothing close to BL unlock. LMK if i can help, dude.