MIUI 12.3 20.12.9/10


Do you like this MIUI version?

  • Total voters
    336
Status
Not open for further replies.
graw2 said:
Yes if you already have this TWRP recovery installed:
TWRP-3.4.2B-1206-XIAOMI10PRO-CN-wzsx150.img

If you don't have it then install ROM 20.12.10 and next time you won't have any issue booting to TWRP recovery in any way

Sent from my Mi 10 Pro using Tapatalk
Click to expand...

Hi,

I am new to the forum and I have a Xiaomi Mi10 pro with ROM 20.9.24 and recovery (TWRP) that works with that ROM. If I download this update directly, will I have a problem not to lose the data? I have tried the new TWRP but it does not recognize the internal memory of the device . Can you help me? Thank you very much for everything, you do a great job.

A greeting
 
Hi @Iain_B (again), so I've been going through your posts trying to figure out how to install the beta on my stock mi 10 (umi).
If I understood well I ~have to (after disabling any pin etc.):
1)Flash the old twrp with fastboot/adb https://androidfilehost.com/?fid=8889791610682877442 (for 20.11.5 version and before)
2)Flash with the recovery the 20.11.5 version (or for extra safety boot into recovery from fastboot/adb and flash the rom from there)
1)Flash through fastboot/adb the 3.4.0 (LittleTurtle2333) TWRP recovery
3)Boot (instead of flash) to TWRP-3.4.2B-1206-XIAOMI10-CN-wzsx150.zip, again through fastboot/adb
4)Format data and cache + davlink partition
5) Flash the latest beta (20.12.10 so far)
6)Boot again to the new twrp and delete cache + davlink partition
Done
 
Last edited:
Blastboom Strice said:
Hi @Iain_B (again), so I've been going through your posts trying to figure out how to install the beta on my stock mi 10 (umi).
If I understood well I ~have to (after disabling any pin etc.):
1)Flash through fastboot/adb the 3.4.0 (LittleTurtle2333) TWRP recovery
2)Boot (instead of flash) to TWRP-3.4.2B-1206-XIAOMI10-CN-wzsx150.zip, again through fastboot/adb
3)Format data and cache + davlink partition
4) Flash the latest beta (20.12.10 so far)
5)Boot again to the new twrp and delete cache + davlink partition
Done
Click to expand...
As I said in a previous post:
"Do NOT format, wipe, or do anything that may adversely affect the installation. There should not really be any problem with the installation. IF, for any reason, the installation does not work 100%, then initially try a Factory reset from withing (sic) TWRP. This should keep all your files intact, but reset the system."

[Edited to correct procedure from Stock ROM]

I use a pattern to unlock my phone, but I still have fingerprints and face recognition working.
Therefore, after downloading whichever ROM you are going to use onto your phone; and then following your numbering:
1) Flash 3.4.0 ... (but maybe not necessary at this stage)
2) Boot into 3.4.2b ... (expect delays) - (never flash this version!)
3) Format data ... as coming from stock ROM
3a) Reboot to TWRP again from Fastboot ... - Mount / Enable MTP
4) Copy across & Install ROM ... (from within TWRP)
5) Clear caches *
Done
If the version jump is not too great, you may still be keeping your data. You should be keeping your files. As above, "If, for any reason, the installation does not work 100%, then initially try a Factory reset from within TWRP."

* Reading within the official TWRP FAQs, the installation process should be taking care of this sort of preparation/clearing; also deleting the data/system/package_cache folder may additionally be needed.
 
Last edited:
... I forgot to mention / remind that TWRP has a really good backup process. Tick all the boxes (except maybe 'cache').
'Restore' brings back all of the apps, and their corresponding data (not files), and puts all icons and widgets back into their same positions.
 
Iain_B said:
As I said in a previous post:
"Do NOT format, wipe, or do anything that may adversely affect the installation. There should not really be any problem with the installation. IF, for any reason, the installation does not work 100%, then initially try a Factory reset from withing (sic) TWRP. This should keep all your files intact, but reset the system."

I use a pattern to unlock my phone, but I still have fingerprints and face recognition working.
Therefore, after downloading whichever ROM you are going to use onto your phone; and then following your numbering:
1) Flash 3.4.0 ... YES (but maybe not necessary at this stage)
2) Boot into 3.4.2b ... YES (expect delays) - (never flash this version!)
3) Format, etc. ... NO - NEVER!!!
4) Install ROM ... YES (from within TWRP)
5) Clear caches ... YES *
Done
If the version jump is not too great, you may still be keeping your data. You should be keeping your files. As above, "If, for any reason, the installation does not work 100%, then initially try a Factory reset from within TWRP."

