yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] lordloki77:
Root 4.2.2 or upgrade to 4.4, then root

Hi all,

If I am still on 4.2.2, should I just root that version, or should I just OTA to 4.4 and then root that?

Thanks in advance!
[Moto X Original Android Development] lowvolt1:
Yes

via my slapped KIT KAT moto X

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

The only suggestion I have is to flash a clean 4.2.2 camera update and start over.

via my slapped KIT KAT moto X

---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------

That totally depends on what you want. If you want 4.4, do that. If your happy with 4.2.2, then do that.

via my slapped KIT KAT moto X
[Moto X Original Android Development] lordloki77:
No stock rooted rom to just flash to after rooting and unlocking on 4.2.2 (have the dev edition)? Used to doing this with my Galaxy Nexus -- As a rule, I never take OTAs, I just upgrade using CWM.
[Moto X Original Android Development] shane1:
Make sure to delete the get.var line in the XML and use the proper fastboot
[Moto X Original Android Development] lowvolt1:
If you have Dev. Edition I would definitely update and root. If you don't like OTA's search for a ROM.

via my slapped KIT KAT moto X

---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------

I think poster was referring to the adb commands. It looks like they have already flashed back to 4.2.2. Or would the get.var need to be removed anyway? Even if pushing individual commands?

via my slapped KIT KAT moto X
[Moto X Original Android Development] shane1:
Yeah I missed that lol are all the parts your flashing in your fastboot folder?
[Moto X Original Android Development] Infekxion:
Might want to see if you can RSD before anything else, that was the last thing I seen and now I cant boot. I'd wait for Jcase to give his opinion.

Sent from my Hammerhead
[Moto X Original Android Development] lowvolt1:
Can you get into fast boot?

via my slapped KIT KAT moto X
[Moto X Original Android Development] cincij:
I can get to fastboot ok.
[Moto X Original Android Development] lowvolt1:
Have you tried to flash back to 4.2.2

Remembering to remove the get.var line

via my slapped KIT KAT moto X
[Moto X Original Android Development] cincij:
Trying to avoid that. I'm sure I removed the get.var line the first time, and I'm stuck at home with slow as$ internet connection and my RSD file is at work.
[Moto X Original Android Development] Infekxion:
I can't, jcase and myself (well mostly him) have been trying to get it to respond.

Sent from my Hammerhead
[Moto X Original Android Development] lordloki77:
Per your suggestion, I updated to 4.4 but now think I need to downgrade....

When I try to start telnet I get an error that says no signature verification bugs available or something like that.... Do I need to downgrade now?

Is there a more straight forward guide? Getting stuck at step one and I have been doing this for years.
[Moto X Original Android Development] lowvolt1:
For slapmymoto. You need to start on 4.2.2 clean 100% stock. Depending on your version of windows telnet may not be the best solution. I used puttytel and it worked great for me. Also you will need cydia impactor. And to know what your phones IP address is.

via my slapped KIT KAT moto X
[Moto X Original Android Development] emmabellachristian:
im confused as heck. every time i try the steps the first step with cydia impactor it goes thru steps says waiting to complete and then it says link failed file exist
[Moto X Original Android Development] MaddHatt3r:
Make sure your telnet client is enabled in windows. Go to control panel/programs/turn windows features on/off. Scroll until you find telnet client.

Sent from my XT1060
[Moto X Original Android Development] lowvolt1:
When I rooted with Rockmymoto, I had no problem at all with impactor. When I rooted with slapmymoto. I had some issues with impactor. I am not saying that the different root methods are the cause. That would be ludacris. I did however notice that on the phone I had to unlock it and authorize something. Seemed like after that impactor worked fine.

via my slapped KIT KAT moto X
[Moto X Original Android Development] lordloki77:
thanks......................... (why did you tell me to update to 4.4 then?)

Anyway, I have flashed back to 4.2.2.

But now, after running Cydia Impactor (and it seems to be working), I get this error:

Connecting To 192.168.1.128...Could not open connection to the host, on port 2222: Connect failed

Any suggestions?
[Moto X Original Android Development] gitku:
Make sure PC and phone are on the same WiFi network
[Moto X Original Android Development] lordloki77:
Heh ... thanks. That wasn't actually the problem. I had misidentified the android device IP -- I have a few on my network. Once I got that, everything went swimmingly.

