yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] JuHJoh:
sorry for the newbie question but I am having hardest time finding out how to downgrade to 4.2.2

i tried using http://xdaforums.com/showthread.php?t=2446515 to downgrade... but had no luck. Used VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_1FF.xml and i get "downgraded security version, update gpt_main version failed, preflash validation failed for GPT"

Is there another reflash file i can use?
[Moto X Original Android Development] lowvolt1:
You need 17-57. Go to post 593.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] Nixal:
Someone succeeded in downgrading the 4.4 Brazil without brick ? and return to 4.4 after root with root ?
[Moto X Original Android Development] barondebxl:
Hey guys, I'm very sorry for the quick off topic but people have been so helpful here that I wanna ask here. I cannot get xposed framework at all. I installed the apk but when I update the framework and reboot I keep getting the red message saying that I need to reboot after I install it. I also delete xposed disabler from my storage but it comes back after every reboot. Any ideas?? Thanks in advance!
[Moto X Original Android Development] h1ghland3r:
Guys, I updated the SuperSU by Play Store, but now it isn't update the binaries. Is it important?
[Moto X Original Android Development] lowvolt1:
Reboot recovery or flash motowpnomo. That will permantly disable write protection.

via my slapped KIT KAT moto X rockin on Verizon

---------- Post added at 05:48 PM ---------- Previous post was at 05:48 PM ----------

Try rebooting recovery. (Wp off)

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] barondebxl:
Thanks, will give it a try.
[Moto X Original Android Development] h1ghland3r:
Sorry, but how can I do that?
[Moto X Original Android Development] lowvolt1:
Power down phone. Hold power and volume - down at the same time. Hold for about 30 seconds. When fastboot screen appears use volume - to scroll to recovery and volume + to select. The phone will boot normally but be write protected off.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] h1ghland3r:
I rebooted following the steps and I opened SuperSu, but this time the binaries didn't ask to be updated.
[Moto X Original Android Development] Toys Samurai:
I feel like an idiot now -- Yea! I just

adb reboot recovery

and it rebooted into Android with write protection OFF! THANK YOU VERY MUCH!

Question -- so, is it a bad idea to install a recovery now? Is there even one that's suitable for a rooted non-DEV VZW Moto X on KitKat?
[Moto X Original Android Development] lowvolt1:
Try to do a task that needs root permission. And see if you get promoted to grant super user access.

via my slapped KIT KAT moto X rockin on Verizon

---------- Post added at 06:32 PM ---------- Previous post was at 06:30 PM ----------

You have a locked boot loader. You can't install a custom recovery.

via my slapped KIT KAT moto X rockin on Verizon

---------- Post added at 06:35 PM ---------- Previous post was at 06:32 PM ----------
[Moto X Original Android Development] h1ghland3r:
Yes, root seems to works fine. And now, should I rebooted in the standard mode?
[Moto X Original Android Development] lowvolt1:
You certainly can. Just remember if you need to write to system you will have to reboot recovery.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] h1ghland3r:
Got it, really thanks lowvolt1 !
[Moto X Original Android Development] lowvolt1:
Your most welcome.

If you are feeling adventurous, you could always do the motowpnomo steps and permanently disable wp. Then you would not have to reboot recovery to write to system.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] h1ghland3r:
But using motowpnomo will I lose warranty?
[Moto X Original Android Development] lowvolt1:
You rooted. You already did. Unless of course if you have an issue you unroot. I was told that if you flash the 4.4 .IMG and recovery you will reverse the motowpnomo. Now keep in mind there has only been one instance of this happening. But I think only one person has tried it. The choice is yours. Just wanted you to be aware of the options.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] emmabellachristian:
i just wanted to ask if anyone who remebers my issue i did

So made dumb mistake had this phone rooted before then was gonna sell it cus didn't like it so went back to 4.2.2 for sale buyer backed out and so was doing root process again and long story short was in flash boot image step didn't bother pay attention so just went ahead and did reboot. Noticed it said boot image wasn't flashed and now my phone won't even boot into boot loader to reef lash 4.2.2 with rsd. It's AT&T so I'm pretty muched effed right. Can't boot obviously can't boot into boot loader. Plug it in here chimes like its on try go into boot loader well connected here chimes again but nothing just black screen.

