yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] dtrud0h:
Exactly, what I just said was that if for whatever reason someone needed an actual recovery from here, that to use an actual recovery it should be from 4.2. But I don't know how to get "Our "Custom-Slapped(RW to System)-Recovery"" Back. If we needed an actual recovery, and should flash a 4.4 recovery, would it screw up the system, and how do we get back to "Normal(Slapped)?"

Get my meaning here?

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] lowvolt1:
I am fairly confused by what you are saying.

We don't really have recovery in a "recovery" sense. We have write protection disabled. I only know of one user that flashed 4.4 recovery after rooting and that user had also done the motowpnomo. Flashing 4.4 recovery and boot IMG. Reversed motowpnomo for him. From what I understand. But he hasn't been able to duplicate it. By no means do I support do it.

Even if you could flash 4.4 recovery, we still would not have recovery in the "recovery" sense. Since we have locked boot loaders.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] dtrud0h:
From what I've gathered from the topic is that the 4.2 recovery simply allows the loophole to accomplish the exploit. If someone should meed an actual recovery, and flashed a 4.4 recovery, would the whole thing go to shixxle?

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] lowvolt1:
Try it and let us know. :D

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] dtrud0h:
Recovery is still there, it would allow you to flash a signed update.zip, clear the cache, or other recovery things that you can do on a stock recovery. But whereas we are technically using a 4.2 recovery for our Slapping purposes, if someone flashed a 4.4 recovery, will it screw the whole thing up? How did. "Said User" make out? Was he borked? Did he end up back "Slapped"? Or stuck with root and no rw access? That's what I'm trying to say.4.2 allows the loophole we need. What happens elseways.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] lowvolt1:
As far as I know "said user" is solid.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] nhizzat:
How would manually flashing the 4.4 recovery be any different from those who took the 4.4 OTA before rooting their phone?

And PLEASE stop using the term custom recovery because there is nothing custom about what we have on the non-DE versions on VZW and ATT. Normal boot ups have write protection on while booting up through recovery has write protection off. A custom recovery has always referred to CWMR or TWRP and the like.
[Moto X Original Android Development] shane1:
After your rooted and can flash the kk boot loader and recovery. Just don't rsd you might be able to restore root once but probably not a second time yet...... If you run motowpnomo you can flash recovery.
[Moto X Original Android Development] dtrud0h:
Has there been any reports of this method working after taking the 4.4 OTA? I honestly don't know the answer to that. I've pointed a few individuals to this via TEAMUSCC forum, but no confirmed successes as yet.

I guess it boils down to this: can we restore the Slapped recovery(System R/W) without the whole process if we should for whatever reason need to flash an actual, working, recovery. Be it stock, or some other iteration of a recovery? If we could narrow down what we actually need to keep our Slapped status, would the next OTA be a breeze? I'm not trying to be difficult here, just trying to think ahead, all cases considered.

Just trying to get people thinking ahead instead of trying to catch up after its too late.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] shane1:
As long as you don't run motowpnomo this method will continue to work. As for future updates its highly doubtful this will work. Moto patches bugs.
[Moto X Original Android Development] dtrud0h:
No. I will not stop. If a slapped user boots into "Recovery" he is not in any kind of recovery that any android user has ever experienced. Hence the term"Custom". Read back six or seven (or thirteen) posts to find out what makes this recovery custom.

And I retract a statement earlier that there are no "confirmed" reports of successful install of "Slapped" after taking the OTA. A USCC user has been successful.

Now the question only lies to what we need to do to revert to being slapped if we should need a real recovery( and which it should be) and then want to become re-Slapped.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] shane1:
There is NO recovery. It just boots to write protection off. It overwrites recovery a "custom" recovery means there is a recovery to boot into.
[Moto X Original Android Development] nhizzat:
Wat? :confused: Seriously, wat? :confused:

Exactly. What we have is only a recovery by name.
[Moto X Original Android Development] dtrud0h:
On my Xoom, I boot recovery, I get TWRP, on my OG electrify I boot recovery, I get CWRM, on my MotoX I boot recovery, I get Slapped, /System =R/W access, on a stock unit I boot recovery, I get recovery.

