yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
Hi,

After installing numerous A13 custom roms and reading some posts on the XDA Poco F3 thread, i decided to see if i had the issue.

I installed stock eea V13.0.9.0.SKHEUXM rom and was presented with the "find device storage corrupted your device is unsafe now" Popup,

The FIX was to install TWRP Recovery, copy the STOCK persist.img from the Official EEA-V13.0.9.0.SKHEUXM rom and flash it via TWRP.

Fortunately Xiaomi also included the persist.img in the stock rom,

even though the persist.img is not installed when returning back to stock:unsure:,

i guess there Devs were aware of this issue.

I Reboot my F3, voila no more nag screen(y)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Pocouser1357:
I got play store unsertified after flashing persist on my poco f3. But I tried flashing China miui with bootloader lock and play store is certified now. But I have a global version of phone and this maybe cannot done with Indian version of phone
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
I have the same issue. Which china miui did you flash, and how did you do that with bootloader lock without bricking the device? Would you mind telling us steps correctly to help us?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Pocouser1357:
I have installed china rom 13.0.6.0 through fastboot using option clean all and lock. My phone didn't brick because china miui can be installed with bootloader lock on global or china version of phone, but not on indian
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Dadovvv:
This is the first time i ever heard that china rom can be flashed on global device with options to lock bl without brick.

U guys need to doublecheck this statement before trying to do that.

yes, every xiaomi device have persist backup img file in system, named persistbak.img.

and its how we on poco f2 pro fix problem with widevine L3 problems, by flashing persistbak as persist.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] airb05:
Yeah But still after fixing the problem with persist by flashing the persist.img from fastboot/recovery rom, we will end with Google uncertified and there is still no solution for that that is the main problem right now
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Dadovvv:
Yes, and now im pretty sure there is no fix for that other then using root and safety net fix or some custom rom.

After some research i found out that all keys used for certification is stored in hardware-backed storage which is impossible to manipulate with, once keys are in a hardware-backed even the OS kernel cannot access this key. So only way is to use safety net fix which spoof evaluation type from "hardware-backed" to "basic".

Maybe xiaomi can fix that issue in future update, but i really doubt since they can't fix some basic bugs for years, I even don't think they have enough developers compared how many devices they produce.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
My device is global too, but would you please confirm using this method without bricking the device?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Pocouser1357:
Ok, this is the video
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
Thank you so much for this video. I see your device as a k40 not global poco f3 which is surprising indeed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Pocouser1357:
It is as k40 because I flashed china ROM, but you can see that is a global device because when it starts the logo is from poco
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
I noticed that, which surprised me.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] moinkhan0137:
Have you found any solution till now?

I have the same problem.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
try this way:

I have installed china rom 13.0.6.0 through fastboot using option clean all and lock. My phone didn't brick because china miui can be installed with bootloader lock on global or china version of phone, but not on indian.

It is in post 44.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] edixon2021:
Writing by google translator:

I also have that problem of non-certified device because I tried to go to the Global Rom (the stock is global Turkey) and after a number of surprising errors with the global rom I decided to go back to the stock and I found that non-certified device, but with magisk and safetynet I was able to get apps like Netflix to appear on the play store.

But it still keeps that "device not certified" section in the play store settings, I hope someone in the future can solve that problem.

Just follow the steps in this post and try if it works for you, in my case only the apps that can only have certified devices appear, but it continues as an uncertified device.

https://xdaforums.com/t/how-to-pass...-protect-certified-on-any-custom-rom.4459057/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Franssen:
I have the same issue with persist and device not certified anymore.

Will a edl flash with stock rom maybe work to fix this issue ? Someone tried this already ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
Hi,

There is a Simple FIX,

"DO NOT GO DOWN THE EDL ROUTE"

Download the original Rom for your F3 Version, (i have the Global/EU version) with "EEA" stock firmware.

1. Unzip the stock rom and open the Images folder, locate and copy the "persist.img" file into a safe place, i use a OTG adaptor and a 64GB USB Memory Stick.

