yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] tejaskary:
Finally got it to work !! If you are having issues, try logging on the freenode #MotoX where jcase will provide extremely helpful suggestions..
[Moto X Original Android Development] zwolf4444:
RSDing and trying again worked for me. Didn't do anything different the second time. Strange, because I tried this the second I pulled it out of the box, so there shouldn't have been any user data to wipe. Thanks jcase for the help and general awesomeness!
[Moto X Original Android Development] atomb:
Got it to work!!!!!! Took some work and some jumping around. I needed an updated version of fastboot.exe and adb.exe from the latest sdk. Thanks for the 4.4 Root!
[Moto X Original Android Development] DiGi91:
Got it to work on my Mac, wasn't too bad hardest part was the equation before running the exploit! xD

Loving 4.4 on my Moto X!
[Moto X Original Android Development] TheScarySnail:
i know it's compatible with SS, and i'm running SS on my vzw gs4 on MI1, will this work? the instructions are only for the moto x
[Moto X Original Android Development] juancaperez2000:
trying to flash factory recovery but system does not found it

help please
[Moto X Original Android Development] grifforama:
OK, this sucks.

I thought I was pretty seasoned in flashing ROMS kernels, back to stock, rooting etc.

I am stuck at the first step. Flashing the stock 4,2,2

I'm getting

"Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned fail.

I had performed a factory reset on my 4.4 , and had removed the line from the xml...

Anyone any ideas ?
[Moto X Original Android Development] eyc:
Are you using rsdlite? And you deleted getvar right?
[Moto X Original Android Development] grifforama:
RSDLite 6.1.5 and removed the getvar line
[Moto X Original Android Development] eyc:
Wish I could be of more help, but I'm pretty new to this. I used the same version of RSDLite and also removed the getvar line. I was using Windows 8.1 and I first downloaded the SDK and also had to get the Moto X drivers from Motorola first, as my computer did not automatically install them.
[Moto X Original Android Development] juancaperez2000:
[MENTION=2169613]eyc[/MENTION] could you help me please where i need to place the recovery for i can flash it for my mac
[Moto X Original Android Development] eyc:
Eating dinner. Will help as much as I can after.

---------- Post added at 09:00 PM ---------- Previous post was at 08:14 PM ----------

The recovery file needs to be in the same folder as the ADB stuff. In fact, all of that stuff from the VZW and Slap zips need to be extracted and placed in that folder.
[Moto X Original Android Development] juancaperez2000:
thanks google help me too lol phone root it i google it how to do it and also think about it and now my phone is running perfect thanks
[Moto X Original Android Development] eyc:
Awesome. Glad you are rooted.
[Moto X Original Android Development] flashallthetime:
Had the same issue yesterday, as I accepted the 4.2 camera ota, tried to rsdlite back to pre camera ota and had the gpt.bin, so I had to download the latest fxz with the camera for it to complete. My boot loader is unlocked, so I guess you can't go back to previous version from an ota. I think your stuck on 4.4. You may want to manually try through fastboot rather than rsdlite and see if it works.

Sent on my Moto X
[Moto X Original Android Development] jdellingson7:
I'm looking to purchase a Developer Edition x and was wondering if this is the way to root it when it comes or is this for the retail version only? I have googled how to root the dev edition and I'm coming up empty. I have heard so many things about this phone and want to make the jump but want to know how to approach things before hand. Please Help
[Moto X Original Android Development] flashallthetime:
Just unlock your boot loader and flash twrp recovery, finish off with flashing superuser and you are rooted.

Slapmymoto is only for folks who can't unlock there bootloader

Sent on my Moto X
[Moto X Original Android Development] grifforama:
Would I only have to flash recovery system and boot ? What about this gpt. Bin ?

---------- Post added at 12:50 PM ---------- Previous post was at 12:44 PM ----------

Is anyone else having problems flashing back to stock from 4.4 ? Anyone else getting this gpt.bin error that I'm seeing?
[Moto X Original Android Development] :
Now that the full RSDlite package is available for the VZW 4.4 version, is there any reason not to flash back the 4.4 recovery, bootloader, gpt & logo, once rooted? I mean, we've determined that the new bootloader does not preclude you from downgrading again if necessary.

---------- Post added at 06:57 AM ---------- Previous post was at 06:53 AM ----------

