Database Users

September Update is up now

Take a look here: https://developers.google.com/android/images
Download it now!!

Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)

ApoelEllhnwn said:
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
Click to expand...
Click to collapse
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.

wish someone would make the factory images Flashable. All this needing a computer to update is getting old!

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I'm sorry I must not have been very clear. My ask was for someone to try the process detailed in the link I provided in my quote above. This is supposed to allow you to uninstall Magisk (don't reboot), take the OTA as you normally would on unrooted phone, and once it installs, apply Magisk to the new slot w/ the OTA installed, then reboot. No computer needed. As I stated above, I would do it, but have yet to get the update thru the Check System Update. I am well aware of how to install it manually, as I have done that process for every update. I just saw that the linked process was updated for Magisk 17.0+ and hoped it could be verified to work. Meaning this would simplify the monthly update process tremendously.

kolothuk said:
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
Click to expand...
Click to collapse
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.

kittygotwet said:
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
Click to expand...
Click to collapse
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.

davidisflash said:
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
Click to expand...
Click to collapse
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.

kittygotwet said:
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
Click to expand...
Click to collapse
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.

davidisflash said:
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
Click to expand...
Click to collapse
I actually figured it out. I had to use the Magisk uninstaller to remove any remaining Magisk, I guess, before I can reinstall. Now I just have another issue on the Pixel 2 9.0. Converting any user app to system app corrupts the phone.

Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I will try this guide as soon as the OTA is available.

I got another update today on my Pixel 2, which said: critical bug and performance fixes... I wonder what it is? The phone isn't as smooth after this and some glitches with youtube in landscape, there white nav bar appears, but I can't click 3 dots menu to adjust quality for example. I have to turn the phone in portrait and then do it.

razorsbk said:
I will try this guide as soon as the OTA is available.
Click to expand...
Click to collapse
I'm also still waiting for the Update ...is that normal to wait that long time?

No, it's not. Other manufacturers have released their patches via OTA.
Sent from my Pixel 2 using Tapatalk

So you think we have to sideload the patch?

How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?

Ashyford said:
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Click to expand...
Click to collapse
You can't. Google is no longer releasing OTAs for 8.1. Your best bet is to use a custom kernel such as FlashKernel, as I believe it is backwards compatible, and Nathan streamlines the security patches from both Google and the Linux kernel fork into his kernel.

Did anyone else got the OTA ? I'm still wainting

P2XL OTA + Magisk install before reboot = keep root

Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.

Did you do this from Pie or from Android Q beta? Also, did you uninstall Magisk from the manager before you did the OTA?

Anybody know if this worked smoothly with their Viper4Android app?

This worked form me going from Android 9 with Magisk to Android 10

I'm glad I waited and saw this before moving to Android 10. This worked like a charm for me as well.

gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and installed it.
---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.

Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is

kmry said:
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Click to expand...
Click to collapse
Is your recovery stock? It may not be clearly stated as I haven't read the thread in its entirety, but the OTA will fail with TWRP installed. It likely will also fail if the system partition is modified.
EDIT: I re-read your post. You clearly note using TWRP.

Nightf0x_007 said:
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
Click to expand...
Click to collapse
How do you flash it, with flash fire, trough TWRP or from fastboot?

kmry said:
How do you flash it, with flash fire, trough TWRP or from fastboot?
Click to expand...
Click to collapse
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk

Anyone know how to get the native led configuration without using a custom rom or the lightflow app?

Should I update Magisk and manager before I do this?
My Magisk installed is 18.1 and it lists 20.1 as available
Magisk Manager installed is 7.0 and 7.4 is listed as available

If you wanna follow the official instructions :
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Nightf0x_007 said:
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Click to expand...
Click to collapse
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.

kmry said:
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
Click to expand...
Click to collapse
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w

Nightf0x_007 said:
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Click to expand...
Click to collapse
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?

kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
Just the flash-all.bat if your using Windows. :good:

kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
.bat file only

How to update to the latest version?

