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?

October 2018 Security Patch

Just checked updates and new October security patch was found.
Captured OTA file:
https://workupload.com/file/jQDkURkS
MD5: 69a58a09918a4735f47de53e478854aa
SHA1: d8a6e5d87a4bb2f5d26bd1b28be829d6b2f3be37
Edit: Couldn't extract the payload.bin inside the archive. :-/

thanks for the info. do you know where i can see the changelogs?

Changelogs are usually never published. This patch looks like a plain security update due to its size of only 82mb.

Doublepost, sorry!

Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB

Txatxiquesi said:
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Click to expand...
Click to collapse
Are you sure this is for the A2 LITE? My version says V9.6.9.0.ODLMIFF.

thorin0815 said:
Are you sure this is for the A2 LITE? My version says V9.6.9.0.ODLMIFF.
Click to expand...
Click to collapse
Ok, i think maybe is the version of the standard A2 (no lite).

There is indeed a security patch for the month of October. Havent updated yet. Its size is 82MB.

Yes just got updated. Magisk and xposed still intact and working perfectly.

Maximuous said:
Yes just got updated. Magisk and xposed still intact and working perfectly.
Click to expand...
Click to collapse
did you just update without flashing the original boot.img from magisk?

Jordan~Kurniawan said:
did you just update without flashing the original boot.img from magisk?
Click to expand...
Click to collapse
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.

Is there chance to install it from adb?

It's just a security patch, yes. No bugfixes. Some bugs including the shutter lag is still there.

Maximuous said:
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Click to expand...
Click to collapse
i thought when you say intact you updated without first flashing the stock boot.img

Maximuous said:
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Click to expand...
Click to collapse
How could you follow the guide? For me it doesn't work. Magisk says "Stock backup does not exist"
Did you place a file manuelly? If yes where exactly?
The only way let magisk creating is a backup by flashing it with twrp, but i want to wait for official twrp first
update - i resolved my problem:
1. i flashed with fastboot the stock boot image of current running version 9.6.6 to the inactive slot, in my case "slot b" by cmd line:
fastboot flash boot_b boot.img
2. i did run magisk - install to inactive slot -> magisk did backup stock image of inactive slot
3. after reboot i was able to use "uninstall - restore stock image" to do the ota update (like described in the guide)

Is it possible to do so?
I have magisk in the Oreo version of September. And I want to upgrade to October. And I thought about doing this:
Install official twrp.
Install original boot img. Current
Install OTA via Twrp.
Install boot patched img. Current
Install magisk via twrp.
And then reboot the phone.
Is it right?
Sent from my Mi A2 Lite using XDA-Developers Legacy app

Ithao said:
Is it possible to do so?
I have magisk in the Oreo version of September. And I want to upgrade to October. And I thought about doing this:
Install official twrp.
Install original boot img. Current
Install OTA via Twrp.
Install boot patched img. Current
Install magisk via twrp.
And then reboot the phone.
Is it right?
Click to expand...
Click to collapse
No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.

BubuXP said:
No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.
Click to expand...
Click to collapse
Ok. Thank you. I understood now how it works.
I did it that way. I had no problems.
https://forum.xda-developers.com/showthread.php?p=77931735
Sent from my Mi A2 Lite using XDA-Developers Legacy app

Txatxiquesi said:
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Click to expand...
Click to collapse
Does second sim slot work?

HTCDevil said:
Does second sim slot work?
Click to expand...
Click to collapse
I personally only use first slot.

[LINK] Internal OTA update to Android PIE for Nokia 8

Thanks to our friend @hikari_calyx, who provided Internal OTA Update zip package to Android Pie for Nokia 8, we can test it before Nokia release it. The link contains two zips
1) December patch for Oreo for Nokia 8
2) Update to Pie for Nokia 8
Link:
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
Preconditions:
1) All must be Stock, no root, magisk, xposed, no mods etc.
Steps you have to do is:
1) Download NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip - this is December Security Patch
2) Update manually (2 ways)
a)
- Copy the file on internal memory root folder
- Dial
Code:
*#*#874#*#*
and there will be possibility of update (this way you may use this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#ota-installation to keep Magisk)
b)
- Connect your phone to PC
- Go to stock recovery (https://www.youtube.com/watch?v=RmewL1i50c0)
- Choose Apply Update from ADB,
- Type
Code:
adb sideload path_to_zip/NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip
where path_to_zip is a path to the location of the file
- Wait and reboot phone, you should have December Security Patch
3) Repeat whole steps froim point 2) for the NB1-5110-0-00WW-B03-488L-0-00WW-B01-update.zip
4) Since @hikari_calyx provided us next internal update, repeat steps for NB1-5110-0-00WW-B05-5110-0-00WW-B03-update.zip and NB1-5110-0-00WW-B07-5110-0-00WW-B05-update.zip.
5) If you want to root your phone, here you may find stock and patched with twrp boot.imgs provided by @THMSP
https://mega.nz/#F!r3RUnaiC!p8FZqNpiPLK8XNwYusJv1Q
Like I wrote at the beginning, it is internal update, so I would strongly recommend to unlock bootloader in case something goes wrong. Additionally it is not known at the moment whether it can be possible to update to official version when it comes, so most likely downgrade will be necessary.
As always, you do all on your own risk and I won't be responsible for any damage you do to your phone.
PS: Here is the proof:

I'm rooted with magisk, can I update uninstalling magisk? or need reinstal firmware with OST?

Gemmik said:
I'm rooted with magisk, can I update uninstalling magisk? or need reinstal firmware with OST?
Click to expand...
Click to collapse
Flash stock or restore stock by magisk, and than give it a try. If it won't work, than OST, downgrade and upgrade again till November, and than zip provided by @hikari_calyx. And than use images provided by @THMSP to root.

If I move those otas to internal download folder and do as described above any chances to go wrong !?
Bootloader locked unrooted and unmodified attached all
Too good to be truth

Just_Rise said:
If I move those otas to internal download folder and do as described above any chances to go wrong !?
Bootloader locked unrooted and unmodified attached all
Too good to be truth
Click to expand...
Click to collapse
There is a chance that you lose possibility for later OTA updates. I would not try to update without unlocking bootloader

czupyt said:
There is a chance that you lose possibility for later OTA updates. I would not try to update without unlocking bootloader
Click to expand...
Click to collapse
You're right ,didn't thinked about that
Really divided about what to do now
Thanks anyway !

Confirmed working on TA-1012

Known issue on NB1-5110:
The lock screen can't be reconfigured - it will crash when you try to change.

I just tried to install on a Mexico TA-1012 and not working, returns an error "package is for source build 00WW_4_88K but expected 00WW_4_84G, installation aborted"
Did you know what is the problem?

rocalino said:
I just tried to install on a Mexico TA-1012 and not working, returns an error "package is for source build 00WW_4_88K but expected 00WW_4_84G, installation aborted"
Did you know what is the problem?
Click to expand...
Click to collapse
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.

Sahilsinghlodhi said:
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Click to expand...
Click to collapse
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.

czupyt said:
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
Click to expand...
Click to collapse
So updates from 488B to 488K need to be uploaded.

On a side note - Pie requiring December security patches means HMD will miss "by end of November" deadline.

revanmj said:
On a side note - Pie requiring December security patches means HMD will miss "by end of November" deadline.
Click to expand...
Click to collapse
Seems so

Solved

Toedwarrior said:
Guys i accidentally flashed stock november boot to october system while doing that now my phone got stuck on Nokia screen and hardwarebuttons is not working. I tried adb command device gets listed but it says unauthorized. What should i do?
Click to expand...
Click to collapse
To be clear - You flashed November /boot partition to October /system partition? Switch slots from active to inactive. If you flashed November boot to October boot, flash again October boot. All in all you can use OST LA to downgrade and upgrade again.

czupyt said:
Preconditions:
1) All must be Stock, no root, magisk, xposed, no mods etc.
......
2) Update manually (2 ways)
a)
- Copy the file on internal memory root folder
Click to expand...
Click to collapse
How does this possible? Without rooting the phone you can`t access root folder, or i am wrong?

phm83 said:
How does this possible? Without rooting the phone you can`t access root folder, or i am wrong?
Click to expand...
Click to collapse
Internal memory root folder, not /

Thank you! Updating as we speak :fingers-crossed:

Sahilsinghlodhi said:
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Click to expand...
Click to collapse
Yes, I know and thats what I tryied to do but unsuccessfully
---------- Post added at 01:30 PM ---------- Previous post was at 01:24 PM ----------
czupyt said:
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
Click to expand...
Click to collapse
hikari_calyx said:
So updates from 488B to 488K need to be uploaded.
Click to expand...
Click to collapse
After that error, I donwloaded the updates from June to november which someone else's uploaded to his gdrive but I got the same error when tried to update via sideload

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.