yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] ThaSik1:
True but I peeked over in his original thread and he posted it for another dev since it's similar to the "unified tree" that the devs have created for the Samsung devices. Didn't know if anyone else had given it a test drive or not :p Guess until he clarifies, I'll stick to an older version if it works for recent roms like Eclipse. Thanks tho mate!

Sauce: http://xdaforums.com/showpost.php?p=51162031&postcount=3026
[Moto X Android Development] DaRkRhiNe:
so it wont work on XT 1052 variants ?
[Moto X Android Development] :
Doesn't say it will in OP.

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Moto X Android Development] letscheckitout:
Hey,

i just now successfully completed rooting my XT1052 using the custoem twrp at the below link.

http://xdaforums.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850

hope it helps.

thanks
[Moto X Android Development] aviwdoowks:
Truth is the dev, Phil3759 , has his hands full, cannot test compatibility for all x variants. I would bet the one version version works on all. But he needs more on his team from our crowd. Edit: I am unrooted!

---------- Post added at 09:30 AM ---------- Previous post was at 09:25 AM ----------

The Older msm8960s are on a unified build. The new 8960s could be too.

http://xdaforums.com/showthread.php?p=51980733

---------- Post added at 09:42 AM ---------- Previous post was at 09:30 AM ----------

Look what [MENTION=2658922]hachamacha[/MENTION] has done! Not to mention THE DEV Phil...
[Moto X Android Development] hachamacha:
Hey aviwdoowks,

I think a key questions that Phil3759 asked back on the first few pages of this thing in response to a request from someone was of this ilk:

"Show me a kk/cm11/{yourdevice} tree on github". That's one of the things that makes a 'unified' build doable without anyone having to devote too much more of their life to it. I have to keep this short since I am currently nursing a useless left hand back to health ;)

There usually good reasons why you can't take say, one device's code and get it to run on a pretty similar device (say xt925/926), which makes those unified builds cool. Similarly, there's other good reasons why one unified build (based even on msm8960) won't run on every msm8960xx chip. If you are rooted, unlocked, whatever on this moto X (that I don't have), well, give it a try if you don't mind recovering from it. It's just recovery and should be easily fixable from either fastboot or flashify or however you want to flash a recovery. (disclaimer, just be careful, geez).

I did a little reading and from this site noticed this about msm8960 and if it's to be believed msm8960dt unified builds (your chipsets all seem to be in that *dt list): Site: http://www.androidheadlines.com/2014/02/cyanogenmod-releases-unified-cm11-nightly-builds-moto-x-moto-g-verizons-moto-droid-devices.html

Quote from that site:

The Philz Touch Recovery world seem to work best if someone that has one of the phones and is interested (and can setup at least a basic build system on some version of Linux even in a VM) takes an interest. In a nutshell, msm8960dt is already in the kk/cm11 tree. Does it work? Not a clue but from the snippet above, it seems possible, and the unified build contains everything from the Ultra/Maxx/Moto/..

Phil's clearly done some work since I see 6.26.* builds under xt10*. I'm really not at all up on the moto/maxx/ultra world but it sounds like the state of unlocking is now pretty bad (or rooting). If I could type OK instead of doing this on the slow, I'd crank out an msm8960dt build just to see if anyone could use it and which devices worked but the best solution would be for one of you to do it. Just get cm11, figure out how to build standard CWM advanced recovery, and then substitute Philz3759 recovery for CWM (./bootable/recovery). Add a clause to ./boardconfig/BoardConfig.mk for the msm8960dt, build the thing and well, good luck ;) (yes, sometimes there's more to it than that, but his faq in main thread is pretty comprehensive).

I'm sure Phil3759 will tell me the ways in which whatever I just typed here are wrong if he happens by. (or I hope so). Cheers. I'll be back when my typing is better again (3-4 weeks).
[Moto X Android Development] Phil3759:
too long post :o

what is exactly your issue?
[Moto X Android Development] hachamacha:
Well, that took a long time ;)

It's not clear to me that there is an issue since I see you've got pretty current versions of your stuff for these moto's. I was just encouraging someone to get into the unified aspect of doing one of your recoveries here. Yeah, it was way too long..
[Moto X Android Development] Phil3759:
The first step to unify them is to have a same kernel running on all devices

After that, ro.bootloader output from each variant must be known

We can then use a unified flag to hack in init binary

You can look at jflte, falcon and klte implementations for how to do this:

for jflte:

https://github.com/CyanogenMod/android_device_samsung_jflte/blob/cm-11.0/BoardConfig.mk#L69

# Vendor Init
TARGET_UNIFIED_DEVICE := true
TARGET_INIT_VENDOR_LIB := libinit_jflte
TARGET_LIBINIT_DEFINES_FILE := device/samsung/jflte/init/init_jflte.c

and see init_jflte.c source

rather easy to do, but better for someone owning at least one variant
[Moto X Android Development] hachamacha:
Intending to do up to date Unified msm8960dt builds

I've been doing the unified moto_msm8960 builds (that work with devices like xt926/5/etc) over here:

For MOTOX/ultra/Maxx/etc, the CM11-based unified build of Philz Touch recovery is named moto_msm8960dt. I've just started to create builds for it so that you'll have up to date builds here. I got in on the mother's day sale at Motorola and ordered a Moto X to use and test development on so as soon as I get it and test my builds, I'll put up a post, a list of which devices are in the unified build (supposedly) and you can check off which one's work with the unified build.

Should be sometime next week, maybe late next week. Philz Touch is currently built to Version 6.40.1 which has quite a few enhancements from the last ones posted here. I'll put up a detailed post if and when it works.

Cheers.

All credits to [MENTION=4666971]Phil3759[/MENTION] and the CM team.

PS: I won't be around much this month but if you're dying to try a build and probably screw up your device , then you can try to PM me. These are untested so don't come after me with a bazooka if your gizmo melts. ;)
[Moto X Android Development] Phil3759:
:good:

I added you as contributor

You can now edit OP as you wish: post direct links to your download pages, updated versions, redirect users to your own thread...

It is up to you to edit as you like, really

Just keep the title so that I can monitor it easily
[Moto X Android Development] hachamacha:
Thanks. The only title change I'd think about making would be from this:

[xt10xx][CWM Advanced Edition] PhilZ Touch

to this:

[msm8960dt][CWM Advanced Edition] PhilZ Touch - unified

In other forums of devices that work with a unified build, I'd likely just point them to this thread. It seems silly to replicate the entire thread everywhere, but nice to provide device-specific answers in whatever device forum(s) they use.

If it turns out that unified recovery builds for msm8960dt don't really do the job (I'll possibly find out later today), then I won't be changing any titles, just adding a little info.
[Moto X Android Development] Phil3759:
sure, no problem in that case
[Moto X Android Development] hachamacha:
It shouldn't be too long now for updates: I just received a device today and have unlocked and installed a unified recovery I built. It's still got an error that I'm working on as time allows, but at least I've got something to test with. I'll post again when I make some progress on the unified build.
[Moto X Android Development] serophia:
So i recently got the Developers Edition and i unlocked and used this recovery and was able to get root using supersu, had to fix root from recovery and redownload supersu from playstore. I seen a couple of post where people say we can not root 4.4.2? If this was true how was i able to obtain it x.x
[Moto X Android Development] hachamacha:
I haven't been keeping up with the Moto X (until that Mother's day sale came along) but I think that 4.4.2 on the non-DE devices locks it down. Since you got a DE (so did I from the site on the mom's day sale), of course we can root it. It makes no difference what version android OS you run if you're able to unlock the bootloader. I've finally gotten mine setup enough to use this afternoon. Neat phone.

As far as a new version of Philz Touch unified goes, I've got to figure out what needs to happen to deal with the f2fs /data partition and also need to get inside using adb during a recovery session to figure out what's up with /sdcard as well. Using the non-unified builds (xt10xx..) work's fine so aside from me not being here much this month , it shouldn't be long before up to date recoveries are rolling out ;)
[Moto X Android Development] serophia:
Ahh thanks for the clarification xD, yea i just got my device yesterday as well! All i did was root and installed xposed and greenify! For now ill see how long the battery lasts for. One thing i do like is the active notification :P the touchless control i hardly use but no biggie
[Moto X Android Development] :
Yes you can root 4.4.2 on a dev edition....same as any other Moto x that can have an unlocked boot loader. All moto x's with unlocked bootloaders root the same way. Nothing is different. Well, dev edition keeps its warranty.... That's the only difference.

4.4.2 on locked phones, like Verizon and at&t phones are out of luck....if they are already on 4.4.2 anyway. ;)

---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------

Not completely true....see my post above. :)

