yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] hanifaz:
Please Help Root

I was able to downgrade the att moto x to 4.2.2 then use RockMyMoto to root, but SlapMyMoto refused to do it, it says device is rooted. Then I tried MotoWPN. In between I have restored 4.2.2 many times using RSD Lite to begin the instructions from scratsh every time. I did not sleep for two nights, **** google, I bought a google phone to avoid iphone and jailbreak and all the ****ty control freaks at apple. Why can't I be the admin of my own phone.

Please help, now i am stuck at 4.2.2 rooted and when I upgrade to 4.4 my phone gets into a loop reboots.
[Moto X Original Android Development] lowvolt1:
Since you have already rooted using rock and ran motowpnomo successfully, now just flash back to clean 4.2.2 no root, write protect disable is permanent, provided it was successful. And do the slapmymoto steps. In the process you will be prompted to take the 4.4 OTA.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] redhonker:
Regarding MotoWPNoMo.

If I go into recovery on each reboot and disable write-protect, will SlapMyMoto work? If so, can I root with SlapMyMoto first and then go with MotoWPNoMo.

Thanks
[Moto X Original Android Development] lowvolt1:
I have asked my self this same question.

It sounds feasible at first thought.

However, In order to "boot recovery" in the disable write protection sense of it, you would have to be rooted. Slap won't work if your already rooted.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] elesatz:
Removed the getvar and have the same problem. Also I'm using the OEM cable and before taking the OTA I flashed the 4.2.2 firmware so I'm pretty confident I'm not doing anything wrong. I am able to flash 4.4. I have a bad feeling the new OTA is changing the bootloader.
[Moto X Original Android Development] lowvolt1:
No one else is reporting this issue. A couple other users just successfully reverted. Make sure your using the correct firmware.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] elesatz:
On the Droid Maxx. Using a Mac with fastboot to flash. I did a fresh download of Android 4.2.2 Blur_Version.12.15.15.obake_verizon.Verizon.en.US. Removed <step operation="getvar" var="max-download-size" /> from the XML. Still can't flash boot, recovery and system. Flashing 4.4 works perfectly.

I can try again tomorrow with the OEM cable, but I tried a HouseOfMoto RSD Lite flash with a Win 7 box although I wasn't using the OEM cable. That resulted in "preflash validation failed for GPT".
[Moto X Original Android Development] lowvolt1:
Yes. Just had another user with the Maxx successfully root 4.4. I do not however know if he was using a Mac. Can you try a windows machine?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] redhonker:
Sorry that I am quite confused.

- In order to do "boot recovery" to disable write protection, the phone must be rooted already -- did I read this right?

- MotoWPNoMo requires root in order to install (maybe I read this wrong)

- SlapMyMoto requires MotoWPNoMo

So we have to:

1. Downgrade to 4.2.2

2. Root with RockMyMoto

3. Install MotoWPNoMo

Are these the necessary steps? Or did I read it wrong?

Now the phone is rooted. And you said "Slap won't work if your already rooted."

What's the sequence after the above steps?

Thanks
[Moto X Original Android Development] lowvolt1:
Yes. Steps 1-3 are correct. After motowpnomo, you will have to flash back to 4.2.2 camera update. Which will effectively cause you to lose root. Write protection disabled through motowpnomo is permanent. After you downgrade to 4.2.2 camera update, you do slapmymoto. In that process you will be prompted to take the 4.4 OTA.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] redhonker:
I see. Looks like a really lengthy process. Does anyone know how long the entire process will take?

Thanks
[Moto X Original Android Development] lowvolt1:
Ha ha ha. When I rooted with rock the first time it took hours, but I really had no idea what I was doing. I have learned a ton along the way. I would anticipate an hour start to finish.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] trrubicon06:
I rooted using Slap 1.0. I just purchased the VZW Dev edition with the $100 off today. I plan on returning my Non-dev Moto X back to stock and resell. What is the easiest method for this after Slap1.0? Would one of the toolkits work?

Thanks
[Moto X Original Android Development] fndpena:
Is there a way to keep root after 4.4.2 OTA update?

