yashsingh1/xdaforums huggingface dataset:
[X 2014 General] JulesJam:
And this is why I don't use those numbers and just use 4.4.4 or 5.0. Idk why they have such confusing numbers - I think it is b/c the OTA is named according to the version it is updating from, not updating to.

Bottom line - if it says Android Version is 5.0 in your settings, you are on 5.0. The images Slack3r made are for 5.0.

It's OK to flash the 5.0 images if you are on 5.0. And even if you are on 4.4.4, as long as you know how to put your device into bootloader mode, you can flash the proper image.
[X 2014 General] JulesJam:
Yeah, even when mofo told me I was flashing something that wouldn't work, I did it anyhow. If you flash the wrong image, the only thing that is going to happen is that you are not going to boot.

So just hold down the power button for awhile, then get into bootloader mode by pressing vol dwn + vol up + pwr for a few seconds, release and then reflash.
[X 2014 General] JulesJam:
Please let us know how it goes for you!!!
[X 2014 General] firewater88:
Got error, this is not a valid ext4 file, do you wish to continue. I'm re-downloading now to see if it was a bad DL.

EDIT- Re-Dl'd the image and same thing. Says want to risk it all? I clicked NO fro now...
[X 2014 General] JulesJam:
Where did you get the image from?

Did you get it from here:

https://mega.co.nz/#!CdsgDQLD!eUJl8Kwnc1QCc8wu4yMvqMLoCKapMEFIs0jrotI1NCU

And did you unzip it?
[X 2014 General] Aroch925:
I just did it and it seems like nothing has changed. I went on the root checker app like the video said and it said I didn't have root. What am i doing wrong?
[X 2014 General] trimax84:
Is that expected JulesJam? I imagine firewater can just click yes to that...

Also, this will delete EVERYTHING, correct? So everyone should back up pictures, texts, and data they hold dear to their hearts!
[X 2014 General] firewater88:
Got it from pg 10 of this forum. I restarted my computer and now it seems to work. Had issues getting mofo verify on a win 8.1 x64 machine, so I'm on my server which is win 7 x64. Now we are rolling...
[X 2014 General] trimax84:
If you loaded the 5.0 ROM, it is not yet rooted! People are working on embedding superuser, but it isn't exactly straightforward. We'll get it though.

For now, the 5.0 ROM just has wifi tether enabled but is otherwise stock.
[X 2014 General] JulesJam:
On 5.0 we don't yet have root. Just on 4.4.4. On 5.0 it is just free WiFi tether and the only people who care about free WiFi tether are those who have unlimited data plans.

Do you have a UDP line?
[X 2014 General] JulesJam:
No if it tells you it is not a valid ext4 image you won't be able to boot if you proceed. You won't brick b/c you can just get into BL mode and flash the stock system to recover.

No, it just flashes system. So anything on the data partition or the sdcard stay intact.

Well that is always a good idea whenever you flash anything IMO.
[X 2014 General] JulesJam:
Did it flash and boot? MoFo takes a long time to flash.
[X 2014 General] trimax84:
Ah, that's good news. I'll still be backing everything up though!

Oh, and computerfreek274 in the Turbo thread recommends wiping cache directly after flashing and before rebooting. I imaging that would be generally good practice for us as well.
[X 2014 General] firewater88:
Confirmed! Posting this from my Nexus 7 on my wifi tethered Moto X 2014!

Thanks for all the help. Having the WiFi is pretty much all I need on this phone. Root would be nice, but this is how this phone should be.

Thanks again!
[X 2014 General] JulesJam:
Yes good idea! I will try to type up a guide.
[X 2014 General] Aroch925:
I don't really care about WiFi tethering I just want root so I can put cyanogenmod on there. Could I flash the 4.4.4 version my phone that has 5.0 and then download cyanogenmod on there? It not is there any other way to get cyanogenmod on there?
[X 2014 General] JulesJam:
Awesome!!!! Yeah root is nice but free WiFi tether is MANDATORY!!!
[X 2014 General] JulesJam:
OK, you don't understand some basics here. To put cyanogenmod custom ROM on your phone, you need an unlocked bootloader. Well no one has unlocked the Verizon Moto X 2014's bootloader.

Now if someone would make you a CM-based 5.0 ROM in an ext4 file for the XT1096, which someone may very well be able to do, THEN you could flash it with mofo.exe.

Root is not going to allow you to flash a custom ROM with a locked bootloader.

There is a program called safe strap that is no longer supported that allowed devices with locked bootloaders to install custom ROMs, but that is not available for the Moto X 2014 AFAIK.

No I tried that already and it won't boot. I even flashed the 4.4.4 kernel too. No dice.

Someone would have to make a 5.0 CM-based ROM for the Verizon Moto X 2014 in the format that mofo.exe can flash (ext4).
[X 2014 General] en_pneumati@netzero.net:
so basically, i should just move on up to LP 5.0. it really makes no dif to me....i was only holding back b/c there seemed like much less hope for LP root than KK root only a few days ago...

i guess i'll wait a little longer and see if the LP 5.0 gets pre-rooted image plus tethering. if so, then i'll just OTA and use Mofo... assuming tha is the correct path.
[X 2014 General] JulesJam:
If you stay on KK, you have root and can use the Entitlement Check Bypass app to bypass the entitlement check to have free Wifi tether.

But someone knowledgeable would have to mod the 4.4.4 image to have the modified build.prop, the Xposed Installer or other desirable features to make staying on 4.4.4 desirable. Idk that anyone is interested in doing that b/c most of us are on 5.0.

As long as you are stock 4.4.4, you can take the 5.0 OTA. If you have already flashed the pre-rooted 4.4.4 image using mofo.exe, you need to flash back to stock 4.4.4 system.img to take the OTA.
[X 2014 General] btdownloads7:
Ok, guys, correct me if I'm wrong, but wouldn't it be pretty easy to get the 5.0 image properly rooted if we had some help from anyone with an unlocked Moto X 2014? All they would have to do is flash our (non-rooted) system image, and TWRP recovery from the bootloader menu using fastboot, then boot into recovery and install the SuperSU update zip. At this point, they would have everything properly rooted, and they would just need to pull that system image from their phone and post it for us to use.

Obviously, they can't boot their phone with our system image, but just to install root on that image, and then pull it off of their phone should be a pretty simple process. Or am I missing something?
[X 2014 General] JulesJam:
They would have to have an unlocked XT1096, which doesn't exist except at the factory in China.
[X 2014 General] btdownloads7:
Why would they need an unlocked XT1096? They're not trying to boot that image, just modify it. Are you saying that the XT1096 image wouldn't flash onto an XT1095 with an unlocked bootloader?
[X 2014 General] JulesJam:
The Pure Edition system.img is a different size from the XT1096 system.img. Would a version of TWRP for the PE be able to recognize it and install SuperSU? I thought each version of TWRP was specific for the model of the device, no?
[X 2014 General] JulesJam:
I am not sure it will flash with fastboot if our system.img is the wrong size for their system partition. Maybe, idk.

I have an XT1060 Dev Ed Moto X 2013 with TWRP on it. I will try flashing the GSM Dev Ed system to it later and see if I can install SuperSu or if I get an error.
[X 2014 General] btdownloads7:
I thought that different versions of TWRP were there to account for the differences in hardware and file system structure. And we won't be flashing the system image using TWRP (although you probably could, I don't thikn it'll care that it's from a different variant of the phone). I thought that you could flash the system image straight from the bootloader menu. The SuperSU script is designed to detect the hardware that it's running on, and run the proper commands for that hardware. And since all the hardware (except for the radios) is the same for the unlocked Moto X, the script should run exactly the same as it would on the XT1096.

Edit: The only thing that matters is that the unlocked XT1095 has been upgraded to 5.0, and not to any other version (so that their bootloader matches ours)

---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------

Great -- that's a good way to test this concept
[X 2014 General] Red_81:
I'm moving the image to my Linux vm and the add in the xbin folder from my xt1095 along with the superSU app. Hopefully that will fix you guys up.
[X 2014 General] btdownloads7:
You'll see that a couple of other people already tried that few pages back, but thatnks for trying (and if you can get it working, that would be awesome). It's not just moving the xbin folder -- there is a bunch more stuff involved with creating symlinks and changing the context on several files. You can see the actual script that's included in the SuperSU update zip to see what's involved. But for whatever reason, once we boot that image, root isn't functional.

Is your XT1095 unlocked? And if so would you mind trying the process I described?
[X 2014 General] JulesJam:
nvm .. ..
[X 2014 General] Red_81:
Sorry, this is my daily I use for work so I can't flash it. However, I've already started going through the script and will try to manually do the steps to the image. I think I already see one step that would have been missed. Plus, I can pull what I need from my device.
[X 2014 General] JulesJam:
This link might be helpful as to what needs to be done.

