yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] ShorelineDroid:
It will be for unlocked bootloaders to start. I will try a safestrap build but can't guarantee anything. Kit Kat brought changes to pretty much every partition so it might be a little challenging for locked bootloaders unfortunately but I'm not saying improbable.
[Moto X Android Development] ariperelman:
Ok, so I flashed 4.4 on my Moto X, versión Retail Latam

It works, just a little buggy, but no big problems so far, but after reading about after the flash (yes, i'm that stupid) I realised that I cannot go backwards to 4.2.2 stock, so I'm screwed.
[Moto X Android Development] jimmypop13:
Please if you do this, can you do it like the other Roms here and not include radios? I think we just need system.img and boot.img? It would be so nice to be able to flash this on any unlocked moto x.

Please!
[Moto X Android Development] jimmydafish:
Well, what I suggest is that you play around find out what you can do and document it for others. Either you can blaze the trail or you can sit back and be a lemming.
[Moto X Android Development] TooSlo:
I'm super excited to see this new version. Hopefully it'll be available by the time I get off my plane flights tonight!

Thanks so much for your hard work mate!
[Moto X Android Development] ShorelineDroid:
Unfortunately, if you haven't done it already you will have to update your partitions if you want the ROM to run right...I will be making a new thread with instructions to make it a little more user friendly but if you want a ROM with no bugs and to enjoy it you'll have to update everything kit Kat needs.

I'm still trying to get my twrp build working flawlessly so it can back up and restore as well as flash but I should have everything up tonight folks! Please be patient and keep an eye out for the new thread!!
[Moto X Android Development] flashallthetime:
I don't know if you're aware or not?

Dhacker has 4.4 twrp and cwm recovery already done, running twrp on my moto right now. What would be the difference between your recovery and dhackers recovery?

Sent on my Moto X
[Moto X Android Development] jimmypop13:
Thanks for the info! I've flashed the newer verizon radios that came with the camera update in fastboot so if something like that is all I need to do again after flashing, that's not so bad. And I ran a t-mobile rom before so I know about having to switch the radio settings to cdma/lte auto(prl) in order to get calls and txts. Instructions would be great though in case anything else needs to be done I don't know about!

Thanks for all your hard work!

---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------

Is it okay to run twrp 4.4 recovery on 4.2.2?

I couldn't find it at first because dhacker didn't update his thread here but I found it over on rootzwiki

http://rootzwiki.com/topic/103457-twrp-263-with-f2fs-support-for-unlocked-bootloader/
[Moto X Android Development] flashallthetime:
Well I guess so, flashed dhackers 4.4 aosp ROM with it and restored my 4.2 ROM afterwards without any hick ups:D:D

Edit, looks like kitkat for AT&T motos is on its way,

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

Sent on my Moto X
[Moto X Android Development] ShorelineDroid:
Yup looks like dhacker29 is already on the clock lol head over to his androidhosting.org site for his taste of kit Kat!
[Moto X Android Development] flashallthetime:
Its huge almost 1 GB? Doesn't sound right to me

Sent on my Moto X
[Moto X Android Development] jimmypop13:
Well I just downloaded the whole thing and tried to extract it to see what's inside and I got an error saying bad zip. So I definitely wouldn't try flashing it!
[Moto X Android Development] flashallthetime:
Yah, you're a brave soul. I stopped the download after I realized the size was way out there.

Sent on my Moto X
[Moto X Android Development] Cheerpipe:
My moto x running kitkat. Runs smoother than jellybean.

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Android Development] jimmypop13:
Did you see my edit? I got a bad zip error when I tried to look in it
[Moto X Android Development] phositadc:
I've read this entire thread but there seems to be some conflicting information. I just ordered a T-Mobile Moto X. Want to flash 4.4. Am pretty competent with fastboot / command line / etc. Unlocking bootloader is no problem.

What's the best way to get 4.4? Just flash the system.img and the boot.img? Or should I flash the entire package?

If you flash the entire 4.4 package, is it possible to return 100% to stock 4.2.2 just by flashing the FXZ files?

If you flash the entire 4.4 package, will you get the official 4.4 OTA when it comes out? Or will you have to return to stock 4.2.2 before you can get the OTA?

Thanks in advance if anybody knows the answers.
[Moto X Android Development] ShorelineDroid:
Is this the 4.4 tmo leak or aosp? If leak did you modify the systemui.apk for the white notification icons?

