yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] jimmiet:
When you "boot to recovery" and it "just boots up", you are actually booting with write protect off, which is essentially having root control. It doesn't boot into recovery because you have removed the stock recovery to allow writing to the system.
[Moto X Original Android Development] karthikmurs:
I did something really stupid. I forgot I had my phone rooted (I have 3 phones and I really forgot) and installed the OTA (Android Kitkat) and of course, I am stuck in a boot loop. Can I recover my phone? If so, how? Please help!

EDIT: So I got out of the boot loop (erased cache and userdata) but now, how can I undo the changed this exploit did? I mean, can I "unroot" it so to say?

EDIT2: Please ignore. Found it here http://xdaforums.com/showpost.php?p=45973206&postcount=276. Trying this.
[Moto X Original Android Development] Droidjava:
Thank you for the reply, That just made the light go on... lol... :good:
[Moto X Original Android Development] arbrouwer:
Does anyone know if this works with the Republic Wireless version of the Moto X?
[Moto X Original Android Development] Dark9781:
To get past the equation simply multiply the 2 known variables and that will be the answer to a.

Sent from my Moto X Rocking Kitkat
[Moto X Original Android Development] redhonker:
How do I stop OTA update after rooting?

And if I do want to update (the official ROM later), how do I do that? Un-root first? Or any non-OTA method?

Thanks
[Moto X Original Android Development] lowvolt1:
I'm going to assume you are on 4.2.2 because you posted in the RockMyMoto thread. If you freeze the Motorola OTA.apk you will not be prompted to update. If you want to update you will have to sbf back to stock using RSdlite. If you want to root 4.4 there is a SlapMyMoto thread on how to do that.

via my slapped KIT KAT moto X
[Moto X Original Android Development] jcase:
It does

Sent from my HTC Two
[Moto X Original Android Development] teh_lorax:
So I am unable to connect via telnet to the phone. It looks like everything works in Impactor. I don't have AP Isolation on my router. Turned the Windows firewall off (even though that shouldn't matter). Rebooted everything a couple times. Anything else I can try?

edit: For those having issues connecting via telnet, here's what I did. Just install a telnet client on the phone (I used the one from ClockworkMod). Connect to LOCALHOST on port 2222. Now run the commands as required.
[Moto X Original Android Development] DssTrainer:
I hate to always be "that guy" but these dev threads are consistently incomplete on the initial setup. I installed drivers (also not mentioned) and hook my moto x up to the usb and then do adb devices and nothing shows attached. Should I be in fastboot mode or some other mode? Do I need to unlock? Do I need a custom recovery?
[Moto X Original Android Development] teh_lorax:
Have you enabled USB debugging?
[Moto X Original Android Development] emmabellachristian:
so ive tried different ones slapmymoto and rockmymoto and cant get either one to work still saying link failed file exist. i ask again can anyone possibly inform me on what im doing wrong ?
[Moto X Original Android Development] DssTrainer:
I have now... this should really be stated

---------- Post added at 11:17 PM ---------- Previous post was at 11:09 PM ----------

I see more on this error here:

seems something with the way the sdk files are setup

http://www.thriveforums.org/forum/t...t/5383-link-failed-file-exists.html#post91866

---------- Post added at 11:36 PM ---------- Previous post was at 11:17 PM ----------

Worked perfectly for me once I had usb debugging enabled! Step by step by the book.. no issues!

Thanks!
[Moto X Original Android Development] lowvolt1:
Are you on 4.2.2 or 4.4?

