I bought the T-Mobile version (on AT&T) and received it yesterday, based on the numerous threads that seemed to be the best option for me. I've been unlocking, rooting, and flashing the previous 3 Android phones and have yet to brick or "damage" any of them (knock on wood). Not too worried about voiding warranty since unfortunately they sold out of DE early on.
Originally, all I wanted to do was root. Though, I should have read more carefully before accepting the 4.4 OTA, chalk it up to "new phone" excitement. Seems like you needed to remain on 4.2.2. to root and THEN updating to 4.4. Decided to go ahead and unlock the bootloader and rooting the "traditional" method. Worked fine. Unlocked bootloader, flashed TWRP, and installed SuperSU. Profit. Thanks to the all the helpful people here.
I plan to stay on stock with the Moto X...for the first time ever with an Android device. Will I be able to accept future OTA updates? From what I've interpreted, I can't because I no longer have stock recovery, is that correct? If that is the case, what would I have to do to "keep up" with future official OTA updates?
Despite unlocking, rooting, and flashing previous phones - I've realized that this is far more complicated than I thought for a layman like myself.
It is still possible, and should remain so, that you can flash OTAs using CWM or TWRP recovery while rooted if you have not made any changes to system apps. I just updated my rooted, stock rom & kernel N7 with TWRP recovery to Kitkat 4.2.2. After updating successfully, I just restored TWRP with a fastboot flash of the twrp recovery image and used TWRP to flash SuperSU 1.8. to restore root. It all worked perfectly, but I had to unfreeze a couple of apps and uninstall the AOSP root browser app. After updating, I reinstalled the AOSP browser and all is well.
Groid said:
It is still possible, and should remain so, that you can flash OTAs using CWM or TWRP recovery while rooted if you have not made any changes to system apps. I just updated my rooted, stock rom & kernel N7 with TWRP recovery to Kitkat 4.2.2. After updating successfully, I just restored TWRP with a fastboot flash of the twrp recovery image and used TWRP to flash SuperSU 1.8. to restore root. It all worked perfectly, but I had to unfreeze a couple of apps and uninstall the AOSP root browser app. After updating, I reinstalled the AOSP browser and all is well.
Click to expand...
Click to collapse
someone will have to provide the OTA zip file for us to flash throu twrp right? we wont be able to install the OTA right on the phone like normally.
claudiuslu2011 said:
someone will have to provide the OTA zip file for us to flash throu twrp right? we wont be able to install the OTA right on the phone like normally.
Click to expand...
Click to collapse
You can't flash the ota with twrp recovery, it will bootloop, other have tried it and always goes south, unlike the previous person who had a nexus 7 , the moto x is a different beast. We do have access to the firmware which you can flash with rsdlite but it wipes the phone, wipes recovery and puts the phone back to original specs
Sent on my Moto X
Related
Hello, I would very much appreciate any help provided.
I just got a moto x developer edition gsm. I'll be using it on tmobile.
I've rooted lots of android phones and have never had this many problems. I tried a lot of different things on these forums and have had some success but i'm stuck now.
I was able to unlock the bootloader using motorola's site. I also have TWRP recovery installed (2.6.3.1). Currently the phone has 4.2.2 (build 13.9.0Q2.x-116-x-17-57) and its rooted, working fine.
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails.
I'm not totally sure if the rom i'm on now is the same one that the phone came with. The rom that's on it now was obtained from this page:
http://sbf.droid-developers.org/phone.php?device=0
(Android 4.2.2 Blur_Version.139.12.57.ghost_row.Retail.en.US) for t-mobile US
Please help me be able to update to 4.4 and ideally keep root.
Jay10826 said:
Hello, I would very much appreciate any help provided.
I just got a moto x developer edition gsm. I'll be using it on tmobile.
I've rooted lots of android phones and have never had this many problems. I tried a lot of different things on these forums and have had some success but i'm stuck now.
I was able to unlock the bootloader using motorola's site. I also have TWRP recovery installed (2.6.3.1). Currently the phone has 4.2.2 (build 13.9.0Q2.x-116-x-17-57) and its rooted, working fine.
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails.
I'm not totally sure if the rom i'm on now is the same one that the phone came with. The rom that's on it now was obtained from this page:
http://sbf.droid-developers.org/phone.php?device=0
(Android 4.2.2 Blur_Version.139.12.57.ghost_row.Retail.en.US) for t-mobile US
Please help me be able to update to 4.4 and ideally keep root.
Click to expand...
Click to collapse
You need to be stock, unrooted, with stock recovery to take the OTA. Use the sbf you have to flash back your stock system and recovery and you should be good to go to accept the update.
Jay10826 said:
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails..
Click to expand...
Click to collapse
that is your problem. The OTA installs will not install via 3rd party recovery like TWRP and CWM.
fastboot flash the stock recovery back on your phone and try the OTA.
Thanks for the help guys, going back to completely stock enabled me to get to 4.4. After that luckily I found out that rooting and installing twrp was very simple, unlike all the info i was reading in the developer forum. All set now
Why didn't you flash the official firmware manually using fastboot? Once done, boot into Android and run adb reboot bootloader. Fastboot flash recovery twrp.img, select recovery, adb push su.zip /sdcard/, flash su.zip, adb reboot?
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
use fastboot to flash stock recovery on your phone, undo the tethering hack, and take the OTA.
Since you have a Dev Edition with unlocked bootloader, Root and Write Protection Disable survive. You can leave stock recovery on there, unless you really need the features of TWRP like backup, etc. Then you just have to do any NEW hacks for tethering (for 4.4.2 its different than 4.4). Or you can use wifi tether for root app instead of hacks.
There was talk about repackaging the OTA to be installed via TWRP or CWM, but I don't recall the thread containing an actual zip, and think they were mostly talking about what needs to be done. Since its easy enough with the Dev Edition to update, its likely not worth the work repacking it, since it wont work for those with LOCKED bootloaders.
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
I pretty much did what was described below and maintained TWRP and root. Note: you must enter TWRP and exit after the update to reinstall SU.
http://forum.xda-developers.com/showpost.php?p=50639372&postcount=25
except I chose not to flash the following...
fastboot flash logo logo.bin
fastboot erase customize
fastboot erase clogo
Whether it makes sense or not my goal is to not "upgrade" my bootloader or GPT until absolutely necessary as they can't be downgraded. The risks associated with doing this are hotly debated so understand what you are getting into if you choose to do this to your phone.
Reverted thether hack.
Recovery tool worked for me on moto x dev. flashed stock recovery. Took ota 442. Flashed twrp. kept root and stuff. no need for a computer.
http://forum.xda-developers.com/showthread.php?t=2334554
I just bought a DE Moto X that's on 4.4.2. The bootloader is unlocked, phone is rooted with TWRP installed. My first question is what do i need to do to update to 4.4.4. If I'm understanding everything correctly I need to flash the stock recovery image..where do I get that??
Once I do that I will need to then reflash TWRP and root again, correct??
mpetruzz said:
I just bought a DE Moto X that's on 4.4.2. The bootloader is unlocked, phone is rooted with TWRP installed. My first question is what do i need to do to update to 4.4.4. If I'm understanding everything correctly I need to flash the stock recovery image..where do I get that??
Once I do that I will need to then reflash TWRP and root again, correct??
Click to expand...
Click to collapse
Yes. Here is the 442 recovery. Extract the img & Flash it with the play app: recovery tools/ Rashr-flash tool.
Once on 444 you do not want to go back.
https://mega.co.nz/#!FQI0zKxR!lS5oSAZiu0Z3dm1OCgkqKE5LqGv9rIT0zAku8juIxPk
---------- Post added at 08:16 PM ---------- Previous post was at 08:07 PM ----------
Good to hide root too with super SU.
mpetruzz said:
I just bought a DE Moto X that's on 4.4.2. The bootloader is unlocked, phone is rooted with TWRP installed. My first question is what do i need to do to update to 4.4.4. If I'm understanding everything correctly I need to flash the stock recovery image..where do I get that??
Once I do that I will need to then reflash TWRP and root again, correct??
Click to expand...
Click to collapse
First, which DEV Edition X do you have? GSM Or VZW? I'm going to Guess VZW, since you say you are on 4.4.2, and the latest for the GSM is 4.4.3.
If GSM, 4.4.4 OTA isn't out yet. So even if you flash back to stock, right now you wont get an update to 4.4.4, but you should get 4.4.3 which will be needed to take 4.4.4.
If Verizon, 4.4.4 OTA and FXZ is out, so you can go either way.
To take any OTA, you need to be aware of several things...
First, the most important, you can't flash an OTA from custom recovery like TWRP. You need STOCK recovery or you will bootloop. (so yes, you can fasboot flash stock recovery on your phone, immediately reboot to booloader and enter recovery to make sure its there). If you are already rooted you can use Rashr (and there is another tool that I can't remember the name of) to put stock recovery back on there.
Next, there is a pre-flash verification check the OTA performs. It makes sure you are on the correct ROM before it installs. It checks files and parts of your phone. It looks to make sure stuff is there, and matches the expected checksum or hash. If you haven't made any mods, and you have stock recovery back on there, you should be OK to take the OTA.. BUT if you've deleted, renamed, modified files or parts and they no longer match close enough to "stock" the OTA will fail to install.
XPosed gets in the way. It must be disabled (there is a zip for that), or uninstalled.
If you manually undo any modifications and take the OTA, you shouldn't have to re-root, and flashing TWRP back on is optional.
You could use mfastboot to re-flash System.img and Recovery.img from 4.4.2 onto your phone, that will usually be enough to allow you to pass the verification checks and take the OTA. But if you do this, you will have to flash TWRP and re-root after you get 4.4.4 on there.
Because many modifications could have been made, and the fact the 4.4.4 FXZ is out for Verizon, if you have a VZW Dev Edition, you can just use RSDLite (or mfasboot) to flash the Verizon 4.4.4 FXZ. Just make sure you remove the ERASE USERDATA line before flashing. This will get you directly to 4.4.4 without you having to manually, one by one, undo any mods you might have made that get in the way of the OTA Verification checks. If you do it this way, you WILL have to flash TWRP and re-root.
Thanks so much for the help!! I flashed the stock recovery image via flashify, accepted the ota and was all set. Then I flased twrp via flashify again and was back and all good!!
So glad I got the DE, this should hold me off til the x+1 drops.
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Anything else I might have missed that is important either from mistakes or just general knowledge I missed would be appreciated. Thanks and Good Night everybody!
Icon000 said:
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
Click to expand...
Click to collapse
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
Click to expand...
Click to collapse
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Click to expand...
Click to collapse
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Great explanation! :good:
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Why do you recommend flashing 4.4.4 over accepting the OTA? I still want to be able to use the additions originally provided by Motorola. I didn't seen a rom built on Moto Stock. Did I miss it?
Flash the stock 4.4.4 ROM that is for your device.
What's better...4.4.2 with patches to make it 4.4.4 (via an OTA) or just the full 4.4.4 (via the full 4.4.4 install) without the need for patching to make it 4.4.4?
Oh well...it looks like there isn't a FULL 4.4.4 for AT&T Moto X released yet....just 4.4.2. Flash the full 4.4.2 then take the OTA update to 4.4.4 and then flash TWRP to get root.
AT&T 4.4.2
http://sbf.droid-developers.org/download.php?device=0&file=849
You can just flash the system.img from the download with mfastboot to revert any changes you did (root, etc..) so that the OTA can be installed successfully. You'll just want to get fully updated before flashing an alternative recovery like TWRP.
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
PedroAlba said:
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
Click to expand...
Click to collapse
This is asked every time an new OTA comes out, and we get many threads started covering it.
To date...
For the Motorola X 2013, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
None of the OTA's will install if you have TWRP recovery on your phone. Instead you get stuck in a bootloop. (mfastboot erase cache will get you out of the bootloop). You need to have stock recovery on your phone. NOTE: I don't recall what happens when using Philz or CWM as recovery.
Each OTA so far has included a "Pre-Install Verification Check", a manifest of files and their checksum/hashes which the update compares against your phone. If expected files are missing, or the wrong hash, the OTA will fail to install. - So any removed or modified "bloat", system files, etc. need to be in place. Any apps like Xposed which change /system need to be disabled/removed. In some cases Freezing apps using Titanium Backup cause the OTA to fail, and the apps need to be unfrozen. However, some have not had to unfreeze. Using the phone's app manager to disable an app (Settings -> Apps -> open app listing -> DISABLE) does not have to be undone.
If you have version mismatch between GPT.BIN or Motoboot.img and the ROM on your phone, taking an OTA WILL brick the phone. - Grab the FULL SBF for the Stock Moto ROM which matches the bootloader version on your phone, or a newer SBF (i.e. if you have the bootloader version that corresponds to 4.4.2, grab the 4.4.2 SBF or 4.4.4 SBF), and flash it via mfastboot. You may need some extra steps to flash GPT.BIN and Motoboot.img.
If you've used hacks to root/disable write protection because you have a locked bootloader, you may lose root, and wont be able to re-root until a new exploit is found. Those hacks might also get in the way of the OTA's pre-install validation checks.
If you have unlocked your bootloader via mfastboot oem unlock UNIQUECODE or Sunshine, the bootloader will not re-lock.
There have been some posts (twitter and G+) about how Lollipop poses new security features which are a challenge to rooting, even with an unlocked bootloader. Since I don't know the technical ins and outs, all I can say is.. Even with an unlocked bootloader, I wont jump on Lollipop as soon as its available, until I know if I can still root my X.
(I have a little bit more detail posted here -> http://mark.cdmaforums.com/MotoX-OTA.html)
lowvolt1 said:
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
Click to expand...
Click to collapse
For what it's worth, you don't need to uninstall the modules. Just use the Xposed Disabler zip in your SD card, then install the framework again once you've flashed /system and taken the update.
When I did updated to 4.4.4 I disabled the modules in the Xposed UI (not sure if that was necessary or not), but did not actually uninstall any of the APKs for the modules. When I reinstalled Xposed after updating, all I just turned all my modules back on and rebooted.
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
mtpease said:
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
Click to expand...
Click to collapse
Not really a bad practice either way, if you clear stuff out now and again. If you try to take an OTA with a modified /system partition, it usually just fails during the hash checks and never installs/modifies anything.
You started your thread title with a [q].... Perhaps the Q&A section would be the section to ask your question? ?