yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] JulesJam:
I do

logo

boot

recovery

radios

But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.

---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------

I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.

https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0

PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.

It should be easy for someone to modify the buildprop so you can have free tether.
[Verizon Motorola Droid Turbo Android Development] madeiracam:
works like a charm

Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X

Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
[Verizon Motorola Droid Turbo Android Development] Koneesha:
Thank you! You are working mighty quickly I must say. We all really appreciate it!
[Verizon Motorola Droid Turbo Android Development] johnwaug:
I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.

After I let LP boot up, I could enter into recovery and factory reset without a problem.
[Verizon Motorola Droid Turbo Android Development] Koneesha:
I just noticed the same exact thing. I am currently going into the first boot as well.
[Verizon Motorola Droid Turbo Android Development] johnwaug:
After boot got into recovery and did factory reset. I like the look of the new recovery. Reminds me of custom recovery. Now to flash the freshly patch xposed img to start the resetting up process. Turbo with rooted LP. Yeah. Thanks OP.
[Verizon Motorola Droid Turbo Android Development] johnwaug:
Followed the process to install the patch and get xposed running but only get framework not installed in xposed app? What am I missing? The rest of the rom seems great so far.
[Verizon Motorola Droid Turbo Android Development] ntxct:
EDIT: This post is no longer valid...

8 Hours after flash and all's been great.
[Verizon Motorola Droid Turbo Android Development] johnwaug:
You can't get back to fastboot by holding the volume down an power buttons for a few seconds?
[Verizon Motorola Droid Turbo Android Development] ntxct:
Oh I can.. its just not showing up ad a connected device when I adb (am I having a brain fart.. it would show up as a listed device right?)

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

Annnnd now mofo sees it and is flashing.... DONT YOU JUST LOVE DRIVERS?!

I'll report back when everythings working again...
[Verizon Motorola Droid Turbo Android Development] johnwaug:
once in fast boot type fastboot device to see it.

---------- Post added at 08:38 AM ---------- Previous post was at 08:30 AM ----------

My problems with xposed were my fault for not flashing the patched rooted image. Sorry. Works perfect.
[Verizon Motorola Droid Turbo Android Development] JulesJam:
WARNING!!!

Peeps - Listen UP!!!

I have already warned you that you need to delete the contents of BOTH /data/dalvik-cache and /cache BEFORE you did any flashing to 5.1. It takes 30 freakin' seconds to do that and you save yourself a whole lot of aggravation if you do it.

You all are experiencing the EXACT SAME ISSUES that we were experiencing on the MX14. I and others did a whole lot of flashing to figure out the solution. There is no need to reinvent the wheel here. I have already told you what you need to do.

AGAIN, these are the exact same issues that arose with the MX14 and the solution is to DELETE THE CONTENTS OF BOTH /data/dalvik-cache and /cache BEFORE you flash to 5.1.

You also can do a factory reset, which wipes and formats /data and /cache, but if you are trying to not have to do that then you need to do what I said to do from the beginning.

---------- Post added at 09:16 AM ---------- Previous post was at 09:08 AM ----------

Before you flash anything 5.1 you need to delete the contents of BOTH /data/dalvik-cache and /cache. THEN boot into bootloader mode and do your flashing.
[Verizon Motorola Droid Turbo Android Development] bqw371:
This upgrade path to 5.1 worked perfectly and the hotspot patch functions as expected. Thanks everyone!
[Verizon Motorola Droid Turbo Android Development] JulesJam:
I was asked how to do this by PM. I will answer here so that everyone who wants to know will know.

While you are running a rooted 4.4.4 image, you download ES File Explorer or any other app that will allow you to delete files on /system. Once you have downloaded ES File Explorer, you have to enable Root Explorer and Show Hidden Files in the Settings. Then you will be able to navigate to /data/dalvik-cache and /cache to delete their contents.