2. Download and install Recovery, if you don`t have recovery, you can use Temporary recovery (i would recommend twrp), look at the bottom of this post.

3. Copy the persist.img into ether the F3 internal memory or a usb stick with OTG,

Start TWRP Recovery, (when using a OTG adaptor, wait 5 seconds before plugging in the Adaptor and then choose "MOUNT", scroll to the bottom of the menu and choose USB-OTG).

4. Locate the "Stock" persist.img and tap on INSTALL IMAGE and select "persist.img", from the "Select partition to flash image" menu, select "persist".

5. at the bottom of the page choose "Swipe to confirm flash".

6. Job done, restart your phone, that's it, SIMPLE (ISH)

If you need temporary root you could use this simple program here,

https://xdaforums.com/t/rom-official-13-statixos-v6-1-alioth-aliothin.4549639/post-88115607

Using a PC start your F3 in FASTBOOT MODE,

I hope this helps.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Franssen:
This won't fix the device not certified anymore after flashing persist file.

It will solve the find my device corrupt error.

But after device will not be certified anymore on locked bootloader and no fix for this now.

That's why I asked someone already tried edl flash or not
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
Hi,

Have you read this post:unsure:

https://xdaforums.com/t/device-is-not-certified.4292469/post-85189597

I have not come across this issue, but then i don`t intend to revert back to stock and relock my bootloader in the near future.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ISaidMe0w:
Yes. I've also touched persist partition and now safety net doesn't pass even with locked bootloader. Guess it's unfixable.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
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?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 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,
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
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
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
Can service center repair this persist? Also yes I have already installed magisk for safety net and play integrity pass
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
Can tee be restored?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
No, only motherboard replacement at an authorized service or a new phone.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
Shame, Xiaomi is really trying to kill devices, first it was the front camera and now persist partition with miui 14.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
If you have an active warranty then return the phone and get your money back.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
If you did sell it then wouldn't the next person have cts and integrity issue?.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] duckyduck!:
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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
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.

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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 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.:unsure:

I have no more to say on this matter.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
I have tried this and I can say that this does not work.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 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.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CRNO:
Johnr64 my friend maybe u missed thing from information uvzen, he right... bcs when u flash the pressist file with twrp that will break ur CTS for ever and thats what mean ? that mean when u try to back in fw miui rom u cant install some app in playstore like "netflix" and some app pay with banking will dont work with u anymore yes it is unfortunately that what hapened with me too when i tryed to sloving that stupid problem of "find device storage corrupted"
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
A year ago I had this problem too, that my CTS would fail and MIUI would show "Find My Storage corrupted" or something.

This week I flashed Stock MIUI 14 and locked bootloader (just to test and see), and it's all good now!

I have no idea what fixed it.

Anyway I'm back to ArrowOS

Edit: I had flashed ArrowOS 11 and Xiaomi.eu in the previous year. Idk if this is helpful to mention. I also flashed Firmware a bunch of times while on ArrowOS. v12.5, v13 and v14 firmware. EEA and Global of those.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] flekkelek:
If you have to flash stock persist.img you are screwed anyways in terms of netflix for example. Better to restore persist.bak then you will have a little chance to get back everything right again.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] hamzahashim011:
Hi Brother

Let me explain you

The thing you are mentioning "find device storage corrupted" can be solved via reflashing persist,

But It will cause more worse conditions it will make CTS profile fail on stock even with locked bootloader

You will not face any issue on custom or on EU rom But this is the real issue

A safe way to Fix "find device storage corrupted" is just to flash any Android 12 Custom Rom

and then you can flash any new rom or stock rom

Hope this will help
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] antony_0_3_4:
Is CTS problem solved?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Yes.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Saitama09:
I have redmi note 10 pro and i installed a custom ROM on it but then i wanted to use MIUI but when i locked bootloader i got device memory corrupted issue which someone suggested me to fix by flashing persist img and i did that but another problem arise that was the failure to pass cts by default.

Even in locked bootloader the cts profile is failing

I have tried flashing rom via recovery and fastboot so many times but still it doesn't workView attachment 5955235
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Saitama09:
bro i have the same issue , I have redmi note 10 pro ....

Even in locked bootloader the cts profile is failing

I have tried flashing rom via recovery and fastboot so many times but still it doesn't work
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Saitama09:
i have the same issue bro , did you find any solutions other than root
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
The only fix for this is to install Safetynet fix module in magisk. But make sure you install one that supports zygisk, the latest one on github for some reason supports only riru for me.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Saitama09:
So I have to use magisk ? There is no other way ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
There is no other way. At least as far as I know.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Saitama09:
well for now on locked bootloader gpay is working but I don't know for how long
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Bullet Saloon:
I have a Moto G 5G 2023 (XT2313-6). Bootloader unlocked and rooted with Magisk 26.1 ( hidden, with Google Play, Google Framework, and Netflix checked in deny list). Required modules installed.

