yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] eyc:
I'm trying to "run telnet" and getting problems.

I've gotten through the steps including launching Cydia Impactor. I "started" the "# start telnetd as system on port 2222" and it completed. The next step is as follows:

----------

Once the process is complete, run telnet:

telnet {your phone's ipaddress} 2222

----------

Where am I supposed to type that in? I tried in the ADB command prompt, and I just get a message that 'telnet' is not recognized as an internal or external command...
[Moto X Original Android Development] lowvolt1:
What version of windows are you on? I had major trouble doing this with RocMyMoto. If you go to that thread there is a HERE tab you can click on that will show you another way to telnet. That seemed to work for me.
[Moto X Original Android Development] MaddHatt3r:
Your windows may not be set up to handle telnet, it is easily turned out, what Windows version are your using?
[Moto X Original Android Development] eyc:
Using Windows 8.1.

Thank god you guys are still around to help me. Very much appreciate.
[Moto X Original Android Development] lowvolt1:
You can't root with rockmymoto because you have disabled write protection. Don't use the script. Use the adb commands. The hard part is over. Slap will only take a few minutes.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.

---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------

Oh and after the OTA you may have to re enable USB debugging. And I am pretty sure you will have to slide unlock the phone and grant permission.

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] grad061980:
This is the guide I used on 2 moto x phones with no issues.

http://www.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/

It says it's for Verizon, but I'm on us cellular & had no issues. I started on 4.2 after the camera update.

I then used this method MotoWpNoMo to disable write protection

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

Edit: On the SlapMyMoto method I used the SlapMyMoto.5c instead of this version 1.0. I used SlapMyMoto on Mac OS X 10.9 & MotoWpNoMo on my virtual machine running windows xp.
[Moto X Original Android Development] rcklss1:
ok so i just got my AT&T Moto X today and it was still on 4.2.2 i was able to root with PwnMyMoto and then I ran MotoWPNoMo successfully but when i get to step 2 in this thread it says it does not support rooted devices... what am i doing wrong??? I thought i only had to reflash 4.2.2 if i had already taken the camera or 4.4 updates...

thanks in advance guys
[Moto X Original Android Development] lowvolt1:
So let me get this straight. You rooted 4.2.2 using slap?

Here's what you need to do. Since you have already rooted and ran Motowpnomo. You have successfully disabled write protection. Now just flash back to clean unrooted 4.2.2 and run slap. In that process you will be prompted to take the 4.4 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] rcklss1:
i rooted with pwnmymoto since it didnt even have the camera update... where im at now is that it keeps trying to install the camera update OTA... i downloaded the 4.4 update manually on my computer but not sure how to flash it... RSD lite failed cause it couldnt swtich to fastboot
[Moto X Original Android Development] lowvolt1:
https://www.dropbox.com/s/rjx71rkhy....9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml (1).zip

Use this to flash 4.2.2 camera update. Edit out the get var line and flash using rsdlite.

Then follow slapmymoto

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] cpetersen2791:
anyone test this on the new OTA 4.4.2 yet? I haven't gotten my OTA yet, but i "want to be ready", or at least deny the update until i can root!
[Moto X Original Android Development] lowvolt1:
There have been reports of people keeping root if they are already rooted on 4.4. But they have pro version of supersu and they tick mark the root keeper option. However I have also heard that it breaks write protection disable.

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] cpetersen2791:
So if it breaks WP...does that mess w/ Root? That part always confused me.
[Moto X Original Android Development] lowvolt1:
No. You would still be rooted you just can't write to system. So things like xposed modules won't work. You may still be able to reboot "recovery" to disable write protection. But that is in confirmed.

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] cpetersen2791:
So best bet is to hold off on OTA until something new to disable write protection comes along? My bootloader is locked (XT-1058 on ATT/USA) so safestrap won't work to disable write protection as well. Right?