via my slapped KIT KAT moto X
[Moto X Original Android Development] emmabellachristian:
i got it to work was stupid mistake i did its worked now.
[Moto X Original Android Development] rockingondrums:
How else would you expect the Android Debugging Bridge to work on your phone? It does it over USB (some apps also do it over wifi, but I've never tried). It's also something that developers use, so naturally it's something you'll need to turn on in the Developer Options. You need to authorize it because someone with knowledge of ADB could completely get around any security you have on your phone if they were to find/steal it (caveat: not sure about full device encryption, but not many people do that).

I hate vague or incomplete OPs as much as the next guy, and sometimes I completely avoid using a mod/whatever if the OP is a mess (and if I can't find an answer in the thread by searching/reading. Also why I hate excessive OT in threads). And maybe this is your very first Android phone. But ADB has been around for awhile, so a few Google searches on ADB would have turned up a lot of info. And unfortunately, spending time to research statements whether they are vague/misleading or that you just don't understand is going to be a part of your Android modding life. I'm just saying.

To share some information that I only recently learned: Google made changes in JB about the way adb devices show up. I wrestled for a few minutes with my device serial showing but being offline. Simply toggling the USB connection mode from whatever state it was in to Camera made it show right up in ADB. I don't know why, but I'm sure it's related to the wonky behavior of MTP. And I'm typing this here so that the next person who does a google or xda search for "adb device offline" may find it and use it. :good:

Now, regarding the OP. Yes, rooting voids warranties. But if I don't ever get a bootloader unlock code, Moto will never know right? From what I understand skimming over some of these pages, the stock recovery is removed to give us the ability to gain write access? So when selecting to boot to recovery from bootloader, it loads the OS without the write protection. So if I have to return my device, I naturally need to restore a recovery.img and remove traces of su. Someone said earlier using SuperSU's built-in su removal didn't work. I'm guessing I'll have to use RSDLite to flash to stock? Does the Moto X have system equivalent to Samsung's flash counter / HTC's "tampered" flag in hboot?
[Moto X Original Android Development] matt99017d:
Yes Motorola does have a tampered counter.

In the bootloader screen it should show something like Q/E 1 or 0 or something....
[Moto X Original Android Development] redhonker:
My phone will arrive tomorrow. Is there a need to check for build number first? Or should I wait for the OTA update first (if any)?

Thanks
[Moto X Original Android Development] atrix_noob:
I have a problem, do i need to press Power and volume down button to get and select Bp Tools? Thats the only way i can get usb debbuging to appear has i see no option in settings menu

edit: succesfully done without errors thanks everyone.
[Moto X Original Android Development] d14gvn:
this needs unlocked bootloader?
[Moto X Original Android Development] h1ghland3r:
No.
[Moto X Original Android Development] dtrud0h:
No. Go to settings on phone, then about phone, then tap the build number like 15 times or so and it will tell you you are a developer. Then go back to settings and you'll see developer options.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] atrix_noob:
It doen't need unlock bootloader
[Moto X Original Android Development] MaKTaiL:
Why does this void warranty? Can't I just flash stock ROM back?

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] Nixal:
Successful root, but /system write return 1:

adb shell getprop ro.boot.write_protect

1

how to solve ?
[Moto X Original Android Development] MaKTaiL:
Reboot into recovery.

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

If this voids warranty, what is the point of using it if I can instead unlock bootloader and make a much more easier process?
[Moto X Original Android Development] Nixal:
Ty, work now =D
[Moto X Original Android Development] tcollum:
There isn't one. Unlock it.
[Moto X Original Android Development] MaKTaiL:
There isn't what?

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] tcollum:
There isn't a point in using this if you are able to unlock your bootloader.
[Moto X Original Android Development] MaKTaiL:
I will lose warranty either way right?

So I think I will unlock it then. :)

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] Dark9781:
For Dev editions you no longer lose your warranty when you unlock. As for root check Moto disabled it once you get Kitkat. In Kitkat q/e always reads 1/1 regardless if you rooted or never rooted the phone.
[Moto X Original Android Development] Arsonik77:
So I've tried everything and I've looked through several forums, but I continue getting an error. Everything is fine until I attempt to run the exploit through telnet. I get this:

In my research I found people that supposedly found a solution but their methods didn't work for me. Any help would be appreciated.
[Moto X Original Android Development] hawkdown77:
Im on 139.12.35 brazilian moto x.

Can i use this to root??

Thanks

Enviado de meu XT1058
[Moto X Original Android Development] rockingondrums:
Oops wrong thread.
[Moto X Original Android Development] dobbs3x:
This happening to me. Can't get super su to install. Says I'm not rooted. Tried to boot into recovery but it didn't fix anything.
[Moto X Original Android Development] mistoffelees:
Success

Sweet! Got my new VZW MotoX today. It was already at 4.4, but I was able to downgrade to 4.2 and then followed the instructions to gain root. Downloading the 4.4 OTA again now.
[Moto X Original Android Development] lowvolt1:
Followed what instructions to gain root? Rockmymoto? If so you will bootloop on OTA.

