Related
Hi
I have a moto x with the bootloader unlocked and stock kernel with TWRP. Everything else is stock android 4.4 from T-Mobile.
I followed this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=2536200 "[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat"
Everything went fine and I had root acces. I installed xposed framework and some moddueles without problem and cerberus but when I tried to install greenify I noticed I couldn't give it root permissions. I checked super su's app and everything seemed normal so I downloaded Root Checker to confirm I'm rooted but it says I'm not.
Knowing that I lost root (can't figure out why) I went to super su app and selected to unroot the device. Then I booted into recovery and flashed again the root zip but when checking again if I have root privileges with root checker, it still says no.
Now I can't get root again. I'd like to avoid using fastboot because I'm using linux (I'm a noob with bootloaders and fastboot because I got spoiled by Samsung).
Can anyone help me?
Thanks in advance :fingers-crossed:
I forgot to mention that I did a backup before I rooted the device the first time in case that helps.
Nevermind. I fixed it.
I just ordered a new Moto X Developer Edition VZN
Can I get native tethering? I know I can probably use FoxFi, but wondered if there is a way that I can use native and if I need to root to do it?
If you've installed Xposed framework (which you definitely should) there's a module called Moto Tether. Been using it for a while, it uses native tethering.
gencode said:
I just ordered a new Moto X Developer Edition VZN
Can I get native tethering? I know I can probably use FoxFi, but wondered if there is a way that I can use native and if I need to root to do it?
Click to expand...
Click to collapse
this is a xposed app that will help you
http://forum.xda-developers.com/showthread.php?t=2601859
and this is a mod you can do but alot more difficult
http://forum.xda-developers.com/showthread.php?t=2536166
enjoy
gencode said:
I just ordered a new Moto X Developer Edition VZN
Can I get native tethering? I know I can probably use FoxFi, but wondered if there is a way that I can use native and if I need to root to do it?
Click to expand...
Click to collapse
Kit Kat broke FoxFi Wifi tether but bluetooth and USB tether still work.
I rooted after I unlocked, which was not at all hard to do. Then I tried the adb commands in this link:
Native Tether for VZW DE 4.4
but my PC won't recognize my Moto X when it is in bootloader mode, and so the adb commands don't work for me although I can use fastboot commands. I have a driver problem that I need to debug.
Anyhow, later on in that thread another poster gave instructions that don't require adb commands, and I did that and it works great:
Native Tether for VZW DE 4.4 Using Root Browser
I used the Root Browser by Jrummy in the Play Store to do it.
The popup that the phone is checking for your subscription comes up but it never does the check and just enables the WiFi Tether.
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Correct me if I'm wrong.
gencode said:
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Click to expand...
Click to collapse
Correct, it requires root.
That Xposed module has been working flawlessly for me as well
Sent from my Nexus 7 using Tapatalk
YankInDaSouth said:
That Xposed module has been working flawlessly for me as well
Click to expand...
Click to collapse
Does Xposed require root?
Cozume said:
Does Xposed require root?
Click to expand...
Click to collapse
Yes
gencode said:
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Xposed requires root, too.
Xposed requires root, but rooting the dev edition is simple
Sent from my Nexus 7 using Tapatalk
gencode said:
Thanks guys Ill probably try the Exposed one since it looks like the APK one requires root.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Is root an obstacle for you for some reason? I'm curious because you possess a developer edition yet ask about root as if it's not something you desire.
nhizzat said:
Is root an obstacle for you for some reason?
Click to expand...
Click to collapse
seriously, it was so easy. But not everyone realizes that.
nhizzat said:
Is root an obstacle for you for some reason? I'm curious because you possess a developer edition yet ask about root as if it's not something you desire.
Click to expand...
Click to collapse
Nope not at all, my GS3 is rooted, just wondered.
Thanks again, now just gotta wait for it to ship out, took advantage of this sale going on with the MotoX.
nhizzat said:
Is root an obstacle for you for some reason? I'm curious because you possess a developer edition yet ask about root as if it's not something you desire.
Click to expand...
Click to collapse
Cozume said:
seriously, it was so easy. But not everyone realizes that.
Click to expand...
Click to collapse
I saw this link
http://forum.xda-developers.com/showthread.php?p=45598679
Is there an easer one? Im getting the developer edition.
gencode said:
I saw this link
http://forum.xda-developers.com/showthread.php?p=45598679
Is there an easer one? Im getting the developer edition.
Click to expand...
Click to collapse
yes there is an easier method if you get the developer edition and unlock the bootloader.
To root the developer edition:
1) Get the unlock code from Motorola and unlock the bootloader by following the directions in this link, including downloading the Android SDK and installing Motorola Device Manager:
Unlock Moto X Bootloader
2) Get mfastboot.exe here:
mfastboot.exe
and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
3) Get the TWRP custom recovery for kit kat here:
TWRP for Moto X 4.4
and place it in the same directory as fastboot.
4) On your unlocked Moto X, enable USB debugging and download SuperSU here:
SuperSU 1.93
5) Double check to make sure USB debugging has been enabled! Put your unlocked Moto X into bootloader mode by pressing the volume down key and then the power key. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
6) Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
7) At the command prompt type:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
to flash the custom recovery to your Moto X.
8) After the custom recovery has been flashed to your Moto X, at the command prompt type:
fastboot reboot-bootloader
to reboot into the bootloader (I am not sure if this step is necessary but I read somewhere it was necessary and I did it and it worked).
9) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
10) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If you want to check to see if you successfully rooted, you can download Root Checker Basic from the playstore and it will tell you if you are rooted.
Remember, to take an OTA, you have to revert back to stock recovery!
Thanks man, x100
Now I'm ready, just waiting for the FedX guy to get here
gencode said:
Thanks man, x100
Now I'm ready, just waiting for the FedX guy to get here
Click to expand...
Click to collapse
My friend just got a Verizon DE and it shipped with 4.2.2. If you are on 4.2.2, you need to update it to 4.4 before you root with that version of TWRP I linked to. That version of TWRP I linked to is for 4.4 only. Verizon should push the 4.4 update to you pretty soon after turning your phone on.
They haven't even started the soak test on Verizon yet for 4.4.2. so don't worry about that now. But once they do start to push it to us, you have to revert back to stock recovery before you take the 4.4.2 OTA. And then I think we have to wait to root until someone updates the TWRP to be compatible with 4.4.2.
Here is the link on this if you need more info:
Unlocked Recovery for Moto X on Android 4.4
ETA - on another thread another poster said the same version of TWRP that I linked to above works for 4.4.2
http://forum.xda-developers.com/showthread.php?t=2646361
Cozume said:
My friend just got a Verizon DE and it shipped with 4.2.2. If you are on 4.2.2, you need to update it to 4.4 before you root with that version of TWRP I linked to. That version of TWRP I linked to is for 4.4 only. Verizon should push the 4.4 update to you pretty soon after turning your phone on.
They haven't even started the soak test on Verizon yet for 4.4.2. so don't worry about that now. But once they do start to push it to us, you have to revert back to stock recovery before you take the 4.4.2 OTA. And then I think we have to wait to root until someone updates the TWRP to be compatible with 4.4.2.
Here is the link on this if you need more info:
Unlocked Recovery for Moto X on Android 4.4
ETA - on another thread another poster said the same version of TWRP that I linked to above works for 4.4.2
http://forum.xda-developers.com/showthread.php?t=2646361
Click to expand...
Click to collapse
Updated to 4.4, unlocked boot loader steps waiting for email from Motorola. Wondering, if all I want to do is root and I don't want to put a custom ROM in do I need a custom recovery? Or is that just part of the necessary step to get the SU on.
Thanks, Ed,
gencode said:
Updated to 4.4, unlocked boot loader steps waiting for email from Motorola. Wondering, if all I want to do is root and I don't want to put a custom ROM in do I need a custom recovery? Or is that just part of the necessary step to get the SU on.
Click to expand...
Click to collapse
As I understand it, you can root without installing a custom recovery, but you do have to boot into a custom recovery to install SU.
See this thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2439536
I am not sure of the benefits of actually installing the custom recovery other than ROMing, but there may be other benefits that I don't know about.
Ok, hope I don't get too much heat over this, my old device was a Samsung with unlocked bootloader, so everything was easily flashed.
Anyway, as to the best order of things, I'm still on AT&T 4.2.2 pre camera update, so I easily rooted with with pwnmymoto. I have Xposed installed with a few modules.
For the unlock steps -looks like this is the best guide: http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394 and using: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
Q: Is my recovery from pwnmymoto "stock" as it needs to be for unlocking process?
Can I just uncheck/disable the modules I have with xposed, or do I need to delete the framework? (which sounds like the only way is to use RSD to install the original ROM?)
Should I also unfreeze any files? (I think I only froze the one's related to motorola OTA)
My intent is to get to 4.4.2, and I know it's optimal to remove things from pwnmymoto (I know unlocking will wipe everything but my ROM), so probably after I've installed TWRP and rooted, to flash the file for AT&T 4.4.2 http://forum.xda-developers.com/moto-x/general/-t2688009 or does it need to be incremental, as I'm on 4.2 (i.e flash 4.2 camera update, then 4.4, etc.) -sorry if I seem a bit confused
Thanks in advance! any and all help is very much appreciated!
Hopefully not too many questions -if any has the best suggestion for any, would be great
M973 said:
Hopefully not too many questions -if any has the best suggestion for any, would be great
Click to expand...
Click to collapse
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
drago10029 said:
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
Click to expand...
Click to collapse
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
M973 said:
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
Click to expand...
Click to collapse
np problem bro, happy rooting! may the flash be ever in your favor
I just bought a VZW Moto X non-dev edition that already came with unlocked bootloader (the seller told me and i confirmed it). The version is 4.4.2.
I could go into TWRP and install SuperSU v1.93. However, after rebooting, my phone still says it's not rooted. What have I done wrong?
X_Fact0r said:
I just bought a VZW Moto X non-dev edition that already came with unlocked bootloader (the seller told me and i confirmed it). The version is 4.4.2.
I could go into TWRP and install SuperSU v1.93. However, after rebooting, my phone still says it's not rooted. What have I done wrong?
Click to expand...
Click to collapse
TWRP does not install SuperSU....it installs "SuperSu Installer".
You need to look in your app drawer and find "SuperSu Installer", and run it. It will give you 2 options to install: choose "Play Store" option. Afterwards, you should be all set.
If you were able to install TWRP, your bootloader is indeed unlocked.
samwathegreat said:
TWRP does not install SuperSU....it installs "SuperSu Installer".
You need to look in your app drawer and find "SuperSu Installer", and run it. It will give you 2 options to install: choose "Play Store" option. Afterwards, you should be all set.
If you were able to install TWRP, your bootloader is indeed unlocked.
Click to expand...
Click to collapse
Hmm interesting. I couldn't find SuperSu Installer in my app drawer. Do I have to go into TWRP and install this file "UPDATE-SuperSU-v1.93.zip" first in order to see SuperSU Installer?
I actually did that too and still could not find SuperSU Installer. Any help is appreciated!
Edit: I guess what I'm trying to ask is how to root my moto X.
X_Fact0r said:
Hmm interesting. I couldn't find SuperSu Installer in my app drawer. Do I have to go into TWRP and install this file "UPDATE-SuperSU-v1.93.zip" first in order to see SuperSU Installer?
I actually did that too and still could not find SuperSU Installer. Any help is appreciated!
Click to expand...
Click to collapse
If you aren't already rooted, when you boot into TWRP and press "REBOOT" and then "SYSTEM", it should pop-up with a message saying something to the effect of: "Your device is not currently rooted. Would you like to install SuperSU-Installer?
Which version of TWRP are you using? AFAIK, only versions 2.6.3.1 and LATER will automatically install SuperSU-Installer for you....
samwathegreat said:
If you aren't already rooted, when you boot into TWRP and press "REBOOT" and then "SYSTEM", it should pop-up with a message saying something to the effect of: "Your device is not currently rooted. Would you like to install SuperSU-Installer?
Which version of TWRP are you using? AFAIK, only versions 2.6.3.1 and LATER will automatically install SuperSU-Installer for you....
Click to expand...
Click to collapse
I have TWRP 2.7.1.1. I just did what you said in TWRP but it rebooted right back to the lockscreen without asking to install SuperSU. By the way, I'm currently on 4.4.2. I'm not sure if that makes any difference.
samwathegreat said:
If you aren't already rooted, when you boot into TWRP and press "REBOOT" and then "SYSTEM", it should pop-up with a message saying something to the effect of: "Your device is not currently rooted. Would you like to install SuperSU-Installer?
Which version of TWRP are you using? AFAIK, only versions 2.6.3.1 and LATER will automatically install SuperSU-Installer for you....
Click to expand...
Click to collapse
This is what mine did too
X_Fact0r said:
I have TWRP 2.7.1.1. I just did what you said in TWRP but it rebooted right back to the lockscreen without asking to install SuperSU. By the way, I'm currently on 4.4.2. I'm not sure if that makes any difference.
Click to expand...
Click to collapse
Ah ha! That must be the issue. The NEW version (2.7.1.1) of TWRP is Official. The previous versions we were using were not from the official TWRP team. It would seem they took out the functionality I was referring to.
We will get you fixed right up though....
Head over to Chainfire's website: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
And click the download button for the latest version (1.99r4)
Flash the file from TWRP. Now you should be all set
samwathegreat said:
Ah ha! That must be the issue. The NEW version (2.7.1.1) of TWRP is Official. The previous versions we were using were not from the official TWRP team. It would seem they took out the functionality I was referring to.
We will get you fixed right up though....
Head over to Chainfire's website: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
And click the download button for the latest version (1.99r4)
Flash the file from TWRP. Now you should be all set
Click to expand...
Click to collapse
Just flashed that file from TWRP but still no root access ...Would I be able to just flash the earlier TWRP version and repeat the reboot system step to install supersu installer?
X_Fact0r said:
Just flashed that file from TWRP but still no root access ...Would I be able to just flash the earlier TWRP version and repeat the reboot system step to install supersu installer?
Click to expand...
Click to collapse
Hmmm....do you have an icon for "SuperSU" in your app drawer at all? I haven't seen the flash fail to install SuperSU.
If you can confirm that no icon is present for SuperSU, I can help you with flashing the older version of TWRP and SuperSU. Let me know...
samwathegreat said:
Hmmm....do you have an icon for "SuperSU" in your app drawer at all? I haven't seen the flash fail to install SuperSU.
If you can confirm that no icon is present for SuperSU, I can help you with flashing the older version of TWRP and SuperSU. Let me know...
Click to expand...
Click to collapse
Nope, no SuperSU icon.
X_Fact0r said:
Nope, no SuperSU icon.
Click to expand...
Click to collapse
OK, something strange is going on. I checked the other threads, and the TWRP version you mentioned, and the SuperSU version I linked are the suggested versions, and have been confirmed to work....
Lets assume this is just a fluke...
Download either Flashify or Rashr from the market
(OR just use mfastboot commands...)
And flash TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Afterwards, do as instructed in my earlier posts. Does TWRP offer to install SuperSU Installer?
samwathegreat said:
OK, something strange is going on. I checked the other threads, and the TWRP version you mentioned, and the SuperSU version I linked are the suggested versions, and have been confirmed to work....
Lets assume this is just a fluke...
Download either Flashify or Rashr from the market
(OR just use mfastboot commands...)
And flash TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Afterwards, do as instructed in my earlier posts. Does TWRP offer to install SuperSU Installer?
Click to expand...
Click to collapse
Will do! By the way, on bootloader page, it says "Device is unlocked. Status code: 3"
samwathegreat said:
OK, something strange is going on. I checked the other threads, and the TWRP version you mentioned, and the SuperSU version I linked are the suggested versions, and have been confirmed to work....
Lets assume this is just a fluke...
Download either Flashify or Rashr from the market
(OR just use mfastboot commands...)
And flash TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Afterwards, do as instructed in my earlier posts. Does TWRP offer to install SuperSU Installer?
Click to expand...
Click to collapse
I just downloaded Flashify. It says "for root users." I don't think my phone is rooted though. Will flashify work?
X_Fact0r said:
Will do! By the way, on bootloader page, it says "Device is unlocked. Status code: 3"
Click to expand...
Click to collapse
Great, that means that you are definitely BL-unlocked (Status code: 3 is correct), and you WILL be rooted very soon. Once we get to the bottom of this...
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
X_Fact0r said:
I just downloaded Flashify. It says "for root users." I don't think my phone is rooted though. Will flashify work?
Click to expand...
Click to collapse
Nope...I'm a dumbass (forgot root required to flash recovery from app)
you will have to use mfastboot. Do you have the android SDK and mfastboot binary installed? (On your PC?) Here is a the best guide I have found (if you don't have them): http://mark.cdmaforums.com/ADB.htm
samwathegreat said:
Great, that means that you are definitely BL-unlocked (Status code: 3 is correct), and you WILL be rooted very soon. Once we get to the bottom of this...
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
Nope...I'm a dumbass (forgot root required to flash recovery from app)
you will have to use mfastboot. Do you have the android SDK and mfastboot binary installed?
Click to expand...
Click to collapse
Yes, I do. Just went back to 2.6.3.1. Hit reboot -> system but it didn't ask me to install supersu installer. I must have done something wrong earlier
I opened Flashify and it said the phone had root but it could not access SuperSU.
I have to step away from the computer a bit. I'll be back in a couple hours..
X_Fact0r said:
Yes, I do. Just went back to 2.6.3.1. Hit reboot -> system but it didn't ask me to install supersu installer. I must have done something wrong earlier
I opened Flashify and it said the phone had root but it could not access SuperSU.
I have to step away from the computer a bit. I'll be back in a couple hours..
Click to expand...
Click to collapse
Sure...when you return, try flashing the new version of SuperSU I linked from within the TWRP version you just flashed.
If this doesn't work, I may have a hunch on what MAY be going on. It is possible that the previous owner was using a root exploit + safestrap + MotoWpNoMo originally, then later had the BL unlocked and did not SBF back to stock firmware. This would explain why the updates you are flashing from TWRP are not being applied for some reason.
If you try flashing the new version of SuperSU from the TWRP version you just installed (2.6.3.1), and it STILL does not work, I highly suggest SBFing back to stock 4.4.2.
Follow the "Return to Stock" thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 VZW SBF from here: http://sbf.droid-developers.org/phone.php?device=0
After you have "SBF'd" back to stock, any changes/exploits that the previous owner had used OR any corruption in the filesystem should be repaired. Afterwards, I almost -guarantee- that the methods I listed early in the thread WILL work.
samwathegreat said:
Sure...when you return, try flashing the new version of SuperSU I linked from within the TWRP version you just flashed.
If this doesn't work, I may have a hunch on what MAY be going on. It is possible that the previous owner was using a root exploit + safestrap + MotoWpNoMo originally, then later had the BL unlocked and did not SBF back to stock firmware. This would explain why the updates you are flashing from TWRP are not being applied for some reason.
If you try flashing the new version of SuperSU from the TWRP version you just installed (2.6.3.1), and it STILL does not work, I highly suggest SBFing back to stock 4.4.2.
Follow the "Return to Stock" thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 VZW SBF from here: http://sbf.droid-developers.org/phone.php?device=0
After you have "SBF'd" back to stock, any changes/exploits that the previous owner had used OR any corruption in the filesystem should be repaired. Afterwards, I almost -guarantee- that the methods I listed early in the thread WILL work.
Click to expand...
Click to collapse
Many thanks!!!! everything worked properly and my phone is now rooted. Thanks again!!
samwathegreat said:
Sure...when you return, try flashing the new version of SuperSU I linked from within the TWRP version you just flashed.
If this doesn't work, I may have a hunch on what MAY be going on. It is possible that the previous owner was using a root exploit + safestrap + MotoWpNoMo originally, then later had the BL unlocked and did not SBF back to stock firmware. This would explain why the updates you are flashing from TWRP are not being applied for some reason.
If you try flashing the new version of SuperSU from the TWRP version you just installed (2.6.3.1), and it STILL does not work, I highly suggest SBFing back to stock 4.4.2.
Follow the "Return to Stock" thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 VZW SBF from here: http://sbf.droid-developers.org/phone.php?device=0
After you have "SBF'd" back to stock, any changes/exploits that the previous owner had used OR any corruption in the filesystem should be repaired. Afterwards, I almost -guarantee- that the methods I listed early in the thread WILL work.
Click to expand...
Click to collapse
So I'm trying to install a custom ROM. I have the retail edition VZW Moto X with unlocked bootloader. When I install the ROM, should I follow the instructions for the dev edition or retail edition?
X_Fact0r said:
So I'm trying to install a custom ROM. I have the retail edition VZW Moto X with unlocked bootloader. When I install the ROM, should I follow the instructions for the dev edition or retail edition?
Click to expand...
Click to collapse
You will use dev edition instructions. Now that you are bootloader-unlocked, you own an 'unofficial' dev edition (for all practical purposes).
Have fun
hope someone can help.i have a vzn dev ed thats bootloader unlock and rooted on 4.4.2 but every time i turn off the phone and turn it back on root is gone and i would have to root again. if anyone can help me out it would be great. thanks in advance for any help
Did you use PIE root method?
Sent from my XT1060 using Tapatalk
i flash recovery twrp with moto toolkit the first time and it work but when i reboot i would lose root.then i try towelroot it would give me root again but if i reboot i would lose root. anyway to solve this would be great. thanks in advance
If you can boot into recovery (twrp) just flash the su zip, if you search the forums or Google you will find a link
You used a toolkit to flash recovery and root the phone? In the time it took to download and get the toolkit ready, you probably could have downloaded mfastboot, recovery, and a superuser zip and had all of them flashed and no issues.
i8rice said:
hope someone can help.i have a vzn dev ed thats bootloader unlock and rooted on 4.4.2 but every time i turn off the phone and turn it back on root is gone and i would have to root again. if anyone can help me out it would be great. thanks in advance for any help
Click to expand...
Click to collapse
If you are using a tool kit, I have to ask.. Have you visited Moto's web site, requested the unlock code for your phone, and actually used it (mfastboot oem unlock uniquecode)?
If you have a developer edtion, consider this... Don't use the tool kit, instead...
Install Android Platform Tools, ADB, mFastboot and the Moto drivers by following -> http://mark.cdmaforums.com/ADB.htm
Root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 however, since it was written some time ago, get and use the newest TWRP from -> http://techerrata.com/browse/twrp2/ghost and get the newest SuperSU from -> http://download.chainfire.eu/supersu and copy it to the /SDCard in your phone (or just download it from the browser on your phone so its in /sdcard/download folder before you start)... Use these versions when following that process.
If you already got your unlock code from Moto's web site and used it, then you can skip step 1.
And step 5 should be started with the phone UNPLUGGED.
thanks for all the reply. i have it unlock by Moto's web site with the code.i have twrp 2711 and everything flash fine. i flash with the new su 2.0 in twrp2.7.1.1 it said flash successful but when it boots up i still have no root. i use rsd lite and flash Google Play Edition 4.4.2, by Q9Nap where the rom is already rooted. root work fine until i reboot i would lose root again.thanks in advance for any and all the help
i8rice said:
thanks for all the reply. i have it unlock by Moto's web site with the code.i have twrp 2711 and everything flash fine. i flash with the new su 2.0 in twrp2.7.1.1 it said flash successful but when it boots up i still have no root. i use rsd lite and flash Google Play Edition 4.4.2, by Q9Nap where the rom is already rooted. root work fine until i reboot i would lose root again.thanks in advance for any and all the help
Click to expand...
Click to collapse
Did you ever try to downgrade to 4.4 and use something like slapmymoto or MotoWpNoMo or something before?
Either way, based on the past seeing similar symptoms.. I would consider downloading the stock verizon 4.4.2 SBF and then follow Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html to get back to stock, then try TWRP and SuperSU again. (and yes there are a few lines/commands repeated there, that is intentional)
Heard of this another time....but can't find the thread. All signs for that person was bootloader unlocked and write protection still enabled.