Device Stuck on Logo After Flashing Firmware via EDL (QFIL)

[support4sanva]

I recently flashed firmware to my device using EDL mode with QFIL, edl qfil rawprogram0.xml patch0.xml . However, after flashing, the device gets stuck on the manufacturer's logo during boot.

I am wondering if this issue is due to a problem with the firmware itself or if I might have missed specifying the correct loader or some other critical step.

Interestingly, when I flash only boot.img or recovery.img individually, they seem to work and produce some effect.

Has anyone encountered this issue before? Any guidance or suggestions would be greatly appreciated!

[support4sanva]

Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2024.
main - Using loader /Users/md/github/edl/Loaders/qualcomm/factory/sdm845_sdm850_sda845/6000000000010000_f8ab20526358c4fa_fhprg.bin ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
sahara -
Version 0x2
------------------------
HWID:              0x0008b0e100000000 (MSM_ID:0x0008b0e1,OEM_ID:0x0000,MODEL_ID:0x0000)
CPU detected:      "SDM845"
PK_HASH:           0xafca69d4235117e5bfc21467068b20df85e0115d7413d5821883a6d244961581
Serial:            0x718f3155

sahara - Protocol version: 2, Version supported: 1
sahara - Uploading loader /Users/md/github/edl/Loaders/qualcomm/factory/sdm845_sdm850_sda845/6000000000010000_f8ab20526358c4fa_fhprg.bin ...
sahara - 64-Bit mode detected.
sahara - Firehose mode detected, uploading...
sahara - Loader successfully uploaded.
main - Trying to connect to firehose loader ...
firehose - INFO: Binary build date: Oct 16 2018 @ 15:29:37
firehose - INFO: Binary build date: Oct 16 2018 @ 15:29:37
firehose - INFO: Chip serial num: 1905209685 (0x718f3155)
firehose - INFO: Supported Functions (14):
firehose - INFO: program
firehose - INFO: read
firehose - INFO: nop
firehose - INFO: patch
firehose - INFO: configure
firehose - INFO: setbootablestoragedrive
firehose - INFO: erase
firehose - INFO: power
firehose - INFO: firmwarewrite
firehose - INFO: getstorageinfo
firehose - INFO: benchmark
firehose - INFO: emmc
firehose - INFO: ufs
firehose - INFO: fixgpt
firehose - INFO: End of supported functions 14
firehose_client
firehose_client - [LIB]: No --memory option set, we assume "UFS" as default ..., if it fails, try using "--memory" with "UFS","NAND" or "spinor" instead !
firehose
firehose - [LIB]: Couldn't detect MaxPayloadSizeFromTargetinBytes
firehose
firehose - [LIB]: Couldn't detect TargetName
firehose - TargetName=Unknown
firehose - MemoryName=UFS
firehose - Version=1
firehose - Trying to read first storage sector...
firehose - Running configure...
firehose - Storage report:
firehose - total_blocks:61258752
firehose - block_size:4096
firehose - page_size:4096
firehose - num_physical:6
firehose - manufacturer_id:462
firehose - serial_num:1297306958
firehose - fw_version:500
firehose - mem_type:UFS
firehose - prod_name:KLUEG8U1EA-B0C1
firehose_client - Supported functions:
-----------------
program,read,nop,patch,configure,setbootablestoragedrive,erase,power,firmwarewrite,getstorageinfo,benchmark,emmc,ufs,fixgpt
firehose_client - [qfil] raw programming...
firehose_client - [qfil] programming rawprogram0.xml
firehose_client - [qfil] programming ./cache.img to partition(0)@sector(8200)...
QCSparse - Sparse Format detected. Using unpacked image.
firehose -
Writing to physical partition 0, sector 8200, sectors 65536
modules
modules - [LIB]: 'Logger' object has no attribute 'loglevel'
Progress: |██████████| 100.0% Write (Sector 0x10000 of 0x10000, ) 30.41 MB/s
firehose_client - [qfil] programming ./recovery.img to partition(0)@sector(73992)...
firehose -
Writing to physical partition 0, sector 73992, sectors 16384
Progress: |██████████| 100.0% Write (Sector 0x4000 of 0x4000, ) 31.25 MB/s
firehose_client - [qfil] programming ./system.img to partition(0)@sector(90632)...
QCSparse - Sparse Format detected. Using unpacked image.
firehose -
Writing to physical partition 0, sector 90632, sectors 1048576
Progress: |██████████| 100.0% Write (Sector 0xFFE00 of 0x100000, ) 29.58 MB/s
Progress: |██████████| 100.0% Write (Sector 0xFFF00 of 0x100000, ) 29.67 MB/s
Progress: |██████████| 100.0% Write (Sector 0x100000 of 0x100000, ) 30.75 MB/s
firehose_client - [qfil] programming ./userdata.img to partition(0)@sector(1139208)...
QCSparse - Sparse Format detected. Using unpacked image.
firehose -
Writing to physical partition 0, sector 1139208, sectors 28311552
Progress: |██--------|  17.1% Write (Sector 0x49A800 of 0x1B00000, 51m:37s left) 30.96 MB/s

This is the result after adding the loader. It seems there is no noticeable difference. Could someone help me check if everything looks normal in the logs? Even without adding the loader, the commands also execute successfully.