Database Info

Correct versions of TWRP and Magisk

Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much

I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.

You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp

Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse

maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.

TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you

maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:

Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.

I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom

Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT

maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck

fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?

maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck

fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal

Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.

bad post

Magisk Root without TWRP for OnePlus 6 Oxygen OS Android 10 Open Beta 5 | OOS 10.3.1

Latest TWRP doesn't support Android Pie 9.0 for OnePlus 6, or at least for me it didn't.
So, I've made a Magisk patched boot image for Android P that we can flash it in fastboot bootloader.
Note: This is not Oxygen OS ROM, this is just a patched boot img for Oxygen OS to make root work. You need to unlock the bootloader before proceeding with anything.
Note 2: Please disable Magisk modules in the Magisk Manager before flashing the patched boot, because some modules might not support the latest OOS and your device will bootloop. If the modules has been updated by the devs to support the latest OOS you can install the modules after that.
Note 3: Sorry guys, I haven't tested the Android Q Developer Previews. Even though Magisk is supported on Q, please flash it at your own risk.
For older versions download from here: Google Drive
Folder updated with Stock boot images as well.
OOS 10 Open Beta 5 Patched Boot
OOS 10 Open Beta 5 Stock Boot
OOS 10.3.1 Patched Boot
OOS 10.3.1 Stock Boot
Flashing instructions:
Code:
fastboot boot (patched_boot_filename_here).img
or
fastboot flash boot (patched_boot_filename_here).img
Thanks @vlaf
reboot to system (if you make another reboot the root won't stick, so continue with the following steps)
Open Magisk (in settings select beta channel) and click install and install Magisk again with Direct Install (recommended)
reboot again and the root will stick even after the reboot.
The thread I followed for the instructions is here. Thanks for @b1czu
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Even easier way to root without TWRP:
1. Install OTA update (Don't reboot).
2. Open Magisk Manager, install Magisk and choose "Install to Inactive Slot (After OTA)" (Now reboot).
3. Now you are rooted without TWRP and without any boot img hassles as well.

wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！

Not work here. Bootloop, only see Bootanimation not more.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
If you are I can give you the stock boot image for reverting it.

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
Yes lol.

It works for me. That's a great help. Thank you.

SpectraFun said:
Yes lol.
Click to expand...
Click to collapse
I've updated the Google drive folder with the stock boot image for DP3.
Download and flash it to revert the bootloop.
I'm not really sure why it didn't work for you. Sorry about that.

Raymond.William said:
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Click to expand...
Click to collapse
Yeah TiBu is the main reason for me as well.

Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.

geoff5093 said:
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
Click to expand...
Click to collapse
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.

Yeah I did, but I rebooted an additional time and everything works now!
ManikandanGuru said:
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.

geoff5093 said:
Yeah I did, but I rebooted an additional time and everything works now!
Click to expand...
Click to collapse
That's great.

What about safety net?

G0dofWar said:
What about safety net?
Click to expand...
Click to collapse
The first one, ctsProfile, fails. But the second one basicintegrity passes. I believe the only app I use that checks safetynet is PokemonGo and that works for me.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first

toastyp said:
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
Click to expand...
Click to collapse
Lol sure is unlock.

MrSteelX said:
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
Click to expand...
Click to collapse
Yes. This worked. A simple workaround to get twrp working with encrypted Android P

Download link updated with Beta 1 patched image.

[OOS 5.1.11] Pre-Rooted Bootimage

Hi there,
OnePlus is rolling out the OxygenOS 5.1.11 update! According to this thread, I made a pre-rooted bootimage for you to flash
I used the guide on the mentioned thread and used Magisk Manager 5.8.3 (129) with Magisk 16.7
For those who'd rather like to do it on their own, I'll also attach the original bootimage of OOS 5.1.11.
Downloads:
- patched bootimage [MD5: 5EC7C328AEE0D38B43A2727BCD767378]
- original bootimage (5.1.11) [MD5: B6790A9D38F41E0EBC6830D1076FAFF0]
Video instructions:
The awesome @GizmoFreak made a nice step-by-step video for you! :good:
Special thanks for his guide at @b1czu, [MENTION=4470081 ]TopJohnWu[/MENTION] and @GizmoFreak! Please also give him a "thanks" :good:
UPDATE: Magisk 17.1 was released by @topjohnwu ! Many fixes and most important: "Install to inactive Slot (After OTA)" is back! Upgrading our ROM should now be much easier again since already rooted users don't need to use the whole fastboot thing again. However, for new 'unrooted' users, I'll still provide here the always latest patched bootimages.
Cheers,
T.Bear

thanks do we still need to do the direct install from magisk manager?

czerdrill said:
thanks do we still need to do the direct install from magisk manager?
Click to expand...
Click to collapse
Yes, if you whish to keep root. Otherwise your device would take the stock bootimage for the next boot again. This patched one is only for booting with 'temp' root privileges so that you can use magisk Manager to direct install the root stuff to the original bootimage.

does this pass the safety checks?

It's the same procedure as in the thread I mentioned! This is not a standalone 'project', just the missing bootimage for the latest OxygenOS update.
But to answer your question, yes if you follow the instructions on the mentioned thread it passes all checks.
Only if you install things like Xposed framework it won't pass.

RiTCHiE007 said:
does this pass the safety checks?
Click to expand...
Click to collapse
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
fastboot boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
EDIT 1: Added 3rd command which I used but forgot to mention it here ?. Thanks GizmoFreak !

amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
SafetyNet will show the response is invalid because Google recently updated the SafetyNet API. Now developers need to use an API key to access SafetyNet. We need to wait for Magisk to be updated.
---------- Post added at 11:03 PM ---------- Previous post was at 10:56 PM ----------
amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
And the second command should be fastboot boot boot.img

Plz make for H2OS OB 1

Thanks

Do I need to install 5.1.11 first?

williamcll said:
Do I need to install 5.1.11 first?
Click to expand...
Click to collapse
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Created a video. I hope it will make things easy for others.

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Will I lose my data in the process?

no, all are retained

GizmoFreak said:
Created a video. I hope it will make things easy for others.
Click to expand...
Click to collapse
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Click to expand...
Click to collapse
Yes feel free to add it to OP.

ed-gonzo said:
no, all are retained
Click to expand...
Click to collapse
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)

Brother, your download link is not working?

williamcll said:
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)
Click to expand...
Click to collapse
Magisk 16.7 is up to date

