Question Unbrick the realme GT 2 Pro from hard brick (black screen) - Realme GT 2 Pro

Hello.
I tried to completely update the Taiwanese firmware.
Basically I flashed all the images taken from the OTA to my phone using fastboot.
The OTA is from here: https://forum.xda-developers.com/t/global-eu-collection-of-firmware-files.4478153/
As a result i got hard brick (black screen). Device doesn't respond to presses, nothing happens. The computer (Windows 11) doesn't see the device.
I performed the following steps:
Code:
adb shell getprop ro.product.name
RMX3301
adb shell getprop ro.build.version.ota
RMX3301_11.C.16_1160_202303162143
adb shell getprop ro.build.version.realmeui
v4.0
adb shell getprop ro.build.oplus_nv_id
00011010
Download OTA:
Code:
E:\Programs\Python\Python39\python.exe .\realme_ota\main.py RMX3301 RMX3301_11.C.16_1160_202303162143 4 00011010
PS D:\0my\phone\realme gt 2 pro\tools\realme-ota> E:\Programs\Python\Python39\python.exe .\realme_ota\main.py RMX3301 RMX3301_11.C.16_1160_202303162143 4 00011010
[2023-04-18 17:28:19.988575] I: Load payload for RMX3301 (RealmeUI V4)
[2023-04-18 17:28:19.988575] I: Wait for the endpoint to reply
PS D:\0my\phone\realme gt 2 pro\tools\realme-ota> [2023-04-18 17:28:21.363576] I: Load payload for RMX3301 (RealmeUI V4)
[2023-04-18 17:28:21.363576] I: Wait for the endpoint to reply
[2023-04-18 17:28:22.285462] I: All good
[2023-04-18 17:28:22.285462] I: Let's rock
[2023-04-18 17:28:22.285462] I: Party time
{
"aid": "RMX3301NV1A_11.C",
"androidVersion": "Android 13",
"colorOSVersion": "ColorOS 13.0",
"componentAssembleType": true,
"components": [
{
"componentId": "my_manifest_RMX3301_11.C.16_1160_202303162143.1A.6f9e3487",
"componentName": "my_manifest",
"componentPackets": {
"id": "foreign_my_manifest_RMX3301_11.C.16_1160_202303162143.1A.6f9e3487_1_65790f8f58d286c8d65dff0ada40aee7",
"manualUrl": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/18/71792dbf4bd649ff9346667b1f25017a.zip",
"md5": "65790f8f58d286c8d65dff0ada40aee7",
"size": "5871425918",
"type": "1",
"url": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/18/71792dbf4bd649ff9346667b1f25017a.zip",
"vabInfo": {
"data": {
"extra_params": "metadata_hash:0c395f95f20207df32aaff86ff7e7ea393369f87876bafc4e9bc517a30077095",
"header": [
"FILE_HASH=idmYLwxiV6ELPhR0QcUtIc5EldhrilpDXfSet7/lF4U=",
"FILE_SIZE=5871420318",
"METADATA_HASH=Y4t+f+3X/Taw1VUq6GqA2wuGcWLk2PGtT8IFpR5GW5M=",
"METADATA_SIZE=225231",
"security_patch=2023-03-05",
"security_patch_vendor=2023-03-05",
"oplus_update_engine_verify_disable=0",
"ota_target_version=RMX3301_11.C.16_1160_202303162143",
"oplus_rom_version=V13.0.0",
"oplus_separate_soft=216AC"
],
"otaStreamingProperty": "payload_metadata.bin:2053:225498,payload.bin:2053:5871420318,payload_properties.txt:5871422429:357,metadata:69:997,metadata.pb:1134:852",
"vab_package_hash": "65790f8f58d286c8d65dff0ada40aee7"
}
}
},
"componentVersion": "RMX3301_11.C.16_1160_202303162143.1A.6f9e3487"
}
],
"decentralize": {
"offset": 508,
"round": 28800,
"strategyVersion": "default"
},
"description": {
"firstTitle": "This update integrates the latest Android security patches, fixes some known issues, and improves system performance.",
"panelUrl": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/31/06c848b83adf43b9afa0a61c4e6f0d30.html",
"share": ".",
"url": "https://h5fsf.coloros.com/3adb669b49144103b5afb789182233ec/static/index.html#/about"
},
"googlePatchInfo": "0",
"id": "6426c6bf124eec0115884385",
"isNvDescription": true,
"isRecruit": false,
"isSecret": false,
"noticeType": 0,
"nvId16": "NV1A",
"osVersion": "ColorOS 13.0",
"otaVersion": "RMX3301_11.C.16_1160_202303162143",
"paramFlag": 1,
"parent": "ota",
"realAndroidVersion": "Android 13",
"realOsVersion": "ColorOS 13.0.0",
"reminderType": 0,
"rid": "d937f577-0f8f-40f5-8bef-d376dbb8138d",
"securityPatch": "2023-03-05",
"securityPatchVendor": "2023-03-05",
"silenceUpdate": 0,
"status": "published",
"versionCode": 1160,
"versionName": "RMX3301_11_C.16",
"versionTypeH5": "Official version"
}
Flashed all images to phone.
Code:
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash abl abl.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop aop.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop_config aop_config.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash bluetooth bluetooth.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash boot boot.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash cpucp cpucp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash devcfg devcfg.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dsp dsp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dtbo dtbo.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash engineering_cdt engineering_cdt.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash featenabler featenabler.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash hyp hyp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash imagefv imagefv.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash keymaster keymaster.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash modem modem.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_bigball my_bigball.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_carrier my_carrier.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_engineering my_engineering.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_heytap my_heytap.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_manifest my_manifest.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_product my_product.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_region my_region.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_stock my_stock.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm odm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm_dlkm odm_dlkm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplusstanvbk oplusstanvbk.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplus_sec oplus_sec.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash product product.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash qupfw qupfw.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash recovery recovery.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash shrm shrm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash splash splash.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system system.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system_ext system_ext.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash tz tz.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefi uefi.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefisecapp uefisecapp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta vbmeta.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_system vbmeta_system.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_vendor vbmeta_vendor.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor vendor.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_boot vendor_boot.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_dlkm vendor_dlkm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl xbl.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_config xbl_config.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_ramdump xbl_ramdump.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing logs.
Code:
PS C:\Users\PeyVodka> cd D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash abl abl.img
Sending 'abl' (216 KB) OKAY [ 0.009s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop aop.img
Sending 'aop' (256 KB) OKAY [ 0.010s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop_config aop_config.img
Sending 'aop_config' (16 KB) OKAY [ 0.003s]
Writing 'aop_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash bluetooth bluetooth.img
Sending 'bluetooth' (1788 KB) OKAY [ 0.063s]
Writing 'bluetooth' OKAY [ 0.006s]
Finished. Total time: 0.193s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash boot boot.img
Sending 'boot_b' (196608 KB) OKAY [ 6.557s]
Writing 'boot_b' OKAY [ 0.342s]
Finished. Total time: 7.086s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash cpucp cpucp.img
Sending 'cpucp' (152 KB) OKAY [ 0.006s]
Writing 'cpucp' OKAY [ 0.001s]
Finished. Total time: 0.119s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash devcfg devcfg.img
Sending 'devcfg' (56 KB) OKAY [ 0.004s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 2.328s]
Writing 'dsp' OKAY [ 0.188s]
Finished. Total time: 2.627s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.864s]
Writing 'dtbo' OKAY [ 0.076s]
Finished. Total time: 1.044s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash engineering_cdt engineering_cdt.img
Sending 'engineering_cdt' (1024 KB) OKAY [ 0.066s]
Writing 'engineering_cdt' OKAY [ 0.004s]
Finished. Total time: 0.196s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash featenabler featenabler.img
Sending 'featenabler' (92 KB) OKAY [ 0.005s]
Writing 'featenabler' OKAY [ 0.001s]
Finished. Total time: 0.129s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash hyp hyp.img
Sending 'hyp' (1356 KB) OKAY [ 0.057s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash imagefv imagefv.img
Sending 'imagefv' (72 KB) OKAY [ 0.004s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash keymaster keymaster.img
Sending 'keymaster' (360 KB) OKAY [ 0.013s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash modem modem.img
Sending 'modem_b' (296436 KB) OKAY [ 11.736s]
Writing 'modem_b' OKAY [ 0.579s]
Finished. Total time: 12.465s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_bigball my_bigball.img
Sending sparse 'my_bigball' 1/2 (786428 KB) OKAY [ 24.105s]
Writing 'my_bigball' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_carrier my_carrier.img
Sending 'my_carrier' (328 KB) OKAY [ 0.016s]
Writing 'my_carrier' FAILED (remote: '(my_carrier_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_engineering my_engineering.img
Sending 'my_engineering' (328 KB) OKAY [ 0.011s]
Writing 'my_engineering' FAILED (remote: '(my_engineering_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_heytap my_heytap.img
Sending 'my_heytap' (775220 KB) OKAY [ 33.016s]
Writing 'my_heytap' FAILED (remote: '(my_heytap_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_manifest my_manifest.img
Sending 'my_manifest' (404 KB) OKAY [ 0.016s]
Writing 'my_manifest' FAILED (remote: '(my_manifest_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_product my_product.img
Sending 'my_product' (507464 KB) OKAY [ 20.867s]
Writing 'my_product' FAILED (remote: '(my_product_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_region my_region.img
Sending 'my_region' (3544 KB) OKAY [ 0.153s]
Writing 'my_region' FAILED (remote: '(my_region_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_stock my_stock.img
Sending sparse 'my_stock' 1/2 (786428 KB) OKAY [ 24.981s]
Writing 'my_stock' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm odm.img
Sending sparse 'odm' 1/2 (786428 KB) OKAY [ 34.161s]
Writing 'odm' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm_dlkm odm_dlkm.img
Sending 'odm_dlkm' (340 KB) OKAY [ 0.012s]
Writing 'odm_dlkm' FAILED (remote: '(odm_dlkm_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplusstanvbk oplusstanvbk.img
Sending 'oplusstanvbk' (2776 KB) OKAY [ 0.095s]
Writing 'oplusstanvbk' OKAY [ 0.007s]
Finished. Total time: 0.214s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplus_sec oplus_sec.img
Sending 'oplus_sec' (328 KB) OKAY [ 0.012s]
Writing 'oplus_sec' OKAY [ 0.002s]
Finished. Total time: 0.124s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash product product.img
Sending 'product' (12516 KB) OKAY [ 0.465s]
Writing 'product' FAILED (remote: '(product_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash qupfw qupfw.img
Sending 'qupfw' (52 KB) OKAY [ 0.003s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.613s]
Writing 'recovery' OKAY [ 0.176s]
Finished. Total time: 3.905s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash shrm shrm.img
Sending 'shrm' (68 KB) OKAY [ 0.003s]
Writing 'shrm' OKAY [ 0.001s]
Finished. Total time: 0.114s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash splash splash.img
Sending 'splash' (528 KB) OKAY [ 0.018s]
Writing 'splash' OKAY [ 0.002s]
Finished. Total time: 0.131s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system system.img
Sending 'system' (678708 KB) OKAY [ 29.067s]
Writing 'system' FAILED (remote: '(system_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system_ext system_ext.img
Sending sparse 'system_ext' 1/2 (786428 KB) OKAY [ 25.175s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash tz tz.img
Sending 'tz' (3712 KB) OKAY [ 0.133s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefi uefi.img
Sending 'uefi' (3080 KB) OKAY [ 0.133s]
Writing 'uefi' OKAY [ 0.007s]
Finished. Total time: 0.255s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (168 KB) OKAY [ 0.007s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta vbmeta.img
Sending 'vbmeta' (12 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.123s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.127s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_vendor vbmeta_vendor.img
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
Finished. Total time: 0.118s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor vendor.img
Sending 'vendor' (650424 KB) OKAY [ 29.825s]
Writing 'vendor' FAILED (remote: '(vendor_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (196608 KB) OKAY [ 6.615s]
Writing 'vendor_boot' OKAY [ 0.326s]
Finished. Total time: 7.058s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_dlkm vendor_dlkm.img
Sending 'vendor_dlkm' (144052 KB) OKAY [ 5.430s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl xbl.img
Sending 'xbl' (1080 KB) OKAY [ 0.056s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_config xbl_config.img
Sending 'xbl_config' (140 KB) OKAY [ 0.006s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_ramdump xbl_ramdump.img
Sending 'xbl_ramdump' (788 KB) OKAY [ 0.026s]
Writing 'xbl_ramdump' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807>
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (12 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.112s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807>
I took the phone apart and got to the test points as described in this post: https://forum.xda-developers.com/t/solved-edl-test-points.4471613/#post-87186865
To short-circuit them and put them into EDL Mode.
I checked the voltage with a voltmeter, it is ~1.8v and 0v. Everything seems to be fine and should work.
But my device is still not detected by the computer (Windows 11).
Any idea how to solve this problem?
I'm not sure what the exact cause is. I didn't think that flashing all the firmware images would be a very bad idea. And as far as I know EDL mode should remain available for me in any case.
And what could be causing the problem?
The only thing that seems strange from flashing logs is that this time boot was written to boot_b for some reason. Before that it usually went to boot_a. I'm not sure if this could have corrupted boot.

---

Okay. I was able to put the device into EDL mode. I soldered the test points to short it. Because the device seems to exit EDL mode every few seconds. Exactly as noted in these messages:
[Solved] EDL test points
Hi guys, i am looking for some help as my Realme GT2 Pro is dead bricked (ie. no response to buttons + usb) I was able to open the back cover but i am not sure which are the correct test points for EDL mode. Below is the picture of the...
forum.xda-developers.com
[Solved] EDL test points
Hi guys, i am looking for some help as my Realme GT2 Pro is dead bricked (ie. no response to buttons + usb) I was able to open the back cover but i am not sure which are the correct test points for EDL mode. Below is the picture of the...
forum.xda-developers.com
So, I got the firware RMX3301export_11_A.06_2022020500280000 from https://realmefirmware.com/realme-gt-2-pro-firmware/
What do I have to do next to flash the device free of charge myself?

---

A bit late now, but if you have a chance it's helpful to make a backup copy before you go flashing.
If your Firehose loader for EDL is unrestricted you can do it as a whole device and/or by partition.
Did you try before: fastboot flashing unlock_critical
Have you got a Firehose loader and gotten an EDL client to work yet? (Either the Python or mine.)

---

Renate said:
A bit late now, but if you have a chance it's helpful to make a backup copy before you go flashing.
If your Firehose loader for EDL is unrestricted you can do it as a whole device and/or by partition.
Did you try before: fastboot flashing unlock_critical
Have you got a Firehose loader and gotten an EDL client to work yet? (Either the Python or mine.)
Click to expand...
Click to collapse
I have no access to fastboot. Fastboot does not see my device after it became a hard brick.
I have not tried Firehose or other EDL clients. I tried opening QFIL. There I see that my device is recognized as qualcomm hs-usb qdloader 9008.
I have no idea what to do next.

---

I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My stuff is in my sig.

---

Renate said:
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
View attachment 5892303
My stuff is in my sig.
Click to expand...
Click to collapse
Okay. I'm going to try bkerler's Python now.
How do I see the solution to my problem:
1. I need to overwrite boot.img in boot_a with the command "edl w boot_a boot.img".
I believe that after that I will transfer my device to soft brick state and be able to boot into recovery mode.
2. In recovery mode, I will be able to use fastboot with my unlocked bootloader to flash the device normally.
Is my plan viable?

---

PeyVodka said:
Is my plan viable?
Click to expand...
Click to collapse
Sure.
Still, flashing with EDL, fastboot, dd, whatever all do the same stuff.

---

Renate said:
Sure.
Still, flashing with EDL, fastboot, dd, whatever all do the same stuff.
Click to expand...
Click to collapse
I'm a little confused trying to install bkerler's edl on Windows 11:
I am following the installation instructions for windows.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Code:
PS D:\Download\Browser\firmware\edl-3.52.1\edl-3.52.1> python3 setup.py build
running build
running build_py
running egg_info
writing edl.egg-info\PKG-INFO
writing dependency_links to edl.egg-info\dependency_links.txt
writing requirements to edl.egg-info\requires.txt
writing top-level names to edl.egg-info\top_level.txt
reading manifest file 'edl.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*' under directory 'Loaders'
adding license file 'LICENSE'
writing manifest file 'edl.egg-info\SOURCES.txt'
running build_scripts
error: file 'D:\Download\Browser\firmware\edl-3.52.1\edl-3.52.1\Loaders\fhloaderparse.py' does not exist
There are no loaders for realme in the repository. What is this loader, where can I get the loader in my case?
GitHub - bkerler/Loaders: EDL Loaders
EDL Loaders. Contribute to bkerler/Loaders development by creating an account on GitHub.
github.com

---

PeyVodka said:
I'm a little confused trying to install bkerler's edl on Windows 11:
Click to expand...
Click to collapse
Lol. Now you know why I wrote a native Windows version.
I have less dependencies and admittedly, less features.

---

Renate said:
Lol. Now you know why I wrote a native Windows version.
I have less dependencies and admittedly, less features.
Click to expand...
Click to collapse
Yes, I understand. In general, the situation is familiar to me.
Will this allow me to overwrite boot_a with boot.img from OTA firmware according to my plan?
How to do this with your tool?
Is it:
Code:
edl.exe /w /pboot_a boot.img
In this case, I will be happy to use your tool.
EDL Utility

---

PeyVodka said:
Is it:
Click to expand...
Click to collapse
Yup, that should do it.
You'll need a Firehose loader.
There might be one in the QFIL stuff.
There might be one in the bkerler GitHub.
Identify what you've got with edl.exe /l

---

Renate said:
Yup, that should do it.
You'll need a Firehose loader.
There might be one in the QFIL stuff.
There might be one in the bkerler GitHub.
Identify what you've got with edl.exe /l
Click to expand...
Click to collapse
Okay.
I reinstalled driver for my device via Zadig.
Downloaded your tool and execute:
Code:
PS D:\Download\Browser\firmware> .\edl.exe /l
Found EDL 9008
Serial: $SERIAL$
Received unexpected 04 command
PS D:\Download\Browser\firmware> .\edl.exe /l
Found EDL 9008
Resetting Sahara
Could not read device
Did i do something wrong?

---

PeyVodka said:
Did i do something wrong?
Click to expand...
Click to collapse
That all looks good.
The Sahara protocol is very brittle (and stupid).
If an attempt at communication has occured but failed, the device will be in la-la land.
Do a clean reset.
(Which is what edl.exe was trying to do, but the implementations of Sahara are all different.)
Actually, it could be flakey communication too. Check your cables and ports.
Edit: Mmm, it could be that this needs some authorization.
In which case you can only do this with the RealMe tools.
You should try the bkerler too. You can leave it on Zadig for that.

---

Renate said:
That all looks good.
The Sahara protocol is very brittle (and stupid).
If an attempt at communication has occured but failed, the device will be in la-la land.
Do a clean reset.
(Which is what edl.exe was trying to do, but the implementations of Sahara are all different.)
Actually, it could be flakey communication too. Check your cables and ports.
Edit: Mmm, it could be that this needs some authorization.
In which case you can only do this with the RealMe tools.
You should try the bkerler too. You can leave it on Zadig for that.
Click to expand...
Click to collapse
I tried bkerler edl on Ubuntu. It got stuck on this message:
Code:
edl --serial
Capstone library is missing (optional).
Keystone library is missing (optional).
No module named 'Cryptodome'
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Trying with no loader given ...
main - Waiting for the device
Detected 0x5c6:0x9008 device at: /dev/ttyUSB0
main - Device detected :)
sahara - Protocol version: 3, Version supported: 1
main - Mode detected: sahara
"it could be that this needs some authorization."
Could this have something to do with the information in this post?:
[No auth collection] Realme No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Realme has blocked offline flashing with authentication required to flash their device. This files will ultimately help you to fix the authorisation issue and hence unbrick your Realme device via EDL mode...
forum.xda-developers.com

---

PeyVodka said:
It got stuck on this message
Click to expand...
Click to collapse
Normally you should be able to get beyond this point with any device.
The authorization comes in Firehose, not Sahara.
Could you try (after a reset): edl.exe /l /v
See, a custom PBL would be unexpected thing.

---

Your tool.
I've tried several times, it keeps giving these messages one after another.
Code:
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Found EDL 9008
USB maximum packet: in=512, out=512
Received 01 command
Received 0b command
Received 0e command
Serial: $SERIAL$
Received 04 command
Sahara exec command 2 unsupported
Received 04 command
Received unexpected 04 command
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Found EDL 9008
USB maximum packet: in=512, out=512
Resetting Sahara
Could not read device
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Could not find EDL device
Here I was told that there is currently no Firehose for my device.
[No auth collection] Realme No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Realme has blocked offline flashing with authentication required to flash their device. This files will ultimately help you to fix the authorisation issue and hence unbrick your Realme device via EDL mode...
forum.xda-developers.com

---

Renate said:
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
View attachment 5892303
My stuff is in my sig.
Click to expand...
Click to collapse
By the they, how do I roll back the changes made by Zadig? From WinUSB.sys driver to qcusbser.sys
UPD: Ok. I've just deleted it via Windows Device Manager.

---

PeyVodka said:
Code:
Sahara exec command 2 unsupported
Click to expand...
Click to collapse
Well, that is strange. I've run into that before on some other Chinese stuff.
Apparently they never burned a HWID or disabled the querying of it.
I'm quite sure that Qualcomm would never make a custom PBL for anybody.
I don't know if they disabled querying of the hash too.

---

Everyone, support this post on realme's website. Let's make Realme release private recovery tools via EDL mode to the public!
So we can experiment with our purchased devices and not pay money for something we could always do for free!
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com

---

Renate said:
Well, that is strange. I've run into that before on some other Chinese stuff.
Apparently they never burned a HWID or disabled the querying of it.
I'm quite sure that Qualcomm would never make a custom PBL for anybody.
I don't know if they disabled querying of the hash too.
Click to expand...
Click to collapse
My dear friend and g0d-tier researcher M3ik Shizuka was able to "spell" offline access to both obfuscated tools. I couldn't believe my eyes.
Indeed, now that I connected my device in MsmDownloadTool, it stopped exiting EDL mode every few seconds. However, to enter EDL mode, I still had to solder test points. According to the status information and logs, I was finally able to connect via Sahara.
Unfortunately, for some stages of verification and data download, the MsmDownloadTool requires authorization with the servers. Apparently, MsmDownloadTool is really the official leaked tool.
Realme Login Tool makes a GET request to check the OPT code on api2.realmelogin.com.
I am not competent in this, but I hope that knowledgeable people can figure out from the log if there is anything useful that we can learn from sniffing the COM port. So that we can eventually use this to interact with the device via EDL mode with other tools.
MsmDownloadTool logs:
Code:
=========================================================
| Msm Download Tool V2.0.67 for eMMC/UFS
|
| Build Data: Nov 2 2021
| Build Time: 20:12:20
=========================================================
[PID:10472] [TID:15296] [2023-04-21 21:16:32::0323] Start log...
[PID:10472] [TID:15296] [2023-04-21 21:16:32::0468] mac:MAC_ADDRESS
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0680] Path:D:\RMX3301export_11_A.06_2022020500280000\RMX3301export_11_A.06_2022020500280000.ofp
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0804] Project:PROJECT_CODE, Compatible:
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0805] Strorage type: UFS
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Mode:After-sales
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Filter Metadata is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Binding Metadata is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Download Config is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Download Config Signed is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Support Reset is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Cloud Flag is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Multi Project is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Erase Oder is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] WO3 is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] UFS is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] SV is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] NV is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] VC is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] OCDT is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Root is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Secsmt is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Support FC is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] -------------------
[PID:10472] [TID:11916] [2023-04-21 21:19:47::0425] Device Remove: \\?\USB#VID_05C6&PID_9008...
[PID:10472] [TID:11916] [2023-04-21 21:20:28::0540] Device Arrival: \\?\USB#VID_05C6&PID_9008...
[PID:10472] [TID:11916] [2023-04-21 21:20:28::0541] Friendly Name: Qualcomm HS-USB QDLoader 9008 (COM5)
[PID:10472] [TID:15296] [2023-04-21 21:20:35::0046] Click Button Refresh
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0202] Click Button Start, mode:After-sale, project:PROJECT_CODE
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] IsPackImage is true
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] FactoryLine is false
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] BootOnly is false
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] DisableBootWizard is false
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Download start
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Set download status ,current status: COM_DOWNLOAD.
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Open the serial device
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Open the serial device retry = 1
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0239] [COM5] Set Sahara file ok��sahara file: prog_firehose_ddr.elf.
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0254] [COM5] Attempting to send a Sahara message for communication
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0254] [COM5] Downloading Firehose protocol file via Sahara protocol
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0811] [COM5] Sahara communication succeeded
[PID:10472] [TID:13348] [2023-04-21 21:20:51::0138] [COM5] filename=ChainedTableOfDigests_PROJECT_CODE_persist_no_userdata_no
[PID:10472] [TID:13348] [2023-04-21 21:20:52::0166] [COM5] Trying to handshake via Firehose communication
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0294] [COM5] Configure the settings of Firehose communication data transmission
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0389] [COM5] Get sign data
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0574] [COM5] ID:CHIP_ID, B:enable
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0574] [COM5] old_sw_name_sign:OLD_SW_NAME_SIGN, new_sw_name_sign:NEW_SW_NAME_SIGN
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0575] [COM5] Verify Data
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0361] [COM5] FirehoseCheckRSP is ERROR, hr=1
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0361] [COM5] Rsp:
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: verify failed." /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0362] [COM5] Verify pass
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0363] [COM5] Current download task end,elapsed time:416s.
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0363] [COM5] Upload download result. chip id: CHIP_ID, result: 1, project: PROJECT_CODE
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0373] [COM5] Upload download result failed.
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0373] [COM5] Close the serial device
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] Download failed
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] Determine whether to upload the download info
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] compress file, retry time is 4
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0514] [COM5] compress file success
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0515] [COM5] start to upload
[PID:10472] [TID:15296] [2023-04-21 21:28:49::0756] Click Button Stop