* Reading within the official TWRP FAQs, the installation process should be taking care of this sort of preparation/clearing; also deleting the data/system/package_cache folder may additionally be needed.
Click to expand...
I can't fully agree with you.
If he's coming from stock, with freshly unlocked bootloader - then I would suggest:
1) flash 3.4.2.0623 and boot
2) skip
3) format data would be necessary, cache and dalvik only wiped
4a) copy ROM to the phone
4b) flash ROM
5a) reboot to twrp via fastboot commands
5b) wipe cache/dalvik again
rreboot system.
After this done, the 3.4.0 is a recovery of the phone and your point 2) is valid from this point.
 
  • Like
Reactions: Iain_B and gkalen
Iain_B said:
... I forgot to mention / remind that TWRP has a really good backup process. Tick all the boxes (except maybe 'cache').
'Restore' brings back all of the apps, and their corresponding data (not files), and puts all icons and widgets back into their same positions.
Click to expand...
This I didn't know. Thank you for sharing this info, even though I personally prefer clean installs with all husle of setting the things back up again (with sufficient beer, of course)
 
Iain_B said:
... I forgot to mention / remind that TWRP has a really good backup process. Tick all the boxes (except maybe 'cache').
'Restore' brings back all of the apps, and their corresponding data (not files), and puts all icons and widgets back into their same positions.
Click to expand...
I think it said that it has stock rom , so it definitely needs format data ..

EDIT
And for everyone comes from stock rom , probably the latest is V12.0.... with Android 10 , so he can flash twrp as well ..
Problems starts since 12.2... so the first installation from stock rom can be done as usual and from next update by fastboot mode ..
 
Last edited:
  • Like
Reactions: Iain_B and m@c|-|oR
cause I'm really annoying about the problem of Instagram and whatsapp notifications, which not arrive on my Mi Note 10 with last weekly, I'm thinking to flash xiaomi.eu stable. anyone can tell me what I won't find on it compared with weekly? thanks all
 
Thank you both @Iain_B @m@c|-|oR!!!!
I think I kinda messed up with the numeration after multiple edits, but I probably fixed the post now..
(This may broke your referrences...)
I'll try to do what you both said and install the new rom today or tommorow!
I may also create a guide or something on the site for all this process, cause almost constantly there are people asking about this for the mi 10 series.
Btw, I ~don't like using pins and such either way.
 
Ehmm, well, I think I skipped multiple steps (some accidentally, some not that accidentally) and it seems to be running ok (?). Lol, you'd probably be pulling your hair if you were watching me. I flashed https://androidfilehost.com/?fid=8889791610682877442 , wiped data and then with otg I flashed the latest rom and done. The device seems not to pass safety net, but I haven't installed magisk with its hide props yet (waiting to install the previous apps first).
 
Blastboom Strice said:
Hi @Iain_B (again), so I've been going through your posts trying to figure out how to install the beta on my stock mi 10 (umi).
If I understood well I ~have to (after disabling any pin etc.):
1)Flash the old twrp with fastboot/adb https://androidfilehost.com/?fid=8889791610682877442 (for 20.11.5 version and before)
2)Flash with the recovery the 20.11.5 version (or for extra safety boot into recovery from fastboot/adb and flash the rom from there)
1)Flash through fastboot/adb the 3.4.0 (LittleTurtle2333) TWRP recovery
3)Boot (instead of flash) to TWRP-3.4.2B-1206-XIAOMI10-CN-wzsx150.zip, again through fastboot/adb
4)Format data and cache + davlink partition
5) Flash the latest beta (20.12.10 so far)
6)Boot again to the new twrp and delete cache + davlink partition
Done
Click to expand...
I thank both @m@c|-|oR and @gkalen (and yourself) for putting me right regarding the formatting.
I've just gone through the process of bricking my phone (wiping various partitions, formatting, resizing, changing the file system, etc!). It would only boot into Fastboot after all of that (not surprisingly). So my only option was to do a full stock ROM install (via Fastboot). Which I did.
I then tried my method, ie. without the formatting, and (of course!) it did not work - I booted into TWRP. So I did a format, re-installed the ROM, and it worked, requiring a new setup. I've restored my backup and am now copying back my files (which will take a few hours) so I shall be back to where I was.
So, in principle, you were correct. I shall repeat your instructions with modifications from my current experience:

