yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] lovetohustle:
Flashed Stock Moto X 2014 - XT1097 Stuck At Moto Screen

Hey Guys I followed directions from https://www.youtube.com/watch?v=AXAYjbf76II&feature=youtu.be to flash Moto X 2014 - XT1097 - 5.0 on my Moto X 2014 but I am stuck on the Motorolla logo screen at boot up. Any ideas on how to solve this issue? I paid for the $20 mofo root and followed the directions. Any ideas? Please thanks!
[Paid Software Announcement and Discussion] JulesJam:
You have the ATT XT1097 right? You have to wipe cache after you flash the MoFo image before you boot into system.

With your phone not connected to a computer or a wall charger, press and hold the power button until your screen turns off. Then immediately press and hold the volume down button for 2 seconds and while still holding it, press and hold the power button for about 3 seconds then release both buttons to get into bootloader mode.

Then use volume down to scroll to recovery, then use volume up to select recovery. When the dead android appears on your device, press and hold the power button for 2 seconds then while still holding it down, press and release the volume up button to get into the recovery menu.

Once in recovery, use the volume down button to scroll to wipe cache and the power button to select it. After the cache wipe is complete, then press the power button to boot into system.

Please read my noob guide here:

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
[Paid Software Announcement and Discussion] lovetohustle:
Yes I have an ATT XT1097 I get into bootloader mode and go down to recovery and hit it and my phone just shuts off or goes black,
[Paid Software Announcement and Discussion] JulesJam:
When in bootloader mode, you use volume down to scroll to highlight recovery and use volume up button to select recovery (not the power button). Then give it a minute for the dead android to appear (has a red triangle with an exclamation point coming out of its stomach).
[Paid Software Announcement and Discussion] lovetohustle:
Okay I have a dead android with his belly open just idle not doing anything. What should i do now?
[Paid Software Announcement and Discussion] JulesJam:
I wrote it out for you here:

http://xdaforums.com/showpost.php?p=60943048&postcount=524

be sure and read my noob guide too.
[Paid Software Announcement and Discussion] lovetohustle:
Thanks I got it! My last ? is how come when I open up google play store it doens't function properly? it just keeps spinning round and round,
[Paid Software Announcement and Discussion] JulesJam:
Try rebooting. Also make sure you are signed into your google account.
[Paid Software Announcement and Discussion] xlightwaverx:
I got it working, thank you.
[Paid Software Announcement and Discussion] lovetohustle:
JulesJam when I try getting into recovery after flashing AT&T XT1097 system IMG using MOFO it says hab check failed for recovery failed to vaildate recovery image boot up failed. I cannot get into recovery mode to wipe cache after flashing the image. Please any help would be greatly appreaciated Im not sure what to do.
[Paid Software Announcement and Discussion] JulesJam:
Post on the noob guide thread on the Mx14 rather than here. I will answer there. Also, if you want someone to notice your post, you need to quote them so that they will get a notification that you are quoting them.

---------- Post added at 10:57 PM ---------- Previous post was at 10:29 PM ----------

Can you please add a link in the FAQs section of the OP to my Noob Guide for Rooting the Moto X 2014:

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375

Thanks.
[Paid Software Announcement and Discussion] JakeDHS07:
Just got my replacement Turbo in the mail. Does anyone know the process for moving my Mofo purchase to the new IMEI? Is there an automated way on the site to DIY or something?
[Paid Software Announcement and Discussion] kitcostantino:
step 1: add $20 to pay pal account. step 2: purchase license. ;) okay, someone had to say it. afaik, [MENTION=5697730]maiko1[/MENTION] had stated (pretty clearly) that the license cannot be transferred. idk if there is an *exception* to the rule, but w/o a way to verify you aren't (not you, literally, just hypothetically and figuratively) just trying to grab an extra unlock for a buddy, it actually makes sense. i mean, the majority of turbos have one free screen replacement. that would mean potentially all Turbo mofo'rs could just grab a free unlock for someone else. not that i think its good to pay twice, it just really doesnt seem like something i would do if i were him. Perhaps I'm wrong.
[Paid Software Announcement and Discussion] JulesJam:
Someone could submit the repair information that you get from Motorola to prove it. Of course people could try to fake that.
[Paid Software Announcement and Discussion] kitcostantino:
idk. the reality is it is a per IMEI service. perhaps it could be looked as at a deductible of sorts. before I bought it I knew if I borked my Turbo and happened to get another one I would be paying $20 again. really I'm not trying to sound like a richard. i just knew that going into it, and think it was pretty clear.
[Paid Software Announcement and Discussion] JakeDHS07:
Just found this in OP. Now just waiting for a response.
[Paid Software Announcement and Discussion] JakeDHS07:
Sorry first post failed to attach
[Paid Software Announcement and Discussion] kitcostantino:
that's actually pretty awesome. i can see either pov, but seriously cool.
[Paid Software Announcement and Discussion] ahaynes42:
I just went through the same process. You buy a new license then they'll refund you the old one.
[Paid Software Announcement and Discussion] hotpass105:
Hi, I contacted you via email regarding my damaged device and an additional code; however, I have yet to hear back. Thanks!
[Paid Software Announcement and Discussion] Alex.Abraham:
Hey I noticed the su binary is outdated. Is there a way to update without reflashing? Is it really necessary or can I mute notifications for su in notification center?