I had no problems going back to the camera update 4.2.2 from 4.4. I might try downloading the RSDlite recovery image package again to make sure nothing was corrupted (though I'd expect an MD5 failure if that were the case - not sure about the error you're getting).
[Moto X Original Android Development] grifforama:
What a nightmare.

I got as far as step 7, and I've lost adb. It says device offline.

I've tried numerous things, but nothing will make the phone connect

Any help/ideas ?
[Moto X Original Android Development] eyc:
With my limited knowledge, my only suggestions are as follows:

1. Make sure that the phone is not requiring you (via popup) to authorize the computer.

2. Make sure USB Debugging is enabled.

3. Restart your computer and phone.

4. Try a different USB port on the computer.

I'm not sure how you were OK on step 6, but then lost ADB on step 7. After the reboot, it just stopped recognizing your phone?
[Moto X Original Android Development] grifforama:
Yes, it looks like it just stoped recognising my device.

I just keep getting error: Device offline now.,

Late for work will try later..

ugh
[Moto X Original Android Development] mrjoshzombie:
make sure ADB is fully updated. If it is, uninstall and reinstall
[Moto X Original Android Development] MaddHatt3r:
Type adb devices and see if that shows the device. If it does, resume the process.
[Moto X Original Android Development] anotherfiz:
What is the deal with this exploit as far as recovery to stock? With the downgraded bootloader can I then automatically step back to 4.2.2 camera OTA firmware using RSDlite? Or will i be flashing back to 4.4 FW with RSDlite (which, i imagine would reflash the new boot loader and cause me to start over) ?
[Moto X Original Android Development] jmill75:
For those having offline issue's...make sure your phone still has debugging activated. If you do try disabling and re-enabling.
[Moto X Original Android Development] lowvolt1:
It takes awhile after reboot to see the device again. I waited like 5 minutes between reboots for the next command.

via rooted KIT KAT moto X
[Moto X Original Android Development] jzanick:
Ran into the same problem yesterday. What I did:

1) Updated SDK

2) Typed "ADB Version" on command prompt to check version

3) Even after SDK update, it looked like ADB is still on the old version 1.0.29

4) It needs to be on 1.0.31

5) Typed "adb 1.0.31 zip" on google search and went with the link that says /pub/mozilla....

6) Downloaded 1.0.31 and replaced the old ADB files with the downloaded ones

7) Now when i type ADB Version,,, it shows 1.0.31

8) I unplugged phone

9) Revoked USB debugging authorization under Developer Options

10) Plugged in phone

11) Typed "ADB Devices"

12) Authorization prompt shows up on my phone this time.. I approve it

13) Phone is now online

13) Continued rest of the steps for root
[Moto X Original Android Development] grifforama:
How do I make sure its fully updated ?

I'm stumped because it was working all the way up to the 4.4ota step.then it borked.

I'm going to try from work in a couple of hours.
[Moto X Original Android Development] eyc:
Did you read the post that immediately precedes yours? jzanick shows you how.
[Moto X Original Android Development] Zero_FeniX:
You also have to accept a "token". Go into the developer options. Also did you re enable the developer options and usb debugging?
[Moto X Original Android Development] grifforama:
Awesome.will try this later .
[Moto X Original Android Development] mrjoshzombie:
Version: 0.5c

Make: Verizon

Prerequisites: Was on 4.2.2 (camera update) fully rooted. Fastbooted back to stock

Ran through all the steps and everything worked well up until I had to install SuperSU. Got the app to install fine but the binaries wouldn't install and I had no root. So, I went back to step 6 and redid everything. Now anytime I run

echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper

I get

shell@ghost:/ $ echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied

I've gone back to step 5 all the way back to 7 and no go. I've rebooted normally, into recovery, pushed the files numerous times (which all show a proper data transfer)

$ ./adb push su /data/local/tmp/su
5646 KB/s (104564 bytes in 0.018s)
$ ./adb push install.sh /data/local/tmp/install.sh
466 KB/s (607 bytes in 0.001s)
$ ./adb push rec.sh /data/local/tmp/rec.sh
100 KB/s (158 bytes in 0.001s)
$ ./adb push install-recovery.sh /data/local/tmp/install-recovery.sh
448 KB/s (702 bytes in 0.001s)
$ ./adb push setup.sh /data/local/tmp/setup.sh
75 KB/s (165 bytes in 0.002s)
$ ./adb reboot