Tell me once more cause I forget quickly, why is this not a custom recovery?

I Don't give a flying frank about what people are accustomed to. If the damned thing boots something besides a recovery its a custom recovery. The more you try to change the terminology, disguise what in fact we have here, or completely mess with the basic minds that have to try to wrap their heads around this, the fact is that this is not "Recovery" as you know it, its "Custom", this friggin' recovery doesn't do anything but boot a normal system that allows a read/write access to /System. What Stock recovery does that? ... waiting......, none. This is a custom recovery, you can't flash ship, you can't do nuthin' but have rw access to /system. Want something more? Unlock your bootloader, flash something else.

I'm done arguing about how I refer to what this is. Glad you think something else of a "Custom" recovery, there are people besides you who need to know what the ffff they have in front of them and have to deal with.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] Toys Samurai:
Now that I re-read the instruction, the only place I see that "custom recovery" being mentioned is this line:

I am sure that many people would understand it immediately, but I am also very sure that a lot of people wouldn't. Frankly, if your post appears in any page before 15 or 20, I think 1/3 less people would be asking this question. Unfortunately, your post appears in page 79.
[Moto X Original Android Development] dtrud0h:
Well, when you find something you want that says " Flash in recovery" , and your MotoX only starts normally ( with read -write access to /system, which you don't even realize, because "recovery doesn't work") come on back and ask about it.

Jcase method works to get the job done as far as rooting goes, but the backlash as far as. "Recovery " mode, I have my reservations. Especially towards those who have no idea what they have just done, or why.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] lowvolt1:
You should start your own thread about recovery and the ignorance of others.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] dtrud0h:
Maybe I will. Prolly top the polls for number of hits.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] tallgrasshawk:
Took some tinkering, but I was finally able to gain root access. Think I could run through this pretty fast now that I know what I'm doing.

Did run into permission denied in step 7 running those final two shell commands (couldn't toggle BT quick enough). Forced reboots through ADB. Was still able to install and use supersu. So far everything is working swell.

Thanks for all the help.
[Moto X Original Android Development] dtrud0h:
[MENTION=4520932]lowvolt1[/MENTION]

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

Sent from my XT1055 using Xparent Cyan Tapatalk 2

Here ya go.
[Moto X Original Android Development] Rebel908:
Hey, do you think we could chat about this? I would love to help out of I can.
[Moto X Original Android Development] Ryphez:
RSD Lite doesn't want to detect my Moto X. I'm running Windows 8 and I'm trying to get this device rooted but I can't get RSD to detect it in bootloader mode. I have installed Motorola's drivers and tried multiple USB ports. Any suggestions would be great!

I have a Verizon non-developer Moto X. Fastboot devices detects the phone in bootloader mode
[Moto X Original Android Development] bd1212:
Yep, the factory reset seems to have done the trick.
[Moto X Original Android Development] GandalfTehGray:
Are you on Kitkat or still Jellybean?
[Moto X Original Android Development] Savassi12:
soo i was trying to root my brazilian version of moto x, already updated to 4.4 thanks to some tutorials out there, and when i was trying to star a telnet session with cydia impactator and it just said that there that there was no signature bugs available any help?
[Moto X Original Android Development] tjohnstone3:
I have experience w/ Java so I could potentially help out (currently stuck w/out root so interested in trying this out). I was able to decompile the smali files but smali is pretty greek to me and I'm not sure how (or if there is a way) to get the Java source back that generated the smali files.
[Moto X Original Android Development] 1ManWolfePack:
Accidental thanks. Why is it not custom?

Because it's not TWRP, CWM, or day I say Voodoo. Lol.
[Moto X Original Android Development] h1ghland3r:
You need to downgrade to 4.2.2 to start this process.
[Moto X Original Android Development] Ryphez:
I'm on KitKat, trying to go back to Jelly Bean for this root process
[Moto X Original Android Development] Rebel908:
I don't have much experience in this, just really wanting to get root back, so I'd like to help where i can.
[Moto X Original Android Development] Toxicoblivion:
Getting root on a nondev version looks like a nightmare. Kind of warding me off from the phone :/ i hardbricked the last moto i had trying to root it. Afraid ill do it with this one too if i get it :/ One's root was so simple, this is not :/
[Moto X Original Android Development] raddacle:
Followed all the steps and everything seemed to complete flawlessly, however SuperSu still isnt able to operate. HELPPPPP
[Moto X Original Android Development] lowvolt1:
Explain operate.

Do you mean update binaries?

" reboot recovery" that will disable your write protection for that boot and then update the binaries.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] raddacle:
It was missing SU binaries, but I figured out that I messed on the last adb shell step. I mistook TOGGLE Bluetooth with turn it on. Rooted now!
[Moto X Original Android Development] rockingondrums:
For anyone who comes after you, within the last couple of pages before you posted, I put up a screenshot of all US carriers shipping firmwares and their version numbers. The screenshot is directly from the moto webpage.
[Moto X Original Android Development] Rebel908:
For those who are having trouble downgrading: YOU NEED TO USE RSD LITE TO DOWNGRADE FROM 4.4 IF YOU ARE ALREADY ON 4.4.

