Database Info

[XPOSED] Installation guide

This is tutorial how to install XPOSED on POCO F1 MIUI global 10 and 11
This is a guide for experienced users ONLY!.
These are the steps for a phone that has already been rooted .
This is new full working Xposed method tested by me.
Download all files from the attachment and copy it to your phone.
Delete all previous old xposed modules
1. Open Magisk application on your phone
2. Go to Modules, and press +
3. Install first magisk-riru-core v18, after installation of the module press close. Then press + again and install magisk-EdXposed-SandHook-v0.4.1.2_beta-release, press close again and reboot your phone.
4. Install EdXposedInstaller_v2.2.4-release normally AND DON'T UPDATE IT. You can update modules but not installer..
5. You can do update via Magisk Manager.
Open Xposed app, and you should see this on your screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another must have tool is Magisk Manager for Recovery made by VR25.
How to use MM (magisk manager) for recovery in TWRP.
1. Download file form provided link and put it on your phone memory.
2. Enter to recovery mode , go to Install and flash the file mm20190404.zip and do not reboot, just go back to main menu.
3. Go to Advanced, then open terminal
4. Write mm and pres enter
5. Pres l to get list of installed modules
6. You can disable or remove modules form here.
You must repeat all these steps every time you want to start MM
It will look like this:
If someone have trouble with SafetyNet check, just add Google play services to Black list in EdXposed.
1. Enable Black/White list in EdXp Settings
2. Add Google services to black list
3. You will pass SafeyNet Check
You can update to MIUI Global 11.0.5. Everything works fine. Just follow my update steps.
1. Open Magisk
2.Go to uninstall than choose RESTORE IMAGES
3. Reboot phone
4. Go to settings/about phone/system update
5. Download update and install it.
6. After update, go to fastboot, pwr+volume down
7. Connect your phone to PC, open cmd or power shell with admin privileges and go to platform tools folder , then type like first time fastboot flash recovery twrp-3.2.3.0-beryllium.img, then fastboot boot twrp-3.2.3.0-beryllium.img ( change the name of image file if it is different on you PC)
8. Flash Magisk again
9. Reboot
10. All should be like before update

Wrong place to post. You should move to the themes and mods section. But GJ.

Thread updated.
Sent from my POCO F1 using Tapatalk

Will this pass safetynet in magisk?

what xposed-mods do you use?

ctsuresh said:
Will this pass safetynet in magisk?
Click to expand...
Click to collapse
Edit: Safetynet is passing, so there is no issue using this xposed.

MechaNarutoSucks said:
Wrong place to post. You should move to the themes and mods section. But GJ.
Click to expand...
Click to collapse
It's a guide. Technically, it is a mod but the post shows guide and installation.

ctsuresh said:
Edit: Safetynet is passing, so there is no issue using this xposed.
Click to expand...
Click to collapse
OMG! Xposed + Safetynet? I'll try today
I'm really excited

if i use it on lineage do i need to turn off modules before OTA update to prevent bootloop or its fine ?

In order to apply OTAs, you have to open Magisk Manager go to Uninstall \Restore Images. Don't reboot or you will have Magisk uninstalled. This will restore your boot and back to 100% untouched stock images in order to pass pre-OTA block verifications.

Cara... Você salvou a minha vida... Obrigado !!
You is the best....

Working like a charm on Poco F1 running stable 10.3.4.0. Thanks!
Edit: sometimes when I turn on the phone, it go into bootloop. I need to restart manually one or more times to start correctly. I have updated to riru core and edxposed lastest versions.
Edit 2: looks like to be related to minminGuard module. After uninstall it, everything is working as expected.

Yes.You must be careful when you choose a modul. You have update for minminguard.
Sent from my POCO F1 using Tapatalk

