Database Info

OTA update for F1f

A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.

Now I wish I can unroot my phone, lol

You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?

You can extract recovery.img from the ColorOS zip.

If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?

This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.

kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?

MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you

MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)

Deleted

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.

wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete

Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota

wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?

Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader

wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work

Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware

wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23

How to re install the original recovery :crying:

5.1.8 update started

Op started rolling 5.1.8 update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk

5.1.8 is intended for India

dgunn said:
5.1.8 is intended for India
Click to expand...
Click to collapse
no it says it "also contains the 5.1.7 changes for India" since there were issues with 5.1.7 update for India, it also includes the above changes for all other phones as well, so does not seem to be region specific

True.its for all regions.
Sent from my ONEPLUS A6003 using Tapatalk

So, these guys have an actual department dedicated to fixing community reported issues?
That's incredible.

Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app

Done

To those of you that updated and are rooted, can you confirm you're not sporadically losing root like 5.1.7 was doing?

slonn said:
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If it installs it won't be active until a reboot anyway, so as long as u don't reboot it won't change, even after install

I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).

akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
users were reporting losing root / twrp with OTA's
im on 5.1.7, if i update to 5.1.8 via system update wont it remove my twrp and root and kernel?
afaik it does...

I applied the OTA (full due to root) with the system installer and reinstalled Magisk via Magisk Manager BEFORE rebooting.
I never used TWRP on the OP 6 and rooted with Magisk, I don't need it. When I got my OP6, there was no TWRP available.
Magisk patched the boot image.
After a smooth reboot, the system was updated and Magisk kept installed.
And yes, TWRP is lost when updating that way but can be reinstalled via Fastboot if it is needed.

so what the proper procedure on installing updates without getting wiped?
so far the most logical way of doing it is downloading the OTA
installing it via twrp
then install twrp.zip in twrp after update
then magisk, then kernel and boot.

If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.

akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.

@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.

akxak said:
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
Click to expand...
Click to collapse
Well I must have read the question wrong as it sounded like some were losing TWRP and root sporadically after the update. I didn't not read it I just took it another way... sorry for confusion
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Also, just as easy to just wait for Funk Wizard to post the official FULL zip on his thread and just Flash in TWRP. Last time I jumped the gun early I was on the beta 5.1.6 build but saw no issues whatsoever. I'll sit back this time.

Eric214 said:
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
Click to expand...
Click to collapse
If you only run Magisk and stock recovery, install the update, but before reboot , re-install Magisk to the other A/B side , then reboot. Then reboot, you'll have Magisk freshly installed.
This doesn't work for TWRP!
Sent from my Brain using my Keyboard

akxak said:
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
Click to expand...
Click to collapse
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it

virtyx said:
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
Click to expand...
Click to collapse
Of course I do... the Oreo update in December led to an unplanned factory reset of my OP 5 while abroad in Europe for Christmas. With A/B, this would not have happened because the present working OS (with Magisk/root) remains untouched and the update is installed in the other partition. If for any reason the updated OS is not coming up, the systems falls back and boots the previous (working) OS from where a new update or whatever measure can be initiated.
I wonder if (and if not why) TWRP does support that, installing the full update in the unsused slot (including TWRP itself and Magisk) and then boot that slot.
With these two partitions in use, you keep your phone working and avoid a soft brick. For the manufacturer it avoids trouble for the normal user in case an OTA fails...

[FASTBOOT] [daisy] Patched boot.img for V11.0.10.0 (Android 10)

I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The August update is 11.0.10.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.10.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz

Can you tell how to to update I have only magisk Installed I want to keep magisk.

Aadil Gillani said:
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Click to expand...
Click to collapse
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.

a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?

elvinguitar said:
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
Click to expand...
Click to collapse
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.

a1291762 said:
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
Click to expand...
Click to collapse
Will I lose my data by flashing the vanilla image?

elvinguitar said:
Will I lose my data by flashing the vanilla image?
Click to expand...
Click to collapse
Flashing a boot image won't lose data unless you use the wrong version and get unlucky.
Flashing any of the partitions that the OTA touches won't lose data.

a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.

RyanCM said:
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
Click to expand...
Click to collapse
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.

