Database Info

Root new OTA updates [September Update]

Hello guys,
I have successfully rooted September update with the help of Flashfire. As there is no fastboot images released at the a time of writing this so I have to make use of dual slots of system. This can be adopted for future OTA's as well:
The process requires you to boot into ur previous slot. It mean that after you have updated you phone boots from updated slot but old slot is still there which can be rooted easily.
Now you have boot from old slot
Code:
fastboot set_active x
x means your old slot before update
Now u have to root this slot by flashing patched boot image.
After successful root use flashfire to backup your updated slot's boot and system , u can use any format I recommend use fastboot flashable.
Now you can use backed up boot to flash on updated slot and enable ever root while flashing.
Now you have rooted your updated slot .
Now you can boot into updated slot by using above code with 'x' being your updated slot identifire.
PS.
Stock September Boot
First boot might take long similar to flashing SuperSU via twrp ( it reboots after boot logo appears)
I used this https://forum.xda-developers.com/mi-5x/how-to/root-mia1-twrp-t3678453 to root my August build.

Google Inc said:
Hi how do i confirm whether a or b slot are previous update?
I need to reboot for further checking?
Click to expand...
Click to collapse
U can guess without rebooting in magisk manager, by boot image location
/dev/block/mmcblk0p22 --> means slot A
/dev/block/mmcblk0p23 --> means slot B
Also fast boot commands can be used for that
Sent from my Mi A1 using Tapatalk

m.atif said:
U can guess without rebooting in magisk manager, by boot image location
/dev/block/mmcblk0p22 --> means slot A
/dev/block/mmcblk0p23 --> means slot B
Also fast boot commands can be used for that
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
I guess slot A is August update and slot B is September update...
Reason: We had slot A activated by default so any new update (say September) will be installed in another slot (say B)...
I rebooted to slot A... opened Settings app -- About Phone -- It says August security patch...
Trying your method to root... Will reply back with the results...
thanks a lot bro

I said that bcz if someone flashes fastboot images , slot a is used for flashing by the provided falsh_all.bat file in stock image file.

Fastboot set _active a or b is not working.

Mr.Crucial said:
Fastboot set _active a or b is not working.
Click to expand...
Click to collapse
Use adb tools from chainfire's autoroot zip
Sent from my Mi A1 using Tapatalk

Google Inc said:
Hi how do i confirm whether a or b slot are previous update?
I need to reboot for further checking?
Click to expand...
Click to collapse
Execute this command in fastboot - fastboot getvar all

m.atif said:
Use adb tools from chainfire's autoroot zip
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Thanks I have rooted my device with september security patch by using different way but got help from your guide

Greetings good friend! Can someone translate this to lay-man-terms coz it's too technical and although I am trying, it's really hard to understand. ???
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Desire 1007 said:
Thanks I have rooted my device with september security patch by using different way but got help from your guide
Click to expand...
Click to collapse
Mate can you elaborate?? Thank you..

melmarPH said:
Greetings good friend! Can someone translate this to lay-man-terms coz it's too technical and although I am trying, it's really hard to understand.
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Mate can you elaborate?? Thank you..
Click to expand...
Click to collapse
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.

Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.

mobadass said:
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
Click to expand...
Click to collapse
Yeah! I wish I saw your post sooner. Anyway I flashed the stock boot.img of september and the bootloops ceased albeit with no root

mobadass said:
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
Click to expand...
Click to collapse
I didn't state a word about magisk, bcz I tried that in August build itself when magisk 14.1 beta was released , it didn't boot so posted about that in magisk thread too, u can't get any logs if the phone restart from splash screen again and again that's bootloop, some kernels have ADB enabled by default in kernel that way we can have logs but it's not possible in stock boot patched by magisk.
Even flashing magisk from flashfire gives same result.

Help!!! Unable to update to September
Hi,
I'm on the August update and I have successfully rooted. But I am unable to install September OTA to update. Can you please advise?

ForTheOne said:
Hi,
I'm on the August update and I have successfully rooted. But I am unable to install September OTA to update. Can you please advise?
Click to expand...
Click to collapse
If u happen to have a unmodified system partion , only flash stock boot.img through fastboot or flashfire (note to disable ever root)
If u have a modified system , them flash system.img from August update fastboot files with boot.img , I will suggest you to do this as you don't know if have modified the system or not (even remounting system bricks OTA). To do so
Code:
fastboot flash system_x system/image/location.img
fastboot flash boot_x boot/image/location.img
x means ur current active slot (a or b)
U can find stock files from miui.com downloads section

