So this may have been asked before, I just haven't seen it . I am rooted and running Feb factory image for a month now with pretty much no issues. The other day I happen to notice there was a Magisk update showing on the app, so I upgraded. After reboot I noticed pretty much any app that requires root (AdAway, De-Bloater, etc.) no longer work since they cant access the root filesystems!
I have tried to reinstall and re-patch through the app but same results each time. Is there a way to get root working again? Should I go back to the previous Magisk build?
Last versions (I think 26207-10?) have been buggy. Either downgrade to 06 or (like I did) use Delta which has fixed these bugs!
I've seen one other report of someone actually losing root.
I tried to set to stable channel and go back to 200, but did not seem to work. Delta seems interesting, do I need to first uninstall current Magisk app?
I think it provides instructions the first time you run it. When I did, I still had official installed and it told me to uninstall it afterwards or something? But there are instructions on GitHub.
...ah, here: https://huskydg.github.io/magisk-files/docs/faq.html .
Though to be honest if you've lost root maybe you'll need to flash it (I recommend Pixel Flasher). Btw, I'm on canary with no issues.
krakout said:
I think it provides instructions the first time you run it. When I did, I still had official installed and it told me to uninstall it afterwards or something? But there are instructions on GitHub.
...ah, here: https://huskydg.github.io/magisk-files/docs/faq.html .
Though to be honest if you've lost root maybe you'll need to flash it (I recommend Pixel Flasher). Btw, I'm on canary with no issues.
Click to expand...
Click to collapse
I use delta. Can I uninstall magisk app now?
Sure, you can always reinstall anyhow. Delta is great for me!
krakout said:
I think it provides instructions the first time you run it. When I did, I still had official installed and it told me to uninstall it afterwards or something? But there are instructions on GitHub.
...ah, here: https://huskydg.github.io/magisk-files/docs/faq.html .
Though to be honest if you've lost root maybe you'll need to flash it (I recommend Pixel Flasher). Btw, I'm on canary with no issues.
Click to expand...
Click to collapse
Nice, so I got Delta installed and root IS working again! I uninstalled original Magisk and all appears ok now! I guess I will keep rolling with the Delta vers from now on as it appears to fix issues quicker.
Thanks for the advice!!
Now just waiting for March updates, LOL.
Same as everyone else Hopefully tomorrow...
Just be prepared, Delta canary has MANY releases, sometimes a couple during the same day. But I've never encountered an issue, and it installs modules nicely (though I use Fox for the repos)
Does Delta works with Android 14 DP2 and hiding works for banking apps?
No idea, I think rooting DP2 is still problematic in general...
Johnwu should make the magisk ui modern like delta. I use delta only for ui. Lol
And no more major updates are coming from magisk. It's still 25.2 The highest gap between major updates is already made
this same thing happened to me too. no matter what i did i couldnt root anymore with magisk canary anymore and it worked for the last few months. is there any way to root again cause i dont like delta.
krakout said:
Last versions (I think 26207-10?) have been buggy. Either downgrade to 06 or (like I did) use Delta which has fixed these bugs!
I've seen one other report of someone actually losing root.
Click to expand...
Click to collapse
That would be me. I did the same thing. I downgraded to 25206, installed delta, everything except wipe the phone and I still don't have root.
When I initially installed 25210, there is something that remains on the phone even after uninstalling magisk multiple ways. I don't have root and it persists.
banshee28 said:
Nice, so I got Delta installed and root IS working again! I uninstalled original Magisk and all appears ok now! I guess I will keep rolling with the Delta vers from now on as it appears to fix issues quicker.
Thanks for the advice!!
Now just waiting for March updates, LOL.
Click to expand...
Click to collapse
I did the same and I still don't have root. What method did you use to uninstall?
UPDATE: Installing march update with magisk delta worked. The uninstall magisk didn't really uninstall the bug. FINALLY I have root again.
if you build the Magisk source files from the GitHub repo, root/magisk works on TQ1A.230205.002.
the instructions are on their GitHub page (https://github.com/topjohnwu/Magisk). i built the APK on my Fedora 37 machine. the process is a bit involved but let me know if you want to try it and have questions.
Fedora 37 comes with Java 17 pre-installed which was helpful for this compilation.
{
"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"
}
Related
here
We will live without pokemon go. No one should cry.
Tomek0000 said:
We will live without pokemon go. No one should cry.
Click to expand...
Click to collapse
We will, but it's harder when you use banking apps that will fail to launch because of such implementation.
Banking apps. NFC Paying apps. GooglePay. Probably Netflix and similar. Maybe even whole device encryption.
Its unfortunate but if there is a demand, there will be a supply. This means that if people are wanting to have this ability to hide their root and the fact that their bootloader is unlocked. You can almost guarantee that you will have many developers working on some sort of way to get around this new verification. It's just a matter of time and how well Google responds to the inevitable bypasses that are presented over time. It's going to take some time for them to properly implement these changes which is why we can still pass ctsprofile and safetynet overall on our devices. In the near future this is probably not going to be a possibility for a while until someone finds a way to get around it. But yeah, it sucks if the app actively checks the status of the safetynet check such as google's play protect. If the device is not certified, it will be unable to install certain applications such as Netflix from my experience. Banking apps also use this technology for "security" reasons.
Any solution? I tried uninstall magisk only and dont work.
{
"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"
}
This same problem from today morning. Google pay fix and Magisk hide unhelpfull.
joaonds said:
Any solution? I tried uninstall magisk only and dont work.
Click to expand...
Click to collapse
This same problem from today morning. Google pay fix and Magisk hide unhelpfull.
joaonds said:
Any solution? I tried uninstall magisk only and dont work.
Click to expand...
Click to collapse
Check your bootloader :
if unlocked => no way to get GPay working anymore !
Netflix is still available and working at (DRM L1) ...
The only way to get back you GPay is to flash an official firmware (not from xiaomi.eu) and relock your bootloader !
Google is giving us a hard time these days !
gringo80 said:
Check your bootloader :
if unlocked => no way to get GPay working anymore !
Netflix is still available and working at (DRM L1) ...
The only way to get back you GPay is to flash an official firmware (not from xiaomi.eu) and relock your bootloader !
Google is giving us a hard time these days !
Click to expand...
Click to collapse
You need to download Rom for fastboot for MI. When you download it, unzip it, there is a "persist.img" file in the Images folder. You put it in your phone or you can install it via USB. Restart to TWRP, install, install the image, find the persist.img file on your phone or flash drive and choose install as persist.
ghostmz said:
You need to download Rom for fastboot for MI. When you download it, unzip it, there is a "persist.img" file in the Images folder. You put it in your phone or you can install it via USB. Restart to TWRP, install, install the image, find the persist.img file on your phone or flash drive and choose install as persist.
Click to expand...
Click to collapse
wtf
gringo80 said:
Check your bootloader :
if unlocked => no way to get GPay working anymore !
Netflix is still available and working at (DRM L1) ...
The only way to get back you GPay is to flash an official firmware (not from xiaomi.eu) and relock your bootloader !
Google is giving us a hard time these days !
Click to expand...
Click to collapse
I see option to fix this, but in Pie roms only (patching a gsm file).
in youtube.
joaonds said:
I see option to fix this, but in Pie roms only (patching a gsm file).
in youtube.
Click to expand...
Click to collapse
Read here the solution
in our case, change (Pie) or add (Q) in build.prop (system_root only) :
ro.product.model=Mi 9 Lite
to
ro.product.model=pyxis
When you finish fixing cts profile go to Magisk Manager and hide GPay & Google Play Services !!!
You must hide the Managisk Manager too (Parameters) with a random name : this is mandatory to get GPay or any banking app working again !
Reboot +++
Hi I've unlocked the bootloader, what's the next step to root & flash twrp?
Hey there, what rom are you hoping to run? I'm on the D6603 and there hasn't been a new twrp for over a year (muppets release).
I'm running Lineage 18.1-20211230 rom & recovery for about an hour now.
Magisk would not install via flash for me, despite claiming success.
Digging around the issues threads I found the 'canary' or debug file works fine.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Specific issue (worth a read, you might face this again and you could always edit the boot_patch.sh yourself)
Magisk 21.2 cannot be installed on Sony Z1c with Android 10 Lineage 17.1 · Issue #3636 · topjohnwu/Magisk
Description The last Magisk version that could be correct installed was 20.4. All versions after 20.4 fail (from the first canaries to 21.2 magisk-debug_6d88d8ad). 1.1 Flashing magisk-debug_6d88d8a...
github.com
Good luck
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others);
[MagiskInit] Support init.real on some Sony devices
Click to expand...
Click to collapse
z3-puzzled said:
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others)
Click to expand...
Click to collapse
ns404art said:
do you have a contact i can call?
Click to expand...
Click to collapse
Not sure what you mean by this. Posting a quick answer. I'll edit it with more:
Magisk can be downloaded from; https://github.com/topjohnwu/Magisk
It is the ONLY place you should get it from!
Edit:
If you were hoping for a one-to-one, I'd rather type it out, just in case anyone else should come looking.
To be honest, you haven't provided enough information about your phone model or your desired goals for me to give you a straightforward answer.
I have experience with the D6603 only. I've been using lineage for about a year with different recoveries and, in my opinion, for the path of least resistance you should probably use a recovery and rom from the same project. (When I had twrp as recovery, OTA updates would fail, but not say so. It was only when commenting on a reddit thread, I thought I'd add my version number and discovered I'd gone months on the same rom. Manually flashing the latest rom broke stuff in all sorts of ways. So...)
Probably best to treat it as a rolling release and stay up to date or else lock-in to one you're happy with.
If using lineage, check update news first, if 'planned for next release' includes rollback of features just added - probably skip that update.
Gaining root was the last step for me. I have no experience of rooting SONY rom.
(My desired goal was to cut out google and play store).
Rooting was just;
1) Download Magisk
2) Rename .apk to .zip (DO NOT zip IT UP)
3) adb sideload, ignore checksum failure and choose install anyway.
The recent Magisk update has made it easier though. I was able to patch the boot file from within the app, so you possibly don't need to sideload anymore.
Right, that's a wall already. If you need more please include details such as;
Phone model :Sony Z3 Plus D6653 (2nd edit - oops just saw this)
Desired goal
Desired rom
/Edit
z3-puzzled said:
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others);
Click to expand...
Click to collapse
I've unlocked the bootloader, what steps should I take to root and I'm planning to install a carbon rom
{
"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 would follow the lineage install guide and change filenames where appropriate.
https://wiki.lineageos.org/devices/z3/install
If you intend to push on with twrp as recovery. see;
TWRP 3.3.1-Z3 Build 2020-02-12
This is the latest TWRP 3.3.1 build by The Muppets. This TWRP supports Android 8-10 for now. ROM recommended: LineageOS 16.0, LineageOS 17.1 and CarbonRom 8.0 Download: TWRP 3.3.1-Z3 or Mirror How to install: First of all you MUST flash...
forum.xda-developers.com
Which recommends, amongst others; Carbon 8. So old version
You could try latest lineage recovery & Carbon 9.
Your best bet is to ask within the Carbon thread;
https://forum.xda-developers.com/t/11-official-carbonrom-cr-9-0-enchilada.4313373
good luck
Official support is now here! You can flash right over your old installation if you are coming from this ROM (no factory reset needed).
https://download.lineageos.org/bluejay
Lineage OS 20.0 - Unofficial - Pixel 6a
{
"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"
}
Hi all. I noticed that there isn't official Lineage OS support for our Pixel 6a, so I decided to build it until then (if it happens). Since it appears to be working correctly, I wanted to share it with anyone else who has an interest. I'm not changing anything about it (other than making the updater allow unofficial updates) and building straight from the Lineage OS sources. I'll attempt to build it roughly 1x per month, usually around the middle to allow for most security updates to take effect. I daily drive the ROM, so I'll try to only post updates as long as basic functionality is working.
Latest ROM and Recovery:
ROM
Recovery
(Don't worry about the page saying Pixel 6. It wouldn't let me select 6a as an option)
Optional Latest Bootloader and Radio:
Bootloader
Radio
(Update with the fastboot flash bootloader / fastboot flash radio command respectively)
Old Releases:
Old
Optional Google Apps:
MindTheGapps
(Use Lineage 20 (Android 13) MindTheGapps link -> MindTheGapps-13.0.0-arm64-20XXXXXX_XXXXXX.zip)
Follow the "official" directions in order to flash the ROM and recovery files:
https://lineage.youd.dev/340458/41/devices/bluejay/install
OTA Support:
I modified the built in updater to support updates from my unofficial source for all flashed builds. I added an option under preferences to go back to the official source in the event that official builds are started. Just go to Settings -> System -> Updater to check. I plan on uploading to OneDrive and Dropbox for these updates (bandwidth might be temporarily limited). You can always manually flash without it from a PC.
Sources:
https://github.com/LineageOS
https://gitlab.com/the-muppets/proprietary_vendor_google_bluejay
https://github.com/calsurferpunk/android_packages_apps_Updater
https://github.com/calsurferpunk/lineageos_update
(roomservice.xml attached to this post for reference)
Great, thank you for your work. I'm downloading it right now. Out of my curiosity, will there be a build for raviole in the future as well?
Thx!
Face unlock built in?
CrazyLyte said:
Great, thank you for your work. I'm downloading it right now. Out of my curiosity, will there be a build for raviole in the future as well?
Click to expand...
Click to collapse
I'm just supporting the 6a/bluejay since that's what I have. If there were a lot of requests, I could attempt it, but I would have no way to test it (and the updater wouldn't be able to use the unofficial sources since I have limited space/bandwidth to share the updates from Dropbox/OneDrive).
lucky58 said:
Thx!
Face unlock built in?
Click to expand...
Click to collapse
I don't think face unlock is supported on any of the 6 series and I've seen no reference in the Lineage OS source/ROM.
Just picked up a 6a, but I'm going to run it stock for a bit just to see what that's like (I don't think I've run stock Android for at least a decade). Can confirm, the stock ROM does not have face unlock. It does have "Screen Attention" which is supposed to delay locking the screen if you're looking at it.
Looking forward to trying out your work Cal
Nice work. Thanks a bunch ..
Bruh, i accidentally flashed the android TV gapps package
New ROM update is available. You can either download it manually or use the built in updater if coming from the earlier version. You might want to update your bootloader/radio as well (optional and links are on the original post). The bootloader/radio img files are extracted from the latest official Google updates.
Mine always gets stuck on a random percentage when sideloading. I factory reset each time and have tried with and without radio/boot updates.
2mnml said:
Mine always gets stuck on a random percentage when sideloading. I factory reset each time and have tried with and without radio/boot updates.
Click to expand...
Click to collapse
Is it anywhere around 47%? It does appear to freeze for a bit but it's still loading. Did you wait a pretty long time and let it just keep going?
calsurferpunk said:
Is it anywhere around 47%? It does appear to freeze for a bit but it's still loading. Did you wait a pretty long time and let it just keep going?
Click to expand...
Click to collapse
No I only ever really waited for about 2 minutes, I know that is super impatient lol.
I am going to try it again today and let it run during my lunch. Is there a specific order in which I should sideload and update the boot/radio?
2mnml said:
No I only ever really waited for about 2 minutes, I know that is super impatient lol.
I am going to try it again today and let it run during my lunch. Is there a specific order in which I should sideload and update the boot/radio?
Click to expand...
Click to collapse
I updated my radio and bootloader first, but doing so is optional. I don't know how much it actually affects.
Looks like the official builds are coming out now:
LineageOS Downloads
download.lineageos.org
phuzz11 said:
Looks like the official builds are coming out now:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
I just saw the XDA article as well. Thanks for the update. I tried downloading the official through the updater but got a verification failed message. I'm not sure if it's a problem with the updater or actual official .zip.
If anyone manually downloads the official update, can you let me know if it works? I had an issue happen once before with my older OnePlus 8 Pro phone to where there was a problem with the first official download. I'm a little hesitant.
I just verified the official ROM. I was able to flash it right over the existing unofficial ROM without any trouble. Just follow the same instructions as for the unofficial:
1) Boot to recovery
2) Flash official ROM .zip
(optional)
3) Reboot to recovery again
4) Flash Google apps
5) Flash Magisk
6) Reboot system
I noticed there were some odd warnings when flashing the Google apps/Magisk (other than signature verification). Google apps seemed to error out at first (never seen that before) but I just flashed it again immediately and it finished.
Thanks to all for their support and the official Lineage OS team.
Hey, It's been for quite some time that I have tried to use google pay with magisk installed but failed miserably. I decided to install lineage on my Google Pixel 6a so that I could do a little more trick with that but still didn't work. What I don't get is that I passed multiple times SafetyNet but when I try to add my card It refuses to add it and then goes back to failed CTS. It's starting to get a little frustrating as I love my Pixel 6a and know that I can do cool stuff with it but the only thing that separates me from rooting and using custom firmwares is that I can't use Google Pay/Wallet (and maybe Netflix but I think there is some workarounds for that). So if anybody knows a way to actually fix that it would mean the world to me.
Thank you.
{
"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"
}
Spengoe said:
Hey, It's been for quite some time that I have tried to use google pay with magisk installed but failed miserably. I decided to install lineage on my Google Pixel 6a so that I could do a little more trick with that but still didn't work. What I don't get is that I passed multiple times SafetyNet but when I try to add my card It refuses to add it and then goes back to failed CTS. It's starting to get a little frustrating as I love my Pixel 6a and know that I can do cool stuff with it but the only thing that separates me from rooting and using custom firmwares is that I can't use Google Pay/Wallet (and maybe Netflix but I think there is some workarounds for that). So if anybody knows a way to actually fix that it would mean the world to me.
Thank you.
View attachment 5884533
Click to expand...
Click to collapse
Do you have the required SafetyNet fix module installed and have you added the required apps to Magisk denylist?
Lada333 said:
Do you have the required SafetyNet fix module installed and have you added the required apps to Magisk denylist?
Click to expand...
Click to collapse
I have installed Safetynet fix as well as putting the needed apps on deny list. I even tried Magiskhide Props config to change my fingerprint and also used Shamiko but it still didn't work.
Spengoe said:
I have installed Safetynet fix as well as putting the needed apps on deny list. I even tried Magiskhide Props config to change my fingerprint and also used Shamiko but it still didn't work.
Click to expand...
Click to collapse
Interesting. Have you cleared application data on the apps you've put on the denylist?
Also, which version of SafetynetFix have you installed? I think the most recent one doesn't work properly all the time.
I did in fact cleared the app data of the apps needed, and also used the latest version of SafetyNet. But an interesting fact is that I have passed SafetyNet times to times but when for example I am trying to add a card, cts just fails randomly. I don't know if it's a common issue or not though..
Lada333 said:
Interesting. Have you cleared application data on the apps you've put on the denylist?
Also, which version of SafetynetFix have you installed? I think the most recent one doesn't work properly all the time.
Click to expand...
Click to collapse
Spengoe said:
I did in fact cleared the app data of the apps needed, and also used the latest version of SafetyNet. But an interesting fact is that I have passed SafetyNet times to times but when for example I am trying to add a card, cts just fails randomly. I don't know if it's a common issue or not though..
Click to expand...
Click to collapse
Install this app from Google Play & test
Play Integrity API Checker - Apps on Google Play
Get info about your Device Integrity through the Play Intergrity API
play.google.com
1. Clean LineageOS with MindTheGapps Installed. (Non root)
2. LineageOS with Magisk Installed (Root without fix)
3. LineageOS with Magisk Installed (Root with Fix and SafetyNet Fix)
@Spengoe
3. LineageOS with Magisk Installed (Root with Fix and SafetyNet Fix)
Try install module
safetynet-fix-v2.4.0-MOD_1.2 by Displax
Spartacus500 said:
Install this app from Google Play & test
Play Integrity API Checker - Apps on Google Play
Get info about your Device Integrity through the Play Intergrity API
play.google.com
Click to expand...
Click to collapse
Thank you so much. Now everything works fine and I even added my card rn! I hope you have a great day and thank you for your time.
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.