to refresh memories i have green light on my phone i did google search to find some info couldnt really fine much sept its related to battery life ? still just trying see if i can figure out anything to do to save it.
[Moto X Original Android Development] Dark9781:
You are hard bricked. Your phone is a paperweight. You can try and see if you can get it warranty replaced through Moto. You may not want to tell them you were messing around with the phone and caused it though.
[Moto X Original Android Development] emmabellachristian:
just curious though, if its hard bricked means it wont turn on etc. when i plug it in my pc makes that noise like detects it. my pc shows thing saying its installing the drivers so it wouldnt do that i thought if it was hard bricked ?
[Moto X Original Android Development] lowvolt1:
Have you charged the phone for 24 hours to make sure the battery is charged? Can you fast boot, adb reboot boot loader? Just throwing it out there.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] emmabellachristian:
not for 24 hours no but for like 5 or 6 i think it was yes, i tried fast booting well plugging it in it makes that sound but nothing happens it says waiting for device and then nothing happens
[Moto X Original Android Development] lowvolt1:
What says waiting for device? Your PC?

Try using rsdlite to flash 4.2.2.

Try using fast boot adb to reboot boot loader.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] emmabellachristian:
thats thing my computer does that sound like i said like it detects it but then rsd doesnt show the device at all..... so thats why im completely confused and when i plug phoen in to charge to see the green light doesnt stay on
[Moto X Original Android Development] lowvolt1:
Have you ever used adb?

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] emmabellachristian:
no i havent guess ill have to google see what it is and how
[Moto X Original Android Development] natezire71:
The file list for previous versions of MotoX software are gone...
[Moto X Original Android Development] Dark9781:
Your device is in QHSUSB_DLOAD mode. It is a mode used by Qualcomm to load software to the phone. You no longer have access to the boot loader because it became corrupt when you were flashing. The only way to fix it is to find someone with the proper file to fix it through QHSUSB_DLOAD mode (going to be very hard to find) or try to warranty exchange.
[Moto X Original Android Development] tallgrasshawk:
Ok maybe someone can help me out. Got downgraded to 4.2.2, everything is fine until I open up cmd window to run telnet. I have telnet client enabled. But any telnet command comes back it's not a recognized command. Win 7 64 bit machine.
[Moto X Original Android Development] brunodmjr:
A question: If I root it through SlapMyMoto (no bootloader unlock) and use the root just for AdBlocking, it will be possible to use OTA update or this oficial .zip for a future update and have as side effect only the lose of root?

Since we don't have roms for International Moto X yet (I think only Brazil and Argentina received it and there is no Moto X at Asia and Europe), there is not ROM, so it will aways be tricky.
[Moto X Original Android Development] Toys Samurai:
Root successful, but can't shut down now

Long story short -- I rooted successfully, everything works fine except that I can't shut down my Moto X now. I originally posted to: xdaforums.com/showthread.php?p=48537068, but now I am thinking of redoing the whole thing from scratch.

First of all, does anyone has the same problem? As I said, I can't shut down my phone. When I power it off, it reboots right back. But other than that annoying issue, everything works fine. Oh, FYI, I did install that mod to enable native wifi tethering -- that's the only thing I've changed after getting root.

Secondly, what would happen if I do a reset on 4.4 now? Will it revert me back to the original unrooted state?

Lastly, if I want to downgrade and start all over, should I reset first, then downgrade, just to make sure everything is as close to stock as possible?
[Moto X Original Android Development] wmarcin:
You're not connected to a charger or your computer via USB when you try to power off your Moto X, are you?
[Moto X Original Android Development] Toys Samurai:
I tried to power off both way. But it didn't make any differences. Whether it's connected to my computer, or not connected to anything at all, whenever I power off, it reboots right back to Android.
[Moto X Original Android Development] bd1212:
Well I can't get telnet to work for the life of me... got the phones ip address, started impactor as system blah blah on port 2222 and waited for it to complete. Opened PuttyTel and entered the ip address of the phone and changed the port to 2222 and made sure the connection type was telnet. Clicked open, and a few seconds later I get a timeout error. I've restarted my PC a few times and have no idea where to go from here. Any tips?