Thanks! Great work :)
[Paid Software Announcement and Discussion] JulesJam:
I would ask the devs who made the images if they can update the su binary.
[Paid Software Announcement and Discussion] drlj78:
Thanks, But I don't need help making a system image, my question is whether the moforoot will support the xt1094. Currently on 4.4.4 when I run it, it says it does not. Should be similar to the Verizon unit though I'm assuming?

Thanks!
[Paid Software Announcement and Discussion] JulesJam:
First, the RW MX14 is nothing at all like the Verizon MX14.

Second, I understood your question completely but you don't understand what I am saying. Maiko1 will not open MoFo for your device until you or someone else make a pre-rooted system image for the XT1094. Go back and read the information in the link I posted. It answers your question completely - the starting point is getting the fxz for your device. Do you have it?
[Paid Software Announcement and Discussion] drlj78:
Gotcha, Ok, yes I just downloaded the fxz. So I should now go about extracting the system image from it?

Thanks!
[Paid Software Announcement and Discussion] JulesJam:
if you post it to mega.co.nz (it is free to sign up) I can take a look at it. if the system.img is a single file it is easier than if there is sparse chunks.
[Paid Software Announcement and Discussion] drlj78:
Here is the fxz: https://mega.co.nz/#!WRxzSSwL!ZvtjWtxLmP9QmxQxfHs6MvghxaL55jl0q8VkDuD4LmM

Thanks!
[Paid Software Announcement and Discussion] doanerock:
mofoverify issue

I am trying to run mofoverify on CentOS Linux release 7.1.1503 (Core), yes libusb is installed and it is recognized by the os. Why is mofoverify only displaying the version number?

UPDATE: I ended up getting it working on a windows VM.
[Paid Software Announcement and Discussion] JulesJam:
Here are 2 ext4 system files that should be flashable by mofo. The first one is an unrooted stock system:

https://mega.co.nz/#!BtVFgZLZ!OKBysFjk0ChV-xoXTfowNHi_gkrGOMtlJtW6yOLS370

MD5 of the unzipped file is 5A181A1BBF0DFF10EA98E13D3A641C33

The second one is rooted:

https://mega.co.nz/#!ksUWxS7S!CikWC2xLiYcaJoG0hI1N0DPV2cGUbu3Vj_bkIAdjrOA

MD5 of the unzipped file is CEAC0EF577480D57383EC540BBB479BA

You will have to ask [MENTION=5697730]maiko1[/MENTION] to open up MoFo for the XT1094 to test the images. I had to combine the sparse chunks you uploaded and remove the header and the footer with a hex editor. The files should be fine but I was not able to test them as they would not boot to my device. I do not think there is anything wrong with the files, I think that the Republic Wireless XT1094 is too different from the Verizon XT1096 for me to be able to boot an XT1094 image on the XT1096. But there is the possibility that I did not remove the header and the footer properly. We will know if you can boot the images.

I would flash the first image (unrooted) first to see if it boots. If not then no need to flash the rooted image. If it does boot, then you can flash the rooted image, download Root Checker Basic and confirm that it is rooted. If it is a valid rooted image, then you can let maiko1 know so that he can open up MoFo for your device to everyone with an XT1094.