So I have fixed this error - issue was wrong IP address.

Only question remaining now (I have gotten the device rooted) is this:

If I try to reboot into recovery, it just boots normally -- I can't actually get to a recovery screen (happens both if I ADB reboot bootloader and select to go to recovery and if I ADB reboot recovery -- this is obviously not ideal.... Okay for the moment, but I want to be able to reboot into recovery if something goes wrong.,,, Ideas?

Related question for those with the dev editions: if I unlock, will running the oem unlock command require that I redo the entire rooting thing? or will I stay rooted after it unlocks?

Thanks everyone for the awesome community support!

:)
[Moto X Original Android Development] lowvolt1:
Well........I'm not sure I told you to update. I said if your on Dev.edition I would definitely update and root. You took the ball and ran without reading how to do so.

via my slapped KIT KAT moto X
[Moto X Original Android Development] sorullo_xgrx:
This method only gives you Root privileges, it does not install a custom recovery. Trying to boot into recovery will boot you normally .
[Moto X Original Android Development] lordloki77:
I was asking for advice because the directions were unclear to me. You didn't bother to warn me. No matter.

Either way, I have now completed the root.

Thanks!

---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------

Yeah, it occurred to me after I posted that that perhaps this was intended behavior... Thanks!

So then the question becomes -- is there a better way to do this if I have unlock privileges with the Dev Edition? Ideally, I would like a fully-rooted STOCK 4.4 rom for now, with full access to CWM/TWRP.

Anyone?
[Moto X Original Android Development] sorullo_xgrx:
Only Dev phones have unlock bootloaders. Is because you use fastboot commands to install custom recoveries. Lock bootloaders no way to install custom recovery
[Moto X Original Android Development] somerandomname1:
If you have a Dev edition phone you completely wasted your time with SlapMyMoto. You can unlock bootloader and install custom recovery/root. You did SlapMyMoto when what you really wanted to do only takes about 5 minutes.
[Moto X Original Android Development] lordloki77:
I know I can unlock the bootloader directly. I know I can install custom recovery. I know I could install a custom pre-rooted rom. However, to my knowledge, that doesn't actually enable me to do what I want, which is to be on STOCK 4.4 (rooted). Simply having an unlocked bootloader and custom recovery doesn't all of a sudden give you root on a stock rom - for instance, if you have an unlocked Galaxy Nexus, you still had to actively root it if you wanted root privileges -- and this required an exploit. Clearly all of the above can be avoided if you can flash a pre-rooted rom, but I don't see on for the VZW Moto X based on 4.4 stock.

Can someone let me know if I am missing something here? It's entirely possible! :)

Thanks!!
[Moto X Original Android Development] tonyf7:
I'm also curious about this. I'm about to get the VZW DevEdition Moto X. Also, I'm totally clueless and and confused about all this adb and telnet stuff. Is there a detailed "explain it to me like I'm 4 years old" guide for unlocking bootloader and rooting the X? Basically, all I want it is to keep the stock rom but be able to flash GravityBox for all of its bells and whistles.
[Moto X Original Android Development] somerandomname1:
Once you have a custom recovery you can flash super user. Then you're rooted on stock. No exploit needed.
[Moto X Original Android Development] lordloki77:
Tony, unless I find a method to do the bootloader, I am happy to help walk you through the process of rooting the VZW DE Moto X and installing xposed and gravity. Will revert back to this forum if I find somewhere how to root 4.4 without doing all of this work (with an unlocked bootloader).

Cheers,

lordloki
[Moto X Original Android Development] sorullo_xgrx:
Let me know too . good luck :beer:
[Moto X Original Android Development] lordloki77:
"flash" super user doesn't mean anything. flash which zip file? to where? /system/bin? just the su binary? superuser.apk?

Can you be more specific?

Is this the zip you would suggest flashing? http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
[Moto X Original Android Development] tonyf7:
:cyclops:Thank you lordloki! I and many other X users would be indebted to you if you somehow found a kindergarten method for rooting the X. Unlocking the bootloader seems totally doable after reading through Motorola's website. I just need to know what to do next, specifically: 1) How to root and 2) How to install xposed and Gravity.
[Moto X Original Android Development] somerandomname1:
Here: http://xdaforums.com/showthread.php?t=2536200
[Moto X Original Android Development] bozbeast:
After I install the 4.4 update both through the phone or rds lite with getvar removed

