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.
Related
Got the OTA for 4.4, how do I apply that to custom recovery? Or do I have to wait till it comes in a downloadable zip and flash it in custom recovery?
tluley51 said:
Got the OTA for 4.4, how do I apply that to custom recovery? Or do I have to wait till it comes in a downloadable zip and flash it in custom recovery?
Click to expand...
Click to collapse
Are you on a VZW Developer Edition (unlocked)?
defsquad said:
Are you on a VZW Developer Edition (unlocked)?
Click to expand...
Click to collapse
No sir. Safestrap on regular version, 16gb
tluley51 said:
No sir. Safestrap on regular version, 16gb
Click to expand...
Click to collapse
there is no way to maintain root and take the 4.4 currently unless you have a dev phone or unlockable bootloader
bummer, was thinking that if on rooted VZW Developer Edition you could OTA update then reboot into recovery and install Su again (with TWRP for instance).
defsquad said:
bummer, was thinking that if on rooted VZW Developer Edition you could OTA update then reboot into recovery and install Su again (with TWRP for instance).
Click to expand...
Click to collapse
if you have a dev edition then you can get root because you have an unlocked BL.
jayboyyyy said:
if you have a dev edition then you can get root because you have an unlocked BL.
Click to expand...
Click to collapse
sorry for the ignorance, but do you happen to have the steps after unlocking the bootloader to install root? I have the dev edition and just upgraded to 4.4 and am interested in gaining root.
schmoe0013 said:
sorry for the ignorance, but do you happen to have the steps after unlocking the bootloader to install root? I have the dev edition and just upgraded to 4.4 and am interested in gaining root.
Click to expand...
Click to collapse
same way you did on the last update you did. you may have to wait a sec if the su and cwm hasn't been udpated to 4.4 but i think it has so you should be able to get root the exact same way you got rot when you took the 4.2.2 OTA
jayboyyyy said:
same way you did on the last update you did. you may have to wait a sec if the su and cwm hasn't been udpated to 4.4 but i think it has so you should be able to get root the exact same way you got rot when you took the 4.2.2 OTA
Click to expand...
Click to collapse
I have yet to perform any such activity.
With some googling, I am estimating the process to be something along the lines of:
unlock bootloader via motorola site
install cwm?
push su app to system
victory?
I have development background but have not kept up recently with process of these things.
jayboyyyy said:
there is no way to maintain root and take the 4.4 currently unless you have a dev phone or unlockable bootloader
Click to expand...
Click to collapse
Okay, so to take the update, I have to unroot and flash stock recovery?
tluley51 said:
Okay, so to take the update, I have to unroot and flash stock recovery?
Click to expand...
Click to collapse
be careful how you do it
I tried that, along with some other things, and apparently it didnt work
alex94kumar said:
be careful how you do it
I tried that, along with some other things, and apparently it didnt work
Click to expand...
Click to collapse
I cheated...I used a toolkit and it did it all for me. Downloading the OTA now and hopefully it gets me all set
tluley51 said:
I cheated...I used a toolkit and it did it all for me. Downloading the OTA now and hopefully it gets me all set
Click to expand...
Click to collapse
Which toolkit?
schmoe0013 said:
sorry for the ignorance, but do you happen to have the steps after unlocking the bootloader to install root? I have the dev edition and just upgraded to 4.4 and am interested in gaining root.
Click to expand...
Click to collapse
To unlock the boot loader I went to the Motorola website and did it.
Sent from my XT1060 using xda app-developers app
schmoe0013 said:
I have yet to perform any such activity.
With some googling, I am estimating the process to be something along the lines of:
unlock bootloader via motorola site
install cwm?
push su app to system
victory?
I have development background but have not kept up recently with process of these things.
Click to expand...
Click to collapse
all sounds good to me. sorry if someone answered you already and this is a repost. but that sounds accurate.
Having trouble finding which method is best for me
nvertigo said:
Having trouble finding which method is best for me
Click to expand...
Click to collapse
Unlock bootloader. Flash twrp 2.6.3.1 for 4.4. Flash latest supersu. Profit.
Sent from my iPhone
phositadc said:
Sent from my iPhone
Click to expand...
Click to collapse
^↑^^^^^^^^^???↑f↑a↑i↑l↑
Funny your using A fruitbox to post in a moto x forum!
Sent from my XT1058 using XDA Premium 4 mobile app
matt99017d said:
^↑^^^^^^^^^???↑f↑a↑i↑l↑
Funny your using A fruitbox to post in a moto x forum!
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've also got a Moto x and a Nexus 5
Sent from my XT1053
still haven't gotten there
I've spent hours on unlocking and rooting my vzw developer's edition. First, the SDK that motorola tells you to download to get fastboot doesn't include fastboot! There are a few ways to get it, but following Motorola's instructions won't get you there. (thanks so much Motorola for posting a solution that doesn't work).
Do Not install the OTA update....if you do, you will not be able to root your phone and you will have to reinstall the stock drivers. It's easy to do, but it will take hours for you to realize that you have to do this. If you have the OTA update already installed, get rid of it by installing the drivers from the motorola site for the developer edition phone (VZW).
You do not need to download the sidekick package that motorola tells you to download in order to unlock your phone. In fact, if you do install it, you still won't have fastboot which is the program you need. Motorola left it out of the most recent sdk. Don't even bother to find another sdk or fastboot....just find TWRP 2.6.3.1 which is a zipped package findable in many places (google is your friend). Unzip that package and voila....there's fastboot and the dll's to support it.
Now,, no thanks to Motorola, you are ready to get the unlock from your phone so you can ask motorola for the unlock key from motorola using fastboot.
note: fastboot is a CMD application! If you just click on it, it will flash the cmd box and seem to do nothing. You have to open cmd and then find/execute fastboot from there. It's an ugly process....thank you again Motorola.
Once your phone is unlocked, you can use the 1 step install for TWRP.
I realize I should write this up with every step...but I've spent almost two days on something that should take about 15 minutes...and I'm not exactly a newby to this stuff. Motorola just made it as hard as possible to do something that's so simple.
After you have root can you then update to kitkat or will you lose root then?
johnh123 said:
After you have root can you then update to kitkat or will you lose root then?
Click to expand...
Click to collapse
If you have a dev edition on kitkat it's as simple as flashing TWRP and then superSU binary
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
ghstudio said:
I've spent hours on unlocking and rooting my vzw developer's edition. First, the SDK that motorola tells you to download to get fastboot doesn't include fastboot! There are a few ways to get it, but following Motorola's instructions won't get you there. (thanks so much Motorola for posting a solution that doesn't work).
Do Not install the OTA update....if you do, you will not be able to root your phone and you will have to reinstall the stock drivers. It's easy to do, but it will take hours for you to realize that you have to do this. If you have the OTA update already installed, get rid of it by installing the drivers from the motorola site for the developer edition phone (VZW).
You do not need to download the sidekick package that motorola tells you to download in order to unlock your phone. In fact, if you do install it, you still won't have fastboot which is the program you need. Motorola left it out of the most recent sdk. Don't even bother to find another sdk or fastboot....just find TWRP 2.6.3.1 which is a zipped package findable in many places (google is your friend). Unzip that package and voila....there's fastboot and the dll's to support it.
Now,, no thanks to Motorola, you are ready to get the unlock from your phone so you can ask motorola for the unlock key from motorola using fastboot.
note: fastboot is a CMD application! If you just click on it, it will flash the cmd box and seem to do nothing. You have to open cmd and then find/execute fastboot from there. It's an ugly process....thank you again Motorola.
Once your phone is unlocked, you can use the 1 step install for TWRP.
I realize I should write this up with every step...but I've spent almost two days on something that should take about 15 minutes...and I'm not exactly a newby to this stuff. Motorola just made it as hard as possible to do something that's so simple.
Click to expand...
Click to collapse
On a VZW dev edition? Just unlock it at any time kitkat or not, then flash TWRP and then superSU binary, it's as easy as that
Rooting the VZW dev edition moto x is EASY.
Go ahead and install all OTA updates.
Download and install latest Android SDK (comes with adb and fastboot).
Unlock bootloader following instructions on moto's website
Download TWRP and flash using fastboot
Boot into recovery and make a nandroid backup
Reboot phone from TWRP. It will ask if you would like to install superuser and root phone.
done.
adtnry senate
teookie said:
Rooting the VZW dev edition moto x is EASY.
Go ahead and install all OTA updates.
Download and install latest Android SDK (comes with adb and fastboot).
Unlock bootloader following instructions on moto's website
Download TWRP and flash using fastboot
Boot into recovery and make a nandroid backup
Reboot phone from TWRP. It will ask if you would like to install superuser and root phone.
done.
Click to expand...
Click to collapse
Sorry teooki....it SHOULD be easy, but it isn't. Fastboot is NOT included in the SDK that motorola has you download on their unlock page. Yes, it's included on other sites, but not on the one that Motorola distributes. So if you follow their directions, you can't find fastboot, etc.
Your direction should work....Motorola's don't.
I followed Moto's instructions and it worked without issue (Except one of my own making).
homemadehitshow said:
I followed Moto's instructions and it worked without issue (Except one of my own making).
Click to expand...
Click to collapse
If you download the sidekick today, it downloads V1.7 and it does not contain fastboot and the two dll's needed. Earlier, they were giving V1.6 which was complete. This is a new issue with V1.7...and it's something that new users or those who are trying to unlock/root their phones will find incredibly annoying.
(hopefully, they have fixed the Motorola delivered v1.7, but last week, it did not include those files).
I've rooted every phone I've ever owned but I'm having second thoughts on the X. I want to continue to get the ota updates, and with root, that isn't possible is it?
Sent from my Nexus 7 using Tapatalk
RyanTX said:
I've rooted every phone I've ever owned but I'm having second thoughts on the X. I want to continue to get the ota updates, and with root, that isn't possible is it?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It's really easy to unroot then root again (on the developer edition)
Rooting by itself won't stop OTA updates. Installing a custom ROM not based on stock firmware will though.
You might have to re-root after getting an OTA update though.
Sent from my XT1060 using Tapatalk
Thanks guys, got unlocked, rooted, and gravitybox all set up!.
So you guys are saying we can accept OTAs while stock rooted? Should I uninstall xposed before doing an OTA?
edit: sorry, don't know why double post happened...
ghstudio said:
Sorry teooki....it SHOULD be easy, but it isn't. Fastboot is NOT included in the SDK that motorola has you download on their unlock page. Yes, it's included on other sites, but not on the one that Motorola distributes. So if you follow their directions, you can't find fastboot, etc.
Your direction should work....Motorola's don't.
Click to expand...
Click to collapse
Just to clarify, it seems that you must use Motorola's version of fastboot, not the one included in the SDK. I used the SDK version to flash TWRP several times, and each time it appeared to be successful, but it was not. Then I discovered that I needed Motorola's fastboot, found it on the forums here, and used it to flash TWRP. That worked.
Hi All,
I just got a new X yesterday and it's running 4.2.2. I heard there's a root method for 4.4 so I'm wondering if it's better to root now, then flash a stock 4.4 ROM or take the OTA to 4.4 and then root?
amghoon said:
Hi All,
I just got a new X yesterday and it's running 4.2.2. I heard there's a root method for 4.4 so I'm wondering if it's better to root now, then flash a stock 4.4 ROM or take the OTA to 4.4 and then root?
Click to expand...
Click to collapse
the 4.4 root process starts on 4.2.2 check out the guide here
http://forum.xda-developers.com/showthread.php?t=2603358
use the guide for Locked bootloaders that should get you started let me know if you have any issues
dray_jr said:
the 4.4 root process starts on 4.2.2 check out the guide here
http://forum.xda-developers.com/showthread.php?t=2603358
use the guide for Locked bootloaders that should get you started let me know if you have any issues
Click to expand...
Click to collapse
Does this guide work for the Verizon moto x? In step one it seems to imply that it only works for Sprint and AT&T. I apologize if this is a dumb question however I just want to make sure before I start.
Thanks
mamba94 said:
Does this guide work for the Verizon moto x? In step one it seems to imply that it only works for Sprint and AT&T. I apologize if this is a dumb question however I just want to make sure before I start.
Thanks
Click to expand...
Click to collapse
the guide is created for all Moto X i just uploaded some complete packages for atnt and sprint just never finished uploading the others
dray_jr said:
the guide is created for all Moto X i just uploaded some complete packages for atnt and sprint just never finished uploading the others
Click to expand...
Click to collapse
Oh okay understood!
Thanks for responding I appreciate it.
mamba94 said:
Oh okay understood!
Thanks for responding I appreciate it.
Click to expand...
Click to collapse
np good luck mate
dray_jr said:
the 4.4 root process starts on 4.2.2 check out the guide here
http://forum.xda-developers.com/showthread.php?t=2603358
use the guide for Locked bootloaders that should get you started let me know if you have any issues
Click to expand...
Click to collapse
Thanks for putting that together dray; I had one question about installing TWRP. It seems like this is the case based on the instructions, but I wanted to be sure, is it OK to install the twrp-2.6.3.1-ghost-4.4.img even though I am running 4.2.2?
I have my bootloader unlocked already (VZW DE and gone through that process via adb) and have been trying to figure out which custom recovery to flash.
TIA
DuvelDroid said:
Thanks for putting that together dray; I had one question about installing TWRP. It seems like this is the case based on the instructions, but I wanted to be sure, is it OK to install the twrp-2.6.3.1-ghost-4.4.img even though I am running 4.2.2?
I have my bootloader unlocked already (VZW DE and gone through that process via adb) and have been trying to figure out which custom recovery to flash.
TIA
Click to expand...
Click to collapse
yea that is fine
DuvelDroid said:
Thanks for putting that together dray; I had one question about installing TWRP. It seems like this is the case based on the instructions, but I wanted to be sure, is it OK to install the twrp-2.6.3.1-ghost-4.4.img even though I am running 4.2.2?
I have my bootloader unlocked already (VZW DE and gone through that process via adb) and have been trying to figure out which custom recovery to flash.
TIA
Click to expand...
Click to collapse
did you get the twrp-2.6.3.1-ghost-4.4.img to flash successfully on 4.2.2 on your Dev edition?
I used mfastboot to flash it and when I try to go to recovery it just boots to Android/
drozek said:
did you get the twrp-2.6.3.1-ghost-4.4.img to flash successfully on 4.2.2 on your Dev edition?
I used mfastboot to flash it and when I try to go to recovery it just boots to Android/
Click to expand...
Click to collapse
alot of people had this issue reinstall TWRP then then use the volume - button and highlight recovery then press the volume + button and it should boot into recovery
dray_jr said:
alot of people had this issue reinstall TWRP then then use the volume - button and highlight recovery then press the volume + button and it should boot into recovery
Click to expand...
Click to collapse
Awesome thanks!
It's your vz still on 4.2.2? If so, will you please see what the boot loader version is?
Thanks
Sent from my XT1060 using Tapatalk
drozek said:
did you get the twrp-2.6.3.1-ghost-4.4.img to flash successfully on 4.2.2 on your Dev edition?
I used mfastboot to flash it and when I try to go to recovery it just boots to Android/
Click to expand...
Click to collapse
Yeah, as dray_jr mentioned, after you flash it, you have to select recovery rather than rebooting.
This video also helped me (youtube.com/watch?v=sw675ipX-ds) (I don't have enough posts to hyperlink).
I actually followed the video but dray's instructions are the same process.
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can't downgrade now due to the bootloader update.
KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
KidJoe said:
Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
Not to nag, but probably important to correct... you CAN'T downgrade now.
Updated last night. I did it cause I wanted to be on latest and greatest, plus I think the camera does take better low-light pictures now.
Schaweet said:
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
Not much different, you can always update everything but motoboot and gpt so you can still downgrade if you don't like...
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
FWIW, The only things I notice are that USB OTG works in 4.4.2 and static in bluetooth headphones when using wifi is gone.
Schaweet said:
You don't have root unless you put the custom recovery back on there.
Click to expand...
Click to collapse
I beg to differ. Root Explore, Greenify, Wifi Tether for Root... all work, as do going into system and renaming files, and downloading/installing the hosts file in AdAway from BigTinCan.com (which survive power off/on, so helps to tell me write protection is still disabled).
On an unlocked bootloader, once you have rooted, you can use whatever recovery you like.
Now, for LOCKED bootloader on the X which are rooted via RockMyMoto or SlapMyMoto without using MotoWPNoMo, you might need to keep that "recovery trick" in place so you can boot with write protect disabled. In that case you would loose the ability to boot with write protect disabled (which makes root useless) when you put stock recovery back on, but that is different and doesn't "unroot" you.
---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------
Mike7143 said:
Not to nag, but probably important to correct... you CAN'T downgrade now.
Click to expand...
Click to collapse
You are right. that is a Typo that I need to fix!!!
cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
It took me about an hour to do the update because I am a novice and had to do a bunch of stuff first but I did it and my phone is back to its current state...except now I am using the xposed wifi tether instead of the hack (And the xposed one is better). So it was worth it just to have the latest and get rid of that wifi mod that i never liked to begin with. Apparently the upate makes battery life better but my battery life was already awesome considering I came from Gnex. So I guess the question is why not update? If you know what you are doing it shouldnt take 5-10 minutes.
from what people are saying it seems 4.4.2 makes a huge difference for battery life, i don't have it yet on my xt1058 so i can't say for sure...
Yeah I really only root for the tether hack and tibackup. Both of which I've used less and less since I got this phone. I've never had any issues with the phone and battery life is awesome so I'll probably just wait for some more feedback on the update before I go through the hassle of doing it.
How do you get rid of the unlocked bootloader message? Just flashing logo.bin?
jawest12 said:
How do you get right of the unlocked bootloader message? Just flashing logo.bin?
Click to expand...
Click to collapse
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
CartlandSmith said:
If you are rooted and locked on 4.4 using SlapMyMoto and MotoWPNoMo, can you downgrade to 4.2.2 and use PwnMyMoto then RockMyMoto then SlapMyMoto 0.5c to get the "recovery trick" back? Or is the ability to do that gone once you have used MotoWPNoMo?
Click to expand...
Click to collapse
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
KidJoe said:
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
Click to expand...
Click to collapse
Thank you for the response. Where can I download your logo.bin to flash?
tcrews said:
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
Click to expand...
Click to collapse
For a n00b,,,,,English please?!
jawest12 said:
Thank you for the response. Where can I download your logo.bin to flash?
Click to expand...
Click to collapse
See the "edit" section of Post #150 in this thread -> Moto X Boot Logos The post also has info how they were made and a link to a zip that contains a little more than 25 LOGO.BIN files, and matching BMP's so you can see what they look like first (or use to flash clogo if you have never unlocked your bootloader). they do include the 0-3% battery indication too.
I'm using Logo-prettydev2.png.bin included in the zip file.
PennyKnight said:
For a n00b,,,,,English please?!
Click to expand...
Click to collapse
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
tcrews said:
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
Click to expand...
Click to collapse
Also for noobs, how do I flash the stock recovery?
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
zackiv31 said:
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
No. Flashing Recovery does NOT erase data. Using RSDLite to flash an entire SBF/XML file (without editing it) will erase data.. or giving the following command via PC with your phone in fastboot mode will erase data... mfastboot erase data
KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
How do I undo the entitlement apk. I tried to reverse it but messed it up.
Not good at that stuff.
Thanks
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
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.