After installing DivestOS on fajita, after postmarketOS install, device is stuck on logo
iamwacko opened this issue · 3 comments
Like the title says, it's stuck on the "DivestOS" logo with changing colors. It's been this way for hours at this point. Holding down the power button fails to restart it and I can't get it to show up with EDL or ADB.
I had previously installed postmarketOS on it, but this is just a spare phone and I wanted to try something else out. I flashed the avb_custom_key, then ran fastboot update divested-20.0-20231206-dos-fajita-fastboot.zip
. Output is below. After it finished flashing it booted straight into the logo, and has been stuck there ever since.
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (64 MB) to disk... took 0.150s
archive does not contain 'init_boot.img'
extracting dtbo.img (8 MB) to disk... took 0.019s
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
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 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
archive does not contain 'product.img'
extracting system.img (1716 MB) to disk... took 8.614s
archive does not contain 'system_dlkm.img'
archive does not contain 'system_ext.img'
archive does not contain 'system_other.img'
extracting vendor.img (575 MB) to disk... took 2.358s
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
extracting boot.img (64 MB) to disk... took 0.109s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.780s]
Writing 'boot_a' OKAY [ 0.377s]
extracting dtbo.img (8 MB) to disk... took 0.026s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (8192 KB) OKAY [ 0.238s]
Writing 'dtbo' OKAY [ 0.045s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.001s]
archive does not contain 'super_empty.img'
extracting system.img (1716 MB) to disk... took 8.476s
archive does not contain 'system.sig'
Warning: skip copying system_a image avb footer (system_a partition size: 2998927360, system_a image size: 140737197901168).
Sending sparse 'system_a' 1/4 (517308 KB) OKAY [ 13.680s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 2/4 (516080 KB) OKAY [ 15.209s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 3/4 (516080 KB) OKAY [ 15.359s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 4/4 (207848 KB) OKAY [ 7.499s]
Writing 'system_a' OKAY [ 0.001s]
extracting vendor.img (575 MB) to disk... took 2.620s
archive does not contain 'vendor.sig'
Warning: skip copying vendor image avb footer (vendor partition size: 1073741824, vendor image size: 140737197901168).
Sending sparse 'vendor' 1/2 (516696 KB) OKAY [ 13.592s]
Writing 'vendor' OKAY [ 0.001s]
Sending sparse 'vendor' 2/2 (73088 KB) OKAY [ 3.979s]
Writing 'vendor' OKAY [ 0.001s]
Rebooting OKAY [ 0.293s]
Finished. Total time: 96.168s
At this point I'm just waiting for the battery to run out so I can try to boot it into fastboot or EDL.
way for hours at this point
never wait for more than 10 minutes
Holding down the power button fails to restart
hold volume up + power for 10 seconds, if that doesn't work try volume down + power
stuck
You likely have outdated firmware, if you can boot into the recovery then adb sideload
the update as per https://divestos.org/builds/LineageOS/fajita/install.html
If you can't boot into the recovery either then follow these steps: https://wiki.lineageos.org/devices/fajita/fw_update/
hold volume up + power for 10 seconds, if that doesn't work try volume down + power
Thank you! I'd tried to find how to hard poweroff it, but I guess I didn't search hard enough. I guess I must have accidentally been holding them both down when I tried down+power
Thank you!