yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] MaddHatt3r:
I did it in normal boot because the directions didn't say otherwise. I don't seem to be having any issues.
[Moto X Original Android Development] somerandomname1:
And you can boot into WP off mode? That's where I started having issues...I don't want to go through all of this again just to get constant crashes when trying to access that mode. So you installed SuperSU in regular boot and then rebooted into WP off?
[Moto X Original Android Development] stillthisguy:
When it reboots on its own, it boots into WPO (recovery) mode, not normal.
[Moto X Original Android Development] lowvolt1:
I was starting over too. Know my adb says cant push read only
[Moto X Original Android Development] MaddHatt3r:
Yes, I have also booted into the WP off mode to edit my /system folder. I had no issues with that.
[Moto X Original Android Development] somerandomname1:
Oh! Still, I shouldn't have any issues booting into either mode later on, yes? I mean, should I always continue to boot into WPO mode?
[Moto X Original Android Development] KidJoe:
The OTA's are incremental upgrades. 4.2.2 -> 4.2.2 w/Camera, 4.2.2. w/camera -> 4.4, and 4.4 -> 4.4.2. There is no OTA to update ANY previous version to 4.4.2. So if anyone still on 4.4 downgrades to 4.2.2 w/camera to root they should be OK if they are CAREFUL and do not take the 4.4.2 if prompted.
[Moto X Original Android Development] KidJoe:
Right, there is a 4.4 -> 4.4.2 OTA.. Each OTA is looking for the phone to be on a specific previous version.

Maybe I should have worded it better... there is not a "one size fits all..." or "Any Version" -> 4.4.2 OTA update.
[Moto X Original Android Development] natezire71:
If anyone is interested, here is the official "4.4.2 Root Bounty Thread": http://xdaforums.com/moto-x/general/verizon-att-locked-bootloader-variants-t2664072/post50677890
[Moto X Original Android Development] mschumacher69:
What he means is that if u're on 4.2.2, u wouldn't get prompted to install the 4.4.2 OTA, u would be prompted to install the 4.4 OTA. U would only be prompted to install the 4.4.2 OTA if u're already on 4.4
[Moto X Original Android Development] _litz:
I've been looking at the 4.4 safestrap setup ...

It's very straightforward, and utilitizes an update.zip file, with an updater-script, to place all the 4.4 files into /system.

I see no reason the same process cannot be utilized to use an edited version of the 4.4.2 update, to update a safestrap 4.4 rom to 4.4.2.

The interesting thing is, safestrap's install process is (of course) no longer subject to the key restriction.

However, such an action would be dependent on also being able to flash the updated boot.img, modem and so forth.

Which means, waiting on the SBF before attempting to proceed ...
[Moto X Original Android Development] whatnow275:
I did the downgrade root/WP and then took the 4.4 ota and now i get the signature bugs unavailable error when I try to use Cydia Impactor...help??
[Moto X Original Android Development] whatnow275:
Yes I did all that and then it wouldn't let me connect on 4.4. I just SBF'd back to 4.2.2 and now trying to use rockmymoto skips to step 3 every time because I still have WP disabled. Flashed to 4.4 and going to flash back to 4.2.2 again to see if anything changes. How can I get root now??
[Moto X Original Android Development] whatnow275:
I mean the third time running the exploit...when it says stage three and that write protection is disabled. I have gone through that whole process (my second moto x, i did it on my first one without issue) and it won't connect once I update to 4.4
[Moto X Original Android Development] whatnow275:
Yeah puTTyTel worked just fine when I was on 4.2.2. Now on 4.4 i get two popups on my phone asking me to improve the install. I do but it fails. I looked up the error and apparently that is the same one you get if you try to skip the 4.2.2 steps. My write protection is disabled and I did all the steps the same way I did it on my first Moto X, so I don't know why it throws that error
[Moto X Original Android Development] mercado79:
This people! Chill out for a few days. A Safestrap version will be available soon after the official SBF becomes available. Kryptonite (the dev on Rootzwiki that created the flashable 4.4 stock ROM) plans to create a stock 4.4.2 ROM for us, but you lose that option (or Eclipse for that matter) by rushing to update knowing full well that there's no root available. Breathe. Really. It's not like the update is a huge one. It's still Kit Kat.

Sent from my Moto X
[Moto X Original Android Development] Toys Samurai:
Sound fishy, but we only need 40 people, each contribute 1 dollar, and 1 person who has a TaoBao account to give it a try. If it works, that guys will surely get a lot of business from folks here. If not ... well, each of those 40 people lose 1 buck.