And also, it does matter what android version you are on....cause with the dev edition, just like any other unlocked moto x brand.....once on 4.4.2....always on 4.4.2.

Downgrading from 4.4.2 on any moto x, locked...unlocked... Dev...non dev....can lead to a bricked phone.
[Moto X Android Development] hachamacha:
Thanks for the info. I just didn't have it in my head that I'd downgrade this thing so hadn't looked into that. I've been running various takes on 4.4.2 for a bit now and do like it, with the usual caveat (being: "Aside from a few irritating quirks") ;)
[Moto X Android Development] :
If you get tired of it....I know stock, rooted and gravity box is the majorities preference. :)
[Moto X Android Development] hachamacha:
I just got the most recent build of Philz Touch to work on the Verizon version, but the unified build (I'm using part of it) is elusive so far. OK: That's the build news for now. I may edit the OP and allow downloads on the xt1060 build, perhaps will build the rest for now, and keep working on the msm8960dt unified one.

Anyway, about your comments on not being able to downgrade the Moto X:

I realized I'd setup my xt1060 DE in what might be an unusual way. I never used any OTA's, never booted it at all until I was completely finished with the setup. I only used mfastboot and the 4.4.2 file for DE from the Motorola site. I'm wondering if this no-downgrade has anything to do with:

a) receiving OTA's while back in an earlier version? or

b) that the "evil magic" happens if you boot before you set things up how you want them.

The reason I now question it is because I did a chat about the DE on the Motorola site, and kept asking for someone who actually understood the DE. When I got someone, I mentioned the obvious flaw of a DE model that costs extra not being able to do well, basically the things a galaxy nexus could do (a real DE). I was told that downgrades were supposed to be possible if you knew what you were doing. I described what I'd done and he claimed I could downgrade that way, doing it all from mfastboot and if it didn't work, then I could a) return it in the next 2 weeks for refund, (or more likely just sell it) or b) get a replacement DE from them for a full year, no limits.

Armed with just this little bit of dodgy information and being a complete idiot, I figured, better now than later, and got the earlier 4.4.13 version from the website (the .xml.zip version), made myself a shell script to try to install it, rebooted into fastboot, and used the script to install 4.4.13. No errors, but then again, I didn't even bother to boot it since this was a first step and I've yet got a bit more time where I can get a refund. All "mfastboot flash * * " commands returned with success. I then switched back to my 4.4.2 folder, and ran that script, which all returned with no errors, installed the above recovery, and installed .. oh yeah, eclipse kitkat, booted up, and things are fine, as before. No possibility exists of my getting an OTA and if you setup the phone entirely before the first boot, I'm not sure how you could get an OTA doing things this way.

OK, enough of this epic/saga. Just some thoughts. ;)
[Moto X Android Development] :
Well, when I and others say you can't downgrade from 4.4.2.....we do realize there are very precise way(s) to do it. But I'm not telling them how, or even pointing them in the right direction. I'm staying completely out of it with a nope, can't downgrade. ;)

But if you Google "moto x brick xda", you'll find threads about it. Yes..most were from downgrading, then taking an ota. But not all. Its a risky venture no matter what. And MANY mess up instructions, happens all the time, and this could be a $350 mess up.

So for me....I say nope, can't downgrade. And if someone wants to dig into it, read up....and figure out how you can do it semi-safely.....then I say good for them! That's what XDA is all about, learning and playing. Don't ever think anyone on xda knows everything. So researching on your own is always the best bet. :) But at least I know I will never get a pm saying "dude, you said I could downgrade and I messed up a step and bricked!!! “ Lol

Personally, I still think its risky. User error happens....and boom....brick. Or another beef I have, someone downgrades....never takes an ota....all is well....sells the phone...they don't know it was downgraded, and boom....they brick their new toy. Lol

See where I'm coming from. ;)
[Moto X Android Development] hachamacha:
Good post ;). and point taken about where you're coming from.

So without talking too much about it, I've become "interested" now, and am messing with critical components of the boot mostly because as you note, lots of people are saying that thing that gets me interested more than anything which is "You Can't do it". . No doubt, I'll brick this thing eventually (like today), and send it back, but it's a lot of fun until then. I've had a bunch of regular linux experience making initrd or boot.img systems and am just playing with those things today.

But none of this is about this thread about Philz Recovery so I'll stop mentioning it ;)
[Moto X Android Development] hachamacha:
Version : 6.41.5 Stable added