Please read my noob guide - link is in the OP of this thread. You need to know how to flash the sparse chunks to your device should the images I made not work properly.

Also all I did was root the image, which is not useful as write protection is still enabled. To be useful, the image would need to be further modified using linux to add things like Xposed. I don't know how to do that and the image I use on my XT1096 that has Xposed was made by someone who knows how to use linux. So either you or someone else who knows how to use linux would have to further modify the rooted image to make it useful.

Please contact [MENTION=5697730]maiko1[/MENTION] if you want to test these images on the XT1094. Let me know how it goes.
[Paid Software Announcement and Discussion] JulesJam:
Rooted Ext4 Image for the XT1058

[MENTION=5697730]maiko1[/MENTION] - I created a rooted image for the XT1058 that will boot on my XT1060 with an unlocked bootloader. [MENTION=6726470]bobglaus[/MENTION] has offered to test it on his ATT XT1058 (which cannot be unlocked).

http://xdaforums.com/moto-x/development/mofo-img-xt1058-rooted-ext4-image-mofo-t3125847

[MENTION=6726470]bobglaus[/MENTION] - please contact maiko1 about testing this image on your XT1058. Once this image is successfully tested and MoFo is opened up for the XT1058, I can see about creating an image with Xposed and other apps in it. I have been able to install Xposed using the APK, but need the rooted image confirmed as working on the XT1058 before I invest any more time in this.
[Paid Software Announcement and Discussion] josetann:
This may not be the best place to post this, but here goes.

