I am aware that I can't get the ota with a custom recovery. when lollipop gets released, how to I update my phone? I want to use stock so that I have active notifications and voice control.
You need to reflash the stock firmware.
Flash the entire stock rom? Or just recovery?
Recovery, revert any framework mods, reinstall any uninstalled system apps, and unfreeze any system apps.
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
Now, i have a Noob Question, but I always had Samsung devices, they have no bootloader like the moto or htc.
I unlocked the bootloader, is it safe to update via OTA ?
thx
TLH11 said:
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
Now, i have a Noob Question, but I always had Samsung devices, they have no bootloader like the moto or htc.
I unlocked the bootloader, is it safe to update via OTA ?
thx
Click to expand...
Click to collapse
Pretty sure all android devices have some sort of bootloader.
Anyway, since your bootloader is unlocked, you shouldn't have a problem rooting.
JJHunterx said:
Pretty sure all android devices have some sort of bootloader.
Anyway, since your bootloader is unlocked, you shouldn't have a problem rooting.
Click to expand...
Click to collapse
What about the OTA for future lollipop?
TLH11 said:
What about the OTA for future lollipop?
Click to expand...
Click to collapse
If you have a custom recovery you wont be able to OTA. That simple.
...or just wait for someone to cook up a custom Lolipop or stock rooted ROM flashable via custom recovery.
JJHunterx said:
If you have a custom recovery you wont be able to OTA. That simple.
Click to expand...
Click to collapse
It will certainly flash via custom recovery. You just can't do an automatic update with custom recovery, where the system reboots itself and tries to update. If you manually download an OTA zip and flash it manually in recovery, it will work as long as all the file checks pass as I've done this several times on different devices.
Sent from my Moto X
TLH11 said:
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
Now, i have a Noob Question, but I always had Samsung devices, they have no bootloader like the moto or htc.
I unlocked the bootloader, is it safe to update via OTA ?
thx
Click to expand...
Click to collapse
For #2 you do not need to UNROOT in most cases. Using the older methods for locked bootloaders like SlapMyMoto/RockMyMoto and the like it was suggested to flash back to stock because of potential changes those processes make that could cause the OTA update's pre-flash validation checks fail.
For #6 it depends on how they are "Frozen." Apps "frozen" or disabled the same way that going Settings -> Apps -> {select the app} -> tap DISABLE button (or uninstall updates, then disable) will be fine and will not impact the OTA.
In the past freezing apps via Titanium Backup did cause problems, so it was suggested to unfreeze. However, more recent updates (like 4.4.2 to 4.4.4) did not encounter that problems, and those who froze apps with Titanium Backup didn't need to unfreeze.
If you have an 3rd party recovery on the device, when it goes to reboot and install the update, it will fail, and get the phone stuck in a boot loop.
When I've tried manually installing an OTA.ZIP in TWRP, it has errored. The only way for me to install was via stock recovery. That being said, I didn't try CWM or Philz.
As for Lollipop, you will be able to install and then flash custom recovery. As for rooting, there are changes in Lollipop, and it wont be confirmed until Lollipop hits a 2013 X, but in theory, due to the latest updates from Chainfire to SuperSU, we may be able to just flash TWRP, and install SuperSU like we did with KitKat.
Related
Is there a guide anywhere on how to install 4.4.2 on the Dev Ed phones?
Assume I can just use TWRP for root after updating?
Thanks!
Mercutio5 said:
Is there a guide anywhere on how to install 4.4.2 on the Dev Ed phones?
Assume I can just use TWRP for root after updating?
Thanks!
Click to expand...
Click to collapse
Are you rooted now? If you are rooted, as long as you haven't changed any of the system files you can install the .zip through the stock recovery and you're good to go (you don't lose root).
If you aren't rooted, just install the .zip through the stock recovery and then flash TWRP recovery and root.
Assuming you have an unlocked bootloader, flashed TWRP and rooted (but no other changes, no VZWentitlement hacks, delete/removing/renaming any apps from /system/app or /system/priv-app, no Xposed Installer and modules installed, etc...).
Download the 4.4.2 update .zip to your phone.
Flash the stock recovery back to your phone.
Boot to recovery and install the .zip you downloaded.
Done.
You'll need to find the .zip and download it.
You'll need to know how to flash the stock recovery back and have it downloaded so you can flash it
You'll need to know how to use the stock recovery (button combos to boot to recovery and enter recovery)
tcrews said:
Are you rooted now? If you are rooted, as long as you haven't changed any of the system files you can install the .zip through the stock recovery and you're good to go (you don't lose root).
If you aren't rooted, just install the .zip through the stock recovery and then flash TWRP recovery and root.
Assuming you have an unlocked bootloader, flashed TWRP and rooted (but no other changes, no VZWentitlement hacks, delete/removing/renaming any apps from /system/app or /system/priv-app, no Xposed Installer and modules installed, etc...).
Download the 4.4.2 update .zip to your phone.
Flash the stock recovery back to your phone.
Boot to recovery and install the .zip you downloaded.
Done.
You'll need to find the .zip and download it.
You'll need to know how to flash the stock recovery back and have it downloaded so you can flash it
You'll need to know how to use the stock recovery (button combos to boot to recovery and enter recovery)
Click to expand...
Click to collapse
Thank you!
Ah, I had forgotten about having to use the stock recovery to flash. When I last updated, I dirty flashed a TWRP-able image. Might wait for someone to make one for maximum laziness
Edit the updater-script and remove the device check for ghost in the OTA zip that's posted. Then you can flash it in CWM or TWRP as long as /system is stock.
Sent from my Moto X
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.
That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?
OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks
@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
Hi guys!
I've finally received 4.4.4 notification to update my German Moto x!!
I'd like to know one thing before I proceed.. If I update, will I have to root again the phone?
My phone has unlocked bootloader so there is no problem, but right now I'm on holiday and I don't have a pc to root it again..
Thanks a lot!
I have not upgrade to 4.4.4 yet.
I don't think you need to root again
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
daede86 said:
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
Click to expand...
Click to collapse
Hi, i was wondering the same thing. Is there a method for someone to create an update for rooted phones?
Also can you link me to the threads for flashing back to stock and what this fwz is?
thank you
Here you can find some info about FXZ (sorry for my typo)
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In the same thread you can find the stock recovery, a user posted it. Just search stock recovery in the thread and you'll find it!
I'm not the right person to help you in detail.
I'm not an expert user
In the meantime I froze motorola OTA app to hide the update notification..
Guys, before anyone gets in trouble....there is no FXZ for the german (or any asia/european) Moto X's yet.
The only one released is the Verizon one....so DON'T flash the verizon FXZ.
You need to flash stock recovery back, and if the phone STILL won't take the OTA, also use "mfastboot" to flash system.img from the 4.4.2 FXZ (which IS released for the european/asia models). Afterwards, the OTA should install without fail.
You WILL need to re-flash TWRP no matter which method you use. You will also need to re-root IF you flash the system.img from the 4.4.2 SBF in order to be able to accept the OTA (you only flash system.img from 4.4.2 if the OTA fails after you have flashed stock recovery - it normally means you have modified /system in some way, and restoring the full system.img fixes this issue).
Good Luck - Remember: Don't flash the Verizon 4.4.4 FXZ to your non-Verizon phone. Not a good idea...
If your phone doesn't vary from Stock but rooted, you can get away with flashing stock recovery back on there and taking the OTA. (OTA wont install via custom recovery like TWRP, CWM, etc). And if that is the case, you will retain root. You can optionally flash TWRP back on there.
If you have Xposed installed, it will need to be disabled or removed for the OTA install to work.
It is when you mess with stock files in /System or other folders on the phone.. i.e. remove, rename, etc. files from them, that you may also need to flash system.img and possibly other parts. This is due to verification checks in the OTA zip itself. If you have to flash those parts, you will have to re-root. Not an issue if you have an unlocked bootloader.
Thanks a lot for your help and clarification!!
I knew I wasn't the right person
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
daede86 said:
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
Click to expand...
Click to collapse
IF you do not vary too much from Stock (i.e. didn't remove, rename or replace any "stock" files on your phone), then yes.
Oh, for Xposed, there is a disabler ZIP you can flash from custom recovery located in /storage/emulated/0/Android/data/de.robv.android.xposed.installer (or /SdCard/Android/data/de.robv.android.xposed.installer ) instead of removing it, as sometimes removing it doesn't undo all the changes.
My N6 is rooted, SuperSU and TWRP. On build LYZ28J and want to update to LYZ28K.
It seems I have 3 ways to do this:
1. Use settings in SuperSU to fully unroot, AND flash the LYZ28J recovery.img to replace TWRP. Then I can take the OTA. After that I can rerun the Chainfire Autoroot script and flash TWRP. So i'm updated with no data loss.
2. Flash the factory image. No need to unroot or remove TWRP, but all data is lost. And I still need to reroot and reflash TWRP. Correct ?
3. sideload the ota zip. Just run adb sideload <ota.zip> . No need to unroot . My problem here is that the only place I found with the ota zip is on Droid Life, not a google url. I like Droid Life, read it all the time, but still... Does anyone have a google url link to the OTA ?
Is there another method?
How are others upgrading? Is #3 as easy as I described ?
sean
1. no. to fully unroot, you need to flash a factory image. if you just remove root, itll still think tour rooted because system files have changed. so, wont work.
2. you can, but why? you gave extra time that you want to burn?
3. nope, cant flash an ots while rooted ir havd chsnged system files.
4. just flash the system.img of a factory image ehen it vomes out, and you will not lose data, but will upgrade.
I've used this thread (http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158) to update within Lollipop through several versions. It is always best to wipe data when going from one version to the next (Lollipop to Marshmallow) but as long as you are staying within Lollipop this should work fine.
Check this out, http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
IMO, easiest way. DL zips to internal storage, wipe, and flash. READ the "Read Me" in the first post. When you update it will get rid of SU. Once you boot with update the first time, you can go back and root with TWRP.
Chose to use this. Did not flash the new recovery image. Updated fine, BUT locked and no root, no TWRP. I'll need to run oem unlock again, wiping all the data.
Sigh.
Wrote too soon. SuperSU and TWRP were gone (even though I did not flash recovery.img). Developer Options was gone. So I needed run CF-Autoroot and still need to flash TWRP. But all apps and data remained.
This is great news, especially if we're going to get monthly updates.
I just unlocked my bootloader using Sunshine and then I flashed twrp and when I went to reboot my phone twrp asked if I want to install SU so i hit yes and it went through its process and now my phone will not boot. Is there anything I can do?
Edit: Thanks for the responses TheSt33v fixed my problem.
Hopefully you unlocked the bootloader before taking the latest OTA to marshmallow?
He couldn't have used Sunshine on Marshmallow. He had to be on Lollipop.
ylevanSnavely said:
I just unlocked my bootloader using Sunshine and then I flashed twrp and when I went to reboot my phone twrp asked if I want to install SU so i hit yes and it went through its process and now my phone will not boot. Is there anything I can do?
Click to expand...
Click to collapse
Go to the development section of the Droid Turbo forum and pick out the rom you want. If you downloaded a stock lollipop rom, download SuperSU from here: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip. If you downloaded the stock marshmallow rom, download this version of supersu in addition to the one above: https://download.chainfire.eu/751/SuperSU/. If you downloaded a CM-based rom, you don't need supersu. Boot into TWRP. Use TWRP to wipe system, cache and dalvik cache (this will not wipe any of your apps, pictures, or other user data). Plug your phone into your computer and transfer both the rom and supersu(s) that you downloaded to the phone. If you are installing a stock lollipop rom, flash the rom followed by the supersu package. If you are installing the marshmallow stock rom, flash in the order of rom, older version of supsersu, newer version of supersu. If you are installing a CM-based rom, just flash that.
The first boot can take a very long time. Be patient. Wait at least 10 minutes before you give up. Also, if you're installing a different version of android than the version that is currently on there, you'll need to wipe your data with a factory reset first. So if you need to back things up, I would recommend putting the stock lollipop on there first, backing everything up, and then installing whatever you want afterwards.