This link will show you how to use RSD Lite - http://xdaforums.com/showthread.php?t=2446515

It also has relevant information for flashing the SBF, namely that you need to edit the XML file before you can flash. READ THE INSTRUCTIONS CAREFULLY.

Also know that using Beaups MotoWPNoMo will prevent you from obtaining root again if you flash back to 4.2.2 to recover from a catastrophic issue. at least with SlapMyMoto in its current state.

Other than that, be careful when modifying your device like this. If you are not comfortable knowing your device may end up in an irreparable state, then do not mess around with the device.
[Moto X Original Android Development] Ryphez:
I made a clearer guide to this process that outlines the steps clearer. http://www.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/

Please let me know if I'm missing anything
[Moto X Original Android Development] erikcave:
I have looked through most of this forum and have not found my answer, so I hope someone can help me out. I just got a new Moto X for Verizon straight from Motorola. It is on 4.2.2, build number 13.9.0Q2.X-116-MX-17-57-X-1. I have not applied the OTA update to 4.4 even though it asks me to every ten minutes.

I want to end up with a stock rooted 4.4 device. What is the best route there? Should I use Rock my Moto to root? I can't find on that thread how to safely go to 4.4 from there. This method seems to indicate that I can get back to 4.4, but since I would downgrade to 4.2 during the process anyway, should I just skip to after the downgrade steps here? I am really confused and would love some advice. Thanks.
[Moto X Original Android Development] sorullo_xgrx:
If you are on 4.2.2 you are good to go. Jump to Step 2 where you push the files to sdcard and continue to step 3. He mentions rock my moto because on that thread he explains how to use impactor and telnet.
[Moto X Original Android Development] erikcave:
I think you just answered my question above. I apparently can use the SlapMyMoto files to root and the upgrade to OTA 4.4 and the regain root. Thanks.

One question you might be able to clairify. When I go to the stock Motorola Firmware page there are two 4.2 versions listed for Verizon:

Android 4.2.2 Blur_Version.139.10.53.ghost_verizon.Verizon.en.US

Android 4.2.2 Blur_Version.139.15.1.ghost_verizon.Verizon.en.US

(from http://sbf.droid-developers.org/phone.php?device=0)

Which should I download and use?

Edit:

Never mind, I see you link to the correct one on your redit page. Thanks!
[Moto X Original Android Development] Ryphez:
The more recent one, 15.1
[Moto X Original Android Development] erikcave:
Thanks a ton!
[Moto X Original Android Development] erikiksaz:
A couple of notes for super newbs like me:

1) Get the newer of the 2 4.2.2 updates on the sbf.droid-developers website.

3) The impactor hung for me unless I had it run telnet on port 22 first. It ran fine on port 2222 after.

4) Find the recovery.img for this step in the original zip from Step 1

