m@c|-|oR
Members
- Sep 5, 2020
- 369
- 67
I saw your post about resting. Hopefully it will help others not to run into problems.
So, you assumed there 3.5.0 is to boot only, while it was supposed to be flashed?
Послато са Mi 10 помоћу Тапатока
MIUI 12.5 21.3.3/5
- Thread starter ingbrzy
- Start date
- Status
So, you assumed there 3.5.0 is to boot only, while it was supposed to be flashed?
Послато са Mi 10 помоћу Тапатока
Achimlk9
Members
- May 2, 2020
- 50
- 30
21.3.3 runs perfectly on my Mi 10 Pro, like a Stable Version. Congratulations Developers!!! The only problem I had was making a Backup with TWRP. Not sure if this is the right forum but maybe somebody already found a solution for this issue:
When the TWRP Backup finishes I get an error message 255 - backup failed. In the TWRP log file it shows
failed to lookup tar policy for '/data/extm' - '78d061efb27572fe'
I:Error adding file '/data/extm' to '/usb-otg/TWRP/BACKUPS/6bf84729/2021-03-06--23-22-06/data.f2fs.win015'
Error creating backup.
I tried to delete the folder /data/extm' with the TWRP file manager but this did not help. Any idea how to fix this?
Update: I found the cause of the problem. I did the backup on a OTG USB Stick. it turned out that the USB Stick by mistake was formatted with FAT32 instead of NTFS. Thus the USB Stick could not save files larger than 4GB. One file of the TWRP backup is 9GB big and obviously TWRP could not save the file on the USB. Conerting the USB to NTFS solved the problem.
When the TWRP Backup finishes I get an error message 255 - backup failed. In the TWRP log file it shows
failed to lookup tar policy for '/data/extm' - '78d061efb27572fe'
I:Error adding file '/data/extm' to '/usb-otg/TWRP/BACKUPS/6bf84729/2021-03-06--23-22-06/data.f2fs.win015'
Error creating backup.
I tried to delete the folder /data/extm' with the TWRP file manager but this did not help. Any idea how to fix this?
Update: I found the cause of the problem. I did the backup on a OTG USB Stick. it turned out that the USB Stick by mistake was formatted with FAT32 instead of NTFS. Thus the USB Stick could not save files larger than 4GB. One file of the TWRP backup is 9GB big and obviously TWRP could not save the file on the USB. Conerting the USB to NTFS solved the problem.
Last edited:
This is a bit weird.. Recently, that extm files seems not to be decrypted and thus backed up by the twrps returning an error. Deleting it should have probably worked, hmmm.
I think there's also another guy reporting similar issue today, I think his issue wasn't resolved (didn't post an update), but check the recommendations below.
Poney70
Donator
- Oct 3, 2019
- 5,488
- 337
hi... on mi note 10 fullscreen gesture not working on nova launcher....whit stock launcher is ok ....solution for nova launcher users ???
Poney70
Donator
- Oct 3, 2019
- 5,488
- 337
Hello
Workarounds for third-party launcher:
- Install from Google Play Store:
- Infinity Gestures
- - OR -
- Fluid Navigation Gestures
./adb shell cmd overlay enable com.android.internal.systemui.navbar.gestural
Iain_B
Members
- Mar 25, 2013
- 1,898
- 297
Yes - I was being careful. It's all irrelevant now anyway because TWRP 3.5.0 is included with the Mi 10 (umi) ROMs. So hopefully these problems will not occur again.
Problems with Magisk 22 (recent RN7 ROMs)
I haven't read all the posts, so may be repeating known information; I read a few pages yesterday and didn't find the answer to a problem I was having.
I am using a rooted Redmi Note 7/lavender, with OrangeFox recovery and Magisk root. Until Magisk 21.4 I would install a new ROM and the current Magisk in a single operation (from OrangeFox, not the Updater app), and everything was hunky-dory. With Magisk 22 I made a copy of the .apk with .zip extension and found that nothing worked, I ended up without root, either trying to install from the app or installing from recovery. Worse, if I uninstalled Magisk then installed the previous 21.4 and the Manager I still didn't have root. What worked (copying notes I made for myself):
Magisk 22 (new format) didn't work by renaming the .apk as .zip and installing from a custom recovery; phone was not rooted. The method that works:
With a custom recovery, OrangeFox or TWRP, installed:
- Extract boot.img from the current .eu ROM ZIP image into a directory on the phone.
- Running Magisk installed as an app, click Install Magisk (not the app). With "Preserve force encryption" and "Recovery Mode" both ticked, click Next, then tick "Select and Patch a File" and LET'S GO. Find boot.img (lot's of picture files with "Img" in the name are found, use the Search magnifying glass) and click it. This creates a file with a name like "magisk_patched_pxIX8.img" in the same directory as boot.img.
Boot to recovery (power button, select boot to recovery) and with OrangeFox or TWRP find magisk_patched_pxIX8.img (or whatever name) and install it in the boot partition. That's all, reboot and the phone will be rooted.
Choose one of: "hope this helps"/"apologies for repeating what everyone knows". Best wishes, pol098
I haven't read all the posts, so may be repeating known information; I read a few pages yesterday and didn't find the answer to a problem I was having.
I am using a rooted Redmi Note 7/lavender, with OrangeFox recovery and Magisk root. Until Magisk 21.4 I would install a new ROM and the current Magisk in a single operation (from OrangeFox, not the Updater app), and everything was hunky-dory. With Magisk 22 I made a copy of the .apk with .zip extension and found that nothing worked, I ended up without root, either trying to install from the app or installing from recovery. Worse, if I uninstalled Magisk then installed the previous 21.4 and the Manager I still didn't have root. What worked (copying notes I made for myself):
Magisk 22 (new format) didn't work by renaming the .apk as .zip and installing from a custom recovery; phone was not rooted. The method that works:
With a custom recovery, OrangeFox or TWRP, installed:
- Extract boot.img from the current .eu ROM ZIP image into a directory on the phone.
- Running Magisk installed as an app, click Install Magisk (not the app). With "Preserve force encryption" and "Recovery Mode" both ticked, click Next, then tick "Select and Patch a File" and LET'S GO. Find boot.img (lot's of picture files with "Img" in the name are found, use the Search magnifying glass) and click it. This creates a file with a name like "magisk_patched_pxIX8.img" in the same directory as boot.img.
Boot to recovery (power button, select boot to recovery) and with OrangeFox or TWRP find magisk_patched_pxIX8.img (or whatever name) and install it in the boot partition. That's all, reboot and the phone will be rooted.
Choose one of: "hope this helps"/"apologies for repeating what everyone knows". Best wishes, pol098
Poney70
Donator
- Oct 3, 2019
- 5,488
- 337
== IMPORTANT - Update to Magisk v22.0 from any previous Magisk version ==
If you hid Magisk Manager app, you have to "Restore Magisk Manager" in Magisk Manager app settings BEFORE installing Magisk v22.0.
If you hid Magisk Manager app, you have to "Restore Magisk Manager" in Magisk Manager app settings BEFORE installing Magisk v22.0.
Last edited:
zeyentology
Members
- Sep 11, 2018
- 190
- 40
I've been able to boot straight into twrp with the previous release already. Has the decryption issue been solved in twrp 3.5 now or do I still have to remove fingerprint and pin and need otg storage to install upcoming releases? This is the biggest pita atm. Apart from that all recent releases ran flawlessly on my umi.With the Mi 10 (umi), and new TWRP 3.5.0 which has been included with this week's ROM - no problems to report so far. (I must have been unlucky this morning when I tested it). I've been in and out of Recovery a couple of times. Just gone into Recovery again and re-installed this week's ROM, plus Magisk, and the normal tidying up. Rebooted back into System. All still seems OK. Another restart - still within 50 seconds. So all running nice and smoothly - both ROM and TWRP.
So it looks like no more Fastboot booting to install ROMs -
Gesendet von meinem Mi 10 mit Tapatalk
I ~don't use any passwords and such, but with this twrp and the previous one (1206) I many times did the updates with the rom.zip I had downloaded in my internal storage (just moved the rom from the pc in my phone or downloaded straight from androidfilehost using fdm).
I can confirm that decrypting data with "pin" in the latest TWRP (the latest one for MI 10, the one provided in the ROM, TWRP 3.5.0) works. I haven't tried "passwords" though, but I assume it works too as "pin" works.
(This was in response to my post regarding problems installing Magisk 22.) While I'm not totally certain - I must have done something if I had trouble where others didn't - I don't think I ever hid Magisk; I don't use payment or banking applications that object to root.== IMPORTANT - Update to Magisk v22.0 from any previous Magisk version ==
If you hid Magisk Manager app, you have to "Restore Magisk Manager" in Magisk Manager app settings BEFORE installing Magisk v22.0.
Mi 9t pro no root, did dirty flash from beta 21.2.3/4
Experiencing issues with battery charging. I usually needed around 1h (maybe less) to charge from 20% to 100%. Now It charged from 25% to 66% in 1h and it shows I need 44 more minutes for full charge. Will post tomorrow if I notice improvement in charging speed
Edit: also phone is freezing for 10-15 seconds if I try to open control center in the first 1-2 minutes after restart.
Also getting short term notifications that some apps are doing random things: last one I saw was "radio is checking storage space", I never opened the radio app.
Also got error that "security is not responding" after opening chrome...
Experiencing issues with battery charging. I usually needed around 1h (maybe less) to charge from 20% to 100%. Now It charged from 25% to 66% in 1h and it shows I need 44 more minutes for full charge. Will post tomorrow if I notice improvement in charging speed
Edit: also phone is freezing for 10-15 seconds if I try to open control center in the first 1-2 minutes after restart.
Also getting short term notifications that some apps are doing random things: last one I saw was "radio is checking storage space", I never opened the radio app.
Also got error that "security is not responding" after opening chrome...
Attachments
Last edited:
I'm absolutely happy with the ROM on MI11. Everything works fluently and I could'nt find a single bug. As I read, the issue with automatic brightness is a general MIUI problem. If the surrounding gets a bit darker, the brightness goes all the way down. This does not change after using the phone for several days. I read about several solutions in different forums but none of them seems to be perfect. Maybe you guys got a hint for me.
Iain_B
Members
- Mar 25, 2013
- 1,898
- 297
- Oct 6, 2016
- 9,907
- 322
21.3.5 already uploaded:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
Xiaomi.eu Multilang MIUI ROMs - Browse /xiaomi.eu/MIUI-WEEKLY-RELEASES/21.3.5 at SourceForge.net
OFFICIAL mirror of MIUI Multilang ROM by https://xiaomi.eu/
sourceforge.net
zeyentology
Members
- Sep 11, 2018
- 190
- 40
Iain_B
Members
- Mar 25, 2013
- 1,898
- 297
A request.
Something which has not yet been resolved.
Widgets: Is it possible to sort these alphabetically, or at least put some logical order on them?
The order seems random.
(Mi 10 - umi)
Something which has not yet been resolved.
Widgets: Is it possible to sort these alphabetically, or at least put some logical order on them?
The order seems random.
(Mi 10 - umi)
IrishKevin
Members
- Jun 4, 2018
- 33
- 20
- Feb 11, 2012
- 11,601
- 322
- Status