---------- Post added at 10:17 AM ---------- Previous post was at 10:12 AM ----------

I can't get mine or dhackers 4.4 recoveries working yet as I may have done something to my recovery partition messing around so I'm just wondering if someone is interested in flashing my build of this leak? I downloaded dhackers to check it out but it's just the leak compressed into a zip folder so I'm going to release mine but I need someone who has already updated the bootloader and baseband to KitKat with a running recovery. I've seen a couple posts in this thread of people who have a running recovery. Send me a pm for some flash fun!
[Moto X Android Development] Cheerpipe:
Moto KitKat, i modded systemui to get aosp icons.

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Android Development] jimmypop13:
Can you teach me what I have to change to get it white like that?
[Moto X Android Development] Cheerpipe:
Sure

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

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Android Development] phositadc:
Could somebody PM me a link to download the 4.4 fastboot images?
[Moto X Android Development] TooSlo:
I'm curious about this as well. The links were taken down while I was on holiday, and dhacker's version fails when trying to flash through the newest version of either recovery.
[Moto X Android Development] flashallthetime:
Dhackers version is the fastboot files I believe, 994 mbs is way to big for a moto flashable rom

Sent on my Moto X
[Moto X Android Development] TooSlo:
The version he has on RW was only 172.2 MB, but it errored out when flashing.

Does anyone have a fully functioning recovery yet? I've tried the dhacker version of twrp 2.6.3 (twrp263-ghost44.img) as well as his 4.4 version of cwm 6.0.4.4 (cwm6044-4.4.img) that have been linked around the forums. CWM will hang and eventually reboot when selecting the "install from .zip" link, and TWRP is hanging on the splash screen and eventually reboots back to the OS.

If someone has a functioning recovery image that will allow you to flash the CF SU.zip, I'd greatly appreciate it.

As I've been able to mount /system through CWM 6.0.4.4, I was able to push the su file to /system/xbin/ and CHMOD the file to 6755 per some instructions earlier in this thread, but when trying to install and run the SU.apk while in the OS, it says that the binaries are missing and fails the SU check.

It seemed some people were able to load the SU.zip through CWM, or properly chmod the binary to 6755, but it's just not working for me right now.
[Moto X Android Development] Cheerpipe:
What i did yo flash root

1.- flash stocks recovery ( fastboot flash recovery recovery.img)

2.- boot into recovery (stock)

3.- reboot into fastboot mode again. (Reboot from recovery while vol down pressed)

4.- flash cwm recovery.

5.- go into recovery (cwm)

6.- mount data and system.

7.- flash root (i use chainfire's one)

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Android Development] TooSlo:
It looks like the way you suggested to re-flash recovery allowed me to mount /system/ and /data/ while in CWM. I can install the su.zip from CF, and it looks like it succeeds, but when I try to open the Superuser.apk on the phone, it says that the binaries need to be updated, and then fails the update.

I'm all for hearing any other options, but for now, I'm headed to sleep. Thanks for the suggestions, hopefully you have another idea up your sleeve. Cheers.
[Moto X Android Development] beelzebu:
Update the binaries using normal option, rebooting CWM will not work. I did it that way succesfully.
[Moto X Android Development] 181charan:
The MOTO Droid Ultra/Maxx has 2GB of system memory AFIK if u navigate to your system you see that it shows 1.0Gb/2.0GB! assumed its the same for a Moto X as well but only thing that surprises mw is that MOTO X FXZs are around 400MB while the Droid Ultra/Maxx have around 750MB.. And except for the useless verizon apps everything else is the same!!! I wonder why... :confused:
[Moto X Android Development] flashallthetime:
I really think were in for a ride when kitkat comes out officially, custom recovery needs to be worked on as dhackers 4.4 trwp recovery does not boot, I just in the process of rsd lite back to stock for the second time. I just might stick with jb 4.2 for awhile:eek::eek::eek::eek:

Sent on my Moto X
[Moto X Android Development] TooSlo:
I'm sorry. I don't quite understand what you mean by "the normal option."

I've attempted to update the binaries through the SU application, but get a permissions failure when doing this. I suppose I may try to re-do everything today and see if it behaves differently this time around.