Download 6.41.5 for your device from the OP:

Note: Still working on unified msm8960dt build, in the meantime, this was a significant release so I just did one for each device.

Latest version for the xt10xx's: 6.41.5 Stable -

Changelogs:
[Moto X Android Development] hachamacha:
Version : 6.41.6 Stable to be added

DL From OP:
[Moto X Android Development] trentonmc24:
When I first got my dev edition moto x I created a nandroid backup before rooting, with 4.2 (JB), now that I've upgraded to 4.4.2, if I was to restore that 4.2 backup, would that brick my phone with the efuse or whatever? If so I'll delete that backup now just so I don't accidently do it one day... Thanks
[Moto X Android Development] dimqs153:
mine is Moto X Sprint using 4.4 firmware n Unlocked.

try to flash ur recovery using cmd on windows n succeed but i can not come in recovery?

any sugestion?
[Moto X Android Development] aviwdoowks:
Extract the IMG file from the zip. Then use recovery tools from play to install the img from homescreen
[Moto X Android Development] dimqs153:
first of all thx for fast response

yes im using IMG file.

what is the tool name?
[Moto X Android Development] aviwdoowks:
Search the play store for "recovery tools" & install. It can put the IMG in your recovery partition.
[Moto X Android Development] dimqs153:
i think its need root access

im flashing recovery for rooting
[Moto X Android Development] aviwdoowks:
Well that is different, I would use

http://xdaforums.com/moto-x/development/tool-moto-x-toolkit-v1-2-1-t2477132

There is a Mac version too.
[Moto X Android Development] :
I'm just guessing as I've never done it, or read about anyone else doing it....but my guess is it would fail due to the 4.4.2 bootloader. That's best case scenario......worst case is brick... Or accidentally taking an ota after, then bricking.

Or it could work.....but honestly, if it did....it would be all over the forum that it works I would think.

I wouldn't risk it....others may tho. ;)
[Moto X Android Development] trentonmc24:
Now I'm curious and wanna try it, but I think I'll just delete the nandroid to be safe.
[Moto X Android Development] aviwdoowks:
Edit

I found out that a nandroid restore from a different X causes data corruption that only a format of data & data media (internal SD) will fix.

There are just toooo many build specific items in /data for it to work. I do not think any recovery touches the bootloader, afaict, if data booted it should work. Data is key. I have done it if builds are close enough, it works but only one same phone. If imei's are different then that is unknown territory...
[Moto X Android Development] aviwdoowks:
Mount USB storage appears not to work while OTG does. Do any versions, previous to the latest, work for USB?
[Moto X Android Development] aviwdoowks:
We have a APP now that allows easy Phone Up backups. Works well with Philz. I upped my philz-touch_6.ini.bak which make Philz as pocket-proof as TWRP.

Online Nandroid Backup
[Moto X Android Development] aviwdoowks:
I just did a full restore (boot, recovery,data & sys) to a different X & it works 100%.
[Moto X Android Development] trentonmc24:
You went from 4.4.2 and restored back to 4.2 with no problems?
[Moto X Android Development] aviwdoowks:
Delete
[Moto X Android Development] aviwdoowks:
Sorry for this FALSE notice of success!!!

Uninstalling any data app causes a reboot!!!

I must RSD The XML now.

---------- Post added at 09:04 PM ---------- Previous post was at 08:57 PM ----------

Do NOT try it. See previous post
[Moto X Android Development] gokart2:
Wow. Why isn't everyone using this? Reminds me of 4EXT Recovery on my old EVO3D, also another great recovery. This recovery is awesome, thank you!
[Moto X Android Development] diegons49:
Mount USB storage is not working?
[Moto X Android Development] dsbalieiro:
It worked perfectly on my XT1058! Good job [MENTION=4666971]Phil3759[/MENTION]! I followed the thread to stay on top of updates and new releases. Wonder!

Enviado de meu XT1058 usando Tapatalk
[Moto X Android Development] 338lm:
Do you think this is safe to flash with the 4.4.3 update?
[Moto X Android Development] rgbc:
I fastboot flashed PhilZ onto my Moto X and Nexus 5 after OTA to 4.4.3 and used it to install Superuser, up and running with root.
[Moto X Android Development] pyromaniac1:
Which one should i use if i have XT1050?
[Moto X Android Development] leon912:
solved. delet
[Moto X Android Development] Yann68:
Which should i use for xt1052 ? Anyone know ???...
[Moto X Android Development] Yann68:
Which should i use for xt1052 Europe? Thank you.
[Moto X Android Development] hachamacha:
Trying new unified version : 6.48.4