I am willing to contribute $1, fyi :)
[Moto X Original Android Development] sorullo_xgrx:
Once goes to that step look at your phone, make sure is unlock and a prompt will pop up asking you for root right make sure you grant them. It will work then
[Moto X Original Android Development] flacco40:
I don't understand why people can't just help each other out here, that would be one way to stop clutter on threads instead of telling someone to go somewhere else...

I believe what you're doing wrong is your not using both guides, you must use the putyytel guide, and on a separate tab open the Slapmymoto 1.0 guide...after second time of running exploit phone reboots itself, then u accept ota 4.4 then you follow step three on the SlapMoto page, hope I helped you unlike previous people that commented to you.

---------- Post added at 11:16 AM ---------- Previous post was at 10:57 AM ----------

I went there and you must register but I can't even register because it says phone number not valid probably because it's us, and the terms say that it will link to your PayPal account, hell no, my Pay Pal is linked to my bank I'm not about to give him access to my bank account are you crazy you can create the account and I'll donate money but I'm not going to register my paypal ..lost your mind Son!!
[Moto X Original Android Development] natezire71:
Do you recommend SafeStrap?
[Moto X Original Android Development] mercado79:
Yes. It works perfectly. I don't use the ROM slots cause I value the storage space on my phone. Instead, I create a Nandroid backup of the stock ROM and then wipe and install Eclipse or Kryptonite's Stock ROM. Easy as pie.

Sent from my Moto X
[Moto X Original Android Development] lowvolt1:
Kryptonite stock ROM???
[Moto X Original Android Development] natezire71:
Thats ballsy.
[Moto X Original Android Development] lowvolt1:
I do the same. Back up stock and flash ROM to stock slot.
[Moto X Original Android Development] natezire71:
So, from my understanding--once I have Safestrap--I can use the stock ROM and root it with ease?

Well hot damn. You're able to install Safestrap once you're on v4.4, right?
[Moto X Original Android Development] lowvolt1:
Well you have to be rooted to use safe strap. Safe strap is not an easy means of rooting. It is like a custom recovery with out really being recovery.
[Moto X Original Android Development] natezire71:
I know what Safestrap used to be. Again, I had it on a Bionic. It seems stuff has changed now--especially considering the majority of my issues arose from radio issues; I was trying to use CM on a Bionic--not a pretty sight. This time it's different, as I wish to keep the stock ROM.

I'm already rooted and on 4.4; but you're saying you still can't root v4.4.2 even after being on Safestrap? I thought that was the point of being on Safestrap.
[Moto X Original Android Development] lowvolt1:
So if your already rooted on 4.4 you can install safe strap.

You will be able to flash a 4.4.2 ROM using safe strap but it will be a custom ROM not the official release.
[Moto X Original Android Development] natezire71:
Will there be a way to get the stock 4.4.2 software on my phone using Safestrap? I'm not ever going to use custom ROMs--I just want to easily root future releases.
[Moto X Original Android Development] lowvolt1:
I don't believe so.

You can take the 4.4.2 OTA and keep root.

You will however lose the write protection disabled feature.
[Moto X Original Android Development] natezire71:
Well yeah, but that kinda makes root useless.

So, what the heck is the point of Safestrap if you don't want to use custom ROMs? I thought that was what the purpose of that other guy telling me I should give it a go.
[Moto X Original Android Development] mercado79:
Yes. It was released / designed for the original 4.2.2 ROM, but works just fine on 4.4. You have to be rooted, of course.

Here's the fully stock 4.4 ROM on Rootzwiki (the dev asked we not repost it here, but rather link to that thread):

http://rootzwiki.com/topic/108826-romsafestrapxt1060-stock-rooted-vzw-140455-kitkat/

He plans to release a 4.4.2 ROM once the sbf file is available. Again, it's not custom. It is stock.

The "custom" ROM here is from Eclipse. It's a heavily modified stock-based ROM. Still on 4.4 for now, but will be updated to 4.4.2 soon, I'm sure.
[Moto X Original Android Development] natezire71:
Okay--that's what I thought. I'm only interested in stock MotoX ROM. I need Active Display. Eclipse doesn't do that.

So, there will be a Safestrap version of 4.4.2, rooted--for the MotoX on Verizon at some point. Gotcha. In that case, I'm gonna see about Safestrap getting installed.