via my slapped KIT KAT moto X
[Moto X Original Android Development] 0utkast:
Hi guys , i done as it instructed but weird thing for me , my phone skipped part 2 and on telnet had part 3 on the second time i runned it. I still don't have SU permisions though . Sprint Moto X bootloader unlcoked . Anyone can help?
[Moto X Original Android Development] lowvolt1:
If your boot loader is unlocked why are you using this exploit? Just flash TWRP. and supersu.

via my slapped KIT KAT moto X
[Moto X Original Android Development] 0utkast:
lol , and i've rooted so many of my phones and i have no idea why that didn't cross my mind . All good now :)

now all i need is someone to figure out to sim unlock the sprint version.
[Moto X Original Android Development] Acturbo:
Man that was a lot more work than usual, takes me back to when I first rooted the Droid 1 when it first came out. Thanks for all the work put in, will be sending a few bux your way :D.
[Moto X Original Android Development] h1ghland3r:
Prepare yourself to SlapMyMoto (KitKat). This is really more work than usual ^_^
[Moto X Original Android Development] core720:
i =
[Moto X Original Android Development] boffster99:
no recovery?

i've rooted with rockmymoto. then tried to get back to stock using rsdlite. the phone boots up and updates and acts like it should except when i try to boot into recovery i get the broken android. su says there is no root. how do i return recovery back to stock?

droid maxx 12.15.15 obake-maxx

any help appreciated.
[Moto X Original Android Development] core720:
Solution????

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Original Android Development] shane1:
Wait for the next exploit update
[Moto X Original Android Development] erikcave:
Is there a safe route to stock 4.4 using this method? 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?
[Moto X Original Android Development] core720:
Really?

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Original Android Development] tluley51:
herp derp, delete
[Moto X Original Android Development] stillthisguy:
Use SlapMyMoto
[Moto X Original Android Development] cvhovey:
After unboxing and activating my X, right away I could see the OTA was starting to download, so quickly began the root process. Hit roadblocks at first so had to turn off Windows (7) Firewall & disable Microsoft Security Essentials in order for Cydia to connect. After that, it was 'just follow the directions' and boom, phone rooted. Reminds me of way back before the previous Ice Age when had to manually root the OG Droid, tho this was fewer steps. As soon as rooted, downloaded TiBu and Root Explorer, froze Motorola OTA and Updater, then went to /cache and deleted the OTA file.
[Moto X Original Android Development] snofrandy:
I get stuck in # start telnetd as system on port 2222

I get "signature bugs unavailable" even if I accept "app may be dangerous" from Google Play. Any ideas? I even disabled Windows Firewall
[Moto X Original Android Development] cmelby:
Hard, long road, but finally got it rooted. Some problems mentioned.

God, that was confusing, but after a lot of searching around and mistakes it finally worked. Tough for someone who doesn't know from adb and sdk to "figure out how to install those, just look around."

Problems I had:

The sdk installed was for 4.4. Don't know if that was an issue. I deleted that sdk and installed 4.2.2, guessing that would fit better with the 15.15 version.

My phone plugged in to the USB port had only about 30 seconds of being seen by adb before going AWOL. Before every step of the procedure I had to unplug then replug in my phone to USB port.

The automatic reboot after the second run of exploit didn't happen. I had to go into adb and adb reboot.

The command to check if rooted in adb never did work. The Root Checker Basic app from Google Play Store told me when it was rooted.

Other than that, thanks very much to all for all the hard work of developing these tools and 90% explaining them. Much appreciated.
[Moto X Original Android Development] havi007:
what was your mistake I am running into the same thing. I tried everything.
[Moto X Original Android Development] sp47:
Please type a whole number as your answer:

2231

Correct!...Rebooting now...

Please run: 'adb reboot', then re-run RockMyMoto

~ $ adb reboot

sh: adb: Permission denied

~ $

what's the problem? cannot follow further steps.
[Moto X Original Android Development] sebadamus:
Thanks, it works perfect on my Moto X 4.2.2 (it is camera patched, too)

Just have to follow the youtube video to get a clearer understanding of the process :good::good::laugh:
[Moto X Original Android Development] schufly:
I am having this problem too, anyone have an answer?
[Moto X Original Android Development] Dark9781:
Are you on 4.2.2?