Anyine has normal boot.img for october update? or even modified?

any link to stock september boot image?

Root for all Nokia6.1 /6.1 plus /x6 devices

How to root your device using magisk?
all the credits go to Magisk team
there`s too many thread about rooting phone using magisk patch method but in this thread i want to make it easier for the newboi it's working on all Nokia 6.1 / Nokia x6 / Nokia 6.1 plus
check first which security patch you have then pick the one matching it
don`t flash it
only boot it don`t flash it if you flash it you probably going to brike your WIFI
In case you flash it by mistake reflash your stock boot
INSTALLATION
1- bootloader unlocked
2- enable usb debugging from developer option
3-adb and fastboot tools
4- use this codes
Code:
adb shell
Code:
reboot bootloader
now we boot it temporary
Code:
fastboot boot <File name>.img
5- after your system boot up install Magisk Manager from here
https://******************/downloading-magisk-manager
6- go to Magisk manager tab install then choose install dirctly recommanded then after the process done reboot
7- now your phone rooted enjoy
8- don't forget to hit like
DOWNLOAD
February patch Pie-9.0
https://drive.google.com/file/d/1L4xnrx9_I3hXou94JT5ED32ju3-Af-Ly/view?usp=drivesdk
January patch Pie-9.0
https://drive.google.com/file/d/1LA9FceK-m4Eyx-NGgqtiD0SFVpGCE2Iv/view?usp=drivesdk
October patch Pie-9.0
https://drive.google.com/file/d/1oP5Eww3ew8yem4DEddDlimayAQ-v9JaO/view?usp=sharing
September patch
https://drive.google.com/file/d/1ub0eBYAzlrpdNsVjEFdNzNU_Yx0kgtsi/view?usp=sharing
August patch
https://drive.google.com/file/d/1B2U_mmqHzLTUl7WXZtWgywwLvfbggcOR/view?usp=drivesdk
June patch
https://drive.google.com/file/d/1FNZ6uG42n_wf6wQiQyB6RJ6ZQ2eRvQZG/view?usp=sharing
July patch
https://drive.google.com/file/d/1jOUe_v0p9xqHdhialMeuwHZ_JRgZcxgb/view?usp=sharing

Reserved

#Reserved

Thanks Maher for you tutorials and help. I was able to instal Global Firmware and update to August OTA. I then used this rooting guide and it worked great. You should link this rooting guide to the last step on the Global Firmware tutorial as optional for people who want to root.

Any root for September? My phone auto updated from August patch. Thanks for all the hard work!
P.S. When a new security patch is installed is it supposed to unroot your device and you have to re-apply one of the patches above to fix?

lespy_laz said:
Any root for September? My phone auto updated from August patch. Thanks for all the hard work!
P.S. When a new security patch is installed is it supposed to unroot your device and you have to re-apply one of the patches above to fix?
Click to expand...
Click to collapse
now uploading patch boot for September

Maherabed1986 said:
now uploading patch boot for September
Click to expand...
Click to collapse
Is already available the September security patch for 6.1 plus ?

neodante said:
Is already available the September security patch for 6.1 plus ?
Click to expand...
Click to collapse
Yes sir uploaded it already

Maherabed1986 said:
Yes sir uploaded it already
Click to expand...
Click to collapse
Thanks for uploading bro. One question, did you receive the september patch update already? I haven't got mine on nokia 6.1 plus.
Also i just wanna confirm the steps i should do, to unroot and updating to September update. ( I am currently rooted with magisk and august patched boot image). Thanks.

raza_maestro said:
Thanks for uploading bro. One question, did you receive the september patch update already? I haven't got mine on nokia 6.1 plus.
Also i just wanna confirm the steps i should do, to unroot and updating to September update. ( I am currently rooted with magisk and august patched boot image). Thanks.
Click to expand...
Click to collapse
i have Nokia 6.1 not plus but this method working on all nokia 6 ,6.1,6.1 plus,x6,7 so on our 6.1 yes we received September update already
to unroot you need to flash your stock boot.image

Maherabed1986 said:
i have Nokia 6.1 not plus but this method working on all nokia 6 ,6.1,6.1 plus,x6,7 so on our 6.1 yes we received September update already
to unroot you need to flash your stock boot.image
Click to expand...
Click to collapse
Okay great. Thanks.

Can you still update after this? Will you have to re-root?

bobbyraduloff said:
Can you still update after this? Will you have to re-root?
Click to expand...
Click to collapse
yes you still can if your system not modified or you have installed magisk modules

i ca't open wifi when flash September patch on my Nokia X6 (TA 1099) hmmm,maybe i'll try again

phanmanhcuong said:
i ca't open wifi when flash September patch on my Nokia X6 (TA 1099) hmmm,maybe i'll try again
Click to expand...
Click to collapse
bro don't flash it i mentioned that 1st post you will brike your wifi only follow the guide please to be in safe side

Maherabed1986 said:
bro don't flash it i mentioned that 1st post you will brike your wifi only follow the guide please to be in safe side
Click to expand...
Click to collapse
i've forgot it,sorry man
---------- Post added at 05:02 PM ---------- Previous post was at 04:52 PM ----------
i've boot it but my phone still can't open wifi :/

phanmanhcuong said:
i've forgot it,sorry man
---------- Post added at 05:02 PM ---------- Previous post was at 04:52 PM ----------
i've boot it but my phone still can't open wifi :/
Click to expand...
Click to collapse
ofcourse my friend you already broke your wifi now you must flash stock boot image ask if someone have it on the group after that come again and follow the thread step by step

Maherabed1986 said:
ofcourse my friend you already broke your wifi now you must flash stock boot image ask if someone have it on the group after that come again and follow the thread step by step
Click to expand...
Click to collapse
Bro, i am rooted with magisk via patched boot image. So to install OTA i need to restore stock boot image right? For that can i restore stock image by going to magisk->uninstall->restore images?

raza_maestro said:
Bro, i am rooted with magisk via patched boot image. So to install OTA i need to restore stock boot image right? For that can i restore stock image by going to magisk->uninstall->restore images?
Click to expand...
Click to collapse
in order to uninstall magisk you need twrp and OTA not working with custom recovery so easier for you to flash the stock boot

Maherabed1986 said:
in order to uninstall magisk you need twrp and OTA not working with custom recovery so easier for you to flash the stock boot
Click to expand...
Click to collapse
I am think i did not made myself clear. I am not on twrp, still on stock recovery. I rooted via booting in patched boot image and installed magisk.

March Boot file - stock & patched

In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
These files are to install Magisk. Please only flash it if you are already on March update. This is not March OTA!
Link courtesy of @i5lee8bit; March OTA patched with Magisk 20.4 https://www.androidfilehost.com/?w=files&flid=306923

Dear Mushtafa, great thanks to you! I've been looking for this all day. Thank you!

mushtafa said:
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
Click to expand...
Click to collapse
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.

onlyguynamedniles said:
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
Click to expand...
Click to collapse
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?

mushtafa said:
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
Click to expand...
Click to collapse
No I'm still on January, I never got the Feb OTA and didn't bother to try manually since it didn't seem significant enough but I wanted this March update because of the new Pixel drop feature set.

You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware

mushtafa said:
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
Click to expand...
Click to collapse
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.

otrobruno said:
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
Click to expand...
Click to collapse
You flashed the March boot.img on your February firmware? Why?

mushtafa said:
You flashed the March boot.img on your February firmware? Why?
Click to expand...
Click to collapse
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?

otrobruno said:
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
Click to expand...
Click to collapse
If you're not getting the March OTA, you need to download it from Google and sideload it. https://developers.google.com/android/ota
There is a thread here somewhere which shows how to do this.
The boot.img I shared above is for people who need it for Magisk and saves them downloading the ~2GB factory file.

Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?

wonderlander17 said:
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
Click to expand...
Click to collapse
Affirmative :good:

dang is it that hard to understand . if youre build number does not look exactly like this QQ2A.200305.003 then do not use these boot.img's
its that simple this is not to upgrade you to the march sec patch with root this is for people already on the march sec patch to use to gain root

FIXED IT!! After taking the March update I flashed this patched img the phone boots up to a black screen. If you use the power button it brings up a White menu with "power off" "restart". So then I turn the phone off and load fastboot and flash the stock boot img and everything works again. Any ideas? Figured it out.... Magisk modules that were running.

Can you flash any of them without the use of a computer?

mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Nope. TWRP or any other recovery is not yet compatible.

mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Yes with ex kernel manager it's possible

Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923

i5lee8bit said:
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
Click to expand...
Click to collapse
Added to OP, cheers

Magisk crashing when trying to patch boot.img (March Patch)

As the title says, Magisk crashes when I try to patch the boot.img after installing the latest March security patch on my Pixel 3a.

You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...

biontx said:
You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...
Click to expand...
Click to collapse
Thanks for letting me know, should've checked the Magisk Canary thread first ^^
However, I get into a bootloop when I try to downgrade back to the February patch. Guess I'll just wait it out...

I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.

NinjaCoool said:
I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.
Click to expand...
Click to collapse
That's weird. How did you update? Magisk OTA, sideload OTA or flashing March factory image?
In any case, would you mind sharing your patched boot.img? I'm not sure I want to live without root until they fix it ^^
EDIT: Scratch that, it seems that flashing a prepatched boot.img causes a bootloop. They probably changed something in the files, that causes the issues when flashing the factory image.

I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.

AndDiSa said:
I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.
Click to expand...
Click to collapse
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.

I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.

Velcorn said:
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.
Click to expand...
Click to collapse
If I remember correctly versions before 19.1 /7.3.x didn't support Android 10. For me 7.5.1 worked flawlessly.

yaconsult said:
I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.
Click to expand...
Click to collapse
Weird, thanks for letting me know. I manually updated through flashing the March factory image and when I patch the boot.img through MM 7.5.1 I just get into a bootloop.

I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.

dkryder said:
I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.
Click to expand...
Click to collapse
Could you upload your patched boot.img please?

It said file too large when I tried. It's about 30MB. Not sure what's up with that.

Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
biontx said:
Could you upload your patched boot.img please?
Click to expand...
Click to collapse
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobootpatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2

captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Super, tx

Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.

captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...

Velcorn said:
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...
Click to expand...
Click to collapse
Sorry it didn't help, thanks for letting me know though, but I'm out of ideas now

MeowDotEXE said:
Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.
Click to expand...
Click to collapse
Me too. It's the first time now with the March update.
"cts profile: false"

Made an account to say I had the same problem with Pixel 3XL and I did what captain sideways posted. I went to the github for magisk, took the apk from the latest zip file release and installed that. I was able to patch my boot image afterwards. Root works fine. I flashed the patched boot image to both slots. However, the ctsProfile does fail like mentioned above.

[UPDATE/KEEP ROOT GUIDE] JAN 2021 (RQ1A.210105.003) "CORAL" Magisk/Stock Boot Images

GravityBox [R] was pre-released today! Thus, I was able to update, using this very method, all the way from August 2020 thru January 2021. Entire process took only about an hour, with no hiccups. =) =) =)
But luckily, that also means I can actually start confirming again, personally, that everything is working fine. I can happily report everything is working great after this update. SafetyNet is passing with the correct configurations, and January 2021 build is working perfectly so far with Kirisakura 6.6.6 (why @Freak07, why did you have to release as this particular version number?? lol).
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ1A.210105.003, Jan 2021"!
Magisk v21.2 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709333
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709334
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145709335
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.201205.008, Dec 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.201205.008-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675600188
coral-rq1a.201205.008-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675600190
January 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq1a.210105.003-ad8d5ecc.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq1a.201205.008-factory-boot.img
3. fastboot flash dtbo coral-rq1a.201205.008-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq1a.210105.003-ad8d5ecc.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq1a.210105.003-magisk_patched-21.2.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16

[EDIT 01-13-2021] YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
Please see this post: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84285539

Thank you for the update guides as always.

Just wanted to say a quick thanks. Worked like a charm!

Worked like a charm

I'd like to ask someone for help! If you haven't updated yet (i.e. you're still on 2020-12 patch level [non-AT&T]), and NOT using Edge Sense Plus (Active Edge Mod in Magisk Manager and/or EdXposed Manager) NOR any of Tulsadiver's theming mods (3minit / clock / 9tiles / etc), could you please send me your stock SystemUIGoogle.apk file? You can find it, using a root capable file explorer app, under:
(root) /system_ext/priv-app/SystemUIGoogle/SystemUIGoogle.apk
It needs to be the stock, completely unmodified .apk, which is why I'm asking to make sure you're not using any of those mods I mentioned. Or, you could disable those mods temporarily (both Magisk and EdXposed), reboot, and pull the .apk file. Unfortunately whenever I pull it from Google's factory system image always seems to be corrupted. Would just be easier for me if I could get it from someone's up-and-running system...
Thanks!! I really hope someone can do me a solid...
Or, does anybody know if it's safe to "downgrade" to December 2020? Using the full factory image and removing -w flag (and replacing boot.img with magisk patched)? I would think it would work, but I've never tried, nor needed, to flash the previous month's firmware before.

i5lee8bit said:
I'd like to ask someone for help! If you haven't updated yet (i.e. you're still on 2020-12 patch level [non-AT&T]), and NOT using Edge Sense Plus (Active Edge Mod in Magisk Manager and/or EdXposed Manager) NOR any of Tulsadiver's theming mods (3minit / clock / 9tiles / etc), could you please send me your stock SystemUIGoogle.apk file? You can find it, using a root capable file explorer app, under:
(root) /system_ext/priv-app/SystemUIGoogle/SystemUIGoogle.apk
It needs to be the stock, completely unmodified .apk, which is why I'm asking to make sure you're not using any of those mods I mentioned. Or, you could disable those mods temporarily (both Magisk and EdXposed), reboot, and pull the .apk file. Unfortunately whenever I pull it from Google's factory system image always seems to be corrupted. Would just be easier for me if I could get it from someone's up-and-running system...
Thanks!! I really hope someone can do me a solid...
Or, does anybody know if it's safe to "downgrade" to December 2020? Using the full factory image and removing -w flag (and replacing boot.img with magisk patched)? I would think it would work, but I've never tried, nor needed, to flash the previous month's firmware before.
Click to expand...
Click to collapse
Well I have a pixel 4 xl and I've rolled back to android 10 back in October, due to 11's bugs. So in my experience it is safe to roll back to previous updates. Being that I flashed

Suavie103 said:
Well I have a pixel 4 xl and I've rolled back to android 10 back in October, due to 11's bugs.
Click to expand...
Click to collapse
Would you mind sharing what kind of bugs you are facing on 11 please? I was going to update from 10 soon.

Ghisy said:
Would you mind sharing what kind of bugs you are facing on 11 please? I was going to update from 10 soon.
Click to expand...
Click to collapse
No those bugs were when 11 was first released. The January 11 update is perfectly fine imo. You should update

Thanks as always. Works like a charm

I just got the OTA update this week (1-14-2021) and was just wondering if the 1st post is still valid? Right now I am on Android 11 (RP1A.200720.009). Which files do I need to download from Google to go from RP1A.200720.009 to the latest OTA? Thanks in advance!

I am confused on number 8 ( 8. fastboot flash boot coral-rq1a.210105.003-magisk_patched-21.2.img ) where do I get that patched img file from? I am already rooted with Magisk vf5593e05 (4835)

One more small question.... what does DTBO stand for? I have never heard of that?

OMG!!!! I did it!!! Woo Hoo!!! Took me about 30 minutes! I did not flash the " coral-rq1a.201205.008-factory-dtbo.img " because I am not using a custom kernel just straight stock!
It scared me at first because it was taking so long for my Pixel 4 Xl to boot back up but it finally came back on.
I also had to update Magisk to f5593e05 (21401).
I have now went from Android 11 (RP1A.200720.009) to Android 11 (RQ1A.210105.003) and I still have ROOT!!!
Thank you @i5lee8bit for this easy to use guide! I am still a noob using ADB but I am learning more and more!
Oh yea... you said "GravityBox [R] was pre-released today!" where can I get that from? Does it work good?
Is anyone monitoring this thread? I feel all alone!

Perfect write-up. Followed it as instructed, had my phone rebooted with the new update in less than 10 minutes. Even had to double-check that it actually updated since it rebooted so fast!
Thanks!

The February update is out. Anyone got the magisk patched file?

For some reason I'm getting installation error when trying to patch boot image. Tried canary & stable magisk APK. Can someone confirm this?

I got the same, on canary

No issues here. Everything worked first try. Updating phone now, guide will be up soon (assuming no other errors otherwise).
Edit: It's up: https://forum.xda-developers.com/t/...5-004-coral-magisk-stock-boot-images.4227845/
Will also be editing the Active Edge Mod for Edge Sense Plus module really soon, and will be indicated on that thread: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/

i5lee8bit said:
No issues here. Everything worked first try. Updating phone now, guide will be up soon (assuming no other errors otherwise).
Click to expand...
Click to collapse
Same here. Working fine with Beta 21.4 on February update.