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.

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.

January Patch

Latest update is out on the developer page of Google.

Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
?
I did not have to use a "patched" boot image thirty days ago . . . Normal old boot image did the trick.
.
You have to boot twrp but what do we gain by loading the twrp zip ? . nandroid backups ?

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Have no idea haven't even tried. Didn't know where to get started since I haven't seen anyone say anything about rooting with the January patch.

Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.

The update is good, I see no new features but I noticed big improvements in performances and RAM management

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Just have to put twrp on and flash through that all good and tested even with swift installer for themes

TonikJDK said:
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
Click to expand...
Click to collapse
OK, yes, Magisk v18 worked fine by flashing it on TWRP

Link to download?
Sent from my Pixel 3 XL using Tapatalk

chakra said:
Link to download?
Click to expand...
Click to collapse
January 2019 Update (for Pixel 3 XL aka "crosshatch"):
Factory Image -- https://dl.google.com/dl/android/aosp/crosshatch-pq1a.190105.004-factory-7165155c.zip
Full OTA Image -- https://dl.google.com/dl/android/aosp/crosshatch-ota-pq1a.190105.004-5f23d043.zip

Can you flash via TWRP?

virtyx said:
Can you flash via TWRP?
Click to expand...
Click to collapse
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.

Just came across this bit of vague information but thought some might be interested. Apologies if it's old info, but seems to indicate the upcoming Feb 2019 update.
Feb 19 Various bug fixes as well as support for Optus VoWIFI + EVS codec activation.
Security updates for Android 9.0
Status: Complete
Click to expand...
Click to collapse
https://yescrowd.optus.com.au/t5/Blog/Android-Software-Updates-07-01-2019/ba-p/522497

sliding_billy said:
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Click to expand...
Click to collapse
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1

Shaftamle said:
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Click to expand...
Click to collapse
It does. Effectively, it does the same thing as the factory image without the -w. It just loads les files. I have been doing the factory image way for years on the OG Pixel XL and now the 3XL. I have done a sideload once just to see the process as well as an OG TWRP sideload once (when it was working) for the same reason. The factory method is the easiest and most reliable IMO. You just need to remember to remove the -w, LOL.

anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp

DrUnkeN_TiGeR said:
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
Click to expand...
Click to collapse
Could be a few things. Make sure you have the current fastboot/adb files, flash boot.img to both slots, make sure you have the most recent TWRP and stable Magisk files, verify all of your downloads and start over.

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