[Q] verizon moto x 4.4 root - Moto X Q&A

Hi all, i'm trying to follow the instructions in the original moto x development thread to root the device now that it has taken the 4.4 update. I'm unclear on the steps, if someone could please help. it says at the beginning of the thread
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
is this all done before step 1 in the directions? if so, i tried to run MotoWPNoMo but it failed at the end.
Is it possible to just use rsd lite and write the earlier software to phone, and then start with step 1?
Any input on clearing up the steps would be appreciated. I've been reading since last night and still not clear on what needs to be done first. I just don't want to mess up the procedure. Thanks

anyone?

Yep, I believe you use RSD to downgrade to 4.2.2. Read this tutorial, it is pretty easy to follow: http://w3.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/

Related

Rooting 4.4 Questions

Hello Fellow of Xda members,
I have very amazing At&t 4.4 Kit Kat Moto X like everyone else.
Rooting Moto X is kinding overwhelming to me from I read some thread for few hours. I know some basic sdk. I don't know where to start since I'm new to Moto X yesterday as 12/27. I had previous phone S4 and Nexus 5.
I have tried to flashed 4.2.2 camera update but it failed on RSD Lite since it has no root permission (stupid me), I flashed back 4.4 instead and working, looking for rooting solution for it. Not calling out for help, taking time here.
Thanks!
LeonKnight12 said:
Hello Fellow of Xda members,
I have very amazing At&t 4.4 Kit Kat Moto X like everyone else.
Rooting Moto X is kinding overwhelming to me from I read some thread for few hours. I know some basic sdk. I don't know where to start since I'm new to Moto X yesterday as 12/27. I had previous phone S4 and Nexus 5.
I have tried to flashed 4.2.2 camera update but it failed on RSD Lite since it has no root permission (stupid me), I flashed back 4.4 instead and working, looking for rooting solution for it. Not calling out for help, taking time here.
Thanks!
Click to expand...
Click to collapse
From what I've seen it looks like you have to revert back to 4.2.2, and then unlock the bootloader, install a custom recovery (my favorite is CWM but some people use TWRP or something), and then flash your device. Here are a couple more comprehensive answers:
http://forum.xda-developers.com/showthread.php?t=2538896
http://forum.xda-developers.com/showthread.php?t=2509590
I think the first one is better, but I think I'm going to give it a shot later today. I'll get back to you if either one of them works.
Kupua said:
From what I've seen it looks like you have to revert back to 4.2.2, and then unlock the bootloader, install a custom recovery (my favorite is CWM but some people use TWRP or something), and then flash your device. Here are a couple more comprehensive answers:
http://forum.xda-developers.com/showthread.php?t=2538896
http://forum.xda-developers.com/showthread.php?t=2509590
I think the first one is better, but I think I'm going to give it a shot later today. I'll get back to you if either one of them works.
Click to expand...
Click to collapse
I went through all process and pain in the ass. I rooted and disabled write protection and flashed back to 4.2.2 camera update and redo root process again and as I go through it, seem I can't obtained root access. Is this lost root? Tried to use supersu from playstore and says "there is no SU binary installed and SuperSu cannot install it. This is a problem"
looks like do I have to wait for next update?
Please help.
LeonKnight12 said:
Hello Fellow of Xda members,
I have very amazing At&t 4.4 Kit Kat Moto X like everyone else.
Rooting Moto X is kinding overwhelming to me from I read some thread for few hours. I know some basic sdk. I don't know where to start since I'm new to Moto X yesterday as 12/27. I had previous phone S4 and Nexus 5.
I have tried to flashed 4.2.2 camera update but it failed on RSD Lite since it has no root permission (stupid me), I flashed back 4.4 instead and working, looking for rooting solution for it. Not calling out for help, taking time here.
Thanks!
Click to expand...
Click to collapse
If you have the ATT variant of the phone (retail or Moto Maker), and want to be rooted on KitKat (Android 4.4) you need to follow SlapMyMoto -> http://forum.xda-developers.com/showthread.php?t=2538896 .
RSDLite should not fail due to no root permissions. RSDLite doesn't care about root.
If you are following SlapMyMoto or RockMyMoto, when you are on KitKat (4.4) and need to revert to a 4.2.2 rom it says you have to flash to the "camera update" 4.2.2 rom. This is because you can't flash back to the initial 4.2.2 rom the phone shipped with. If you had problems with RSDlite, I would question if you are trying to flash the initial shipping 4.2.2 rom, not the camera update one.
If you are having problems with either process, I'd go into the appropriate thread and post a detailed account of what you've done (including exact file names for roms you flashed), and what the outcome was, asking for help. That is going to be the best way to find a solution.
---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------
Kupua said:
From what I've seen it looks like you have to revert back to 4.2.2, and then unlock the bootloader, install a custom recovery (my favorite is CWM but some people use TWRP or something), and then flash your device. Here are a couple more comprehensive answers:
http://forum.xda-developers.com/showthread.php?t=2538896
http://forum.xda-developers.com/showthread.php?t=2509590
I think the first one is better, but I think I'm going to give it a shot later today. I'll get back to you if either one of them works.
Click to expand...
Click to collapse
unlocking the bootloader, installing custom recovery and installing/flashing SuperSU only works for those with an unlocked bootloader. And it can be done on any rom version. If you can unlock your bootloader, it is the quickest and easiest way to root. NOTE: Unless your phone is the developer edition, unlocking your boot loader voids your warranty.
ATT variant of the phone can't unlock the bootloader, so SlapMyMoto is needed if you want to be running Kit Kat (android 4.4). And RockMyMoto is used if you want to be on Jelly Bean (4.2.2), but only works on the "Camera update" OTA rom. Not the initial rom the X shipped with which is also 4.2.2
KidJoe said:
If you have the ATT variant of the phone (retail or Moto Maker), and want to be rooted on KitKat (Android 4.4) you need to follow SlapMyMoto -> http://forum.xda-developers.com/showthread.php?t=2538896 .
RSDLite should not fail due to no root permissions. RSDLite doesn't care about root.
If you are following SlapMyMoto or RockMyMoto, when you are on KitKat (4.4) and need to revert to a 4.2.2 rom it says you have to flash to the "camera update" 4.2.2 rom. This is because you can't flash back to the initial 4.2.2 rom the phone shipped with. If you had problems with RSDlite, I would question if you are trying to flash the initial shipping 4.2.2 rom, not the camera update one.
If you are having problems with either process, I'd go into the appropriate thread and post a detailed account of what you've done (including exact file names for roms you flashed), and what the outcome was, asking for help. That is going to be the best way to find a solution.
---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------
unlocking the bootloader, installing custom recovery and installing/flashing SuperSU only works for those with an unlocked bootloader. And it can be done on any rom version. If you can unlock your bootloader, it is the quickest and easiest way to root. NOTE: Unless your phone is the developer edition, unlocking your boot loader voids your warranty.
ATT variant of the phone can't unlock the bootloader, so SlapMyMoto is needed if you want to be running Kit Kat (android 4.4). And RockMyMoto is used if you want to be on Jelly Bean (4.2.2), but only works on the "Camera update" OTA rom. Not the initial rom the X shipped with which is also 4.2.2
Click to expand...
Click to collapse
I get it, I was flashing initial 4.2.2 and failed to flash and I did flash camera update and went through fine and rooted and write protection off. After this I flashed back to 4.2.2 and tried rockmymoto again and It all I can get system warning "system is not write protected executing step 3" reroot has been lost.