Could someone who has successfully updated the SU binary pull it and upload to the forums? I'd be curious to just push that through fastboot to see if it grants me permissions.
[Moto X Android Development] beelzebu:
ok so you where able to install supersu using TWRP or CWM right? if so when you open supersu app will say binaries needs to be updated, then you have two options, normal or recovery I chosed normal and everything went fine. I have root. that's it.
[Moto X Android Development] TooSlo:
Huh. I'm not getting that option when installing SuperSU. Can you upload the .zip that you installed through recovery? I'd like to check it against the one that I downloaded from CF's site.
[Moto X Android Development] uljanik:
hello,

I have to do to get everything to 4.4 and where can I download the files?

I have read and do not know what to do.
[Moto X Android Development] beelzebu:
I did not installed any special package, just installed twrp and reboot from there, it will ask me if I want to root and said yes. after that I got an ican on android telling me to install supersu from google play or another source I choosed from google play, after installation it is where super su was installed and then ask me to update the binaries though normal or recovery.

hope it's make it clearer
[Moto X Android Development] TooSlo:
That definitely helps. Which version of TWRP are you using? I couldn't get the 4.4 version to load past the splash screen. I'll give it a try in a little bit when I get home.

Thanks!
[Moto X Android Development] beelzebu:
in the first post are the instructions, here you can get the file: http://androidhosting.org/Devs/Dhacker29/MotoX/tmobile_motox_4.4.zip

---------- Post added at 06:45 PM ---------- Previous post was at 06:39 PM ----------

to root this is what I did.

1 install the leak. (do full wipe)

2 after the leak installed reboot into bootloader again, prior configuring the phone

installed twrp from here http://androidhosting.org/Devs/Dhacker29/MotoX/

3 fastboot TWRP ghost 4.4,

4 just reboot into bootloader and fastboot stock recovery (Optional)

5 configure your phone as normal

6 super will ask to install supersu, use google play method,

7 after supersu is installed update binaries using normal option.

enjoy.
[Moto X Android Development] MEGABYTEPR:
Has anybody compared this to the T-Mobile 4.4 leak? I can see this one has some AT&T stuff in it.
[Moto X Android Development] Cheerpipe:
ATT ota has working ART runtime :D

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Android Development] TheOrangeRemix:
Updated link in OP.
[Moto X Android Development] TheOrangeRemix:
Updated build in OP. Now with white KitKat icons and support for Tap to Pay with Google Wallet!
[Moto X Android Development] Cheerpipe:
Is art working in the new build?

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Android Development] tw1tch175:
Do we have a recovery that work right yet? With the last builds had to temp install before setup then sideload the SU zip.

Yup and unlike the AT&T leak it has the new dialer =D
[Moto X Android Development] phositadc:
So it's even newer than ATT OTA? Sweet. Will flash for my wife today.

Sent from my Nexus 5

---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------

Edit: wtf if the screenshots in the OP are of this build then it still has the stupid gap with the LTE icon between WiFi and signal strength even when WiFi is on and connected. I really hate that. ATT build got rid of that and had WiFi icon right next to signal strength icon (like everybody else except Motorola).

Sent from my Nexus 5
[Moto X Android Development] jimmypop13:
What all do I need to change if I wanna flash this on a vzw Dev edition? I know I need to avoid the radios. Or would it be easier to just flash the whole thing and then flash the two radio files in fastboot afterwards?
[Moto X Android Development] lensgrabber:
This might be a stupid question for some people but I want to be 100% sure before doing anything. I have a GSM Dev Edition, bootloader unlocked. Is it safe for me to flash everything, including radios, in the OP? I'm assuming the answer is yes but would rather hear from someone else before taking the plunge.
[Moto X Android Development] tw1tch175:
Yea, you're fine you can flash AT&T or Tmobile leaks without issue.
[Moto X Android Development] phositadc:
Has anybody flashed Cheerpipe's AOSP status bar mod from http://xdaforums.com/showthread.php?t=2520346?

I'll be trying in later this afternoon but would love to know if anybody else has had success/failure with it!

Sent from my XT1053
[Moto X Android Development] lensgrabber:
Same problem. Did you resolve it on yours?

EDIT: Nevermind, flashed stock recovery and did a reset there then installed TWRP as beelzebu said earlier. Appears to work. Now to get everything restored.
[Moto X Android Development] lensgrabber:
Got everything restored. Tap & Pay is showing as "not available" on the device. Is there any hackery that has to be done for this to work? *This* was the main reason I wanted 4.4.

EDIT: Got it working!

Grab the apk from here