Motorola makes things so confusing, compared to my old Maguro, then HTC One.
[Moto X Original Android Development] a1exus:
where is 4.4.2?! i'll try it out)))
[Moto X Original Android Development] lowvolt1:
Yeah. I'm not taking OTA. Safestrap won't disable write protection. Not even sure safestrap will work on 4.4.2. Nitro has some things in the works. I hear its supposed to be awesome. I'm waiting on OTA until I see what is developing.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.

---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------

It depends on your carrier. It hasn't been released in USA yet to my knowledge. At least not to every carrier.

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] a1exus:
Verizon Wireless
[Moto X Original Android Development] cpetersen2791:
Thanks for the info!
[Moto X Original Android Development] lowvolt1:
I'm on vzw also. I am pretty sure they haven't pushed it yet

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] lulajardim:
Another thing I'd like to add is that without being able to write to system you won't be able to update the su binaries whenever chainfire updates it.

About reboot "recovery" to disable write protection, I'm still waiting for the Brazilian 4.4.2 files to show up on droid-developers to run a few tests on my phone. But so far no luck on reproducing what jcase did to disable write protection.
[Moto X Original Android Development] lucfig:
Just for you guys know.

I have already received the 4.4.2 OTA and root is still working, I don't have the pro version of SuperSu.

Xposed works if you soft reboot. A normal reboot breaks xposed, just soft reboot and it works again.

Enviado de meu XT1058 usando Tapatalk

---------- Post added at 08:26 PM ---------- Previous post was at 08:00 PM ----------

https://www.youtube.com/watch?v=Nr_pEWbn-UM&feature=youtube_gdata_player

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] cpetersen2791:
with locked bootloader??
[Moto X Original Android Development] lucfig:
Yep

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] LuciferzRage:
Soo many questions, soo many different answers and yet im still confused after reading a few pages.

So my own question is:

I had my own Moto X delivered to me with 4.4 right off the box. Can I still root using this and if so what will I not be able to do while rooted?

I am asking this because I want to keep the stock rom, but remove all the crapware in here (ie Moto Care, Migrate some Google apps, etc)

I also have some backed up apps from an old phone I'd like to restore. I wanna make sure I can do any of these before I attempt to root using this method.
[Moto X Original Android Development] lowvolt1:
In order to root you have to flash back to 4.2.2 post camera update. Then root using rockmymoto then run motowpnomo then flash back to 4.2.2 post camera update. Then root using slapmymoto. In that process you will be prompted to take 4.4 OTA.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.

---------- Post added at 03:32 PM ---------- Previous post was at 03:28 PM ----------

Okay. Have you checked your write protection status? My prediction would be you would receive back a 1 meaning write protection is enabled.

The developer of gravity box module recommends a full re boot when using his module and not a soft boot.

Doing a soft boot and keeping xposed modules working makes sense as you would not be rebooting totally out of "recovery" but what if/when you need to do a full re boot?

I for one don't think its worth risking for what fixes come with the update that I have already put in place using root browser.

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] LuciferzRage:
Kool, so even though I'm already on 4.4 right off the box I can still downgrade. I was worried I wouldn't be able to since 4.4 was/is my default firmware
[Moto X Original Android Development] lowvolt1:
You should be able too. But not if you are/were on 4.4.2.

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:
Oh I definitely didn't realize I didn't need to use RockMyMoto...thanks for that! So really all I need to do now is flash back to 4.2.2, root with SlapMyMoto, and take the OTA, then use the install script...?

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

Thank you for the links, I'll look into it. I have already used RockMyMoto and MotoWpNoMo, so I think all I need to do is flash back to 4.2.2 and use SlapMyMoto. I'll keep this guide for reference, just in case. Thanks!
[Moto X Original Android Development] Redjax:
Ok, using that guide, I got all the way to step 19 (echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper), but I get "/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission Denied."

Any suggestions?

