yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] _litz:
Can we get a big honkin' huge flashing warning put up on the opening post that you cannot take the OTA if the OTA is 4.4.2?

This is going to trip up lots of people ...
[Moto X Original Android Development] boss.:
So will I need to unlock the bootloader first then use this? And I have the US Cellular version of the Moto X so do I use the Verizon or AT&T camera update?
[Moto X Original Android Development] mschumacher69:
The US Cellular Moto X has an unlockable bootloader, so you don't need this at all. Just unlock ur bootloader, flash twrp, flash supersu and u're done...
[Moto X Original Android Development] boss.:
Oh man... when I went and tried to unlock my bootloader, the Motorola site said that my phone wasn't eligible for bootloader unlocking. What do I do now? This kinda sucks.
[Moto X Original Android Development] grad061980:
Try again. Make sure you typed in the numbers correctly without spaces.
[Moto X Original Android Development] boss.:
Oh wow, I feel like an idiot. I was expecting a message to come up saying that I can request an unlock code. Didn't realize that the request button was at the very bottom of the page and not just under the code entry space. Thanks heaps.

Okay so I unlocked the bootloader. So do I just use this: http://xdaforums.com/showthread.php?t=2424110

It doesnt matter what Android version i'm on does it? BTW thanks heaps for the help.
[Moto X Original Android Development] mschumacher69:
Not sure if this one is up to date or not, but I know this one is:

http://xdaforums.com/showthread.php?t=2534850
[Moto X Original Android Development] boss.:
Thanks so much! Now i'm rooted :D
[Moto X Original Android Development] stillthisguy:
That is the Verizon 4.2.2 camera update.
[Moto X Original Android Development] _litz:
You sure?

the updater script contains this, indicating it's 4.2.2 -> 4.4 ...

file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/ghost_verizon/ghost:4.2.2/13.9.0Q2.X-116-MX-17-57-X-1/1:user/release-keys" ||

file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/ghost_verizon/ghost:4.4/13.11.1Q2.X-69-3/5:user/release-keys" ||

Remember, the verizon OTA zip files are named after the version they're updating FROM, not TO ...

e.g. 4.2.2->4.4 would be : Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip

and 4.4->4.4.2 would be : Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip
[Moto X Original Android Development] mschumacher69:
No I think he's right, usually OTA zips pulled from phones are named with the version of Android that's currently installed on the phone which would be the 4.2.2 camera update (139.15.1) at the time the 4.4 OTA was released, making this the 4.4 OTA zip...

I think u're right, see explanation above...
[Moto X Original Android Development] stillthisguy:
Never mind, I forgot Motorola names OTA's based off what version the phone is currently on. So that would be the 4.4
[Moto X Original Android Development] _litz:
The important thing is ...

the pieces are in place to preserve the SlapMyMoto process now, if the instructions are changed to indicate apply the 4.4 update from the ZIP FILE and not via OTA.

If you take the 4.4.2 OTA instead of 4.4, the process will no longer work.

At least as far as making it to 4.4 w/root. Beyond that still a crapshoot.

We need a way to apply the 4.4.2 update zip w/out updating the partition map or the bootloader.
[Moto X Original Android Development] tomh12player:
Is there a way to unlock the bootloader after I've rooted my Moto X using this method? Or do I have to revert back to stock and root my device again?
[Moto X Original Android Development] mschumacher69:
I would unlock my bootloader, flash back to stock, flash twrp and flash supersu...
[Moto X Original Android Development] AaronCompNetSys:
Its vaguely mentioned in post #2 now, I would hope that anyone following the instructions would read second post. I agree that it would be best to inject it into jcase's post.

Message a mod about it, but I'll go ahead and stick your quote in #2 post.
[Moto X Original Android Development] _litz:
Hah, I'd call that a "big honkin huge" warning ... :)
[Moto X Original Android Development] AaronCompNetSys:
I thought you might like my subtle edit ;)

---------- Post added at 03:16 AM ---------- Previous post was at 03:11 AM ----------

I think this should be the best option for most, wait until a manual partial update is available. Do you know who would be best for making that and can we get a thread started early, as a place holder? Maybe a title of "[4.4.2 ROOT]Upgrade Path". I think its better to have people subscribe to a thread just for the 4.4.2 WP issue, instead of hunting around and getting their phones to a point of no return.
[Moto X Original Android Development] cmonkEP:
Jcase already answered your question.

So you have three choices:

Stop worrying about it and just do it now before the VZW update is pushed to everyone

Keep worrying about it and learn how to side load (reboot your device to stock recovery and execute the 'adb sideload [OTA filename]' command.)

Live without root
[Moto X Original Android Development] AaronCompNetSys:
Dropped in #2 post, mirror needed. Magnet link recommended.
[Moto X Original Android Development] _litz:
Someone does indeed need to mirror that ... it took me quite some searching to find it.
[Moto X Original Android Development] lowvolt1:
Can't we just take the XML files we have already ie. The 4.4.2 XML files that have been released and modify the boot loader out of them and start a thread with each one posted for a quick download and instructions on how to fast boot side load them.
[Moto X Original Android Development] AaronCompNetSys:
That would be sweet, but I'm not experienced enough to feel comfortable doing that. Any volunteers?
[Moto X Original Android Development] lowvolt1:
I'm not sure I'm confident in my abilities either.

Another thought would be to also add the 4.4 XML and people could choose.
[Moto X Original Android Development] AaronCompNetSys:
Can you verify that this magnet matches up to the file you downloaded? Can anyone with a copy of the 4.4 update zip file verify this checks out?

magnet:?xt=urn:btih:CDARPSOTRY7CO4EY6K6SNWVASPBPX46S
[Moto X Original Android Development] _litz:
I'm not getting any connection to that, so can't download it and check.
[Moto X Original Android Development] AaronCompNetSys:
You may need to let it sit for a while.
[Moto X Original Android Development] _litz:
The issue here is, the XML files are the RSD-Lite firmware images.

If I'm understanding the way SlapMyMoto works, it takes the 4.2.2 system and modifies it, then you apply the OTA (or 4.4 upgrade zip) on top of that modified system. Then after it's updated, there's a second process required to finish the process.

If, instead, you use RSD-Lite to apply 4.4, you will overwrite the system partition and (as a consequence) the stuff SlapMyMoto has inserted into it.

If this is not the case, then the update process is dead simple : simply don't flash the bootloader in RSD-Lite.

But I doubt this is the case.

What we need is an update.zip modified to not update the bootloader ... and to do that you have to have a way to defeat the motorola signed file ...

Changing the updater script is easy enough, and changing the manifest file is easy enough.

The problem is the manifest itself is also checked by the bootloader when applying the update. So the only way to go seems to be resigning the update.zip ... and the bootloader will reject the file if it's not motorola signed.

---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------

I'm getting no connection at all, even after a while. I think it's dead.

Why do you need this link, when the other one works?

We just need someone to mirror it.

---------- Post added at 11:51 PM ---------- Previous post was at 11:36 PM ----------

I'd also add that there *IS* a possible update path that avoids the motorola signed file (I think) and that's SafeStrap.

Since this uses TWRP to execute the update file, the digital signature verification can be disabled.

That is, of course, presuming that it will work after the 4.2.2 to 4.4 update, and (ideally) would will still work in 4.4.2.
[Moto X Original Android Development] lowvolt1:
I really think your over thinking this. All the modifications are done before taking the 4.4 OTA. You should be able to do the same slap process then side load adb push the 4.4.2 XML file minus the boot loader.
[Moto X Original Android Development] _litz:
Really ... if that's the case, then in theory the process would be the following instead of taking the OTA :

SlapMyMoto as described, except use ADB sideload in place of the 4.4 OTA ... then

Use RSD-Lite to apply the 4.4.2 system, radios, etc (but no bootloader, partition map, or recovery)

Of course, we still need the 4.4.2 SBF file.

Anyone got any thoughts on this as a process, instead of applying the OTA zip file?

My problem with this is, will you end up with a 4.4.2 that has root?

You WILL lose supsersu, for sure, since that's installed into system, and RSD will over-write system. You would have to install from appstore.

Remember, an OTA patches an existing system. RSD-Lite erases, and replaces the entire system.
[Moto X Original Android Development] lowvolt1:
Yes, but instead of taking 4.4 OTA why couldn't you just side load adb 4.4.2 without the boot loader? Keeping instead the 4.2.2 boot loader?

Or sideload the 4.4 boot loader.

Note: I am not saying to use rsdlite at all.

Also you can take 4.4.2 OTA and retain root. You just lose write protection disable.

What is it that motowpnomo changes in the system?

It is feasible that we could adb sideload everything but boot loader and whatever motowpnomo changes and have root and write protection disabled on 4.4.2
[Moto X Original Android Development] _litz:
It all hinges on two things, I think ...