5) Same as step 4

6) All the files that you need to push are in the SlapMyMoto zip file at the bottom of the OPs post

7) Load up into the bluetooth tab so you can toggle it on immediately. I entered the command in cmd by hitting enter then immediately toggling the BT on the phone.

--

Otherwise, worked perfectly, thanks OP!
[Moto X Original Android Development] Ryphez:
I'm gonna add these to my reddit post too. Thanks!
[Moto X Original Android Development] tluley51:
After getting through every step no problem, I got to the very last command and it did not reboot on its own...So I went ahead and rebooted it myself, let it sit for 5 minutes then installed SuperSu...

Unable to install binaries and my apps are saying I do not have root. Any help would be great.

EDIT: Went back to step 6 and did it again and it worked!
[Moto X Original Android Development] h1ghland3r:
Hey guys,

Is there a problem always rebooting in recovery mode (to get WP off) ?
[Moto X Original Android Development] lowvolt1:
Please elaborate.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] erikcave:
When I run Cydia Impactor it just sits there forever saying "testing #9950697."

If I issue an ADB command like "adb devices" Cydia then crashes with this error:

Runtime Error!

Program: C:\users\Erik\Desktop\Impactor_0.9.14\Impactor.exe

This application has requested the Runteim to terminate in an unusual way.

Please contact this applications support team for more information.

This is true whether I do it on port 22 or 2222.

Any tips on what I am doing wrong would be helpful.

My PC has Windows 8.1

I can see my device in ADB and get it's IP address. I was able to push the slapmymoto.jar file no problem. I just got stuck on this step.

Thanks
[Moto X Original Android Development] tallgrasshawk:
Had that happen to me. I had to move all the cydia files to my desktop and run them from there.
[Moto X Original Android Development] erikcave:
Thanks for the suggestion. I will try that when I get home.
[Moto X Original Android Development] h1ghland3r:
I remembered you recommend me a tutorial to set WP off, but I didn't do. So, I'd like to know if it's prejudicial to phone always turn on/reboot choosing recovery mode in fastboot.

Sorry for my English =(
[Moto X Original Android Development] lowvolt1:
In order to write to system you must turn write protect off.

To do so.

Power off phone.

Hold power and volume- down for a few seconds

Let go

Phone will boot into fastboot

Volume- to recovery

Volume+ to select

Phone will boot in what appears to be normal mode but write protect will be disabled for that boot.

To turn write protect on just simply reboot.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] _litz:
Okay, here's a question for y'all on the update package xml files ...

It's been stated that this :

<step operation="getvar" var="max-download-size" />

has to be removed ...

For people who have MotoMaker customized devices ... would removing :

<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />

prevent the erasure and destruction of their MotoMaker customizations?

Seems to me this is simply listing a sequence of (the equivalent of) fastboot commands ...
[Moto X Original Android Development] lowvolt1:
Although I know nothing about motomaker and how they implement the customizations on a device from motomaker, I would have to assume that by flashing the stock .XML file you would erase your customizations.

Could you delete those two commands and successfully flash the .XML? I do not know. I do however believe it to be plausible.

You could always "take one for the team" and try it. ;)

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] _litz:
Answer is, yep! works flawlessly.

So by removing the "clogo" and "customize" lines from the xml file as well, you preserve your motomaker customizations.
[Moto X Original Android Development] Dark9781:
By removing

you will prevent any motomaker customizations from being erased. If you flash logo.bin you may lose any customized startup message, but it will remain on your phone. Mine returned after Moto sent out the surprise Holiday boot screen.
[Moto X Original Android Development] kpoverdorf:
In step 17 when I run the Echo commands the phone reboots almost immediately, barely able to turn bluetooth on, and then it stop at fastboot with the error:

Failed to hab check for recovery:0x56

Fastboot Reason: Boot Failure

USB connected

ATT new out of box. Any thoughts?
[Moto X Original Android Development] lowvolt1:
Toggling Bluetooth isn't really necessary. It is only in the instructions in case your phone doesn't reboot on its own, by toggling Bluetooth you can force a reboot. Your error is from something else. Without knowing all you did it will be difficult to tell you.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] kpoverdorf:
I followed this walkthrough (but with the ATT image) http://www.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/

