Related
Anyone Rooted update to the new HTC EVO 4G LTE updated to 1.22.651.3 ?
gomfam said:
Anyone Rooted update to the new HTC EVO 4G LTE updated to 1.22.651.3 ?
Click to expand...
Click to collapse
I have been trying to update since last night to no avail... I keep getting a failure notice "Error Flashing zip /sdcard/ext_sd/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.652.3-1.13" once I try to install it with the Team recovery app.
Cybnex said:
I have been trying to update since last night to no avail... I keep getting a failure notice "Error Flashing zip /sdcard/ext_sd/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.652.3-1.13" once I try to install it with the Team recovery app.
Click to expand...
Click to collapse
I was finally able to update
gomfam said:
I was finally able to update
Click to expand...
Click to collapse
How did you do it. I am unable to update
I'm with you guys. When I try to update I get this from TeamWinRecovery's error log:
/sdcard/Download/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268352pdwvnjlt5q0w5qsi.zip ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
Installing update...
script aborted: assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"SPCS_001") == "t"
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" , "22222222" , "33333333" , "44444444" , "55555555" , "66666666" , "77777777" , "88888888" , "99999999" , "SPCS_001") == "t"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p35 | ext4 | 1277951 | 926668 | 1 | f |
| data | /dev/block/mmcblk0p37 | ext4 | 2260991 | 550776 | 1 | f |
| boot | /dev/block/mmcblk0p21 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p36 | ext4 | 229375 | 4260 | 1 | f |
| sdcard2 | /dev/block/mmcblk1p1 | vfat | 7768064 | 4882560 | 1 | n |
| sdcard | /dev/block/mmcblk0p38 | vfat | 10418176 | 2442368 | 1 | n |
| andsec | /sdcard | vfat | 32 | 32 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
Error flashing zip '/sdcard/Download/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268352pdwvnjlt5q0w5qsi.zip'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
The best option right now is to download and flash either the odexed or deodexed version of the Rooted Stock ROM, which can be found here on xda - http://forum.xda-developers.com/showthread.php?t=1766628
Hey Guys! I was wondering what the heck factory mode is because every time my phone turns on it always starts up with it. I have no lock screen and when I hold the home button it pretty much just powers of without any confirmation. Anyone know how to get out of it? I have been stuck on this got a while, searching everywhere and I already got into trouble because if the power off sound going on in my bag.
Extra Info:
Device is working. Stock Rom. If an sdcard is needed I have a 16gb one.
On the hsome screen it shows the system information. No WiFi.
Have you done anything at all to the phone or is it stock? Root, etc., you know what I mean.
Sent from my SCH-I535 using xda premium
The problem is in the data contained in the file "/efs/FactoryApp/factorymode"
This may seem counter-intuitive, but the proper value is "ON". (without the quotes)
I think you'll need to root to be able to edit it.
EDIT: I ought to say this is my best guess - I haven't seen this problem myself and the stuff I found about this related to a different variant of the GS3 than ours.
x-y-no said:
The problem is in the data contained in the file "/efs/FactoryApp/factorymode"
This may seem counter-intuitive, but the proper value is "ON". (without the quotes)
I think you'll need to root to be able to edit it.
EDIT: I ought to say this is my best guess - I haven't seen this problem myself and the stuff I found about this related to a different variant of the GS3 than ours.
Click to expand...
Click to collapse
Thanks Bro! This seemed to work for me and my friend who's in sprint.
Excellent! Glad it worked for you.
Not working for me
Unfortunately this method:
echo -n ON > /efs/FactoryApp/factorymode
didn't work for me on my SCH-i535 (Verizon, US, latest stock jellybean, rooted of course). I solved an earlier problem where I had to rebuild my EMEI since I hosed my efs directory and did not have a backup - So phone and data works but I'm still stuck in Factory Mode. updated factorymode every which way possible. Here is a directory snapshot of my /efs folder (if someone who has a virgin efs could compare I would greatly appreciate it (some file and dir names obscured for security purposes)
/efs
|-- FactoryApp
| |-- baro_delta
| |-- factorymode
| |-- factorymode.bak
| |-- fdata
| |-- hist_nv
| |-- hw_ver
| |-- keystr
| |-- prepay
| |-- serial_no
| `-- test_nv
|-- bluetooth
| `-- bt_addr
|-- drm
| |-- dxhdcp2
| | `-- acGS***************e1aFGgUxE_
| | |-- et********************hEQM_
| | `-- zttE**************************RZM_
| |-- h2k
| | `-- 8tjf**************************fZTU_
| | |-- HA*******************************hE_
| | `-- S*****************************FM_
| |-- playready
| | |-- 00002.PRV
| | |-- EFPJyjN***********************S8_
| | | |-- -lndc*******************************QU_
| | | |-- 13*******************************9Pvc_
| | | |-- 2a8*******************************yqY_
| | | |-- 39*******************************Bss_
| | | |-- 39j-*******************************FY_
| | | |-- A*******************************zFwI_
| | | |-- fi*******************************Ms_
| | | |-- g2*******************************ij5w_
| | | |-- m*******************************u4M_
| | | |-- o*******************************FYw+ik_
| | | |-- sA*******************************a6Kc_
| | | |-- wH*******************************Dz4_
| | | `-- xm*******************************OFiI_
| | |-- bdevcert.dat
| | |-- devcert.dat
| | `-- license.hds
| `-- widevine
| `-- 5*******************************2K5InM_
| |-- D3*******************************434rc_
| `-- RX*******************************Bq8_
|-- h2k.dat
|-- imei
| `-- mps_code.dat
|-- nv.log
|-- sensors
|-- wifi
`-- wv.keys
14 directories, 38 files
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode.
To make sure this guide will work as expect, following requirements are needed:
- Know how to trigger the phone to EDL mode, and you can force reboot the phone (Required for Driver Changing)
- Qualcomm EDL mode doesn't require service authentication, or specially modded (e.g. Lumia Emergency Files)
- Firehose file for your SoC and storage type (eMMC or UFS storage)
- Latest Qualcomm USB Drivers (at least 2.1.2.0 or newer, you can check yourself in Device Manager) and QPST Tool
Driver version is pretty important. If older than 2.1.2.0, it won't support partition dumping properly.
You may need to reboot your Windows PC to Disable Driver Signature Enforcement mode to allow you use the driver.
I won't provide any download link of the proper drivers, please find yourself.
Click to expand...
Click to collapse
For non-Android Smartphones, HP Elite X3 (At least for prototype unit) is confirmed working with this method.
Most of Android Smartphones should work as well.
Step 1: Trigger the phone to EDL mode
Following methods can be used as reference:
- Connect your phone to PC with a specific key pressed
e.g. TCL / Alcatel / Blackberry Android Smartphones can use Volume Down key to trigger to EDL mode
- EDL cable (DIY or order it on eBay / AliExpress, keyword: Xiaomi EDL cable)
e.g. Smartisan Smartphones that made recently can use EDL cable to unlock the bootloader.
- Fastboot command
e.g. Few Xiaomi Phones
- Wire trick
If you know where's the test point / components (like resistant) on CLK pin of eMMC/UFS storage is connected as well, short it to the GND will trigger your phone to EDL mode.
This will be usable for almost every Qualcomm devices, once you have schematic provided by the manufacturer.
- Erase aboot / abl / xbl / UEFI from your phone
This method is dangerous, do it at your own risk!
Step 2: Change the Driver to Qualcomm HS-USB QDLoader 9008
Skip this step if it's already indicated as HS-USB QDLoader 9008 in Device Manager, "Ports (COM or LPT)" category.
If it's indicated as HS-USB Diagnostics 9008 in "Ports (COM or LPT)" category, or "QHSUSB__BULK" in "Universal Serial Bus devices" category, you must update the driver to Qualcomm HS-USB QDLoader 9008, then reboot your phone to Qualcomm EDL mode again to ensure the EDL port will not throttle.
To reboot your phone, you need to perform hard reboot until you see the port disappeared immediately or refresh (in case the phone is bricked).
Step 3: Open QFIL, load Firehose file
You must choose correct storage type in right down corner.
In many cases keep it as "emmc" for default, otherwise choose "ufs" for flagship devices. In this case we choose emmc.
Then choose "Flat Build" as Build Type, and select the firehose file for your phone. If there's no firehose file specifically for your device, you may want to choose another firehose file for the same SoC, same storage type for different phone.
For example, I used the "prog_emmc_firehose_8996_ddr.elf" for ZUK Z2 on HP Elite X3 and it works perfectly.
In many cases, you can obtain firehose file for your phone from stock firmware.
Click to expand...
Click to collapse
Step 4: Open Partition Manager
Now choose "Tools" - "Partition Manager", and please pay attention to the Status box.
When it indicates:
Code:
2019-07-18 20:04:19.775 20:04:19: Sahara protocol completed
2019-07-18 20:04:19.776 Sending Programmer Finished
2019-07-18 20:04:19.776 Switch To FireHose
2019-07-18 20:04:19.777 Wait for 3 seconds...
If you didn't see the output above, then the firehose file is incorrect or the EDL port is throttled. Reboot your phone to EDL mode again.
Then you've partially succeeded, just wait for the Partition Manager appears.
This is the partition table of your phone. Please take note on the Start LBA and LBA number of the last partition.
Take HP Elite X3 partition table for example, the last partition is "Data", it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors. Multiple the sector numbers with 512 will get the total bytes of the eMMC storage, in this case, the capacity of eMMC storage is 62,537,055,744 bytes.
You'll need the number 122,142,687 for later use.
If you don't want to dump userdata partition, just use the Start LBA value of userdata partition and convert it to decimal values - the overall dump will not contain actual userdata.
Don't close Partition Manager, we need to keep it for later use.
Now choose either Step 5A or 5B as your wish.
Step 5A: Dump the storage
Please copy following path to your File Explorer:
Code:
%AppData%\Qualcomm\QFIL
This will redirect you to C:\Users\[your_user_name]\AppData\Roaming\Qualcomm\QFIL .
Find the COMPORT_XX directory respective to your exact COM port - in this case, I choose COMPORT_8 for example.
And open a command prompt or PowerShell window here.
Execute following command here, remember to change the COM port number and num_sectors to your exact number, or the actual path of fh_loader.exe and your dump if possible:
Note, this command will not create the path of your dump for you, you must create yourself.
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\your\dump --convertprogram2read --sendimage=full_dump.bin --start_sector=0 --lun=0 --num_sectors=122142687 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Now just wait for dumping procedure complete.
Expected output should look like this:
Code:
20:45:50: INFO: Current working dir (cwd): C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\
20:45:50: INFO: Showing network mappings to allow debugging
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: User specified --num_sectors=524288 but file only has 524288 sectors. **Ignoring --num_sectors
20:45:50: INFO: User wants to talk to port '\\.\COM8'
20:45:50: INFO: Took 0.00000000 seconds to open port
20:45:50: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
20:45:50: INFO: If you don't want this, use --dontsorttags
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
20:45:50: INFO: Sending <configure>
20:45:50: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
20:45:50: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
20:45:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
20:45:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
20:45:50: INFO: In handleRead('full_dump.bin')
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'full_dump.bin'
20:45:50: INFO: =======================================================
20:45:50: INFO: <read> (262144.0KB) 524288 sectors from location 0 FILE: 'full_dump.bin'
20:45:50: INFO: =======================================================
20:45:52: INFO: Overall to target 2.000 seconds (32.34 MBps)
20:45:54: INFO: Overall to target 4.000 seconds (32.38 MBps)
20:45:56: INFO: Overall to target 6.000 seconds (32.37 MBps)
20:45:58: INFO: Overall to target 7.844 seconds (32.64 MBps)
20:45:58: INFO: TARGET SAID: 'Finished reading from sector address 0 to 524288'
20:45:58: INFO: =======================================================
20:45:58: INFO: ===================== SUCCESS =========================
20:45:58: INFO: =======================================================
20:45:58: INFO: ==============================================================
20:45:58: INFO: Files used and their paths
20:45:58: INFO: 1 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
20:45:58: INFO: 2 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:58: INFO: ==============================================================
20:45:58: INFO: NOTE: There were WARNINGS!! Repeated here, but please see log for more detail
Couldn't find the file 'full_dump.bin', returning NULL
User specified --num_sectors=524288 but file only has 524288 sectors. **Ignoring --num_sectors
Couldn't find the file 'full_dump.bin', returning NULL
Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'full_dump.bin'
NOTE: There were WARNINGS!! Repeated above, but please see log for more detail
20:45:58: INFO: ==============================================================
20:45:58: INFO: _ (done)
20:45:58: INFO: | |
20:45:58: INFO: __| | ___ _ __ ___
20:45:58: INFO: / _` |/ _ \| '_ \ / _ \
20:45:58: INFO: | (_| | (_) | | | | __/
20:45:58: INFO: \__,_|\___/|_| |_|\___|
20:45:58: INFO: {All Finished Successfully}
20:45:58: INFO: Overall to target 7.969 seconds (32.12 MBps)
Writing log to 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt', might take a minute
Log is 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
You can use 7-Zip archiver to open this dump and extract any partition you want.
Step 5B: Write the dump back to storage
Open Partition Manager, and don't close it.
Please copy following path to your File Explorer:
Code:
%AppData%\Qualcomm\QFIL
This will redirect you to C:\Users\[your_user_name]\AppData\Roaming\Qualcomm\QFIL .
Find the COMPORT_XX directory respective to your exact COM port - in this case, I choose COMPORT_8 for example.
And open a command prompt or PowerShell window here.
Execute following command here, remember to change the COM port number and num_sectors to your exact number, or the actual path of fh_loader.exe and your dump if possible:
In this case, the dump is located at D:\path\to\your\dump\full_dump.bin .
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\your\dump --sendimage=full_dump.bin --start_sector=0 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Now just wait for the procedure complete.
The output should look like this:
Code:
20:05:30: INFO: Current working dir (cwd): C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\
20:05:30: INFO: Showing network mappings to allow debugging
20:05:30: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO: User wants to talk to port '\\.\COM8'
20:05:31: INFO: Took 0.01600000 seconds to open port
20:05:31: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
20:05:31: INFO: If you don't want this, use --dontsorttags
20:05:31: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO:
Total to be tansferd with <program> or <read> is 36.09 GB
20:05:31: INFO: Sending <configure>
20:05:31: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
20:05:31: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
20:05:31: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
20:05:31: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
20:05:31: INFO: In handleProgram('full_dump.bin')
20:05:31: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO: =======================================================
20:05:31: INFO: {<program> FILE: 'D:\path\to\your\dump\full_dump.bin'}
20:05:31: INFO: {<program> (36.09 GB) 75685888 sectors needed at location 0 on LUN 0}
20:05:31: INFO: =======================================================
20:05:31: INFO: TARGET SAID: 'start 0, num 75685888'
20:05:33: INFO: Overall to target 2.031 seconds (26.59 MBps)
20:05:33: INFO: {percent files transferred 0.15%}
20:05:35: INFO: Overall to target 4.063 seconds (26.34 MBps)
20:05:35: INFO: {percent files transferred 0.29%}
20:05:37: INFO: Overall to target 6.094 seconds (26.26 MBps)
20:05:37: INFO: {percent files transferred 0.43%}
20:05:39: INFO: Overall to target 8.110 seconds (26.26 MBps)
20:05:39: INFO: {percent files transferred 0.58%}
20:05:41: INFO: Overall to target 10.125 seconds (26.27 MBps)
20:05:41: INFO: {percent files transferred 0.72%}
20:05:43: INFO: Overall to target 12.141 seconds (26.27 MBps)
20:05:43: INFO: {percent files transferred 0.86%}
20:05:45: INFO: Overall to target 14.141 seconds (26.31 MBps)
20:05:45: INFO: {percent files transferred 1.01%}
20:05:47: INFO: Overall to target 16.156 seconds (26.49 MBps)
20:05:47: INFO: {percent files transferred 1.16%}
20:05:49: INFO: Overall to target 18.172 seconds (26.52 MBps)
20:05:49: INFO: {percent files transferred 1.30%}
20:05:51: INFO: Overall to target 20.188 seconds (26.55 MBps)
20:05:51: INFO: {percent files transferred 1.45%}
20:05:53: INFO: Overall to target 22.188 seconds (26.59 MBps)
20:05:53: INFO: {percent files transferred 1.60%}
20:05:55: INFO: Overall to target 24.188 seconds (26.62 MBps)
20:05:55: INFO: {percent files transferred 1.74%}
20:05:57: INFO: Overall to target 26.188 seconds (26.62 MBps)
20:05:57: INFO: {percent files transferred 1.89%}
20:05:59: INFO: Overall to target 28.188 seconds (26.61 MBps)
20:05:59: INFO: {percent files transferred 2.03%}
20:06:01: INFO: Overall to target 30.235 seconds (26.59 MBps)
20:06:01: INFO: {percent files transferred 2.18%}
20:06:03: INFO: Overall to target 32.266 seconds (26.56 MBps)
20:06:03: INFO: {percent files transferred 2.32%}
20:06:05: INFO: Overall to target 34.281 seconds (26.57 MBps)
20:06:05: INFO: {percent files transferred 2.47%}
20:06:07: INFO: Overall to target 36.328 seconds (26.56 MBps)
20:06:07: INFO: {percent files transferred 2.61%}
20:06:09: INFO: Overall to target 38.328 seconds (26.56 MBps)
20:06:09: INFO: {percent files transferred 2.75%}
20:06:11: INFO: Overall to target 40.360 seconds (26.56 MBps)
20:06:11: INFO: {percent files transferred 2.90%}
20:06:13: INFO: Overall to target 42.391 seconds (26.56 MBps)
20:06:13: INFO: {percent files transferred 3.05%}
(ignored too many logs)
20:28:17: INFO: Overall to target 1366.235 seconds (26.33 MBps)
20:28:17: INFO: {percent files transferred 97.33%}
20:28:19: INFO: Overall to target 1368.266 seconds (26.33 MBps)
20:28:19: INFO: {percent files transferred 97.48%}
20:28:21: INFO: Overall to target 1370.281 seconds (26.33 MBps)
20:28:21: INFO: {percent files transferred 97.63%}
20:28:23: INFO: Overall to target 1372.313 seconds (26.33 MBps)
20:28:23: INFO: {percent files transferred 97.78%}
20:28:25: INFO: Overall to target 1374.313 seconds (26.33 MBps)
20:28:25: INFO: {percent files transferred 97.93%}
20:28:27: INFO: Overall to target 1376.344 seconds (26.34 MBps)
20:28:27: INFO: {percent files transferred 98.08%}
20:28:29: INFO: Overall to target 1378.344 seconds (26.34 MBps)
20:28:29: INFO: {percent files transferred 98.22%}
20:28:31: INFO: Overall to target 1380.360 seconds (26.34 MBps)
20:28:31: INFO: {percent files transferred 98.37%}
20:28:33: INFO: Overall to target 1382.375 seconds (26.34 MBps)
20:28:33: INFO: {percent files transferred 98.51%}
20:28:35: INFO: Overall to target 1384.406 seconds (26.34 MBps)
20:28:35: INFO: {percent files transferred 98.66%}
20:28:37: INFO: Overall to target 1386.438 seconds (26.34 MBps)
20:28:37: INFO: {percent files transferred 98.80%}
20:28:39: INFO: Overall to target 1388.438 seconds (26.34 MBps)
20:28:39: INFO: {percent files transferred 98.94%}
20:28:41: INFO: Overall to target 1390.453 seconds (26.34 MBps)
20:28:41: INFO: {percent files transferred 99.09%}
20:28:43: INFO: Overall to target 1392.485 seconds (26.34 MBps)
20:28:43: INFO: {percent files transferred 99.25%}
20:28:45: INFO: Overall to target 1394.516 seconds (26.34 MBps)
20:28:45: INFO: {percent files transferred 99.40%}
20:28:47: INFO: Overall to target 1396.531 seconds (26.34 MBps)
20:28:47: INFO: {percent files transferred 99.55%}
20:28:49: INFO: Overall to target 1398.750 seconds (26.33 MBps)
20:28:49: INFO: {percent files transferred 99.66%}
20:28:51: INFO: Overall to target 1400.766 seconds (26.33 MBps)
20:28:51: INFO: {percent files transferred 99.81%}
20:28:53: INFO: Overall to target 1402.797 seconds (26.33 MBps)
20:28:53: INFO: {percent files transferred 99.96%}
20:28:54: INFO: Overall to target 1403.422 seconds (26.33 MBps)
20:28:54: INFO: {percent files transferred 100.00%}
20:28:54: INFO: TARGET SAID: 'Finished programming start_sector 75685888 and TotalSectorsToProgram 75685888'
20:28:54: INFO:
20:28:54: INFO: =======================================================
20:28:54: INFO: ==================== {SUCCESS} ========================
20:28:54: INFO: =======================================================
20:28:54: INFO: {percent files transferred 100.00%}
20:28:54: INFO: ==============================================================
20:28:54: INFO: Files used and their paths
20:28:54: INFO: 1 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
20:28:54: INFO: 2 'D:\path\to\your\dump\full_dump.bin'
20:28:54: INFO: _ (done)
20:28:54: INFO: | |
20:28:54: INFO: __| | ___ _ __ ___
20:28:54: INFO: / _` |/ _ \| '_ \ / _ \
20:28:54: INFO: | (_| | (_) | | | | __/
20:28:54: INFO: \__,_|\___/|_| |_|\___|
20:28:54: INFO: {All Finished Successfully}
20:28:54: INFO: Overall to target 1403.578 seconds (26.33 MBps)
20:28:54: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt', might take a minute
Log is 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
If you only want to write back only one specific partition, you need to specify the start_sector value to the decimal value of a partition's Start LBA.
Always keep the Partition Manager window opened!
Step 6: Quit Partition Manager
After everything dumped, you can close Partition Manager, the QFIL will reboot your phone back to EDL mode or reboot your phone back to normal mode.
Then you can force reboot your phone or mess up your phone as you want.
reserved
Awesome Guide!
Qualcomm HS-USB QD loader 9008 drivers showing briefly in device manager
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.
user agent said:
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.
Click to expand...
Click to collapse
I remember Galaxy Note 3 can remove the battery right?
In may cases, Qualcomm based phone can stay at EDL mode without battery.
the partitiion maneger do not appear
Hey, Thank you so much for prividing this GUIDE!
I just try to maake a backup of my data. I followed the steps above but the partition manager do not appear. Anyone know what is the problem? Log see below. Thank you for any coming tipps!
2020-04-19 23:31:12.778 Validating Application Configuration
2020-04-19 23:31:12.790 Load APP Configuration
2020-04-19 23:31:12.810 COM:12
2020-04-19 23:31:12.810 PBLDOWNLOADPROTOCOL:0
2020-04-19 23:31:12.810 PROGRAMMER:True
2020-04-19 23:31:12.810 PROGRAMMER:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:31:12.810 RESETSAHARASTATEMACHINE:False
2020-04-19 23:31:12.810 SAHARAREADSERIALNO:False
2020-04-19 23:31:12.810 SEARCHPATH:\Firefox_download\01\images
2020-04-19 23:31:12.810 ACKRAWDATAEVERYNUMPACKETS:False
2020-04-19 23:31:12.810 ACKRAWDATAEVERYNUMPACKETS:100
2020-04-19 23:31:12.810 MAXPAYLOADSIZETOTARGETINBYTES:False
2020-04-19 23:31:12.810 MAXPAYLOADSIZETOTARGETINBYTES:49152
2020-04-19 23:31:12.810 DEVICETYPE:ufs
2020-04-19 23:31:12.810 PLATFORM:8x26
2020-04-19 23:31:12.810 VALIDATIONMODE:0
2020-04-19 23:31:12.811 RESETAFTERDOWNLOAD:False
2020-04-19 23:31:12.811 MAXDIGESTTABLESIZE:8192
2020-04-19 23:31:12.811 SWITCHTOFIREHOSETIMEOUT:30
2020-04-19 23:31:12.811 RESETTIMEOUT:200
2020-04-19 23:31:12.811 RESETDELAYTIME:2
2020-04-19 23:31:12.811 METABUILD:
2020-04-19 23:31:12.811 METABUILD:
2020-04-19 23:31:12.811 FLATBUILDPATH:C:\
2020-04-19 23:31:12.811 FLATBUILDFORCEOVERRIDE:True
2020-04-19 23:31:12.811 QCNPATH:C:\Temp\00000000.qcn
2020-04-19 23:31:12.811 QCNAUTOBACKUPRESTORE:False
2020-04-19 23:31:12.811 SPCCODE:000000
2020-04-19 23:31:12.811 ENABLEMULTISIM:False
2020-04-19 23:31:12.811 AUTOPRESERVEPARTITIONS:False
2020-04-19 23:31:12.811 PARTITIONPRESERVEMODE:0
2020-04-19 23:31:12.811 PRESERVEDPARTITIONS:0
2020-04-19 23:31:12.811 PRESERVEDPARTITIONS:
2020-04-19 23:31:12.811 ERASEALL:False
2020-04-19 23:31:12.812 Load ARG Configuration
2020-04-19 23:31:12.888 Validating Download Configuration
2020-04-19 23:31:12.890 Image Search Path: D:\Firefox_download\01\images
2020-04-19 23:31:12.895 Programmer Path:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:31:13.548 Process Index:0
2020-04-19 23:31:13.567 Qualcomm Flash Image Loader (QFIL) 2.0.2.3
2020-04-19 23:32:56.567 Start Download
2020-04-19 23:32:56.588 Program Path:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:32:56.593 ***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:32:57.013 Binary build date: Apr 27 2018 @ 03:04:33
2020-04-19 23:32:57.015 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\QUALCOMM\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:32:57.018 Sahara mappings:
2020-04-19 23:32:57.020 2: amss.mbn
2020-04-19 23:32:57.020 6: apps.mbn
2020-04-19 23:32:57.021 8: dsp1.mbn
2020-04-19 23:32:57.022 10: dbl.mbn
2020-04-19 23:32:57.022 11: osbl.mbn
2020-04-19 23:32:57.023 12: dsp2.mbn
2020-04-19 23:32:57.023 16: efs1.mbn
2020-04-19 23:32:57.024 17: efs2.mbn
2020-04-19 23:32:57.024 20: efs3.mbn
2020-04-19 23:32:57.025 21: sbl1.mbn
2020-04-19 23:32:57.025 22: sbl2.mbn
2020-04-19 23:32:57.026 23: rpm.mbn
2020-04-19 23:32:57.027 25: tz.mbn
2020-04-19 23:32:57.027 28: dsp3.mbn
2020-04-19 23:32:57.028 29: acdb.mbn
2020-04-19 23:32:57.030 30: wdt.mbn
2020-04-19 23:32:57.031 31: mba.mbn
2020-04-19 23:32:57.032 13: D:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:32:57.032
2020-04-19 23:32:57.033 23:32:56: Requested ID 13, file: "D:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf"
2020-04-19 23:32:57.033
2020-04-19 23:32:57.034 23:32:57: 715496 bytes transferred in 0.391000 seconds (1.7451MBps)
2020-04-19 23:32:57.034
2020-04-19 23:32:57.035
2020-04-19 23:32:57.035
2020-04-19 23:32:57.036 23:32:57: File transferred successfully
2020-04-19 23:32:57.036
2020-04-19 23:32:57.036
2020-04-19 23:32:57.037
2020-04-19 23:32:57.038 23:32:57: Sahara protocol completed
2020-04-19 23:32:57.038 Sending Programmer Finished
2020-04-19 23:32:57.039 Switch To FireHose
2020-04-19 23:32:57.039 Wait for 3 seconds...
2020-04-19 23:33:00.041 Max Payload Size to Target:49152 Bytes
2020-04-19 23:33:00.041 Device Type:ufs
2020-04-19 23:33:00.042 Platform:8x26
2020-04-19 23:33:00.043 Disable Ack Raw Data Every N Packets
2020-04-19 23:33:00.044 Skip Write:False
2020-04-19 23:33:00.044 Always Validate:False
2020-04-19 23:33:00.045 Use Verbose:False
2020-04-19 23:33:00.050 ***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:33:00.124
2020-04-19 23:33:00.126 Base Version: 18.02.16.18.26
2020-04-19 23:33:00.131 Binary build date: Apr 27 2018 @ 03:04:29
2020-04-19 23:33:00.131 Incremental Build version: 18.04.27.03.04.29
2020-04-19 23:33:00.138
2020-04-19 23:33:00.138 23:33:00: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2020-04-19 23:33:00.139 ************************************************
2020-04-19 23:33:00.140 C:\Program Files (x86)\QUALCOMM\QPST\bin\fh_loader.exe --port=\\.\COM12 --search_path=C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12 --convertprogram2read --sendimage=fh_gpt_header_0 --start_sector=1 --lun=0 --num_sectors=1 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
2020-04-19 23:33:00.142 ************************************************
2020-04-19 23:33:00.142
2020-04-19 23:33:00.143 23:33:00: INFO: Current working dir (cwd): C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\
2020-04-19 23:33:00.144 23:33:00: INFO: Showing network mappings to allow debugging
2020-04-19 23:33:00.145 23:33:00: INFO: Looking for file 'fh_gpt_header_0'
2020-04-19 23:33:00.147
2020-04-19 23:33:00.147
2020-04-19 23:33:00.148 (_)
2020-04-19 23:33:00.149 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.150 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.151 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.151 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.152 __/ |
2020-04-19 23:33:00.153 |___/
2020-04-19 23:33:00.153
2020-04-19 23:33:00.154
2020-04-19 23:33:00.154 23:33:00: WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL
2020-04-19 23:33:00.156
2020-04-19 23:33:00.156
2020-04-19 23:33:00.157 (_)
2020-04-19 23:33:00.158 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.158 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.159 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.160 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.160 __/ |
2020-04-19 23:33:00.161 |___/
2020-04-19 23:33:00.161
2020-04-19 23:33:00.162
2020-04-19 23:33:00.163 23:33:00: WARNING: User specified --num_sectors=1 but file only has 1 sectors. **Ignoring --num_sectors
2020-04-19 23:33:00.163
2020-04-19 23:33:00.164
2020-04-19 23:33:00.164 23:33:00: INFO: User wants to talk to port '\\.\COM12'
2020-04-19 23:33:00.165 23:33:00: INFO: Took 0.01500000 seconds to open port
2020-04-19 23:33:00.166 23:33:00: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
2020-04-19 23:33:00.167 23:33:00: INFO: If you don't want this, use --dontsorttags
2020-04-19 23:33:00.167
2020-04-19 23:33:00.168 23:33:00: INFO: Looking for file 'fh_gpt_header_0'
2020-04-19 23:33:00.171
2020-04-19 23:33:00.172
2020-04-19 23:33:00.172 (_)
2020-04-19 23:33:00.173 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.174 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.174 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.175 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.176 __/ |
2020-04-19 23:33:00.177 |___/
2020-04-19 23:33:00.178
2020-04-19 23:33:00.179
2020-04-19 23:33:00.179 23:33:00: WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL
2020-04-19 23:33:00.180 23:33:00: INFO: Sending <configure>
2020-04-19 23:33:00.181
2020-04-19 23:33:00.181 23:33:00: INFO: TARGET SAID: 'INFO: Binary build date: Dec 27 2019 @ 18:17:54'
2020-04-19 23:33:00.182
2020-04-19 23:33:00.182 23:33:00: INFO: TARGET SAID: 'INFO: Binary build date: Dec 27 2019 @ 18:17:54
2020-04-19 23:33:00.183 '
2020-04-19 23:33:00.184
2020-04-19 23:33:00.184 23:33:00: INFO: TARGET SAID: 'INFO: Chip serial num: 2650911984 (0x9e01b4f0)'
2020-04-19 23:33:00.185
2020-04-19 23:33:00.186 23:33:00: INFO: TARGET SAID: 'INFO: Supported Functions (14):'
2020-04-19 23:33:00.187
2020-04-19 23:33:00.188 23:33:00: INFO: TARGET SAID: 'INFO: program'
2020-04-19 23:33:00.188
2020-04-19 23:33:00.189 23:33:00: INFO: TARGET SAID: 'INFO: read'
2020-04-19 23:33:00.190
2020-04-19 23:33:00.190 23:33:00: INFO: TARGET SAID: 'INFO: nop'
2020-04-19 23:33:00.191
2020-04-19 23:33:00.191 23:33:00: INFO: TARGET SAID: 'INFO: patch'
2020-04-19 23:33:00.192
2020-04-19 23:33:00.192 23:33:00: INFO: TARGET SAID: 'INFO: configure'
2020-04-19 23:33:00.193
2020-04-19 23:33:00.194 23:33:00: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
2020-04-19 23:33:00.194
2020-04-19 23:33:00.195 23:33:00: INFO: TARGET SAID: 'INFO: erase'
2020-04-19 23:33:00.196
2020-04-19 23:33:00.196 23:33:00: INFO: TARGET SAID: 'INFO: power'
2020-04-19 23:33:00.197
2020-04-19 23:33:00.198 23:33:00: INFO: TARGET SAID: 'INFO: firmwarewrite'
2020-04-19 23:33:00.198
2020-04-19 23:33:00.199 23:33:00: INFO: TARGET SAID: 'INFO: getstorageinfo'
2020-04-19 23:33:00.199
2020-04-19 23:33:00.200 23:33:00: INFO: TARGET SAID: 'INFO: benchmark'
2020-04-19 23:33:00.201
2020-04-19 23:33:00.201 23:33:00: INFO: TARGET SAID: 'INFO: emmc'
2020-04-19 23:33:00.202
2020-04-19 23:33:00.202 23:33:00: INFO: TARGET SAID: 'INFO: ufs'
2020-04-19 23:33:00.203
2020-04-19 23:33:00.203 23:33:00: INFO: TARGET SAID: 'INFO: fixgpt'
2020-04-19 23:33:00.204
2020-04-19 23:33:00.205 23:33:00: INFO: TARGET SAID: 'INFO: End of supported functions 14'
2020-04-19 23:33:00.205
2020-04-19 23:33:00.207 23:33:00: INFO: TARGET SAID: 'ERROR: Only nop and sig tag can be recevied before authentication.'
2020-04-19 23:33:00.208 23:33:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
2020-04-19 23:33:00.210 23:33:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2020-04-19 23:33:00.211 23:33:00: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2020-04-19 23:33:00.211
2020-04-19 23:33:00.212 Writing log to 'C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\port_trace.txt', might take a minute
2020-04-19 23:33:00.213
2020-04-19 23:33:00.213
2020-04-19 23:33:00.214 Log is 'C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\port_trace.txt'
2020-04-19 23:33:00.215
2020-04-19 23:33:00.215 Download Fail:FireHose Fail:FHLoader Fail:FHLoader Failrocess fail
2020-04-19 23:33:00.225 Finish Get GPT
the other Log is attached here.
View attachment port_trace.txt
Excuse me, do you happen to have any official documentation on EDL?
Sorry for the slight offtopic.
Phone stuck in EDL Mode
Hello hikari, my device Nokia 4.2 (TA-1152) is stuck in EDL MODE after dumping the boot image file.
Can you please help me to exit from EDL mode?
Hi! even with another firehose, Crosscall Core-X3 won't accept entering Sahara mode. wrong 'pkhash'.
Recovery show HS8917QC, modem show 8937. I tried many of each without success. I don't know which one is relevant.
[ro.product.device]: [HS8917QC]
[ro.hmct.modem.version]: [MSM8937.LA.3.0.1-00490-STD.PROD-1]
[ro.fota.oem]: [hisense8917_8.1]
[ro.fota.platform]: [MSM8917_8.1]
[ro.bootimage.build.fingerprint]: [CROSSCALL/L750/HS8917QC:8.1.0....]
[gsm.version.baseband]: [MPSS.JO.3.0-00464-8937_GENNS_PACK-1]
[gsm.version.baseband1]: [MPSS.JO.3.0-00464-8937_GENNS_PACK-1]
fastboot getvar all : https://pastebin.com/pmPDpeJ8
Of course no firehose neither full image is available for this exotic device.
Bless you.
Thank you for providing the instructions!
I'd like to extract LeEco Le Max 2 (X820) but QFIL won't bring me the Partition Table.
Device recognized as "Qualcomm HS-USB QDLoader 9008 (COM12)" in Device Manager.
QFIL tells me 10:52:37: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
(Log attached.)
I used "prog_emmc_firehose_8996_ddr.elf" because I didn't find a firehose for X820. May this error be caused by a wrong firehose file? If yes, is it safe to have a try with one of the firmware image files without bricking the device or destroying data?
Length Name
------ ----
16777216 adspso.bin
405504 BTFM.bin
201304 cmnlib.mbn
256008 cmnlib64.mbn
1048576 ddr.mbn
39976 devcfg.mbn
296 devinfo.bin
793040 emmc_appsboot.mbn
264120 hyp.mbn
226008 keymaster.mbn
85004288 NON-HLOS.bin
42728 pmic.elf
229540 rpm.mbn
1634304 tz.mbn
1836136 xbl.elf
Or is it more likely that this model just doesn't respond?
Anyone ever tried this on an ROG phone 2?
Step 3: Open QFIL, load Firehose file
Hello everyone. I have nokia 1.4 TA-1322. I have downloaded several firmwares from the different websites but the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
hikari_calyx said:
This is the partition table of your phone. Please take note on the Start LBA and LBA number of the last partition.
Take HP Elite X3 partition table for example, the last partition is "Data", it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors. Multiple the sector numbers with 512 will get the total bytes of the eMMC storage, in this case, the capacity of eMMC storage is 62,537,055,744 bytes.
Click to expand...
Click to collapse
Hello, my partitions on my phone are wildly different compared to these. The userdata partition says it's only about 3,933,729,792 bytes. It's a 32GB phone, any reasons why it's so tiny?
Thanks for taking time to write all this out and help out a lot of people. Everything made sense until I got to
"it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors"
I don't think this is common knowledge. Could you please explain or just point me in the right direction to understand how adding 0x01E20000 and 0x0565BFDF resulted in 0x0747BFDF, and how we translate that string of characters into 122,142,687?
Thank you!
Hello everyone. I have a bricked Asus Zenfone 8 and I'm trying to recover userdata partitiion from it using 9008 mode. I have correct Firehose file and everything should work fine. I've easily recovered data from system partition using this manual, but I have problem with userdata. This partition is huge, around 230 GB, and phone just disconnects from PC in the middle of the process. First time it downloaded 98GB, second time - 60GB, so I don't think this is because of broken flash memory or smth. What can be a reason of this problem and how to solve that? Thanks for any reply!
Cirrus9 said:
Thanks for taking time to write all this out and help out a lot of people. Everything made sense until I got to
"it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors"
I don't think this is common knowledge. Could you please explain or just point me in the right direction to understand how adding 0x01E20000 and 0x0565BFDF resulted in 0x0747BFDF, and how we translate that string of characters into 122,142,687?
Thank you!
Click to expand...
Click to collapse
Hi. This string of characters is hexadecimal numeral system. You can use standart Windows calculator in programmer mode to convert these numbers.
{
"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"
}
Thank you! Learned something new today!
Hi! This guide is great. I have an issue with the firehose file where I found the right firehose file from my device using firehose finder on GitHub. However, that file is in .bin format instead of .elf. How can I convert it, and is that safe?
kjullian19 said:
However, that file is in .bin format instead of .elf. How can I convert it, and is that safe?
Click to expand...
Click to collapse
Firehose loaders are technically ELF 32 or 64 bit files but may be named elf, bin, img, mbn, whatever.
Use a hex editor and look at the start of the file.
It should be 7f 45 4c 46
Or use my elfview.exe (in the sig) to check it out.
Or use my qcomview.exe (in the sig) to check it out.
Code:
C:\>elfview /p motog.bin
# Type Flags Size Offset Address
-- ------- ----- ------- ------ --------
0 null 7 1016 000000 00000000
1 null 2.2 7384 001000 4602c000
2 load RWZ 0 06b4b0 0c100000
3 load RX 7772 0549f0 0c119000
4 load RWZ 0 056850 0c11c000
5 load RWZ 0 06b4b0 0c11e000
6 load RWZ 0 0549f0 0c219000
7 load RX 301376 003000 0c225000
8 load RWZ 0 04c940 0c276c00
9 load RW 32932 04c940 0c279c00
10 load RWZ 0 0549f0 0c286c00
11 load RWX 85080 056850 0c29b000
12 load 1RWX 84 06b4b0 0c2c9000
13 load 1RWX 29168 06b504 0c2c9054
14 load 1RWX 1496 0726f4 0c2d0244
15 load 5RX 139264 072ccc 0c350000
16 load RWZ 0 0549f0 45e11000
C:\>qcomview /h motog.bin
64 bit ELF, Version 6, SHA384
0 00000000 000003f8 a3836cd6c3e2dbed 5dd00c97349c8598 92a5051c08ae65d4 171ba1ece407a7b2 1cdf27a97ff437c7 0488bb944956fbc2 Ok
1 00001000 00001cd8
2 0006b4b0 00000000
3 000549f0 00001e5c 3972d9e5346b52cc e71c31a437500b8f 57f2fc8124e97cd5 b2f70a4829e98196 03d89d4b946261e2 9b2a58949b92b7dc Ok
4 00056850 00000000
5 0006b4b0 00000000
6 000549f0 00000000
7 00003000 00049940 503b424c75f6d657 e4363c830deeebee afe0ac82ce04dfec e8ac03fb47b129a3 fc221acc0d515b22 ed17d86b0f6b585c Ok
8 0004c940 00000000
9 0004c940 000080a4 2f7aec3605fbce70 ec0c83a703435845 e969988f390787d7 aa8d0a13a6d9e06f ee2af4e9b86b8a75 fc81fbe1017d1c64 Ok
10 000549f0 00000000
11 00056850 00014c58 fec3a6b9f6d71a18 aadd3f722fc73bea d3197c24c397d55d 4f3d4a9c25661db1 152c60664fcbe4a6 c2441120afc4b3c9 Ok
12 0006b4b0 00000054 db139c6f70d88269 a61cb1a7be2ce363 55faf1ff1c3b9c3d 27cd8d65bef7f710 9bc83c6255ea8104 6d7ac582cc778f15 Ok
13 0006b504 000071f0 a27a7dc0040a1bfa 8e24e4a42bead90e ae10a91c37d19105 bce9da69383004ea c933b87ac4a88653 ccbb4a6b1407d15d Ok
14 000726f4 000005d8 8dcaae787361a3c4 3bad6d344641d061 35170b5a30607e20 a30cd23884bbc0b0 790681aa36a1fe60 98501a103b62088a Ok
15 00072ccc 00022000 1f939df47e7fae80 2c127e10474ff9e6 2faecd5fab873bf8 928cab0a5ef28261 5d4b19cc57cca817 37fa9fad42971c40 Ok
16 000549f0 00000000
Thanks Renate. I'm new to this stuff, so you might have to ELI5, I'm not seeing 7f 45 4c 46 in your log.
Ultimately, I need to learn how to convert the binary file into a compatible .elf file. Will either elfview or qcomview do that?
Thanks again and sorry for the dumb questions
After trying to flash my phone with lineage OS via adb it has gone black. Only EDL working.
I tried to flash a Android 9 1.6 for recovery, but with following log. Can anyone help?
============================================================================================================
15:32:28: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
15:32:28: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
15:32:28: DEBUG: CharsInBuffer = 16
15:32:28: DEBUG: printBuffer:5435 PRETTYPRINT Buffer is 16 bytes
15:32:28: DEBUG: printBuffer:5512 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
15:32:28: DEBUG: printBuffer:5525
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: DetermineTag:6236 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7310 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7320
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
Did you make an EDL backup before performing this procedure?
What is the model number of your phone?
Gararoth said:
After trying to flash my phone with lineage OS via adb it has gone black. Only EDL working.
I tried to flash a Android 9 1.6 for recovery, but with following log. Can anyone help?
============================================================================================================
15:32:28: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
15:32:28: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
15:32:28: DEBUG: CharsInBuffer = 16
15:32:28: DEBUG: printBuffer:5435 PRETTYPRINT Buffer is 16 bytes
15:32:28: DEBUG: printBuffer:5512 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
15:32:28: DEBUG: printBuffer:5525
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: DetermineTag:6236 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7310 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7320
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
Click to expand...
Click to collapse
ZTE BLACK 5g a20n2
Hi thx for your reply - i got i to work again... BUT!!!
->
->
I wanted to update the firmware of my zte axon 10 pro. I installed a 1.6 version with EDL tool. Android is working, but then i realized the SIM-CARD wont work....!!!! Then i saw that the firmware i installed was for the 4G version.. I than found a firmware for my a2020n2...
ztedevices.com/cn/supports/zte-a2020n2-pro/[/url]
only problem is, i am not able to install the SD version because update now thinks i have the 4G version.... Only possible way would be to install force via 5G EDL version - but i can only find SD -Card versions and they won'T work...
any help??
Gararoth said:
Hi thx for your reply - i got i to work again... BUT!!!
->
->
I wanted to update the firmware of my zte axon 10 pro. I installed a 1.6 version with EDL tool. Android is working, but then i realized the SIM-CARD wont work....!!!! Then i saw that the firmware i installed was for the 4G version.. I than found a firmware for my a2020n2...
ztedevices.com/cn/supports/zte-a2020n2-pro/[/url]
only problem is, i am not able to install the SD version because update now thinks i have the 4G version.... Only possible way would be to install force via 5G EDL version - but i can only find SD -Card versions and they won'T work...
any help??
Click to expand...
Click to collapse
I don't have experience actually doing this but I have seen plenty of people mention doing it and it working - google "payload dumper xda" and you'll find a thread explaining how to use a python script that will take the SD card payload.bin and unpack it. You should then be able to use those files with the EDL tool.
ZTE BLACK 5g a20n2
bobthenormal said:
I don't have experience actually doing this but I have seen plenty of people mention doing it and it working - google "payload dumper xda" and you'll find a thread explaining how to use a python script that will take the SD card payload.bin and unpack it. You should then be able to use those files with the EDL tool.
Click to expand...
Click to collapse
I tried that and i managed to dump the payload bin. installing via EDL Tool 5G says: Not found important files, or detected SPARSE image... and MiFlash won't work either... I have bootloader unlocked but no root.... any help?
Gararoth said:
I tried that and i managed to dump the payload bin. installing via EDL Tool 5G says: Not found important files, or detected SPARSE image... and MiFlash won't work either... I have bootloader unlocked but no root.... any help?
Click to expand...
Click to collapse
When you try to use MiFlash what is your error?
If it's the hello packet issue - try this. Get MiFlash ready, all set up to hit "flash". Reset the phone (long press power) into EDL - as the phone is booting up into EDL, keep hitting refresh in MiFlash. The second the phone shows up, hit flash
ZTE BLACK 5g a20n2
Before i read your suggestion, i managed to install a 5G version via EDL-Tool 5G with success, but i am stuck in a bootloop... tried to get the battery to 0%, but as soon as i connect the phone via usb, bootloop is starting again, what now?
Gararoth said:
Before i read your suggestion, i managed to install a 5G version via EDL-Tool 5G with success, but i am stuck in a bootloop... tried to get the battery to 0%, but as soon as i connect the phone via usb, bootloop is starting again, what now?
Click to expand...
Click to collapse
How fast is the bootloop? 3 seconds or more like 8?
I assume by bootloop you mean the ZTE logo.
ZTE BLACK 5g brick
It's 3 seconds ZTE Screen. I waited some days to have zero power and tried to get in EDL mode... but no chance. When there is enough power again it starts autmatically with the ZTE screen 3 secs.
Gararoth said:
It's 3 seconds ZTE Screen. I waited some days to have zero power and tried to get in EDL mode... but no chance. When there is enough power again it starts autmatically with the ZTE screen 3 secs.
Click to expand...
Click to collapse
You couldn't get in EDL mode? That's very unlikely if the buttons aren't broken... it's part of the boot process that's stored in hardware, so you can't really lose it.
You're holding down BOTH the Vol+ and Vol- buttons? And plugged into a computer? If so and you hold those down while it bootloops (no need to press the power button), the loops should stop and the phone stay black. That indicates it's in EDL mode and you should see it show up in Device Manager.
If it doesn't, you might need the USB drivers. You can get them from the tools I posted in the Guide section, or probably from ZTE (I'm not sure).
ZTE BLACK 5g
You were right.... i switched to edl mode via adb and this won't work with a boot loop... i didnt know about the volume up and down command you saved my life.. only thing now is that i have to find a 5G img that works.. with EDL tool i manage to install the images resulting everytime in a bootloop. 3secs.... lineageOS boots to recovery with and error "cannot load android system" - installation via Miflash doesnt work exept A2020G_PRO_V1.6_FULL_EDL (but thats 4G and doesn't regognize the SIM card) - i will try some other images and let you know.
ZTE BLACK 5g
I managed now to install lineageOS16 after a factory reset in recovery mode! But the same .. regognizing the SIM Card but no mobile netzwork... working on other phone...
Gararoth said:
You were right.... i switched to edl mode via adb and this won't work with a boot loop... i didnt know about the volume up and down command you saved my life.. only thing now is that i have to find a 5G img that works.. with EDL tool i manage to install the images resulting everytime in a bootloop. 3secs.... lineageOS boots to recovery with and error "cannot load android system" - installation via Miflash doesnt work exept A2020G_PRO_V1.6_FULL_EDL (but thats 4G and doesn't regognize the SIM card) - i will try some other images and let you know.
Click to expand...
Click to collapse
ZTE BLACK 5g
I now tried to install the original firmware A2020N3 Pro (A1) SD card software package(378980B2730A1_AT_EEA_A2020N3_Pro_V1.20) i dumped the payload bin and installed via EDL5G and MIFlash.. bothe installation worked. ending in a bootllop....
Gararoth said:
I now tried to install the original firmware A2020N3 Pro (A1) SD card software package(378980B2730A1_AT_EEA_A2020N3_Pro_V1.20) i dumped the payload bin and installed via EDL5G and MIFlash.. bothe installation worked. ending in a bootllop....
Click to expand...
Click to collapse
I might be able to get the SD card package to apply with my tools, but I need some things:
a) List of the files from the payload (just copy-paste a "dir" of the directory, filenames and file sizes)
b) If in those files you have a bunch of files starting with GPT, like gpt_main0.bin, etc. Copy them all into a zip file and upload them (no personal information in them, they're partition sector information for the hard disk)
c) just to double check - download the tools I uploaded and follow the instructions in that thread to run GPT backup... that will get a bunch of gpt files - zip those up and upload them too
With those I'll modify the tools to work with your phone variant and you may be able to manually flash the payload files.
Use QFIL or Windows 7 64-bit command line tool + "QSaharaserver.exe" + "fh_loader.exe", through "Qualcomm HS-USB QDLoader 9008（COM30）" to OPPO R9S, send the "img" file is always failed.
Hello everyone,
I often encountered an acquaintance in these days: Mr."Error" !
I don't like him at all, but he often shakes in front of me. My head is a bit dizzy!
Is there any good way to disappear this Mr. "Error"?
First, my computer's system: Windows 7 64-bit, has entered the test mode.
The screenshot of the test mode is as follows:
{
"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"
}
Second, the OPPO R9S mobile phone uses the Snapdragon 625 (MSM8953) CPU, eMMC 5.1 model of memory.
After OPPO R9S mobile phone connecting to the computer with a USB cable, the opening is first vibrating, and then it is in a black screen state.
Then, in the Windows device manager, the port (COM and LPT) can see "Qualcomm HS-USB QDLoader 9008 (COM30)" device.
##########################################################
The first kind test：
The tools used is as follows:
QFIL Version 2.0.2.3
OPPO R9S related files——prog_emmc_firehose_8953_ddr.mbn、rawprogram0.xml、patch0.xml、recovery.img
In the process of use, in the device manager, the port (COM and LPT) can see "Qualcomm HS-USB QDLoader 9008（COM30）" device.
Test failed.
Mr. "Error" Say:
2022-02-03 12:36:18.083 12:36:17: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
2022-02-03 12:36:18.083
2022-02-03 12:36:18.099 12:36:17: ERROR: function: sahara_main:983 Sahara protocol error
2022-02-03 12:36:18.099
2022-02-03 12:36:18.099 12:36:17: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-02-03 12:36:18.115
2022-02-03 12:36:18.115
2022-02-03 12:36:18.115 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-02-03 12:36:18.115 Finish Download
Screenshot below:
Why ? Sahara doesn't like me? ? ?
##########################################################
Second kind test:
The tools used is as follows:
Windows 7 64-bit command line tool, QSaharaServer.exe and fh_loader.exe in the MiFlash 20191206 toolbox,
OPPO R9S related files——prog_emmc_firehose_8953_ddr.mbn、rawprogram0.xml、patch0.xml、recovery.img
In the process of use, in the device manager, the port (COM and LPT) can see "Qualcomm HS-USB QDLoader 9008（COM30）" device.
The relevant main orders I entered are as follows:
QSaharaServer.exe –p \\.\COM30 -s 13:\OPPOR9S\113391\6\prog_emmc_firehose_8953_ddr.mbn
fh_loader.exe --port=\\.\COM30 --erase=0 --sendxml=rawprogram0.xml,patch0.xml --search_path=D:\OPPOR9S\113391\6 --noprompt --showpercentagecomplete --memoryname=eMMC --reset
Testing still failed.
Mr. "Error" shouted:
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
12:45:22: {ERROR: ReadPort:5272 Could not read from '\\.\COM30', Windows API ReadFile failed! Your device is probably *not* on this port
However, this Mr. "Error" is wrong!
I clearly see that there is "Qualcomm HS-USB QDLoader 9008 (COM30)" in port (COM and LPT).
Why??????????????
Things have changed.
After connecting the phone to the computer, press the "Volume +", "Volume -" and "Power" buttons at the same time for 10 seconds.
So, in the device manager, the original "Qualcomm HS-USB QDLoader 9008 (COM30)" has become "Qualcomm HS-USB QDLoader 9008 (COM3)".
So, the old Mr. Error is gone.
However, here comes the new Mr. Error.
Note: The following error log content, the original text is without emoji pictures.
#################QFIL Error begin#########################
QFIL Error:
……
2022-02-04 02:23:28.706 31: mba.mbn
2022-02-04 02:23:28.706 13: D:\OPPOR9S\113391\6\prog_emmc_firehose_8953_ddr.mbn
2022-02-04 02:23:28.706
2022-02-04 02:23:28.722 02:23:28: Requested ID 13, file: "D:\OPPOR9S\113391\6\prog_emmc_firehose_8953_ddr.mbn"
2022-02-04 02:23:28.722
2022-02-04 02:23:28.722 02:23:28: 353828 bytes transferred in 0.281000 seconds (1.2008MBps)
2022-02-04 02:23:28.737
2022-02-04 02:23:28.737
2022-02-04 02:23:28.737
2022-02-04 02:23:28.737 02:23:28: File transferred successfully
2022-02-04 02:23:28.737
2022-02-04 02:23:28.737
2022-02-04 02:23:28.753 NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
2022-02-04 02:23:28.753
2022-02-04 02:23:28.753
2022-02-04 02:23:28.753 02:23:28: Sahara protocol completed
2022-02-04 02:23:28.769 Sending Programmer Finished
2022-02-04 02:23:28.784 Switch To FireHose
2022-02-04 02:23:28.784 Wait for 3 seconds...
2022-02-04 02:23:31.795 Max Payload Size to Target:49152 Bytes
2022-02-04 02:23:31.795 Device Type:emmc
2022-02-04 02:23:31.795 Platform:8x26
2022-02-04 02:23:31.811 Disable Ack Raw Data Every N Packets
2022-02-04 02:23:31.811 Skip Write:False
2022-02-04 02:23:31.811 Always Validate:False
2022-02-04 02:23:31.811 Use Verbose:False
2022-02-04 02:23:31.889 ***** Working Folder:C:\Users\Userstest\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2022-02-04 02:23:31.920 Download Fail:FireHose Fail:FHLoader Fail:FHLoader Fail:The system can not find the file specified.
2022-02-04 02:23:31.998 Finish Get GPT
#################QFIL Error end#########################
######"QSaharaserver.exe + fh_loader.exe" Error begin############
"QSaharaserver.exe + fh_loader.exe" Error:
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
23:50:47: {ERROR: DetermineTag:6180 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
23:50:47: {ERROR: GetNextPacket:7254 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
23:50:47: {ERROR: GetNextPacket:7264
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
######"QSaharaserver.exe + fh_loader.exe" Error end############
prog_emmc_firehose_8953_ddr.mbn、rawprogram0.xml、patch0.xml、recovery.img---Is there something wrong with these files?
It took me a lot of time to find these files at first, and I got them from some maintenance software.
By the way: how do you get these files in general?
Don't tell me about the official website of the mobile phone, they do not provide wire brush packs publicly.
"FHLoader Fail" problem solved.
Before I solved it, I also found it difficult.
After various attempts and searches, I accidentally checked the installation directory of "QFIL" and found that there is no "fh_loader.exe" file in this directory.
Copy the file "fh_loader.exe" from other places to the installation directory of "QFIL", and then try to read the information of each partition of eMMC, this time it is successful.
Check out the screenshot:
Next, I can do some of the things I want to do.
Did something go wrong? ! Does that solve it? Is it too simple?
I have encountered this kind of thing many times, and sometimes it is just a small oversight, and as a result, it takes a lot of time to check.