Open ghost opened 1 year ago
The DivestOS 20.0 recovery (with manual reboot) doesn't validate the divested-20.0-20230825-dos-davinci.zip
.
Is it orange?
Is it orange?
Yes
The DivestOS recovery (from step 8), can't install divested-20.0-20230825-dos-davinci.zip
. But if I use the lineageOS recovery to flash divested-20.0-20230825-dos-davinci.zip
, I have a working DivestOS recovery.
I have a similar looking issue on davinci trying to install latest 17.1-20240620.
All previous steps from https://divestos.org/builds/LineageOS/davinci/install.html were fine, maybe except that there is a warning (does it matter?)
$ fastboot wipe-super super_empty-davinci.img
Warning: skip copying system image avb footer due to sparse image.
Sending 'system' (264 KB) OKAY [ 0.012s]
Writing 'system' OKAY [ 0.000s]
Sending 'cust' (0 KB) OKAY [ 0.005s]
Writing 'cust' OKAY [ 0.000s]
Sending 'vendor' (0 KB) OKAY [ 0.007s]
Writing 'vendor' OKAY [ 0.000s]
Finished. Total time: 0.041s
After rebooting to the bootloader I try next step which fails:
$ fastboot update divested-17.1-20240620-dos-davinci-fastboot.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e3ac69b7
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'version-cn' FAILED
Could not getvar for 'version-cn' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Trying to force it fails midway:
$ fastboot update --force divested-17.1-20240620-dos-davinci-fastboot.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e3ac69b7
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'version-cn' FAILED
Could not getvar for 'version-cn' (remote: 'GetVar Variable Not found')
requirements not met! but proceeding due to --force
Checking 'version-in' FAILED
Could not getvar for 'version-in' (remote: 'GetVar Variable Not found')
requirements not met! but proceeding due to --force
Checking 'version-eea' FAILED
Could not getvar for 'version-eea' (remote: 'GetVar Variable Not found')
requirements not met! but proceeding due to --force
archive does not contain 'fastboot-info.txt'
extracting boot.img (64 MB) to disk... took 0.189s
archive does not contain 'init_boot.img'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (64 MB) to disk... took 0.197s
extracting vbmeta.img (0 MB) to disk... took 0.000s
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 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (559 MB) to disk... took 8.519s
extracting system.img (910 MB) to disk... took 12.747s
archive does not contain 'system_dlkm.img'
archive does not contain 'system_ext.img'
extracting vendor.img (752 MB) to disk... took 16.277s
archive does not contain 'vendor_dlkm.img'
archive does not contain 'super_empty.img'
archive does not contain 'super_empty.img'
extracting boot.img (64 MB) to disk... took 0.311s
archive does not contain 'boot.sig'
archive does not contain 'super_empty.img'
Sending 'boot' (131072 KB) OKAY [ 2.745s]
Writing 'boot' OKAY [ 0.646s]
archive does not contain 'super_empty.img'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'super_empty.img'
Sending 'dtbo' (32768 KB) OKAY [ 0.690s]
Writing 'dtbo' OKAY [ 0.173s]
archive does not contain 'super_empty.img'
extracting recovery.img (64 MB) to disk... took 0.197s
archive does not contain 'recovery.sig'
archive does not contain 'super_empty.img'
Sending 'recovery' (65536 KB) OKAY [ 1.372s]
Writing 'recovery' OKAY [ 0.333s]
archive does not contain 'super_empty.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
archive does not contain 'super_empty.img'
Sending 'vbmeta' (8 KB) OKAY [ 0.010s]
Writing 'vbmeta' OKAY [ 0.001s]
archive does not contain 'super_empty.img'
archive does not contain 'super_empty.img'
extracting product.img (559 MB) to disk... took 10.120s
archive does not contain 'product.sig'
archive does not contain 'super_empty.img'
Warning: skip copying product image avb footer due to sparse image.
Sending 'product' (573308 KB) OKAY [ 12.050s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
The device is bootlooped. When I try to enter recovery sometimes it appears on the screen for a split second and then reboots immediately. But once when it appeared I managed to tap a button in it and it stayed. The recovery says its 17.1 so I guess it flashed OK, but not the rest.
Before trying to install Divested I had a PixelOS (android 14) and a pixelos recovery on this phone. Could it be an issue?
fastboot getvar all
output (there is no "product" partition there):
fastboot-getvar-all.txt
My FW version is Mi 9T (Global) - V12.1.4.0.RFJMIXM which is the one LineageOS recommends.
I've managed to fix my issue following way.
I've re-flashed PixelOS recovery. Entered it and switched it to fastbootd mode.
Flashed product
, system
, vendor
, boot
, recovery
images "manually" i.e. via fastboot flash product product.img
. Other images (dtbo.img
, etc.) gave errors.
Then I followed https://divestos.org/builds/LineageOS/davinci/install.html from the start, fastboot update --force
gave same errors as above (but it managed to flash imgs that gave errors via fastbootd).
Then did copy-partitions-davinci-release.zip
(there were a lot of errors).
Then sideloaded the main zip, wiped data and rebooted to the system! The system seems to work so far!
The only bug I've noticed is in the Updater: it offers me to download the 17.1 2024.06.20 update which I've just installed.
Weird, but nice to see you got it to work.
As for the updater, it'll always show the latest update even if it is already installed.
Phone: Xiaomi 9T (davinci) Version: 20.0
Bug:
I am trying to follow this guide: https://divestos.org/builds/LineageOS/davinci/install.html. But the step number 8 failed.
With
--force
the device reboot to the system:With
--force
and a manual reboot (Volume Down + Power):Additional Information
I am able to install lineageOS (https://wiki.lineageos.org/devices/davinci/install/variant1) and Xiaomi official ROM (https://xiaomifirmwareupdater.com/miui/davinci/).
The
--force
seems to force the installation DivestOS recovery.