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? ?
Related
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
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
You need stock /system partition and stock recovery. It doesn't matter whether the bootloader is locked or unlocked.
Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
To install? or to be notified and receive the update?
To receive the update you'll need to be running the "stock" Verizon firmware, rooted/unrooted and bootloader locked/unlocked doesn't matter.
For it to install successfully, to expand on what kbluhm posted...
Keep in mind that usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail. That is why "stock /system" is required.
And "stock recovery" is needed because when the phone reboots to install the update, it tries to boot to stock recovery and run the install script. The 3rd party recoveries don't seem to work, or have errors, when installing the OTA update zips.
If you've rooted with SlapMyMoto, RockMyMoto, or thel like, you may have other issues to deal with in order to take any OTA updates since those processes can touch other files/partitions on the phone which will cause problems with the OTA Updates.
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
You could grab the factory image from Motorola and flash only system and recovery using fastboot. That is my plan. You can find the zip file on Motorola's site or there is a topic here on XDA.
Sent from my XT1060 using Tapatalk
guitarbedlam said:
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Click to expand...
Click to collapse
Mike7143 said:
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
Click to expand...
Click to collapse
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
KidJoe said:
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
guitarbedlam said:
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
Click to expand...
Click to collapse
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
KidJoe said:
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
Click to expand...
Click to collapse
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
tcrews said:
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
Click to expand...
Click to collapse
Interesting. One of the issues reported with the Kit Kat update was the OTA failing due to apps frozen with Titanium Backup. I only "disable" via the stock app manager, so I haven't had a problem.
Most likely those with failures had modified/deleted/renamed something else that was causing the issues and blaming it on the frozen apps. I have updated every device I've had with frozen apps. Freezing, at least in Titanium Backup, tells the OS the app is not available. In recovery, the OS is not loaded and knows nothing about frozen apps. Titanium doesn't touch the actual files so they are still present to be patched by the OTA.
Sent from my Nexus 10
I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
JJHunterx said:
I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
Click to expand...
Click to collapse
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
asuhoops8628 said:
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
Click to expand...
Click to collapse
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
JJHunterx said:
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
Click to expand...
Click to collapse
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
KidJoe said:
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
Click to expand...
Click to collapse
For some reason, I didn't think 4.4 had a SBF...Found it. Thanks.
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
You can unlock your BL regardless of what version of android you are on. I just wanted to get back to stock so slapmymoto was no longer active (which is kinda a workaround for root imho, but it works and does its job.)
To root with an unlocked bootloader, all you have to do is download the TWRP img file and the supersu.zip file. Push the supersu.zip to your SD card. Use fastboot to flash TWRP img file. Boot into the recovery you just flashed and install the supersu.zip file. Bam you're rooted.
fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
KidJoe said:
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
Click to expand...
Click to collapse
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
fury683 said:
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
Click to expand...
Click to collapse
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. 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.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. 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.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
EvanVanVan said:
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
Click to expand...
Click to collapse
For the most part, you can use mfastboot to flash just system.img and recovery.img, this will get those two parts back to stock, which is often enough to allow you to take an OTA update, however, if you've touched any other part, your phone wont be 100% stock. And then, how long does it take for the OTA to install and reboot? Now, in fury683's case, the phone is on 4.4 and he wants to go to 4.4.2. But if the phone was on say either of the 4.2.2 versions and he wanted to go to 4.4.2, then you'd also have multiple OTA's to install.
Using the full SBF and RSDlite will flash all parts, gets you to 100% stock, and immediately on the version you want. I don't know everything that SlapMyMoto and MotoWpNoMo touch, so I can't say for sure if flashing system and recovery are enough to totally remove them, or just remove enough to allow you to take an OTA.
System.img takes the longest to flash via either mFastboot or RSDLite, the rest are really quick, so the time spent using RSDLite to flash everything isn't that much more than manually flashing just system.img and recovery.img via mfastboot.
So considering that the mfastboot oem unlock does a factory reset anyway (so data is going to be lost), and flashing with RSDlite flashes all parts as 1 batched operation (i.e. you don't have to individually execute mfastboot lines...) using RSDLite can get you to the final destination, and ensure 100% stock, more easily.
I did mine last night from 4.4. I unlocked, got a clean 4.4 , took ota, flash twrp, install su. If you do in the right order shouldn't take more than 30 mins to be up and running again. If you use Titanium backup be sure to pull your files to computer before doing the bootloader unlock.
KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. 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.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
Thanks for your help. The process was much less painful than I expected. Aside from downloading the SBF file, whole process to SBF, unlock, flash TWRP and root took about 20 minutes.
Working great now!
Thanks again
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
yankeesfan714 said:
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
Click to expand...
Click to collapse
I've had no issues updating OTA while rooted and unlocked. It only becomes an issue if you modify the system. You will also not be able to update OTA if you have a custom recovery installed. However, to play it completely safe it is always best to go back to stock if you are doing an OTA.
Installing a custom recovery and messing with system apps will cause an ota to fail. Unlocking and SU alone won't make it fail
Leave system apps alone and flash back to the stock recovery prior to accepting the ota.
yankeesfan714 said:
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
Click to expand...
Click to collapse
Since the OTA can only install via stock recovery, installing a custom recovery is technically the point at which you lose the ability to do an OTA update.
to quote SOME of what I put here -> http://mark.cdmaforums.com/MotoX-OTA.html
For the Motorola X, 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.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall.
Because of #2, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
Click to expand...
Click to collapse
So any any point you deviate from stock too much, an OTA will fail to install.
(there is more info at that link)
If all you have done is unlocked the bootloader, flashed custom recovery, and installed SuperSU to root... then installed root capable apps like Adfree, Wifi Tether for root, Greenify, or others that don't mess with system files and the like, you can just flash stock recovery back on to take an OTA.
If you unlock the bootloader, flash custom recovery, and install SuperSU to root... then alter the build.prop, remove or rename the BLOAT APK's from your phone, install Xposed, etc. You'll have some work to do getting back to "stock" to take the OTA.
KidJoe said:
Since the OTA can only install via stock recovery, installing a custom recovery is technically the point at which you lose the ability to do an OTA update.
to quote SOME of what I put here -> http://mark.cdmaforums.com/MotoX-OTA.html
So any any point you deviate from stock too much, an OTA will fail to install.
(there is more info at that link)
If all you have done is unlocked the bootloader, flashed custom recovery, and installed SuperSU to root... then installed root capable apps like Adfree, Wifi Tether for root, Greenify, or others that don't mess with system files and the like, you can just flash stock recovery back on to take an OTA.
If you unlock the bootloader, flash custom recovery, and install SuperSU to root... then alter the build.prop, remove or rename the BLOAT APK's from your phone, install Xposed, etc. You'll have some work to do getting back to "stock" to take the OTA.
Click to expand...
Click to collapse
Does this also apply to moto x non-dev devices?
dmonleo said:
Does this also apply to moto x non-dev devices?
Click to expand...
Click to collapse
Yes. Every device with an unlocked bootloader is essentially a 'non official' Dev edition (although unlike the Dev edition, your warranty is void).
We always got "swappa"!
dmonleo said:
Does this also apply to moto x non-dev devices?
Click to expand...
Click to collapse
While Not Explicitly stated on -> http://mark.cdmaforums.com/MotoX-OTA.html yes, that info about the conditions for taking an OTA applies to ALL Moto X's... Dev Edition, Non-Dev Edition, Moto Maker, Retail, etc. With locked bootloader and with Unlocked Bootloader.
What @samwathegreat replied to you is very accurate. From a functional stand point, once you unlock the bootloader on a Non-Dev Edition... your phone acts as if you have a Dev Edition.. (Except your warranty is void). And it doesn't matter if you have a Rogers Wireless, Sprint, GSM Unlocked, etc... and got your code from Moto, or you had a Verizon Non-Dev or ATT or Republic wireless and got the code from the Chinese website or middleman.
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.