I'm on 4.4 rooted by SlapMyMoto. Anybody know if updating and running those ADB commands will keep root on 4.4.2 as well?
[Moto X Original Android Development] lowvolt1:
Not enough people have received the update to be able to tell.

You should try it.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] fndpena:
A lot of users from Europe received the update yesterday. I hope someone come here with good news. I don't want to unlock my bootloader in order to root...
[Moto X Original Android Development] lowvolt1:
I'm thinking I might try it when I get the update.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] fndpena:
I'll try too and report back.

Should I run SlapMyMoto on 4.4 before updating to 4.4.2 or just run adb commands after the update is complete (assuming SlapMyMoto was already applied on 4.2).
[Moto X Original Android Development] elesatz:
I tried Win 7 today with the OEM cable. It is still refusing to flash boot, recovery and system. I was able to flash 4.4. The only thing I can think of is write protection is disabled. I wonder if somehow once its disabled you can't go back.
[Moto X Original Android Development] h1ghland3r:
Hi guys,

I received the 4.4.2 OTA today. I'm with SlapMyMoto 0.5, it means I didn't do MotoWPNoMoto. Is it possible to update?
[Moto X Original Android Development] lowvolt1:
I would think you would have to sbf to clean 4.2.2 or 4.4 before the OTA will take. Be prepared to lose root forever.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] h1ghland3r:
I haven't updated yet.
[Moto X Original Android Development] lowvolt1:
Which carrier? I'm assuming its out of the US.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] h1ghland3r:
Brazil Retail.
[Moto X Original Android Development] lowvolt1:
So, are you thinking about taking it?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] h1ghland3r:
No, in fact I would like to know if is possible keep the root updating for 4.4.2 (not using OTA, but downloading the zip file and flash).
[Moto X Original Android Development] lowvolt1:
Have you checked out the 4.4.2 update thread?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] h1ghland3r:
Only at the beginning.
[Moto X Original Android Development] fndpena:
Update downloaded, ready to install.

But I don't want to lose root :(

Nobody here with rooted 4.4 (slapmymoto) to confirm if root can be restored on 4.4.2?

I'm kinda afraid to take the risk.

ps.: SlapMyMoto files are still in my /sdcard, so my guess is that running these commands may restore root after 4.4.2 update. Is there even a chance for this to be true?

adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
[Moto X Original Android Development] lowvolt1:
I have heard that the boot loader is not updated. It is feasible that you could take OTA. You might try voodoo root keeper. Keep in mind no one knows for sure. You may be okay, but you may brick or lose root.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] fndpena:
It seems Voodoo Rootkeeper is not working anymore since android 4.3.

I guess I'm going to wait someone to test before updating...
[Moto X Original Android Development] lowvolt1:
Ha ha ha. Let someone else be the guinea pig.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] fndpena:
lol

You got the update already?
[Moto X Original Android Development] Deenybird:
Thank you for your work on this jcase, and thank you everyone else for your contributions.

I have a problem on step 2.

In impactor I run the command "# start telnetd as system on port 2222" and that completes successfully.

Then when I run the command in impactor "telnet {192.168.1.11} 2222" it performs some actions for ~5 seconds and then I get the error "link failed file exists". Same thing for this command "dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto"

telnet client is installed

stock 4.2.2

ADB is enabled

Install from unknown sources is enabled

Connected to same wifi network as computer

Thanks for any advice!

Update: Unclear what solved things (perhaps using puttytel for telnet), but by continually plugging away I got past it.
[Moto X Original Android Development] fndpena:
I heard about an user that updated and root was kept.

But now he got an error when trying to boot recovery. The following message:

partition (recovery) Security Version Downgrade

Boot up failed﻿

Somehow, recovery is not working on his phone now...
[Moto X Original Android Development] lowvolt1:
No. I'm not sure I want it if I can't have root.

---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------

is he on locked boot loader?
[Moto X Original Android Development] Deenybird:
After many tribulations, i have things working up to this point. I am unclear about this step, and could use some guidance.

If in fact I am not currently running the 4.2.2 camera update, how would I go about restoring to it?