Before 4.4 was released I was able to root my Moto X on 4.2.2 with no problems and telnet worked just fine, so I no it's not my router or my PC as nothing has changed since then. I have no idea why its having problems now, but it's very annoying.
[Moto X Original Android Development] Toys Samurai:
Can you ping your phone?

---------- Post added at 10:48 AM ---------- Previous post was at 10:41 AM ----------

Did you check if you have Verify Apps disabled?
[Moto X Original Android Development] lowvolt1:
Use puttytel

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] bd1212:
Just tried pinging it and that's timing out as well, and yes verify apps is disabled. Really at a loss for what could be causing this.
[Moto X Original Android Development] Toys Samurai:
Just to make sure, you have both "Verify Apps" and "Verify Apps over USB" disabled (the second one should be disabled whenever the first one is, the checkbox may be checked, though.)

I had the same problem when I was following the instruction, but after toggling the 2 "Verify Apps" settings a couple times, it suddenly worked -- not sure what exactly made it work, though.
[Moto X Original Android Development] bd1212:
Yep, both disabled... toggled them a few times and toggled USB debugging and still nothing. I have no idea what the problem is. :/
[Moto X Original Android Development] tallgrasshawk:
I have Verify over USB is checked, but it's grayed out and can't change it. It becomes unchecked if I turn off USB debugging (well, that isn't going to work) but rechecks when debugging is on. What the heck.
[Moto X Original Android Development] dtrud0h:
Just a thought, but is wifi.set up and enabled? Might have switched off upon the 4.4 install

Sent from my XT1055 using Xparent Cyan Tapatalk 2

---------- Post added at 11:47 AM ---------- Previous post was at 11:40 AM ----------

The tepnet is working over the wifi, not the USB so if its not on your wifi network it won't work. May be a port blocked on your router also.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] Toys Samurai:
Not sure if it mattes, but to uncheck "Verify over USB", you need to check "Verify Apps" in the "Security" settings first. Then uncheck "Verify over USB", and go back to uncheck "Verify Apps".

Hope that helps.
[Moto X Original Android Development] chrisbass:
SlapMyMoto 0.5c Beta (4.4 root, RW to system)

I've been having the same problems for a couple days now and have tried everything that's been suggested to the both of us. Changed to a different router and tried two different computers....win7 & win8. As I've read it looks like we're the only two with the problem. I've tried to catch Saurik on irc.saurik.com to no avail.
[Moto X Original Android Development] bd1212:
No blocked ports and wifi is connected to the same network as my PC. I had no issue doing this a few weeks ago before the Moto X was updated to KitKat, so nothing has changed.
[Moto X Original Android Development] cdmove:
so I need to downgrade to 4.2.2 before i can do this?
[Moto X Original Android Development] bd1212:
Yup.
[Moto X Original Android Development] sd0070:
Is there a post in here that explains in detail how to revert to 4.2.2? I dont even see which version of the camera update to download. Guess its a bad sign when I cant do the first step lol. But I've used adb several times before on other devices, just need a little help getting started. :confused:
[Moto X Original Android Development] bd1212:
Just updating everyone, but I finally was able to gain root and get past the telnet issues. I had to do a factory reset and then go through the whole process of rooting, but in the end it all worked out.

Now, to answer your question: sure, I can help you with getting started. :)

If you've got a VZW Moto X, download this: Click Here.

That's the 4.2.2 camera update/firmware file that you'll be referring to throughout the rooting process. You'll want to unzip that and put that in the same folder as SlapMyMoto just to keep things organized.

Guide on how to revert to 4.2.2: Click Here.

That should be all you need for reverting to 4.2.2 and then beginning the rooting process for 4.4. Let me know if you have any other questions, I'm happy to help and answer questions. There's never any dumb questions... gotta start somewhere and you can only learn from asking questions and making mistakes. :)
[Moto X Original Android Development] scootle74:
SuperSU v1.85