a1291762 said:
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
Click to expand...
Click to collapse
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
---------- Post added at 05:02 AM ---------- Previous post was at 04:24 AM ----------
RyanCM said:
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
Click to expand...
Click to collapse
I successfully flashed the patched boot.img and installed Magisk Manager and the only options I have are to flash a zip in recovery (I don't have recovery, hindsight) and "select and patch a file". I don't know how to proceed with either of those options.
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.

RyanCM said:
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
Click to expand...
Click to collapse
That's why the standard way is to BOOT the patched image and use Magisk Manager to install.
If you want to flash partitions, you need to use the correct set (a or b). Fastboot can tell you (getvar current-slot). Flashing both is useless, since the inactive set of partitions is only used when doing OTA (or dual boot, for some brave souls).
If you're coming from phones without a/b partitions you should definitely read about them. Several things are quite different.

Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat hai mara pass pc nahe ha bootsign.img file link=https://drive.google.com/file/d/1Q172DYs7t7bIo0K_LENCO1OAo6tg0FTz/view?usp=drivesdk and video how to boot sign.img unsing img link=https://youtu.be/ZWphK23KLew

a1291762 said:
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Click to expand...
Click to collapse
Offline ... can you please reup?

networxpsc said:
Offline ... can you please reup?
Click to expand...
Click to collapse
It's hosted on Google drive. It just loaded for me (private window to simulate anon user). The preview won't work because it's not that kind of file. Just click download.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can't boot Magisk 21 and Android 11

Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and the latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"
Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?
Edit:
Was able to boot without issue with the latest Magisk Canary 04995881 (21002).
Apparently, it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271
I'm willing to help anyone else suffering from this issue get their phones booting back up.

nontheoretical said:
Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"
Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?
Thanks in advance.
Click to expand...
Click to collapse
Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812
I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.

dcarvil said:
Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812
I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.
Click to expand...
Click to collapse
I'm on the Oct update and I don't have any modules installed.
It's a clean install so I haven't even had the chance to install modules yet.
I might downgrade to Sept update if I can't root soon.
Apparently it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271

I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.

Bubbler4343 said:
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Click to expand...
Click to collapse
There are some recent comments on running the remove-module script in the github link in post 2. Hopefully something there will help.

Bubbler4343 said:
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Click to expand...
Click to collapse
Not sure about the removing of the modules (maybe try the safe mode trigger built into the new Magisk?)
I was able to successfully boot by flashing the stock boot image, the updating to the latest Magisk Canary 04995881 (21002)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like this was updated recently due to the two issues I listed earlier.
I'm gonna keep my magisk_patched.img for this build of Magisk and try with the latest beta and stable releases as they come out.
I'm happy to help anyone else get their build to boot, provide checksums for sanity checks, etc.

I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!
Directly flashing an image over Android 10 with boot.img patched throws it into fastboot

EndlessBliss said:
I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!
Directly flashing an image over Android 10 with boot.img patched throws it into fastboot
Click to expand...
Click to collapse
Are you using Canary or Stable?
I had to switch to Canary to get it to boot.
I was coming from a clean install so I had no user data to upgrade.

I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL

EndlessBliss said:
I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL
Click to expand...
Click to collapse
It looks like this was only reported by users on pixel 3a and older models.

General Global 11.2.7.7. Root Guide

Frist off Im not responsible for anything that happens to your phone!!!
MUST HAVE UNLOCK BOOTLOADER!!
Steps to root
If you are on 11.2.6.6. and rooted
to take update you must flash stock boot.img can be found in link
reboot to bootloader
fastboot flash boot boot11.2.6.6 .img
once done
fastboot reboot
take update
once update is completed
reboot to bootloader
now down load the PATCHEDBOOT.IMG
and flash
fastboot flash boot patched-11.2.7.7.img
once done
fastboot reboot
BOOM NOW YOUR AR ROOTED!!!
STOCK 11.2.6.6 FIXED AND TESTED THANKS TO
mattie_49​
LINKS / HELP
BOOT.IMGS
HELP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue

Josh McGrath said:
View attachment 5335417
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Click to expand...
Click to collapse
please try new uploaded stock boot imgs there fixed now sorry

so, what I (a newbie to rooting without TWRP) should understand is that if I am on stock I just have to unlock bootloader and flash the patched .img?

FizzyAps said:
please try new uploaded stock boot imgs there fixed now sorry
Click to expand...
Click to collapse
Just updated through updated stock image. Thanks for all your efforts

In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner

Won't let me download the OTA after going back to stock bootloader. I have my CN OP9 cross flashed to global. I keep getting Couldn't Update Installation Problem. Guess i'll wait for Oxygen Update.

notiflux said:
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Click to expand...
Click to collapse
You can't install they update if rooted it errors out

hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?

infamousvincci said:
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
Click to expand...
Click to collapse
please click the help link we have untouched stock 11.2.5.5 there

FizzyAps said:
You can't install they update if rooted it errors out
Click to expand...
Click to collapse
if it detects that your device is rooted, it will switch to downloading the full update instead of the incremental one. Maybe it is different on global ROM, but that's what worked for me

Thanks, updated from 11.2.4.4 with the stock boot img i found in the other thread with this guide.