I am on 4.2.2 (build# 13.9.0Q2.X-116-X-17-54), rocked & motowpnomo'd.

I feel confident I can proceed with SlapMyMoto once I am at the proper starting point. Thank you.

Edit:

Dark9781 posted the following here.

The fastboot instructions he linked to on this page show many fastboot commands and I don't know which one would install the 4.2.2 camera update. And he's missing the line to remove when using rsdlite
[Moto X Original Android Development] lowvolt1:
You should just use rsdlite.
[Moto X Original Android Development] nexus7lte:
I have had no luck getting root on 4.4 I went through all the steps in the root script, the moto x tool kit, and manually. If I was on 4.2.2 pre camera update but rooted with write protection off when booting into the recovery slot, how do i get my phone back to complete stock 4.2.2 with camera update? My guess is my phone was not completely stock when I updated to 4.2.2 camera update and that stopped me from getting root in 4.4 . Will RSDLIte bring my phone to where it needs to be to gain root and update to 4.4 ? thanks

---------- Post added at 07:54 PM ---------- Previous post was at 07:44 PM ----------

My guess is I missed step 4 here since i havent used rsdlite. What is the line to be removed from the xml file and where is it located? thanks
[Moto X Original Android Development] lowvolt1:
Download the proper XML file for your device and carrier. Edit the file and remove the get-var line. Its in the XML. You will see it.
[Moto X Original Android Development] a1exus:
oh boy! i can't wait for 4.4.2!! i hope we'll be able to preserve root and all))
[Moto X Original Android Development] lowvolt1:
I wouldn't count on it.

Slapped the sh*t out of my X.

If you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] n3ptun3:
Just a heads up. I had a 4.4 Retail BR rooted phone, I received the OTA update, flashed and I still have root. I did not flash the stock image before taking the OTA, I just had it install as if I was stock.

I did have SuperSU ota survival checked though, don't know if it helped. But anyhow, my 4.4.2 has a working root. Xposed is a mess though... it doesn't work like on 4.4 and screws SuperSU prompt and other stuff

D/SFPerfTracer( 7303): layers: (3:10) (DimLayer: 0:28)* (DimLayer: 0:2)* (FocusedStackFrame: 0:1039)* (StatusBar: 0:7286) (NavigationBar: 0:8012) (com.android.systemui.ImageWallpaper: 0:905)* (DimLayer: 0:991)* (DimLayer: 0:171)* (de.robv.android.xposed.installer/de.robv.android.xposed.installer.WelcomeActivity: 0:103)* (de.robv.android.xposed.installer/de.robv.android.xposed.installer.XposedInstallerActivity: 1:69)
F/libc ( 3515): Fatal signal 11 (SIGSEGV) at 0xb6f24698 (code=1), thread 3515 (app_process)
I/DEBUG ( 230): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 230): Build fingerprint: 'motorola/ghost_retbr/ghost:4.4.2/KXA20.16-1.26/28:user/release-keys'
I/DEBUG ( 230): Revision: 'p300'
I/DEBUG ( 230): pid: 3515, tid: 3515, name: app_process >>> app_process <<<
I/DEBUG ( 230): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr b6f24698
W/NativeCrashListener( 7645): Couldn't find ProcessRecord for pid 3515
I/DEBUG ( 230): r0 ffffffff r1 b6ea44f5 r2 0000005f r3 00007550
[Moto X Original Android Development] lowvolt1:
Nice! So did you have xposed modules active when you took OTA?

And then you just downloaded and installed?

Slapped the sh*t out of my X.

If you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] n3ptun3:
I did, I might have screwed up on Xposed by having it enabled during the OTA update. I was so excited I forgot about it and didn't disable it. I'll try recovering some stock files later on and doing a proper install of xposed to see if it fixes the errors.
[Moto X Original Android Development] lucfig:
My update is sitting here waiting for me to press install. I don't want to lose xposed, does any one knows for sure if disabling xposed before installing the update will keep it working?

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] lulajardim:
Nice to know that! I just received my notification and I'm thinking about trying myself the OTA with Xposed disabled...