1) whether or not any changes have, at that point, been made to /system

2) if the answer to 1) is "none", whether or not the changes to gain root in 4.4 will work in 4.4.2

If /system has been changed when the 4.4 OTA is applied, it won't work, because the only way to side-load 4.4.2 is via RSD-lite which would overwrite /system. (and that's only after the SBF is released)

I can't think of any way to sideload the OTA zip and omit bootloader ... doing so requires editing the zip package, and the signing of the zip file will cause the install to fail if you do so. While it's possible to resign the update, it's no longer a motorola signed package at that point, and the bootloader should reject it, as a result.
[Moto X Original Android Development] lowvolt1:
Can you not use adb commands to push the files to the phone. And not use rsdlite at all. I think you can.

Or even yet, edit the XML to omit the boot loader and erase data lines and whatever else and then flash using rsd lite.
[Moto X Original Android Development] _litz:
It has to do with how the various update methods work ...

OTA uses an updater-script that the stock recovery utilizes to make changes to the system.

these changes can either be patches to files, or actual image flashes.

In the case of 4.4.2, it's patches for /system, and flashes for recovery/boot/radios.

RSD-Lite, by comparison, only flashes entire images, and it does so from the bootloader, not recovery.

It has no means to apply patches, only flash images.

When you say "edit the XML", in the case of the OTA zip, there is no xml ... and it can't be applied using RSD-lite.

---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------

The problem is, the 4.4.2 OTA (unlike the 4.4 OTA) rewrites the bootloader, and the partitionmap ... this removes the 'loophole' used to downgrade (which means you have NO ability to re-gain root if it's lost), and no way to ever regain moto-wp-nomo.

The sideload method of an update zip would be ideal. It would do exactly what you describe.

Except for that pesky problem with the motorola signed update file.
[Moto X Original Android Development] lowvolt1:
But they will release the XML soon
[Moto X Original Android Development] _litz:
Yes, but then we're back to the issue of how SlapMyMoto works ...

Two possibilities have to happen for RSD-Lite to work ...

1) the standard SlapMyMoto changes to 4.4 are not undone by flashing over it with 4.4.2 via a customized RSD-Lite XML.

or

2) RSD-Lite and a custom 4.4.2 XML can replace the "Take the OTA" step. The steps in the instructions taken after the OTA would have to work in 4.4.2, for this to work. A very, very big "if".
[Moto X Original Android Development] mercado79:
I'm excited to see how all this gets worked out. Honestly, it's all part of the fun here on XDA. Just be patient guys!

Also, for anyone that's using Safestrap, I'm sure there'll be a compatible stock 4.4.2 rooted ROM soon after the sbf is made available. That's how I originally ran 4.4 (using a Safestrap ROM posted on Rootzwiki). Just loaded it up on the stock slot.

Sent from my Nexus 7
[Moto X Original Android Development] _litz:
loading it up on the "stock" slot replaces the existing system, or is that in a "slot" utilized by safestrap, taking memory away from the sdcard storage? Also, this is on a locked bootloader?

(I'm presuming you start with 4.2.2, then install safestrap, then go directly to the 4.4 or 4.4.2 safestrap rom?)

any drawbacks to running a safestrap setup?
[Moto X Original Android Development] mercado79:
Exactly. Replacing System altogether. Safestrap can run on both 4.2.2 and 4.4, so long as you're rooted. If coming from 4.2.2, the dev on Rootzwiki suggested flashing some related files (maybe radio, can't recall). Otherwise, is very straight forward.

Here's the link:

http://rootzwiki.com/index.php?/top...rap][XT1060]-Stock-Rooted-Vzw-140.45.5-KitKat

Oh, and yes... Locked VZ Bootloader.

Sent from my Moto X
[Moto X Original Android Development] flacco40:
Is there an sbf xml file for the new 4.4.2? Can someone post it if so, thanks.
[Moto X Original Android Development] mercado79:
Nope. Nothing official yet (for VZ). See the link below for currently available sbf's.

Sent from my Moto X
[Moto X Original Android Development] stillthisguy:
RSD-Lite just preforms all the fastboot commands to flash what is listed in the XML. Technically you can remove any line from the xml and it will still flash, but it will overwrite anything that you flash. It is used so that you don't have to manually type 'fastboot flash recovery recovery.img' and so on.

So...