Also, this might help...I just went through the steps again, and on step 8-9, where you open the telnet session and do the dalvikvm command, my phone doesn't auto-reboot like it says it should...is that a problem?
[Moto X Original Android Development] jpjm132003:
Anybody having troubles

After trying for longer than it EVER took to root ANY other device, I finally obtained root on my VZW Moto X on 4.4

I would like to provide the guides I had success with so that anyone frustrated might be able to reproduce my results:

First: FOLLOW THIS LINK

--Then expand the section: Locked Bootloader

--FOLLOW THIS SECTION PRECISELY

Then, Follow SlapMyMoto 1.0 (Works with MotoWPNoMo)

--When you START the SlapMyMoto process, your phone should be on a FRESH FLASH of 4.2.2

---I had trouble with RSDlite, Following the guide to do it manually through Fastboot and mFastboot yielded the successful result

--You should have Write Protection off

RUN: adb shell getprop ro.boot.write_protect

If the result is 0, then you are good with Write Protect

If you satisfy both of these conditions, begin the SlapMyMoto process.

--THESE CONDITIONS ARE CRUCIAL TO THIS PROCESS

Screenshot 1

Screenshot 2
[Moto X Original Android Development] Redjax:
Is it a problem that my phone doesn't reboot after the second time running the dalvikvm command through telnet? All the other steps seem to work just fine, but the phone doesn't reboot.
[Moto X Original Android Development] jimbo0914:
It doesn't auto-reboot on the 2nd time. You have to manually reboot before doing the 3rd step
[Moto X Original Android Development] Redjax:
Even when I manually reboot I still get the permission denied error on the first step. When I just typed adb devices into my terminal window, it lists the name of my device, but says "unauthorized" next to it....could that be my problem?
[Moto X Original Android Development] stillthisguy:
Yes, that is probably the problem. It should list "device", try switching from MTP to PTP and you should get a pop up on the phone to allow usb debugging. Then switch back to MTP.
[Moto X Original Android Development] grad061980:
Did you toggle the bluetooth(I put the Android power control widget on my homescreen to be able to toggle the bluetooth quickly). Also sometimes it does disable the USB debugging (double check that). Also after being on 4.4 you have to grant access to adb. I would double check that adb is seeing your phone.

EDIT: I see that your phone is not playing well with adb. Unplug your phone & run

adb kill-server

adb start-server

Plug phone back in & it should ask you to grant adb access on the phone. After granting adb access run

adb devices
[Moto X Original Android Development] Redjax:
Forgot to reply...I did fix it. I just unplugged the phone, plugged it back in, and I turn debugging off and back on, that fixed the issue.
[Moto X Original Android Development] grad061980:
Good to hear. Do you have root then?
[Moto X Original Android Development] Redjax:
No...I'm still in the process of running the script. I'm not getting very far with this process, and it's making me really mad.
[Moto X Original Android Development] lowvolt1:
Don't use the script. Do it manually. It works.

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:
Well, after the hours upon hours upon hours of manual attempts (literally over 20 hours of trying to get this done manually), the script worked in about half an hour on the first try. I'll be recommending it to people having trouble.
[Moto X Original Android Development] slanidracula:
THIS ^^^

Mine did not reboot automatically. I upgraded adb, waited a few minutes, rebooted manually, installed supersu, and had root. Thanks to all.
[Moto X Original Android Development] lulajardim:
I don't recommend upgrading to 4.4.2 at all... The write protection will be enabled again!

This means that you won't be able to update su binaries and also you wont be able to use Xposed unless you install it and soft reboot everytime you do a full reboot.

But there are some weird consequences if you do that. For example: after roughly 10hours of uptime my phone's package manager executable (pm) will stop working and give you a segmentation fault everytime you try to open it.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] ecetim:
So does the issue appear to only be with using Xposed? Personally I just wanted root so I could run WiFi tether.
[Moto X Original Android Development] r_diaz13:
One more thing though.. Now that 4.4.2 is out in full mode ready to be installed, we don't control the OTA correct so after you root with smmoto, it might upgrade straight to 4.4.2? Or am I wrong
[Moto X Original Android Development] lowvolt1:
Yes that very much could be the case. If you have the 4.4 XML you may be able to use rsdlite to do the upgrade.

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] lulajardim:
It seems that way.