Everything goes great until I get to step 5

First is gpt.bin:

c:\android>fastboot flash par

(bootloader) Variable not sup

target reported max download

sending 'parition' (32 KB)...

OKAY [ 0.248s]

writing 'parition'...

(bootloader) Permission denie

FAILED (remote failure)

finished. total time: 0.349s

Next is motoboot.img

c:\android>fastboot flash motoboot motoboot.img

(bootloader) Variable not supported!

target reported max download size of 805306368 bytes

sending 'motoboot' (1588 KB)...

OKAY [ 0.363s]

writing 'motoboot'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 1.083s

After that is the logo.bin

c:\android>fastboot flash logo logo.bin

(bootloader) Variable not supported!

target reported max download size of 805306368 bytes

sending 'logo' (2563 KB)...

OKAY [ 0.445s]

writing 'logo'...

OKAY [ 0.982s]

finished. total time: 1.429s

The log seems okay though at first it declares the variable as unsupported.

Is this fine or do I need to tweak something before continuing?
[Moto X Original Android Development] matt99017d:
Success!!!!!
[Moto X Original Android Development] lordloki77:
thanks!! will try :)
[Moto X Original Android Development] Coderedpl:
Did this on my wifes Moto-X and everything seems to be working fine.

I couldn't toggle bluetooth since it restarted almost immediately but it seems to work without issue. R/W and Root.
[Moto X Original Android Development] shawnbon206:
It is unclear wether I am supposed to do this twice for stage 2.
[Moto X Original Android Development] eyc:
Three time total.
[Moto X Original Android Development] shawnbon206:
Okay thanks. That second step obviously needs to be rewritten :)
[Moto X Original Android Development] shane1:
The directions are quite clear
[Moto X Original Android Development] jayboyyyy:
i can't agree with that. the directions state to run the stage two command twice (kind of). That would give you a total of running that command four times. The only way to reconcile the two sentences stated in regards to stage two would be to assume that the first sentence is telling you what you are about to do and the second sentence is telling you to actually do it. It doesn't really matter at this point because the question has been answered, but i can easily see how it is confusing.
[Moto X Original Android Development] SYNSYNACKACK:
Success with Verizon phone. Thanks jcase !

---------- Post added at 04:42 PM ---------- Previous post was at 04:35 PM ----------

Assuming you got this figured out by now.

I received a similar error, then realized I didn't have the SlapMyMoto and the VZW files in one folder.
[Moto X Original Android Development] ericizzy1:
at first try i had heating and battery draining fast issues, no one has heating and fast battery issues? if not, will try this again...
[Moto X Original Android Development] shawnbon206:
Exactly. Thanks for the backup. For the record, I never said it wasnt an easy method (it was quite easy), but it would be foolish to say that particular step was clearly written. Any native english speaker who is educated can see it is not. BTW, dont feed the trolls :)
[Moto X Original Android Development] mercado79:
Happened to me. Rogue app, though I think it was caused by restoring settings via Titanium Backup. At the very least, uninstall (then reinstall without restoring settings) any apps you see behaving strangely in the battery stats area.

Sent from my Moto X
[Moto X Original Android Development] ericizzy1:
which app was causing this for you?
[Moto X Original Android Development] mercado79:
Can't remember. Think it was All in One Agenda Widget. Honestly, I think if we were able to run Fix Permissions after this, it'd solve many problems. Anyone know if that's possible without a proper custom recovery?

Sent from my Moto X
[Moto X Original Android Development] shane1:
You can fix permissions with ROM toolbox
[Moto X Original Android Development] Dark9781:
Grab AppOps 4.3/4.4 from the play store. It allows you to toggle permissions on an app by app basis. This was something that was added natively to 4.3, but was hidden. It was removed from 4.4, but this will restore it. Was able to stop some battery drain by toggling off wake lock. Here is a link below.

https://play.google.com/store/apps/details?id=com.colortiger.appopsinstaller&hl=en
[Moto X Original Android Development] devaughnaw:
I'd really appreciate it if you did. I'd definitely give a nice donation.
[Moto X Original Android Development] lowvolt1:
I just re-read the OP. the first time I read through it to root I totally missed it. I guess this was a good lesson in seeing who legitimately read the OP, and who just skimmed it and looked at the pictures.:D