Fastboot erase cache does not work right for this purpose.
[Verizon Motorola Droid Turbo Android Development] Koneesha:
I actually haven't deleted my cache but so far there are no issues? What issues should I be seeing?
[Verizon Motorola Droid Turbo Android Development] AlexR666:
Any chance you are working on a debloat and/or iOS emoji patch like I see exists on the moto x side? I think the android emojis are a little ridiculous and I have had trouble with emoji switcher on rooted 4.4.4.

And follow up, could I just remove any app I don't want with a system app remover from the play store if there is no debloated image?

Anyway, thanks for your time! Can't wait to flash when I get home from work tonight.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
FYI I was having strange issues because I went directly from cfs 4.4.4 to this (after doing both cache wipes) instead of from straight stock, but a few reboots and a cache wipe from recovery seems to have straightened the phone out.
[Verizon Motorola Droid Turbo Android Development] incredibler:
Followed the steps exactly and I keep getting the little android guys flashing quickly with "no command" written under. I see there were a few other people with similar issues. Any suggestions?
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Did you wipe your caches? Please describe what you came from and what you did.
[Verizon Motorola Droid Turbo Android Development] gqskrub:
I deleted /data/dalvik-cache (erased entire folder) but /cache is not erasable as a folder and its contents are empty. Am I looking at the wrong "/cache"?
[Verizon Motorola Droid Turbo Android Development] johnbravado:
does a titanium backup work between KK and LP? not sure if with the change in the system if there was a change in organization
[Verizon Motorola Droid Turbo Android Development] janitorjohnson:
OK. Which Xposed do I download???? arm, arm 64, or x86??
[Verizon Motorola Droid Turbo Android Development] koftheworld:
There is only one apk on that page. Those are sdk downloads.
[Verizon Motorola Droid Turbo Android Development] JulesJam:
Yes, you don't do a cache wipe using fastboot, you manually delete the contents of /cache while running the OS using a root file explorer as well as manually deleting the contents of /data/dalvik-cache. If that doesn't work, you wipe cache through recovery, which actually formats the /cache partition.

And if that doesn't work, you do a factory reset, which formats the /data partition too.

---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------

well you are not supposed to delete the folders /data/dalvik-cache and /cache. You are supposed to delete the CONTENTS of those folders.
[Verizon Motorola Droid Turbo Android Development] incredibler:
I got it up and running... I redid the entire process. It wouldn't let me into recovery or boot initially... Had to hold volume down and power 3 or 4 times. I may not have wiped cache... I did fastboot erase ddr. Maybe should have wiped cache in recovery prior to starting anything.
[Verizon Motorola Droid Turbo Android Development] JulesJam:
That's probably a good idea.
[Verizon Motorola Droid Turbo Android Development] gqskrub:
Had problems patching the file due to " 'xdelta3' " is not recognized as an internal or external command." Everything else seems to be working.

Edit: Nvm. I literally renamed it to "xdelta3.exe". Did not need the ".exe". Everything is working now.

Edit2: VoLTE doesn't appear to work. I had 4G and someone called me and I lost data.
[Verizon Motorola Droid Turbo Android Development] pjsockett:
I updated and was getting an error that play services needed to be upgraded but the update wouldn't show up through the play store. I tried to download using apkmirror but didn't realize they were so specific, I just grabbed the newest one that wasn't M preview. Now I keep getting play service crashes, so I think I got the wrong one. I tried reflashing the image but I get the same thing. What is the correct version of play services?

Edit - Fixed deleted files and installed correct 430 version
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
I don't think wiping /cache manually before flashing is necessary, mofo uses the cache partition in its exploit, and it's wiped after the flashing process is complete.

Unless you boot into recovery and wipe cache after flashing but before booting, which might help by formatting the cache partition properly.

/data/dalvik-cache doesn't seem to be touched by the 5.1 OTA upgrade script either. But didn't you say this was a requirement for the Xposed image only?

Not trying to argue, I'd just like to know what's strictly necessary before telling people what to do.

