Database Info

If you have missed the news ... about SafetyNet !

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 +++

Netflix problem on rooted POCO (with TWRP and Magisk)

Hey Guys,
do you know how to fix problem with Netflix app? My app after unlock bootloader, install TWRP and root by Magisk doesn't work.
I try download older versions to 5.x and "liboemcrypto disabler" or even "magisk drm disabler (MDD)" with LITE option, but this is not working.
Please help me to fix this problem. I have original MUI stock.

mutineer said:
Hey Guys,
do you know how to fix problem with Netflix app? My app after unlock bootloader, install TWRP and root by Magisk doesn't work.
I try download older versions to 5.x and "liboemcrypto disabler" or even "magisk drm disabler (MDD)" with LITE option, but this is not working.
Please help me to fix this problem. I have original MUI stock.
Click to expand...
Click to collapse
Magisk DRM disabler disables DRM which Is necessary for Netflix to work, so don't install it next time if you want Netflix to work. Currently, our device doesn't pass SafetyNet which Is necessary for Netflix and some banking apps to work. There Is a solution to that by using MagiskProps Config and some other solution, but I don't care about Netflix as I don't use it so I can't give you a complete solution.

SkaboXD said:
Magisk DRM disabler disables DRM which Is necessary for Netflix to work, so don't install it next time if you want Netflix to work. Currently, our device doesn't pass SafetyNet which Is necessary for Netflix and some banking apps to work. There Is a solution to that by using MagiskProps Config and some other solution, but I don't care about Netflix as I don't use it so I can't give you a complete solution.
Click to expand...
Click to collapse
Thx for answer. I have MagiskProp Config and my POCO X3 NFC pass SafetyNet - I can pay by phone in shops.
Do you know how to enable DRM again? When I delete the Magisk DRM disable that will be ok?

mutineer said:
Thx for answer. I have MagiskProp Config and my POCO X3 NFC pass SafetyNet - I can pay by phone in shops.
Do you know how to enable DRM again? When I delete the Magisk DRM disable that will be ok?
Click to expand...
Click to collapse
That's right. Just delete module, reboot & you're good to go.

Netflix works on stock ROM with magisk and twrp and no mentioned modules.
{
"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"
}

editheraven said:
Netflix works on stock ROM with magisk and twrp and no mentioned modules.
Click to expand...
Click to collapse
Can you find Netflix in Google Play? I cant find, so I download by official Netflix page. I delete whole modules in Magisk and clean app data in Netflix app. App starts but after 10sec shows error that cant be run on my device...

[FASTBOOT] [daisy] Patched boot.img for V11.0.16.0 (Android 10)

boot img for december update, patched it with magisk 21.4 :
https://yasmar.net/xda/patched_boot_11.0.16.0_214.img.gz
thanks to @a1291762
Spoiler: magisk 20.4
Xiaomi Mi A2 Lite 11.0.16.0 / Magisk 20.4
or
{
"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"
}

Seems that Magisk 21.3 was declared stable. I have upgraded and it seems fine.
If anyone's looking for a 21.3 patched boot...
https://yasmar.net/xda/patched_boot_11.0.16.0_213.img.gz

... and now we have 21.4
https://yasmar.net/xda/patched_boot_11.0.16.0_214.img.gz

yhanks you, updated the post

I'm experiencing an isue after instal·ling Magisk.
Ringtones (notifications, and so on) are not working, and if I try to change them through the setup menu, it freezes for a while and has no effect).
I was a bit lost until after repeating the flash procedure I identified it happens only after Magisk has been installed. Flashing again stock solves the problem.
I've tried:
- with twrp: Magisk 21.4
- with twrp Magisk canary 21.4
- fastboot flash boot @a1291762 patched boot image
- fastboot flash boot my own patched boot image
- fastboot boot patched boot image
I've read of someone with the same issue, but have not found any solution.
Any idea?
Thks!

xabier-bo said:
Ringtones (notifications, and so on) are not working, and if I try to change them through the setup menu, it freezes for a while and has no effect).
Click to expand...
Click to collapse
That's a bit odd... I don't see this on my phone.
There was an issue I ran into on Pie where having the phone in do not disturb meant notifications couldn't be changed. And another on 10 where Outlook notifications couldn't be changed. But neither of these should affect changing the ringtone on 10.

a1291762 said:
That's a bit odd... I don't see this on my phone.
There was an issue I ran into on Pie where having the phone in do not disturb meant notifications couldn't be changed. And another on 10 where Outlook notifications couldn't be changed. But neither of these should affect changing the ringtone on 10.
Click to expand...
Click to collapse
I hadn't seen this before either. But I have reproduced the process, and at least on my device, I have verified that it is installing Magisk that generates the issue, and uninstalling it eliminates the problem.
I will search better in the forums, to see if I can locate the message describing the same or quite a similar problem.
Thanks, by the way!

maybe one of your modules. what if you deactivate all modules and reinstall magisk?

Thanks!
I'll try it, I have very few and basic ones, but I'll tell if it works

Any improvement on this update?

Kaimilo said:
Any improvement on this update?
Click to expand...
Click to collapse
IMO This phone is never going to get better. The updates are mandatory (for Xioami) security updates but that's it. Seems pretty clear they are not trying to fix bugs, they're just bringing the security patches over.

xabier-bo said:
Thanks!
I'll try it, I have very few and basic ones, but I'll tell if it works
Click to expand...
Click to collapse
I promised feed back.
Just in case anybody finds him/herself with this odd issue: your suggestion worked. What I did:
- I removed magisk manager
- ran the magisk uninstaller (booting in twrp)
- installed magisk 21.4 with twrp as well
And it did it!
Thanks again...
PS. The only module I had installed was the systemless one

Oh... I never did my change analysis for this version.
It's the usual(ish) suspects for a security update...
media stuff (av1, mediaplayerservice), DNS, bluetooth, wifi, qti (qualcomm?) libs.
a bunch of camera libs changed (iface, imglib, mct, sensor_modules, stats_modules).

Nexus 6P - Lineage OS 15.1 - Magisk fails CTS Profile check

Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
{
"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"
}

StyleM said:
Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
View attachment 5324283View attachment 5324285View attachment 5324287
Click to expand...
Click to collapse
try using magisk 20.4 n dont update just keep the 20.4 version

howdeedodat said:
try using magisk 20.4 n dont update just keep the 20.4 version
Click to expand...
Click to collapse
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.

StyleM said:
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.
Click to expand...
Click to collapse
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?

howdeedodat said:
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?
Click to expand...
Click to collapse
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)

StyleM said:
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)
Click to expand...
Click to collapse
flash it in magisk or sideload theres no different as long u have tha magisk on ur phone because its a magisk module

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.