I'm trying to create a rooted system image of the Moto G Verizon model ( XT1028 ). That's not the hard part (it's already done). Rather, fastboot can't handle such a large file, it has to be broken down into multiple sparse files. So, my question(s):

1. Can MOFO handle sending a single large system_img file to the Moto G XT1028?

2. If #1 is a no, can MOFO handle sending multiple sparse files?

3. If #2 is a yes, how do I create multiple sparse files? I know how to make a regular img file sparse, but not sure how to create multiple sparse files from a single image.

For testing purposes, what process best mimics how MOFO is flashing the system image? I.e. a certain version of fastboot, or mfastboot? Not asking for state secrets, just want to practice flashing a stock image before I shell out $20 for something that may or may not work. BTW, trying to use mfastboot results in this:

D:\AB>mfastboot flash system system_motog.img

sending 'system' (524288 KB)...

OKAY [ 16.552s]

writing 'system'...

Multi-Flash is not supported any more!

Please download latest fastboot from: http://goo.gl/7fS50o

FAILED (remote failure)

finished. total time: 16.568s

So frustrating, it starts to send it but then throws up a "not supported" error.
[Paid Software Announcement and Discussion] JulesJam:
mfastboot can flash large files. Does the Moto G Verizon model have an unlocked bootloader? If so, just use mfastboot to flash it.

Also, you can use SparseConverter.exe to break a system.img into sparse chunks.

http://xdaforums.com/showthread.php?t=2749797

however, I keep getting an error when I try to do it. But maybe it will work for you.

---------- Post added at 07:58 AM ---------- Previous post was at 07:56 AM ----------

AFAIK, mofo.exe requires that you have a single file ext4 system.img. The MX14 ext4 system.img is 2.8GB and mofo.exe flashes it fine. But MoFo is not open for the Moto G

---------- Post added at 08:00 AM ---------- Previous post was at 07:58 AM ----------

mfastboot. Regular fastboot can only flash the sparsechunks once the files get this big.

---------- Post added at 08:01 AM ---------- Previous post was at 08:00 AM ----------

MoFo is not open for the Moto G so you can't buy it anyhow. maiko1 doesn't open it up for a model until there is a valid ext4 image available for a device.

---------- Post added at 08:04 AM ---------- Previous post was at 08:01 AM ----------

If you are trying to flash an unsigned rooted file using mfastboot- you can only do that if your bootloader is unlocked. If your bootloader is unlocked, you don't need MoFo.

If your bootloader is locked, you can't flash unsigned rooted files using mfastboot or fastboot no matter what the size.
[Paid Software Announcement and Discussion] josetann:
Nope, bootloader is locked. If I can get root, then I might be able to use another program to unlock the bootloader.

So the error I'm getting trying to flash with mfastboot, is that an error from mfastboot itself or is that an error from the phone? I suppose a better question would be, is it possible that mofo.exe will work if mfastboot does not?

Ok, so how do I find out if I have a valid ext4 image? Do I need to send it to maiko1 for verification? I mean, I have no way of knowing for sure if it'll work without actually testing it. Seemed simple enough to do (combine sparse files, mount img, make changes, unmount image, then remount to make sure the changes were saved).

I know that. I just don't want to waste anyone's time. If mofo.exe works like mfastboot which does not work on the XT1028, then I won't go any further. If it worked like fastboot then I'd make sure I could split the img back into multiple sparse files before proceeding. Or maybe it's somewhere in between in which case I suppose I could send a PM and hope I get past maiko1's newbie filter.
[Paid Software Announcement and Discussion] JulesJam:
If you are talking about Sunshine, that is only for motorola devices below 4.4.4. Sunshine does not work on motorola devices running 4.4.4 or higher.

---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------

What are you trying to flash? A system image you modified? If so, of course mfastboot won't work. You can't flash unsigned files if your bootloader is locked.

That is the WHOLE point of mofo.exe - it gives you the ability to flash unsigned system images when your bootloader is locked. Read my noob guide - there is a link in the OP to it.

---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------

Link me to the system.img for your device and I will make you one.

---------- Post added at 08:19 AM ---------- Previous post was at 08:18 AM ----------

You have to remove the header and the footer too with a hex editor.

---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------

mfastboot works fine on the XT1028. It is just that if your bootloader is locked, you can't flash unsigned files.

---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------

Unfortunately, I think I am maiko1's newbie filter, lol!

Link me to your system image and I will make you a rooted ext4 image that is mofo.exe flashable. But if you are doing this b/c you think Sunshine can unlock your bootloader - it cannot if your bootloader is 4.4.4 or above. However, you can bake a lot of nice things into the rooted image like Xposed and free wifi tether if you have UDP and then flash with mofo.exe.
[Paid Software Announcement and Discussion] josetann:
I guess that would be the easier way, it's just that I have this system.img file just begging to be tested out. I do understand that I can't flash it as-is, I'm just trying to understand the procedure.

I thought I had read that the bootloader could be unlocked if you were already rooted; Sunshine could do a temp root on 4.4.2 but not 4.4.4. Of course I could be completely wrong (I don't have a rooted XT1028 on 4.4.4 to test with). I do like to tinker though.

Assuming that I can eventually get mofo.exe to flash the system image, not having write access would just be an inconvenience. I can easily add the apks I want, remove bloatware, edit hosts file, etc. I'll just have to explain to my wife why I have to flash her phone three times a day.
[Paid Software Announcement and Discussion] JulesJam:
Sunshine will not unlock the bootloader of any Motorola phone running 4.4.4 bootloader or higher regardless if you are rooted or not. The 4.4.4 update to the bootloader patched the exploit that Sunshine uses for Motorola phones. Feel free to read the Sunshine thread if you don't believe me.

---------- Post added at 08:32 AM ---------- Previous post was at 08:31 AM ----------

You are.

---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------

Inconvenient or not, if you are running the 4.4.4 bootloader on a Motorola device it is your only option if you want to use rooted apps. If Sunshine worked, why would the rest of us still be using mofo.exe?

---------- Post added at 08:35 AM ---------- Previous post was at 08:33 AM ----------

Why would you have to flash it 3 times a day? You bake the changes into the system image before you flash it and then those changes survive reboot. Read my noob guide.
[Paid Software Announcement and Discussion] josetann:
Oh goodness...pretend I have a high post count. Why would a dev need to flash a phone three times a day? Even with full access, I've flashed my Galaxy phones more than that whenever I got a new one to play with. And WITHOUT write access, any changes I want to make will require a complete flash.

:)
[Paid Software Announcement and Discussion] JulesJam:
And a complete MoFo flash takes about 25 minutes for the XT1096. Obviously, whatever exploit it uses takes some time, more time than mfastboot.

If your device has a smaller image and it should, it would take less time.

I am happy with my Moto X 2014 just with free wifi tether, TiB/U, Xposed and AdAway.
[Paid Software Announcement and Discussion] josetann:
Oh, I'm never "happy" with a phone. By the time I have it set up just the way I want it, I get bored and have to swap for another one. I've been through four phones so far this year, and my GS2 is getting a bit long in the tooth (had it since March). Playing with my wife's Moto G might help me get through another month, two if I'm lucky.

Back on topic, the system.img is nearly 1GB. The four sparse files add up to a bit less (about 875MB). I know why the single image is larger (I haven't made it sparse, because I figure it either didn't matter, or I needed multiple sparse files...sounds like mofo.exe only works with one file so I won't bother with the multiple ones). I downloaded the fastboot files a while back from sbf-droid-developers; their site is down and so is the archive. I still have my copy and know it's good (the original, untouched files of course) as I can flash normally with no errors.
[Paid Software Announcement and Discussion] JulesJam:
I question whether that is a decompressed ext4 file. The ext4 file for the MX14 is 2.8GB and for the XT1058 it is 1.5GB.

If your starting file is not an ext4 file, then it won't work.
[Paid Software Announcement and Discussion] JulesJam:
[MENTION=6726470]bobglaus[/MENTION] - there is now a rooted image with Xposed baked in but please test the image with just root first. Here is a link to the thread with the images for the XT1058:

http://xdaforums.com/moto-x/develop...image-mofo-t3125847/post61148543#post61148543

[MENTION=5697730]maiko1[/MENTION] - these images are ready to be tested! I cannot test them b/c I do not have an XT1058. I can only flash them to my XT1060 because it has an unlocked bootloader.
[Paid Software Announcement and Discussion] bobglaus:
I can't test any of them. Mofo hasn't been opened and [MENTION=5697730]maiko1[/MENTION] hasn't responded yet. I also dont have a copy to test but I have a feeling that I can make the images myself too. I just have to mount the filesystem as read and write and make my changes then pull the IMG before a reboot. I can't test tho because no mofo
[Paid Software Announcement and Discussion] JulesJam:
[MENTION=5697730]maiko1[/MENTION] - please respond to bobglaus so he can test the images I made for the XT1058, thanks!!

---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------

You can make whatever images you want but I need you to test the ones I made. I know I can make them properly. After you test the ones I made, make as many images as you like and if they work w/o issue, then please post them so others can use them too, thanks!!
[Paid Software Announcement and Discussion] bobglaus:
Yea I will test yours. I was just thinking out loud. Hopefully we get a response soon
[Paid Software Announcement and Discussion] JulesJam:
You can do that in linux. But your device is write protected so you can't do it in android. If you read back in this thread you will see that others have tried that and it doesn't work while running Android.

I don't think you can make the changes while running android. Read this thread - others have tried it.

EDITED - I am correct on that. Just search the thread for mount and remount and you will bring up the discussion. Despite root and despite mounting/remounting /system as RW, the write protection is enforced by aboot and does not allow any changes to system while Android is running.

That is why I have to use the XT1060 with an unlocked bootloader and make my changes on that.

---------- Post added at 04:35 AM ---------- Previous post was at 04:33 AM ----------

I am in the process of making one with busy box and xposed and cf lumen.
[Paid Software Announcement and Discussion] bobglaus:
Good. I know some people would like free tethering and some other stuff too but idk what a lot of them are.

Can you make a debloated version too?
[Paid Software Announcement and Discussion] JulesJam:
free tethering doesn't hide it from ATT but I will add it. What bloat do you want removed?

Also - it doesn't help you to remove bloat b/c it frees up space on /system which you can't use anyhow. I just freeze it with TiB/U Pro.
[Paid Software Announcement and Discussion] bobglaus:
Possibly all at&t apps except visual voicemail or just move all apps off of system so they can be removed if the user wants to
[Paid Software Announcement and Discussion] JulesJam:
It doesn't help you to remove them - just freeze them with TiB/U pro.
[Paid Software Announcement and Discussion] bobglaus:
Doesn't it help with low storage phones? Because even with all updates uninstalled it's still like 25 mb
[Paid Software Announcement and Discussion] JulesJam:
No, the /system partition size is set by the partition table. It cannot be made smaller. Removing system apps merely frees up space on the /system partition. But the device is write protected so you can't use that space for anything.

Now in linux, you may be able to move /data partition apps to the freed up space on /system, idk, but if you were going to use linux to do that, you could just debloat then anyhow.
[Paid Software Announcement and Discussion] bobglaus:
Yea that's true. The issue is I can't flash them [MENTION=5983610]JulesJam[/MENTION]