MI 8 Global Beta - Magisk 17.1 ctsProfile: false - Magisk

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

Related

Magisk Hide

Magisk Hide doesn't seem to be working when it comes to my automobile's app, Uconnect. I'm rooted and now the Uconnect app states that I'm using an unsupported device. It worked before rooting.View attachment magisk_log_20181022_153305.log
{
"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"
}
tried clearing apps data?
kamilmirza said:
tried clearing apps data?
Click to expand...
Click to collapse
Yes. I even uninstalled, then reinstalled the Uconnect app.
destiple said:
Yes. I even uninstalled, then reinstalled the Uconnect app.
Click to expand...
Click to collapse
THIS great module might help :fingers-crossed:
Destiple, can you confirm whether MagiskHide Props Config, which kamilmirza referred you to, worked?
Alternately, did you find another solution to get Uconnect working?
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Didgeridoohan said:
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Click to expand...
Click to collapse
That's very good to know. I'm nervous about running a Canary build on my normal phone, but I'll see if I can find a spare to test it on.
Will the new MagiskHide be on the next Magisk update, or is it several versions away from being in the stable build?
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Coop9 said:
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Click to expand...
Click to collapse
Good to know! I tried it - hiding the manager by itself wasn't enough. But once I added Uconnect to the apps being hidden, *then* the app finally loaded.
Of course, upon trying to log in, the app immediately crashes. Would that have anything to do with it being added to the MagiskHide list?

[Ask] Is your rog phone 2 Safetynet pass without root? [Tencent model]

Is anyone use CN rom or WW rom(tencent) without root please share. Are your phone pass safetynet? also bootloader unlock or lock?
Now, I've tencent model with latest A10 WW rom(2004.60).
My fingerprint already WW but my phone description show as CN (use to be WW when I'm on A9). The phone is unroot but safetynet is failed (only CTS profile) not sure what the problem is but I kept my bootloader open (google already detect that?)
If I flash root image and install Magisk manager my phone will pass safetynet. The problem is I don't want to keep root.
Yes it is. You have install this module
{
"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"
}
Enviado desde mi ASUS_I001DC mediante Tapatalk
jorgeepelos said:
Yes it is. You have install this module
Enviado desde mi ASUS_I001DC mediante Tapatalk
Click to expand...
Click to collapse
OP does not want to keep Magisk on their phone.
l2aYz said:
Is anyone use CN rom or WW rom(tencent) without root please share. Are your phone pass safetynet? also bootloader unlock or lock?
Now, I've tencent model with latest A10 WW rom(2004.60).
My fingerprint already WW but my phone description show as CN (use to be WW when I'm on A9). The phone is unroot but safetynet is failed (only CTS profile) not sure what the problem is but I kept my bootloader open (google already detect that?)
If I flash root image and install Magisk manager my phone will pass safetynet. The problem is I don't want to keep root.
Click to expand...
Click to collapse
If you unlock the bootloader but do not use Magisk to pass Safetynet, most likely your kernel is exposing the fact that your bootloader is unlocked, thus tripping Safetynet. Stock kernel usually does this check.
Only suggestion would be to try flashing custom kernel by @Freak07 to see if that will work. Though I am not sure if he has patched his kernel to bypass the bootloader status check.

How To Guide Remove 10 seconds Always on Display Limit

If you are the Redmi note 10 Pro and Redmi Note 10 pro max use and want to remove the annoying option of "10 seconds after tapping" on Always in Display.
{
"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"
}
All you need a Rooted phone,, Just flash one magisk Module by @santiagog242 and you are done
Download Link of Magisk Module : https://forum.xda-developers.com/attachments/v1-1_miui_aod-patched-zip.5218833/
Video Guide :
on latest xiaomi.eu ROM this module doesn´t work... it often stucks and screen gets white etc...
i´ve tested this last week
There is no "solution" for this yet !
All the methods around it's FHET ( Fix Here Error There).
we hope to get a real solution
b0mb said:
on latest xiaomi.eu ROM this module doesn´t work... it often stucks and screen gets white etc...
i´ve tested this last week
Click to expand...
Click to collapse
Same thing for me..
b0mb said:
on latest xiaomi.eu ROM this module doesn´t work... it often stucks and screen gets white etc...
i´ve tested this last week
Click to expand...
Click to collapse
Edit Xiaomi EU AOD apk and try
Vatumb said:
Edit Xiaomi EU AOD apk and try
Click to expand...
Click to collapse
How to?
Can someone share the modified Xiaomi.eu-APK, so I can test it via ADB Sideload?
I asked xiaomi support and this is their response
We at Xiaomi value your trust and we apologize for the inconvenience. Rest assured that we'll assist you on this.
To ensure our users have smooth system operation and the best using experience on MIUI12, this feature/function is not supported due to SoC (System-on-a-Chip) and RAM.
However, we will record the case and forward it to our concerned authorities. Also, I would request you to submit your demand through Feedback & Suggestion (Settings >> Feedback & Suggestion), and wait for the future update.
but this limiti is only with miui or with aosp too ?
aleMarvel said:
but this limiti is only with miui or with aosp too ?
Click to expand...
Click to collapse
only with miui, but on Xiaomi EU rom, you can set the AOD to always.
augustusk said:
only with miui, but on Xiaomi EU rom, you can set the AOD to always.
Click to expand...
Click to collapse
txxx is a good news for me... i always used aosp..
Or just use MMX lol.
Or disable miui optimization
zoOMito said:
Or disable miui optimization
Click to expand...
Click to collapse
not recommend. disabling miui optimization has side effects...
disable optimization create issue with 3 fingers screenshot for example...
or double tap to sleep in home

Unable to pass ctsProfile

Hello All,
My device was brick when I dirty flash the Lineage OS 20211003 to 20211110.
So the flash it back to stock Android 11 (Nov 2021 update) via fastboot, then flash Lineage OS 20211110 again.
And this time everything is fine except I can get the ctsProfile pass at 20211003, but failed this time.
I have try though the process at https://forum.xda-developers.com/t/tutorial-unlock-bootloader-get-root-and-valid-safetynet.4178673/
but no luck.
Magisk version is 23.0
Spoiler
{
"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 the modules I currently installed, tried riru - LSposed but it is not helping so I removed.
Spoiler
Any ideas I can fix the ctsProfile issue?
{Mod edit: Spoiler added for better reading & scrolling experience}
Is that build of LOS using a certified device fingerprint out of the box? Otherwise you need to apply one to pass CTS.
Didgeridoohan said:
Is that build of LOS using a certified device fingerprint out of the box? Otherwise you need to apply one to pass CTS.
Click to expand...
Click to collapse
Humm ... I'm not sure, may I ask how to check?
Ok, I installed MagiskHide Props Config, and got a string as following:
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
but I'm not sure it is certified or not
Arlik said:
Humm ... I'm not sure, may I ask how to check?
Ok, I installed MagiskHide Props Config, and got a string as following:
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
but I'm not sure it is certified or not
Click to expand...
Click to collapse
You mean that's the reported used fingerprint? Looks ok, but it's also possible that the ROM has a security patch date that doesn't match the print. Try applying a Pixel 5 print from the module and see if that helps.
Try to apply Pixel 5, 5a, 3a Android 11's fingerprint by pressing
f - Pick a certified fingerprint
After reboot, it still show
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
Did I do something wrong?
Just an update.
The issue should be relay to the November update of LOS
now I redo all my process with LOS 20211020 version, safetyNet has passed.
Arlik said:
Just an update.
The issue should be relay to the November update of LOS
now I redo all my process with LOS 20211020 version, safetyNet has passed.
Click to expand...
Click to collapse
All of a sudden, my SafetyNet is failing. I've tried these tricks posted online like Riru, Universal Safety Fix, etc. None of them work! I am on LOS 20211229. If the 20211020 version would work, I don't mind going back. Where can I download it? The official LOS site now has only the Dec 2021 version. I tried to Google for this older version but can't find it. Thank you

Question Board name, rosemary or secret?

I have Checked my "redmi note 10s" with AID64(https://play.google.com/store/apps/details?id=com.finalwire.aida64)
The board name appeared is "secret" but google search shows me I should have the board name as "rosemary"
Are those same or different?
{
"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"
}
Mdalmamun said:
I have Checked my "redmi note 10s" with AID64(https://play.google.com/store/apps/details?id=com.finalwire.aida64)
The board name appeared is "secret" but google search shows me I should have the board name as "rosemary"
Are those same or different?
Click to expand...
Click to collapse
Rosemary, Secret and Maltose all are SAME.
Rosemary is the device with NFC,
Secret is the device without NFC.
Maltose is for China Market.
shyam jamnagar said:
Maltose is for China Market.
Click to expand...
Click to collapse
I bought mine in LatinAmerica (Chile), and it turned out to be a maltose. I bought it through a mobile operator, so it is officially intended for this market. It's non-NFC as well.
BTW, the model in my case is listed as M2101K7BL (final 'L' instead of 'I')
Besides, it appears to me that the Note 10s has never been released in the China market, there is no Chinese ROM whatsoever (and that's why we don't have a xiaomi.eu ROM, if I'm not wrong)
Is there any rooting/modding/flashing method for secret?
Mdalmamun said:
Is there any rooting/modding/flashing method for secret?
Click to expand...
Click to collapse
Look, Rosemary and Secret are just as written above. Normally Xiaomi uses the same name, but for some reason they changed the board name this time. Just no NFC. I also use Secret and you just need to root it with classic Magisk.
Would u plz guide me as i can't manage to have twrp for this hence no root option is in my mind.
Turbodr said:
Look, Rosemary and Secret are just as written above. Normally Xiaomi uses the same name, but for some reason they changed the board name this time. Just no NFC. I also use Secret and you just need to root it with classic Magisk.
Click to expand...
Click to collapse
Would u plz guide me as i can't manage to have twrp for this hence no root option is in my mind.
So can I use rosemary rom files in the device with codename secret??
Dipanjan6291 said:
So can I use rosemary rom files in the device with codename secret??
Click to expand...
Click to collapse
from what I've gathered yes you can you will just not have NFC functionality, but you don't have NFC anyway so no loss there.
Cryptonite26 said:
from what I've gathered yes you can you will just not have NFC functionality, but you don't have NFC anyway so no loss there.
Click to expand...
Click to collapse
Ok bro thanks... That means I can flash rosemary fastboot rom in secret also... No issues will be there..
shyam jamnagar said:
Rosemary, Secret and Maltose all are SAME.
Rosemary is the device with NFC,
Secret is the device without NFC.
Maltose is for China Market.
Click to expand...
Click to collapse
thanks now i understand the different.

Categories

Resources