As far as I can understand the redmi boot screen is only cosmetic. I have been running this rom since November on my mi10t pro and have had an excellent experience so far.Well, that was a bummer. Tried to bring my new Mi 10T Pro onto Xiaomi.EU.
Not only did the install not work, it also showed "Redmi" in boot screen. Now it has messed up my folder structure, so I can't install ANY Roms anymore.
That was very disappointing. I think the first time i had that issue with Xiaomi.EU. But I reckon I shall fastboot install the original Xiaomi ROM and keep my fingers off this.
Good luck for everyone else!
fastboot boot <new file>.img
As far as I can understand the redmi boot screen is only cosmetic. I have been running this rom since November on my mi10t pro and have had an excellent experience so far.
I can say that it is the only rom that works so well, and I have tried crdroid , lineage and fluid
You do realize that it's the first time we're hearing anything of this sort?Not only does it not install, it has also essentially bricked my device by setting the antirollback counter to 1 - the official global versions are at 0.
So I can put this phone on a shelf now until the official Global ROM moves up to 12.5
I have to say, that is pretty unbecoming. My experience is thus not as good as yours.
It never does any harm in tidying up before installing a new ROM. So 'Yes' - wiping the Dalvik and cache is recommended, as well as deleting theNoob question here, is recommended to wipe cache and dalvik on every update? If yes, is needed too when flashing magisk?
fixed problem with beta roms.fastboot boot <new file>.img
shows me only 1-st screen with hellenic rabbit and some red lines. Then autoreboot to system.
I'm using your previous one (3.5.A10) for a month already.
clean 21.2.3 -> dirty 21.2.24 -> dirty 21.3.3
clean 21.3.11 -> dirty 21.3.17
I guess it would work if installed, because i've got such report from 4pda.ru user. But i prefer not to install twrp, just boot.
Fixed. Confirming. Working now. Thanks.