I've been out of the country awhile, just back and trying to update things:

Here is a unified version that seems to work fine on my 1060. You can get it from the OP (in a few minutes): I don't know if it'll work on all models but please let me know:

Download image:
[URL="http://d-h.st/yKU"]Image version[/URL]
Download Zip:
[URL="http://d-h.st/fcH"]Zip Version[/URL]

Edit: Seems like I may have jumped the gun on that last version having just found this a few pages back in the main thread:

Unfortunately I don't have time to roll my code back to that and regenerate until late today but 6.48.4 seemed OK for me so just let me know how it works if you try it.
[Moto X Android Development] VerneVerne:
I was successful with backing up and restoring on my xt1056 with your latest unified build. Haven't really tested much more than that quite yet.
[Moto X Android Development] diegons49:
Thanks for the update!
[Moto X Android Development] hachamacha:
Version : 6.50.6 Stable added

Download from OP please:
[Moto X Android Development] Phil3759:
I added your common build to the goo mirror :good:

Can you post the changes you need to board config?
[Moto X Android Development] hachamacha:
Thanks: Here is the patch file for BoardConfig.mk:

--- boardconfig/BoardConfig.mk.orig	2014-07-15 05:46:37.280959930 -0700
+++ boardconfig/BoardConfig.mk	2014-07-15 05:49:00.911301356 -0700
@@ -854,8 +854,8 @@
TARGET_SCREEN_WIDTH := 720
BRIGHTNESS_SYS_FILE := "/sys/class/backlight/lcd-backlight/brightness"

-#Motorola Moto X: TMO (xt1053), US Cellular (xt1055), Sprint (xt1056), GSM (xt1058), VZW (xt1060)
-else ifneq ($(filter $(TARGET_PRODUCT),cm_xt1053 cm_xt1055 cm_xt1056 cm_xt1058 cm_xt1060),)
+#Motorola Moto X: TMO (xt1053), US Cellular (xt1055), Sprint (xt1056), GSM (xt1058), VZW (xt1060), and Unified msm8960dt build.
+else ifneq ($(filter $(TARGET_PRODUCT),cm_xt1053 cm_xt1055 cm_xt1056 cm_xt1058 cm_xt1060 cm_moto_msm8960dt),)
TARGET_COMMON_NAME := Moto X ($(TARGET_PRODUCT))
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
[Moto X Android Development] hachamacha:
Version : 6.54.9 added

Please download from OP:
[Moto X Android Development] hachamacha:
Version : 6.55.0 added

Please download from OP:
[Moto X Android Development] hachamacha:
Sorry but I'm not showing 6.55.0 on the latest build , so it is either me or not.

I know I checked the Android.mk file before building and it was 6.55.0 , also cleared intermediates and recovery.img so it's likely the newest build regardless if it says 6.55.x or 6.54.x, just wanted to mention.

Edit: New builds up of 6.55.0 that are the correct version.
[Moto X Android Development] hachamacha:
Version : 6.56.2 added

In the OP:
[Moto X Android Development] gokart2:
Thanks for the best recovery ever!
[Moto X Android Development] x000x:
so.. if i have XT1050 am I out of luck? I see pretty much every version listed except XT1050 :(
[Moto X Android Development] hachamacha:
Not necessarily. It depends what devices are considered part of the unified build (CM11-wise). I'll look around and see what is included these days since there were just some cm11 changes on Motorola unified builds.

I need to try to kick out a new build for this device anyway.

Edit: I took a look at Philz/BoardConfig.mk and it's not yet in there, and I also aren't seeing it as part of cm11. I've not got the device so can you give me a description (carrier? protocol type, anything unusual compared to say xt1060?) : Also, have you just tried say, the last build of recovery from the OP?
[Moto X Android Development] x000x:
I'll send you a pm so as to not clutter the topic :)
[Moto X Android Development] hachamacha:
Version : 6.57.5 added

Please download from OP as soon as it's updated:

Change log: (If I can find it):
[Moto X Android Development] hachamacha:
Version : 6.57.8 added

In OP:
[Moto X Android Development] waiwang:
Good to see new version but still no xt1502. Feeling sad.