[GUIDE] How to dump and write back the storage on most of Qualcomm devices

[Renate]

Unless your file is a zip or something there is no conversion necessary or possible.
What do you have? Post it publicly or priately.

 

[kjullian19]

This is the file I have. QFIL only accepts .elf or .mbn files. If there's no conversion possible, how could I load the programmer?

 

[Renate]

This is the file I have. QFIL only accepts .elf or .mbn files.

It's a perfectly fine Firehose loader.
Just rename it .elf
Or use an EDL client that isn't so picky on stupid stuff.
Like the Python EDL client. Or mine.

 

[kjullian19]

It's a perfectly fine Firehose loader.
Just rename it .elf
Or use an EDL client that isn't so picky on stupid stuff.
Like the Python EDL client. Or mine.

Thanks Renate. I tried to proceed with it. The "partial success" log mentioned in the post shows up:

2023-03-22 10:29:18.787    10:29:18: Sahara protocol completed
2023-03-22 10:29:18.787    Sending Programmer Finished
2023-03-22 10:29:18.788    Switch To FireHose
2023-03-22 10:29:18.788    Wait for 3 seconds...

So I think you were right, the firehose file works. But then I get the following error, and the Partition Manager doesn't open. (Log Attached)

2023-03-22 10:29:21.799    Skip Write:False
2023-03-22 10:29:21.800    Always Validate:False
2023-03-22 10:29:21.800    Use Verbose:False
2023-03-22 10:29:21.802    ***** Working Folder:C:\Users\kandr\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2023-03-22 10:29:21.802    Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified
2023-03-22 10:29:21.808    Finish Get GPT

Do you or anyone else have solved this error in the past, and managed to get Partition Manager to open?

 

[Renate]

If you use Windows you can try my native Windows EDL client (in the sig).

C:\>edl /l000a50e100514985_2acf3a85fde334e2_fhprg_op7t-bin
C:\>edl /g
C:\>edl /u /g

 

[kjullian19]

I'll give your EDL client a try thanks. Do I need to change the driver or is the one from this guide okay?

EDIT: I managed to get the partition manager working, and got Start LBA 0x00479676 and LBA Number 0x0184C185. Added together it gives 0x01CC57FB or 30,169,083.

Spoiler: Old Log

I ran the command to dump, changed it to my needs, and this is the most recent log, it has been running for 15 minutes now:

AppData\Roaming\Qualcomm\QFIL\COMPORT_6>"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM6 --search_path=C:\oneplusdump --convertprogram2read --sendimage=full_dump.bin --start_sector=0 --lun=0 --num_sectors=30169083 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs

Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02

12:00:11: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM6 --search_path=C:\oneplusdump --convertprogram2read --sendimage=full_dump.bin --start_sector=0 --lun=0 --num_sectors=30169083 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
************************************************

12:00:11: INFO: Current working dir (cwd): C:\Users\kandr\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\
12:00:11: INFO: Showing network mappings to allow debugging
12:00:11: INFO: Looking for file 'full_dump.bin'


