Kolobok737
Members
- Apr 16, 2016
- 33
- 20
Why Mi Note 10 LITE ROM has the 'fastboot' in the name of zip file ? How to install this zip image ? Via TWRP or MI Flash in fastboot mode ?
Also have this problemToday I updated my Redmi 8T from version 11.04 to 11.05, but the system cannot be started and recovers are started every time. What can I do?
Also have this problem
Download ROM again.. should be fixed..Today I updated my Redmi 8T from version 11.04 to 11.05, but the system cannot be started and recovers are started every time. What can I do?
Now it's OKDownload ROM again.. should be fixed..
What is the most recent version for the 8T (Willow)?
I am asking as there is one labeled V11.0.7 dated March 2020, an V11.0.4 dated June 2020 and a recent V11.0.5 dated August 2020.
This one has been announced for August. According to one moderator at the official Mi-Forum, the release has been postponed and no new release date has been mentioned yet.. So we just have to wait some more..Why aren't we talking about a V12 ROM for RN8T? Are we going to receive it at all? And Android 10?
This phone has a year, how it it possible to such delay on having MiUI 12?! Very disappointed with Xiaomi, if wasn't for Huawei block from Google, I would certainly change the brand of my phones.. Thank you to XIAOMI EU developers for this new update.This one has been announced for August. According to one moderator at the official Mi-Forum, the release has been postponed and no new release date has been mentioned yet.. So we just have to wait some more..
This phone has a year, how it it possible to such delay on having MiUI 12?! Very disappointed with Xiaomi, if wasn't for Huawei block from Google, I would certainly change the brand of my phones.. Thank you to XIAOMI EU developers for this new update.
OR flash fencrypt.zip and start from format data/clean install if you want to boot the first time.On Mi Max 3, encryption doesn't work.
There's some vague suggestions that make reference to the modification of /system/vendor/etc/fstab.qcom, but that method makes the Mi Max 3 refuse to boot the ROM, and immediately enter TWRP, which subsequently hangs.
Then you must flash orangefox instead, so that you can wipe or re-flash the eu rom, then flash TWRP again. But in that case - still no encryption!
The combination of a custom recovery and no encryption is devastatingly insecure!
Maybe I missed an FAQ, or a link to such?
flash fencrypt.zip
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
# Non-A/B fstab.qcom variant
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,nodiscard,inline_xattr,reserve_root=32768,resgid=1065,fsync_mode=nobarrier wait,check,fileencryption=ice,quota,reservedsize=128M
/devices/soc/c084000.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=footer
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait
/devices/soc/a800000.ssusb/a800000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
- Removing forced encryption from fstab
- Patching fstabs:
/vendor/etc/fstab.qcom
/system/system/vendor/etc/fstab.qcom
Is there any way to modify some system? Or isn't there currently?Because this phone has "dynamic partition" scheme.
Google about it for more explanation.
Yes but not via TWRP.Is there any way to modify some system? Or isn't there currently?
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
Forget about MI8 Fstab. It is different.Yes, I have been reading your comments in other threads in detail.
However, I'm stuck here:
1. What/Where is fencrypt.zip? Do you mean the files you attached in other threads?
2. If I use your fstab.qcom file in your forceencrypt.zip, it comes back with errors.
3. Doesn't your MI8 have a different partition table to my MiMax3? If yes, then if I flash your fstab, my system won't boot.
4. My fstab.qcom doesn't have '=ice', it has '=footer'. When I mount vendor and edit the file in vi, to change /data to have 'fileencryption=ice', the phone won't boot, and even TWRP won't load!
5. I downloaded your forceencrypt.zip, replaced the file with my modified fstab.qcom, and the same thing happens - phone won't boot, TWRP won't boot.
This is the fstab.qcom file I tried to edit by hand (vi) and by flashing inside forceencrypt.zip:
Code:# Android fstab file. # The filesystem that contains the filesystem checker binary (typically /system) cannot # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK #TODO: Add 'check' as fs_mgr_flags with data partition. # Currently we dont have e2fsck compiled. So fs check would failed. # Non-A/B fstab.qcom variant #<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags> /dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,nodiscard,inline_xattr,reserve_root=32768,resgid=1065,fsync_mode=nobarrier wait,check,fileencryption=ice,quota,reservedsize=128M /devices/soc/c084000.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=footer /dev/block/bootdevice/by-name/misc /misc emmc defaults defaults /dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait /dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait /devices/soc/a800000.ssusb/a800000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto /dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait /dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait /dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
Forget about MI8 Fstab. It is different.
Your mofified Fstab is good to encrypt. It has fileencryption=ice correctly set.
Did you format data? This is mandatory to start the encryption process....
d=/dev/block/mmcblk0p79 # your /data partition here - " mount | grep '/data' "
umount $d
dd if=/dev/zero of=$d bs=1M count=128
echo 'end_sector - start_sector - (16384 / logical_sector_size)'
echo '122142686 - 17301504 - (16384 - 512)'
echo '104841150'
mkfs.f2fs $d 104841150
mount $d
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation