Database Info

Is it safe to update to 5.1.11 on a rooted devices now or should I wait later?

It took me 3 nights just to get magisk and exposed running properly on 5.1.9, should I update to 5.1.11 now? Are all the rooting programs like Xposed, TWRP and magisk patched for 5.1.11? If so do I need to go all the way from the start and flash TWRP again after the update?

williamcll said:
It took me 3 nights just to get magisk and exposed running properly on 5.1.9, should I update to 5.1.11 now? Are all the rooting programs like Xposed, TWRP and magisk patched for 5.1.11? If so do I need to go all the way from the start and flash TWRP again after the update?
Click to expand...
Click to collapse
Yes but you need to just repeat your action is easily take 5 minutes [emoji846]

Flash the full ROM zip in TWRP, flash TWRP installer zip to patch the boot image again, reboot recovery to make it switch to the now active slot, flash magisk, reboot to system and you're done.

When applying the patch in form of the Full-OTA properly, this is a matter of less than a few minutes. I am curious - how did you manage to waste three nights for this?

Be aware that the simple path forward ( 09 to 11 ) works. It did for me. I am simple. But many, many people found the path back ( 11 to 09 ) was broken by oneplus . A lot of these people are vested in custom rom solutions.
.
Here is a quote from Joe Moss, Jr.
IT HAS COME TO MY ATTENTION THAT PEOPLE ARE HAVING ISSUES WITH THERE DATA PARTITION BEING ENCRYPTED. THIS IS BECAUSE IF YOU FLASH A NEWER ROM WITH A SECURITY PATCH LEVEL OF AUGUST AND TRY TO GO BACK TO OOS WHICH IS JULY TWRP WILL NOT BEING TO DECRYPT THAT. BECAUSE YOUR DATA IS NOW AUGUST PATCHED WHILST YOUR SYSTEM READS JULY .AS OF NOW I DON'T HAVE A PC TO FULLY TEST AND FIX THIS ISSUE. ONLY WAY TO FIX IS BY FORMATTING DATA.

Safe with masgisk but no root after that
With magisk is safe no bug

Worked here 1st try no issues and I have a tendency to mess stuff up. I did TWRP, full .11 release, TWRP, latest magisk, blu kernel(all from TWRP). Safetynet apps like my bank and googlepay work.
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
old_fart said:
Be aware that the simple path forward ( 09 to 11 ) works. It did for me. I am simple. But many, many people found the path back ( 11 to 09 ) was broken by oneplus . A lot of these people are vested in custom rom solutions.
.
Here is a quote from Joe Moss, Jr.
IT HAS COME TO MY ATTENTION THAT PEOPLE ARE HAVING ISSUES WITH THERE DATA PARTITION BEING ENCRYPTED. THIS IS BECAUSE IF YOU FLASH A NEWER ROM WITH A SECURITY PATCH LEVEL OF AUGUST AND TRY TO GO BACK TO OOS WHICH IS JULY TWRP WILL NOT BEING TO DECRYPT THAT. BECAUSE YOUR DATA IS NOW AUGUST PATCHED WHILST YOUR SYSTEM READS JULY .AS OF NOW I DON'T HAVE A PC TO FULLY TEST AND FIX THIS ISSUE. ONLY WAY TO FIX IS BY FORMATTING DATA.
Click to expand...
Click to collapse
It's my understanding that the dated security patches come from Google not OnePlus. Is this no longer correct?

cciechad said:
Worked here 1st try no issues and I have a tendency to mess stuff up. I did TWRP, full .11 release, TWRP, latest magisk, blu kernel(all from TWRP). Safetynet apps like my bank and googlepay work.
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
It's my understanding that the dated security patches come from Google not OnePlus. Is this no longer correct?
Click to expand...
Click to collapse
Yes, I believe you are the correct one sir.
Point. If oneplus had given us all the latest patch ( August ) instead of last month's . . . Come on onplus. . . . How hard would have that been ?

old_fart said:
Yes, I believe you are the correct one sir.
Point. If oneplus had given us all the latest patch ( August ) instead of last month's . . . Come on onplus. . . . How hard would have that been ?
Click to expand...
Click to collapse
Yeah or atleast the 7/5 patch. I don't get how they couldn't have pulled that in. There were a lot of QCOM bug patches in there.

black_file said:
Yes but you need to just repeat your action is easily take 5 minutes [emoji846]
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)

Hi guys. Help me plz. I have rooted OnePlus 6. After yesterday update I lost root. I've reboot my phone and flashed TWRP and Magisk. But forgot about boot.img
Now a don't know what to do. Now I can't open fastboot mode and phone can't load (stuck in the clock red and white circles).
Help me please

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.

Android 10 factory and magisk patched boot images

