Help xiaomi poco f1 cant flash

xenxu92

Junior Member
Jul 6, 2021
4
0
spain
xiaomi poco f1 cant flash
Firmware package: beryllium_global_images_V12.0.3.0.QEJMIXM_20201227.0000.00_10.0_global_f4a9dbd1d3
Scanning for Qualcomm HS-USB QDLoader 9008 device...
Download Port: Qualcomm HS-USB QDLoader 9008 (COM5)
Connection status: XHCI:HUB3:[#0]:USB 2.00 High-Speed
USB Driver: [Qualcomm Incorporated] qcusbser, version: 2.1.2.7, date: 8-2-2017
Initializing...
MSM Serial number: 0x7a1b641b
MSM HW ID: 0x0008b0e1 (SDM845), OEM ID: 0x0072 (Xiaomi), MODEL ID: 0x0000
OEM Public Key Hash: c924a35f39ce1cdd1b8d5a9f3b8e3c51317930431d7a9dd5a55028cf6965fe65
SBL SW version: 1
Firehose: prog_ufs_firehose_sdm845_ddr[2].elf
hash: fb3c858504d781b0fcbd86a556d55276ec213a22, size: 702.79 KiB
oem version: c4-miui-ota-bd48.bj
qc version: BOOT.XF.2.0-00389-SDM845LZB-1.258085.1
variant: SDM845LA
Loading firehose... Done
Handshaking...
ERROR: Call to ufs_open(0, UFS_WLUN_DEVICE) failed:0
Sending ping... Done
INFO: Binary build date: Dec 27 2020 12:56:12
INFO: Chip serial num: 2048615451 (0x7a1b641b)
Sending configurations...
Requesting flash signature from server...
[SERVER] XIAOMI_FL [beryllium,7a1b641b] cost: 0, your balance: 25
This authorization request was handled free of charge for a limited time.
MemoryName: UFS
DateTime: Dec 27 2020 - 12:56:12
Version: 1
ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0
ERROR: Failed to open the device:3 slot:0 partition:0 error:0
ERROR: OPEN handle NULL and no error, weird 344577508
ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3
Failed to configure device for UFS, retrying to configure for eMMC storage instead...
MemoryName: eMMC
DateTime: Dec 27 2020 - 12:56:12
Version: 1
ERROR: Failed to open the SDCC Device slot 1 partition 0
ERROR: Failed to open the device:1 slot:1 partition:0 error:0
ERROR: OPEN handle NULL and no error, weird 344577508
ERROR: Failed to open device, type:eMMC, slot:1, lun:0 error:3
 

GhunzMR

Active Member
Jul 30, 2018
18
3
Tanjung Priuk
Sonork ID
0
variant 64? this case happens a lot with damaged ufs


the best solution is to replace ufs with cpu
 

Attachments

  • IMG_20210801_143616.jpg
    IMG_20210801_143616.jpg
    399.5 KB · Views: 38
Top