bixirulo said:
Working like a charm on Poco F1 running stable 10.3.4.0. Thanks!
Edit: sometimes when I turn on the phone, it go into bootloop. I need to restart manually one or more times to start correctly. I have updated to riru core and edxposed lastest versions.
Edit 2: looks like to be related to minminGuard module. After uninstall it, everything is working as expected.
Click to expand...
Click to collapse
I tested new 2.0.9 version and everything works good. No bootloop. But i found that minminGuatd is not very effective in removing ads. I recomand that you use lucky patcher instead. Inapp purchase option.
But something is buggy with this modul...avoid it.
Sent from my POCO F1 using Tapatalk

@delevic Have you tried "customiuizer" module? Also stuck at boot screen randomly...

Which edxposed version you use ?
Just tested customiuizer. No bootloops no bugs. Write me all your installed versions from magisk riru edxposed ...
Sent from my POCO F1 using Tapatalk

Thanks for sharing.i am use 9.3.21 eu beta weekly and working well.no bootloop everything is okey now

I am testing now magisk-EdXposed-SandHook-v0.4.2.3_alpha-release.zip So far so good

4. Install EdXposedInstaller_v2.2.4-release normally.
Click to expand...
Click to collapse
what is meant by "normally"?

Just install apk fille like all other app. Find apk fille and press enter
Sent from my POCO F1 using Tapatalk

OTA update & Magisk : Bootloop. Please help!