1) the standard SlapMyMoto changes to 4.4 are not undone by flashing over it with 4.4.2 via a customized RSD-Lite XML. - They would be overwritten when RSD-Lite flashes the full system file.

2) RSD-Lite and a custom 4.4.2 XML can replace the "Take the OTA" step. The steps in the instructions taken after the OTA would have to work in 4.4.2, for this to work. A very, very big "if". - Again, RSD-Lite will overwrite whatever you are using it to flash, boto.img, fsg.mbn, recovery.img, system.img, etc. etc.

I don't want to get anyone down, but I think the only options are safestrap on 4.2.2 or 4.4/someone releasing a 4.4.x root exploit. A youtube video comes to mind, but the exploit wasn't released, hence SlapMyMoto. Who knows if it would even work with 4.4.2, it was only shown working on 4.4.

---------- Post added at 08:36 PM ---------- Previous post was at 08:27 PM ----------

SBF files are located here. The site is updated as they become available and there are some 4.4.2 already uploaded to the site.
[Moto X Original Android Development] blackhand1001:
I am so happy to have my Verizon dev edition. Its great to not have to worry about root access in the future. I just got my Dad a regular motomaker one this week, but he could care less about root and this phone came with very little bloat and runs great out of the box.
[Moto X Original Android Development] elliot2112:
Is it true if I have a Verizon moto x and I took the 4.4 ota that all I have to do is follow the slap my moto steps to achieve a rooted phone?
[Moto X Original Android Development] mschumacher69:
Yes but you would have to downgrade back to 4.2.2 first. So it would be better if you start the process before taking the OTA to 4.4 so that you don't have to downgrade again...
[Moto X Original Android Development] _litz:
1) above is confusing ...

Are you saying that when using RSD-lite to flash a system.img to /system, it does not overwrite the changes applied by slapmymoto?

That doesn't make sense, because one of the things SlapMyMoto does is place supsersu inside the system partition.

I think you meant to say "the standard SlapMyMoto changes to 4.4 are not undone by flashing over it with 4.4.2 via a customized OTA updater script" ... which, of course, is not possible due to the zip file signing process.
[Moto X Original Android Development] stillthisguy:
I am saying RSD-lite or fastboot flashing the system.img to system partition will overwrite any changes applied by slapmymoto.

And yes, if you had a customized OTA updater script to run through recovery, that would make things easier, but only if we could flash it in recovery, which isn't possible like you said because of the zip file signing process.
[Moto X Original Android Development] AaronCompNetSys:
I apologize if I missed it, but does RSD-lite check signing before flashing? Would it be possible for someone to make a custom crafted system image and XML combo that is pre-rooted, pre-patched for 4.4.2, and contained 4.4 bootloader?
[Moto X Original Android Development] icase81:
Yeah, if you flash a system.img it overwrites the entire /system folder. If you install the OTA/flash a .zip, it only overwrites the updated files and thus doesn't overwrite your su binaries.
[Moto X Original Android Development] stillthisguy:
RSD-lite probably doesn't care, all rsd-lite does is flash the commands in the xml file. A custom system image wouldn't be signed by Motorola, so it will fail to flash. If you have seen the Xt1060 164.55.2 unofficial fxz thread in Android Dev section, you can see that you can use it to flash any part, except system or modem partition, as they aren't signed by Moto. You need an unlocked bootloader to flash images other than Moto signed.
[Moto X Original Android Development] lowvolt1:
All in all, we really need to work on a way to unlock bootloaders.
[Moto X Original Android Development] natezire71:
That would be ideal, lol. There is a hefty bounty for the guy who pulls that off.
[Moto X Original Android Development] KidJoe:
See this recent post -> http://xdaforums.com/moto-x/moto-x-qa/moto-x-vzw-bootloader-t2659234/post50641851#post50641851 does it help? I don't know how trust worthy they are. It converts to about $40. I have a Dev Edition, so I'm already unlocked.
[Moto X Original Android Development] lowvolt1:
I don't know, seems sketchy.
[Moto X Original Android Development] JarMagic:
WpNoMo Wont' Work

I keep getting a countdown "waiting for fastbook (3/120) in test 1

than waiting for ADB in test 2 (41/120)

The [TTTT**************************************************]

Press ENTER to exit

And no WP off.

Any ideas?

All anti-virus is off, and I've run this like 20 times