Have you tried uninstalling and reinstalling xposed to see if it fixes?
[Moto X Original Android Development] Redjax:
Hey guys. I sold my Moto X on Swappa, and the buyer wanted a refund, so I decided to reactivate it and use it for my daily phone. I rooted it before selling it, but it appears the process has changed, and I've spent about 8 hours over the last 2 days trying to get it rooted again, with no success. I've followed this guide (including all the guides it links to), to a T, and every time I get to the very last step where I run SlapMyMoto, it tells me permission is denied. It appears when I flashed back to 4.2.2, rooted (which worked), and then took the OTA, it didn't actually open the backdoor, so I am unable to root on 4.4, and now it seems like I'm suck on 4.4

When I try flashing back to 4.2.2, whether through RSD or through the steps listed as part 2 of this guide, I get a failed error at the second step, trying to flash the gpt.bin partition. Is there really no way back to 4.2.2 after taking the 4.4 OTA? I thought I did that at least twice last night, but this morning it wouldn't let me flash back.

Thank you for the help.
[Moto X Original Android Development] lulajardim:
I decided I would take my chances and also do the OTA...

After checking the OTA SURVIVAL option on SuperSu, I uninstalled Xposed Framework and took the OTA...

I ended up with 4.4.2 rooted but I cannot install the Xposed Framework.

After I press install I get no error and the installer says that I have to reboot.

After rebooting, the app_process is back to its original state and app_process.orig is gone.

There seems to be some kind of protection which restores system to its original state.

I tried remounting system and creating a new blank file on /system

I was able to do it but after rebooting my phone the file is gone.

EDIT: After checking if my write protection is gone, It seems that MotoWpNoMo won't survive this OTA.

Also I tried running MotoWpNoMo again and no good.

So unless you wanna keep your Xposed up and running do not take the 4.4.2 OTA until someone finds a workaround.
[Moto X Original Android Development] lowvolt1:
Good to know. I can live without write protect being disabled. But not root.

---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------

OTA survival mode? Do you have paid version?
[Moto X Original Android Development] Mr. Orange 645:
Make sure you are using the 4.2.2 post camera fix firmware. You can't downgrade the bootloader to the 4.2.2 pre camera fix software.
[Moto X Original Android Development] lulajardim:
For me it is hard to live without xposed, specially because GravityBox helps me through a lot of things. For example, in my place of work it is impossible to make a call using 3G so I always switch to 2G. Right now I'm search for an alternative to this :(

About the OTA survival mode, yes I do have the paid version of the Supersu app.
[Moto X Original Android Development] h1ghland3r:
I update yesterday for 4.4.2 with root. But I needed to unlock bootloader, because I was having bootloop issues when trying to apply OTA. After I unlocked and flashed a recovery for 4.4 the OTA worked and my root keeped the same. Xposed and Gravity works fine.
[Moto X Original Android Development] Redjax:
Thanks for the reply. That is the firmware I'm using.
[Moto X Original Android Development] lulajardim:
If you have 4.2.2 camera update (I believe for at&t it is build number 139.12.54) you can use the method presented on this thread and you'll end up on version 4.4. But I do not recommend taking the OTA to 4.4.2.

You can only change your recovery if you have an unlocked bootloader. If i'm not mistaken, on AT&T, you can only do that if you have developer edition.

If you happen to have a dev edition, I don't recommend using this method. Search the forums for help on unlocking your bootloader and rooting.

Please only use this thread if have doubts specific to the SlapMyMoto root method.
[Moto X Original Android Development] Redjax:
I have rooted my phone on 4.2.2, and used MotoWPNoMo, but when I try rooting with SlapMyMoto, the first time I have to open Cydia Impactor I get the error "Signature bugs unavailable." Any known fixes?
[Moto X Original Android Development] lowvolt1:
It sounds like you took OTA to 4.4. Is that correct?
[Moto X Original Android Development] Redjax:
Yes, why? Should I flash up to it or something?
[Moto X Original Android Development] lowvolt1:
You have to be on 4.2.2 to use cydia.

Here's the breakdown.

1) Root 4.2.2 using rockmymoto ( you did that)

2) disable write protection using motowpnomo. (You did that)