So my 32GB MotoX (VZW non-dev edition) was rooted just fine up until now. I was able to run Wifi Tether for root against grandfathered VZW unlimited data.

I noticed SuperSU updated yesterday (15 Dec 2013) to v1.85. Anyone having problems since this update?

When I launch SuperSU it tries to update the binary and fails, asking for a reboot. Tried a few times and no luck. Did something break in the new version with respect to the MotoX? What are the steps to fix this problem? I'd hate to have to run the whole process of downgrading to 4.2.2 and wipe again to re-root the phone from scratch.

Losing root means I lost my ability to tether (the only way right now on MotoX due to VZW being dumb), so this is somewhat important! :D

Thanks.
[Moto X Original Android Development] sd0070:
Thank you! Yesss I can finally root when I get home tonight! lol
[Moto X Original Android Development] lowvolt1:
Have you permanently disabled write protect using motowpnomo?

If not did you reboot recovery to update the supersu binaries?

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] GandalfTehGray:
Anyone tried to do this over a tethered connection? Or should I wait until normal wifi is available?
[Moto X Original Android Development] tallgrasshawk:
NM
[Moto X Original Android Development] bd1212:
No problem! :)

Good luck, let me know if you have any questions.

I'd wait till normal wifi is available.
[Moto X Original Android Development] lowvolt1:
Are you running impactor first?

via my slapped KIT KAT moto X rockin on Verizon

---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------

You have to be on the same network as your PC.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] chrisbass:
So how'd you fix your telnet issues? Was it the factory reset?
[Moto X Original Android Development] sd0070:
Is an easier root method being worked on...or does it look like this will be the only option for some time?
[Moto X Original Android Development] gitku:
@ jcase did anyone take you up on making your method work after rw off by beaups?

Don't know that I'm 100% confident I can do it but I'll give it a look and see if I can make it work on mine.
[Moto X Original Android Development] scootle74:
Didn't know about motowpnomo... will check into that.

I'm not sure I can update SuperSU binaries from factory recovery, can we? In the meantime, it seems my system still has root access for the main apps that require it... especially Ti Backup. Turns out my tethering issue was related to Wifi Tether itself, not SuperSU, but the problem of updating SuperSU still remains.

Thanks a bunch. Will report back if issue is solved or something else pops up.
[Moto X Original Android Development] lowvolt1:
You really don't have a recovery anymore. The process of recovery now just becomes a process of disabling write protection.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] jcase:
can you come to #MotoX on freenode, so i can poke around
[Moto X Original Android Development] mj0528:
That's exactly what is happening to me.

---------- Post added at 11:42 PM ---------- Previous post was at 11:34 PM ----------

If I remove the erase user data from the XML file for rsd, it will boot loop. Is there a way to downgrade to 4.2.2 and keep user data?
[Moto X Original Android Development] :
So, if one was at 4.2.2 w/ camera fix and rooted via RockMyMoto, but no other system modifications made, do you still have to re-apply the original system image? Or can you just proceed with this rooting process?
[Moto X Original Android Development] jcase:
"Failed to nab check for recovery: 0x56" issue should be fixed in 0.5c that I just uploaded, if you had the 0x56 error, you can use 0.5c starting at step 6 without having to downgrade again
[Moto X Original Android Development] Sinderan:
Success

0.5c working here! Time for TiBu and Xposed!
[Moto X Original Android Development] phositadc:
Is Xposed available for KitKat yet?

Sent from my XT1030
[Moto X Original Android Development] Sinderan:
You know... I haven't even thought to check. I'm just happy to freeze the ATT apps
[Moto X Original Android Development] mjphillips1981:
0.5c worked for me as well!! Your hard work is much appreciated!! Buy a few beers on me!!
[Moto X Original Android Development] stillthisguy:
0.5c working great on vzw! Thanks jcase - Donation Confirmation number: 1XH19098S48300611.
[Moto X Original Android Development] phositadc:
Haha don't think it's available yet but hopefully soon!

Sent from my XT1030
[Moto X Original Android Development] jcase:
Looks like 0.5c cleared up most of the lingering issues, im going to go relax
[Moto X Original Android Development] shane1:
Thanks jcase for all your hard work! Nice to know root is an option again :)
[Moto X Original Android Development] Sinderan:
Strangely I've found KitKat modules, but they all say that the Framework isn't compatible so they don't work yet 0.o
[Moto X Original Android Development] bigv5150:
No he has a beta version here you go http://xdaforums.com/showthread.php?p=47771876
[Moto X Original Android Development] Infekxion:
I got to step 6, got the getvar error and now I have a brick sitting in front of me. My computer recognizes it but says it needs to install driver for QHSUSB_DLOAD, any ideas?

Sent from my Flo
[Moto X Original Android Development] staveandor:
Running Version 5.0, VZW Moto X:

I've run SlapMyMoto.jar 3 times, and am stuck here:

fastboot flash recovery recovery.img

I keep receiving the error below

The system cannot find message text for message number 0x2331 in the message file for Application.

Any help?
[Moto X Original Android Development] jcase:
What OS is your computer? as I am not familiar with that kind of error
[Moto X Original Android Development] jcase:
What getvar error? Sounds like the bootloaders you flashed were corrupted some how

Yes, yes you have a damn near brick, but I have the signed files to recovery from that. Add jcase@cunninglogic.com and msg me
[Moto X Original Android Development] staveandor:
Windows 8.

This is happening during Step 4.
[Moto X Original Android Development] anpan879:
Got root on ATT with .5c, Thanks.
[Moto X Original Android Development] dtrud0h:
Its pretty bad that 78 pages later people still don't get the recovery vs. rw / ro system thing.

Yes, it's a custom recovery, no your bootloader doesn't need to be unlocked. How hard is that to understand? Read-Write access happens through the custom recovery that you boot into if you want to have read-write access to system, otherwise system is read only. Your boot loader is still locked, you can't do anything that a. "Custom Recovery" ( as normally defined) can do, yours is custom in that it allows read-write access to your system partition, period.

Sorry, just had to put this out this out there.

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] scootle74:
got it!

Now that makes sense. Rebooted "recovery" and applied the SuperSU update... rebooted again and all is well. Thanks for clearing that up! Props.
[Moto X Original Android Development] lowvolt1:
I think your explanation of it will just confuse people. When people talk about "custom recovery" they are thinking along the lines of TWRP or CWM. Where as the phone actually boots into recovery. When you have wp disabled and "boot recovery" your phone boots as what appears to be "normal" boot. But with write protection disabled for that boot. So, in essence, you no longer have "recovery" but "write protection" off.

via my slapped KIT KAT moto X rockin on Verizon
[Moto X Original Android Development] scootle74:
If this was explained from the get-go in the OP regarding what this "rooting" process does, those of us with lower IQ would have probably understood this. ;) Just sayin'

Makes perfect sense now though... just took a go-around to understand what exactly is the deal here.

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

The confusion lies with exactly the fact that hitting "recovery" from the bootloader sends the phone into an apparently normal boot-up.

I wish this could be added to the OP regarding the root process, seriously. It makes perfect sense once someone takes the tiny bit of time to lay it out rather than try to be condescending towards other users.

Thanks again.
[Moto X Original Android Development] dtrud0h:
Sorry scootle74,

You're over-ruled. Two against one. Just sayin'.

That how I see this whole thing, thought it may help others to get their head......:) around it.

On a side note, if you should meed an actual recovery, and someone please correct me if I'm wrong, I think it would be prudent to temporarily flash the 4.2 camera update recovery, then (and this escapes me) somehow flash back to our "Custom-[Slapped]-Recovery". Anyone know how to do that?, jcase(if you have a minute)?

Sent from my XT1055 using Xparent Cyan Tapatalk 2
[Moto X Original Android Development] lowvolt1:
Correct me if I am wrong but did we not flash the 4.2.2 camera update recovery in order to root with slap on 4.4? I believe we did.

via my slapped KIT KAT moto X rockin on Verizon