I was personally able to upgrade without wiping anything, so people who have gotten it to work, let me know what you had to do (if anything).
[Verizon Motorola Droid Turbo Android Development] my2cents:
Can someone give me a little more detail on this step? Where do we type these commands, for example? Sorry for the dumb question, I'm not a programmer... Thanks guys!
[Verizon Motorola Droid Turbo Android Development] gqskrub:
I installed something called Minimal ADB and Fastboot.

Open that program (which opens a CMD window)

Type: fastboot flash logo "insert path for logo.bin" (probably by dragging and dropping file into window)

Repeat for other commands.

install image with mofo.

Reboot.

---------- Post added at 05:24 PM ---------- Previous post was at 05:03 PM ----------

I had this same problem when I installed the unpatched root system. I patched it, reflashed, and no more play services errors.
[Verizon Motorola Droid Turbo Android Development] JulesJam:
We have already been down this road on the MX14. I flashed, and flashed back and flashed again and flashed back, etc. until we figured it out. This is what worked for us. Why? Idk exactly because MoFo isn't open source, but it is what has worked to consistently and reliably avoid all of the exact same issues that are being reported here.

All of what was done to diagnose this issue and come up with a solution was documented on the MX14 MoFo threads.

---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------

After you manually delete the contents of both /data/davlik-cache and /cache, you boot into bootloader mode. Then connect your device to your computer, open a command shell, navigate to where you have fastboot.exe and type in those commands.

---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------

You don't delete the /cache, you delete the contents of the /cache. If you aren't having any issues then I wouldn't worry about it, but it never hurts to boot into recovery and wipe the cache (which will also format it). You don't lose any data or settings or media by doing that.
[Verizon Motorola Droid Turbo Android Development] ntxct:
You keep saying issues.. can you be more elaborate? As far as Ive seen in this thread the biggest issue anyone is having is recovery not working until after a few boots. Outside of that, I'm not sure what issues you are seeing..?
[Verizon Motorola Droid Turbo Android Development] JulesJam:
That's one of them. The others are what people are posting here. If you aren't having any of the issues people are posting here, don't worry about it.

Why some people have issues and others don't, idk, but it takes 30 seconds to delete the contents of those folders and it avoids a lot of headaches if you are one of those who ends up having problems. And people here are having the exact same issues that we saw on the MX14 forums. Again, MoFo isn't open source so I don't know all the ins and outs of how it works and why some people have issues and others don't. Also, Xposed causes a lot of issues when you go from kit kat to lollipop.
[Verizon Motorola Droid Turbo Android Development] cenobite138:
I wiped beforehand while booted into 4.4 with ES File Explorer, only the contents of the folders. Then I followed instructions, but could not boot into recovery to wipe cache, and after a few reboots still can't get into recovery and am having the play services errors.

Edit: after a few more reboots I was finally able to update play services normally, but I still cannot get into recovery by any method.

Edit 2: Some strange behavior as well. I can't use the google search bar and certain apps say no connection, while other apps and chrome connect just fine over 4g
[Verizon Motorola Droid Turbo Android Development] JulesJam:
Yes, I do think formatting the cache partition can help too. Why some people have issues and others don't seem to have them, idk for sure. Just reporting what trial and error has taught us best avoids the issues in the first place.

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

Do you see the dead android when you attempt to boot into recovery?

---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------

For MX14, we started on 5.0. You all are starting on 4.4.4 and there was a transition from dalvik to ART in Lollipop. I think it is a good idea to wipe the dalvik-cache before upgrading to 5.1. from 4.4.4.

But yes, for those of us already on 5.0 when we first used mofo, the issue did not appear until Xposed for Lollipop was baked into the image we were flashing.
[Verizon Motorola Droid Turbo Android Development] cenobite138:
Yes, dead android comes up with "No command."
[Verizon Motorola Droid Turbo Android Development] JulesJam:
Press and hold the power button, then tap the volume up and release. That will get you into the recovery menu.

That is normal btw. Please read my noob guide:

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
[Verizon Motorola Droid Turbo Android Development] Flowah:
So where do I unzip the 5.1 _images.zip to?