3) flash back to clean unrooted 4.2.2 (you didn't do that)

4) root using slapmymoto. ( you will be prompted to take the OTA in this process)
[Moto X Original Android Development] Redjax:
You are correct. What I was doing was rooting using RockMyMoto and disabling the write protection, but then the directions got unclear so I actually flashed up to 4.4, THEN used SlapMyMoto. I will try flashing back and then using SlapMyMoto, then taking the OTA. Hopefully it works this time. Thanks for the advice!

If it helps, I've been using this script for rooting.
[Moto X Original Android Development] lowvolt1:
Whether doing it manually or using the script, the process is the same.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Redjax:
Ok, I'm starting to get pissed, I have spent so many hours doing this at this point. Never had this much difficulty rooting a device.

I keep getting this: and I don't know why.

Here's what I'm doing.

1. Flash back to 4.2.2 using this guide (at the end of the post, click "Show content."

2. Root using RockMyMoto

3. Attempt MotoWpNoMo (it tells me write protection is already off, but I try it every time just to be sure).

4. Flash back to 4.2.2 using RSD Lite because aforementioned method doesn't work anymore (some kind of PIV error).

5. Take 4.4 OTA on my phone, let it install.

6. Try to install the install.sh script (doesn't work).

Am I missing something?
[Moto X Original Android Development] lowvolt1:
So when your on 4.2.2 and you do slapmymoto, are you pushing su and slap .jar files and running cydia and telnet before taking the OTA?

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Redjax:
Yes I am. I do the whole process, as listed in the OP, before taking the OTA, and after the OTA the install shell script doesn't run. But now I can't even root the phone with RockMyMoto for some reason.
[Moto X Original Android Development] lowvolt1:
You just want to be in fastboot, which is where you are before when you are trying to enter recovery.
[Moto X Original Android Development] eyc:
But, to complete the first step (flash back to camera update), I need to flash the zip, right? I can only do that in recovery, as I understand it.

** OK, so I think I have the terminology wrong. I want to be in fastboot to flash the zip. I'm about to **** up my phone. I feel it. Whatever. **** it.
[Moto X Original Android Development] lowvolt1:
No. use rsdlite. from fastboot you can flash the xml
[Moto X Original Android Development] MaddHatt3r:
Yes that whole 4.2.2blahblahblah.xml.zip file you download is the file your run through RSD Lite and you run it when you are in that 1st screen when it boots up after holding power+Vdown
[Moto X Original Android Development] lowvolt1:
Just remember to remove getvar line
[Moto X Original Android Development] MaddHatt3r:
good call, open the xml.zip with an archive manager (winrar or 7zip) and edit the longnamethatisstupidlong.xml and delete ONLY the line that contains getvar, the entire line.
[Moto X Original Android Development] lowvolt1:
Why on Gods green earth wont supersu update the binaries?
[Moto X Original Android Development] eyc:
I don't understand. Why do I need to delete that line? Am I getting in over my head here?
[Moto X Original Android Development] MaddHatt3r:
LOL maybe.....do you have your adb working?
[Moto X Original Android Development] mj0528:
If you reboot and attempt to get to recovery wo off mode, what happens?
[Moto X Original Android Development] eyc:
ADB is working. Files all downloaded. I'm ready to take the plunge, but I'm getting stuck at the first step (i.e., flashing back to camera update).

I've now downloaded RSD Lite 6.1.5, gone into the VZWyaddayadda.zip, deleted the getvar line, and am ready to flash this sucker. Crossing my fingers.
[Moto X Original Android Development] lowvolt1:
How do I go about trying to get to recovery wo off mode.?
[Moto X Original Android Development] mj0528:
Adb reboot bootloader then press volume down till you get to recovery and the press volume up to enter the hijacked recovery which is wp off mode to install supersu.
[Moto X Original Android Development] lowvolt1:
In the powered off state, I hold power and volume down. get into the bootloader. volume down to recovery then volume up. Phone just reboots.
[Moto X Original Android Development] mj0528:
Then try to update binaries in supersu since you made it into the mode correctly
[Moto X Original Android Development] lowvolt1:
I tried. It failed.

What weird is root checker says I have root. but it never prompts for permission.