Phone passes Google ATI and CTS Match.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] FrostY17:
is it still working?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ISaidMe0w:
few months ago i modified persist partition in my poco f3 and it caused cts profile failure. i decided to request a warranty fix because it had not expired yet back then. they have replaced a mobo and now i've obtained a new fresh warranty for another 2 years. win win
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Techno_Physics:
Can I install someone else's persist backup and fix CTS fail bcz I didn't backed mine

Someone help me out and help me pass safety net ALIOTH
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
If your bootloader is unlocked, just install (F3-NoGravityKernel-1.5.0-HotFix or BaalamKernel-6.0-ksu-ALIOTH) from twrp.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Techno_Physics:
Will it going to fix CTS in my alioth? Can I lock bootloader After flashing No gravity kernal?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] usmanjavid:
Just flash latest fastboot rom if you are on global use global by miflash tool
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Techno_Physics:
Did, but still not CTS certified! WHAT DO I DO?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
Flashing persist from another alioth device won't work, your device is permanently damaged. If you care so much about safetynet pass on a locked bootloader, replace motherboard or return the device under warranty if you have it. And if it doesn't bother you, just flash a custom rom and continue using Alioth.

Nonsense

No

Nonsense
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
Did you try installing (F3-NoGravityKernel-1.5.0-HotFix or BaalamKernel-6.0-ksu-ALIOTH) and yet cts issue in your device, or just bluffing? try at first before writing your nonsense response.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
Please explain to me, "Mr. Genius", how a custom kernel is supposed to repair a permanently damaged CTS? Do you really know what the problem is in this thread, or does reading comprehension hurt? Those who mindlessly flashed persist.img have their TEE (Trusted Execution Environment) permanently damaged and will never successfully pass safetynet without magisk modules or a custom rom with passed safetynet out of the box. Flashing a custom kernel won't help, so don't spread nonsense.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
Your answer means you did not install any kernelsu to fix cts issue. so, why you talk in vain like you're in a battle, 'champ"?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] uvzen:
Your answer means that reading comprehension is a big obstacle for you. I have and use KernelSU, but it DOES NOT SOLVE the main problem in this thread.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Techno_Physics:
Yes, even after installing BAALAM 6.0 KSY it wasn't passing safety net
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mogamycool:
just install KernelSU apk, ans see the result.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] NoirBird:
Probably too late but if your device is rooted with magisk you may use "MagiskHide Props Config" module which allows to spoof fingerprints of ur device so it pass cts. It was the only way i could use google pay.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ankur Mish:
I also had the same problem . cts is still failing for me but i got a solution to fix this find device storage corrupt problem.

Before flashing stock rom from mi flash, I just formatted data from twrp and then did pre installation wipe ( like wipe data, cache, system) and then flashed stock ROM through mi flash , it solved the corrupt storage problem.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] zaki789:
I had the find device storage corrupt problem and like a stupid person I flashed the persis.img file and I thought the problem is gone but i lost CTS in google play and am regretting my stupidity
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
Hi,

i just looked back at what i did 13 months ago:

Nov 5, 2022

Summary guide:

1. Download the fastboot ROM and extract the "persist.img" image for your installed version of Miui.

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

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

4. Restart the device, it should work fine.

When you install a Miui Stock rom is doesn't replace the installed persist.img, even though it is present in the Fastboot Firmware, i guess its there just in case owners have problems.

if you haven`t got TWRP installed on your device, you could always try my "Temporary Recovery" Program found in the HOW TO GUIDE.

TEMPORARY RECOVERY "TWRP 3.7.1_12-v8.6_A14-alioth-skkk + OrangeFox-alioth-stable@R11.1_5_1" (Updated 22-04-2024) & More

Hi All, I would like to start by saying say a BIG Thank You to DarthJabba9, Sa Gar and RoXoR for supporting this project:cool:. I`m a prolific Custom Rom installer on my F3, i am maybe up to 60+ roms in the last two years. Over time i...

xdaforums.com

After your all sorted i would suggest to switch to MATRIXX A14(y)(y)(y)

https://sourceforge.net/projects/pr...0-Official-alioth-Gapps-20231210.zip/download

IT IS THE BEST A14 ROM I HAVE EVER TRIED

All my banking apps work fine including Google wallet,

I hope you sort it:)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jefffrom:
I tried that Matrixx rom and it is a good rom and has dolby one of A14 roms I think that have it , battery not as good as CRDROID A14 in my opinion and thats the one I'm back on I think it's smoother and more stable and Ray pops out updates faster than anyone else