MIUI 13 22.7.21


Status
Not open for further replies.
But what I don't understand is that it's only in the Chinese rom the widgets are there! And that the xiaomi.eu rom is taken from the chinese rom! That's why I asked the question here.
So what? Some of the MIUI apps we use are Global variants because the Chinese ones are not suitable for Global users and have poor integration with Google services. The Global app was not updated for a long time despite these widgets being advertised and even referenced in Global App vault server. If you expect 1:1 copycat of China ROM, better use China ROM.
 
this error comes for me only when I use the Updater App and choose boot to recovery.
if I boot twrp manually it works as it should

so reboot into recovery again, and try again.
My solution was to install another recovery and have it recognize the pin to decrypt data.

 
I solved my earlier problems with Google Assistant crashing after the rebuilt ROM.

I cleared all the user data (not just cache) for the Google app, rebooted, and set that up again. As mentioned, the two assistant app appearances were a red herring and had nothing to do with the solution.
 
I solved my earlier problems with Google Assistant crashing after the rebuilt ROM.

I cleared all the user data (not just cache) for the Google app, rebooted, and set that up again. As mentioned, the two assistant app appearances were a red herring and had nothing to do with the solution.
The two apps with the same name you're referring to were always there, both are responsible for Voice Match communication with the device's hardware.
 
heck
 

Attachments

  • Screenshot_2022-07-25-21-58-22-079_com.atari.mobile.rctclassic-edit.jpg
    Screenshot_2022-07-25-21-58-22-079_com.atari.mobile.rctclassic-edit.jpg
    2 MB · Views: 229
I've been doing no updates for a while, so I might have to do some extra work. Maybe someone can help me out.

My situation:
Mi 10 Pro, currently on Xiaomi.eu rom (12.6 - 21.10.20 Beta) and Android 11
TWRP installed (although not the latest version)

Should I update to the latest TWRP via fastboot first, and should I Wipe data before being able to flash the latest development rom?
and should the rom also be installed via fastboot? or can I just download the zip and use TWRP?
 
I solved my earlier problems with Google Assistant crashing after the rebuilt ROM.

I cleared all the user data (not just cache) for the Google app, rebooted, and set that up again. As mentioned, the two assistant app appearances were a red herring and had nothing to do with the solution.
Does this permanently solve the Google Assistant Problem? In my case it stops working after a while (starting Google Assistant from search bar icon in launcher fails).
 
… Should I update to the latest TWRP via fastboot first, and should I Wipe data before being able to flash the latest development rom?
and should the rom also be installed via fastboot? or can I just download the zip and use TWRP?
FORMAT DATA is needed when you switch weekly to stable and vice versa.
Check the filename of the ROM you want to install, there is the answer.
For A12 ROM an A12 recovery is a must.
 
FORMAT DATA is needed when you switch weekly to stable and vice versa.
Check the filename of the ROM you want to install, there is the answer.
For A12 ROM an A12 recovery is a must.
Thank you. well. its weekly miui 12.6 to weekly miui 13. I Expect having to format the data as well then?
 
Hi, in installed the Rom just on my Xiaomi 12x via TWRP but now it boots everytime back in twrp whats wrong?
 
Thank you. well. its weekly miui 12.6 to weekly miui 13. I Expect having to format the data as well then?
Regarding format data on Alioth, is it prudent to format both slots since there is old data on the one not in use and then what is the procedure to format one or both slots before flashing a new rom?
 
Regarding format data on Alioth, is it prudent to format both slots since there is old data on the one not in use and then what is the procedure to format one or both slots before flashing a new rom?
Data is not duplicated across the two slots. Imagine otherwise, when slot A would be active and you install an app or set something, later when you switch to the slot B, all that would be 'lost',' you would see something else you had installed/set previously maybe a month or two ago, when slot B was active last time

Only system partitions are duplicated to the slots A and B. Data partition (with user apps and settings) and Internal memory (with your documents, photos, etc) are not. When you Format Data from TWRP, it formats that single and unique Data partition
 
Last edited:
  • Like
Reactions: trustkill
Data is not be duplicated to the two slots. Imagine otherwise, when slot A would be active and you install an app or set something, later when you switch to slot B, that would be 'lost',' you would see something else you previously installed/set maybe a month or two ago, when slot B was last time active

Only system partitions are duplicated to the slots A and B. Data partition (with user apps and settings) and Internal memory (with your documents, photos, etc) are not duplicated. There is only one/unique Data partition, no matter if currently slot A or B is active. When you Format Data from TWRP, it formats that one and unique Data partition
Thank you for the explanation.
 
Thank you for the explanation.
Just a short continuation. A/B is not about redundancy (like Raid disks on servers) but about seamless OTA upgrades

While you work from say, active slot B, phone gets notification and starts downloading OTA (I'm talking about stock OTA!).
Once downloaded, it immediately continues by installing to the currently inactive slot A. Your usage from slot B is not affected

When the inactive slot is updated, phone reboots and now you don't need to "Wait while installing the the upgrade"

Phone immediately reboots to the already updated system in slot A, you continue to use and phone again, in background updates the now, currently inactive slot B
 
Just a short continuation. A/B is not about redundancy (like Raid disks on servers) but about seamless OTA upgrades

While you work from say, active slot B, phone gets notification and starts downloading OTA (I'm talking about stock OTA!).
Once downloaded, it immediately continues by installing to the currently inactive slot A. Your usage from slot B is not affected

When the inactive slot is updated, phone reboots and now you don't need to "Wait while installing the the upgrade"

Phone immediately reboots to the already updated system in slot A, you continue to use and phone again, in background updates the now, currently inactive slot B
very advance

double copy update
 
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.3.4
Replies
150
Views
42K
  • Locked
HyperOS 1.0 24.2.26
Replies
161
Views
49K
  • Locked
HyperOS 1.0 24.1.29
Replies
227
Views
120K