Is the thread on Rootzwiki up to date? I was reading through it a day or two ago and there didn't seem to be a concrete write-up on how to install Safestrap on 4.4.
[Moto X Original Android Development] mercado79:
Eclipse DOES support all native Moto X features and more. Or it did as of version 2.2. Version 3.0 broke compatibility with GravityBox quick settings tiles and possibly other Xposed modules. I think Active Display was temporarily affected too. May have been fixed in 3.x. Not sure. That'd be an issue for me. I haven't checked lately as I was turned off by the drama (on all sides) that ensued when that happened.

Yeah. It's not exactly clear, but Safestrap 3.65 works just fine. I installed it while on 4.2.2 so I'm guessing, but I think you can just I install the apk once rooted.

Sent from my Moto X
[Moto X Original Android Development] natezire71:
It does!? That's weird. I always thought it was like EclipseROM, which to my knowledge, was just a CM copy-cat. I'd still prefer stock though.
[Moto X Original Android Development] j2cool2012:
Just because you can flash it doesn't mean it's a custom ROM. There are many reason why the Stock ROM could be ported to Safestrap for flashing.

1. Easy return to stock without having to use RSD.

2. Getting OTA updates without having to take the OTA or unroot

3. Because you feel like having a backup stable stock ROM on a separate slot.

A custom ROM is just that; customized. If all someone has done is make a safestrap-flashable stock ROM. it is still a stock ROM.

Being unnecessarily condescending and rude weakens your argument really quickly.
[Moto X Original Android Development] lowvolt1:
I stand corrected.

My apologies.

Thanks for explaining it. And not just being jerky.
[Moto X Original Android Development] KidJoe:
And now back the the [4.4 ROOT] SlapMyMoto 1.0 (Works with MotoWPNoMo) discussion already in progress ????

There is still no change in the status of SlapMyMoto/MotoWPNoMo and 4.4.2. It doesn't work.

Will it ever work for 4.4.2? Probably not.

Will a new process to replace it ever come out? That is unknown. But if a NEW/DIFFERENT process is developed and released, I think it would get its own thread.
[Moto X Original Android Development] Toledo_JAB:
I just wanted to say thanks for not letting that get out of hand.

I think every one had their say

I have deleted the OT discussion from the thread.

Thread cleaned
[Moto X Original Android Development] hecantbreathe:
Verizon locked bootloader

Can we not RSD Lite back to 4.2.2 if the OTA of 4.4.2 on the phone?
[Moto X Original Android Development] mercado79:
Apparently 4.4.2 blocks any downgrading (unlike 4.4 which did allow it).

Sent from my Moto X
[Moto X Original Android Development] KidJoe:
Once you install the 4.4.2 ota on your phone, you can not downgrade. You will brick your phone. There is a long thread on the uploaded boot loader included in 4.4.2, and the inability to downgrade
[Moto X Original Android Development] hecantbreathe:
Crap, okay thanks. I tried to downgrade and it just failed. Now I know why.
[Moto X Original Android Development] southern87:
This was an adventure for me. I had a HTC One till it decided to not work not more(user abuse per say). So I got a Moto X because I really didn't like the bulkness of the One. Anyways.

I had updated to 4.4 straight from stock. I decided I wanted to root this phone, mainly to remove the stupid apps.

Heads up if anyone is coming from unrooted/stock 4.4. I had to use RSD Lite to flash the 4.2.2 then use MoToWPnomo. Then use Slapmymoto. Accept the OTA. That is where the fun started. My phone would start up, but within 5 seconds it would reboot and repeat. I had to redo the entire thing over because the OTA didn't download fully lol.
[Moto X Original Android Development] JarMagic:
adb Push problems

I keep getting the message that SlapMyMoto cannot be found. I've included a screenshot. Any thoughs as to what I'm doing wrong?

Thanks
[Moto X Original Android Development] thesomnambulist:
Check your spelling... it looks like you added an "m" where it shouldn't be.
[Moto X Original Android Development] JarMagic:
ADB Push Issues

Sorry for the mispelling, it is the same issue I have when I do spell correctly. I've attached another screenshot. Thank you any hints, or advice I would sincerely appreciate.
[Moto X Original Android Development] jimbo0914:
Is SlapMyMoto.jar on your desktop? That screen grab indicates adb is looking for that file on your desktop.
[Moto X Original Android Development] mschumacher69:
U have to navigate to wherever slapmymoto.jar is, using the cd command. Use cd .. to navigate up one folder and cd <foldername> to navigate into a folder.
[Moto X Original Android Development] hovax615@hotmail.com:
No need to navigate. Put the file into where you have the adb folder at then you won't have to CD to the folder. Easier if you don't know how to use those commands.