Since i never needed it, I don't know the steps to enable WiFi tethering. But if one of the steps involve writing something on a write protected partition (i.e. /system) you shouldn't upgrade to 4.4.2

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] tejaskary:
Did 4.4.2 actually patch the exploit that slapmymoto uses? Who has confirmed this? If not, why can't we regain root on 4.4.2 using these steps?
[Moto X Original Android Development] lowvolt1:
The reports are that you can retain root through the OTA. What breaks is write protection disable.

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] kperajis:
I'm having trouble with step number 4. When I follow the first command cp /sdcard/install.sh /data/local/tmp/install.sh I get the this error:

C:\android-sdk-windows\platform-tools>adb shell
shell@ghost:/ $ cp/sdcard/install.sh /data/local/tmp/install.sh
cp/sdcard/install.sh /data/local/tmp/install.sh
/system/bin/sh: cp/sdcard/install.sh: not found

Any ideas why that's happening?
[Moto X Original Android Development] lowvolt1:
Those files need to be in your fast boot folder. The same place as you put the .jar and su.

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] erikiksaz:
So those of us on rooted 4.4 will have to wait for another workaround for 4.4.2 to be working normally with write protection off?
[Moto X Original Android Development] lowvolt1:
To be safe, don't take the OTA. There may never be another work around.

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] erikiksaz:
Oye, thanks. I wonder why a Google-owned Motorola is still such a pita to root.

Although I can't imagine the rooting process being any more of a pita with Lenovo.
[Moto X Original Android Development] densets:
Do you have a way to stop getting the annoying OTA notifications? tried FOTakill but didn't work.

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

Hey, did you flash the OTA manually? i tried installing it the normal way but it just restart to 4.4.
[Moto X Original Android Development] lowvolt1:
Freeze your motoOTAupdater .apk

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] tabii:
There's a space after cp
[Moto X Original Android Development] Levistras:
I followed the walkthrough to the letter, putting my Rogers Moto X back to 4.2.2, running RockMyMoto (successfully) then MotoWpNoMo (successfully).

Then I ran SlapMyMoto a couple times, it told me to accept the OTA and resume once I'm on 4.4.2.

At this point I definitely had "adb shell getprop ro.boot.write_protect" returning me 0.

AFTER the OTA... I checked this again, and "adb shell getprop ro.boot.write_protect" is now 1.

The install.sh exists in the /sdcard/, however after I run this:

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

I can confirm that the /data/local/tmp/install.sh gets added to uevent_helper, for a brief period of time

Then uevent_helper changes to this:

root@ghost:/sdcard # cat /sys/kernel/uevent_helper

cat /sys/kernel/uevent_helper

1

root@ghost:/sdcard #

Only has a "1" in it, which indicates to me that the script that we copied into there has been run, and.... failed? I"m guessing because write protect is back on again?

Can anybody advise how I might get around this? I have a sinking feeling that the Rogers OTA for 4.2.2 (which came out a little after the AT&T one) may have patched this exploit hole...

Apps seem to think that the device is rooted.. as in they pause and wait to get Root access (usually a dialog would appear here from whatever superuser app i have installed)... however no superuser popup occurs.

If I launch Chainfire or Koush's Superuser app.. it indicates that it cannot update and cannot obtain root itself.

Some more info while trying to step through the install.sh myself:

#!/system/bin/sh

echo 1 > /sys/kernel/uevent_helper

/system/bin/mount -o remount,rw /system

/system/bin/rm /system/etc/install-recovery.sh

/system/bin/cp /sdcard/install-recovery.sh /system/etc/install-recovery.sh