via my slapped KIT KAT moto X
[Moto X Original Android Development] emmabellachristian:
dunno if you were refering to me but if u were the answer is it is turned on/ enabled
[Moto X Original Android Development] geekabilly:
Is your cmd session in the directory where the 3 files are? If not, then cd there and try again
[Moto X Original Android Development] bozbeast:
starting from the top and re installing everything

got it
[Moto X Original Android Development] tluley51:
I cant even get into stock recovery. I was previously rooted and rommed with custom recovery, but unrooted and went back to stock for 4.4. Now I am trying to flash 4.2.2 to get this started and I can't even get into stock recovery. I select it in fastboot and it just comes up to a screen with Andy the Android on his back and it says "no command". Any ideas?
[Moto X Original Android Development] imTousey:
So as of yesterday I apparently don't have root access anymore, but xposed modules and titanium still work fine. Any new apps that require root will not work. Do I have to downgrade again to re-root myself and fix this? Anyone else had this issue?
[Moto X Original Android Development] bozbeast:
Are you just doing adb reboot bootloader, then rds lite flashing 4.2.2?
[Moto X Original Android Development] Sharkeyd:
Try booting into recovery, which will just take you to your home screen, and updating supersu
[Moto X Original Android Development] AdhvanIt:
You're actually missing quite a lot. The sole purpose of unlocking a bootloader is to flash the recovery partition. Once that's done, there's nothing to rooting.

Step 1: unlock boot loader

Step 2: flash desired recovery (via fastboot)

Step 3: flash the super su zip found in this thread (via whichever recovery you flashed) http://xdaforums.com/showthread.php?p=23427715

Step 4: Reboot.

You're done. That's all there is to rooting a dev edition device. Exploits bypass a locked system or bootloader. Neither of these are locked on DE devices.

Hopefully this made it a little more clear.
[Moto X Original Android Development] TheWhiteChallenger:
ok got a little confused right here by "normal", were talking about flashing thie 4.2.2 camera update files from the fzx correct?
[Moto X Original Android Development] MaddHatt3r:
Yes, copy those .bin and .IMG files from the 4.2.2 fxz to where your fastboot file is.

Sent from my XT1060
[Moto X Original Android Development] TheWhiteChallenger:
cool thanks thats what i thought i just didnt want to screw up

---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------