[Q] Update rooted Verizon 4.2.2 X to 4.4 on Mac?

Howdy all, I truly believe I've searched far and long to no avail.
I have a Verizon Moto X, on 4.2.2, rooted by simply downloading (on the phone) and installing PwnMyMoto 1.4.3 for VZW.
I followed a YouTube video titled "How To One Click Root Verizon MotoX [Updated] PwnMyMoto With Write Protection Bypass"
I'd like to update to 4.4. I'm using a Mac, and I've successfully set up ADB/Fastboot in Terminal.
I've seen a few guides, but I'm still not 100% getting it.
Is it relatively easy, being that I'm rooted?
Could any kind soul make my day and please give me simple steps for a lunkhead like myself?
Thanks.

[Q] Black screen after trying to root, did i hard bricked my moto x?

Hey guys,
So i was interested in installing a custom rom im my moto x and started by trying to root it.
Every thing was going fine, but after i placed the unlock code via CMD, i've got an error during the root process and my phone just died. Now all that i've got is a black screen, no matter if I try to hard reset or anything.
Any idea?
tl;dr my phone just died in the root process, wtf can i do?
Unlock code? Root process?
Which model do you have? Which version of Android was it on? What exactly were you doing or using to root or unlock?
Which model you have used ?
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
You will need to be far more specific in what commands you did, if any...and the specific errors.
Only way we'll know what's happened.
It may be of some help if you post the tutorial you followed and say exactly at what step things went wrong.
Sent from my Moto X using Tapatalk Pro
monzillo said:
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
Click to expand...
Click to collapse
The XT1058 has a locked bootloader, so I hope that tutorial didn't have you try to downgrade your ROM in order to use SlapMyMoto/MotoWpNoMo to root and disable write protection.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone anymore. Additionally, 4.4.2 closed the exploits used by SlapMyMoto/RockMyMoto to gain root, and the exploit used by MotoWpNoMo to disable write protection.
As others have suggested, post a link to the turtorial, and any error messages you saw while running the scripts.
Also, try booting into bootloader/fastboot mode. Can you get there? What version bootloader does it say you are on? I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. If you have 30.B4, then your only fix might be using RSDLite to flash the 4.4.2 SBF for your carrier, or mFastboot to individually flash all parts of 4.4.2 on your phone, and then forget about rooting unless Moto's web site gives out the bootloader unlock code for your phone.

