You will need to clear all app data for "Camera" app, then flash your current ROM again (126.96.36.199 Stable) via TWRP.Hello,
yesterday I installed a Mi 9T Pro with the current ROM 11.0.8 and after installation I applied the K20 Pro / Mi 9T Pro patch. Since then I cannot open the camera settings anymore. We haven't changed to any custom theme. The app crashes every time with the following error message:
View attachment 28998
You will need to clear all app data for "Camera" app, then flash your current ROM again (188.8.131.52 Stable) via TWRP.
Finally, you can try my conversion patch (Warning: Use "Safe" version for 184.108.40.206+ Stable ROM version):
EDIT: Please feedback if it's working, thanks!
You can use "Actual" version, it has April, 2020 security patch date info and 220.127.116.11 Stable ROM has March, 2020.Thanks.
If I have Codered's patch installed on MIUI v11.0.5 Stable, and I am going to install v11.0.8 then I have to use the Safe version, correct?
If new Stable ROM get May, 2020 security patch date info ---> "Actual" patch (v20.4.x) will not work but you can use "Safe" patch without issue.But if I use Actual once then I can never use Safe thereafter (eg in case a future ROM release). I have to wait for the new Actual version. Is it true?
Why is fingerprint important? As I see this is the difference between Actual and Safe versions.
So on Stable I can usually use Actual.If new Stable ROM get May, 2020 security patch date info ---> "Actual" patch (v20.4.x) will not work but you can use "Safe" patch without issue.
To simplify: If "Actual" patch doesn't work, "Safe" patch will always work. (After re-flashing the new ROM if you flashed the non-working "Actual" version)
"Actual" version target weekly ROM because they have an old fingerprint build and security patch date info.
New "Universal" patch is available.Btw, thanks for working on and maintaining this patch, almost forgot to say
Will this work with miui 12? ThanksNew "Universal" patch is available.
Thank you Poney70, it was really fast!New "Universal" patch is available.
I think this patch is not for the security patch but it's fir ths boot logo/camera watermark/and device nameBtw, what advantage does it give to change fingerprint build & security patch date info other than xiaomi.eu team has given with their ROM?
If this patch does not actually install a new security patch but changes the info to a fake one then the users will think their security patch is up to date but it is not the case actually.
Hello and thanks for using my "Universal" conversion patch.I had the Codered universal version installed, and it works fine. However, I think the conversion patch is no longer needed now, as the xiaomi.eu has finally corrected the stuff themselves. I tried now to install 20.6.11, and indeed it starts up with the Mi logo instead of the Redmi logo. HOWEVER, it then reboots into TWRP instead of into the system. I think it is a problem of encryption. Only after I install the patch again I can boot into the system proper.
The question is now: How can I get rid of this dependence? If I don't need the patch anymore, I don't want to use it. How can I revert the patch before (or after, I don't mind) updating the system to 20.6.11, so that it the phone boots into system rather than back into TWRP?