Ok so i'm running now OOS Stable 10.0 with TWRP running, and Magisk ofc.
Now, i used this guide -
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-twrp-data-decryption-t3995861
To update from 9.0.17 to 10.0
But never tried to update from 10.0.
Can i update like the usual process ?
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Or i need to do it differently .
Edit : I want to update from 10.0 to OB3.

yot2703 said:
Ok so i'm running now OOS Stable 10.0 with TWRP running, and Magisk ofc.
Now, i used this guide -
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-twrp-data-decryption-t3995861
To update from 9.0.17 to 10.0
But never tried to update from 10.0.
Can i update like the usual process ?
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Or i need to do it differently .
Edit : I want to update from 10.0 to OB3.
Click to expand...
Click to collapse
Why would it be different?
It seems complicated enough for people to catch up with only one logical method, I dare not imagine what it would be if there were different procedures....

yot2703 said:
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Click to expand...
Click to collapse
If you do it this way make sure you update to the latest version of TWRP that was released today (3.3.1-30) before upgrading the ROM.

Open magisk manager and restore boot.img.
Update locally in system settings.
Dont reboot.
Install magisk to inactive slot in magisk manager.
Reboot and provit.
No need for twrp.

Striatum_bdr said:
Why would it be different?
It seems complicated enough for people to catch up with only one logical method, I dare not imagine what it would be if there were different procedures....
Click to expand...
Click to collapse
There are people updating with local update.
alryder said:
If you do it this way make sure you update to the latest version of TWRP that was released today (3.3.1-30) before upgrading the ROM.
Click to expand...
Click to collapse
Update it via Magisk?
bokkoman said:
Open magisk manager and restore boot.img.
Update locally in system settings.
Dont reboot.
Install magisk to inactive slot in magisk manager.
Reboot and provit.
No need for twrp.
Click to expand...
Click to collapse
I still want TWRP , Flash it over Magisk?
And can you provide me the boot.img? 10.0

yot2703 said:
There are people updating with local update.
Update it via Magisk?
I still want TWRP , Flash it over Magisk?
And can you provide me the boot.img? 10.0
Click to expand...
Click to collapse
And why would you need TWRP?
You don't need boot.img. Magisk automatically backups the original boot.img and patches it. That way you can restore it thru magisk manager. And patch the new boot.img (install to in-active slot) after local upgrade.

bokkoman said:
And why would you need TWRP?
You don't need boot.img. Magisk automatically backups the original boot.img and patches it. That way you can restore it thru magisk manager. And patch the new boot.img (install to in-active slot) after local upgrade.
Click to expand...
Click to collapse
I'm trying this guide
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-update-to-op6t-ob3-q-t4021299

yot2703 said:
I'm trying this guide
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-update-to-op6t-ob3-q-t4021299
Click to expand...
Click to collapse
Well, that doesn't answer the question: why do you need TWRP?

The problem is that you ask for a recipe, without knowing clearly what you're doing when applying the recipe.
Yes you can update with local update while keeping Magisk and twrp. See first posts of OOS 10.0.1 thread in Guide section.
Yes you can update from within twrp, the way ROMs are fleshed since nearly a decade
Yes you can flash twrp with Magisk manager, since months it's a basic knowledge.
No you don't need stock boot.img
Don't follow the guide you quote WHICH WAS WRITTEN WHEN NO WORKING TWRP was available for A10. It's outdated now. Use regular and classical procedures

bokkoman said:
Well, that doesn't answer the question: why do you need TWRP?
Click to expand...
Click to collapse
Flash other zips and kernels?

yot2703 said:
Flash other zips and kernels?
Click to expand...
Click to collapse
Alright, well then it is useful.
IMHO, i recommend using stock OOS and root only. Because it already is a great rom. You can flash certain extras with magisk manager anyway.
But whatever rows your boat

