Updating via OTA breaks TWRP on Nexus 5

[vanitasvitae]

Hi
By now I did two OTA updates and both times I couldn't boot back into recovery to flash superuser right after the updates. The phone only shows the droid with the triangle on top. It seems like the OTA update damages twrp iin some way.

I had to flash twrp manually. When I flash updates via adb sideload, twrp stays untouched. Is this an issue of TWRP or of CopperheadOS?

[thestinger]

CopperheadOS updates the recovery image when it performs an OTA update, so it has switched you back to the stock recovery. In user builds, you need to hold the power button and press volume up to get to the menu because it doesn't want to drop users into a dangerous menu if there's an error. Keeping the recovery up-to-date is important and the intention is that people use the official recovery image so that there's proper signature verification, so it's not going to be worked around.

[thestinger]

CopperheadOS updates the recovery image when it performs an OTA update, so it has switched you back to the stock recovery. In user builds, you need to hold the power button and press volume up to get to the menu because it doesn't want to drop users into a dangerous menu if there's an error. Keeping the recovery up-to-date is important and the intention is that people use the official recovery image so that there's proper signature verification, so it's not going to be worked around.

[polyzen]

Bundling the recovery started in 2016-01-28?

On January 30, 2016 6:31:05 AM EST, Daniel Micay notifications@github.com wrote:

CopperheadOS updates the recovery image when it performs an OTA update,
so it has switched you back to the stock recovery. In user builds, you
need to hold the power button and press volume up to get to the menu
because it doesn't want to drop users into a dangerous menu if there's
an error. Keeping the recovery up-to-date is important and the
intention is that people use the official recovery image so that
there's proper signature verification, so it's not going to be worked
around.

---

Reply to this email directly or view it on GitHub:
#155 (comment)

[polyzen]

Bundling the recovery started in 2016-01-28?

On January 30, 2016 6:31:05 AM EST, Daniel Micay notifications@github.com wrote:

CopperheadOS updates the recovery image when it performs an OTA update,
so it has switched you back to the stock recovery. In user builds, you
need to hold the power button and press volume up to get to the menu
because it doesn't want to drop users into a dangerous menu if there's
an error. Keeping the recovery up-to-date is important and the
intention is that people use the official recovery image so that
there's proper signature verification, so it's not going to be worked
around.

---

Reply to this email directly or view it on GitHub:
#155 (comment)

[thestinger]

It started when CopperheadOS moved to AOSP but the applypatch tool had memory corruption detected by OpenBSD malloc so it wasn't working.

[thestinger]

It started when CopperheadOS moved to AOSP but the applypatch tool had memory corruption detected by OpenBSD malloc so it wasn't working.

[thestinger]

See https://github.com/CopperheadOS/platform_bootable_recovery/commits/marshmallow.

[thestinger]

See https://github.com/CopperheadOS/platform_bootable_recovery/commits/marshmallow.

[thestinger]

It also might not have happened before the switch to proper OTA updates via Android's RecoverySystem.installPackage API.

[thestinger]

It also might not have happened before the switch to proper OTA updates via Android's RecoverySystem.installPackage API.

[polyzen]

Well, I'm on 0120, and have a couple ways to keep TWRP(, Superuser, and GApps):

If you use the updater, you will have to babysit the update. Boot back into TWRP just after the update finishes, before Android boots. If you do not, a recovery (not sure if Android or ChOS) will get installed during that boot. This gives you a chance to update/re-flash Superuser/GApps, if that's your thing.

or

Get the latest installers for your stuff -> boot into TWRP -> install/sideload

[polyzen]

Well, I'm on 0120, and have a couple ways to keep TWRP(, Superuser, and GApps):

If you use the updater, you will have to babysit the update. Boot back into TWRP just after the update finishes, before Android boots. If you do not, a recovery (not sure if Android or ChOS) will get installed during that boot. This gives you a chance to update/re-flash Superuser/GApps, if that's your thing.

or

Get the latest installers for your stuff -> boot into TWRP -> install/sideload

[vanitasvitae]

I think I'll then go for manual download&sideload of new images and avoid using OTA.

[vanitasvitae]

I think I'll then go for manual download&sideload of new images and avoid using OTA.