Question CTS doesn't pass even with locked bootloader.

[johnr64]

Yes. I've also touched persist partition and now safety net doesn't pass even with locked bootloader. Guess it's unfixable.

Unlock your bootloader, Install temporary TWRP using my updated Temporary Recovery
download the correct stock firmware for your phone, unzip the firmware copy over the new persist.img and replace your old version using TRWP, as post 57 above.

 

[duckyduck!]

Unlock your bootloader, Install temporary TWRP using my updated Temporary Recovery
download the correct stock firmware for your phone, unzip the firmware copy over the new persist.img and replace your old version using TRWP, as post 57 above.

hey, i have redmi note 10 pro and after miui 14 update sensors went bad,cts profile was passing and device certified, tried hard reset many times to get the sensors working but they did not. i then unlocked bl and backed original persist and restored it from persistbk partition, sensors started working but cts profile fails on locked bootloader. i tried restoring original persist but that did not work. any idea or help?

 

[johnr64]

Sorry,
I can only help on a Poco F3, I used the Original Persist file from a stock Miui Rom and used TWRP to overwrite the corrupted version, it worked on my F3, have you tried a older/newer versions of a persists file,

I hope you sort it,

 

[user0u]

hey, i have redmi note 10 pro and after miui 14 update sensors went bad,cts profile was...

The only way to fix this is to install safetynet fix module in magisk.
Force stop play store, uninstall updates. Do the same for play services, install safetynet module, reboot.

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com

 

[duckyduck!]

The only way to fix this is to install safetynet fix module in magisk.
Force stop play store, uninstall updates. Do the same for play services, install safetynet module, reboot.

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com

Can service center repair this persist? Also yes I have already installed magisk for safety net and play integrity pass

 

[johnr64]

Can service center repair this persist? Also yes I have already installed magisk for safety net and play integrity pass

Hi Duckyduck,
Have you tried a Xiaomi.eu rom and see if the persists issue is still present, on my F3 i found installing .EU rom stopped the pop up, before i found the persist.img Fix.

How i Fixed my Persist issue.

Install guide:
1. Download the correct fastboot ROM for your device and extract the stock "persist.img" image.

2. Put persist.img into your device's internal memory or OTG USB Storage and open TWRP Recovery.

3. In TWRP, go to: Install> select install image> select file "persist.img"> select "Persist" partition

4. Restart the device.

 

[uvzen]

If you want to permanently corrupt the TEE (Trusted Execution Environment) on your device, go ahead and use this crappy tutorial from @johnr64 which tells you to flash the persist.img image. You will have broken hardware attestation and then there will be problems on stock ROM with locked bootloader when in future google will shut down safetynet servers and replace it completely with Play Integrity which checks your hardware attestation. At the moment the solution is a custom rom that passes safetynet or Universal SafetyNet Fix magisk module by kdrag0n which "tricks" Play Integrity into thinking that the device is not capable of hardware backed attestation, which will force a fallback to basic attestation. More details on how this magisk module works can be found here.

Edit:
If you have a problem with the message "find device storage corrupted", then don't flash persist.img image. Just don't touch it. If you haven't flashed persist.img then I've seen information on various telegram channels that flashing AOSP custom rom with android 12 and using it for 10 minutes then flashing stock MIUI can fix this problem. How much truth is in this, I don't know, because I no longer have Poco F3. I returned it under warranty, got my money back and bought another phone.

 

[duckyduck!]

If you want to permanently corrupt the TEE (Trusted Execution Environment) on your device, go ahead and use this crappy tutorial from @johnr64 which tells you to flash the persist.img image. You will have broken hardware attestation and then there will be problems on stock ROM with locked bootloader when in future google will shut down safetynet servers and replace it completely with Play Integrity which checks your hardware attestation. At the moment the solution is a custom rom that passes safetynet or Universal SafetyNet Fix magisk module by kdrag0n which "tricks" Play Integrity into thinking that the device is not capable of hardware backed attestation, which will force a fallback to basic attestation. More details on how this magisk module works can be found here.

Can tee be restored?

 

[uvzen]

Can tee be restored?

No, only motherboard replacement at an authorized service or a new phone.

 

[duckyduck!]

No, only motherboard replacement at an authorized service or a new phone.

Shame, Xiaomi is really trying to kill devices, first it was the front camera and now persist partition with miui 14.

 

[uvzen]

Shame, Xiaomi is really trying to kill devices, first it was the front camera and now persist partition with miui 14.

It's not Xiaomi's fault, but Google's decision that new devices that have been produced since 2020 must support hardware attestation. You can find more information about it here.

 

[duckyduck!]