(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/


12:00:11: WARNING: Couldn't find the file 'full_dump.bin', returning NULL


(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/


12:00:11: WARNING: User specified --num_sectors=30169083 but file only has 30169083 sectors. **Ignoring --num_sectors


12:00:11: INFO: User wants to talk to port '\\.\COM6'
12:00:11: INFO: Took 0.00000000 seconds to open port
12:00:11: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
12:00:11: INFO: If you don't want this, use --dontsorttags

12:00:11: INFO: Looking for file 'full_dump.bin'


(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/


12:00:11: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
12:00:11: INFO: Sending <configure>

12:00:11: INFO: TARGET SAID: 'Storage type set to value UFS'
12:00:11: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
12:00:11: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
12:00:11: INFO: In handleRead('full_dump.bin')
12:00:11: INFO: Looking for file 'full_dump.bin'


(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/


12:00:11: WARNING: Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'C:\Users\kandr\AppData\Roaming\Qualcomm\QFIL\COMPORT_6\full_dump.bin'
12:00:11: INFO: =======================================================
12:00:11: INFO: <read> (120676332.0KB) 30169083 sectors from location 0 FILE: 'full_dump.bin'
12:00:11: INFO: =======================================================

12:00:13: INFO: Overall to target 2.000 seconds (105.30 MBps)
12:00:15: INFO: Overall to target 4.000 seconds (105.50 MBps)
12:00:17: INFO: Overall to target 6.000 seconds (105.79 MBps)
12:00:19: INFO: Overall to target 8.000 seconds (105.75 MBps)
12:00:21: INFO: Overall to target 10.000 seconds (101.01 MBps)
12:00:23: INFO: Overall to target 12.000 seconds (99.42 MBps)
12:00:25: INFO: Overall to target 14.000 seconds (98.41 MBps)
12:00:27: INFO: Overall to target 16.000 seconds (96.69 MBps)
12:00:29: INFO: Overall to target 18.000 seconds (95.56 MBps)
12:00:31: INFO: Overall to target 20.000 seconds (94.45 MBps)
12:00:33: INFO: Overall to target 22.000 seconds (93.63 MBps)
12:00:35: INFO: Overall to target 24.000 seconds (93.63 MBps)
(Repeats every 2 seconds...)

Does anyone know where this error may be coming from? Is it safe to stop the process or disconnect my device?

 

[kjullian19]

Last question. I have the full_dump.img file now, and I tried using 7-zip to extract my (user)data. The file is 115 GB which is in line with phone's storage, but it only extracts to a 7.6MB folder. How can I actually access the userdata?

 

[Renate]

Doing a full raw dump is only useful as a snapshot.
If you want to backup useful data you'll have to backup files when userdata is mounted (and decrypted) by the system.

 

[kjullian19]

Thanks for the clarification there. You've been super helpful all around!

 

[marc.2377]

Doing a full raw dump is only useful as a snapshot.
If you want to backup useful data you'll have to backup files when userdata is mounted (and decrypted) by the system.

Renate: Do you know of a way to decrypt offline, i.e. from a PC?

 

[Renate]

Renate: Do you know of a way to decrypt offline, i.e. from a PC?

No, I don't know how to decrypt offline.
The whole point of encryption is to make that difficult.

 

[Isrgish]

Thanks for this great guide.

My Partition Manager results seems to have 2 separate last partitions. Which numbers should I use to get the number of sectors to use? There is a partition called "ALIGN_TO_128K_2" which starts again from 0x06. Should I calculate the numbers from both last partitions separately and then combine them to get my number?

My device is UFS, should I change the `--memoryname=emmc` to `--memoryname=ufs`?

I'm attaching my Partition list file.

 

[Renate]

My Partition Manager results seems to have 2 separate last partitions.

No, it actually has 4.
That's just unused space at the end of each unit. There could be 6.

My device is UFS, should I change the `--memoryname=emmc` to `--memoryname=ufs`?

Yes

 

[Isrgish]

No, it actually has 4.
That's just unused space at the end of each unit. There could be 6.

I'm not clear how to calculate the number of sectors I should use.

Am I only looking for the dump of the partitions of LUN 0? (This seems to be what the OP is using since the command has --lun=0).
Wouldn't I need ALL partitions to be able to restore my device?
What are the other LUN's?

 

[Renate]

I'm not sure about the Python EDL client, but with mine you can just do:

C:\>edl.exe /r /u0 unit0.img

You don't have to count sectors.

 

[Isrgish]

I'm not sure about the Python EDL client, but with mine you can just do:

C:\>edl.exe /r /u0 unit0.img

You don't have to count sectors.

Will this get all the sectors from all the parts (LUNs)?

How do I connect to the device using your program? I tried edl.exe /I just to see if it works but I get error no device found.

 

[Renate]

Will this get all the sectors from all the parts (LUNs)?

If you have UFS and 6 LUNs you will need to do 6 separate operations.
Th /u specifies which LUN, obviously the output files should be different.

... I get error no device found.

QFIL only uses the bogus Qualcomm driver.
The Python EDL client can use the Qualcomm driver or generic WinUsb driver (installed by Zadig).
My native Windows EDL client only uses WinUsb driver. See the documentation.

 

[Isrgish]

QFIL only uses the bogus Qualcomm driver.
The Python EDL client can use the Qualcomm driver or generic WinUsb driver (installed by Zadig).
My native Windows EDL client only uses WinUsb driver. See the documentation.

Will I need to uninstall the dricers I currently have insralled? Will QFIL be able to use the WinUSB driver?

 

[Renate]

Will I need to uninstall the drivers I currently have installed?

Installing new drivers replaces old drivers.

Will QFIL be able to use the WinUSB driver?

QFIL only uses the bogus Qualcomm driver.

 

[Isrgish]

Installing new drivers replaces old drivers.

Thanks for all your help.