thanks in advance
[Moto X Original Android Development] grifforama:
Jcase. We need you. I would pay for 4.4.2 root method.
[Moto X Original Android Development] KidJoe:
You need Root *AND* Disable Write Protection unless you have an unlockable bootloader (like Dev edition, or T-Mobile, or Sprint, or ??)
[Moto X Original Android Development] _litz:
So Verizon has now officially approved the 4.4.2 update (this means all you people taking the OTA, it will be 4.4.2, and not 4.4, so you'll need to sideload for Slap! instead of taking the OTA) ...

Anyone know how long the process for the SBF to go online is?
[Moto X Original Android Development] MaddHatt3r:
I don't know much about Windows 8, but hopefully its like 7 as far as that goes. Try this: Go to Control Panel, Programs, Turn Windows Features On/Off, scroll down and check the box for Telnet Client.

If that doesn't work, just google enable telnet windows 8 or similar
[Moto X Original Android Development] eyc:
YES. YESSSSSS. It worked. Thank you.

---------- Post added at 11:42 PM ---------- Previous post was at 11:37 PM ----------

For f***'s sake. I ran telnet and entered the following line:

dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

It asked me to complete a simple math problem, which I did. The next step is to "use adb reboot," but when I type in adb reboot, I get "Permission denied."

Thoughts?

*** To be more specific, this is what I'm seeing:

Correct!...Rebooting now...

Please run: 'adb reboot', then re-run SlapMyMoto

~ $ adb reboot

sh: adb: Permission denied
[Moto X Original Android Development] MaddHatt3r:
did you run the adb reboot in a separate command prompt?
[Moto X Original Android Development] lowvolt1:
Still looking for possible cause for supersu not updating binaries.

When I did step 6 it says to toggle Bluetooth. I never had time as it rebooted too fast.

Thoughts?
[Moto X Original Android Development] MaddHatt3r:
I didn't need to toggle bluetooth either and by SuperSu updated just fine. Did you let it soak for a few min before you did anything? Can always go back and try Step 6 again incase something didn't write properly.
[Moto X Original Android Development] somerandomname1:
Quick question if you could maybe help? I did this whole process earlier, and everything seemed to work fine. No issues, installed SuperSU, ran a few apps that required root and had no problems. Apparently, after all my reading, I missed the most important part.

After the entire process, I just booted normally and installed SuperSU. I didn't go to bootloader and enter the "recovery." Still, root works, just temporarily it seems.

However, if I go to bootloader and enter the "recovery", it boots up, but at the unlock screen I get "com.process.systemui(or something similar) has crashed" over and over again. Luckily I can still enter the power menu and shutdown. I can even boot normally, but if I try to boot into the recovery, I get the constant crashes again. Any thoughts on how to fix this so I can have permanent root?
[Moto X Original Android Development] lowvolt1:
I tried step 6 again and consistently get permission failed. even after adb reboot which I can not do from adb shell.
[Moto X Original Android Development] mj0528:
Not sure bud, haven't had that issue yet.
[Moto X Original Android Development] somerandomname1:
Damn, I'm ****ed now. Now even if I try to reboot normally, I get the crash.
[Moto X Original Android Development] eyc:
I'm really sorry to clutter up this thread with my bullsh**. I am stuck and need more help.

I've completed all the Telnet steps, and am at Step 4. I typed "adb reboot bootloader" and my phone reset into the bootloader. The next step is to type the following:

fastboot flash recovery recovery.img
fastboot reboot

I typed the first line, and the message I keep getting is as follows:

(bootloader) Variable not supported!
error: cannot open 'recovery.img'

Anyone know how to get past this?

*** MaddHatt3r tells me to extract the VZW file and run the prompt from there. I'll try that.

*** Yup, that did it. Thank you MaddHatt3r.
[Moto X Original Android Development] devaughnaw:
I really want to try this but I'll probably screw something up.
[Moto X Original Android Development] lowvolt1:
No you wont. I am going on my fourth attempt. You can always revert back to 4.2.2
[Moto X Original Android Development] MaddHatt3r:
If you are patient, us early adopters will learn all the bugs the hard way, then when its at 1.0 release and no longer beta it should be more clear what needs to be done. It's a daunting task just looking at it if you have little to know experience, but it's really not that bad once you get into it.
[Moto X Original Android Development] somerandomname1:
I'm starting over and I'm hoping someone could clarify one thing that I think may have screwed up my last attempt:

"After it reboot's on it's own allow it to sit undisturbed for 1-2 minutes, then install SuperSU"

Do I install SuperSU in the regular boot? Or do I boot into the "recovery" with WP off and install SuperSU?