And how exactly am I supposed to enter these "fastboot" commands. I think I installed fastboot, but when I try the "fastboot flash logo logo.bin" command it just hangs at <waiting for device>
[Verizon Motorola Droid Turbo Android Development] ntxct:
Is your phone in bootloader mode? Does your computer recognize the phone as an adb device?

To answer what you specifically asked, you can unzip the images to where ever you want.. to be able to use the fastboot commands as they're typed out, you should unzip the images to where fastboot is installed... assuming you used "minimal adb and fastboot" and are on windows, the default directory is, "C:\Program Files (x86)\Minimal ADB and Fastboot"
[Verizon Motorola Droid Turbo Android Development] Flowah:
My phone is in bootloader mode. Same mode I used when flashing with mofo. I don't know if my computer recognizes my phone as an adb device.

I get the feeling I don't have ADB drivers. I checked device managers and under "other devices" it lists adb interface with an exclamation point.

Not sure how to fix that.
[Verizon Motorola Droid Turbo Android Development] pjsockett:
The easiest thing to do to make sure your command window is looking in the correct folder is to use file explorer to go the folder containing your fastboot and image files, the while holding shift, right-click and select open command window here. From there you will need to be in bootloader mode. If your phone is still on normally you can use "adb reboot bootloader" and continue on from there with the direction for fastboot flashing.
[Verizon Motorola Droid Turbo Android Development] ntxct:
AFAIK the exclamation point means a driver issue... Im not good with directions for drivers other than to say heres where you can get the Moto adb drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

EDIT: This installs the Motorola Device Manager as well as the drivers during the install.. you dont need to run Motorola Device manager.. in fact, running it may say there's an update for your phone and doing that will(?) give you the official 5.1 and then.... SOL. So just install it, unplug phone, replug phone.. maybe reboot system...but dont actually Run Motorola device manager.
[Verizon Motorola Droid Turbo Android Development] cenobite138:
Update: all my troubles seem so far away. Thanks for the image and the help. Noticeably snappier and I'm noticing better text prediction with the stock keyboard

Awesome work
[Verizon Motorola Droid Turbo Android Development] diabl0w:
did anyone do a factory reset and get stuck on "checking for system update" when setting up the phone ?