Sent from my Moto X on KitKat
[Moto X Original Android Development] schufly:
No, I am on 4.4
[Moto X Original Android Development] snofrandy:
That was the problem! when I downgraded to 4.2.2, it fixed it and Impactor ran as it's supposed to
[Moto X Original Android Development] Dark9781:
That's your problem. You need to be on 4.2.2. There is no known exploit for 4.4. I recommend using SlapMyMoto to root.

Sent from my Moto X on KitKat
[Moto X Original Android Development] schufly:
I can't currently get my phone to downgrade. really weird.
[Moto X Original Android Development] ijeenyus:
Edit: found solution
[Moto X Original Android Development] markwebb:
What was it?
[Moto X Original Android Development] LeonKnight12:
signture bug unavailable

I'm on 4.4 and the progress goes until this point where cydia impactor is and warning sign comes up says "Signture bug unavailable" and can't do anything.
[Moto X Original Android Development] Dark9781:
You need to be on 4.2.2. There is no known exploit for 4.4. I recommend using SlapMyMoto so you can return to 4.4 with root.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
ok, from my experience , you can't down grade android.. so, ur saying you need to be on 4.2.2 but i'm on 4.4.. how to go i get back onto 4.2.2? and if i'm on 4.4 would that explain why the "adb shell getprop dhcp.wlan0.ipaddress" command wouldn't give me my ipaddress?
[Moto X Original Android Development] Dark9781:
Normally you can't downgrade with android because of security reasons, but with 4.4 Moto allows you to downgrade. You simply need to flash the 4.2.2 OTA camera update via RSDLite or manually through fastboot and then root. If you can't get your IP address by running the adb command then you can go to settings>about phone>status and scroll down to IP address.
[Moto X Original Android Development] LeonKnight12:
I manged to downgrade from 4.4 to 4.2.2 moto firmware file download. and yet I'm not getting ip adress show up in cmd is weird. I followed the steps
[Moto X Original Android Development] xpsychox:
I fallowed the steps too but it took the command but it just went to the next line like nothing happen..
[Moto X Original Android Development] LeonKnight12:
upon telnet I manged to run the exploit through telnet using this

dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto

it doesn't say adb reboot and have to answer question WTF?

Edit: solved
[Moto X Original Android Development] xpsychox:
How'd u solve it? I'm trying to figure out how to pit 4.2.2 on it then put 4.4 back on..ideas?
[Moto X Original Android Development] LeonKnight12:
if you are rooted on camera update and write protection off and flash back to 4.2.2 camera update again and do slapmymoto process. The process I was having has been hard time going through and made it to 4.4 rooted.
[Moto X Original Android Development] dazz1996:
Dazz1996

Thanks Jcase for making this happen by giving us root.

I have a question for anyone that can answer it. I rooted my MotoX Verizon with this method but for the life of me I can't get Xposed install to work. After installing it and rebooting I get force close/crash android system. I tried booting into recovery/install Xposed framework/shut down the phone/boot recovery again/still the same problem. Thanks if anyone can help

sorry wrong thread
[Moto X Original Android Development] xpsychox:
ok, I got the root to work, then the directions say to go ahead with OTA update, I downloaded it clicked install, and now my phone keeps restarting very 20-30 seconds? Did I do something wrong?

Rsd'd it back to stock 4.2.2 and redid the root process and took the 4.4 update, clicked install...samething.. what am I doing wrong?
[Moto X Original Android Development] gmmurphy:
got through 2 telnet sessions, cannont reconnect to run third time. refusing connection. any help would be greatly appreciated
[Moto X Original Android Development] xpsychox:
I had to connect my phone to WiFi...was urs? Also, check ur antivirus.. What r u using?
[Moto X Original Android Development] gmmurphy:
yes connected to wifi, no antivirus. winxp. tried putty and impactor. worked great for the first to commands now cannot connect via telnet.
[Moto X Original Android Development] xpsychox:
So u can't do telnet at all?
[Moto X Original Android Development] gmmurphy:
nope, network error connection refused
[Moto X Original Android Development] xpsychox:
It actually does stay to use adb reboot the first time...the dalvkvm command is to b ran after ur connected to ur phone..also the telnet command must b enabled for it to work.. U can Google it..its not hard to enable...as my previous post states.. I did it twice last night but after I kept rebooting..