http://mydragonboard.org/community/hw-sw-8064/super-su-or-equivalent/
[X 2014 General] Red_81:
That looks good. I figured it was the install-recovery not launching the daemon on boot and that seems to confirm my theory. I need to sleep now but will work on it in the morning.
[X 2014 General] JulesJam:
well it is not easy to find a stock 4.4.4 for the XT1053 - I had to find one from a chinese site!
[X 2014 General] JulesJam:
Would it help if [MENTION=1576439]Slack3r[/MENTION] sent you a link to his ext4 image that he rooted? I can link to it but need him to OK it since it is his file.
[X 2014 General] JulesJam:
I downloaded SuperSU zip to the sd card of my unlocked XT1060 and flashed a stock XT1053 4.4.4 system.img to it. Then booted into recovery and installed the SuperSU zip from the sdcard.

Now what am I supposed to do to pull the files from the device?
[X 2014 General] JulesJam:
How do I do that? I am doing a backup of the system partition via TWRP, is that what I am supposed to do?
[X 2014 General] btdownloads7:
I'm a little rusty at this -- the last time I did this was on an unlocked XT926, but here's a tutorial for doing this. The basic process is this:

1. Figure out which mount point is used for the system partition ("/dev/block/mmcblk0p9" in the tutorial, but would probably be different on both Moto X versions).

2. Run the "dd" command to make an image of that partition and save it on the SD card.

3. Pull the image from the SD card

The only problem is that you'll have to run this from TWRP, so you'll need to mount the SD card before you run the "dd" command
[X 2014 General] Slack3r:
I'd prefer not to share that link since it's incomplete. I've made some progress though, I picked up mofo and have been testing images on my device. After fixing a few minor mistakes (something something stupid permissions :o) I've gotten root to work. It complains that the binary needs to be updated and I need to make it default to accept (probably a gui issue) but it seems to be working.

I'm going to keep poking at it and hopefully I'll have something to release soon.
[X 2014 General] switch81:
Incredible! :good: I've been following the thread intently but i haven't dove in just yet. But thanks to everyone who has put in such a large amount of time and effort to get this going!!!
[X 2014 General] trimax84:
Nice going Slack3r! Looking forward to it :)
[X 2014 General] JulesJam:
Weeeeeee!!!! Root is near!!!!!:good::good::good::good::good::good:

Now I am inspired to learn linux and cook up my own ROMs! Because if you think about it that is what mofo.exe gives you - the ability to flash custom ROMs with a locked bootloader. They just have to be in ext4 file format.

You can't do custom kernels but maybe [MENTION=5697730]maiko1[/MENTION] can make a tool that will let you flash a custom kernel with a locked bootloader.

From everything I have seen with the Motorola devices, if you don't mess with the partition table or the bootloader and you have a stock image to flash back to, you can mess with any of the other partitions and be OK b/c you will still be able to get back into bootloader mode to flash back to stock.
[X 2014 General] no3no3:
Can I flash the ROM so pure edition of our xt1096?

Can I flash the ROM so pure edition of our xt1096?
[X 2014 General] trimax84:
[MENTION=3241948]no3no3[/MENTION] It will flash (so technically yes to your question), however it will not boot. So stick with those that are designed for our device.
[X 2014 General] no3no3:
wow..!

that sound great!!

omg~!
[X 2014 General] 1upyours:
Amazing progress guys. Glad I decided to check XDA today to see that we can flash a stock file to get TETHER!!!!

That's all I care about. :p

Getting MOFO nowww!!!! THANKS!!!!
[X 2014 General] ClydeDroid:
Thanks for getting us root, Slack3r, and thanks to JulesJam for all the hard work. I am impossibly excited.

One question though, once we have root, will we be able to use Xposed? Or does that have to be baked into the image as well?
[X 2014 General] Interflop:
To my understanding apps that need to be installed into the System partition (like Xposed) need to be baked into the image. Modules we'll be able to download just fine.
[X 2014 General] Slack3r:
This is where I'm at right now:

-Image boots after flashing with Mofo

-Need to open SuperSU and set default permissions to Grant

-Close/reopen SuperSU and update binary without rebooting

-Change default back to Prompt and everything works

Of course it goes back to not working after reboot. I checked after updating the binary and it seems that all of the files are in the same places with the same permissions as before, so either the script is getting something I'm missing or the version it's flashing (2.45) is needed for it to work properly. I'm going to try building it with 2.45 after work and see what happens.