Striatum_bdr said:
The problem is that you ask for a recipe, without knowing clearly what you're doing when applying the recipe.
Yes you can update with local update while keeping Magisk and twrp. See first posts of OOS 10.0.1 thread in Guide section.
Yes you can update from within twrp, the way ROMs are fleshed since nearly a decade
Yes you can flash twrp with Magisk manager, since months it's a basic knowledge.
No you don't need stock boot.img
Don't follow the guide you quote WHICH WAS WRITTEN WHEN NO WORKING TWRP was available for A10. It's outdated now. Use regular and classical procedures
Click to expand...
Click to collapse
Well now i'm stuck with no twrp. how to flash it ?

yot2703 said:
Well now i'm stuck with no twrp. how to flash it ?
Click to expand...
Click to collapse
The answer is in the post you quoted:
'Yes you can flash twrp with Magisk manager, since months it's a basic knowledge"
What I did was open Magisk Manager - go to Modules - click Add (+) - select the TWRP installer (zip) - exit Magisk Manager - reboot to TWRP - reinstall Magisk.
There might be a way to reinstall Magisk from Magisk Manager to the active slot but I'm not sure so I did it through TWRP.

Android 11 is live.

Today just received update notification as below image. Downloading now, let see what are changes and improvements.

I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?

TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.

tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.

Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.

socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary

Anyone have the screen record enabled in power menu and how ?

khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop

monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.

V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?

monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.

V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?

SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.

Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )

hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?

V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions

I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.

Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.

V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.

Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.

oneplus 6t stuck when i try to flash twrp after msm

so, i had my op 6t bricked and in a bootloop to fastboot
i managed to recover my data through twrp, but couldnt get lineage to run again, so i used the msm tool to downgrade to android 9 oos
now when i try to install a custom recovery i the phone freezes in this "the bootloader is unlocked warning"-screen
no idea why i cant boot into a custom recovery, with a unlocked oem
my plan is to get it back to run lineage os with twrp recovery
can u maybe help me?

I wasn't able to boot into twrp since a11. Had to install from magisk in booted oos using twrp installer. Not sure why it wouldn't work if you downgraded but maybe not using the correct twrp? Sounds like things are messed up. I would start from scratch and get a clean oos on both slots. If you can't boot into twrp then root with magisk and install directly from magisk manager with the installer.

So I am on 11.1.2.2, how do I get twrp installed on this. I cannot get twrp to boot past the logo. I have been trying to Flash HAVOC but have been stuck

Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.

Brettroth said:
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Click to expand...
Click to collapse
Which magisk? latest or canary

Gytole said:
Which magisk? latest or canary
Click to expand...
Click to collapse
I use the latest

and are we talking 3.6.0_9? orr...

Gytole said:
and are we talking 3.6.0_9? orr...
Click to expand...
Click to collapse
Yeah that's the newest. Older ones work but that one has a lot of good changes

Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.

Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
You need to flash a magisk modded boot in fastboot from your oos. Someone has a post somewhere in here hosting them I'll try to get a link for you.

so fastboot flash boot_a and b like usual for the patched boot image and then once in android just open magisk, then install the latest twrp from there? I think that's what put me in crash dump mode before

Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
Are you on 11.2.1.1?

Brettroth said:
Are you on 11.2.1.1?
Click to expand...
Click to collapse
11.1.2.2 I believe?

Gytole said:
11.1.2.2 I believe?
Click to expand...
Click to collapse
Sorry that's what I meant. Here is modded boot. Flash in fastboot.

Brettroth said:
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Click to expand...
Click to collapse
Done. Now I boot into android, open magisk, and install the recovery?

Gytole said:
Done. Now I boot into android, open magisk, and install the recovery?
Click to expand...
Click to collapse
Yessir

Brettroth said:
Yessir
Click to expand...
Click to collapse
Work out for ya?

Wow. Alright. You all need to remember this. Msm only flashes to slot a. NOT slot b. So, if you were previously in A10 or A11 and flash msm OOS 9, there will be issues unless you local update the same android version to slot b. You can't have 2 different android version on your slots unless you're using dualboot mod. Like on 8 pro, crashdump happens when twrp is installed if both slots aren't using the same android version