This is a cache of https://discuss.96boards.org/t/dragon-board-stuck-again-at-qualcomm-dl-mode-not-able-to-recover-to-fastboot-adb-mode/6603. It is a snapshot of the page at 2024-10-31T10:05:32.642+0000.
Dragon Board stuck again at Qualcomm DL Mode (Not able to recover to fastboot/adb mode) - DragonBoard410c - 96Boards Forum

Dragon Board stuck again at Qualcomm DL Mode (Not able to recover to fastboot/adb mode)

Products Support DragonBoard410c
#1

I have worked with my Dragonboard several times and changed from Linux to Android and back to Linux. But recently I flashed bootloader using the regular method (referring same tutorial, DragonBoard 410c Board Recovery - 96Boards), but it is not detecting SD Card with linux/android anymore. It looks, not able to boot the SBL and load the LK, it keeps on rebooting. Even I tried to flash the entire system in Windows with Windows10 IOT image using USB Boot but it also fails.

  • changed the S6 to USB Boot mode and flashed the bootloader using qdl tool
    dragonboard-410c-bootloader-emmc-linux-108$ sudo qdl prog_emmc_firehose_8916.mbn rawprogram.xml patch.xml
    HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
    READ image: 13 offset: 0x0 length: 0x34
    READ image: 13 offset: 0x34 length: 0x60
    READ image: 13 offset: 0x1000 length: 0x1000
    READ image: 13 offset: 0x2000 length: 0x988
    READ image: 13 offset: 0x3000 length: 0x1000
    READ image: 13 offset: 0x4000 length: 0x1000
    READ image: 13 offset: 0x5000 length: 0x1000
    READ image: 13 offset: 0x6000 length: 0x1000
    READ image: 13 offset: 0x7000 length: 0x1000
    READ image: 13 offset: 0x8000 length: 0x1000
    READ image: 13 offset: 0x9000 length: 0x1000
    READ image: 13 offset: 0xa000 length: 0x1000
    READ image: 13 offset: 0xb000 length: 0x1000
    READ image: 13 offset: 0xc000 length: 0x1000
    READ image: 13 offset: 0xd000 length: 0x1000
    READ image: 13 offset: 0xe000 length: 0x1000
    READ image: 13 offset: 0xf000 length: 0x1000
    READ image: 13 offset: 0x10000 length: 0x1000
    READ image: 13 offset: 0x11000 length: 0x1000
    READ image: 13 offset: 0x12000 length: 0x1000
    READ image: 13 offset: 0x13000 length: 0x1000
    READ image: 13 offset: 0x14000 length: 0x1000
    READ image: 13 offset: 0x15000 length: 0x1000
    READ image: 13 offset: 0x16000 length: 0x1000
    READ image: 13 offset: 0x17000 length: 0xbd8
    END OF IMAGE image: 13 status: 0
    DONE status: 0
    LOG: logbuf@0x0801CDC0 fh@0x08019C28
    LOG: Host’s payload to target size is too large
    LOG: logbuf@0x0801CDC0 fh@0x08019C28
    LOG: logbuf@0x0801CDC0 fh@0x08019C28
    LOG: start 131072, num 1
    LOG: Finished sector address 131073
    [PROGRAM] flashed “cdt” successfully
    LOG: start 262144, num 506
    LOG: Finished sector address 262650
    [PROGRAM] flashed “sbl1” successfully
    LOG: start 263168, num 303
    LOG: Finished sector address 263471
    [PROGRAM] flashed “rpm” successfully
    LOG: start 264192, num 1183
    LOG: Finished sector address 265375
    [PROGRAM] flashed “tz” successfully
    LOG: start 266240, num 120
    LOG: Finished sector address 266360
    [PROGRAM] flashed “hyp” successfully
    Unable to open sec.dat…ignoring
    LOG: start 267296, num 1067
    LOG: Finished sector address 268363
    [PROGRAM] flashed “aboot” successfully
    Unable to open boot.img…ignoring
    LOG: start 0, num 34
    LOG: Finished sector address 34
    [PROGRAM] flashed “PrimaryGPT” successfully
    LOG: start 15269855, num 33
    LOG: Finished sector address 15269888
    [PROGRAM] flashed “BackupGPT” successfully
    Update last partition 10 ‘rootfs’ with actual size in Primary Header.
    LOG: Patched sector 4 with 00E8FFDE
    Update last partition 10 ‘rootfs’ with actual size in Backup Header.
    LOG: Patched sector 15269857 with 00E8FFDE
    Update Primary Header with LastUseableLBA.
    LOG: Patched sector 1 with 00E8FFDE
    Update Backup Header with LastUseableLBA.
    LOG: Patched sector 15269887 with 00E8FFDE
    Update Primary Header with BackupGPT Header Location.
    LOG: Patched sector 1 with 00E8FFFF
    Update Backup Header with CurrentLBA.
    LOG: Patched sector 15269887 with 00E8FFFF
    Update Backup Header with Partition Array Location.
    LOG: Patched sector 15269887 with 00E8FFDF
    Update Primary Header with CRC of Partition Array.
    LOG: crc start sector 2, over bytes 1536
    LOG: Patched sector 1 with 4AD0DADB
    Update Backup Header with CRC of Partition Array.
    LOG: crc start sector 15269855, over bytes 1536
    LOG: Patched sector 15269887 with 4AD0DADB
    Zero Out Header CRC in Primary Header.
    LOG: Patched sector 1 with 00000000
    Update Primary Header with CRC of Primary Header.
    LOG: crc start sector 1, over bytes 92
    LOG: Patched sector 1 with 232FB7A1
    Zero Out Header CRC in Backup Header.
    LOG: Patched sector 15269887 with 00000000
    Update Backup Header with CRC of Backup Header.
    LOG: crc start sector 15269887, over bytes 92
    LOG: Patched sector 15269887 with E4874975
    LOG: Set bootable drive to 0.
    partition 0 is now bootable
  • changed the S6 to SD Boot mode and inserted with linux (dragonboard410c_sdcard_install_debian-xx ) and then repowered the device here