Does anyone know of a way to capture what the binary updater is doing?
[X 2014 General] btdownloads7:
Could you please post the image the you have now? I'll see what I can do about modifying it with the latest su binary, but in the meantime, everyone will at least have a working rooted image to use.
[X 2014 General] JulesJam:
I believe the latest version of SuperSu is 2.46 and you can download it here:

http://download.chainfire.eu/696/SuperSU/
[X 2014 General] Red_81:
Anybody feeling brave and want to try the image I just finished modifying?
[X 2014 General] Twistitup:
Well, depends. Haha.

What did you modify on the img?
[X 2014 General] Red_81:
I took the build.prop modified one and added root (2.46). I'm compressing and uploading now, but it will be about an hour before it is finished. Fair warning, it's my first time doing this.

50% uploaded
[X 2014 General] Slack3r:
I'm at work and can't upload it right now, but I'd prefer not to post it publicly since having superuser default to grant is not very secure. If I don't make any progress in the near future however, I'll send it out via PM or something.

I've actually tried both 2.46 and the 2.48 beta with the same results which is why I'm thinking 2.45 might be needed.
[X 2014 General] btdownloads7:
The update message isn't referring to the SuperSU update zip or APK . It's specifically referring to the su binary., which according to the SuperSU script should have been copied to the following places: /system/xbin/su, /system/bin/.ext/.su , /system/xbin/daemonsu, /system/xbin/sugote. So, after you let the APK do the update, you can ADB pull those files, and copy them over to your image (but you'll most likely need to change the permissions and the context on them, just like you did with the original ones)
[X 2014 General] slogar25:
I'm with you on this. I've been looking into running the update script. Its just a simple updater which the only thing that hangs me up is the script needs to be able to differentiate between soc platforms but then again the binary looks to be calling towards the build.prop for that information. I would think that since the images are mounted for the editing that running the script should work but I can't seem to figure out how
[X 2014 General] Red_81:
I'm hoping my mods will work out pretty well. I pulled most of the items from my rooted, pure edition and added them, line by line, as the script does. I made sure to chmod as I went as well.
[X 2014 General] JulesJam:
The Android SDK has a tool called Device Monitor. Not sure if that would give you the information you need or not.

https://developer.android.com/tools/help/monitor.html

It looks like DDMS is the tool that would be the most useful but it also looks like it was written for Dalvik, not ART so idk if it would work on 5.0.
[X 2014 General] JulesJam:
I will flash it if you send me the link.
[X 2014 General] Twistitup:
I'll try it as well. I just bought and downloaded mofo.

Just give me instructions on anything I need to do once done flashing.
[X 2014 General] JulesJam:
I would advise first flashing one of the images that we know works before you try one under development.
[X 2014 General] Twistitup:
Any particular reason or just to get the hang of doing it?

Not sure if there was a software/hardware related reason to flashing a working one, first?
[X 2014 General] JulesJam:
Just to get the hang of it to make sure you can flash a valid image first. It takes awhile to flash presumably b/c it is doing something to circumvent the signature check.

No I would just make sure the copy of mofo.exe you got works to flash an image that we know is bootable and stable first.
[X 2014 General] JulesJam:
FYI - I timed it this time and it took only 10 minutes to flash. Seemed like a lot longer, lol! I guess it is one of those a watched pot never boils kind of thing.
[X 2014 General] Twistitup:
Was it the one that Red_81 made that you just flashed?
[X 2014 General] JulesJam:
yeah, it starts to boot but then hangs on the Verizon screen and never boots.
[X 2014 General] btdownloads7:
Ok, I justtested my theory, and it worked. I actually didn't need an unlocked Moto X -- all I needed was an unlocked device with an armv7 CPU, so I used the Nexus 7. Bootetd it into TWRP, mounted the ext4 image, ran the SuperSU script, and then pulled the system image from the device and used mofo to flash it to my XT 1096. It runs perfectly, without any su update prompts or anything like that. I'm uploading the image now, will post a link when it's ready (looks like it'll take about an hour to upload).
[X 2014 General] Red_81:
I'm wondering if I didn't close the image properly or if I made an incorrect edit somewhere.....

Screw it! ^^^^ That's a much easier method.
[X 2014 General] JulesJam:
Awesome!!! So can I use my XT1060 Moto X 2013 Dev Ed to make XT1096 images?