Link contains factory boot, and patched images, bootloader and radio from stated release
August 2020 (canary): https://drive.google.com/drive/folders/1SpBngNA35CnCCF57jK8wjhRUQEeyyCHG?usp=sharing
Tulsadiver module disabler: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867 (i think magisk canary disables modules if you boot into safe mode https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24 )
Way to update without flashing: https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md
here is a guide for getting root: https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
platform tools were updated in july 2020: https://developer.android.com/studio/releases/platform-tools
and a guide for google pay with root: https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248
Hide Google pay, Google play services, Google services framework, clear Google pay data after update and apply module.
old factory and patched images:
July 2020 (canary patch): https://drive.google.com/folderview?id=16-XxwJbT5VIIT1cbDTXIffdOuqwx3XCH
Feb 2020 (beta patch): https://drive.google.com/open?id=1WZ2-tza0IB3oICGFCHuj1GJKJr0nd8a3
Jan 2020 (canary patch): https://drive.google.com/open?id=1_zNt1i2uqbGhfEiWn0O716v9noJdR4uJ
Dec 2019(canary patch): https://drive.google.com/open?id=1JHc86ZOHkyNA0uJ6r43eLqG4oe6KBfGy
nov 2019(canary patch): https://drive.google.com/open?id=14GA7qrPITZ_-jYNDAFuC0bJiaKwGmqRP
oct 2019(canary patch) : https://drive.google.com/folderview?id=16bbXgyWwi8TmJNaih_UvdtXxB8fC5W0t
note: i think you can go into recovery mode to disable modules with canary magisk if you have trouble.

updated OP with nov images
one report of nov 2019 update breaking google pay

The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?

if you can push the magisk uninstall zip to your device, then fastboot booting into twrp then flashing the magisk uninstall zip that should do the trick.

swieder711 said:
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
Click to expand...
Click to collapse
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.

jd1639 said:
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
Click to expand...
Click to collapse
Thanks for the pointer. I wasn't sure if that Disabler would work with the November image.
I ended up reflashing the factory default and than reapplying the correct files. I now have GravityBox running on the Nov Image!

Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯

ffchampmt said:
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
Click to expand...
Click to collapse
OP updated to show 19.5.

Had the same issue and ran into the problem getting the modules disabled. Glad you were able to get it up and running.
Sent from my Pixel 3 XL using Tapatalk

i think doing a full uninstall of magisk (removes modules and settings) might be best until twrp or something else comes along...

Thanks for the patched image @dipstik. Gonna wait for Dec's iteration

chinesecooler said:
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
Click to expand...
Click to collapse
wait no more!

Woop woop, time for my bi-annually update

dipstik said:
wait no more!
Click to expand...
Click to collapse
Which version of Magisk did you use to patch the boot image? I tried using stable and canary to patch the stock boot image when I updated earlier, but each time it would just reboot straight to bootloader.

i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605

dipstik said:
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
Click to expand...
Click to collapse
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...

Face_Plant said:
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Click to expand...
Click to collapse
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.

Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.

comady25 said:
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
Click to expand...
Click to collapse
It is working for many and not for others. My wife's P3 rooted fine with canary.

jlokos said:
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Click to expand...
Click to collapse
I used this method and it worked with no issues. It was only the second time i used this method but with others having issues with the factory image and patched boot image i thought I'd give it a try.

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

Accidentally OTA updated my pixel, all fine but root gone

So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!

ViruuZ said:
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
Click to expand...
Click to collapse
You need to patch the new boot.img.

sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
Thanks for reply! So i extract my current boot.img, but how to patch it?

ViruuZ said:
Thanks for reply! So i extract my current boot.img, but how to patch it?
Click to expand...
Click to collapse
Open Magisk manager app
Select install magisk
Select and Patch a File
Copy new patched boot.img to pc
Flash

well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?

ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Found my current firmware, will extract it there. Thanks anyway!

ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Normally you have to go to google firmware page and download it.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

Are you guys having the SafetyNet passed?

sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
No you don't. You only have to repatch the new boot image when a new major Android revision comes out. For example going from Android 11 to 12. I've updated my Pixel 5 every month a new update comes out. And I've always used the same boot.image file. No need to keep wasting your time patching that file. When you look through the OTA files you'll notice that none of those files in the zip file are a boot.image file. Meaning it doesn't touch it when it's doing the OTA.

xT29c said:
You only have to repatch the new boot image when a new major Android revision comes out.
Click to expand...
Click to collapse
That is kind of useful, thank you for sharing. Can someone confirm this?

@hanni2301 Have you succeeded in getting root back ? I got the same problem today....

Why do you ask me?
I always patch the actual boot.img out of the monthly factory image with magisk (beta or Canary) first and flash then the factory image, reboot, flash boot boot.img and afterwards the custom kernel.
@xT29c said that you can reuse ure patched boot.img from last month, as it changes only between different mayor Versions.
So you can save some time, but the process is still the same.

IMO, yes, you should always patch the new boot.img from each months new factory image in Magisk when re-rooting.
Do you need to? i suppose that's up to you. However I think you should want to.
Essentially, you're missing out on any code changes/fixes, etc that Google may have added to the new months kernel.
~ Maybe an idea for a new thread to upload the Pixel 5 stock boot.img from each months new OTA, along with a Magisk patched boot.img. ~

Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.

leveleyed said:
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
Click to expand...
Click to collapse
I am not sure, but this may be because Magisk Manager is no longer..
get v22
New v22.0 update merges Magisk and Magisk Manager app
Samsung's Galaxy S21 series is now supported too
www.androidpolice.com