write_gpt_partition_error

[bentalebnordine]

log.txt

hi gays; I tryed to write gpt partition but I failed;

~/edl$ edl w gpt gpt_main0.bin --memory=ufs --lun=4 Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) main - Mode detected: firehose modules modules - [LIB]: 'Logger' object has no attribute 'loglevel' Done |----------| 0.0% Write (Sector 0x0 of 0x6) 0.00 MB/s Wrote gpt_main0.bin to sector 0. thanks.

[RenateUSB]

We have no idea what happened. We need a log or something.

[bentalebnordine]

We have no idea what happened. We need a log or something.

The only log I have is this, is there any other log I can retrieve, thanks for replying to my issue, appreciate it.

[RenateUSB]

Add --debugmode to the command. It will write a log into a subdirectory "logs" that you will probably have to create first.

When things are wacky you shouldn't be writing. You should be reading until you are sure what is going on.

[bentalebnordine]

Add --debugmode to the command. It will write a log into a subdirectory "logs" that you will probably have to create first.

When things are wacky you shouldn't be writing. You should be reading until you are sure what is going on.

Thank you, I will.

[bentalebnordine]

Add --debugmode to the command. It will write a log into a subdirectory "logs" that you will probably have to create first.

When things are wacky you shouldn't be writing. You should be reading until you are sure what is going on.

here is the log my friend; thank you in advance

log.txt

[RenateUSB]

There are so many things wrong here.

First, as I said, when you don't know what's going on, you should be trying reads not writes. "Yeah, but I don't need to read!" Yes, you should read so that you have a backup when you realize later what you wrote was wrong. You should read to check basic functionality. Reads do no harm. Writes brick your device.

I will never understand the logs from this piece of software. It seems the prime purpose is to obfuscate. Why is one log (version 3.62):

