[Safety Pass] Fix ctsProfile is false

Search This thread

Whyle

Senior Member
Mar 10, 2017
132
127
Italy
Code:
ro.product.model=M2007J3SG
ro.product.system.model=qssi system image for arm64
ro.product.vendor.model=M2007J3SG
ro.product.product.model=qssi system image for arm64
ro.product.product.model=qssi system image for arm64
ro.product.odm.model=M2007J3SG

I changed these value to Pass safety test, maybe this is useful for someone.

Fixing:
- ctsProfile to true
- evalType to Basic
- show correct Device name in some app

Working on:
- Xiaomi 10T
- Xiaomi 10T Pro
- Redmi K30S Ultra

Install:
- as Magisk Module

Donation:



Discussion:

View attachment 5130935
 

Attachments

  • Mi10TPRO_SafetyPass.zip
    2.6 KB · Views: 832
  • RedmiK30SUltra_SafetyPass.zip
    2.7 KB · Views: 330
Last edited:

NOSTALGIA

Retired Forum Moderator
Jan 11, 2012
3,706
1,633
Cebu
Code:
ro.product.model=M2007J3SG
ro.product.system.model=qssi system image for arm64
ro.product.vendor.model=M2007J3SG
ro.product.product.model=qssi system image for arm64
ro.product.product.model=qssi system image for arm64
ro.product.odm.model=M2007J3SG

I changed these value to pass safety test, maybe this is useful for someone

View attachment 5130935

Install: with magisk


did you try any banking app ? coz if banking apps work and magisk hide is working then im rooting my 10t pro
 

OliwierGL

New member
Nov 7, 2020
3
1
Second Way :)

If Magisk module doesn't work in this case (On my Mi 10T it doesn't work) you can try this:
1. Install MagiskHide Props Config.
2. Start Termux and type "su" and hit enter , after this termux ask Magisk Manager to prompt for root access => Grant it
3. Type "props" command and hit enter
4. After MagiskHide Props loaded successfully, type "1" to edit device fingerprint
5. Type "f" to pick a certified fingerprint
6. Type "25" to choose "Redmi"
7. Type "3" to choose "Redmi K30 Ultra (10)"
8. Type "y" to confirm it
9. Type "y" to reboot your device

In my case that works :D
 
  • Like
Reactions: Manuel Lobos

Whyle

Senior Member
Mar 10, 2017
132
127
Italy
If Magisk module doesn't work in this case (On my Mi 10T it doesn't work) you can try this:
1. Install MagiskHide Props Config.
2. Start Termux and type "su" and hit enter , after this termux ask Magisk Manager to prompt for root access => Grant it
3. Type "props" command and hit enter
4. After MagiskHide Props loaded successfully, type "1" to edit device fingerprint
5. Type "f" to pick a certified fingerprint
6. Type "25" to choose "Redmi"
7. Type "3" to choose "Redmi K30 Ultra (10)"
8. Type "y" to confirm it
9. Type "y" to reboot your device

In my case that works :D

The method is similar, but Redmi K30 Ultra isn't Redmi K30S Ultra?
 
O

OliwierGL

Guest
The method is similar, but Redmi K30 Ultra isn't Redmi K30S Ultra

But works :D
124028841-844842132924988-2365622267682349289-n.jpg
 

d3smond

Senior Member
Aug 8, 2020
67
19
Second Way :)

If Magisk module doesn't work in this case (On my Mi 10T it doesn't work) you can try this:
1. Install MagiskHide Props Config.
2. Start Termux and type "su" and hit enter , after this termux ask Magisk Manager to prompt for root access => Grant it
3. Type "props" command and hit enter
4. After MagiskHide Props loaded successfully, type "1" to edit device fingerprint
5. Type "f" to pick a certified fingerprint
6. Type "25" to choose "Redmi"
7. Type "3" to choose "Redmi K30 Ultra (10)"
8. Type "y" to confirm it
9. Type "y" to reboot your device

In my case that works :D

Didn't work for me either on Lineage OS.
Works fine with your instructions but for Mi10T Pro select 30 and 23.
 
Last edited:
D

Deleted member 2582513

Guest
Didn't work for me either on Lineage OS.
Works fine with your instructions but for Mi10T Pro select 30 and 23.

Do you mean to say that if you use 30 and 23 it works on lineage OS? Or it doesn't work for you at all on Lineage? Has anyone got Lineage to work?
 
D

Deleted member 2582513

Guest
Ah ok. I managed to get it working with google services/lineage using your instructions, thanks! I've also tried with microg and it doesn't work but that might be microg's problem.
 

crosskyo

New member
Sep 21, 2015
2
0
using Lineage OS 17.1 latest version..
i've try both method but still false in cts profile.. please help me.. Thank you
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Code:
    ro.product.model=M2007J3SG
    ro.product.system.model=qssi system image for arm64
    ro.product.vendor.model=M2007J3SG
    ro.product.product.model=qssi system image for arm64
    ro.product.product.model=qssi system image for arm64
    ro.product.odm.model=M2007J3SG

    I changed these value to Pass safety test, maybe this is useful for someone.

    Fixing:
    - ctsProfile to true
    - evalType to Basic
    - show correct Device name in some app

    Working on:
    - Xiaomi 10T
    - Xiaomi 10T Pro
    - Redmi K30S Ultra

    Install:
    - as Magisk Module

    Donation:



    Discussion:

    View attachment 5130935
    4
    This was taken from MI 10T telegram group. Should work on all android versions from android 8 up to android 11. I've installed it and it fixes ctsprofile and safetynet passes now. But it breaks amazon prime hd playback, so if you have fyrplays safetynet fix leave it enabled.
    1
    Second Way :)

    If Magisk module doesn't work in this case (On my Mi 10T it doesn't work) you can try this:
    1. Install MagiskHide Props Config.
    2. Start Termux and type "su" and hit enter , after this termux ask Magisk Manager to prompt for root access => Grant it
    3. Type "props" command and hit enter
    4. After MagiskHide Props loaded successfully, type "1" to edit device fingerprint
    5. Type "f" to pick a certified fingerprint
    6. Type "25" to choose "Redmi"
    7. Type "3" to choose "Redmi K30 Ultra (10)"
    8. Type "y" to confirm it
    9. Type "y" to reboot your device

    In my case that works :D
    1
    Could everyone double check, this doesn't seem to work anymore, as I've read on several telegram groups. Ctsprofile fails...
    It doesn't work for me either
    1
    Google made an update that caused this, there is a fix but I haven't tried it