oh but here is another likly stupid question, what is the purpose of reflashing the logo/bin? isnt that just the image at frist boot?
[Moto X Original Android Development] willverduzco:
Amazing work, as always jcase. I've posted this to the Portal and our G+ page :)
[Moto X Original Android Development] dicarli:
The "Claro Brazil" file on that list is corrupted, which is exactly mine (WHY GOD?!).
[Moto X Original Android Development] Rhiannon224:
Will this work on the T Mobile version?
[Moto X Original Android Development] NoNotReally:
So if I let my new stock Verizon Moto X get the OTA can I use this afterwards?
[Moto X Original Android Development] spiral777:
Should have called it pimpmymoto :)
[Moto X Original Android Development] StephenMilone:
PimpSlapMyMoto
[Moto X Original Android Development] jcase:
Should work on those variants, but they are unlockable and unlocking your bootloader no longer voids your warranty with motorola, so no point in me supporting it
[Moto X Original Android Development] a1exus:
[MENTION=2376614]jcase[/MENTION] isn't that only applies for developer edition phones?
[Moto X Original Android Development] Zero_FeniX:
Verizon has developers editions because they don't allow you to unlock their consumer phones. T-Mobile on the other hand does. unless you're talking about the reinstation of warranties, on that subject I do not know.
[Moto X Original Android Development] a1exus:
I see.. I didn't know that) I'm on Verizon non-DE((
[Moto X Original Android Development] jcase:
I need a technically adapt person, on Verizon or AT&T who wants to walk through this process and help me debug it more. I'm on freenode in the #MotoX channel
[Moto X Original Android Development] mkinney88:
Thanks [MENTION=2376614]jcase[/MENTION] your the man. Now maybe if you figured out the boot loader you can collect some good amount of money.
[Moto X Original Android Development] graffixnyc:
[MENTION=2376614]jcase[/MENTION] I couldn't get it working after using Alpha to get WP off. After we got WP off on IRC and I tried pushing the files I lost root. Also the part to push recovery.sh didn't boot the bootloader. It just booted into Android again. I also tried starting over from scratch(4.2.2) and no dice. I'm not home so I can't do any testing but something screwed up. After that time I tried another 2 or 3 times afterwards from scratch and got the same result every time.
[Moto X Original Android Development] jcase:
Yeah, bug existed after the alpha that prevented the backdoor from being installed. Fixed now, testing and will re-upload a more reliable version.
[Moto X Original Android Development] matt99017d:
Will this ever be as simple as your first .apk method?
[Moto X Original Android Development] Sinderan:
Most root methods aren't that simple. And as they fix the vulnerabilities it requires more complex exploits
[Moto X Original Android Development] jcase:
Not likely, that was a series of lucky breaks. Less lucky here
[Moto X Original Android Development] Rebel908:
How adept are we talking? Like being able take the commands you give into adb or (presumably) more advanced than that?
[Moto X Original Android Development] BrokenWall:
SlapMyMoto 0.4.1 worked for me, Fully rooted on KitKat
[Moto X Original Android Development] ericizzy1:
Anyone on Verizon?
[Moto X Original Android Development] mercado79:
Yeah, I just wish I could do all apps at once. Unless I missed something, ROM Toolbox makes you do it one app at a time.

Thanks for that tip, but I meant the Fix Permissions option that you find in custom recoveries like CWM or TWRP.

Sent from my Moto X
[Moto X Original Android Development] Corvida:
If you're getting the permission denied error in step 7, you'll more than likely need to start over from 4.2.2 using RSD Lite and fastboot, but everything should work after that!

I didn't get a chance to toggle BT on the first command, but did manage to toggle it on the second command. You need to have BT enabled and up on the Moto X's screen as you're entering the echo command on your comp to toggle before the reboot.

Thanks to [MENTION=2376614]jcase[/MENTION] for the help!
[Moto X Original Android Development] mordakk:
I'm on new phone, verizon, 4.4. Is there a new version of this root coming out? Or should I just go ahead and do it now?
[Moto X Original Android Development] GandalfTehGray:
Had several troubles trying to get this up and running over 3 days :P If anyone wants to read them http://xdaforums.com/showthread.php?p=48047953#post48047953 Finally got it working and am very happy.

Thank you Jcase for this method as I really needed root.
[Moto X Original Android Development] mrjoshzombie:
I jumped back about 4-5 pages and didn't see anything relevant, but is anyone else here randomly loosing root about mid-way through the day?

I have no exact time frame, but occasionally TiBa, AdAway, ES File explorer, etc won't be able to access root. I'll attempt to open SuperSu but nothing happens at all. Once I reboot, everything is fine and working again (including the ability to open SuperSu).
[Moto X Original Android Development] eyc:
I actually noticed this for the first time today. My experience was slightly different. I was trying to install Xposed, and I kept getting the message that the system was read-only. I opened SuperSu, only to find that it would not install binaries and would automatically close. I had to restart the phone for it to work again.
[Moto X Original Android Development] Sharkeyd:
Reboot into recovery and update super su binaries.
[Moto X Original Android Development] eyc:
For fear of sounding like an idiot, I thought of not asking this, but, here goes: How do you do that? I can't seem to get into recovery properly. I shut the phone down, then press PWR+VOL Down and get into the fastboot screen. Click down to recovery, click up to select, and then it just restarts. I try jamming VOL Up and PWR, but nothing happens.

Once (if) I get into recovery, how do you update SuperSU binaries?
[Moto X Original Android Development] somerandomname1:
When you hit volume up, you are doing it correctly. After SlapMyMoto, booting into recovery just boots the device with write protection off. This is what you want. Now that you have root you can also use the method posted in these forums to have more permanent write protection off and not have to worry about booting into recovery.
[Moto X Original Android Development] MaKTaiL:
So, if I don't use this, only SlapMyMoto, when does the write protection turns on? How often will I have to boot into recovery to get write protection off?

Enviado de meu GT-I9082L usando Tapatalk
[Moto X Original Android Development] halfcab123:
CydiaImpactor gives me base_clear::ios error... fancy. I'm on 4.2.2 using Windows...

I tried installing telnet and removing telnet, error happened before and after... nearing the give up point.
[Moto X Original Android Development] dtrud0h:
You will have to boot into recovery anytime you want to do something that requires write protection off. You could run in recovery mode all the time, but its not recommended.

Sent from my XT1055 using Xparent Cyan Tapatalk 2