Database Develop

MI 8 Global Beta - Magisk 17.1 ctsProfile: false

I installed the latest beta beta version of my device. Magisk gives this error. How can I solve?
MIUI 10 Android 9 8.11.15
ctsProfile: false
{
"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's likely not certified yet. Try using a certified device fingerprint:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228

Didgeridoohan said:
It's likely not certified yet. Try using a certified device fingerprint:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I uploaded it to the device, but nothing changed.

By.TRabZonLu™ said:
I uploaded it to the device, but nothing changed.
Click to expand...
Click to collapse
Did you run the props command, pick a certified fingerprint and reboot?
https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#usage

Didgeridoohan said:
Did you run the props command, pick a certified fingerprint and reboot?
https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#usage
Click to expand...
Click to collapse
What am I supposed to do now? (xiaomi mi 8)

By.TRabZonLu™ said:
What am I supposed to do now? (xiaomi mi 8)
Click to expand...
Click to collapse
You pick the option to edit your device's fingerprint, pick one from the list and see if it works.
There's no Mi 8 fingerprint on there, but for the sake of just passing SafetyNet it doesn't matter witch one you use.
If you have further questions check the documentation, most things are covered there:
https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md

Didgeridoohan said:
You pick the option to edit your device's fingerprint, pick one from the list and see if it works.
There's no Mi 8 fingerprint on there, but for the sake of just passing SafetyNet it doesn't matter witch one you use.
If you have further questions check the documentation, most things are covered there:
https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md
Click to expand...
Click to collapse
I chose Pocophone F1, it was successful. How can I return to the original?

By.TRabZonLu™ said:
I chose Pocophone F1, it was successful. How can I return to the original?
Click to expand...
Click to collapse
If you haven't found it already there's an option to reset the fingerprint when running the props command. But your device will fail CTS again. If you could get me a Mi 8 stable fingerprint I could add it to the module. Instructions here:
https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

Didgeridoohan said:
If you haven't found it already there's an option to reset the fingerprint when running the props command. But your device will fail CTS again. If you could get me a Mi 8 stable fingerprint I could add it to the module. Instructions here:
https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
Click to expand...
Click to collapse
In this way?
:/ # getprop ro.build.fingerprint
Xiaomi/dipper/dipper:9/PKQ1.180729.001/8.11.15:user/release-key

Magisk v 20.2 - Fingerprint auth double step

Hey there, community !
I've noticed that since last update, whenever Magisk prompts for su authorization I have to press "grant" button and then touch the fingerprint to authenticate. I would like to got back to just touch the fingerprint for authorization.
I've already reinstalled Magisk, double checked configuration, cleaned up dalvik/art cache but the 'problem' persists.
TLDR;
What I want:
{
"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"
}
What I've got:
Thanks you all !
EDIT: Wondering if it is an Android 10 "feature" rather than a magisk 'bug'

If I remember correctly, that's caused by the Magisk Manager supporting Google's new biometric authentication API (Pixel 4 face unlock) and not something that can be changed.

Penaa said:
Hey there, community !
I've noticed that since last update, whenever Magisk prompts for su authorization I have to press "grant" button and then touch the fingerprint to authenticate. I would like to got back to just touch the fingerprint for authorization.
I've already reinstalled Magisk, double checked configuration, cleaned up dalvik/art cache but the 'problem' persists.
TLDR;
What I want:
What I've got:
Thanks you all !
EDIT: Wondering if it is an Android 10 "feature" rather than a magisk 'bug'
Click to expand...
Click to collapse
They're using the new API for Biometrics. It's not actually an Android 10 feature, but just a new API... It also looked like that on older versions such as Pie (older versions than Pie aren't tested yet.)

yashinodon said:
They're using the new API for Biometrics. It's not actually an Android 10 feature, but just a new API... It also looked like that on older versions such as Pie (older versions than Pie aren't tested yet.)
Click to expand...
Click to collapse
By 'they' you mean Android or Magisk ?
Thanks for the answer !

Magisk - SafetyNet CTSprofile false (Xiaomi Redmi Note 8 Pro)

Hi, yesterday i just rooted phone and installed magisk for the first time. I installed my bank app to payment and i couldnt use nfc. SafetyNet didnt pass test correctly. I installed fix "Universal SafetyNet fix" and it didnt work, i used "MagiskHidePropsConfig" and changed device fingerprint and still nothing. Finally i found some youtube video and installed "Magisk Canary" and something finally changed. BasicIntegrity passed test, evaltype was "hardware" (i fixed it by downloading some fix called hardwareoff_1.1), but ctsProfile is still failing and now im stuck. Dont know what to do.
I downloaded ROM from here : https://c.mi.com/oc/miuidownload/detail?guide=2
and its "Xiaomi Redmi Note 8 Pro Latest Europe Stable Version Fastboot File Download"
I think MagiskHide works fine, because when i added my bank app its shows that i can log in with my biometric, same Netflix works fine, but still cant add my payment card in "NFC"
{
"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 have root my Samsung Note 8 as yesterday and was headache with fix SafetyNet. But after all, I have success. I dont know exactly what made it success but you can try.
You have install MagiskProps and Universal SafetyNet fix, that good.
Let disable Universal SafetyNet fix and reboot.
Then use MagiskProps change to another license (I use samsung s9 plus - android9) > reboot and check.
If still fail, use MagiskProps change to default (remove all settings) > reboot and check.
If still fail, now enable Universal SafetyNet fix and reboot.
Result: SafetyNet suddenly pass.
That all I do. Good luck!

Question How to gain root access PLUS pass Safety Net

Hi All,
Received this phone a couple of weeks ago and have successfully unlocked the bootloader. I've also obtained root access, but have never been able to pass SafetyNet. The traditional methods do nothing. Have made various attempts using suggestions here on XDA, as well as searching Google, but each and every one results in an "Attestation Failed" message.
Some posts state to use the Magisk canary build and then hide Magisk as well as verifying SafetyNet. Unfortunately, the canary build doesn't provide an option to check the SafetyNet, nor is there any way to hide Magisk, nor hide any Google services/apps. The MagiskHide Props Config also has never worked for me either. Even when selecting Pixel 3A which supposedly was passing the old SafetyNet attestation method.
So, does anyone have or know of any root method that actually works correctly for the Redmi Note 10 Pro?
Cheers and Happy New Year,
Amy

AmyS9 said:
Hi All,
Received this phone a couple of weeks ago and have successfully unlocked the bootloader. I've also obtained root access, but have never been able to pass SafetyNet. The traditional methods do nothing. Have made various attempts using suggestions here on XDA, as well as searching Google, but each and every one results in an "Attestation Failed" message.
Some posts state to use the Magisk canary build and then hide Magisk as well as verifying SafetyNet. Unfortunately, the canary build doesn't provide an option to check the SafetyNet, nor is there any way to hide Magisk, nor hide any Google services/apps. The MagiskHide Props Config also has never worked for me either. Even when selecting Pixel 3A which supposedly was passing the old SafetyNet attestation method.
So, does anyone have or know of any root method that actually works correctly for the Redmi Note 10 Pro?
Cheers and Happy New Year,
Amy
Click to expand...
Click to collapse
Canary with zygisk and deny list additional flash magisks safetynefix (Google it) is still working
{
"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"
}

Question System UI isn't responding - after December update

Rooted Pixel7 here.
After the December update, I randomly get:
"system UI isn't responding"
Do you also have this problem without root?
Installed magisk modules:
LSPosed
volte-properties for pixel6
universal safety net fix
Systemless hosts
Call recorder skvalex
AOSP mods
Does anyone know where the problem is?

I was also getting random SystemUI crashes until I updated AOSPMods.
Unless you are on the latest canary builds (178+ I believe), you may see issues like this. There were lots of changes in the December feature drop that broke AOSPMod for many users.

Well thank you. And what version of AOSP mods do you have?
I can't update.
ekeppel said:
I was also getting random SystemUI crashes until I updated AOSPMods.
Unless you are on the latest canary builds (178+ I believe), you may see issues like this. There were lots of changes in the December feature drop that broke AOSPMod for many users.
Click to expand...
Click to collapse
{
"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 on canary build 186, which is the latest as of this post. Just open the AOSPMods app, hit the 3-dot menu in the upper right, select App Updates, then select the Canary update channel / full package, and finally hit Update. After the update, you will be prompted to reboot.

NOT COMPATIBLE WITH Android 13 Dec 2022 (Feature drop 2022), or AOSP 13 R18 or Later

Right. The version you have installed has issues with the December update. You should see the AOSPMod app in your apps list though all the same, and it should open just fine. It's just that many features are broken. Once you get into the app, you can change over to the Canary channel and get the working version.
Edit: By the way, even though it says it's not compatible when you're on the canary branch on Github, the latest builds are in fact compatible. These updates were just rolled out over the past couple of days.

Thank you for your help and your time.
I updated it successfully.

Great! Hopefully, that was the source of your SystemUI crashes. ;-)