Problems with Mi9 (cepheus)

Apps & Core Settings
1

Hi,

I have a Mi9 running with Iode for quite some time. I did not use it for some months, when I wanted to run an update, it did work (always telling me I have no network connection, which I had).

I then tried tried to reinstall it with the installer - same problem.

Therefore I downloaded the complete fastboot package and ran the windows batch command, which also finished without errors. But afterward the MI 9 ist not booting anymore. I can still access the fastboot menu but not any recovery (most errors refer to “failed to mount”). Resetting did not work either.

I realized that the whole packages (also old releases ) haben been updated 5 days ago and I wondered if there are any known issues with these updates?

Best regards

Marc

2

Users with Mi 10 T Pro have solved an issue with OTA updates failing to install by clearing their system cache using Recovery: XIAOMI Mi 10 T Pro : mise a jour / update impossible de 6.7 vers 6.8

But now that you have attempted full re-flashing, please get any output from the terminal when you attempt to flash it, I suspect something didn’t complete successfully?

3

This is the log, there aren’t any issues shown:

mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 560e034c-bf95-11f0-8652-530670f0c523
Superblock backups stored on blocks:
32768

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Sending ‘cache’ (184 KB) OKAY [ 0.021s]
Writing ‘cache’ OKAY [ 0.000s]
Finished. Total time: 0.741s
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘cache’ OKAY [ 0.000s]
Finished. Total time: 0.011s
Warning: metadata type is raw, but ext4 was requested for formatting.
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

Sending ‘metadata’ (52 KB) OKAY [ 0.008s]
Writing ‘metadata’ OKAY [ 0.000s]
Finished. Total time: 0.115s
Erasing ‘metadata’ OKAY [ 0.000s]
Finished. Total time: 0.016s
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 29136891 4k blocks and 7290880 inodes
Filesystem UUID: 56a6aa34-bf95-11f0-b662-63f6e5c87e77
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending ‘userdata’ (5277 KB) OKAY [ 0.165s]
Writing ‘userdata’ OKAY [ 0.000s]
Finished. Total time: 0.491s

Bootloader Version…:
Baseband Version…:
Serial Number…: 561241c9

extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.000s]
extracting boot.img (128 MB) to disk… took 0.447s
archive does not contain ‘boot.sig’
Sending ‘boot’ (131072 KB) OKAY [ 3.824s]
Writing ‘boot’ OKAY [ 0.673s]
archive does not contain ‘init_boot.img’
extracting dtbo.img (32 MB) to disk… took 0.089s
archive does not contain ‘dtbo.sig’
Sending ‘dtbo’ (32768 KB) OKAY [ 0.872s]
Writing ‘dtbo’ OKAY [ 0.153s]
archive does not contain ‘dt.img’
archive does not contain ‘pvmfw.img’
extracting recovery.img (64 MB) to disk… took 0.405s
archive does not contain ‘recovery.sig’
Sending ‘recovery’ (65536 KB) OKAY [ 1.845s]
Writing ‘recovery’ OKAY [ 0.332s]
extracting vbmeta.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta.sig’
Sending ‘vbmeta’ (8 KB) OKAY [ 0.000s]
Writing ‘vbmeta’ OKAY [ 0.002s]
archive does not contain ‘vbmeta_system.img’
archive does not contain ‘vbmeta_vendor.img’
archive does not contain ‘vendor_boot.img’
archive does not contain ‘vendor_kernel_boot.img’
archive does not contain ‘super_empty.img’
archive does not contain ‘odm.img’
archive does not contain ‘odm_dlkm.img’
archive does not contain ‘product.img’
extracting system.img (2293 MB) to disk… took 14.020s
archive does not contain ‘system.sig’
Sending sparse ‘system’ 1/4 (775360 KB) OKAY [ 19.168s]
Writing ‘system’ OKAY [ 0.000s]
Sending sparse ‘system’ 2/4 (774312 KB) OKAY [ 20.068s]
Writing ‘system’ OKAY [ 0.006s]
Sending sparse ‘system’ 3/4 (769904 KB) OKAY [ 19.633s]
Writing ‘system’ OKAY [ 0.008s]
Sending sparse ‘system’ 4/4 (28792 KB) OKAY [ 13.323s]
Writing ‘system’ OKAY [ 0.000s]
archive does not contain ‘system_dlkm.img’
archive does not contain ‘system_ext.img’
extracting vendor.img (827 MB) to disk… took 4.379s
archive does not contain ‘vendor.sig’
Sending sparse ‘vendor’ 1/2 (774820 KB) OKAY [ 23.228s]
Writing ‘vendor’ OKAY [ 0.000s]
Sending sparse ‘vendor’ 2/2 (72704 KB) OKAY [ 13.532s]
Writing ‘vendor’ OKAY [ 0.000s]
archive does not contain ‘vendor_dlkm.img’
Finished. Total time: 136.822s
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘userdata’ OKAY [ 0.633s]
Finished. Total time: 2.292s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.014s
Press any key to exit…

4

it seems to be the same bevaviour (e.g. screen) as desribed here:

5

Hi, I found the solution (as mentioned in previous article).

The recovery image included in the img was broken, it could not load up.

I downloaded alternative recovery image from orangeFox:

Unzip, find the recovery.img

You can upload it to device with:

fastboot flash recovery recovery.img

I then did format data und rebootet, it then found the iode img which was already on the device from initial installation.

Hope that helps others

Marc

6

Thanks, I will pass that back to the developers!