I started with the fully stock image right out of the box. Everything seemed to go well. Until the echo commands
[Moto X Original Android Development] lowvolt1:
Were you on 4.2.2 out of the box?

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] kpoverdorf:
Yes 4.2.2 and pre camera update.
[Moto X Original Android Development] lowvolt1:
You need to start out on 4.2.2 with camera update.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] kpoverdorf:
I guess it would be easier if I just start over. What ATT image should I use? There are a couple available.

---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------

Ahhh. Ill just start over. Flash stock, apply camera update then proceed with process.
[Moto X Original Android Development] nhizzat:
This root is far from a nightmare. It's not difficult to follow instructions and type letter for letter what jcase posted. The people have problems/issues are those that didn't follow the instructions.

1. If you bought your Moto X through the Cyber Monday deal, your phone shipped with the 4.2.2 camera OTA already installed.

3. If Impactor isn't connecting, simply try unlocking the lock screen. That's all that was required for it to connect for me.

No, boot into recovery/wp off mode to apply/install SU binaries and other root-related needs. Reboot normally once done and root will stick.

Did you try unlocking the lock screen before running Impactor?

139.12.54.ghost_att.ATT.en.US is what you want to be on before running SlapMyMoto.
[Moto X Original Android Development] Ryphez:
I wonder if there's a way to get the custom boot up screen back. Slightly sad that it's gone, but really I never see it.
[Moto X Original Android Development] nhizzat:
There's several threads that cover this in Themes & Apps and General.
[Moto X Original Android Development] Ryphez:
Just looked through it and don't see anything to customize the boot animation to the text from MotoMaker
[Moto X Original Android Development] sd0070:
Finally rooted! Confirmed with titanium backup. Installed adaware, exposed, and other root apps.

But when trying to use secure settings, it says I need busybox. Busybox won't install :( It says try a different location, which I did to no avail.

Any advice?

Edit: is it possible to flash a custom kernel now?
[Moto X Original Android Development] nhizzat:
Read your post wrong. Thought you were referring to the winter splash and boot animation. Maybe try going back to stock with RSD?

Custom kernel? Only if your bootloader is unlocked.
[Moto X Original Android Development] erikcave:
Thanks a lot. This was the charm for me.
[Moto X Original Android Development] sfetaz:
Well I am in the boat of stuck without root because of the write protection mod and a soft brick I caused. I am not a developer or anything but is there any way to get in touch with Jcase if he needs someone to test his updated methods with? I don't mind using my Verizon Moto X for testing if he needs someone to do so.
[Moto X Original Android Development] id0l:
I know a bunch of people lost root after using MotoWpNoMo. Figured out a way to get root again. Made a thread here with instructions.
[Moto X Original Android Development] kpoverdorf:
Phew! I started over with the newer of the two 4.2.2 versions. I accidentally skipped a cmd but was able to double back and fix my mistake.

Root obtained! This is a tedious process but it's easy. Just gotta take your time and be very aware of what you are doing.

Thank you jcase!
[Moto X Original Android Development] joebarkho:
Do I need to downgrade to 4.2.2 before moving to step 2? There aren't any instructions for that part :/
[Moto X Original Android Development] kpoverdorf:
I used this - http://www.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/

If you're on 4.4 you need the newest version of 4.2.2 (has camera update)
[Moto X Original Android Development] TheWhiteChallenger:
Quick interjection, is dose safestrap work after this method? can someone who has tried confirm plz?
[Moto X Original Android Development] kpoverdorf:
I am having trouble getting Adaway to work. Any thoughts?

Nevermind... I had to run "adb reboot recovery" to get write access

---------- Post added at 12:46 PM ---------- Previous post was at 12:00 PM ----------

Is there a recommended way to install a zip file (http://xdaforums.com/showthread.php?t=1749921)? I am too used to just installing through my phones custom recovery.