MOTO X SLAPPED
[Moto X Original Android Development] JarMagic:
On Desktop

Yes, slap is on my desktop.
[Moto X Original Android Development] Toys Samurai:
I've never use SafeStrap before, so excuse me if this question is too "beginner" like. If I install Safestrap (assuming I am on rooted 4.4 Verizon Locked Bootloader), and someone releases a rooted 4.4.2 ROM. Does it mean I can flash that ROM even though my bootloader is locked, but rooted, even though my underlying system is 4.4?
[Moto X Original Android Development] mercado79:
Exactly. And just your luck, KrYpToNiTe just posted a stock Safestrap-flashable 4.4.2 ROM over on Rootzwiki.

http://rootzwiki.com/topic/116025-romsafestrapxt1060-stock-rooted-vzw-164552-kitkat-442/

Sent from my Moto X
[Moto X Original Android Development] Wingdom:
I seem to have found myself in a bind with SlapMyMoto. I am on a Verizon Moto X, I have downgraded from 4.4 from 4.2.2, rooted it, with RockMyMoto, and run MotoWPNoMo, all with no problem. Write protection is off, adb shell getprop ro.boot.write_protect returns 0. I get to step 3 in SlapMyMoto, it tells me to accept the 4.4 OTA. I go into settings, and tell it to accept the update, the phone reboots, straight back into 4.2.2, stays on for a second or two, and reboots again, and over and over. Has anyone else run into this? I have gone through this cycle twice now.
[Moto X Original Android Development] NightThyme:
When I did it, I didn't have to do that. All that had to happen was for me to turn WiFi on and the 4.4 OTA almost immediately started to download.
[Moto X Original Android Development] Wingdom:
Im giving it one more shot before I give up for now. I had hit "install later" on the popup that comes up when the download finished, because the download finished before I was ready for it. Thus the need to go into settings and start the update manually.

Edit: Somehow magically the combination of 3am and too many tries, it work. Not sure what happened different...
[Moto X Original Android Development] thesomnambulist:
Try either moving the SlapMyMoto.jar file into your platform-tools folder, and running it from there, or else specifying the path where it is located(e.g. C:\Users\jfulton1\Desktop>adb push C:\Users\jfulton1\Desktop\SlapMyMoto.jar /sdcard/SlapMyMoto.jar)
[Moto X Original Android Development] AaronCompNetSys:
Can anyone verify this is correct before I update second post?
[Moto X Original Android Development] _litz:
Judging by the one OTA zip file that has been found, might well be the case ... do we want to take the chance?

that's a big question ...

if VZW (or any other carrier) decides to do a cumulative update to 4.4.2 at some point, then it'll screw the process.

It is much, much safer (e.g. foolproof) to apply a known 4.4 OTA zip file via sideload.
[Moto X Original Android Development] AaronCompNetSys:
Yeah, but for now at least I can put a date stamp on it if we know it works. I don't think its risky as long as someone can verify the 4.4.2 update is indeed always like 100MB or so. The only chance I know that my post could be wrong is if there actually is a 400MB+ full flash 4.4.2 OTA that exists. I have not seen anyone post about it though.

I guess its remotely possible that updates queue and install without prompt, but I highly doubt that.
[Moto X Original Android Development] sorullo_xgrx:
I have found and downloaded a 692mb zip Verizon 4.4.2 OTA

---------- Post added at 07:18 AM ---------- Previous post was at 07:18 AM ----------
[Moto X Original Android Development] AaronCompNetSys:
Just the confirmation I was looking for, thank you.
[Moto X Original Android Development] KidJoe:
can you share the link? Are you sure its the OTA and not the full SBF?

The full 4.4.2 SBF for Verizon posted here -> http://sbf.droid-developers.org/phone.php?device=0 is 692.7 MiB

The SBF is a full rom, is "cumulative" or all inclusive, and can be flashed no matter what ROM is on your phone (depend on bootloader versions), where as the OTA updates only patch certain existing files/partitions, is not complete, are smaller than full SBF, and so far have all been incremental, not cumulative.
[Moto X Original Android Development] sorullo_xgrx:
Yeah I was referring to that one
[Moto X Original Android Development] mschumacher69:
That's not an OTA, that's a full SBF...
[Moto X Original Android Development] KidJoe:
Ok, that is NOT an OTA update. That is a full SBF which must be installed via RSDLite or mFastboot on the PC.