And I am entirely at a loss now. I've restarted my computer, redownloaded the SlapMyMoto files, pushed them probably 20 times now, and still no go. I've even read every single post in this thread hoping to find an answer, and it seems to "just work" for people eventually with the permission issues.
[Moto X Original Android Development] mj0528:
All went well here except for when i did the last shell command and I got the same permission denied. I updated adb earlier as well so not sure the issue now

worked the second time starting from step 6. Bluetooth is on so leave it on then run the last shell command and then turn it off
[Moto X Original Android Development] grifforama:
I'm getting the same problems.

It didn;t even let me toggle bluetooth. It just rebooted on it's own.

It says I dont have SU binaries installed.
[Moto X Original Android Development] jzanick:
I read from the threads that most have trouble toggling bluetooth because the phone rebooted too fast.

What I did was either;

1) Go to bluetooth page so I can quickly toggle before the screen goes off, OR

2) Set Power Control widget on my homepage so I can quickly toggle blueetooth before the screen goes off

Not sure what the bluetooth toggle does for the root though. I have read that some successfully root without toggling bluetooth.
[Moto X Original Android Development] lowvolt1:
I haven't heard from anyone that toggling Bluetooth is a must. I never had time to toggle and I am rooted.

I had to do the entire thing 4 times.

Try waiting about 5 minutes after each reboot to do the next step. It worked for me.

via rooted KIT KAT moto X

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

On my third try I had this exact issue. Binaries would not update. Root checker said I was rooted but I could not do anything without supersu.

I flashed back to 4.2.2 and started fresh. Waited 5 minutes between reboots and then 5 minutes after final reboot to install supersu and it worked.

