guys, let's say we got our pie update, ok? if I am to make the upgrade through OTA is it ok with an unlock bootloader?
I hope so. But otas can be installed using the stock recovery
I can confirm on the xt1922-7 Moto G6 Play (and likely all G6 variants) that a locked bootloader is not required to install incremental or version OTA updates. As long as /system, /vendor, /boot & /oem are unmodified and untouched, stock recovery will install the OTA update package with no issues. OTAs can be force installed with TWRP, but this requires a manual and tedious removal of all file integrity checksums within the updater-script of the OTA. Much simpler to use stock recovery to install the OTA, then change back over to TWRP and decrypt /userdata again, re-install systemless root, etc.
Related
Hi, i got my nexus flo a week ago. This is my first nexus device.I have some queries. I have unlocked the bootloader, installed twrp and rooted the device.
Will that prevent me getting OTA?
Also, does having unlocked bootloader and custom recovery cause failure to update the software?
(Not just the JSS15R but future updates to kitkat as well)
Also what is the odex and deodex in this thread? which one should i flash?
http://forum.xda-developers.com/showthread.php?t=2383059
littleromeo said:
Hi, i got my nexus flo a week ago. This is my first nexus device.I have some queries. I have unlocked the bootloader, installed twrp and rooted the device.
Will that prevent me getting OTA?
Also, does having unlocked bootloader and custom recovery cause failure to update the software?
(Not just the JSS15R but future updates to kitkat as well)
Also what is the odex and deodex in this thread? which one should i flash?
http://forum.xda-developers.com/showthread.php?t=2383059
Click to expand...
Click to collapse
Odex vs deodex: http://forum.xda-developers.com/showthread.php?t=2200349
If I understand well, updates will 'fail' with custom recovery, whereas the update is flashed the firmware version number shows the old version. Explained in the guides somewhere.
Sent from my Nexus 7 (2013)
littleromeo said:
Hi, i got my nexus flo a week ago. This is my first nexus device.I have some queries. I have unlocked the bootloader, installed twrp and rooted the device.
Will that prevent me getting OTA?
Also, does having unlocked bootloader and custom recovery cause failure to update the software?
(Not just the JSS15R but future updates to kitkat as well)
Also what is the odex and deodex in this thread? which one should i flash?
http://forum.xda-developers.com/showthread.php?t=2383059
Click to expand...
Click to collapse
Unlocked bootloader has no direct negative effect on ota installs.
With an unlocked bootloader you might do further actions which can affect the ota like modify or delete /system files. You might install an enhancement like apm. Those, among others, would prevent the ota update from completing.
Now normally root by itself would not prevent an ota update, but there was an issue with SuperSU v 1.51 and earlier which did prevent the ota install from completing. This was fixed in SuperSU v1.55 and above.
Installing twrp will not block the ota.
The ota will disable root and overwrite custom recovery by default.
If you would like to prevent that behavior, the easiest way is to
copy the ota update.zip and supersu update.zip to your virtual sdcard
boot into twrp
install ota update.zip
immediately (prior to reboot) re-install supersu
sfhub said:
Unlocked bootloader has no direct negative effect on ota installs.
With an unlocked bootloader you might do further actions which can affect the ota like modify or delete /system files. You might install an enhancement like apm. Those, among others, would prevent the ota update from completing.
Now normally root by itself would not prevent an ota update, but there was an issue with SuperSU v 1.51 and earlier which did prevent the ota install from completing. This was fixed in SuperSU v1.55 and above.
Installing twrp will not block the ota.
The ota will disable root and overwrite custom recovery by default.
If you would like to prevent that behavior, the easiest way is to
copy the ota update.zip and supersu update.zip to your virtual sdcard
boot into twrp
install ota update.zip
immediately (prior to reboot) re-install supersu
Click to expand...
Click to collapse
Thank you for the guide, updated to JSS15R. There were no touchscreen problems for me before the update and everything is just like before even after update. Hope someone comes up with a changelog soon.
I have rooted my Nexus 7 wifi 2012 tablet with TWRP
I don't want to keep un-rooting, applying ota updates then re-rooting my tablet. Is there an easy way. Maybe modified images i can use on a rooted tablet which i can install via the install option in twrp recovery loader.
I also notice that Nexus root tool kit has a ota sideload update option in the advanced menue.
So my question is where are the modifies ota update files if they exist as I don't want to keep un-rooting, rerooting each time to apply official ota updates. I have searched the net and can't find modifies ota updates?
My OTA failed due to root and modifications so I extracted system.img and boot.img from the 5.1 tarball and flashed them using Nexus Root Toolkit. Works well.
I'm going through the same issue - I want to keep running stock, but every time an OTA update comes in, it bugs me for an update until I go through the whole process of finding the files elsewhere, using the Toolkit to flash them etc etc.
Is there a better way to do this automatically? Can I find the downloaded OTA package on the Nexus and just flash it from there?
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
I assume that means waiting for someone to post the update?
If you want to wait for someone to make a prerooted image, then yes. Otherwise just download the official factory image (Google it) and go for it.
Google doesn't always release OTAs and factory images at the same time, so some waiting will probably always be involved...
Drives me crazy. TWRP used to be able to intercept a OTA flash, flash the needed images, detect you lost root and ask to restore root.
Somewhere that disappeared.
I just flashed a very old stock and took every OTA to 5.0.2, rooted, setup... now getting bombarded with 5.1.1 update notification. Ugh
Didgeridoohan said:
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
Click to expand...
Click to collapse
I need to flash the latest lollipop image to my rooted nexus with TWRP. I know where to find the images but don't remember how to flash it. What exactly are the steps and how do I leave out userdata.img ?
And what are the steps to reroot lollipop?
Thanks
i keep getting the offer to download the 5.1 update but when i do it dloads it then tries to reboot into recovery to flash it but it obviously boots into TWRP recovery which is no good.
So the question is when it dloads the update where does it dload to?
and could i flash it from TWRP if i find it?
I have my M8 running the GPE ROM which I have rooted. On previous Android versions, I was able to apply the OTA albeit manually in the custom recovery.
The last few OTA's I have attempted on my M8 have been a complete failure and I have ended up having to wipe and apply a factory image. Recently therefore i have been ignoring the updates (L-MR1 has been bugging me to install for weeks!)
Is there a method of applying these updates with the phone rooted?
Thanks
An ota will install with root applied BUT you have to make sure the system partition is untouched. This means that ALL the "stock" apps need to be there and nothing can be removed. xposed is also a known bugger to refuse official ota updates. And a must have is the HTC stock recovery. An ota never installs through a custom recovery !
I posted a while back in February about how I was unable to install the December Security OTA Update on my XT1710-01 RETUS, but I didn't get any responses. I believe that I have learned that this is due to the fact that I have unlocked my bootloader and rooted with Magisk (however I have not flashed TWRP or a custom recovery, if that makes a difference).
It looks like some other users had this issue too, and that some of you were able to get by with flashing a different Stock ROM in to get back to Stock and then flashing the OTA update.
Is that what I need to do in order to be able to flash my OTA updates in the future? Is there any other method aside from flashing the ROMs to get the updates too install on my phone?
I received an OTA patch security for aljeter xt1922-5 retbr. The package is identified as PPPS29.55.35.12-3. I don't know if there's anyone working on a sideload package of this that I could flash with twrp. The device has only partition A to boot.
twrp and magisk were installed on factory rom 8.1, oreo and the pie upgrade OTA went smoothly, overwriting twrp for the recovery stock and magisk, I just had to install magisk zip and twrp again later. But this is just a security paych and it won't even have boot and recovery partitions included, as far as I know. so if I'm correct about that, it won't be able to "auto apply" like the previous one, so:
is twrp able to flash the patch?
can I just roll back to stock and apply the OTA?
finally, is there a way to install this update without all the work of reverting to stock recovery and stock ROM via ADB?
I've read similar topics for other model versions here on XDA, but still can't be sure about this issue. I read reports of users who were able to flash OTA with twrp and others not. How should I proceed? I really do not wish to risk brick the device.