What's the benefit of keeping stock recovery and not rooting via twrp?

[Guide] Update and Retain Root

*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse

If you do it this way you'll be using the patched boot image from the previous update and not the current one.

airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.

For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.

pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.

So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!

DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

This work for the Verizon Pixel 4 XL???

SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.

Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.

Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?

Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img

When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it

Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.

mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC

eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol

[Solved] Can't update

Hi,
I recently installed kosp on my device and rooted my device. I tried to install twrp (without any success), but after multiple tries, it seems I broke something.
I can't update anything, it seems the a partition of my device is broken :
if I try to install the update, my phone boots on the a partition and jumps immediately to the bootloader (no recovery nor system).
I tried to hard brick retore my phone twice with no luck yet.
If you have any idea on how to fix this issue, it would be much appreciated.
If not, I'll try to hardbrick restore this device once more....
Thanks !

Please read the thread before posting:
Upgrading:
It is recommended to update using updater
Via recovery:
Reboot to recovery
Sideload with ADB (preferred)
Reboot to recovery
Reboot
Via updater app:
Open Settings -> System -> KOSP Updater
Download the ota if available or if you have already downloaded the zip then use it for local upgrade
Install the update
Flash magisk to inactive slot (optional)
(optional) Reboot to recovery if you have anything else to flash
Reboot

Just use MSMTool and do a clean/fresh install.
After that. Read the OP in KOSP thread how to update. And i think u cant use TWRP with KOSP.

spinoza23 said:
Please read the thread before posting:
Upgrading:
It is recommended to update using updater
Via recovery:
Reboot to recovery
Sideload with ADB (preferred)
Reboot to recovery
Reboot
Via updater app:
Open Settings -> System -> KOSP Updater
Download the ota if available or if you have already downloaded the zip then use it for local upgrade
Install the update
Flash magisk to inactive slot (optional)
(optional) Reboot to recovery if you have anything else to flash
Reboot
Click to expand...
Click to collapse
Thanks, tried that already, sorry if I wasn't clear, but that's not working.

Dan3ll1 said:
Just use MSMTool and do a clean/fresh install.
After that. Read the OP in KOSP thread how to update. And i think u cant use TWRP with KOSP.
Click to expand...
Click to collapse
That's what I'm trying to avoid if possible...

But why? This will take you 30-60 min and u have a fresh 7 Pro with KOSP on it.

Dan3ll1 said:
But why? This will take you 30-60 min and u have a fresh 7 Pro with KOSP on it.
Click to expand...
Click to collapse
Ok, so I ended up doing that, but I'm still facing the same issue : when the device tries to boot on the a partition, I'm just immediately sent to the bootloader and have to run "fastboot --set-active=b" to reboot into my system...

KK...Don´t know were the error is. I did install KOSP and ArrowOS both 2 times to test wich rom is the best for me.
I did not having any issue with the install on both of them.
But as spinoza23 said.
Do it like the OP post and you should not have any issue.
Maybe make a post in KOSP thread if u think it is a general Rom issue.
​

Have you tried flashing the recovery to both slots in fastboot screen? In your case, fastboot flash boot boot.img --slot all
Ensure you're using the kosp recovery boot.img. After that, cycle the volume key to recovery then factory reset. Then adb sideload the kosp zip
I use this method all the time and avoid using twrp. Then since you already did the effort of getting the boot img, just patch it. If you really want to use twrp, just use the fbev2 version to flash things like magisk or kernels. Just boot the twrp.img though not flash. I hope this helps. Currently on derp12. I was daily driving kosp12 for a while with the patched boot and using gpay with no issues.

If you can boot to bootloader than you should be fine. A reliable way of installing roms is using the payload dumper and flashing boot.img, dtbo.img, odm.img, system.img, vbmeta.img, and vendor.img.

Thanks, I tried what you propose, unfortunately, still the same result : can't boot to a partition, which means no update possible...

lost boy said:
Thanks, I tried what you propose, unfortunately, still the same result : can't boot to a partition, which means no update possible...
Click to expand...
Click to collapse
maybe use the msm tool take it down to 9 and ota back up to 11 if you havent tried already, just a thought

Solved :
What I had to do :
use msmtool to go back to android 9
update to android 10's latest official build through the updater
update to android 11's latest beta build using oxygenos updater
update to kosp 2.2 using the provided fastboot sequence
update to kosp 2.3 using kosp updater
Took me the afternoon but seems to be working fine now !
My guess is, the device was not ready for a jump from android 9/10 to 12 directly or something...
Thanks for the help

So yeah you actually never said that u are on A9 or A10 release. I mean it is in the KOSP thread that you need 11.0.4 or the lastest A11.
Do you know that there are "newer" MSMTool builds than A9? Makes things easy.