... (I'm running the patched rooted image)
[Verizon Motorola Droid Turbo Android Development] siegesoldier:
mine hung there for a little bit but I backed out of it a few times and it went through. Also did a factory reset.
[Verizon Motorola Droid Turbo Android Development] diabl0w:
I cant for the life of me get past that screen on any rooted image (root only/ patched/ computerfreek), i went right through it though on stock nonroot.... hmmmm..
[Verizon Motorola Droid Turbo Android Development] my2cents:
Did you figure out how to get past this? I have the same issue.

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

Ok. I am going to go through the whole process again because I've tried rebooting and getting into recovery like 20 times!
[Verizon Motorola Droid Turbo Android Development] Koneesha:
You have to boot into the system before you can get into recovery.
[Verizon Motorola Droid Turbo Android Development] charklos:
Mine is on the "Android is Upgrading" screen that comes up upon first boot. I have been getting the flashing android as well, so I'll report what I get after the boot finalizes.
[Verizon Motorola Droid Turbo Android Development] gqskrub:
Everything awesome
[Verizon Motorola Droid Turbo Android Development] ds728:
A few posts back, you had mentioned that VoLTE stopped working.... any updates? That'd make-or-break the update decision for me right now.
[Verizon Motorola Droid Turbo Android Development] MonkeyMouth:
How long did everyones else system img take to flash using mofo?
[Verizon Motorola Droid Turbo Android Development] ntxct:
The whole Mofo process? 25-30 mins.. however that was because it failed loading at 15%.. 95%... 35%... before completing the flash.

I was also using Mofo .0.0.1 .. Ive read the most recent .0.0.3 flashes more reliably.

The time it didn't fail probably took about 5-10 mins.

I think the first boot actually took longer, but at least I could breath easier seeing boot animation.
[Verizon Motorola Droid Turbo Android Development] MonkeyMouth:
I'm using the first mofo release. I didn't know it's been updated. The flashing for me takes like 10 seconds and continues with the prompt. I've used it to root 4.4.4, but it's been a while, I'm lost.
[Verizon Motorola Droid Turbo Android Development] ntxct:
Sounds like we were in similar boats.. after immediately buying mofo in march and flashing an image I havent touched it since then, so I was playing the catch up and the "how did I.." game last night.. my best advice is to watch or rewatch Tom's mofo video: Youtube Linky

Today I just figured out how to update mofo.. run mofoverify again in bootloader mode, copy link, redownload mofo and boom, .0.0.3

The 10 second thing tells me something isnt right.. from a technical standpoint mofo is moving like 3.5(?) gigs of information, so even at the fastest known transfer rate it should still take longer than 10 seconds. That said I remember people saying to use usb 2 and not 3.. which would make flashing even slower...
[Verizon Motorola Droid Turbo Android Development] MonkeyMouth:
Sir you are a savior, lol. If you didn't mention mofo being updated I would have been lost. I'm currently on the "Android is upgrading..." prompt.

For those who are nervous. Recovery flashed and didn't work. Booted to the animation. Let sit for a few minutes. Hard rebooted and loaded recovery (which stayed this time). Wiped cache (took five mins, lol). Rebooted. Sat at animation for 5-10 mins.

Now I just need to install extras. Thank you again ntxct.
[Verizon Motorola Droid Turbo Android Development] JulesJam:
When did it get updated? I have version 0.0.2, should I update it?
[Verizon Motorola Droid Turbo Android Development] Mattish13:
It seems fixable.

http://xdaforums.com/showthread.php?p=61771016
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Go to mofo site and do the steps with your phone connected it will pick up your id and let you download the new ver. you need the new ver it will fix this.
[Verizon Motorola Droid Turbo Android Development] MonkeyMouth:
Already done that. I'm loaded. I just want to get xposed injected.
[Verizon Motorola Droid Turbo Android Development] ntxct:
I'm not entirely sure when it was updated, it appears when more Moto X support started to get added? Maybe?

Anyways I did this whole 4.4.4 to 5.1 process on Mofo .0.0.1 And it worked.. it also worked how .0.0.1 worked before... Flashing: 13%...14%....15%... failed... Somewhere around the 4th-5th try it finally 100%-ed the flash of 5.1

So I havent had a reason to try .0.0.3 and I randomly saw someone post to someone else that the later versions are more reliable at flashing.. It was buried somewhere in the Mofo thread.
[Verizon Motorola Droid Turbo Android Development] MonkeyMouth:
Has anyone had luck making an image with the patch the patch provided and flashed successfully?
[Verizon Motorola Droid Turbo Android Development] siegesoldier:
Yes. The easiest way to do it is to download Xdelta from the link provided and save it to your desktop. Then open a command prompt and drag the xdelta.exe into the command prompt. Then add

(Space)

-d -s

(Space)

then drag the image file into the command prompt

(Space)

drag the patch file in to the command prompt

then press enter

it will look like this if all of your stuff is on the desktop. Messy but it works.

C:\Users\name\Desktop\delta.exe -d -s C:\Users\name\Desktop\image.img C:\Users\name\Desktop\image.patch
[Verizon Motorola Droid Turbo Android Development] pjsockett:
Worked for me as well. I made a folder that had the image, patch and xdelta3 in it and then opened a command prompt in the folder. Installing straight over the top of my 4.4.4 build with exposed most of my modules still worked even before I updated xposed.
[Verizon Motorola Droid Turbo Android Development] gqskrub:
Working now. I think it was just a reboot.
[Verizon Motorola Droid Turbo Android Development] MonkeyMouth:
Okay. I cannot, for the life of me, get this patched img to boot past the animation. Anyone have a spare patched img for me to try?

Nevermind. lol. Just took like 4 reboots. (into fastboot. Back to M logo. (Not intentionally))