/system/bin/cp /sdcard/su /system/xbin/su

/system/bin/cp /sdcard/su /system/xbin/daemonsu

/system/bin/chown 0.0 /system/xbin/su

/system/bin/chown 0.0 /system/xbin/daemonsu

/system/bin/chown 0.2000 /system/etc/install-recovery.sh

/system/bin/chmod 06755 /system/xbin/su

/system/bin/chmod 06755 /system/xbin/daemonsu

/system/bin/chmod 755 /system/etc/install-recovery.sh

/system/bin/rm /system/bin/log

/system/bin/ln -s /system/bin/toolbox /system/bin/log

root@ghost:/sdcard # /system/bin/mount -o remount,rw /system

/system/bin/mount -o remount,rw /system

root@ghost:/sdcard # /system/bin/rm /system/etc/install-recovery.sh

/system/bin/rm /system/etc/install-recovery.sh

root@ghost:/sdcard # /system/bin/cp /sdcard/install-recovery.sh /system/etc/install-recovery.sh

/system/bin/cp: /system/etc/install-recovery.sh: I/O error

1|root@ghost:/sdcard # /system/bin/mount -o remount,rw /system

/system/bin/mount -o remount,rw /system

mount: Read-only file system

255|root@ghost:/sdcard # chown 0.0 /system/xbin/su

chown 0.0 /system/xbin/su

Unable to chown /system/xbin/su: Read-only file system

10|root@ghost:/sdcard # /system/bin/mount -o remount,rw /system

/system/bin/mount -o remount,rw /system

mount: Read-only file system
[Moto X Original Android Development] jimbo0914:
Did you OTA to 4.

4

.2 by chance?
[Moto X Original Android Development] rivlez:
I had so many issues with this the past day on a new AT&T Moto X I had tried to get root for 4.4. I was able to get root without issues using rockmymoto but I could never get WP off no matter what. I read and read but found nothing that helped me out. While running motowpnomo it would never work and I had no idea why. I reflashed my phone more than a dozen times and rooted but would always get stuck on motowpnomo not working. I noticed shortly after that ADB SHELL was asking for su access which I granted and it seemed to get my further along in the process. Next it would fail on supersu and uninstall itself and I would be stuck again. I finally tried using supersu v1.75 instead of the latest from the market and it worked without issue. I would bet that these are the issues that most people are having. Good luck!

FYI - I thought I would post this so that someone wouldn't waste 5 hours of their life like I did.

---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------

This doesn't work on 4.4.2 OTA.
[Moto X Original Android Development] Levistras:
I did OTA to 4.4.2... .is there a 4.4 OTA being offered to AT&T and other carriers that comes before this? (As in.. is 4.4.2 not supported for this?)

From the 4.2.2 Camera Update I was offered only a 4.4.2 OTA update. Taking this after running SlapMyMoto (the requested two times) on 4.2.2 removes my write access to the system partition.
[Moto X Original Android Development] lowvolt1:
I am sorry to inform you that you are done. Since you took 4.4.2 there is no going back to 4.2.2. You at this point can't root

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] bongostl:
Yep. Exactly.

For most carriers there was a 4.4 Rogers went straight to 4.4.2

I'm afraid you're out of luck, unless you're willing to unlock your bootloader
[Moto X Original Android Development] Levistras:
Bootloader unlocked, root restored. It is still a good day. :)
[Moto X Original Android Development] cpetersen2791:
So, quick question. If you take the OTA to 4.4.2, you remain rooted, but lose the ability to write to /system.

Does that mean all existing apps that had root (gravity box on Xposed Framework) will still work, since they were there before the OTA, or do they break?
[Moto X Original Android Development] lowvolt1:
There are mixed reports of this. Some say soft boot and your good others say it breaks.

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] cpetersen2791:
Ever?

Or full reboot, broken (as in FC errors), then reboot soft, all Ok?

Just trying to wrap my head around it.