It's not Xiaomi's fault, but Google's decision that new devices that have been produced since 2020 must support hardware attestation. You can find more information about it here.

I am not talking about google decision, I am talking how Xiaomi killed persist partition on my rn10pro with miui 14, before this front cameras were dying with updates.

 

[uvzen]

I am not talking about google decision, I am talking how Xiaomi killed persist partition on my rn10pro with miui 14, before this front cameras were dying with updates.

If you have an active warranty then return the phone and get your money back.

 

[johnr64]

If you want to permanently corrupt the TEE (Trusted Execution Environment) on your device, go ahead and use this crappy tutorial from @johnr64 which tells you to flash the persist.img image. You will have broken hardware attestation and then there will be problems on stock ROM with locked bootloader when in future google will shut down safetynet servers and replace it completely with Play Integrity which checks your hardware attestation. At the moment the solution is a custom rom that passes safetynet or Universal SafetyNet Fix magisk module by kdrag0n which "tricks" Play Integrity into thinking that the device is not capable of hardware backed attestation, which will force a fallback to basic attestation. More details on how this magisk module works can be found here.

Edit:
If you have a problem with the message "find device storage corrupted", then don't flash persist.img image. Just don't touch it. If you haven't flashed persist.img then I've seen information on various telegram channels that flashing AOSP custom rom with android 12 and using it for 10 minutes then flashing stock MIUI can fix this problem. How much truth is in this, I don't know, because I no longer have Poco F3. I returned it under warranty, got my money back and bought another phone.

Hi,
My Crappy tutorial fixed my F3 "find device storage corrupted" issue, i have no intension to return back to stock unless i sell my F3, i did explain that this worked on my F3 and the advice was base on a Poco F3 only, as you know "All the advice given on XDA" is used at your own risk,
i hope duckyduck! finds a work around.

 

[duckyduck!]

Hi,
My Crappy tutorial fixed my F3 "find device storage corrupted" issue, i have no intension to return back to stock unless i sell my F3, i did explain that this worked on my F3 and the advice was base on a Poco F3 only, as you know "All the advice given on XDA" is used at your own risk,
i hope duckyduck! finds a work around.

If you did sell it then wouldn't the next person have cts and integrity issue?.

 

[duckyduck!]

If you have an active warranty then return the phone and get your money back.

Warranty ended last year in October. After that it started showing problems,like heating issues etc. But now after persist restore(original backup and restore process) phone isn't heating up anymore. Last nail in coffin was miui 14. But the phone is now working after persist fix and downgrade to miui 13.0.18 global.

 

[uvzen]

Hi,
My Crappy tutorial fixed my F3 "find device storage corrupted" issue, i have no intension to return back to stock unless i sell my F3, i did explain that this worked on my F3 and the advice was base on a Poco F3 only, as you know "All the advice given on XDA" is used at your own risk,
i hope duckyduck! finds a work around.

Nobody cares that you're not going back to stock MIUI, nobody asked. The xda-developers forum is there to help users, not to lead them into an even worse swamp. Any risk should be minimized to the minimum extent so that no one suffers, but you spreading this crappy tutorial of yours only increases the risk. Find another job and stop spreading this harmful content.

If you did sell it then wouldn't the next person have cts and integrity issue?.

I don't know if there will be a buyer who will buy a phone from him that will have a damaged CTS profile and will not be able to pay with banking applications if he would like to stay on stock MIUI and not play with custom roms and magisk. Well, unless he lies to the buyer and disappears with the money.

 

[johnr64]

Hi,
As i explained this "FIXED MY ISSUE", i read a post on the Evo-X thread regarding "find device storage corrupted" issue when returning back to stock Miui Firmware, i decided to return back to stock to see if i was affected by the issue and the answer was "YES".
I did some research on xda, as you do and came across the fix.
I used the instructions i posted and applied the FIX and the "nag screen" disappeared.
I remember installing a Xiaomi.eu fastboot rom first and then Stock Miui Firmware, all was good and i returned back to the amazing Evo-X Rom,

I have no intension to sell my F3, also in the UK, i got 24 Months warranty that runs out on the 11-2023.


i hope to find a work around.

I have no more to say on this matter.

 

[user0u]

I've seen information on various telegram channels that flashing AOSP custom rom with android 12 and using it for 10 minutes then flashing stock MIUI can fix this problem. How much truth is in this, I don't know,

I have tried this and I can say that this does not work.

 

[nabecite]

another confirmation that safetynet passes on the chinese rom with a locked bootloader. It does not resolve the issue. Instead it seems like it falls back to basic attestation akin to a custom rom. Google services work surprisingly well with minimal effort.

Switched back to xiaomi eu because I cannot figure out how to get android auto working on chinese phones.