FYI - last night I actually booted the rooted XT1053 system.img on my XT1060 but it was unstable so I couldn't run the root checker b/c the system kept crashing. So I flashed the XT1053 boot.img but it still kept crashing then I flashed system and kernel back to stock. Then I got tired and went to bed, lol!
[X 2014 General] Twistitup:
I'm super sorry if this has been answered, but if we are already on 5.0 and will be flashing a rooted 5.0 img, what all will it wipe?

I know it won't wipe any data, but will it wipe all of the apps?
[X 2014 General] JulesJam:
This is from the guide I am typing up.

NOTE – flashing the system partition does NOT affect your apps/settings/text messages/call history, which are stored on the data partition, not the system partition.

NOTE – flashing the system partition does NOT affect your stored media (e.g, pictures, music, videos), which are stored on the sdcard partition, not the system partition.

I would back up pictures and anything if it is important to you. I use SMS Backup and Restore to backup my texts to my google drive account but it also keeps a local copy.
[X 2014 General] btdownloads7:
Yes, but there was a slight change in the process (at least on the Nexus 7) from they way I described it originally. Since the image is huge, and wouldn't fit onto the system partition of the Nexus 7, i couldn't just flash it as a system image from fastboot. Here's what I ened up doing:

1. Make sure that you have at least 6 GB free on the SD card, and boot into TWRP

2. Copy the clean ext4 image file to the SD card (the links are a few pages back in this thread)

3. Create a "supersu" folder on the SD card

4. Download the SuperSU update zip (the current version is 2.46)

5. Extract the "armv7" and "common" folders from the update zip to the "supersu" folder from Step 3.

6. Extract the "update-script" binary from the attached zip, and copy it to the same "supersu" folder. It's a script from tha update binary that I modified for our purposes.

7. In TWRP gui, wipe the system partition (this may not have been necessary, but I did it just in case)

8. In TWRP gui, unmount the system partition from the TWRP menus

9. open ADB shell

10. run "rm -r /system", and disregard any errors that it gives you. This will clear the mount point for our image

11. run "mkdir /system", and ignore any errors it gives you

12. run "mount -t ext4 -o loop /sdcard/system.img /system"

13. run "chmod +x /sdcard/supersu/update-script"

14 run "cd /sdcard/supersu" followed by "./update-script". You might see some errors when it's running, but you can disregard them

15. In ADB shell, run "mount", and that should list all the partitions. Remember which path is for the system partition (on my end it was "/dev/block/loop0")

16. run "dd if=dev/block/loop0 of=/sdcard/new_image.img". Obviously replace "/dev/block/loop0" with whatever you got in the previous step

And thats it. Copy the new image back to your PC, and you're ready to flash it with mofo
[X 2014 General] JulesJam:
This is the SuperSU update zip you are talking about correct?

http://download.chainfire.eu/696/SuperSU/
[X 2014 General] btdownloads7:
yes
[X 2014 General] mdmogren:
Sunshine/BL Unlock Possible Soon?

With all of this progress, will it be possible to get a BL Unlock / SunShine working? Would LOVE to give them my money.

I am holding on 4.4.4 to see how this plays out...
[Galaxy Tab 4 Q&A, Help & Troubleshooting] emeroj:
just wondering if can extract network/sim unlock codes thru extracting bml5.img or similar file when rooted then opening it to hexeditor to see codes for galaxy tab t337a, i hope someone help, thanks in advance
[Upgrading, Modifying and Unlocking] mnazmi:
I have made my own ROM and got my PPC as I wanted it.

I setup the messaging with the required operator numbers etc. When testing I am able to receive SMS messages but when I send or reply to any they end up in the drafts folder and not being sent out.

I wonder if I missed out any necessary cab files? I have what I thought is the right file Alpine_SMS05272005.sa.CAB or am I missing something else?

I hope some one can help. THX
[Android Auto General] jkcarp94:
Anyone seen any reports of the M9 being confirmed to work with Android Auto? I know on paper it should work fine but I'm looking for confirmation.
[Android Auto General] tgcid2040:
HTC M9 was confirmed as supported by Android Central

http://www.androidcentral.com/psa-some-more-popular-android-phones-dont-yet-work-android-auto

Other devices which are having problems should become compatible once Google Play Services 7.3.29 (1866531-xxx) for Android 5.0+ (Lollipop, API 21) is pushed out.
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Please delete.