I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?
Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.
Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
numanair said:
I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?
Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.
Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
Click to expand...
Click to collapse
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
coles427 said:
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
Click to expand...
Click to collapse
I am almost certain that I flashed it after taking the update. The update won't flash with anything other than the stock recovery. It was probably user error of some sort when flashing.
Related
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
gustavorod said:
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
Click to expand...
Click to collapse
i guess you cant flash official OTA through custom recovery..u need stock recovery to do this
gustavorod said:
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
Click to expand...
Click to collapse
Actually, you won't be able to do an OTA update when you've a custom recovery (you shouldn't even get it in the first place, sometimes it comes through), if you try to apply the OTA, you'll boot back to the TWRP recovery.
So, you should either go full stock (recovery & ROM), then do an OTA. Or flash some 4.4 Custom ROM.
By itself the phone alerted me that the OTA download is available and wants to download and flash itself as it did when it upgraded from 4.2.2 to 4.3 so I am not planning to flash through TWRP...
gustavorod said:
By itself the phone alerted me that the OTA download is available and wants to download and flash itself as it did when it upgraded from 4.2.2 to 4.3 so I am not planning to flash through TWRP...
Click to expand...
Click to collapse
it will download OK, but when it reboots to start installing, you'll just see the TWRP screen and nothing is gonna happen; because the OTA expects stock recovery.
Thanks!!!!
I guess I better flash another 4.3 or 4.4 by myself, I just thought the OTA would be better first to upgrade to the latest firmware...
gustavorod said:
I guess I better flash another 4.3 or 4.4 by myself, I just thought the OTA would be better first to upgrade to the latest firmware...
Click to expand...
Click to collapse
you can do two things:
1- get s-off and flash any firmware you want
2- "download & install later" the OTA, once downloaded pull it to your PC, the OTA file will contain a "firmware.zip" which is signed and can be flashed in fastboot ruu mode (you have to issue the flash command twice!!!), which would upgrade your firmware (including hboot, kernal and recovery), but will leave your rom intact
----- because it flashes recovery, you need to reflash custom recovery
----- and, kernel (boot.img) you'll need to reflash the custom one (or dirty install the ROM), otherwise the ROM won't boot up
nkk71 said:
you can do two things:
1- get s-off and flash any firmware you want
2- "download & install later" the OTA, once downloaded pull it to your PC, the OTA file will contain a "firmware.zip" which is signed and can be flashed in fastboot ruu mode (you have to issue the flash command twice!!!), which would upgrade your firmware (including hboot, kernal and recovery), but will leave your rom intact
----- because it flashes recovery, you need to reflash custom recovery
----- and, kernel (boot.img) you'll need to reflash the custom one (or dirty install the ROM), otherwise the ROM won't boot up
Click to expand...
Click to collapse
I've looked around for a CWM compatible version of the Dev Edition + Root, but I'm not finding one. Is anyone aware of a CWM-packaged version that I can flash using CWM on a rooted device? Reverting to stock to pick up the OTA seems like a long way to go
Hi guys.. I have recently flashed several Custom Roms in my X.. But i wanted to go back to stock.. I have a backup made when i was on 4.4.3 and now in the custom rom i have 4.4.4..my question is can i return to stock with my backup without having problems? Thanks in advance
Musa95 said:
Hi guys.. I have recently flashed several Custom Roms in my X.. But i wanted to go back to stock.. I have a backup made when i was on 4.4.3 and now in the custom rom i have 4.4.4..my question is can i return to stock with my backup without having problems? Thanks in advance
Click to expand...
Click to collapse
It depends entirely on how you flashed your custom ROMs. If you flashed them from TWRP or other custom recovery, you should be safe because your bootloader and partition table (these are what cannot be downgraded without bricking) are still on 4.4.3. TWRP only restores/flashes /system, /boot, and (sometimes) /data.
If you ever flashed a 4.4.4 ROM from fastboot (and flashed motoboot.img and gpt.bin) then you could potentially be in big trouble if you go back to 4.4.3. (even if it is successful, you might brick during the future OTA to 4.4.4).
Anyways, as long as you are absolutely sure you never flashed the 4.4.4 bootloader or partition table, you should be safe.
samwathegreat said:
It depends entirely on how you flashed your custom ROMs. If you flashed them from TWRP or other custom recovery, you should be safe because your bootloader and partition table (these are what cannot be downgraded without bricking) are still on 4.4.3. TWRP only restores/flashes /system, /boot, and (sometimes) /data.
If you ever flashed a 4.4.4 ROM from fastboot (and flashed motoboot.img and gpt.bin) then you could potentially be in big trouble if you go back to 4.4.3. (even if it is successful, you might brick during the future OTA to 4.4.4).
Anyways, as long as you are absolutely sure you never flashed the 4.4.4 bootloader or partition table, you should be safe.
Click to expand...
Click to collapse
Perfect.. I flashed trough twrp from 4.4.3 so i dont think i will have trouble.. Thanks for your response
Hi, I have a Moto X 2013 Developer Edition with bootlocker unlocked and stock rom with Android 4.4.4. It's root, has TWRP and SuperSU.
Since last week my phone is shutting down almost always after power on (only a few times it keeps power on for a few hours), and restarting in TWRP recovery mode.
Do you know what could be the cause of this boot loop?
I suspect it has something to do with the Lollipop Update to 5.1, cause I start getting this boot loop after the update option was shown in my phone (I didn't accept the update at first).
I tried installing again SuperSu (thinking that maybe root was disabled), but without luck. The phone continue with this boot loop.
I also tried installing now the Lollipop Update to see if that resolve the issue, unfortunately after the update is downloaded and I accept the install, the phone shutdown and it boots in TWRP again (so the updated doesn't install).
Hope my problem was explained well and anybody can help cause my phone is really unusable like this.
Thanks in advance!
You're only suppose to install stock ota's using stock recovery not custom recovery. It's best (if you can) flash back to stock if you know how.
Sent from my XT1055 using Tapatalk
can you please tell me how to flash stock recovery
Thanks for your response. Do you mean to flash stock recovery? or full stock rom?
Just in case, I don't need/want to install lollipop, only want to avoid this kind of boot loop and stay at 4.4.4. I'll only install 5.1 it if that fix the issue /but as I say I can't do it because after download and try to install, it power down the phone and goes to twrp recovery).
Thanks for your help!
ninguno2 said:
Thanks for your response. Do you mean to flash stock recovery? or full stock rom?
Just in case, I don't need/want to install lollipop, only want to avoid this kind of boot loop and stay at 4.4.4. I'll only install 5.1 it if that fix the issue /but as I say I can't do it because after download and try to install, it power down the phone and goes to twrp recovery).
Thanks for your help!
Click to expand...
Click to collapse
It's best that you flash back to fully stock rom. If you can flash back to 4.4.4
Sent from my XT1055 using Tapatalk
What if they disabled the update app, wouldn't that stop the update from trying to install and cause it to reboot into twrp
Sent from my XT1060 using Tapatalk 2
TRY THIS POST
http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
I USED OPTION 1 i.e USED THE TOOL KIT ...
Hi cdiamon, sorry asking again, but there is something I don't understand.
I have original stock rom 4.4.4. I only unlock bootloader (I have the developer edition), put twrp and root the phone. Why the suggestion is to flash back to 4.4.4 to resolve the issue? Didn't I'm already at stock rom?
By the way do you think the problem is because twrp and/or root by supersu? If yes, can't i simply uninstall supersu or remove twrp in some way?
B.E.McAllister and praty, thanks both for your answers, I'll look at them too.
Thanks in advance!
ninguno2 said:
Hi, I have a Moto X 2013 Developer Edition with bootlocker unlocked and stock rom with Android 4.4.4. It's root, has TWRP and SuperSU.
Since last week my phone is shutting down almost always after power on (only a few times it keeps power on for a few hours), and restarting in TWRP recovery mode.
Do you know what could be the cause of this boot loop?
I suspect it has something to do with the Lollipop Update to 5.1, cause I start getting this boot loop after the update option was shown in my phone (I didn't accept the update at first).
I tried installing again SuperSu (thinking that maybe root was disabled), but without luck. The phone continue with this boot loop.
I also tried installing now the Lollipop Update to see if that resolve the issue, unfortunately after the update is downloaded and I accept the install, the phone shutdown and it boots in TWRP again (so the updated doesn't install).
Hope my problem was explained well and anybody can help cause my phone is really unusable like this.
Thanks in advance!
Click to expand...
Click to collapse
The problem is you have twrp on your phone when the phone is trying to update. You need to flash stock recovery then take update. Or keep twrp and disable update app.
monkeytools said:
The problem is you have twrp on your phone when the phone is trying to update. You need to flash stock recovery then take update. Or keep twrp and disable update app.
Click to expand...
Click to collapse
Hi monkeytools. thanks for the explanation. I think I'll disable update app then.
Just to know, is there any way to uninstall TRWP without flashing stock recovery and loosing all of my configuration?
Thanks in advance!
ninguno2 said:
Hi monkeytools. thanks for the explanation. I think I'll disable update app then.
Just to know, is there any way to uninstall TRWP without flashing stock recovery and loosing all of my configuration?
Thanks in advance!
Click to expand...
Click to collapse
You don't loose anything by flashing recovery. That is if you just flash recovery or fastboot recovery.
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Groid said:
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Click to expand...
Click to collapse
OTA checks system and kernel and if anything is changed, OTA will fail. That includes root.
Fastboot flashing a system.img, boot.img and recovery.img would be enough to unroot and get back to stock however, you would only want to OTA if the rom you wanted didn't have a factory image.
Decryption is possible on all ROMs. It's just a custom kernel (boot.img) that doesn't force encryption on boot, then format userdata to get rid of existing encryption. Of course you're modified now so no OTA.
People care so pointlessly about OTA. Advice: forget about it and fastboot flash to update, or easier yet, wait for someone to package it up into a recovery flashable zip
Hi all,
I just received my new ZenWatch 3 today. I turned it on, set it up, and unlocked the bootloader.
From there, I flashed the MWG68 stock images so I could update to the latest AW 1.5 version (I had no intention of upgrading to AW 2.0). I also flashed TWRP so I could later edit the build.prop and disable OTA updates.
However, the watch no longer boots. Instead, it boots directly to recovery. I have tried wiping, flashing the stock images, flashing the 2.0 OTA, flashing the custom ROM, but nothing seems to work. I have full TWRP and fastboot access, but I can't get the watch to boot. Should I also attempt to flash the second half of the MWF76 stock images?
I'm at a loss here. Any help is appreciated.
Thanks.
re: flashing issues
SS111 said:
Hi all,
I just received my new ZenWatch 3 today. I turned it on, set it up, and unlocked the bootloader.
From there, I flashed the MWG68 stock images so I could update to the latest AW 1.5 version (I had no intention of upgrading to AW 2.0). I also flashed TWRP so I could later edit the build.prop and disable OTA updates.Thanks.
However, the watch no longer boots. Instead, it boots directly to recovery. I have tried wiping, flashing the stock images, flashing the 2.0 OTA, flashing the custom ROM, but nothing seems to work. I have full TWRP and fastboot access, but I can't get the watch to boot. Should I also attempt to flash the second half of the MWF76 stock images? - I'm at a loss here. Any help is appreciated.
Click to expand...
Click to collapse
1: Whenever you unlock the bootloader you have to re-lock
it before flashing any roms.
2: You MUST do a full wipe and factory reset in TWRP before
flashing any roms. (especially for watches)
I flashed the same rom and twrp as you have 3 days ago
and I had no issues with flashing it It's an excellent rom.
Also you do not need to edit the build-prop file to disable
OTA updates and notifications.
Since the rom is pre-rooted it will not allow OTA updates
and will not notify you about any. (just like cell phones)
Good luck,
Have a great day!
Misterjunky said:
1: Whenever you unlock the bootloader you have to re-lock
it before flashing any roms.
2: You MUST do a full wipe and factory reset in TWRP before
flashing any roms. (especially for watches)
I flashed the same rom and twrp as you have 3 days ago
and I had no issues with flashing it It's an excellent rom.
Also you do not need to edit the build-prop file to disable
OTA updates and notifications.
Since the rom is pre-rooted it will not allow OTA updates
and will not notify you about any. (just like cell phones)
Good luck,
Have a great day!
Click to expand...
Click to collapse
Hi, thanks for the reply. Unfortunately, even after locking the bootloader, doing a full wipe, and then flashing the ROM it still boots straight into TWRP after reboot. Should I try flashing the stock images with the stock recovery?
Ah, good news! I got it to boot. Apparently the stock recovery is needed as well. Only flashing the system.img and boot.img without the stock recovery.img causes it to bootloop. Thanks again for taking the time to respond to me.