http://xdaforums.com/showpost.php?p=47433727&postcount=391
[Moto X Android Development] phositadc:
trouble with flashall.bat

I'm trying to run the flashall.bat from today's leak, but having trouble.

When I run the flashall command, it says "waiting for fastboot enumeration . . . ." and then repeatedly says "The system cannot find the path specified."

fastboot devices shows that my device is recognized. I could just flash each piece manually, I guess, but I'd prefer to run the flashall.bat script.

Any ideas? Cannot find the path specified makes me think the filepath is wrong or something.
[Moto X Android Development] Cheerpipe:
Change the line with fastboot path, remove the c:\windows\part.

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Android Development] phositadc:
Lol, thanks! Did it and it worked. Gonna flash your SystemUI mod here in a minute if I can get a custom recovery to work.
[Moto X Android Development] phositadc:
Bazinga! Running the latest leak + Cheerpipe's awesome SystemUI mod. Working great so far.
[Moto X Android Development] Steve-x:
Have two Moto X's so I am trying both this tmobile leak and the at&t leak running side by side. So far I have to give the edge to the at&t leak, while it has a little bloatware it doesn't have the bugs2go or the battery tracer. I have also had the tmobile lag just a little when unlocking, I have never seen that with the at&t leak.

Looking at the compile dates of the two I suspect the engineers are in different states as one is compiled in pst, the other in cst.

thanks for posting the updated tmobile image.

Now someone dig up a Rogers Canada leak as its my favorite stock firmware thus far.
[Moto X Android Development] MEGABYTEPR:
I tried both and I agree with you also, I think I'm going back to the AT&T version for now, what do you think?
[Moto X Android Development] lensgrabber:
I can confirm that with the Wallet APK I posted a few posts up that tap-to-pay works just fine.

My problem is that I cannot get TWRP to boot unless there has been a factory reset. Once I boot into the rom and set up my account, TWRP just hangs at the splash screen and eventually reboots. I have tried both the twrp263-ghost44.img and previous twrp263.img which was working on the 4.2.2 rom. Both do the same thing. CWM reboots when I try to backup anything. Anyone else having these problems? I have not tried the AT&T rom yet.
[Moto X Android Development] phositadc:
I rooted and uninstalled battery tracer and bugs2go. Problem solved!

I did notice unlock lag once though. I can live with that until the official comes out though.
[Moto X Android Development] tw1tch175:
Odd I found the AT&T build far more laggy, lots of issues with active display. With the TMO one I just rooted and deleted the bloat and it is running really smooth

Anyone else feel like they are putting the wifi icon too close to the network indicator now? Maybe it's a Motorola screw you to use for complaining about the space before.
[Moto X Android Development] Steve-x:
I'm leaning towards the AT&T for sure but I'll give both a try for a few more days, I only have one cell account so I just swap the sim between phones.
[Moto X Android Development] beelzebu:
I have better and stable signal witch tmo loak than with AT&T leak + OTA. Also witch root freeze al the bloatware
[Moto X Android Development] phositadc:
I installed Cheerpipe's system ui mod and noticed that sometimes the Wi-Fi icon gets too close to the signal strength icon. Turn WiFi off and on fixes it.

I thought it was a bug with the mod, but maybe it's the leak lol.

Sent from my Nexus 5
[Moto X Android Development] jimmypop13:
Anyone have a working recovery? I tried like what one guy said about installing dhacker's TWRP for 4.4 but it just hangs at the splash logo and then reboots to system
[Moto X Android Development] jimmydafish:
There are no working recoveries right now.
[Moto X Android Development] jimmypop13:
Hmm well hopefully soon! I did just now get twrp to work and install superSU for me and I detailed how below but when I tried to wipe cache/dalvik it froze so I at least got root out of it

I FINALLY GOT ROOT!

I have a VZW dev edition. I flashed this in full as 3g and 4g still work with these radios, just make sure you switch in the phone info app to lte/cdma auto(prl).

Then I tweaked another user's guide to root since his method didn't work for me. I first tried just flashing dhacker's twrp for 4.4 and it would freeze at the splash screen. Once I did steps 1-3 first though, I was able to finally get past the splash screen and flash superSU and once I rebooted, superuser seems to work great. I was able to install busybox and titanium backup without issue.

1.- flash stock recovery ( fastboot flash recovery recovery.img)

2.- boot into recovery (stock)