main - Device detected :)
DeviceClass
DeviceClass - [LIB]: ?[95mread:0x30?[0m

And another log (also version 3.62) is:

read:0x70
['  File "/usr/local/bin/edl", line 4, in <module>\n    __import__(\'pkg_resources\').run_script(\'edlclient==3.62\', \'edl\')\n', '  File "/home/bentalebnordine/.local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 752, in run_script\n    self.require(requires)[0].run_script(script_name, ns)\n', '  File "/home/bentalebnordine/.local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 1739, in run_script\n    exec(code, namespace, namespace)\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 393, in <module>\n    base.run()\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 290, in run\n    conninfo = self.doconnect(loop)\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 222, in doconnect\n    resp = self.sahara.connect()\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/edlclient/Library/sahara.py", line 136, in connect\n    res = self.cdc.read(timeout=1)\n']
RX:<?xml version="1.0" encoding="UTF-8" ?>
RX:<data>

(And needlessly splitting up the XML.)

Apparently you are trying to write 128 kB to LUN 4. Why? 32 blocks of 4096? MBR + GPT header + GPT entries is 6 blocks of 4096. What are you doing here? Why? Why do you even think that LUN 4 needs repartitioning? How the heck big is this "gpt_main0.bin"? There is no way that it should be bigger than 24kB

[bentalebnordine]

There are so many things wrong here.

First, as I said, when you don't know what's going on, you should be trying reads not writes. "Yeah, but I don't need to read!" Yes, you should read so that you have a backup when you realize later what you wrote was wrong. You should read to check basic functionality. Reads do no harm. Writes brick your device.

I will never understand the logs from this piece of software. It seems the prime purpose is to obfuscate. Why is one log (version 3.62):

main - Device detected :)
DeviceClass
DeviceClass - [LIB]: ?[95mread:0x30?[0m

And another log (also version 3.62) is:

read:0x70
['  File "/usr/local/bin/edl", line 4, in <module>\n    __import__(\'pkg_resources\').run_script(\'edlclient==3.62\', \'edl\')\n', '  File "/home/bentalebnordine/.local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 752, in run_script\n    self.require(requires)[0].run_script(script_name, ns)\n', '  File "/home/bentalebnordine/.local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 1739, in run_script\n    exec(code, namespace, namespace)\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 393, in <module>\n    base.run()\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 290, in run\n    conninfo = self.doconnect(loop)\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 222, in doconnect\n    resp = self.sahara.connect()\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/edlclient/Library/sahara.py", line 136, in connect\n    res = self.cdc.read(timeout=1)\n']
RX:<?xml version="1.0" encoding="UTF-8" ?>
RX:<data>

(And needlessly splitting up the XML.)

Apparently you are trying to write 128 kB to LUN 4. Why? 32 blocks of 4096? MBR + GPT header + GPT entries is 6 blocks of 4096. What are you doing here? Why? Why do you even think that LUN 4 needs repartitioning? How the heck big is this "gpt_main0.bin"? There is no way that it should be bigger than 24kB

Thank you so much.

[RenateUSB]

Please post this gpt_main0.bin

Are you using the stock Qualcomm Window driver or the WinUsb driver installed using Zadig? No, this won't make a difference in how this works but it could help the legibility of the log.

This is one of the obtuse Firehose loaders that ignores LUN number on getstorageinfo.

You may have broken provisioning or write protection on this LUN. It's hard to tell. As I said (a few times already) try reading. edl printgpt

[bentalebnordine]

There are so many things wrong here.

First, as I said, when you don't know what's going on, you should be trying reads not writes. "Yeah, but I don't need to read!" Yes, you should read so that you have a backup when you realize later what you wrote was wrong. You should read to check basic functionality. Reads do no harm. Writes brick your device.

I will never understand the logs from this piece of software. It seems the prime purpose is to obfuscate. Why is one log (version 3.62):

main - Device detected :)
DeviceClass
DeviceClass - [LIB]: ?[95mread:0x30?[0m

And another log (also version 3.62) is:

read:0x70
['  File "/usr/local/bin/edl", line 4, in <module>\n    __import__(\'pkg_resources\').run_script(\'edlclient==3.62\', \'edl\')\n', '  File "/home/bentalebnordine/.local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 752, in run_script\n    self.require(requires)[0].run_script(script_name, ns)\n', '  File "/home/bentalebnordine/.local/lib/python3.12/site-packages/pkg_resources/__init__.py", line 1739, in run_script\n    exec(code, namespace, namespace)\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 393, in <module>\n    base.run()\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 290, in run\n    conninfo = self.doconnect(loop)\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/EGG-INFO/scripts/edl", line 222, in doconnect\n    resp = self.sahara.connect()\n', '  File "/usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/edlclient/Library/sahara.py", line 136, in connect\n    res = self.cdc.read(timeout=1)\n']
RX:<?xml version="1.0" encoding="UTF-8" ?>
RX:<data>

(And needlessly splitting up the XML.)

Apparently you are trying to write 128 kB to LUN 4. Why? 32 blocks of 4096? MBR + GPT header + GPT entries is 6 blocks of 4096. What are you doing here? Why? Why do you even think that LUN 4 needs repartitioning? How the heck big is this "gpt_main0.bin"? There is no way that it should be bigger than 24kB

I am trying to write gpt partition because when I try to write any other partition it says partition not found. The problem is that I tried to flash my phone with MSM tool (download button enabled) the tool started the provisioning but it stopped, it said target id should not be 0.

[RenateUSB]

... the tool started the provisioning but it stopped

OMG, you provisioned your device? Smacks forehead.

When you're neck-deep in mud you should definitely stop digging.

Why don't you answer my questions? I asked you to post this gpt file. I asked you to tell me which Windows loader you were using. I asked you to do a simple edl printgpt.

[bentalebnordine]

... the tool started the provisioning but it stopped

OMG, you provisioned your device? Smacks forehead.

When you're neck-deep in mud you should definitely stop digging.

Why don't you answer my questions? I asked you to post this gpt file. I asked you to tell me which Windows loader you were using. I asked you to do a simple edl printgpt.

Nothing, it writes nothing in the commands : printgpt, r , the only commands that work is r/w gpt(when w it writes nothing) and qfil also work (but writes nothing) Here is the gptmain0.bin file https://drive.google.com/file/d/1y_azLSoOX3fcqV3WxckN4s88nlrp-dJr/view?usp=drive_link

I relyesd that I was wrong writing gptmain0.bin file to lun4, instead of lun0

[RenateUSB]

You realized that it was the wrong LUN? This is how people get in trouble.

And as I said enough times already, don't even try to write until you know what's going on.

Sheesh. Do this.

edl rs 0 6 --lun=0 g0.img --memory=ufs
edl rs 0 6 --lun=1 g1.img --memory=ufs
edl rs 0 6 --lun=2 g2.img --memory=ufs
edl rs 0 6 --lun=3 g3.img --memory=ufs
edl rs 0 6 --lun=4 g4.img --memory=ufs
edl rs 0 6 --lun=5 g5.img --memory=ufs

[bentalebnordine]

You realized that it was the wrong LUN? This is how people get in trouble.

And as I said enough times already, don't even try to write until you know what's going on.

Sheesh. Do this.

edl rs 0 6 --lun=0 g0.img --memory=ufs
edl rs 0 6 --lun=1 g1.img --memory=ufs
edl rs 0 6 --lun=2 g2.img --memory=ufs
edl rs 0 6 --lun=3 g3.img --memory=ufs
edl rs 0 6 --lun=4 g4.img --memory=ufs
edl rs 0 6 --lun=5 g5.img --memory=ufs

Thank you very much, the reason I am always late to reply to you because I don't have a computer, I use VM machine to run Ubuntu on windows in a cyber café, thanks again

[RenateUSB]

Sorry, I know this is difficult.

Can't you just run the Python under Windows?

Zip up those six files if you can get them and post them. If something won't run get a log.

[bentalebnordine]

You realized that it was the wrong LUN? This is how people get in trouble.

And as I said enough times already, don't even try to write until you know what's going on.

Sheesh. Do this.

edl rs 0 6 --lun=0 g0.img --memory=ufs
edl rs 0 6 --lun=1 g1.img --memory=ufs
edl rs 0 6 --lun=2 g2.img --memory=ufs
edl rs 0 6 --lun=3 g3.img --memory=ufs
edl rs 0 6 --lun=4 g4.img --memory=ufs
edl rs 0 6 --lun=5 g5.img --memory=ufs

here is the output: https://drive.google.com/file/d/1TFH30vb8646ZhJ39PwNUo-2VVNgxIkIE/view?usp=drive_link

[bentalebnordine]

You realized that it was the wrong LUN? This is how people get in trouble. And as I said enough times already, don't even try to write until you know what's going on. Sheesh. Do this.

edl rs 0 6 --lun=0 g0.img --memory=ufs
edl rs 0 6 --lun=1 g1.img --memory=ufs
edl rs 0 6 --lun=2 g2.img --memory=ufs
edl rs 0 6 --lun=3 g3.img --memory=ufs
edl rs 0 6 --lun=4 g4.img --memory=ufs
edl rs 0 6 --lun=5 g5.img --memory=ufs

here is the output: https://drive.google.com/file/d/1TFH30vb8646ZhJ39PwNUo-2VVNgxIkIE/view?usp=drive_link

Itried to write back the file g0.img but I failed: bentalebnordine@bentalebnordine:~/edl$ edl w gpt g0.img --memory=ufs --lun=0 /usr/local/bin/edl:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import('pkg_resources').run_script('edlclient==3.62', 'edl') Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2024. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) main - Mode detected: firehose modules modules - [LIB]: 'Logger' object has no attribute 'loglevel' Done |----------| 0.0% Write (Sector 0x0 of 0x6) 0.00 MB/s Wrote g0.img to sector 0. bentalebnordine@bentalebnordine:~/edl$ edl w PrimaryGPT g0.img --memory=ufs --lun=0 /usr/local/bin/edl:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import('pkg_resources').run_script('edlclient==3.62', 'edl') Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2024. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) main - Mode detected: firehose firehose_client firehose_client - [LIB]: Error: Couldn't detect partition: PrimaryGPT Available partitions:

[bentalebnordine]

Sorry, I know this is difficult.

Can't you just run the Python under Windows?

Zip up those six files if you can get them and post them. If something won't run get a log.

and this files are extracted by msm tool readback option. https://drive.google.com/file/d/1bRk_XiVs9qLsx5xhWxYF2J7rYHIIw27v/view?usp=drive_link msm tool can read partitions but edl master can't isn't virde!.thank you my friend.

[RenateUSB]

Didn't I say something about not writing?

The MSM tool are giving the same files. 99% empty.

Apparently you don't have any partitioning on any of your LUNs. How did you do that?

[bentalebnordine]

Didn't I say something about not writing?

The MSM tool are giving the same files. 99% empty.

Apparently you don't have any partitioning on any of your LUNs. How did you do that?

I activated the download button on the msm flash tool as the last resort, the tool said provisioning ufs but I don't know the stage it arrives at, so may be you're right, the tool erased the existing partitions and do not arrive to repartition the device. But there is a thing, when activating the readback option the tool succeed to pull all the partitions as IMGs, including super, boot and recovery. I appreciate your patience with me my friend, thank you so much for helping me.

[RenateUSB]

And did you check super, boot and recovery to see if they were real stuff?

You should really stick to one tool. Don't just push buttons on things.

Do you have real copies of the GPTs and the backup GPTs and know where they go?

[bentalebnordine]

And did you check super, boot and recovery to see if they were real stuff?

You should really stick to one tool. Don't just push buttons on things.

Do you have real copies of the GPTs and the backup GPTs and know where they go?

Next time I will pull all the partitions and tell you about their size, I did pull out the boot partition and it's real (98,xxxx mb)

[bentalebnordine]

And did you check super, boot and recovery to see if they were real stuff?

You should really stick to one tool. Don't just push buttons on things.

Do you have real copies of the GPTs and the backup GPTs and know where they go?

I did pulled out all partitions (11.2GB) but it seems all empty (when checked with the hex editor)i am really shocked. I can tell you that I flashed all these stuff with fastbootd hopping that the phone will be converted from t-mobile to cyberpunck but it failed to boot. is there any thing I can do about this mess. thank you for your assistance appreciate it

[RenateUSB]

When you say that you pulled all the partitions, what tool were you using? Pulling partitions without partitioning is only possible when making presumptions.

[bentalebnordine]

When you say that you pulled all the partitions, what tool were you using? Pulling partitions without partitioning is only possible when making presumptions.

I used msm tool read back option

[bentalebnordine]

When you say that you pulled all the partitions, what tool were you using? Pulling partitions without partitioning is only possible when making presumptions.

my friend , when starting teminal it says firehose - [LIB]: Couldn't detect TargetName firehose - TargetName=Unknown is'nt it the whole problem here bentalebnordine@bentalebnordine:~/edl$ edl gpt . --genxml --memory=ufs /usr/local/bin/edl:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import('pkg_resources').run_script('edlclient==3.62', 'edl') Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2024. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) sahara - Protocol version: 2, Version supported: 1 main - Mode detected: sahara sahara - Version 0x2

HWID: 0x000c30e100514d6d (MSM_ID:0x000c30e1,OEM_ID:0x0051,MODEL_ID:0x4d6d) CPU detected: "SM8250:CD90-PH805-1A" PK_HASH: 0x7c15a98db4e70963715f51c8da39c1e66fc1c3334e95f4c6a5627da6a49c842f06b43e8de1f589fc36ce1135c7fa5aa2 Serial: 0xdb543462

sahara - Detected loader: /usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/edlclient/../Loaders/oneplus/000c30e100514d6d_7c15a98db4e70963_fhprg_op8_op8tmo_op8t_op8ttmo.bin sahara - Protocol version: 2, Version supported: 1 sahara - Uploading loader /usr/local/lib/python3.12/dist-packages/edlclient-3.62-py3.12.egg/edlclient/../Loaders/oneplus/000c30e100514d6d_7c15a98db4e70963_fhprg_op8_op8tmo_op8t_op8ttmo.bin ... sahara - 64-Bit mode detected. sahara - Firehose mode detected, uploading... sahara - Loader successfully uploaded. main - Trying to connect to firehose loader ... firehose - Binary build date: Sep 18 2020 @ 11:44:21 firehose - Binary build date: Sep 18 2020 @ 11:44:21 firehose - Chip serial num: 3679728738 (0xdb543462) firehose - Supported Functions (24): firehose - program firehose - read firehose - nop firehose - patch firehose - configure firehose - setbootablestoragedrive firehose - erase firehose - power firehose - firmwarewrite firehose - getstorageinfo firehose - benchmark firehose - emmc firehose - ufs firehose - fixgpt firehose - getsha256digest firehose - gethwversion firehose - getrfversion firehose - getprjversion firehose - eraseuserdata firehose - sha256init firehose - sha256final firehose - demacia firehose - setprojmodel firehose - getddrtype firehose - End of supported functions 24 firehose - ERROR: 0x1370 r_data:0x20 firehose - ERROR: 0x1342 r_data:0x1 firehose - ERROR: 0x1366 r_data:0x3 firehose - ERROR: 0x1365 r_data:0xb5 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 - {'ERROR': '[ffu]FWversion', 'UFS fInitialized': '0x1', 'UFS Current LUN Number: ': ' 0xd0', 'UFS Total Active LU': '0x6', 'UFS wManufacturerID': '0x1ce', 'UFS Boot Partition Enabled': '0x1', 'UFS Raw Device Capacity: ': ' 0x1dcbc000', 'UFS Min Block Size': '0x8', 'UFS Erase Block Size': '0x2000', 'UFS Allocation Unit Size': '0x1', 'UFS RPMB ReadWrite Size: ': ' 0x40', 'UFS Number of Allocation Uint for This LU': '0x0', 'UFS Logical Block Size': '0x0', 'UFS Provisioning Type': '0x0', 'UFS LU Write Protect': '0x0', 'UFS Boot LUN ID: ': ' 0x0', 'UFS Memory Type': '0x0', 'UFS LU Total Blocks': '0x0', 'UFS Supported Memory Types': '0x800f', 'UFS dEnhanced1MaxNAllocU': '0xee5e', 'UFS wEnhanced1CapAdjFac': '0x300', 'UFS dEnhanced2MaxNAllocU: ': ' 0x0', 'UFS wEnhanced2CapAdjFac': '0x0', 'UFS dEnhanced3MaxNAllocU': '0x0', 'UFS wEnhanced3CapAdjFac': '0x0', 'UFS dEnhanced4MaxNAllocU': '0x0', 'UFS wEnhanced4CapAdjFac': '0x0', 'UFS LUN Enable Bitmask': '0x3f', 'UFS Logical Block Count': '0x0', 'UFS bConfigDescrLock': '0x0', 'UFS iManufacturerName String Index': '0x0', 'UFS iProductName String Index': '0x1', 'UFS iSerialNumber String Index': '0x2', 'UFS iOemID String Index': '0x3', 'UFS_High_Priority_LUN': '0x0', 'UFS Inquiry Command Output': 'SAMSUNG KLUEG8UHDB-C2D1 1302 '} firehose - {'ERROR': '[ffu]FWversion', 'UFS fInitialized': '0x1', 'UFS Current LUN Number: ': ' 0xd0', 'UFS Total Active LU': '0x6', 'UFS wManufacturerID': '0x1ce', 'UFS Boot Partition Enabled': '0x1', 'UFS Raw Device Capacity: ': ' 0x1dcbc000', 'UFS Min Block Size': '0x8', 'UFS Erase Block Size': '0x2000', 'UFS Allocation Unit Size': '0x1', 'UFS RPMB ReadWrite Size: ': ' 0x40', 'UFS Number of Allocation Uint for This LU': '0x0', 'UFS Logical Block Size': '0x0', 'UFS Provisioning Type': '0x0', 'UFS LU Write Protect': '0x0', 'UFS Boot LUN ID: ': ' 0x0', 'UFS Memory Type': '0x0', 'UFS LU Total Blocks': '0x0', 'UFS Supported Memory Types': '0x800f', 'UFS dEnhanced1MaxNAllocU': '0xee5e', 'UFS wEnhanced1CapAdjFac': '0x300', 'UFS dEnhanced2MaxNAllocU: ': ' 0x0', 'UFS wEnhanced2CapAdjFac': '0x0', 'UFS dEnhanced3MaxNAllocU': '0x0', 'UFS wEnhanced3CapAdjFac': '0x0', 'UFS dEnhanced4MaxNAllocU': '0x0', 'UFS wEnhanced4CapAdjFac': '0x0', 'UFS LUN Enable Bitmask': '0x3f', 'UFS Logical Block Count': '0x0', 'UFS bConfigDescrLock': '0x0', 'UFS iManufacturerName String Index': '0x0', 'UFS iProductName String Index': '0x1', 'UFS iSerialNumber String Index': '0x2', 'UFS iOemID String Index': '0x3', 'UFS_High_Priority_LUN': '0x0', 'UFS Inquiry Command Output': 'SAMSUNG KLUEG8UHDB-C2D1 1302 '} firehose - 0x1 firehose_client - Supported functions:

program,read,nop,patch,configure,setbootablestoragedrive,erase,power,firmwarewrite,getstorageinfo,benchmark,emmc,ufs,fixgpt,getsha256digest,gethwversion,getrfversion,getprjversion,eraseuserdata,sha256init,sha256final,demacia,setprojmodel,getddrtype,ERROR: 0x1370 r_data:0x20,ERROR: 0x1342 r_data:0x1,ERROR: 0x1366 r_data:0x3,ERROR: 0x1365 r_data:0xb5,demacia,setprojmodel bentalebnordine@bentalebnordine:~/edl$ thanks.

[RenateUSB]

Try the other loader: https://github.com/bkerler/Loaders/blob/main/oppo/0000000000514d6d_7c15a98db4e70963_fhprg.bin

Post the response in lines with triple backquotes.

Like this

[bentalebnordine]

Try the other loader: https://github.com/bkerler/Loaders/blob/main/oppo/0000000000514d6d_7c15a98db4e70963_fhprg.bin

Post the response in lines with triple backquotes.

Like this

'''the log is attached'''

log.txt

[RenateUSB]

Which loader were you using? This one requires image verification.

[bentalebnordine]

Which loader were you using? This one requires image verification.

I used the one you attached to the reply oppo...

[RenateUSB]

Neither of the Firehose loaders are working.

The first log you posted shows a strange error and it doesn't seem able to accept the LUN parameter.

--> <getstorageinfo physical_partition_number="0"/>
<-- <log value="ERROR: [ffu]FWversion:302." />
<-- <log value="UFS fInitialized: 0x1" />
<-- <log value="UFS Current LUN Number: = 0xd0" />

The first Firehose loader fails but does't say why. (Also, you were flashing 32 sectors instead of 6.)

--> <program SECTOR_SIZE_IN_BYTES="4096" num_partition_sectors="32" physical_partition_number="4" start_sector="0" />
<-- <response value="NAK" rawmode="false" />

The second Firehose loader fails and seems to want verified images.

--> <program SECTOR_SIZE_IN_BYTES="4096" num_partition_sectors="6" physical_partition_number="4" start_sector="0" />
<-- <log value="ERROR: Validate image failed. 1:2" />
<-- <response value="NAK" rawmode="false" />

I don't know if I can suggest anything further. I would like to know where that LUN parameter bug is coming from. I've seen it elsewhere.