dragonboard-410c-bootloader-emmc-linux-108$ adb devices
List of devices attached
^C
dragonboard-410c-bootloader-emmc-linux-108$ lsusb
Bus 001 Device 081: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
dragonboard-410c-bootloader-emmc-linux-108$ adb devices
List of devices attached
^C
dragonboard-410c-bootloader-emmc-linux-108$ fastboot devices

Serial Console log

[2018-11-13 15:27:44] Format: Log Type - Time(microsec) - Message - Optional Info
[2018-11-13 15:27:44] Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
[2018-11-13 15:27:44] S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00288
[2018-11-13 15:27:44] S - IMAGE_VARIANT_STRING=HAAAANAZA
[2018-11-13 15:27:44] S - OEM_IMAGE_VERSION_STRING=CRM
[2018-11-13 15:27:44] S - Boot Config, 0x000002e1
[2018-11-13 15:27:44] S - Core 0 Frequency, 0 MHz
[2018-11-13 15:27:44] B - 1547 - PBL, Start
[2018-11-13 15:27:44] B - 3494 - bootable_media_detect_entry, Start
[2018-11-13 15:27:44] B - 140399 - bootable_media_detect_success, Start
[2018-11-13 15:27:44] B - 140403 - elf_loader_entry, Start
[2018-11-13 15:27:44] B - 142717 - auth_hash_seg_entry, Start
[2018-11-13 15:27:44] B - 142929 - auth_hash_seg_exit, Start
[2018-11-13 15:27:44] B - 158719 - elf_segs_hash_verify_entry, Start
[2018-11-13 15:27:44] B - 219686 - PBL, End
[2018-11-13 15:27:44]
[2018-11-13 15:27:44] Format: Log Type - Time(microsec) - Message - Optional Info
[2018-11-13 15:27:44] Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
[2018-11-13 15:27:44] S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00288
[2018-11-13 15:27:44] S - IMAGE_VARIANT_STRING=HAAAANAZA
[2018-11-13 15:27:44] S - OEM_IMAGE_VERSION_STRING=CRM
[2018-11-13 15:27:44] S - Boot Config, 0x000002e1
[2018-11-13 15:27:44] S - Core 0 Frequency, 0 MHz
[2018-11-13 15:27:44] B - 1547 - PBL, Start
[2018-11-13 15:27:44] B - 3494 - bootable_media_detect_entry, Start
[2018-11-13 15:27:44] B - 140387 - bootable_media_detect_success, Start
[2018-11-13 15:27:44] B - 140391 - elf_loader_entry, Start
[2018-11-13 15:27:44] B - 142466 - auth_hash_seg_entry, Start
[2018-11-13 15:27:44] B - 142677 - auth_hash_seg_exit, Start
[2018-11-13 15:27:44] B - 158628 - elf_segs_hash_verify_entry, Start
[2018-11-13 15:27:44] B - 219623 - PBL, End

  • Then I flashed recovery sd image( dragonboard-410c-sdcard-rescue-108 ) and put it in SD card slot and repowered the device, PBL is not restarting, but there is no trace from serial console, but when i ejected the SD card, i found some more interesting logs mentioned below.

[2018-11-13 15:27:45] Format: Log Type - Time(microsec) - Message - Optional Info
[2018-11-13 15:27:45] Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
[2018-11-13 15:27:45] S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00288
[2018-11-13 15:27:45] S - IMAGE_VARIANT_STRING=HAAAANAZA
[2018-11-13 15:27:45] S - OEM_IMAGE_VERSION_STRING=CRM
[2018-11-13 15:27:45] S - Boot Config, 0x000002e1
[2018-11-13 15:27:45] S - Core 0 Frequency, 0 MHz
[2018-11-13 15:27:45] B - 1547 - PBL, Start
[2018-11-13 15:27:45] B - 3495 - bootable_media_detect_entry, Start
[2018-11-13 15:27:45] B - 140376 - bootable_media_detect_success, Start
[2018-11-13 15:27:45] B - 140380 - elf_loader_entry, Start
[2018-11-13 15:27:45] B - 142455 - auth_hash_seg_entry, Start
[2018-11-13 15:27:45] B - 142667 - auth_hash_seg_exit, Start
[2018-11-13 15:27:45] B - 158553 - elf_segs_hash_verify_entry, Start
[2018-11-13 15:27:45] B - 219518 - PBL, End
[2018-11-13 15:27:45] B - 184189 - SBL1, Start
[2018-11-13 15:27:45] B - 235246 - pm_device_init, Start
[2018-11-13 15:27:45] B - 237412 - SPMI Fatal: Timeout while executing SPMI transaction
[2018-11-13 15:27:45] B - 240675 - Error code 302a at boot_error_handler.c Line 466

#2

Can you disable SDCARD BOOT, flash recovery via QDL, and then try to boot in fastboot mode (VOL DOWN while booting).

#3

It looks we damaged the hardware while trying to tap out soldering wires from JTAG test point. Now power manager MCU PM8916 burned out. We have to replace it. How can we identify other parts which got damaged if we replace it?

#4

Predicting what and how a board is broken is difficult. There’s the schematic of course but It is possible you might be better off just getting another board (which you could also use to help debug the first by comparing voltages, etc).