---------- Post added at 01:41 AM ---------- Previous post was at 01:40 AM ----------

I figured this out last night..telnet must b enabled on ur PC to use command.. Google it..its a quick setting change and a MUST reboot.
[Moto X Original Android Development] gmmurphy:
im using putty and/or impactor, worked first two sessions now i get network error. rebooted, laptop, phone, router. flushed ip im out of thoughts.
[Moto X Original Android Development] xpsychox:
I don't know what putty was.. i followed these instructions. http://xdaforums.com/showthread.php?t=2509590 and http://xdaforums.com/showthread.php?t=2538896

i also used this to help me set up adb in command prompt. http://www.youtube.com/watch?v=Khrxo0-NieM
[Moto X Original Android Development] gmmurphy:
thanks, if i can get the last step to take, install supersu from market. now i want to update to kitkat. can i go from here to slapmymoto to upgrade to kit kat.

---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------

i got telnet back, cant get past step two. says will reboot now but does not. so close but yet so far.
[Moto X Original Android Development] xpsychox:
try to open a new command prompt and type adb reboot.. see if that helps..

lemme know what happens after ur 4.4 update.
[Moto X Original Android Development] gmmurphy:
i got telnet back, cant get past step two. says will reboot now but does not. so close but yet so far.
[Moto X Original Android Development] xpsychox:
try to make it--adb reboot
[Moto X Original Android Development] gmmurphy:
tried adb reboot, it rebooted however running command in telnet results are the same running step two. wow i feel like a dummy, i have rooted so many devices im at a loss.
[Moto X Original Android Development] xpsychox:
don't feel bad.. when it reboots the first time, are you re-running impactor to run on port 2222?
[Moto X Original Android Development] gmmurphy:
yes, i tried to start from the beginning, but stuck on step two.
[Moto X Original Android Development] xpsychox:
that's weird... err... try to manually reboot the phone, hold power down button, for some reason, i remember seeing that you could do that.. i think? worth a shot.
[Moto X Original Android Development] gmmurphy:
each time it reboots, do i have to start another telnet session? seems no way to enter commands unless a new session starts
[Moto X Original Android Development] xpsychox:
yes, you must restart telenet on port 2222, THEN you go back to command prompt, it'll say "lost connection" just re-type "telnet **ipaddress** 2222" then the dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto command and it'll reboot... then do the same thing AGAIN..
[Moto X Original Android Development] gmmurphy:
This is exactly the steps i am taking, however the cmd window for impactor does not say lost connection, "press enter to close" so I start another session on 2222 open shell enter the command and I get executing step 2, device will reboot. Does not reboot, I tried manual boot, adb boot. each time. each time I try i get the same thing. Its gotta be something stupid im missing. Thanks for all help.
[Moto X Original Android Development] user1484:
You are still connected to telnet.

Type exit, hit enter (to disconnect from telnet), then run adb reboot.
[Moto X Original Android Development] GloriousDJ:
For those who ran into this problem

just skip to SlapMyMoto
[Moto X Original Android Development] koocheese:
Just an FYI for fellow Rogers Moto X XT1058 users out there.

I read most of this 25+ pg thread and couldn't find confirmation, this root method WORKS for our 4.2.2 camera updated phones.

Super easy to do.

Now if they will get off their asses and release kitkat for us, that'd be great.
[Moto X Original Android Development] Android.Junkii:
Thanks!! Worked like a charm...though, not at first. Had networking issues with the whole "AP iso" thing. FIX: Cydia Impact > Download telnet app on phone and perform commands. I suppose this could be done from phone entirely; with file manager, term emulator, telnet, archiver app from playstore. GOOD STUFF :good:
[Moto X Original Android Development] hawkdown77:
When we use the rockmymoto....we lost the Android recovery??

Enviado de meu XT1058 usando o Tapatalk 2
[Moto X Original Android Development] DanRo80:
NEVER MIND, I finally was able to get ADB to work. I simply didn't have the WiFi activated on the phone.

What files are you talking about that you copied? Like this for instance? RockMyMoto.jar /sdcard/

Because I can't for the life of me get ADB to see my device using a Windows 8.1 machine.