Hello guys.
I've always used a xiaomi.eu - stable rom on my mi8 and googlepay (an this ctsProfile) has never been a problem.
Around ~a month ago i tried a pixel-experience rom on my device and since then (no idea if there can be a correlation) i'm no longer able to make it work.
I returned to the same stable i was using, i tried newer stable, newer beta, i even deep flashed via fastboot the stock rom for my mi8 but i always fail the ctsProfile test, even with the stock rom unrooted.
I tried the SafetyPatch - https://forum.xda-developers.com/apps/magisk/module-safetypatcher-t3809879 but with no success and even the MagiskHide Props Config https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228.
Currently i'm running:
MIUI 11.2
Xiaomi.eu 20.3.5
Android 10QKQ1.190828.002
and according to Magiskhide this is my device fingerprint.
Any suggestion?
https://i.imgur.com/avQBehI.jpg
{
"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"
}
Ozozuz said:
Hello guys.
I've always used a xiaomi.eu - stable rom on my mi8 and googlepay (an this ctsProfile) has never been a problem.
Around ~a month ago i tried a pixel-experience rom on my device and since then (no idea if there can be a correlation) i'm no longer able to make it work.
I returned to the same stable i was using, i tried newer stable, newer beta, i even deep flashed via fastboot the stock rom for my mi8 but i always fail the ctsProfile test, even with the stock rom unrooted.
I tried the SafetyPatch - https://forum.xda-developers.com/apps/magisk/module-safetypatcher-t3809879 but with no success and even the MagiskHide Props Config https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228.
Currently i'm running:
MIUI 11.2
Xiaomi.eu 20.3.5
Android 10QKQ1.190828.002
and according to Magiskhide this is my device fingerprint.
Any suggestion?
https://i.imgur.com/avQBehI.jpg
Click to expand...
Click to collapse
This is known problem as Google changed the safety check methods more-less week ago. So if you had bootloader unlocked it dorsn't matter if you have stock rom and no root
Here you can find hot discussion regarding this new CTS issue:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page288
Sent from my SM-N960F via Tapatalk
Related
Hi guys !
Just got my Xiaomi MI5 Pro.
Miui version: 7.2.94.99 (MAACNDB) stable.
Build number: MRA58K
Everything is stock, non root it.
I didn't touch nothing yet.
For now it's only chase bank app. It's weird guys, if someone one knows what the heck....
avetny said:
Hi guys !
Just got my Xiaomi MI5 Pro.
Miui version: 7.2.94.99 (MAACNDB) stable.
Build number: MRA58K
Everything is stock, non root it.
I didn't touch nothing yet.
For now it's only chase bank app. It's weird guys, if someone one knows what the heck....
Click to expand...
Click to collapse
That is a weird custom rom mate. Just install some official or xiaomi.eu rom, then you should be fine.
abyssq said:
That is a weird custom rom mate. Just install some official or xiaomi.eu rom, then you should be fine.
Click to expand...
Click to collapse
oh man thank you soo much.
Ill take a look now
abyssq said:
That is a weird custom rom mate. Just install some official or xiaomi.eu rom, then you should be fine.
Click to expand...
Click to collapse
My friend I think the seller modified my rom. If I will flash the stock rom I will get in to bootloop....
Please is there any guide how to do everything safely?
(ps: sorry im not a noob just never deal with xiaomi devices before. (I also received a permission to unlock bootloader)
i have newest rom. brand new phone. Original stable rom. (same version as on website, ota updated).
My chase app wont log in. if i type in incorrect stuff it says my password is wrong, but when i type in right stuff it gives me this:
{
"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've been able to successfully install Viper on several Oreo Roms - it works fine for internal speaker and wired headphones. However as soon as I connect my Bluetooth Headphones (Sony MDR1000X) the driver state changes to Abnormal and Viper stops processing - meaning I don't get Viper goodness through my Bluetooth headphones.
I've tried every which way to install Viper, various APK's, Flashable Zips, all available in Magisk, ARISE sound system, etc..
The same occurs across all Oreo Roms. Works fine on Nougat Roms...
Any ideas? Anyone else see the same behaviour?
Thanks
Paul
How did you installed V4A on Oreo 8.1? I'm running LOS 15.1 on Mi6 I can't figured it out how to install it. Classic I/O error...
I have this exact same problem, have you found any solution to this yet?
The only Oreo ROM I was able to get this working on was the MIUI Oreo. I no longer own the Mix, moved to a Note 8. Hope you guys get to the bottom of this!
Using Mi6 with LineageOS 15.1. Perfectly running was at first build but now ( running 3th build ) it gives I/O error still can't able to solve...
Chandler Muriel Bing said:
Using Mi6 with LineageOS 15.1. Perfectly running was at first build but now ( running 3th build ) it gives I/O error still can't able to solve...
Click to expand...
Click to collapse
SOLVED! Just ROOT your device with latest Magisk (using v16 now), open Magisk menu tap downloads and type "viper4android" and then download and install "ViPER4Android FX for Magisk v15" module. Now you are good to go!
{
"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"
}
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 !
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!
I recently changed my default rom to do some tests with the miui beta china, but I ended up coming across this message in some apps that I tried to 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"
}
My device is not rooted at the moment!
OYH0 said:
I recently changed my default rom to do some tests with the miui beta china, but I ended up coming across this message in some apps that I tried to install:
My device is not rooted at the moment!
Click to expand...
Click to collapse
Probably because the bootloader is unlocked and the play store not certified.
If your device is a Chinese version you cannot lock the bootloader (brick) with a Global, EEA, etc. version.
Root +magisk hide necessary.
For other versions locking possible with Miflash.
Or
Install these Roms (based on china ,stable or Weekly) you will have the play store certified without root and without locking the bootloader.
NOSS8 said:
Probably because the bootloader is unlocked and the play store not certified.
If your device is a Chinese version you cannot lock the bootloader (brick) with a Global, EEA, etc. version.
Root +magisk hide necessary.
For other versions locking possible with Miflash.
Or
Install these Roms (based on china ,stable or Weekly) you will have the plastore certified without root and without locking the bootloader.
Click to expand...
Click to collapse
I've already done some procedure to hide magisk, like installing safetyNet Fiz, Shamiko and Airfrozen
I saw some things as soon as there are some modules that solve this problem, like the play store visa or vending visa, but if there is another module that can help me?
OYH0 said:
I've already done some procedure to hide magisk, like installing safetyNet Fiz, Shamiko and Airfrozen
I saw some things as soon as there are some modules that solve this problem, like the play store visa or vending visa, but if there is another module that can help me?
Click to expand...
Click to collapse
Did you try Magisk Beta which can be activated from the classic apps.