via my slapped KIT KAT moto X
[Moto X Original Android Development] mrjoshzombie:
Is it possible to downgrade to 4.2.2 camera update without having to wipe the phone, or is that going to cause a bootloop? (I'd rather try to avoid wiping things as much as I can.) I suppose this is the next course of action I'm at.
[Moto X Original Android Development] mandrsn1:
i spent a couple days trying to upgrade to 4.4 without wiping data. the install was failing to flash the OTA (it would error out). After wiping, it worked the first time.
[Moto X Original Android Development] typhoone:
It may have taken me the better part of 5 hours .... but I have a rooted KitKat Moto x
[Moto X Original Android Development] grifforama:
I'm rooted.

I just did 5,6 and 7 again making sure I had Bluetooth toggle on the home screen.

Thank jcase. Awesome job.
[Moto X Original Android Development] MaddHatt3r:
Backup your data and use RSDLite, you will loose data. On a process that is already relatively sensitive, minimize the variables. Rooting isn't for the play it safe crowd, especially since the big corps are crunching down on vulnerabilities.

Sent from my XT1060
[Moto X Original Android Development] Jposton:
Who has done this successfully on Ubuntu? Do I just fastboot the recovery, system, and boot images? I'm currently on 4.4 leak.

Thanks
[Moto X Original Android Development] MaddHatt3r:
You could try and see if RSDLite will function properly through wine, but that might be stretching it. My guess would be do a factory reset then yes fastboot all your .img files from the 4.2.2 fxz. iirc you need to do a fastboot -w before rebooting to clean data and cache. Its been a while since I have done this on Linux so take it with a grain of salt.

Sent from my XT1060
[Moto X Original Android Development] ericizzy1:
Im on rooted, 4.4 non de verizon moto x and since i rooted yesterday, im experiencing over heating issues and fast battery drain issues. Anyone else? Any fix?

Thanks
[Moto X Original Android Development] MaddHatt3r:
No problems here. Running smooth as butter, temps good, battery is good.

Sent from my XT1060
[Moto X Original Android Development] mercado79:
i highly doubt this is at all related to rooting, but...maybe. i'm at a loss. i've never seen this before.

just finished setting my vz moto x back up post-kit kat and rooting, etc. rebooted my phone for good measure. it's now stuck at a flashing status and nav bars. no adb. no network. screen just slowly flashes on and off.

if anyone is willing to take a look, i created a thread over here:

http://xdaforums.com/showthread.php?t=2543529
[Moto X Original Android Development] mrjoshzombie:
In case anyone is curious to know, to deal with my "Permission Denied" errors, I just wiped the phone completely, reverted back to 4.2.2 camera update, and went through all the steps from there (avoiding setting up the phone or my data until I was done).

I'm now able to report I'm part of the rooted 4.4 crowd.
[Moto X Original Android Development] jimmiet:
Just wondering if anyone has switched to ART after rooting? It "seemed" a little snappier to me on complete lockdowned stock and I wanted to make sure I wouldn't lose root before going back to it.
[Moto X Original Android Development] n1ckr0th:
can't seem to get impactor running on my mac. keeps saying "signature bugs unavailable" any ideas?
[Moto X Original Android Development] cmo220:
I had no problems at all on Verizon with Windows 8.1. Thanks!
[Moto X Original Android Development] dhoppy:
This won't be helpful to you, but I had the same error on windows. I was using "minimal adb and fastboot" to run adb. I can't say this for certain, but it seems that Impactor can't run without knowing where adb is. Once I added the path to adb to my "Path" in windows, Impactor began to work.
[Moto X Original Android Development] jcase:
are you on 4.4 or 4.2.2
[Moto X Original Android Development] erikwervo:
Hiya guys, sorry if this was asked before, but im trying to delete some root apps using root explorer. It was succeed. But when im rebooting the phone the deleted apps come back to the drawer. Why is that?

Im at rooted ota 4.4
[Moto X Original Android Development] bigv5150:
You can't delete system apps with just root you have to be in recovery side with wife permission for it to stick
[Moto X Original Android Development] TheDave1022:
Rooted just fine. Was on 4.2.2 rooted. Now on 4.4 rooted. Thanks
[Moto X Original Android Development] n1ckr0th:
4.4. missed the line saying to flash down first. thanks.
[Moto X Original Android Development] sfetaz:
Are system r/w functions not working properly? I have verizon and everything worked with the install. I install SuperSU, install binary successfully and reboot. Right after reboot I can use es file explorer to write a file to system, but then other things don't work like trying to install xposed 2.41 or busy box. I open SuperSU and it says again that binary needs to be updated. When I click normal this time it says installation failed, reboot and try again. I do that but it fails again. I can uninstall and reinstall SuperSU but then the process starts over again. For some reason I am losing system R/W access. Used 5c version.
[Moto X Original Android Development] jcase:
You have to be in recovery bootmode to write to system, see PwnMyMoto Thread
[Moto X Original Android Development] sfetaz:
Is recovery boot mode the reason why when I reboot to recovery it just boots to the ROM?
[Moto X Original Android Development] cmo220:
Yes
[Moto X Original Android Development] inneyeseakay:
I was on rooted 4.4 last night but seemed to have lost root with the recent supersu update... :/
[Moto X Original Android Development] Omen87:
Success. Thanks, Justin.
[Moto X Original Android Development] geekabilly:
Excellent work, went right the first time, bravo jcase!

Tapatalking Moto X on AT&T
[Moto X Original Android Development] StephenMilone:
mine updated and i'm fine.
[Moto X Original Android Development] sdxda:
So if were on pwnmymoto we should:

go back to stock after camera patch

then update to kitkat

then use slapmymoto?

how do we go back to stock from pwnmymoto?
[Moto X Original Android Development] MaddHatt3r:
No. If you read the OP and that is what you took from it, don't bother. Its not a run-n-done. If you did not read the OP, quit waisting our time.

Sent from my XT1060
[Moto X Original Android Development] sdxda:
I read the OP. I didn't mean to sound like it was an easy process. I was just talking about the first few steps. Haven't gotten further into the steps.
[Moto X Original Android Development] mistermojorizin:
i think the starting point needs to be an unrooted 4.2.2 with camera update. do whatever you need to do to get there. your post made it sound like the starting point is kitkat. but i agree with you, i read the op and every post in this thread many times and it's confusing as ****. no need for anyone to be rude.
[Moto X Original Android Development] eyc:
The process is difficult, but I really don't think the instructions are confusing as f***. This is the first step repeated verbatim:

Flash back to camera update. Be 100% stock. What don't you get?
[Moto X Original Android Development] mistermojorizin:
the implied assumption that you took kit kat before reading up on how to get root. and it's not that i don't get it, it's that i'm not sure my understanding is correct, because the assumption is unstated.

any more questions?
[Moto X Original Android Development] eyc:
Be on stock camera update.

Who cares if the post assumed you were on a non-stock version or on 4.4? Just be on stock camera update and get going. If someone's driving directions said "point your car north and begin driving on State street," then perhaps they are assuming you're not already pointing north. So what? Just point north and go.
[Moto X Original Android Development] mistermojorizin:
that's what i said! you really don't see the source of confusion for some people?

also, your attitude is all wrong here in how you're talking to me. i wasn't asking anyone for help. i've just been quietly reading the thread, trying to udnerstand it. the only reason i post, is cause some a-hole decided they need to mouth off to someone genuinely asking for help. I was just empathizing with the asker. this is not clear at all. easy way for it to be more clear "if you took kit kat, you need to do step 1. if you didn't, start at step x." And that was just one example.

You say it's difficult? it's not. It's just pushing buttons on a computer and phone. The problem is instructions don't clearly tell you when to push which button. the task itself is easy.
[Moto X Original Android Development] MaddHatt3r:
Don't mistake this for a rant or an attack, just getting it out there.

This process assumes a degree of 'able to figure some things out on your own.' It says you need to be on 4.2.2 camera update, stock version. Why would an individual flash to it if that's what they already have. It is not the job of this or any Dev to hold every users hand and write out a step by step for every scenario with diagrams and footnotes. If you don't know how to do something like flash an fxz or enable telnet, there are tools like the xda search tool and Google. If someone needs a picture book for every mod they want to do for their phone, this is the wrong hobby.

If, however, someone is trying to learn how to make something work such as communicating through adb or flashing an fxz and a search did not return any clear results, there is a Q and A forum for such questions. If you ask, someone will answer. I'm not against 'newbs' trying to get their teeth wet and being confused, we've all been there, but this thread's OP was as clear as he needed to be.

Sent from my XT1060
[Moto X Original Android Development] jcase:
This is right on.

This is a "beta" preview, as I knew I wouldn't have time to get a clean one built and tested for quite a while. However I knew it would work for those that took the time to play with it, and knew what they were doing. People got spoiled with the simplicity of PwnMyMoto. One clicks are a double edged sword, they save me time when they are possible, yet it does not allow the end user to learn the more advanced stuff.

Dunno, maybe I'll drop a Christmas gift or something to make this all simple again. Depends how generous I feel and how much time I have.
[Moto X Original Android Development] MaddHatt3r:
My personal feeling on this is that a method like what we have here is good for the community at large. In combines a few basic android dev operations, flashing fxz, setting up and using adb and fastboot. This was the first time I had used telnet, so I got to do a little learning in the process too. The resources are out there, and going out there to find them is part of the process. If one has no intention on learning a little something along the way, or isn't willing to take a chance, then what business do they have rooting in the first place.
[Moto X Original Android Development] stonesaber:
MaddHatt3r, I agree completely. I, also have never used telnet or heard of it before now. Took a little bit of searching and watching the video jcase has on his RockMyMoto thread and figured it out. I was not totally unfamiliar with adb, but now am a lot further along thanks to this. Sometimes it is frustrating to read the same ?'s over and over but it's unfortunately not gonna change.

I have to say that I am in awe of jcase and devs like him that can figure this out and put their work out there not expecting anything. It makes my brain hurt just thinking about how they figure this stuff out. So thanks for your hard work Justin, I really appreciate your time and trouble.
[Moto X Original Android Development] km8j:
Will this work on a non Dev VZW X on KK
[Moto X Original Android Development] matt99017d:
Sending bro love over. I love you man!
[Moto X Original Android Development] MaddHatt3r:
That's what its designed for.

Sent from my XT1060
[Moto X Original Android Development] Dark9781:
Well said. I've used telnet on many occasions so that was no big deal for me. Jcase's instructions were as clear as day. If you really don't know what you are doing or are uncomfortable with it then you really should steer clear of rooting. The exploits are getting few and between and will only keep getting more complicated as time goes on.
[Moto X Original Android Development] cincij:
Stuck at:

fastboot flash partition gpt.bin

fastboot flash motoboot motoboot.img

fastboot flash logo logo.bin

fastboot reboot

On the CMD screen:

<bootloader> Variable not supported!

target reported max download size of 805306368

error: cannot load 'gpt.bin': No error

On device screen:

getvar partition-type:partition

getvar max-download-size

Any thoughts?