search

Divested-Mobile / DivestOS-Build

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system.
https://divestos.org/index.php?page=build
Other
226 stars 31 forks source link

fastboot update divested-20.0-[...]-fastboot.zip on OnePlus 9 Pro results in Qualcomm CrashDump Mode on boot #333

Closed kiecla closed 3 months ago

kiecla commented 3 months ago

I'm trying to install DivestOS on a new OnePlus 9 Pro. I followed the guide link and on running fastboot update divested-20.0-20240810-dos-lemonadep-fastboot.zip fastboot initiates a reboot to the bootloader, but instead of reaching bootloader it goes to the Qualcomm CrashDump Mode, and does so every time I reboot. I can still access bootloader, and also boot in to the A partition using --set-active=a, which has a tool I don't recognise installed with options for wiping data and cache. Attempting to boot in to recovery here as the guide suggests goes to CrashDump Mode again.

My terminal logs during install are below, with comments for when I rebooted the phone.

# initial boot in to new phone, installed update from OnePlus
# enabled Developer Options, allowed unlocking, and allowed ADB
# rebooted one time here back into the untouched OS
# reboot into fastboot
$ fastboot oem unlock
OKAY [  0.036s]
Finished. Total time: 0.036s
# reboot to OS
# reboot to bootloader
$ fastboot erase avb_custom_key
Erasing 'avb_custom_key'                           OKAY [  0.012s]
Finished. Total time: 0.020s
$ fastboot flash avb_custom_key avb_pkmd-lemonadep.bin 
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB)                    OKAY [  0.003s]
Writing 'avb_custom_key'                           OKAY [  0.009s]
Finished. Total time: 0.036s
# reboot in to bootloader
$ fastboot update divested-20.0-20240810-dos-lemonadep-fastboot.zip
--------------------------------------------
Bootloader Version...: 
Baseband Version.....: 
Serial Number........: ff0ded02
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.002s]
Setting current slot to 'b'                        OKAY [  0.009s]
archive does not contain 'fastboot-info.txt'
extracting boot.img (192 MB) to disk... took 0.463s
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.045s
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'
extracting vendor_boot.img (192 MB) to disk... took 0.432s
archive does not contain 'vendor_kernel_boot.img'
archive does not contain 'boot_other.img'
extracting odm.img (988 MB) to disk... took 3.554s
archive does not contain 'odm_dlkm.img'
extracting product.img (515 MB) to disk... took 2.332s
extracting system.img (920 MB) to disk... took 4.261s
archive does not contain 'system_dlkm.img'
extracting system_ext.img (276 MB) to disk... took 1.128s
archive does not contain 'system_other.img'
extracting vendor.img (614 MB) to disk... took 2.761s
extracting vendor_dlkm.img (37 MB) to disk... took 0.123s
archive does not contain 'vendor_other.img'
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting super_empty.img (0 MB) to RAM...
extracting boot.img (192 MB) to disk... took 0.467s
archive does not contain 'boot.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'boot_b' (196608 KB)                       OKAY [  4.593s]
Writing 'boot_b'                                   OKAY [  0.528s]
extracting super_empty.img (0 MB) to RAM...
extracting dtbo.img (24 MB) to disk... took 0.049s
archive does not contain 'dtbo.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'dtbo' (24576 KB)                          OKAY [  0.575s]
Writing 'dtbo'                                     OKAY [  0.086s]
extracting super_empty.img (0 MB) to RAM...
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'vbmeta' (8 KB)                            OKAY [  0.002s]
Writing 'vbmeta'                                   OKAY [  0.001s]
extracting super_empty.img (0 MB) to RAM...
extracting vendor_boot.img (192 MB) to disk... took 0.457s
archive does not contain 'vendor_boot.sig'
extracting super_empty.img (0 MB) to RAM...
Sending 'vendor_boot' (196608 KB)                  OKAY [  4.576s]
Writing 'vendor_boot'                              OKAY [  0.577s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot                            OKAY [  0.002s]
< waiting for any device >
# phone boots in to Qualcomm CrashDump Mode without any input from me
# powering off and rebooting returns me to Qualcomm CrashDump Mode
# using the button combination I can return to fastboot, reattempting the fastboot update command makes no difference to the outcome
# if I catch the phone during its automated reboot and use the button combination I can get back into fastboot on that reboot, but the fastboot update command just displays this at the end of its output, then stops waiting and quits out
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I can provide any other output requested.

kiecla commented 3 months ago

I should have searched harder before I reported. Two other issues here with a very similar problem and suggested solutions. https://github.com/Divested-Mobile/DivestOS-Build/issues/125 https://github.com/Divested-Mobile/DivestOS-Build/issues/297 Closing unless I can't get things working based on the replies to that issue. I suspect out of date firmware.

SkewedZeppelin commented 3 months ago

sideload via recovery if you can boot to it, otherwise try steps here: https://wiki.lineageos.org/devices/lemonadep/fw_update/

kiecla commented 3 months ago

Unfortunately I can't make it to recovery, I get CrashDump Mode when I try to. I was aiming to try the firmware update with the firmware you directed another user to here (because I can't run the Oxygen Updater whilst my phone won't boot of course) but the .imgs in the repo there don't look right to me. All of the files are around about ~150B with text contents that describes sha256 and sizes rather than the 100-200kB files uploaded for other devices on that repo that are binary. That's not how they should be right? I'm looking into the MSM tool route where I could reload stock, then use that to complete the steps on the Lineage wiki for updating firmware.

kiecla commented 3 months ago

Looks like the .imgs at that link became metadata files after their last commit. I think I will try with the previous version and raise a report on that repo too so they can get fixed for the latest version.

kiecla commented 3 months ago

I'm sorted now. Thanks for the pointer. Quick description for anyone who faces the same issue or if you're curious. You do not need to reinstall the stock OS or use the MSM (which supposedly burns up a little bit of your read only memory lifespan, not sure how much weight there is to that though).