3.- hold volume up for 5-10 seconds, then press power and immediately release both buttons. (you should get a menu)

3.- Now reboot from recovery back to the bootloader by highlighting reboot, then hold volume down and the reboot to system should still be highlighted. Press power to choose it and continue holding volume down and it will actually reboot to the bootloader.

4.- now fastboot flash recovery of dhacker's twrp for 4.4 http://rootzwiki.com/topic/103457-tw...ed-bootloader/

5.- go into recovery (twrp 4.4)

6.- flash root (i use chainfire's one) https://plus.google.com/113517319477...ts/Hd4MRq53V1x

7.- reboot! I tried to clear cache/dalvik at this point and it froze after "updating partition details" so I had to hold the home button to reboot.

So far I've been able to do everything I previously could with root. Hope this works for you guys too
[Moto X Android Development] jimmydafish:
I'm sure a functioning recovery will come along soon.
[Moto X Android Development] gcarterny:
Thanks For the post I just used the same method on the latest ATT and also got ROOT so Thanks!
[Moto X Android Development] fairct:
I successfully flashed the twrp263-ghost44 img file, and made a backup. I'm on the first OTA though. Is that why it works for me?

Well, NOW I see the issue. The recovery doesn't work after flashing this rom. Awesome!
[Moto X Android Development] xitake:
Thanks! I can confirm that this worked with ATT OTA.

You should create a thread with this information to help others
[Moto X Android Development] publicanimal:
Does anyone with a VZW Dev edition know what the trick is to getting CDMA calls/data to persist without needing to manually set the preferred network type after every reboot? I think that the above is part of the solution, but not the whole story. I was able to get this working on the previous T-Mobile 4.4 leak but I wasn't sure exactly what I did that solved it. I know that changing the telephony.cdmaonltedevice value wasn't enough to do the trick (because I still had to do some monkeying around to get it to work after changing that value in the build.prop).

I've been trying all day to fix this issue on the newer T-Mobile 4.4 leak and I've come up empty. It's not that big of a deal to manually set the preferred network type after a reboot, but knowing that there's a solution that I can't figure out is nagging the hell out of me.
[Moto X Android Development] arcanexvi:
Default network needs to be cdma/vzw.

Sent from my XT1080MDEV.
[Moto X Android Development] publicanimal:
Right... but how do I set it to that?

The build prop from the T-Mobile leak has:

ro.telephony.default_network=9

The value on the last official VZW build has:

ro.telephony.default_network=10

I thought that changing this value to 10 might have been the key to getting lte/cdma to be the default network type (it seemed to work on the previous 4.4 leak) but apparently that's not it because it's not working on the newest leak.
[Moto X Android Development] arcanexvi:
Check home operator and below.

Sent from my XT1080MDEV.
[Moto X Android Development] publicanimal:
No luck, thanks though. I had tried copying the ro.cdma values from the build.prop of the latest VZW build and the only ones that were missing from that one that yours had were the ro.cdma.home.operator.numeric & ro.cdma.home.operator.alpha values. I tried adding those in and it didn't work.

EDIT: I should add that none of the ro.cdma values were needed to get this to work on the previous leaked 4.4 build.
[Moto X Android Development] beelzebu:
Maybe you had luck, I never was able to do it
[Moto X Android Development] phositadc:
Here's my idle drain with this leak. On 4.2 I was closer to 1% per hour, but I have more stuff frozen on this than I did on 4.2.

So minor improvement perhaps, but still nowhere close to other flagships that get 0.1 - 0.3% per hour.

Sent from my XT1053
[Moto X Android Development] jimmypop13:
Mine is halfway persisting on my vzw dev edition and I only made two changes to the T-Mobile build prop. I'm running the full leak from 11-15, radios and all. In the build.prop towards the bottom i changed telephony.lteoncdmadevice to =1 and below that I changed ro.carrier=unknown to ro.carrier=Verizon Wireless.

So I don't know if its due to me using the radios in the package or changing those values but the phone ALWAYS reboots to CDMA auto(prl). Which is all I care about at home since I'm on WiFi. I still have to switch it to LTE/CDMA auto(prl) if I want 4g. Weird huh?
[Moto X Android Development] jimmypop13:
I'm running the 11-15 leak on my vzw dev edition. Is anyone else running this build occasionally getting a blank screen for a second when they unlock their phone from active notifications? I did a full wipe with the stock recovery after installing so I'm hoping it's not just me