When I try to OTA update to 5.1 my phone reboots and ends up in TWRP. I've restored back to my oldest backup so my phone is stock 4.4.4 but unlocked with TWRP installed. Do I have to do more to restore full stock before OTA to 5.1 will work? Is there a way to manually install 5.1 with TWRP that might be easier?
Thanks
PS I had installed zwliew Kernel but I assume that when I went back to my oldest backup with TWRP that it went back to stock kernel
Your device has to be fully stock to take the OTA including your recovery. Also 5.1 has not been pushed to Verizon yet, so no OTA to update to.
You have to have stock recovery. There are lots of threads that tell how to mfastboot flash the stock recovery back onto your phone. You will not lose root doing this.
drdeathly said:
When I try to OTA update to 5.1 my phone reboots and ends up in TWRP. I've restored back to my oldest backup so my phone is stock 4.4.4 but unlocked with TWRP installed. Do I have to do more to restore full stock before OTA to 5.1 will work? Is there a way to manually install 5.1 with TWRP that might be easier?
Thanks
PS I had installed zwliew Kernel but I assume that when I went back to my oldest backup with TWRP that it went back to stock kernel
Click to expand...
Click to collapse
First, are you sure its a 5.1 OTA?? I wasn't aware that was being pushed. There is a maintenance release to 4.4.4 that VZW has been pushing this week.
Next... TWRP is big reason. If you still had ZWLIEW Kernel on there, that would have been something else to correct.
Please take a few moments and read -> [FAQ] How to prepare for and take an OTA update (All Carriers)
I believe that kernel also modifies the system.img, in that case it would be wise to mfastboot the system.img as well as the stock recovery.
---------- Post added at 09:15 PM ---------- Previous post was at 08:20 PM ----------
Also when I used the app to revert back to my stock kernel it broke my wifi. So you are better off just mfastboot the stock images.
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
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.
Want either to cancel forced AT&T update or flash the 5.1 OTA zip without formating
Hello, recently, my step-father got a dip with's LG G2 and decide to buy a Moto X from Ebay and it came bootloader unlocked with AT&T Kitkat 4.4.4. Today, we opened it and it asked to do the update at which i heard there was some issue with the update and they pulled it off. He's an user who only want stability, so that why when he got it and i saw it was bootloader unlocked i install TWRP and roooted it.
So i have 2 choose, try to cancel the force update because he reboot to recovery for trying to install it and it's not flashing at all or simply try to update without losing the data. If i need to, i would like to flash the stock recovery of AT&T. It's not a contract phone, i buyed it on ebay and i am using it with Roger in Canada, so i don't want to get it brick. Thank you.
If you update it, you will never be able to unlock the bootloader on the AT&T phone again. It is unlockable after update. If you want to flash kit kat 4.4.4, why don't you just flash a Rogers 4.4.4 rom from xda on it? Why even take an ota to lollipop when you don't want to because of issues? You won't be able to go back. I would just flash Rogers stock modded with twrp, or in my opinion, flash eclipse 4.4.4, it has all moto stock options and is faster and better battery life. But if you want to flash lollipop ota, you have to flash back original at&T recovery.
---------- Post added at 10:39 AM ---------- Previous post was at 09:59 AM ----------
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
That's the stock [email protected] rom lollipop rom. You can flash that and it will lock your bootloader, put stock recovery and unroot but you can't unlock the bootloader again and can't go back. If you want the stock lollipop KitKat rom, I can get that
Well, finally, i freezed the update module with titaniumbackup on the stock 4.4.4 kitkat from AT&T on the moto x, i will wait for a modded zip file debloated to flash later.
I am using a rooted moto g 2014. I have an ota update notification. how to install the the ota update? I'm using twrp 2.8.6.0 custom recovery.
You need to go back to stock recovery to install the updates. However the update might fail on a rooted phone and you might need to unroot it. Also you need to remove rooted apps like xposed to have a successful OTA. For a smooth OTA, I would suggest you move back to stock ROM and recovery and then OTA update.
pank.dhnd said:
You need to go back to stock recovery to install the updates. However the update might fail on a rooted phone and you might need to unroot it. Also you need to remove rooted apps like xposed to have a successful OTA. For a smooth OTA, I would suggest you move back to stock ROM and recovery and then OTA update.
Click to expand...
Click to collapse
Share the process plz... (in details)
Here is the post to flash the stock recovery and firmware
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
Make sure you back up your data before you perform the procedure. Also for being safe side, back up all the contents of your internal memory.
Good luck
I keep seeing a link to sbf.droid-developers.rog for stock Moto X firmware files. It appears that site is no longer maintained. Is there any other resource for stock firmwares out there?
I'm currently on rooted 4.4.2 (Moto X 2013) and was hoping to use Sunshine to unlock my bootloader, return to stock, take the new Republic 5.1 OTA that's due out soon, and root from there with an unlocked bootloader.
I believe if you upgrade any further then you currently are (EG: Android 4.4.4 or higher), you will not be able to root and unlock your Republic Wireless phone...
Hey
Apparently am not able to send outside links so look for the stock firmware in yandex. Hope you understand
BSnapp said:
I believe if you upgrade any further then you currently are (EG: Android 4.4.4 or higher), you will not be able to root and unlock your Republic Wireless phone...
Click to expand...
Click to collapse
I was able to use Sunshine to unlock my bootloader at 4.4.2. Then I was able to upgrade to 4.4.4 and ultimately to 5.1 and get root due to the unlocked bootloader.
Kingathia said:
Apparently am not able to send outside links so look for the stock firmware in yandex. Hope you understand
Click to expand...
Click to collapse
I managed to find 4.4.2 here: filefactory.com/file/6rarzwf3okj3/ghost_repw-user-4.4.2-KXA20.16-1.24-1.12-12-release-keys-cid6.xml.zip
News: the Republic Wireless 5.1 SBF is out on File Factory. Here's the link: http://www.filefactory.com/file/27kl2ef9ngk7/XT1049_GHOST_REPW_5.1_LPA23.12-39-R-15_cid6_CFC.xml.zip
Nicene Nerd said:
News: the Republic Wireless 5.1 SBF is out on File Factory.
Click to expand...
Click to collapse
Fantastic! Thanks for the link. I ran a bit of a risk rooting on 5.1 without a backup stock rom. Glad to know I don't have to worry about it now.
parody24 said:
Fantastic! Thanks for the link. I ran a bit of a risk rooting on 5.1 without a backup stock rom. Glad to know I don't have to worry about it now.
Click to expand...
Click to collapse
if it makes you feel better, I have an unlocked bootloader and I used the file above yesterday (using the instructions on here to restore to stock, editing the xml file, etc). worked fine! I was nervous too, after taking the 5.1 RW update, rooting, and messing something up myself with an older xposed version (I was NOT paying attention. LOL). All better! Nice to have that file handy now!
I was just able to take the EMR update first through system update OTA. Now it won't give me the 5.1 OTA. I currently have stock recovery, no root, with no system mods. I tried manually installing the 5.1 OTA but it doesn't work. It says it was aborted because the package expected a different build fingerprint. But I'm on 212.154.2.ghost_row.RepublicWireless.en.US Any suggestions for getting the OTA to work, or do I have to get root and TWRP back and flash the 5.1 SBF? If so, is the 894.64 MB zip from file factory for sure the one I need for Republic Wireless? I just don't want to brick my phone. Thanks!
---------- Post added at 10:58 AM ---------- Previous post was at 10:29 AM ----------
I was doing some research and I think I forgot 1 step to make sure I'm 100% back to stock. I made no system mods and I did flash stock recovery, but I forgot about the boot image I was using so I wasn't seeing the bootloader unlocked message. Would that make the manual OTA fail/abort and/or also make system update not recognize 5.1 is needed? I'm guessing it does. So I'll try getting TWRP back and flashing the correct stock boot image for 4.4.4, then remove root/TWRP again and see if it will take the OTA, either from system update or manual OTA. Hopefully this works, or at least reminds others to take this step if necessary. Thanks for any feedback!
PackerDroid said:
I was just able to take the EMR update first through system update OTA. Now it won't give me the 5.1 OTA. I currently have stock recovery, no root, with no system mods. I tried manually installing the 5.1 OTA but it doesn't work. It says it was aborted because the package expected a different build fingerprint. But I'm on 212.154.2.ghost_row.RepublicWireless.en.US Any suggestions for getting the OTA to work, or do I have to get root and TWRP back and flash the 5.1 SBF? If so, is the 894.64 MB zip from file factory for sure the one I need for Republic Wireless? I just don't want to brick my phone. Thanks!
---------- Post added at 10:58 AM ---------- Previous post was at 10:29 AM ----------
I was doing some research and I think I forgot 1 step to make sure I'm 100% back to stock. I made no system mods and I did flash stock recovery, but I forgot about the boot image I was using so I wasn't seeing the bootloader unlocked message. Would that make the manual OTA fail/abort and/or also make system update not recognize 5.1 is needed? I'm guessing it does. So I'll try getting TWRP back and flashing the correct stock boot image for 4.4.4, then remove root/TWRP again and see if it will take the OTA, either from system update or manual OTA. Hopefully this works, or at least reminds others to take this step if necessary. Thanks for any feedback!
Click to expand...
Click to collapse
Are you installing the full 5.1 recovery or are you trying to flash just the OTA? The OTA file itself is just a diff not the full recovery. The file linked above should be the full system.
I'm trying to get the OTA to work first. If I can't, then I'll use the full SBF. I've already returned to stock recovery. I just wanted to check to make sure someone has used the full SBF that is posted and that there are no issues with it. Thanks!