Hello, this morning I thought I'd try to apply Oneplus OTA update, but while keeping Magisk and its modules installed.
So I googled it and I was candid enough to follow this tutorial.
Here are the exact steps I followed:
Apply the Oneplus OTA update (download & install) BUT did not reboot
Magisk Manager → Uninstall → Restore Images (Maybe that's where I screwed up as I should have run this before above step?)
installed TWRP A/B Retention Script from Magisk Manager (installed module but did not reboot).
Magisk Manager → Install Magisk → Install to Inactive Slot
Pressed the reboot button in Magisk Manager
Now the phone rebooted, oneplus boot logo, then phone unlock screen and automatically "restarted" as shown on this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then it rebooted into TWRP, asking for my password. After I enter the password, TWRP decrypt my partition and then I don't know what to do.
I flashed magisk again, but with no luck.
Thanks a lot in advance for your help and suggestions!
[EDIT] here is what happen when I flash twrp zip installer
Shoud I flash FULL oneplus firmware from this link?

I solved it by flashing oneplus full update image, then directly flashing twrp (from twrp), then flashing magisk, and finally rebooting.

I spoke too fast.
I was able to boot into oneplus system, but Magisk was not there anymore.
So I booted into recovery (twrp), flashed magisk (it said flashing on slot A this time), rebooted: Bam, same bootloop issue than before!!
Is it related to magisk modules that were not disabled? Or what?
Any feedback would be much appreciated! Thanks

Ok, so finally I did identified the root problem : Magisk module incompatibility! The faulty module is LOS Call Recorder, so I had to do this:
Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!

Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.

larsdennert said:
Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.
Click to expand...
Click to collapse
I agree, and to elaborate one step further than this, I had the exact same issue and found that you don't just have to disable the modules, but you have to fully remove them (using the little trash icon in Magisk). I've heard the call recording module causes issues, but from now on I remove all of them to avoid the issue.
The way that I solved it post-bootloop was by booting to TWRP (either your phone retained it or use Fastboot boot with the .img file), and then using the function in TWRP 'Advanced > File Explorer' browsing to access 'Data\adb\modules'. For each offending module, browse into the module folder, then hit the blue folder icon on the bottom right to select and delete the entire folder. Be sure to only do this to the specific modules, I don't want you accidentally removing anything core to the OS.
That's the steps that worked for me I hope this helps you!

You actually don't have to trash them but it makes it clearer to most people. The issue is that after the update, Magisk thinks a particular module is installed when it isn't. If you simply disabled it previously, you can boot no problem after the OTA however if you then reenable the module, your next boot will loop because the module isn't there. Confusing so really the best advice is to uninstall modules and reinstall them so that nobody will simply reenable a dead module.

I'm having this exact issue, except I DON'T HAVE ANY MODULESSS
I don't know what to do... I've completely factory reset and it still didn't help

Have you flashed full stock without root?

larsdennert said:
Have you flashed full stock without root?
Click to expand...
Click to collapse
Haha, I actually did and that was the fix... After many Magisk Uninstaller flashes and Magisk installations, I realised the issue was with the OS itself, and flashing the stock image replaced the boot image which was causing the problem (I think... Idk if I'm right about this)

Depending on the phone model you'll need another rooted boot image. If you need a current one for the 1917, I can get you one.

Hi so i'm having this exact problem. Is there any solution that doesn't include a factory reset? Currently I'm stock os android 10 and was running magisk 20.4. had a bootloop uninstalled all modules etc and still bootloop. Only when I uninstall magisk does my phone boot to system. Reflash and we get a bootloop. Does anyone know what could be corrupted etc to stop magisk from rooting my phone? I'm sure a factory wipe will fix this but surely theres a better way.
Again,works perfectly without magisk installed. Then install magisk and we get a bootloop. Please help.

Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.

larsdennert said:
Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.
Click to expand...
Click to collapse
Magisk has been fully removed by flashing the zip file in twrp. Everything is deleted. When I reflash the zip in twrp I get a bootloop. It's the same steps as I originally used to root the phone without issue.

You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?

larsdennert said:
You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?
Click to expand...
Click to collapse
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.

Bxperiaz3 said:
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.
Click to expand...
Click to collapse
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted

Joker123## said:
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted
Click to expand...
Click to collapse
All modules have been removed. I might try flashing the stock boot image and see if that helps. my other plan was to dirty flash the stock rom and the magisk again to see if this repairs the problem.
---------- Post added at 10:49 PM ---------- Previous post was at 10:23 PM ----------
SOLVED!
In case anyone runs into this issue in future. I'm guessing something must have happened to the boot image because I fired up TWRP, cleared Dalvik, flashed the stock os, booted straight back to recovery, flashed TWRP again, then magisk 20.2. Then I switched slots and did the same thing and then rebooted. Now I have everything working again, magisk updated to 20.4 and no data or app loss. Very happy

Oct 1 2019 patch

Just got it this morning on my stock version 9
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Dude+ said:
Just got it this morning on my stock version 9
View attachment 4874129
Click to expand...
Click to collapse
I cant root this version

GabrielBPereira said:
I cant root this version
Click to expand...
Click to collapse
Oooooooof I thought it was only me and I was doing something wrong!!!

Was just about to do it ! Glad I read this....I assume you tried with magisk 20.1 ?

I'm not rooted and haven't tried yet. I'm no help there.

buddy96 said:
Was just about to do it ! Glad I read this....I assume you tried with magisk 20.1 ?
Click to expand...
Click to collapse
I yes, 20.1 dont work... I have bootloop ...

buddy96 said:
Was just about to do it ! Glad I read this....I assume you tried with magisk 20.1 ?
Click to expand...
Click to collapse
You can do it. You just need to root with magisk 19.3 and use the forceencrypt disabler file from 8/8/20 not the recent one and it will work.

Jemec26 said:
You can do it. You just need to root with magisk 19.3 and use the forceencrypt disabler file from 8/8/20 not the recent one and it will work.
Click to expand...
Click to collapse
ok ! do you keep it as 19.3 or do you then update it to 20.1 using magisk manager ?

buddy96 said:
ok ! do you keep it as 19.3 or do you then update it to 20.1 using magisk manager ?
Click to expand...
Click to collapse
Keep it 19.3.

Jemec26 said:
You can do it. You just need to root with magisk 19.3 and use the forceencrypt disabler file from 8/8/20 not the recent one and it will work.
Click to expand...
Click to collapse
Forceencrypt 8/8/20 ? You have link ?
I dont have bootloop ?

GabrielBPereira said:
Forceencrypt 8/8/20 ? You have link ?
I dont have bootloop ?
Click to expand...
Click to collapse
No bootloop. Don't have a link sorry, I got it from the Telegram group

Magisk 20.1 does work. No bootloops. If you are starting fresh, just install TWRP and do the usual 2 full wipes, then flash Magisk 20.1 and boot to system. The Dm-Verity file is no longer needed, as Magisk does it for you. That's where I was having problems rooting it. The Dm-Verity_ForceEncrypt was the cause of the bootloops.
UPDATE : The removal of Forced Encryption is needed. Just Remove the "Dm-Verity" from the zip file name. I'm using the 10.20.2019 version. The filename should be changed to "Disable_ForceEncrypt_10.20.2019.zip". I didn't use the file at all the first time, and recovery was unable to mount data because of it. But the Dm-Verity part of that zip is what was causing all of my bootloops.

Did you have "Preserve avb 2.0/dm-verity" checked in magisk manager before re-flashing ? Default is unchecked, I'm wondering what would trigger encryption to remain disabled during the first reboot.

buddy96 said:
Did you have "Preserve avb 2.0/dm-verity" checked in magisk manager before re-flashing ? Default is unchecked, I'm wondering what would trigger encryption to be remain disabled during the first reboot.
Click to expand...
Click to collapse
I didn't change any of the default Magisk settings. I have no clue why it allowed the 1st reboot to have no encryption, but it was definitely encrypted on the 2nd reboot. Everything was working fine, then I tried to go to recovery again after I had everything setup the way I like it and make a backup, and that's when TWRP was showing the encryption dialog. I had to reset and start over because of that.

Just seen your edit to #12, makes sense now. Encryption occurs during first boot if not disabled.

xfrobex said:
Magisk 20.1 does work. No bootloops. If you are starting fresh, just install TWRP and do the usual 2 full wipes, then flash Magisk 20.1 and boot to system. The Dm-Verity file is no longer needed, as Magisk does it for you. That's where I was having problems rooting it. The Dm-Verity_ForceEncrypt was the cause of the bootloops.
UPDATE : The removal of Forced Encryption is needed. Just Remove the "Dm-Verity" from the zip file name. I'm using the 10.20.2019 version. The filename should be changed to "Disable_ForceEncrypt_10.20.2019.zip". I didn't use the file at all the first time, and recovery was unable to mount data because of it. But the Dm-Verity part of that zip is what was causing all of my bootloops.
Click to expand...
Click to collapse
what would be the correct procedure? twrp, after the two wipe on "data", flash "Disable_ForceEncrypt_10.20.2019.zip", then magisk? without rebooting?

dont start telephone ...

xfrobex said:
Magisk 20.1 does work. No bootloops. If you are starting fresh, just install TWRP and do the usual 2 full wipes, then flash Magisk 20.1 and boot to system. The Dm-Verity file is no longer needed, as Magisk does it for you. That's where I was having problems rooting it. The Dm-Verity_ForceEncrypt was the cause of the bootloops.
UPDATE : The removal of Forced Encryption is needed. Just Remove the "Dm-Verity" from the zip file name. I'm using the 10.20.2019 version. The filename should be changed to "Disable_ForceEncrypt_10.20.2019.zip". I didn't use the file at all the first time, and recovery was unable to mount data because of it. But the Dm-Verity part of that zip is what was causing all of my bootloops.
Click to expand...
Click to collapse
I tried these steps immediately after flashing the oct 1 patch and couldn't get it working. I tried both Magisk 19.3 as the other comment suggested, and the latest 20.1 - both resulted in bootloops. Any idea what might fix this, or some mistake I overlooked?

today launched december patch, brazillian phone

I don't understand why everyone is using this awful Disable_Dm-Verity_ForceEncryption.zip??
As xfrobex already said the disable dm-verity option is no longer needed thanks Magisk. But to disable the encryption of your device you don't need to flash the .zip, too!
Open the fstab.qcom file and edit the mount flags of /userdata like this:
Instead of "forceencryption" => "encryptable"
That's all!
As I red many times in several threads this .zip causes more problems instead of being an advantage...

How To Guide New firmware "keep root" WW-18.0840.2103.26

Okay so I went to the Asus website
https://www.asus.com/supportonly/ROG Phone 5 (ZS673KS)/HelpDesk_Download/
Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method with the OnePlus 8 pro same process worked for me I downloaded the firmware from the website put it in the root of my phone, the phone detected the update immediately I got to pop up on the screen and it started installing the update. Then it asked if you want to reboot or reboot later "do not reboot" then go into magisk, then go into "install"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it will give you an option to keep root after an OTA. So once you choose the option as you can see on the screenshot let it patch and do its thing and reboot. I hope this helps somebody.

Whenever i dump payload.bin using payload dumper to get boot.img and patching it using magisk when i flash it causes bootloop! So i can't root it. I think it's payload dumper's issue. Btw can you give me the patched boot.img?

sorankira said:
Whenever i dump payload.bin using payload dumper to get boot.img and patching it using magisk when i flash it causes bootloop! So i can't root it. I think it's payload dumper's issue. Btw can you give me the patched boot.img?
Click to expand...
Click to collapse
What formal version were you in before? Would you like to try my patched boot image?

chairman011 said:
What formal version were you in before? Would you like to try my patched boot image?
Click to expand...
Click to collapse
I just bought the Rog 5 and upgraded to last firm and never had problem to dumpa boot img ( my phone before Rog 5 was Nubia Redmagic 5G). Yes I like to try your boot img, my last firm is WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46. Thanks!

chairman011 said:
What formal version were you in before? Would you like to try my patched boot image?
Click to expand...
Click to collapse
Yes i would like to use your patched boot.img
And anyway to disable HardwareStub Service notification? V

how to solve this ? i follow your method to upgrade my rooted firmware to latest version , but my safetynet not passed ? before uograde my firmware , the safetynet passed without error

Quiinny said:
how to solve this ? i follow your method to upgrade my rooted firmware to latest version , but my safetynet not passed ? before uograde my firmware , the safetynet passed without errorView attachment 5400203
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com

twistedumbrella said:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
already installed it. but still not passed the safety net

Quiinny said:
already installed it. but still not passed the safety net
Click to expand...
Click to collapse
Clear Data of Google Playstore and Play Services.
Ensure Magisk hide is enabled and Magisk app is hidden with a different package name.

OP your advice worked perfectly for me.
I wanted to note that my phone didn't see the update file right away, but I was prompted immediately after exiting my adb shell session and unplugging the phone from my laptop.

Question HELP!!! Pixel 7 Pro rooted - Magisk N/A [SOLVED]

Hi,
My Pixel 7 Pro has a problem.
My phone has QPR3 Beta 3 T3B3.230413.003.
The phone is rooted but Magisk dosen't work and root access and modules icons are grayed out.
I tried to patch the phone with PixelFlasher and ADB, but no way.
Attached you will find the screenshot of Magisk App.
Please help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm confused. I'd say... you're not rooted?

I'M ROOTED...

Yeah that's weird then
When you open a root app, does it request root?

krakout said:
Yeah that's weird then
When you open a root app, does it request root?
Click to expand...
Click to collapse

Just a thought - could it be you patched with another Magisk version rather than the official one?

krakout said:
Just a thought - could it be you patched with another Magisk version rather than the official one?
Click to expand...
Click to collapse
Installed Greenify. No root request. Attached the creenshot. I installed Magisk from the Github site. 26.1 version.

podon81 said:
Hi,
My Pixel 7 Pro has a problem.
My phone has QPR3 Beta 3 T3B3.230413.003.
The phone is rooted but Magisk dosen't work and root access and modules icons are grayed out.
I tried to patch the phone with PixelFlasher and ADB, but no way.
Attached you will find the screenshot of Magisk App.
Please help me.
Click to expand...
Click to collapse
Do you have another version of the Magisk app hidden? If so, uninstall it.
Also, what exact steps did you take to root?

^^^^ You most likely have another Magisk on your phone, but it's hidden.
That's why apps that previously had root still work.
Go through the apps list and look for the app "Settings" without an icon.

Ripthulhu said:
^^^^ You most likely have another Magisk on your phone, but it's hidden.
That's why apps that previously had root still work.
Go through the apps list and look for the app "Settings" without an icon.
Click to expand...
Click to collapse
Yeah but if that were the case the apps would ask for root and the prompt would appear.

Nope it doesn't. Not in this scenario

Ripthulhu said:
Nope it doesn't. Not in this scenario
Click to expand...
Click to collapse
"This scenario" meaning two managers? Actually yes, the prompt is given. I witnessed it myself (again) yesterday.

It seems like you are having trouble getting root access and modules to work on your Pixel 7 Pro. Try these things if they can work-
Update to the latest version of Magisk.
Uninstall and reinstall Magisk.
Check your device's firmware compatibility.Open the Magisk app and go to Settings. Check that the "Magisk Hide" option is enabled and that the "Magisk Core Only Mode" option is disabled.
If none of the above steps work, you may need to flash the stock firmware on your device.
Just try I am hopeful that it will resolve your issue.​

krakout said:
"This scenario" meaning two managers? Actually yes, the prompt is given. I witnessed it myself (again) yesterday.
Click to expand...
Click to collapse
I was in the same scenario and it did not prompt me for new apps.
Apps previously granted root would still work, but new ones didn't.

Ripthulhu said:
I was in the same scenario and it did not prompt me for new apps.
Apps previously granted root would still work, but new ones didn't.
Click to expand...
Click to collapse
Fair enough, I don't remember about new apps to be honest.

anyabaker said:
It seems like you are having trouble getting root access and modules to work on your Pixel 7 Pro. Try these things if they can work-​​Update to the latest version of Magisk.​Uninstall and reinstall Magisk.​Check your device's firmware compatibility.Open the Magisk app and go to Settings. Check that the "Magisk Hide" option is enabled and that the "Magisk Core Only Mode" option is disabled.​If none of the above steps work, you may need to flash the stock firmware on your device.​​Just try I am hopeful that it will resolve your issue.​
Click to expand...
Click to collapse
No way to access to the options you mentioned... Look at screenshot pls...

What version of Magisk are you flashing?
Others on the thread....wasn't there a bug on certain Magisk canary versions where root checks were passing and root access was supposedly given to apps, but Magisk wasn't able to implement modules or confirm its own root status? It most likely has to do with that and/or in conjunction with being on a QPR as well....

simplepinoi177 said:
What version of Magisk are you flashing?
Others on the thread....wasn't there a bug on certain Magisk canary versions where root checks were passing and root access was supposedly given to apps, but Magisk wasn't able to implement modules or confirm its own root status? It most likely has to do with that and/or in conjunction with being on a QPR as well....
Click to expand...
Click to collapse
Version 26.1 stable

podon81 said:
Version 26.1 stable
Click to expand...
Click to collapse
Hmmm...interesting...
I forgot where I saw it -- it might've been in the main Magisk thread here on XDA, or in one of the Pixel 7 Pro rooting guides, might've even been a PixelFlasher thread -- but there was an issue (I believe it was canary 25206-25209 or something like that) that spoke about this similar issue; root detection would detect root and apps wouldn't put up a warning of lack of root access, but Magisk itself wouldn't confirm its own root status, the modules couldn't be activated, and the apps couldn't actually accomplish the tasks that required root -- it just wouldn't put up a warning/error stating it was lack of root access. I can't recall whatever came of it; I believe it was either downgrading to stable or updating to higher canary of 25210, but I can't recall off the top of my head. I do believe being on QPR was a factor, but I might be misremembering...
I suggest you try "finegling" the search function as best you can and see what users ended up doing...I'll see if I can't find it later...

Just to note, T3B3 runs fine with 26101 for me.