The OTA's are smaller, update only the files that have changed, and get installed via the phone's stock recovery, and can't be installed via RSDLite or mFastboot.
[Moto X Original Android Development] AaronCompNetSys:
:eek: So now we've come full circle, is it confirmed that there is no full OTA for 4.4.2 or is it still up in the air?
[Moto X Original Android Development] KidJoe:
Not sure what you are asking.

The OTA's are incremental. For Verizon, there have been 3 of them.

4.2.2 to 4.2.2 w/camera fix

4.2.2 w/camera fix to 4.4

4.4 to 4.4.2

There is no single OTA update that is cumulative and will flash a 4.2.2 directly to 4.4.2. or a single update that will flash "any/all prior versions" directly to 4.4.2.
[Moto X Original Android Development] AaronCompNetSys:
Sounds good to me. 4.2 and 4.4 users should have no fear following jcase's guide in #1 post.

---------- Post added at 05:22 PM ---------- Previous post was at 05:10 PM ----------

I reworded it all to try to include everything without editorializing.
[Moto X Original Android Development] Wingdom:
I just re-rooted my phone the day before yesterday, and can confirm that as of now, the upgrade path is 4.2.2->4.4->4.4.2. Verizon is NOT pushing a combo update 4.2.2->4.4.2, so the original instructions still work. :good:
[Moto X Original Android Development] lowvolt1:
+1 on this. Updates come in stages.
[Moto X Original Android Development] JGoldz75:
So I was stupid enough to take the 4.4.2 OTA update when it came. I'm Verizon Locked Bootloader. I have lost my write permissions... but still have root to some extent (xposed still works and some other certain apps). Am I royally screwed until a new root method comes out? I heard that you will brick your device if you try to use any method to get back to 4.4.2. If I'm wrong, please tell me! I need write permissions!

Not related... anyone getting horrific battery life? 5.5 hours and 100%-0%.
[Moto X Original Android Development] Toys Samurai:
That is awesome! Now, excuse me again for being uninformed ... There must be some shortcomings running a setup like this (I mean, running a 4.4.2 Safestrap ROM on top of a rooted stock 4.2.2 ROM), aren't there? It just sounds too good to be true, and it reminds me of the duck test: If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
[Moto X Original Android Development] KidJoe:
In short, 4.4.2 upgrades the bootloader and patches the exploit used by MotoWpNoMo and re-enables Write Protection. To disable Write Protection, a new exploit and process will be needed. It is not likely that will happen. And if it does, it probably wont be any time soon.

The long version...

When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you take the 4.4.2 OTA), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.

Even if you have root, but lost Write Protection, any apps you've installed that need to write to system can't permanently save their changes (you have to re-do every time your phone powers off/on), and any Root type app, or app that gets installed to /system after WP is enabled will be lost at power off/on.

As you can see, Root is only half of the equation. For root to be useful, you need to be able to write to /system, in the X's case, this means you also need write protection disabled.

The updated bootloader in 4.4.2 prevents properly downgrading roms. There are reports of errors while trying to downgrade, and bricking if you manage to downgrade and then take an OTA update because of it. This impacts trying to use the "current" root/WPDisable methods as they require you to downgrade your ROM and perform steps that involve taking OTA updates for the process to work.

So if you had previously been rooted, took the 4.4.2 update and have a locked bootloader, yes you are stuck with Root that is mostly useless without Write Protection being disabled, and no way to disable write protection. If you never rooted, and upgraded to 4.4.2, then your stuck without even a way to just gain root.

If you have a developer edition, or other version X where the bootloader can be unlocked by visiting Moto's web page to get the code (like Sprint, T-Mobile, and a few others), no matter which rom or bootloader version you are on, once you unlock the bootloader, Write Protection is disabled and root is easy to achieve by flashing a custom recovery and installing SuperSU from the custom recovery.
[Moto X Original Android Development] 640k:
These posts were getting buried and I didn't see a thread started for the SBFs so I created one here:

http://xdaforums.com/moto-x/general/verizon-sbf-blurversion-164-55-2-t2673795

There are several carrier SBFs on that site already.
[Moto X Original Android Development] mercado79:
I imagine that at some point, not updating certain files will cause problems, but for now, all seems well. Plus, you have nothing to lose. Taking the 4.4.2 update on the other hand is currently irreversible.

Sent from my Moto X
[Moto X Original Android Development] KidJoe:
One thing to keep in mind, safestrap will use of space on your internal storage, or the phone's "emulated SD card" so you'd also need to consider how much space would be available after safestrap and its roms are all setup.