1) Prepare ROM onto USB memory stick
2) (Flash TWRP 3.4.0 - not necessary at this stage)
3) Boot into TWRP 3.4.2b
4) Format data (only)
5) Install ROM via USB-OTG
6) Boot to system

I put the ROM onto a USB stick because it saved the fiddling around having just formatted the data partition.
 
  • Like
Reactions: gkalen
Iain_B said:
I thank both @m@c|-|oR and @gkalen (and yourself) for putting me right regarding the formatting.
I've just gone through the process of bricking my phone (wiping various partitions, formatting, resizing, changing the file system, etc!). It would only boot into Fastboot after all of that (not surprisingly). So my only option was to do a full stock ROM install (via Fastboot). Which I did.
I then tried my method, ie. without the formatting, and (of course!) it did not work - I booted into TWRP. So I did a format, re-installed the ROM, and it worked, requiring a new setup. I've restored my backup and am now copying back my files (which will take a few hours) so I shall be back to where I was.
So, in principle, you were correct. I shall repeat your instructions with modifications from my current experience:

1) Prepare ROM onto USB memory stick
2) (Flash TWRP 3.4.0 - not necessary at this stage)
3) Boot into TWRP 3.4.2b
4) Format data (only)
5) Install ROM via USB-OTG
6) Boot to system

I put the ROM onto a USB stick because it saved the fiddling around having just formatted the data partition.
Click to expand...
Don't forget after format data to add the step to Reboot to Recovery again .. this must be done also ..
 
  • Like
Reactions: Iain_B
Blastboom Strice said:
Ehmm, well, I think I skipped multiple steps (some accidentally, some not that accidentally) and it seems to be running ok (?). Lol, you'd probably be pulling your hair if you were watching me. I flashed https://androidfilehost.com/?fid=8889791610682877442 , wiped data and then with otg I flashed the latest rom and done. The device seems not to pass safety net, but I haven't installed magisk with its hide props yet (waiting to install the previous apps first).
Click to expand...
Obviously successfully done while I was bricking and preparing my latest contribution. You clearly saw the wisdom in using the USB-OTG method as well.
 
Solved the problem of a battery drain on 20.12.9 for the Apollo device.
It is enough to flash the kernel (boot.img) from 20.12.2 (where the battery consumption was normal) through twrp.
Maybe this solution will be useful.
 
  • Like
Reactions: Honuz
nik.shersh said:
Solved the problem of a battery drain on 20.12.9 for the Apollo device.
It is enough to flash the kernel (boot.img) from 20.12.2 (where the battery consumption was normal) through twrp.
Maybe this solution will be useful.
Click to expand...

How much SOT do you have on MIUI.EU rom...I am on global and have pretty good sot and battery time, but been thinking of unlocking bootloader and flashing MIUI.EU.
 
Iain_B said:
I did not do that, and it has not adversely affected anything. (yet?!)
Click to expand...
In my opinion there are 2 choices
1. reboot to twrp again, MTP is activated automatically in twrp
2. in twrp disable MTP and then enable MTP again
I prefer opton 1
 
  • Like
Reactions: Iain_B
Hi guys, need some help.. right now my Violet stucks at bootscreen (I've waited for half an hour)..

Several days ago I dirty-flashed latest xiaomi.eu weekly 20.12.9 over 20.11.25, when I booted it to recovery to flash hosts file (I did this everytime after flashing newer rom), I noticed some errors after I entered the password (pattern), while in recovery I can see all the folders/files in sdcard, system and vendor partition, and my phone booted to system just fine, and I could use my device without problem, but I noticed my phone was kinda slower while opening apps, so today I dirty-flashed my device once more with the same weekly rom 20.12.9, but this time, It won't boot to system, it stucked at bootscreen.

I don't root my phone.

Here are some screenshoots I took while in OrangeFox recovery.

Any helps / idea to how I can fix this will be very much appreciated, thanks in advance.

Note : While I could copy most of my files in internal storage to my pc, there were some files that can't be copied for example latest backup file of whatsapp database (screenshoot 4).

33506

.

33507
33508
33509
 
fmcheetah said:
In my opinion there are 2 choices
1. reboot to twrp again, MTP is activated automatically in twrp
2. in twrp disable MTP and then enable MTP again
I prefer opton 1
Click to expand...
If MTP = Media Transfer Protocol, then I must assume that it has been enabled because I am copying back 1000s files onto my phone now.
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
246K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
41K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
36K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
38K
HyperOS
KGVER
KGVER
ingbrzy
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
32K
HyperOS
emre_66
E
Top Bottom
Back