4.2.2 to 4.4 Root Nightmare

So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
HTC-OH_SNAP said:
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
Click to expand...
Click to collapse
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
kj2112 said:
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
Click to expand...
Click to collapse
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
kj2112 said:
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
Click to expand...
Click to collapse
The Safestrap process, and installing a proper safestrap rom does not update the phone's bootloader. I think it also doesn't touch the GPT.BIN.
I know you haven't had experience with Safestrap, so think of it as kind of a Host OS/Guest OS setup, or if it was a PC then kind of like a Virtual PC setup where you could have a PC running real Windows 7 on your C drive that you boot too, plus having Windows 8 in a virtual PC and the Virtual PC's image file being stored on your "D drive". Installing W8 in the virutal PC doesn't touch the W7 "host" os, or its boot partition, etc. (its not 100% exactly the same, but that is the best analogy I can come up with at the moment).
---------- Post added at 06:35 AM ---------- Previous post was at 06:02 AM ----------
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
re: safestrap affecting the bootloader, no, it does not. At least if you are using a ROM made for safestrap, and properly follow the process.
To determine the bootloader version, boot the phone to bootloader mode it should show the version number. I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. As @kj2112 has mentioned, If the bootloader has been updated to 4.4.2, do NOT attempt to downgrade. However when using safestrap properly, its different.
As for the error at step 3... apparently it is common for those who had once used MotoWpNoMo to disable write protection, then trying to run though the SlapMyMoto process.
The actual process for getting a working Safestrap setup is the same for all Moto X's, however the Safestrap roms, and possibly the installer, are model specific... So, for example, if you have a Verizon X with locked bootloader, you could still follow [GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo but using the Verizon specific SBFs, SafeStrap and Safestrap Roms instead of the ones for T-Mobile and RW linked in that thread (like on steps 1b, 3a, 5a, 6b).
Because of that, I'll point you to -> http://forum.xda-developers.com/showpost.php?p=52401229&postcount=30 as it is the quickest link I can find to a work around for slapmymoto if you've already disabled write protection with MotoWpNoMo.
I'm sure if you took the time to read every post in the SlapMyMoto thread or the entire MotoWpNoMo thread you will likely find discussions about your situation and a fix. For example: Post 349 through 357 of the MotoWpNoMo thread is a user having the same issue, but later says it was due to the SlapMyMoto file being the older 0.5c version rather than 1.0.
I'm sorry, I'm just not good with RockMyMoto/SlapMyMoto/MotoWpNoMo/etc and Safestrap as I have an unlocked bootloader, so I never had to mess with them to root and disable write protection.
how do i spf back to 4.2.2?
coolguy71261 said:
how do i spf back to 4.2.2?
Click to expand...
Click to collapse
This is someone's thread with their particular issue. If we start helping you in this thread with your issue....that is called thread hijacking.
You need to ask in a thread relevant to your issue, or start a new thread.
However.....since we don't know anything about your situation or your issue.....advice is hard to give.
You can probably start here tho.... http://forum.xda-developers.com/showthread.php?t=2603358
If that doesn't help, you need to make your own thread. And be as specific as possible with the details. But only start a thread if searching comes up with nothing and no existing threads match your issue.
Just some XDA etiquette.
Good luck.
And sorry to OP for off topic.
If you rooted with rockmymoto and took write protection off. You'll still have it so the only process you'll need to do is slapmymoto on 4.4. Safestrap will work with 4.2.2 and 4.4. If you want root stay there don't go to 4.4.2
MOTO X
KidJoe said:
Great Advice
Click to expand...
Click to collapse
Ok... so here is how the whole thing ended.
Checked my Bootloader - it was still 30.71.
Verified I still had Write Protection off.
Ran SlapMyMoto 1.0.
Took the OTA (From 4.2.2 it is still 4.4 and NOT 4.4.2)
Ran the ADB Shell Commands.
Installed SuperSu from the Play Market, and...
Rooted 4.4 with Write Protection Off.
Thanks!

First time rooting. Own MOTOROLA DROID TURBO from Verizon. Help!!!!!!!!!!!!

Hi,Im first time rooter and i have a problem to understand the whole story about this. I found all the step by step instructions how to root it to 5.1 lollipop(as much i understood i need to root it on kk and after to flash it to lollipop) but my concern is how to downgrade firmware from 21.21.15quark_verizon.en.us to firmware 21.44.12. so i can do a rooting after. I was digging all over internet especially on this forum and i couldn't find any instructions how to do it. I will need step by step about this. Please if there is anybody that can help me i would appreciate his help. Thank you
I don't think you can downgrade once you're at lollipop. That's why people have been not upgrading or calling to get a refurbished phone and hoping it still has kit kat on it

Categories

Resources