Official Security Update on Rooted XT1550 - Moto G 2015 Q&A, Help & Troubleshooting

This morning, I received April Security Patch for my XT1550. I'm on rooted stock 6.0.1 with stock recovery and I have flashed sound mods like Viper4Android and Dolby Atmos, and uninstalled some system apps like Hangouts, Play Movies, etc. When I tried to install the update, I got an error. If I unroot, will I be able to install the update? Or will the system modifications I made interfere with the OTA? Is there a way to flash the update manually with TWRP if I got the zip file of the update (I got it from system/cache)? I don't want to flash stock rom and start from scratch just to install this update.

Don't do an OTA update. Install the stock rom again. And you will get nearly 3 updates including the April patch. Update them and then root it.

just try to flash stock recovery then try to install update.It works

You've got a modified system partition. You need to be full stock to be able to take an OTA. Unrooting and/or removing mods will be useless as the system will still be marked as modified by the update script (search block based OTA for more info).
Also, AFAIK TWRP doesn't support stock firmware zips so the install will likely fail too.
Your choices are -
1. Flash full stock, and then update.
2. Wait for the updated fastboot flashable​ firmware images to arrive.
Broadcasted from Zeta Reticuli

Related

OTA's failing on stock unmodified phone claiming system is mounted as r/w

**Resolved** I managed to resolve this by re-enabling all apps I'd disabled using the normal android option in settings (just google newsstand etc.), It wouldn't update from an OTA or a full package of a later version but it would accept an update from YNG1TAS2I3 that it was already on, it updated over the top of itself and after that OTA's seem to be working, there's a lot to do though.
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
Hi, I'm trying to update a family members phone from YNG1TAS2I3. The phone is completely stock, it's never been modified or rooted at all. It only runs apps from Google Play and it was updated to this version by OTA.
Recovery gives the following error when installing the update:
/dev/block/platform/msm_sdcc.1/by-name/system has been remounted r/w; reflash drvice to reenable ota updates
Any ideas? I really really don't want to have to factory reset it, root it or put a custom recovery on it? Can I force flash it over the top to marshmallow without unlocking the bootloader or anything? I've also tried flashing the full rom from stock recovery but that doesn't seem to work either.
Thanks,

Can/Should I install update?

I have my Pixel (obtained from Google) rooted. I have not installed any Kernels or Roms.
I received a notification that there is an Android system update. Is is OK to install this update?
Based on your comments, I assume you are not on Verizon - if that is the case, whether you do an update or not is completely up to you - I have the GOOGLE PIXEL - am using ATT service and I am also rooted - I updated - ultimately I had to re-root - install Twrp and flash the rom I wanted to use - but beyond that - no reason not to - completely up to you. Good luck.
So, if I install the update, I will lose TWRP and root?
You never want to take an OTA update if you have a custom recovery. Can and will brick your phone. As long as you have stock recovery your more than welcome to take an OTA update.
Restored factory boot.img to boot_a and boot_b
When I try to install the update, it says "Installation Problem"

Update 6.0 to 6.0.1 OTA: unroot, recovery, howto?

I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Quark^2 said:
I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Click to expand...
Click to collapse
It's just a simple security patch, not an version upgrade, it can be safely ignored. That said, if you really want it you need to be pure, unmodified stock... Restore your pre-root Nandroid or flash the current factory image with fastboot.

OTA Issue

first of all, i was a rooted user since a long time, but the recent january patch gave me a hard time, so i went through a lot of testing and here are those, if anyone can help me.
I was having MagiskSU.
1. by uninstalling MagiskSU and getting back to stock recovery, i was able to install the october patch OTA.
2. Installed Magisk again, then one day i saw another OTA (this was the january security update), so i followed my previous steps, again uninstalled magisk and went back to stock recovery, but it gave me a status 7 error.
3. I copied the update.zip, tried to flash it manually from recovery, it said error in /sideload/package.zip, status 7.
3. i reinstalled the stock ROM, repeated everything, again i was able to accept the october patch. this time i backed up the october boot.img and restored it before installing the january patch, but same error. i tried to modify the zip file by removing the system checks, but it didn't allow me. Can anyone tell me what is so special about January patch that it simply doesn't get installed?
P.S. I finally gave up and reinstalled stock and all the patches, without root.
Try installing stock recovery. Download the stock firmware for your device from XDA. Unzip. Flash the stock recovery.img using fast boot. Then download the update and let the device do all that is necessary.
P.S. you need to completely uninstall Magisk. Flash the uninstall Magisk.zip (available from Magisk thread at XDA) before installing stock recovery.

Custom ROM

Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.

Categories

Resources