MiBoi9000
Members
- 27 May 2021
- 126
- 40
I am still on 8.31 because performance is good. What build you run?Was it okay on the previous build?
I haven't updated yet but the previous build on Mi 11 was the best performance ever.
I am still on 8.31 because performance is good. What build you run?Was it okay on the previous build?
I haven't updated yet but the previous build on Mi 11 was the best performance ever.
I thought Vanced project was dead? Ive been using Revanced.Does anyone managed to install Youtube Vanced on Mi 11?
I get the error attached. Searching the internet I found that it's a problem with SAI and MIUI optimisation. Since MIUI optimisation it's gone from xiaomi eu roms, I wonder if someone found a workaround for this issue.
Project is dead but the app works just fine.I thought Vanced project was dead? Ive been using Revanced.
It is probably a bug of the new version of the MIUI installer. Which is used for the first time in this ROM version.Does anyone managed to install Youtube Vanced on Mi 11?
I get the error attached. Searching the internet I found that it's a problem with SAI and MIUI optimisation. Since MIUI optimisation it's gone from xiaomi eu roms, I wonder if someone found a workaround for this issue.
Yes, it's related to the new MIUI package installer, but it's not a bug, just a new intended limitation placed by Xiaomi, but like I said, I already patched it.It is probably a bug of the new version of the MIUI installer. Which is used for the first time in this ROM version.
Will not allow installation of applications via Vanced Manager..
I had to use ROM 22.9.21 where there is an old version of the installer. This problem with Vanced manager does not exist there.
Supposedly, download was broken - try againPlease help me with this problem. I cant update. It says check md5 and install.
My device is REDMI 9TSupposedly, download was broken - try again
On go to page 1, post #1, find a link to the server and manually download the zip for your device and install per instructions in the post #1 (basically, reboot to TWRP and flash the downloaded zip)
Or wait till tomorrow, new Weekly is expected
And next time better provide more details like what is your device (might be an md5 missmatch with the zip for that device and only the other users with the same device will be aware of that to help you) and what is your current ROM version
I already tried to install it via TWRP but my internal storage is encrypted.Supposedly, download was broken - try again
On go to page 1, post #1, find a link to the server and manually download the zip for your device and install per instructions in the post #1 (basically, reboot to TWRP and flash the downloaded zip)
Or wait till tomorrow, new Weekly is expected
And next time better provide more details like what is your device (might be an md5 missmatch with the zip for that device and only the other users with the same device will be aware of that to help you) and what is your current ROM version
For me its working without any error. 12xSorry to ask again, but I like to know if Dolby Atmos is working for xiaomi 12x, because for me it's not
Thanks, might be the problem from going from stable to betaFor me its working without any error. 12xView attachment 44352
Problem found and fixed. It was cause by an other sound modThanks, might be the problem from going from stable to beta
On almost every page here there will be a similar question (for this or that device, doesn't matter) and then an answer with a link to the thread on Xiaomi.eu, about which TWRPs to use for particular devices, where to download them, how to install and use themI already tried to install it via TWRP but my internal storage is encrypted.
Roll back (Flash) the 22.9.28 again.Stupid me just installed 22.9.7 version (thinking its new version for October.....please no bad jokes...). Flashing worked, I was on 22.9.28 before.
Now when bootup is (not) complete, I cannot open any apps because it tells me to wait for bootup to complete, waiting does not change things.....ALso in recovery I cannot access because my PIn seems to be not valid (its the same I use for years). Any idea How I can resolve this? THANKS!
Yes, I have a suggestion, but it's up to you. When this happened to me, I took the latest Xiaomi.EU fastboot version and the latest recovery version (22.9.29), took all the internal files of the recovery (IMG) version that has the same name and replaced it in the fastboot version (vendor_boot, boot and all from the firmware-update folder). Then I installed the fastboot version. Right after you install, you can access recovery and you will decrypt the internal memory with your pin, normally. Then you will install the latest recovery version normally. Naturally, when you access TWRP you will have to put the latest recovery version in the device's internal memory. Did you understand? I did and it worked, but it's up to you. It sounds difficult, but it's actually super easy to do.Stupid me just installed 22.9.7 version (thinking its new version for October.....please no bad jokes...). Flashing worked, I was on 22.9.28 before.
Now when bootup is (not) complete, I cannot open any apps because it tells me to wait for bootup to complete, waiting does not change things.....ALso in recovery I cannot access because my PIn seems to be not valid (its the same I use for years). Any idea How I can resolve this? THANKS!
How to when I do not get into recovery? Fastboot? as described below by @Rodrigo N. Leles? Thanks for the feedbacks!Roll back (Flash) the 22.9.28 again.
There is a new vanced based on the old one. Vanced Extended.I thought Vanced project was dead? Ive been using Revanced.
You made a downgrade - you have to Format DataStupid me just installed 22.9.7 version (thinking its new version for October.....please no bad jokes...). Flashing worked, I was on 22.9.28 before.
Now when bootup is (not) complete, I cannot open any apps because it tells me to wait for bootup to complete, waiting does not change things.....ALso in recovery I cannot access because my PIn seems to be not valid (its the same I use for years). Any idea How I can resolve this? THANKS!
I did it and I didn't need do format data. But replace only the SAME IMG files, with the same names, like I said. And, when it boot, go to recovery, decrypt it with the pin, put the last zip recovery (22.9.29) in internal memory from PC, and install (flash) again. It worked for me.How to when I do not get into recovery? Fastboot? as described below by @Rodrigo N. Leles? Thanks for the feedbacks!
Downloading latest Fastboot (June 15th) and Recovery version (Sep 29th). Understood what you mean, but just to make sure. How do I get latest Recovery version into Device internal memory when I am in its Recovery? Can I copy from my PC while it is in Recovery?I did it and I didn't need do format data. But replace only the SAME IMG files, with the same names, like I said. And, when it boot, go to recovery, decrypt it with the pin, put the last zip recovery (22.9.29) in internal memory from PC, and install (flash) again. It worked for me.
Boot to Fastboot and temporarily flash TWRP:How do I get latest Recovery version into Device internal memory when I am in its Recovery?
When you flash in fastboot mode, with the new IMG files, you can access your data again, decrypting it, that's the point. After that, it's the ordinary way: plug it in your computer and copy latest ZIP recovery to its internal memory. Then flash it.Downloading latest Fastboot (June 15th) and Recovery version (Sep 29th). Understood what you mean, but just to make sure. How do I get latest Recovery version into Device internal memory when I am in its Recovery? Can I copy from my PC while it is in Recovery?
[Update] I guess I use ADB Sideload https://www.droidwin.com/transfer-install-files-twrp/#How_to_Use_the_ADB_Sideload_Feature
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation