Related
I bricked my Lenovo Vibe K5 while trying to install TWRP.
Now it's stuck at boot and will only enter download mode.
I've tried to flash it with QFIL but I only get Sahara error.
Here is the QFIL log:
Validating Application Configuration
Load APP Configuration
COM:3
SAHARA:True
SAHARA:C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW\prog_emmc_firehose_8929.mbn
SEARCHPATH:C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW
RAWPROGRAM file path: C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW\rawprogram0.xml
PATCH file path:C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW\patch0.xml
Programmer Path:C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW\prog_emmc_firehose_8929.mbn
Start Download
Program Path:C:\Users\sondre\Documents\A6020a40_S022_160423_ROW_qpst\SW\SW\prog_emmc_firehose_8929.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
hi all
i have my V10 bricked. i guess i flashed a wrong version of OS via LGUP.
its H901 or F600L(printed in the motherboard), t-mobile.
its on Qualcomm HS-USB QDLoader 9008 mode now.
followed the method from this thread:
https://forum.xda-developers.com/tmobile-lg-v10/general/unbrick-h901-f600l-board-2017-t3635697
i flashed the extracted files from F600L20e KDZ, using the mbn and the xml provided in the first post here.
extracted the files from this kdz - F600L20e_00_0216.kdz. is this the correct one.
i get this firehose error..
Start Download
Program Path:C:\Users\NewUser1\Desktop\LG\OS\prog_emmc_fir ehose_8992_lite_lge.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Users\NewUser1\Desktop\LG\OS\QSaharaServer.exe -p \\.\COM3 -s 13:C:\Users\NewUser1\Desktop\LG\OS\prog_emmc_fireh ose_8992_lite_lge.mbn 'Current working dir: C:\Users\NewUser1\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\NewUser1\Desktop\LG\OS\prog_emmc_firehose _8992_lite_lge.mbn
01:14:32: Requested ID 13, file: "C:\Users\NewUser1\Desktop\LG\OS\prog_emmc_fir ehos e_8992_lite_lge.mbn"
01:14:32: 273568 bytes transferred in 0.078000 seconds (3.3448MBps)
01:14:32: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
01:14:32: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
Download Fail:FireHose Fail FHLoader Fail:The system cannot find the file specified
Finish Download
i renamed the files and checked the paths. i am not sure why i am getting this error. please someone help
I am getting same error.. i think we are using wrong qfil files.. i am looking for h901 qfil files and cant find it at all.
Why you extract F600l file for H901 modal .. extract H901 files and check
so i have a LG K20 (mp260) from MetroPCS, and like a fool, i flashed a rom that wasnt compatible...
its now hard bricked. my computer can only recognize it now as "Qualcomm HS-USB QDLoader 9008 (COM3)" in the "Ports" section of the device manager. the device itself cant turn on for nothing, there are no lights, no vibrations. but my computer can read it...
i have minimal knowledge on this stuff and ive been at this for almost a week now and how found nothing but the QFIL program that looked promising. ive installed all the appropriate drivers and give it the appropriate files (i hope):
Programmer: prog_emmc_firehose_8936.mbn
XML: rawprogram0.xml with the patch: patch0.xml
the files were manually extracted from my own phones stock .KDZ
i have seen others use rawprogram files such as "rawprogram_unsparse_without_qcn", and "rawprogram_unsparse". i dont know how to obtain these files and if they would help my problem.
(note: im using QFIL 2.0.1.7 and ive tried numerous previous versions:crying
apon pressing the "download" button, it says:
2018-08-01 21:26:02.821 Start Download
2018-08-01 21:26:02.843 Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\8675_W00\prog_emmc_firehose_8936.mbn
2018-08-01 21:26:02.860 ***** Working Folder:C:\Users\IZACOR\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2018-08-01 21:27:43.158 Binary build date: Nov 21 2017 @ 02:53:37
2018-08-01 21:27:43.160 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\IZACOR\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2018-08-01 21:27:43.164 Sahara mappings:
2018-08-01 21:27:43.165 2: amss.mbn
2018-08-01 21:27:43.166 6: apps.mbn
2018-08-01 21:27:43.167 8: dsp1.mbn
2018-08-01 21:27:43.168 10: dbl.mbn
2018-08-01 21:27:43.173 11: osbl.mbn
2018-08-01 21:27:43.174 12: dsp2.mbn
2018-08-01 21:27:43.175 16: efs1.mbn
2018-08-01 21:27:43.176 17: efs2.mbn
2018-08-01 21:27:43.178 20: efs3.mbn
2018-08-01 21:27:43.179 21: sbl1.mbn
2018-08-01 21:27:43.180 22: sbl2.mbn
2018-08-01 21:27:43.181 23: rpm.mbn
2018-08-01 21:27:43.182 25: tz.mbn
2018-08-01 21:27:43.183 28: dsp3.mbn
2018-08-01 21:27:43.184 29: acdb.mbn
2018-08-01 21:27:43.186 30: wdt.mbn
2018-08-01 21:27:43.188 31: mba.mbn
2018-08-01 21:27:43.190 13: C:\Program Files (x86)\Qualcomm\QPST\bin\8675_W00\prog_emmc_firehose_8936.mbn
2018-08-01 21:27:43.192
2018-08-01 21:27:43.194 21:27:43: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
2018-08-01 21:27:43.196
2018-08-01 21:27:43.197 21:27:43: ERROR: function: sahara_main:924 Sahara protocol error
2018-08-01 21:27:43.198
2018-08-01 21:27:43.199 21:27:43: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2018-08-01 21:27:43.201
2018-08-01 21:27:43.202
2018-08-01 21:27:43.203 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2018-08-01 21:27:43.205 Finish Download
im getting tired of seeing this log lol. but as you can see the problem (from i can see) is that its getting stuck at the "Sahara" bit. i cant seem to fix this to save my life. and ive littrally tried everything!
yes including putting the firmware files into the "bin" folder of the program and stuff like that...
fastbooting wont work either as the screen is always black and the computer never sees it as a device, but a port.
i turned to creating this post as a last resort, for if i cant find an answer here, im afraid ill just have to use the phone for parts or something:crying:. please! if anyone has suggestion or a solution that i haven't tried yet it would be truly appreciated!
Hi , try this from my post
1. Disable or remove your Antivirus (because sometimes virus can block instaling drivers , ports or running flash tool)
2. Uninstall all the previous drivers you used for flashing or unbrick use free tool called USBDeview
for 32 bit users:
https://www.nirsoft.net/utils/usbdeview.zip
for 64 bit users:
https://www.nirsoft.net/utils/usbdeview-x64.zip
3. Put your windows in Test mode
To put your Windows in test mode just Run As Administrator Command Prompt and insert one of the following command:
bcdedit -set testsigning on ( to enable test mode)
http://s000.tinyupload.com/index.php...66266232947643
bcdedit -set testsigning off ( to disable test mode)
http://s000.tinyupload.com/index.php...26094979151761
Or Disable driver signature
for Windows 7
https://www.youtube.com/watch?v=6gYhHD622AA
for Windows 10 users:
https://www.youtube.com/watch?v=71YAIw7_-kg
After that reboot your PC .
4. Uninstall all flash program from your pc like MiFlash , QPST , Qloader ...
Use Revo Uninstaller for advanced uninstaling that clean leftover files and registry which is stored inside your Windows registry.
https://www.revouninstaller.com/revo..._download.html
After that reboot your PC .
5. Install Microsoft .NET Framework 4 download from here: (if you already have instaled skip this)
https://www.microsoft.com/en-us/down....aspx?id=17851
6. Install Minimal ADB & Fastboot 1.4.2 command tool download from here
(while you start installing tool check to be in desktop is easy )
https://androidfilehost.com/?fid=745425885120698566
in order to install run ADB & Fastboot 1.4.2.exe with Administrator and just write y and hit enter for all .
Now follow this tutorial for unbrick your device : ) .
It must to work
http://lgk20.com/lg-k20-plus-mp260-stock-rom-download-firmware-update-tutorial/
Don't forget to run flash tool with Administrator.
Good Luck and Never give UP
Thank you for these tips! but unfortunately, i cant follow the tutorial because im unable to access download mode or any mode for that matter. my screen is black and isnt recognized by the computer as a normal LG phone anymore...
im trying to find a solution that does not involve download mode, fastboot, or anything involving the phone displaying anything if that makes sense...
You should try to let your battery to dry out and then hold Vol - button and plug usb ,just keep holding for few minutes to see if your pc is detecting your device if not try to replace the battery if that also doesn't help then probably your emmc chip is dead or something other.
Teddy Lo said:
You should try to let your battery to dry out and then hold Vol - button and plug usb ,just keep holding for few minutes to see if your pc is detecting your device if not try to replace the battery if that also doesn't help then probably your emmc chip is dead or something other.
Click to expand...
Click to collapse
i truly appreciate your helpfulness, but my main focus is trying to fix the Sahara error i keep receiving, and/or if im doing something wrong thats causing it.
Izaiah Coronado said:
i truly appreciate your helpfulness, but my main focus is trying to fix the Sahara error i keep receiving, and/or if im doing something wrong thats causing it.
Click to expand...
Click to collapse
Is your PC detecting your device at all ? and like which one ? can you post some photos ?
Also what you can try is to extract that stock firmware on another location like D:/ Firmware/(your extracted firmware) , run Qfil with Administrator , load extracted firmware from D:/Firmware/ in Qfil and make sure that you have 9008 open port .
Teddy Lo said:
Is your PC detecting your device at all ? and like which one ? can you post some photos ?
Also what you can try is to extract that stock firmware on another location like D:/ Firmware/(your extracted firmware) , run Qfil with Administrator , load extracted firmware from D:/Firmware/ in Qfil and make sure that you have 9008 open port .
Click to expand...
Click to collapse
{
"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"
}
its seen only as Qualcomm HS-USB QDLoader 9008 (under ports)and nothing else. i apologize but i cant seem to put up my picture...
i also just tried your suggestion and it didn't work sadly. im having horrible luck with these things lol.
When your PC is detecting your device as Qualcomm HS-USB QDLoader 9008 is good news : ) , it looks like path from firmware which you inserted inside Qfil tool are wrong or firmware at all .
Try again if you are able to put your device in fastboot mode:
Open Minimal ADB & Fastboot , in my case C:\Program Files (x86)\Minimal ADB and Fastboot right click on cmd-here.exe and Run as Administrator .
1. Now take out the battery , and insert again .
2. Next hold just vol - and plug usb cable don't release yet wait few seconds and see if your device is detected like that then release Vol - .
3. Write inside adb & fastboot terminal :
- fastboot device and press Enter
(see if is show up like some numbers or what )
if not try
- adb devices and press Enter
(if your device is available there just write adb reboot bootloader
-write again fastboot devices , and if everything is fine you should see your device
now from stock firmware extract recovery.img , also if you have single system.img , boot.img extract that also to in my case C:\Program Files (x86)\Minimal ADB and Fastboot and write for each one:
fastboot erase cache and press Enter
fastboot erase system and press Enter
fastboot flash recovery recovery.img and press enter
fastboot flash boot boot.img and press enter
fastboot flash system system.img and press enter
If that doesn't help you , try to flash this firmware with LG UP
Example how to flash :
https://www.youtube.com/watch?v=NIHTx6a_kDI
Stock firmware:
https://mega.nz/#!ymZQHI5S!F3x1I0qM_iXNEg9WnqLINkRATUvlBWigmnzfMD5pUZI
If doesn't help you is better to replace new motherboard and save your time .
so i was poking around and found out that the Firehose file i needed is like super specific to the device im using it on (a signed Firehose_emmc). so finding that ever so specific Firehose file could very much possibly be the fix. (i just dont know how to find and obtain it)
im also looking into the new motherboard because...you know...
would it matter the carrier? like if my phone is metroPCS and the new mother board is T-mobile?
Same Issue here.
Validating Application Configuration
Load APP Configuration
COM:5
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: D:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0
RAWPROGRAM file path: D:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\rawprogram0.xml
PATCH file path:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\patch0.xml
Programmer Path:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
Process Index:0
Start Download
Program Path:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: D:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
22:17:50: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
22:17:50: ERROR: function: sahara_main:924 Sahara protocol error
22:17:50: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
I have a problem
I,ve tried QFIL QPST and recieved
/*invalid image type recieved*/
is_ack_succesfull : 1031 SAHARA_NAK_INVALID_IMAGE_TYPE
sahara protocol error
uploading image using sahara protocol failed
Before that
My emmc card was already formatted to fat32
same issue here
having this same issue tried older version, short paths and lots of retries
BQ Aquarius X5 Plus Sahara Fail
Hi! I have this Fail on QFIL whith BQ Aquarius X5 Plus
I see my phone on Device Manager like: Qualcomm HS-USB QDOWNLOADER 9008 (COM3)
Pls someone...
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Fellow FOOL am I
I also have a K20... and a Stylo 4 with the same problem... (me) Flashed different variant of firmware (KDZ) and get QUALCOMM HS-USB QDLoader 9008
following this thread
For those still having ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
Please use older Qfil version, I flash successfully with version 2.0.0.0 after latest version giving above error..
handasan10 said:
For those still having ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
Please use older Qfil version, I flash successfully with version 2.0.0.0 after latest version giving above error..
Click to expand...
Click to collapse
Tried that thing but no success.
Possible problem with Qfil and network
JoshuaX12 said:
Tried that thing but no success.
Click to expand...
Click to collapse
Depending on how the Qualacom (sp) driver was installed, if you remember, it asked about a network connection type.
I found this problem while searching TONS of possible solutions, and it might work for you as I was getting the same errors with QFIL.
DISCONNECT FROM YOUR NETWORK. That means ALL interfaces, like wired ethernet, and wireless. ALL OF THEM.
Then try running the flash with QFIL.
I have an Essential PH-1 and tried this but of course got the Sahara Fail.
See log here:
2019-05-22 22:51:24.743 Validating Application Configuration
2019-05-22 22:51:24.752 Load APP Configuration
2019-05-22 22:51:24.773 COM:5
2019-05-22 22:51:24.773 PBLDOWNLOADPROTOCOL:0
2019-05-22 22:51:24.773 PROGRAMMER:True
2019-05-22 22:51:24.773 PROGRAMMER:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:51:24.773 RESETSAHARASTATEMACHINE:False
2019-05-22 22:51:24.773 SAHARAREADSERIALNO:False
2019-05-22 22:51:24.773 SEARCHPATH:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00
2019-05-22 22:51:24.773 RAWPROGRAM:
2019-05-22 22:51:24.773 rawprogram0.xml
2019-05-22 22:51:24.773 PATCH:
2019-05-22 22:51:24.773 patch0.xml
2019-05-22 22:51:24.773 ACKRAWDATAEVERYNUMPACKETS:False
2019-05-22 22:51:24.773 ACKRAWDATAEVERYNUMPACKETS:100
2019-05-22 22:51:24.773 MAXPAYLOADSIZETOTARGETINBYTES:False
2019-05-22 22:51:24.773 MAXPAYLOADSIZETOTARGETINBYTES:49152
2019-05-22 22:51:24.773 DEVICETYPE:emmc
2019-05-22 22:51:24.773 PLATFORM:8x26
2019-05-22 22:51:24.773 VALIDATIONMODE:0
2019-05-22 22:51:24.773 RESETAFTERDOWNLOAD:False
2019-05-22 22:51:24.773 MAXDIGESTTABLESIZE:8192
2019-05-22 22:51:24.773 SWITCHTOFIREHOSETIMEOUT:30
2019-05-22 22:51:24.773 RESETTIMEOUT:200
2019-05-22 22:51:24.773 RESETDELAYTIME:2
2019-05-22 22:51:24.773 METABUILD:
2019-05-22 22:51:24.773 METABUILD:
2019-05-22 22:51:24.773 FLATBUILDPATH:C:\
2019-05-22 22:51:24.773 FLATBUILDFORCEOVERRIDE:True
2019-05-22 22:51:24.773 QCNPATH:C:\Temp\00000000.qcn
2019-05-22 22:51:24.773 QCNAUTOBACKUPRESTORE:False
2019-05-22 22:51:24.773 SPCCODE:000000
2019-05-22 22:51:24.773 ENABLEMULTISIM:False
2019-05-22 22:51:24.773 AUTOPRESERVEPARTITIONS:False
2019-05-22 22:51:24.773 PARTITIONPRESERVEMODE:0
2019-05-22 22:51:24.773 PRESERVEDPARTITIONS:0
2019-05-22 22:51:24.773 PRESERVEDPARTITIONS:
2019-05-22 22:51:24.773 ERASEALL:False
2019-05-22 22:51:24.774 Load ARG Configuration
2019-05-22 22:51:24.810 Validating Download Configuration
2019-05-22 22:51:24.811 Image Search Path: E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00
2019-05-22 22:51:24.819 RAWPROGRAM file path: E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\rawprogram0.xml
2019-05-22 22:51:24.820 PATCH file path:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\patch0.xml
2019-05-22 22:51:24.820 Programmer Path:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:51:25.172 Process Index:0
2019-05-22 22:51:25.189 Qualcomm Flash Image Loader (QFIL) 2.0.1.9
2019-05-22 22:51:35.483 Start Download
2019-05-22 22:51:35.494 Program Path:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:51:35.502 ***** Working Folder:C:\Users\Grant\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
2019-05-22 22:53:05.646 Binary build date: Nov 21 2017 @ 02:53:37
2019-05-22 22:53:05.647 QSAHARASERVER CALLED LIKE THIS: 'E:\Users\Grant\Downloads\PH1 Qualcomm\Qualcomm_Flash_Image_Loader_v2.0.1.9\QSaharaServer.ex'Current working dir: C:\Users\Grant\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
2019-05-22 22:53:05.653 Sahara mappings:
2019-05-22 22:53:05.653 2: amss.mbn
2019-05-22 22:53:05.654 6: apps.mbn
2019-05-22 22:53:05.654 8: dsp1.mbn
2019-05-22 22:53:05.655 10: dbl.mbn
2019-05-22 22:53:05.655 11: osbl.mbn
2019-05-22 22:53:05.656 12: dsp2.mbn
2019-05-22 22:53:05.656 16: efs1.mbn
2019-05-22 22:53:05.657 17: efs2.mbn
2019-05-22 22:53:05.657 20: efs3.mbn
2019-05-22 22:53:05.658 21: sbl1.mbn
2019-05-22 22:53:05.658 22: sbl2.mbn
2019-05-22 22:53:05.659 23: rpm.mbn
2019-05-22 22:53:05.659 25: tz.mbn
2019-05-22 22:53:05.660 28: dsp3.mbn
2019-05-22 22:53:05.660 29: acdb.mbn
2019-05-22 22:53:05.661 30: wdt.mbn
2019-05-22 22:53:05.661 31: mba.mbn
2019-05-22 22:53:05.662 13: E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:53:05.662
2019-05-22 22:53:05.663 22:53:05: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
2019-05-22 22:53:05.663
2019-05-22 22:53:05.664 22:53:05: ERROR: function: sahara_main:924 Sahara protocol error
2019-05-22 22:53:05.664
2019-05-22 22:53:05.665 22:53:05: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2019-05-22 22:53:05.665
2019-05-22 22:53:05.666
2019-05-22 22:53:05.667 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2019-05-22 22:53:05.668 Finish Download
hi guys, sorry if this post or my comment is out of date, been awhile for too long
simple solution for Sahara Fail is just as simple as rename your image folder with alphanumeric characters without space and put it in your root directory (e.g. D drive) because Sahara can't recognize your folder if it use space in it's name
bapakerwe said:
hi guys, sorry if this post or my comment is out of date, been awhile for too long
simple solution for Sahara Fail is just as simple as rename your image folder with alphanumeric characters without space and put it in your root directory (e.g. D drive) because Sahara can't recognize your folder if it use space in it's name
Click to expand...
Click to collapse
How to do that?
Hey, I have a problem, I spend 2 days on it and can't find solution. So in the past I unlocked bootloader, used Qfil, everything was fine but few months ago i switch to Z fold 3 and stop using my G8X, now I have a buyer for that phone and I can't lock bootloader at all.
So manual pressing buttons not working, I tried hundred times. adb reboot bootloader/fastboot just restarting my phone. I have access to recovery, EDL mode etc, my phone is visible as adb devices.
Choosing option restart to bootloader in recovery just restarting my phone. I tried every f**cking thing to do it with Qfil and do it again with switching abl_a etc but It's always sahara fail doesn't matter what version qfil or QPST is. I even installed clear windows 7 and still same problem (on my main PC I'm using windows 11). adb, fastboot, qualcomm 9008, lg drivers, everything is installed.
I installed different OS with KDZ with android 9/10/11, Canadian/US, no different
I beg you, please give me something what I can try cause I'm going crazy here. Like it's unlocked, it's not a phone what you can't unlock. I was hoping to write fastboot oem lock and that's it.
With unlocked bootloader fingerprint reader not working. Guy is waiting with money, I said I need few days to fix it but I feel I tried everything.
Thanks everyone who will answer here.
You can try use ADB,adb reboot fastboot.If can't enter fastboot,that may be because boot or abl does not support FastBoot,you can try using adb reboot bootloader.
Like I said adb reboot fastboot and adb reboot bootloader just restarting my phone
SiNec said:
Like I said adb reboot fastboot and adb reboot bootloader just restarting my phone
Click to expand...
Click to collapse
If you cant get into qfil, then why are u expecting to get fastboot mode????
First load eng abl. For sahara error, use a different usb port, or restart to edl when you are connected to qfil or use a different pc.
lefttobleed said:
If you cant get into qfil, then why are u expecting to get fastboot mode????
First load eng abl. For sahara error, use a different usb port, or restart to edl when you are connected to qfil or use a different pc.
Click to expand...
Click to collapse
In 2 days of struggling I tried everything even if obviously it was stupid and not possible but that actually was answer to guy who said to try use that commends
I tried my PC and my laptop. Both of them had windows 11, I even installed Windows 7 on my laptop after many fails on both devices, all usb port on PC and laptop checked with 5 cables, with PC on tower cases and motherboard, on laptops i tried even usb type C, no results. Cable and PC exactly same what few month ago I used to unlocked it.
I'm always in edl mode cause with booted phone is just says "switch to edl -> fail to switch into emergency download mode"
I'm not good at English, hope you understand: how to lock bootloader
edl mode -> use QFIL load image abl_a, abl_b by abl unlock file ( this step help you get in to fastboot mode).
get into fastboot mode: using fastboot command
fastboot flash abl_a xxx (xxx = your stock abl_a file)
fastboot flash abl_b xxx (xxx = your stock abl_b file)
fastboot flash boot_a xxx (xxx = your stock boot_a file)
fastboot flash boot_a xxx (xxx = your stock boot_b file)
fastboot oem lock
but lock bootloader doesn't fix fingerprint scanner working, have to downgrade to android 9 and fix by hide code *#546368#*xxx# example:
KillerOpen said:
edl mode -> load image abl_a, abl_b by abl unlock file, get into fastboot mode: using fastboot command
fastboot flash abl_a xxx (xxx = your stock abl_a file)
fastboot flash abl_b xxx (xxx = your stock abl_b file)
fastboot flash boot_a xxx (xxx = your stock boot_a file)
fastboot flash boot_a xxx (xxx = your stock boot_b file)
fastboot oem lock
but lock bootloader doesn't fix fingerprint scanner working, have to downgrade to android 9 and fix by hide code *#546368#*xxx# example:
Click to expand...
Click to collapse
Thanks for reply. Its almost 3am for me and still fighting with it Fingerprint is one thing but my guy want locked bootloader cause he is scared of stuff like that and it shows warning when boot up.
But could you explain more your way with edl mode? I dont get it. Im trying for the whole day make rawprogram and patch so I could finally use QFIL, without it it's sahara problem. But all methods online are old. Most of it not supporting new KDZ files, python way not working, linux way not working. My phone is in 9008 drivers when in EDL mode and its not visible for adb. It's only visible with normal mode.
Is your way skip qfil and load modified adl files straight into device?
SiNec said:
Thanks for reply. Its almost 3am for me and still fighting with it Fingerprint is one thing but my guy want locked bootloader cause he is scared of stuff like that and it shows warning when boot up.
But could you explain more your way with edl mode? I dont get it. Im trying for the whole day make rawprogram and patch so I could finally use QFIL, without it it's sahara problem. But all methods online are old. Most of it not supporting new KDZ files, python way not working, linux way not working. My phone is in 9008 drivers when in EDL mode and its not visible for adb. It's only visible with normal mode.
Is your way skip qfil and load modified adl files straight into device?
Click to expand...
Click to collapse
if you want lock bootloader, enter edl mode, use QFIL load image abl_a and abl_b by a abl file (using to unlock), it help you can get intro fastboot ( press -vol and power until you hear sound on windows, release power, keep hold -vol ), when you get intro fastboot mode (status: unlocked) flash your stock abl_a abl_b boot_a boot_b by fastboot command before you lock bootloader by command: fastboot oem lock
But I cant use Qfil, All ways to get rawprogram and patch0 not works anymore. Some of them not supporting new KDZ, some of them have problems in general. I tried python way, linux way etc. All youtube videos are outdated. Idk how I can get that files for my g8x. without that(I think) I'm getting Sahara fail error and cant open partition menager. Last year when I was unlocking my bootloader everything work perfect, I rooted like 10lg before, first time in my life I have such a big problem with that phone.
SiNec said:
But I cant use Qfil, All ways to get rawprogram and patch0 not works anymore. Some of them not supporting new KDZ, some of them have problems in general. I tried python way, linux way etc. All youtube videos are outdated. Idk how I can get that files for my g8x. without that(I think) I'm getting Sahara fail error and cant open partition menager. Last year when I was unlocking my bootloader everything work perfect, I rooted like 10lg before, first time in my life I have such a big problem with that phone.
Click to expand...
Click to collapse
QFIL -> Flat Build > Browse > choose G8x firehose > Tools > Partition manager
Did it work ?
KillerOpen said:
QFIL -> Flat Build > Browse > choose G8x firehose > Tools > Partition manager
Did it work ?
Click to expand...
Click to collapse
I'm still getting sahara fail error. 2 computers, trying windows 11, windows 8, windows 7, bunch of different drivers, 5 cables, still nothing. It's still "unable to read packet header" error :/
SiNec said:
I'm still getting sahara fail error. 2 computers, trying windows 11, windows 8, windows 7, bunch of different drivers, 5 cables, still nothing. It's still "unable to read packet header" error :/
Click to expand...
Click to collapse
Unistall your QFIL, try this: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file
If it wont work, I give in.
KillerOpen said:
Unistall your QFIL, try this: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file
If it wont work, I give in.
Click to expand...
Click to collapse
I have a QPST from the beginning. I tried all different kinds, and qfill standalone, nothing helps :/ Thank you anyway for help
KillerOpen said:
QFIL -> Flat Build > Browse > choose G8x firehose > Tools > Partition manager
Did it work ?
Click to expand...
Click to collapse
This is log:
2022-06-29 03:07:44.989 Image Search Path: C:\Users\Kopec\Downloads\firehose\
2022-06-29 03:07:45.004 Start Download
2022-06-29 03:07:45.004 Program Path:C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:07:45.017 ***** Working Folder:C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.465 Binary build date: Jun 25 2019 @ 03:16:15
2022-06-29 03:09:15.469 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.475 Sahara mappings:
2022-06-29 03:09:15.477 2: amss.mbn
2022-06-29 03:09:15.482 6: apps.mbn
2022-06-29 03:09:15.485 8: dsp1.mbn
2022-06-29 03:09:15.488 10: dbl.mbn
2022-06-29 03:09:15.491 11: osbl.mbn
2022-06-29 03:09:15.493 12: dsp2.mbn
2022-06-29 03:09:15.495 16: efs1.mbn
2022-06-29 03:09:15.496 17: efs2.mbn
2022-06-29 03:09:15.498 20: efs3.mbn
2022-06-29 03:09:15.499 21: sbl1.mbn
2022-06-29 03:09:15.500 22: sbl2.mbn
2022-06-29 03:09:15.501 23: rpm.mbn
2022-06-29 03:09:15.502 25: tz.mbn
2022-06-29 03:09:15.504 28: dsp3.mbn
2022-06-29 03:09:15.505 29: acdb.mbn
2022-06-29 03:09:15.515 30: wdt.mbn
2022-06-29 03:09:15.516 31: mba.mbn
2022-06-29 03:09:15.517 13: C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:09:15.517
2022-06-29 03:09:15.518 03:09:15: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2022-06-29 03:09:15.519
2022-06-29 03:09:15.519 03:09:15: ERROR: function: sahara_main:982 Sahara protocol error
2022-06-29 03:09:15.520
2022-06-29 03:09:15.521 03:09:15: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-06-29 03:09:15.522
2022-06-29 03:09:15.522
2022-06-29 03:09:15.523 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-06-29 03:09:15.529 Finish Get GPT
SiNec said:
This is log:
2022-06-29 03:07:44.989 Image Search Path: C:\Users\Kopec\Downloads\firehose\
2022-06-29 03:07:45.004 Start Download
2022-06-29 03:07:45.004 Program Path:C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:07:45.017 ***** Working Folder:C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.465 Binary build date: Jun 25 2019 @ 03:16:15
2022-06-29 03:09:15.469 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.475 Sahara mappings:
2022-06-29 03:09:15.477 2: amss.mbn
2022-06-29 03:09:15.482 6: apps.mbn
2022-06-29 03:09:15.485 8: dsp1.mbn
2022-06-29 03:09:15.488 10: dbl.mbn
2022-06-29 03:09:15.491 11: osbl.mbn
2022-06-29 03:09:15.493 12: dsp2.mbn
2022-06-29 03:09:15.495 16: efs1.mbn
2022-06-29 03:09:15.496 17: efs2.mbn
2022-06-29 03:09:15.498 20: efs3.mbn
2022-06-29 03:09:15.499 21: sbl1.mbn
2022-06-29 03:09:15.500 22: sbl2.mbn
2022-06-29 03:09:15.501 23: rpm.mbn
2022-06-29 03:09:15.502 25: tz.mbn
2022-06-29 03:09:15.504 28: dsp3.mbn
2022-06-29 03:09:15.505 29: acdb.mbn
2022-06-29 03:09:15.515 30: wdt.mbn
2022-06-29 03:09:15.516 31: mba.mbn
2022-06-29 03:09:15.517 13: C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:09:15.517
2022-06-29 03:09:15.518 03:09:15: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2022-06-29 03:09:15.519
2022-06-29 03:09:15.519 03:09:15: ERROR: function: sahara_main:982 Sahara protocol error
2022-06-29 03:09:15.520
2022-06-29 03:09:15.521 03:09:15: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-06-29 03:09:15.522
2022-06-29 03:09:15.522
2022-06-29 03:09:15.523 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-06-29 03:09:15.529 Finish Get GPT
Click to expand...
Click to collapse
have you switch emmc to ufs on QFIL ?
KillerOpen said:
have you switch emmc to ufs on QFIL ?
Click to expand...
Click to collapse
Yes, all that basic stuff, I done
KillerOpen said:
I'm not good at English, hope you understand: how to lock bootloader
edl mode -> use QFIL load image abl_a, abl_b by abl unlock file ( this step help you get in to fastboot mode).
get into fastboot mode: using fastboot command
fastboot flash abl_a xxx (xxx = your stock abl_a file)
fastboot flash abl_b xxx (xxx = your stock abl_b file)
fastboot flash boot_a xxx (xxx = your stock boot_a file)
fastboot flash boot_a xxx (xxx = your stock boot_b file)
fastboot oem lock
but lock bootloader doesn't fix fingerprint scanner working, have to downgrade to android 9 and fix by hide code *#546368#*xxx# example:
Click to expand...
Click to collapse
Friend I have a problem with my g8x and the fingerprint sensor, since I did a bad flashed to a11 it does not work for me it gives me an error, do you think that downloading a9 can fix it?
I have blocked the network and error in nt code but I have understood that in another problem and it is fixed through server
mclarenf195 said:
Friend I have a problem with my g8x and the fingerprint sensor, since I did a bad flashed to a11 it does not work for me it gives me an error, do you think that downloading a9 can fix it?
I have blocked the network and error in nt code but I have understood that in another problem and it is fixed through server
Click to expand...
Click to collapse
I've tried A9 (the indian variant given that's the one people say works) to fix my fp scanner and had no luck, but that's the only solution people give so maybe on yours it will work.
mclarenf195 said:
Friend I have a problem with my g8x and the fingerprint sensor, since I did a bad flashed to a11 it does not work for me it gives me an error, do you think that downloading a9 can fix it?
I have blocked the network and error in nt code but I have understood that in another problem and it is fixed through server
Click to expand...
Click to collapse
I tried with Android 9 UM version and it works. Test will fail but when you go to the settings it will let you to scan fingerprint. After that you need to update phone from the phone, not installing new KDZ. when you will update to androind 10/11(yours prefers) it's still working. I even did factory reset and it still works fine
SiNec said:
This is log:
2022-06-29 03:07:44.989 Image Search Path: C:\Users\Kopec\Downloads\firehose\
2022-06-29 03:07:45.004 Start Download
2022-06-29 03:07:45.004 Program Path:C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:07:45.017 ***** Working Folder:C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.465 Binary build date: Jun 25 2019 @ 03:16:15
2022-06-29 03:09:15.469 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.475 Sahara mappings:
2022-06-29 03:09:15.477 2: amss.mbn
2022-06-29 03:09:15.482 6: apps.mbn
2022-06-29 03:09:15.485 8: dsp1.mbn
2022-06-29 03:09:15.488 10: dbl.mbn
2022-06-29 03:09:15.491 11: osbl.mbn
2022-06-29 03:09:15.493 12: dsp2.mbn
2022-06-29 03:09:15.495 16: efs1.mbn
2022-06-29 03:09:15.496 17: efs2.mbn
2022-06-29 03:09:15.498 20: efs3.mbn
2022-06-29 03:09:15.499 21: sbl1.mbn
2022-06-29 03:09:15.500 22: sbl2.mbn
2022-06-29 03:09:15.501 23: rpm.mbn
2022-06-29 03:09:15.502 25: tz.mbn
2022-06-29 03:09:15.504 28: dsp3.mbn
2022-06-29 03:09:15.505 29: acdb.mbn
2022-06-29 03:09:15.515 30: wdt.mbn
2022-06-29 03:09:15.516 31: mba.mbn
2022-06-29 03:09:15.517 13: C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:09:15.517
2022-06-29 03:09:15.518 03:09:15: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2022-06-29 03:09:15.519
2022-06-29 03:09:15.519 03:09:15: ERROR: function: sahara_main:982 Sahara protocol error
2022-06-29 03:09:15.520
2022-06-29 03:09:15.521 03:09:15: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-06-29 03:09:15.522
2022-06-29 03:09:15.522
2022-06-29 03:09:15.523 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-06-29 03:09:15.529 Finish Get GPT
Click to expand...
Click to collapse
The elf file is corrupt
Hello.
I tried to completely update the Taiwanese firmware.
Basically I flashed all the images taken from the OTA to my phone using fastboot.
The OTA is from here: https://forum.xda-developers.com/t/global-eu-collection-of-firmware-files.4478153/
As a result i got hard brick (black screen). Device doesn't respond to presses, nothing happens. The computer (Windows 11) doesn't see the device.
I performed the following steps:
Code:
adb shell getprop ro.product.name
RMX3301
adb shell getprop ro.build.version.ota
RMX3301_11.C.16_1160_202303162143
adb shell getprop ro.build.version.realmeui
v4.0
adb shell getprop ro.build.oplus_nv_id
00011010
Download OTA:
Code:
E:\Programs\Python\Python39\python.exe .\realme_ota\main.py RMX3301 RMX3301_11.C.16_1160_202303162143 4 00011010
PS D:\0my\phone\realme gt 2 pro\tools\realme-ota> E:\Programs\Python\Python39\python.exe .\realme_ota\main.py RMX3301 RMX3301_11.C.16_1160_202303162143 4 00011010
[2023-04-18 17:28:19.988575] I: Load payload for RMX3301 (RealmeUI V4)
[2023-04-18 17:28:19.988575] I: Wait for the endpoint to reply
PS D:\0my\phone\realme gt 2 pro\tools\realme-ota> [2023-04-18 17:28:21.363576] I: Load payload for RMX3301 (RealmeUI V4)
[2023-04-18 17:28:21.363576] I: Wait for the endpoint to reply
[2023-04-18 17:28:22.285462] I: All good
[2023-04-18 17:28:22.285462] I: Let's rock
[2023-04-18 17:28:22.285462] I: Party time
{
"aid": "RMX3301NV1A_11.C",
"androidVersion": "Android 13",
"colorOSVersion": "ColorOS 13.0",
"componentAssembleType": true,
"components": [
{
"componentId": "my_manifest_RMX3301_11.C.16_1160_202303162143.1A.6f9e3487",
"componentName": "my_manifest",
"componentPackets": {
"id": "foreign_my_manifest_RMX3301_11.C.16_1160_202303162143.1A.6f9e3487_1_65790f8f58d286c8d65dff0ada40aee7",
"manualUrl": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/18/71792dbf4bd649ff9346667b1f25017a.zip",
"md5": "65790f8f58d286c8d65dff0ada40aee7",
"size": "5871425918",
"type": "1",
"url": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/18/71792dbf4bd649ff9346667b1f25017a.zip",
"vabInfo": {
"data": {
"extra_params": "metadata_hash:0c395f95f20207df32aaff86ff7e7ea393369f87876bafc4e9bc517a30077095",
"header": [
"FILE_HASH=idmYLwxiV6ELPhR0QcUtIc5EldhrilpDXfSet7/lF4U=",
"FILE_SIZE=5871420318",
"METADATA_HASH=Y4t+f+3X/Taw1VUq6GqA2wuGcWLk2PGtT8IFpR5GW5M=",
"METADATA_SIZE=225231",
"security_patch=2023-03-05",
"security_patch_vendor=2023-03-05",
"oplus_update_engine_verify_disable=0",
"ota_target_version=RMX3301_11.C.16_1160_202303162143",
"oplus_rom_version=V13.0.0",
"oplus_separate_soft=216AC"
],
"otaStreamingProperty": "payload_metadata.bin:2053:225498,payload.bin:2053:5871420318,payload_properties.txt:5871422429:357,metadata:69:997,metadata.pb:1134:852",
"vab_package_hash": "65790f8f58d286c8d65dff0ada40aee7"
}
}
},
"componentVersion": "RMX3301_11.C.16_1160_202303162143.1A.6f9e3487"
}
],
"decentralize": {
"offset": 508,
"round": 28800,
"strategyVersion": "default"
},
"description": {
"firstTitle": "This update integrates the latest Android security patches, fixes some known issues, and improves system performance.",
"panelUrl": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/31/06c848b83adf43b9afa0a61c4e6f0d30.html",
"share": ".",
"url": "https://h5fsf.coloros.com/3adb669b49144103b5afb789182233ec/static/index.html#/about"
},
"googlePatchInfo": "0",
"id": "6426c6bf124eec0115884385",
"isNvDescription": true,
"isRecruit": false,
"isSecret": false,
"noticeType": 0,
"nvId16": "NV1A",
"osVersion": "ColorOS 13.0",
"otaVersion": "RMX3301_11.C.16_1160_202303162143",
"paramFlag": 1,
"parent": "ota",
"realAndroidVersion": "Android 13",
"realOsVersion": "ColorOS 13.0.0",
"reminderType": 0,
"rid": "d937f577-0f8f-40f5-8bef-d376dbb8138d",
"securityPatch": "2023-03-05",
"securityPatchVendor": "2023-03-05",
"silenceUpdate": 0,
"status": "published",
"versionCode": 1160,
"versionName": "RMX3301_11_C.16",
"versionTypeH5": "Official version"
}
Flashed all images to phone.
Code:
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash abl abl.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop aop.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop_config aop_config.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash bluetooth bluetooth.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash boot boot.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash cpucp cpucp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash devcfg devcfg.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dsp dsp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dtbo dtbo.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash engineering_cdt engineering_cdt.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash featenabler featenabler.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash hyp hyp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash imagefv imagefv.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash keymaster keymaster.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash modem modem.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_bigball my_bigball.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_carrier my_carrier.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_engineering my_engineering.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_heytap my_heytap.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_manifest my_manifest.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_product my_product.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_region my_region.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_stock my_stock.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm odm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm_dlkm odm_dlkm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplusstanvbk oplusstanvbk.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplus_sec oplus_sec.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash product product.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash qupfw qupfw.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash recovery recovery.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash shrm shrm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash splash splash.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system system.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system_ext system_ext.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash tz tz.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefi uefi.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefisecapp uefisecapp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta vbmeta.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_system vbmeta_system.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_vendor vbmeta_vendor.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor vendor.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_boot vendor_boot.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_dlkm vendor_dlkm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl xbl.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_config xbl_config.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_ramdump xbl_ramdump.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing logs.
Code:
PS C:\Users\PeyVodka> cd D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash abl abl.img
Sending 'abl' (216 KB) OKAY [ 0.009s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop aop.img
Sending 'aop' (256 KB) OKAY [ 0.010s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop_config aop_config.img
Sending 'aop_config' (16 KB) OKAY [ 0.003s]
Writing 'aop_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash bluetooth bluetooth.img
Sending 'bluetooth' (1788 KB) OKAY [ 0.063s]
Writing 'bluetooth' OKAY [ 0.006s]
Finished. Total time: 0.193s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash boot boot.img
Sending 'boot_b' (196608 KB) OKAY [ 6.557s]
Writing 'boot_b' OKAY [ 0.342s]
Finished. Total time: 7.086s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash cpucp cpucp.img
Sending 'cpucp' (152 KB) OKAY [ 0.006s]
Writing 'cpucp' OKAY [ 0.001s]
Finished. Total time: 0.119s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash devcfg devcfg.img
Sending 'devcfg' (56 KB) OKAY [ 0.004s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 2.328s]
Writing 'dsp' OKAY [ 0.188s]
Finished. Total time: 2.627s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.864s]
Writing 'dtbo' OKAY [ 0.076s]
Finished. Total time: 1.044s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash engineering_cdt engineering_cdt.img
Sending 'engineering_cdt' (1024 KB) OKAY [ 0.066s]
Writing 'engineering_cdt' OKAY [ 0.004s]
Finished. Total time: 0.196s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash featenabler featenabler.img
Sending 'featenabler' (92 KB) OKAY [ 0.005s]
Writing 'featenabler' OKAY [ 0.001s]
Finished. Total time: 0.129s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash hyp hyp.img
Sending 'hyp' (1356 KB) OKAY [ 0.057s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash imagefv imagefv.img
Sending 'imagefv' (72 KB) OKAY [ 0.004s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash keymaster keymaster.img
Sending 'keymaster' (360 KB) OKAY [ 0.013s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash modem modem.img
Sending 'modem_b' (296436 KB) OKAY [ 11.736s]
Writing 'modem_b' OKAY [ 0.579s]
Finished. Total time: 12.465s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_bigball my_bigball.img
Sending sparse 'my_bigball' 1/2 (786428 KB) OKAY [ 24.105s]
Writing 'my_bigball' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_carrier my_carrier.img
Sending 'my_carrier' (328 KB) OKAY [ 0.016s]
Writing 'my_carrier' FAILED (remote: '(my_carrier_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_engineering my_engineering.img
Sending 'my_engineering' (328 KB) OKAY [ 0.011s]
Writing 'my_engineering' FAILED (remote: '(my_engineering_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_heytap my_heytap.img
Sending 'my_heytap' (775220 KB) OKAY [ 33.016s]
Writing 'my_heytap' FAILED (remote: '(my_heytap_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_manifest my_manifest.img
Sending 'my_manifest' (404 KB) OKAY [ 0.016s]
Writing 'my_manifest' FAILED (remote: '(my_manifest_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_product my_product.img
Sending 'my_product' (507464 KB) OKAY [ 20.867s]
Writing 'my_product' FAILED (remote: '(my_product_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_region my_region.img
Sending 'my_region' (3544 KB) OKAY [ 0.153s]
Writing 'my_region' FAILED (remote: '(my_region_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_stock my_stock.img
Sending sparse 'my_stock' 1/2 (786428 KB) OKAY [ 24.981s]
Writing 'my_stock' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm odm.img
Sending sparse 'odm' 1/2 (786428 KB) OKAY [ 34.161s]
Writing 'odm' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm_dlkm odm_dlkm.img
Sending 'odm_dlkm' (340 KB) OKAY [ 0.012s]
Writing 'odm_dlkm' FAILED (remote: '(odm_dlkm_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplusstanvbk oplusstanvbk.img
Sending 'oplusstanvbk' (2776 KB) OKAY [ 0.095s]
Writing 'oplusstanvbk' OKAY [ 0.007s]
Finished. Total time: 0.214s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplus_sec oplus_sec.img
Sending 'oplus_sec' (328 KB) OKAY [ 0.012s]
Writing 'oplus_sec' OKAY [ 0.002s]
Finished. Total time: 0.124s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash product product.img
Sending 'product' (12516 KB) OKAY [ 0.465s]
Writing 'product' FAILED (remote: '(product_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash qupfw qupfw.img
Sending 'qupfw' (52 KB) OKAY [ 0.003s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.613s]
Writing 'recovery' OKAY [ 0.176s]
Finished. Total time: 3.905s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash shrm shrm.img
Sending 'shrm' (68 KB) OKAY [ 0.003s]
Writing 'shrm' OKAY [ 0.001s]
Finished. Total time: 0.114s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash splash splash.img
Sending 'splash' (528 KB) OKAY [ 0.018s]
Writing 'splash' OKAY [ 0.002s]
Finished. Total time: 0.131s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system system.img
Sending 'system' (678708 KB) OKAY [ 29.067s]
Writing 'system' FAILED (remote: '(system_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system_ext system_ext.img
Sending sparse 'system_ext' 1/2 (786428 KB) OKAY [ 25.175s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash tz tz.img
Sending 'tz' (3712 KB) OKAY [ 0.133s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefi uefi.img
Sending 'uefi' (3080 KB) OKAY [ 0.133s]
Writing 'uefi' OKAY [ 0.007s]
Finished. Total time: 0.255s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (168 KB) OKAY [ 0.007s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta vbmeta.img
Sending 'vbmeta' (12 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.123s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.127s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_vendor vbmeta_vendor.img
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
Finished. Total time: 0.118s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor vendor.img
Sending 'vendor' (650424 KB) OKAY [ 29.825s]
Writing 'vendor' FAILED (remote: '(vendor_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (196608 KB) OKAY [ 6.615s]
Writing 'vendor_boot' OKAY [ 0.326s]
Finished. Total time: 7.058s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_dlkm vendor_dlkm.img
Sending 'vendor_dlkm' (144052 KB) OKAY [ 5.430s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl xbl.img
Sending 'xbl' (1080 KB) OKAY [ 0.056s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_config xbl_config.img
Sending 'xbl_config' (140 KB) OKAY [ 0.006s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_ramdump xbl_ramdump.img
Sending 'xbl_ramdump' (788 KB) OKAY [ 0.026s]
Writing 'xbl_ramdump' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807>
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (12 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.112s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807>
I took the phone apart and got to the test points as described in this post: https://forum.xda-developers.com/t/solved-edl-test-points.4471613/#post-87186865
To short-circuit them and put them into EDL Mode.
I checked the voltage with a voltmeter, it is ~1.8v and 0v. Everything seems to be fine and should work.
But my device is still not detected by the computer (Windows 11).
Any idea how to solve this problem?
I'm not sure what the exact cause is. I didn't think that flashing all the firmware images would be a very bad idea. And as far as I know EDL mode should remain available for me in any case.
And what could be causing the problem?
The only thing that seems strange from flashing logs is that this time boot was written to boot_b for some reason. Before that it usually went to boot_a. I'm not sure if this could have corrupted boot.
Okay. I was able to put the device into EDL mode. I soldered the test points to short it. Because the device seems to exit EDL mode every few seconds. Exactly as noted in these messages:
[Solved] EDL test points
Hi guys, i am looking for some help as my Realme GT2 Pro is dead bricked (ie. no response to buttons + usb) I was able to open the back cover but i am not sure which are the correct test points for EDL mode. Below is the picture of the...
forum.xda-developers.com
[Solved] EDL test points
Hi guys, i am looking for some help as my Realme GT2 Pro is dead bricked (ie. no response to buttons + usb) I was able to open the back cover but i am not sure which are the correct test points for EDL mode. Below is the picture of the...
forum.xda-developers.com
So, I got the firware RMX3301export_11_A.06_2022020500280000 from https://realmefirmware.com/realme-gt-2-pro-firmware/
What do I have to do next to flash the device free of charge myself?
A bit late now, but if you have a chance it's helpful to make a backup copy before you go flashing.
If your Firehose loader for EDL is unrestricted you can do it as a whole device and/or by partition.
Did you try before: fastboot flashing unlock_critical
Have you got a Firehose loader and gotten an EDL client to work yet? (Either the Python or mine.)
Renate said:
A bit late now, but if you have a chance it's helpful to make a backup copy before you go flashing.
If your Firehose loader for EDL is unrestricted you can do it as a whole device and/or by partition.
Did you try before: fastboot flashing unlock_critical
Have you got a Firehose loader and gotten an EDL client to work yet? (Either the Python or mine.)
Click to expand...
Click to collapse
I have no access to fastboot. Fastboot does not see my device after it became a hard brick.
I have not tried Firehose or other EDL clients. I tried opening QFIL. There I see that my device is recognized as qualcomm hs-usb qdloader 9008.
I have no idea what to do next.
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My stuff is in my sig.
Renate said:
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
View attachment 5892303
My stuff is in my sig.
Click to expand...
Click to collapse
Okay. I'm going to try bkerler's Python now.
How do I see the solution to my problem:
1. I need to overwrite boot.img in boot_a with the command "edl w boot_a boot.img".
I believe that after that I will transfer my device to soft brick state and be able to boot into recovery mode.
2. In recovery mode, I will be able to use fastboot with my unlocked bootloader to flash the device normally.
Is my plan viable?
PeyVodka said:
Is my plan viable?
Click to expand...
Click to collapse
Sure.
Still, flashing with EDL, fastboot, dd, whatever all do the same stuff.
Renate said:
Sure.
Still, flashing with EDL, fastboot, dd, whatever all do the same stuff.
Click to expand...
Click to collapse
I'm a little confused trying to install bkerler's edl on Windows 11:
I am following the installation instructions for windows.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Code:
PS D:\Download\Browser\firmware\edl-3.52.1\edl-3.52.1> python3 setup.py build
running build
running build_py
running egg_info
writing edl.egg-info\PKG-INFO
writing dependency_links to edl.egg-info\dependency_links.txt
writing requirements to edl.egg-info\requires.txt
writing top-level names to edl.egg-info\top_level.txt
reading manifest file 'edl.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*' under directory 'Loaders'
adding license file 'LICENSE'
writing manifest file 'edl.egg-info\SOURCES.txt'
running build_scripts
error: file 'D:\Download\Browser\firmware\edl-3.52.1\edl-3.52.1\Loaders\fhloaderparse.py' does not exist
There are no loaders for realme in the repository. What is this loader, where can I get the loader in my case?
GitHub - bkerler/Loaders: EDL Loaders
EDL Loaders. Contribute to bkerler/Loaders development by creating an account on GitHub.
github.com
PeyVodka said:
I'm a little confused trying to install bkerler's edl on Windows 11:
Click to expand...
Click to collapse
Lol. Now you know why I wrote a native Windows version.
I have less dependencies and admittedly, less features.
Renate said:
Lol. Now you know why I wrote a native Windows version.
I have less dependencies and admittedly, less features.
Click to expand...
Click to collapse
Yes, I understand. In general, the situation is familiar to me.
Will this allow me to overwrite boot_a with boot.img from OTA firmware according to my plan?
How to do this with your tool?
Is it:
Code:
edl.exe /w /pboot_a boot.img
In this case, I will be happy to use your tool.
EDL Utility
PeyVodka said:
Is it:
Click to expand...
Click to collapse
Yup, that should do it.
You'll need a Firehose loader.
There might be one in the QFIL stuff.
There might be one in the bkerler GitHub.
Identify what you've got with edl.exe /l
Renate said:
Yup, that should do it.
You'll need a Firehose loader.
There might be one in the QFIL stuff.
There might be one in the bkerler GitHub.
Identify what you've got with edl.exe /l
Click to expand...
Click to collapse
Okay.
I reinstalled driver for my device via Zadig.
Downloaded your tool and execute:
Code:
PS D:\Download\Browser\firmware> .\edl.exe /l
Found EDL 9008
Serial: $SERIAL$
Received unexpected 04 command
PS D:\Download\Browser\firmware> .\edl.exe /l
Found EDL 9008
Resetting Sahara
Could not read device
Did i do something wrong?
PeyVodka said:
Did i do something wrong?
Click to expand...
Click to collapse
That all looks good.
The Sahara protocol is very brittle (and stupid).
If an attempt at communication has occured but failed, the device will be in la-la land.
Do a clean reset.
(Which is what edl.exe was trying to do, but the implementations of Sahara are all different.)
Actually, it could be flakey communication too. Check your cables and ports.
Edit: Mmm, it could be that this needs some authorization.
In which case you can only do this with the RealMe tools.
You should try the bkerler too. You can leave it on Zadig for that.
Renate said:
That all looks good.
The Sahara protocol is very brittle (and stupid).
If an attempt at communication has occured but failed, the device will be in la-la land.
Do a clean reset.
(Which is what edl.exe was trying to do, but the implementations of Sahara are all different.)
Actually, it could be flakey communication too. Check your cables and ports.
Edit: Mmm, it could be that this needs some authorization.
In which case you can only do this with the RealMe tools.
You should try the bkerler too. You can leave it on Zadig for that.
Click to expand...
Click to collapse
I tried bkerler edl on Ubuntu. It got stuck on this message:
Code:
edl --serial
Capstone library is missing (optional).
Keystone library is missing (optional).
No module named 'Cryptodome'
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Trying with no loader given ...
main - Waiting for the device
Detected 0x5c6:0x9008 device at: /dev/ttyUSB0
main - Device detected :)
sahara - Protocol version: 3, Version supported: 1
main - Mode detected: sahara
"it could be that this needs some authorization."
Could this have something to do with the information in this post?:
[No auth collection] Realme No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Realme has blocked offline flashing with authentication required to flash their device. This files will ultimately help you to fix the authorisation issue and hence unbrick your Realme device via EDL mode...
forum.xda-developers.com
PeyVodka said:
It got stuck on this message
Click to expand...
Click to collapse
Normally you should be able to get beyond this point with any device.
The authorization comes in Firehose, not Sahara.
Could you try (after a reset): edl.exe /l /v
See, a custom PBL would be unexpected thing.
Your tool.
I've tried several times, it keeps giving these messages one after another.
Code:
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Found EDL 9008
USB maximum packet: in=512, out=512
Received 01 command
Received 0b command
Received 0e command
Serial: $SERIAL$
Received 04 command
Sahara exec command 2 unsupported
Received 04 command
Received unexpected 04 command
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Found EDL 9008
USB maximum packet: in=512, out=512
Resetting Sahara
Could not read device
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Could not find EDL device
Here I was told that there is currently no Firehose for my device.
[No auth collection] Realme No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Realme has blocked offline flashing with authentication required to flash their device. This files will ultimately help you to fix the authorisation issue and hence unbrick your Realme device via EDL mode...
forum.xda-developers.com
Renate said:
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
View attachment 5892303
My stuff is in my sig.
Click to expand...
Click to collapse
By the they, how do I roll back the changes made by Zadig? From WinUSB.sys driver to qcusbser.sys
UPD: Ok. I've just deleted it via Windows Device Manager.
PeyVodka said:
Code:
Sahara exec command 2 unsupported
Click to expand...
Click to collapse
Well, that is strange. I've run into that before on some other Chinese stuff.
Apparently they never burned a HWID or disabled the querying of it.
I'm quite sure that Qualcomm would never make a custom PBL for anybody.
I don't know if they disabled querying of the hash too.
Everyone, support this post on realme's website. Let's make Realme release private recovery tools via EDL mode to the public!
So we can experiment with our purchased devices and not pay money for something we could always do for free!
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com
Renate said:
Well, that is strange. I've run into that before on some other Chinese stuff.
Apparently they never burned a HWID or disabled the querying of it.
I'm quite sure that Qualcomm would never make a custom PBL for anybody.
I don't know if they disabled querying of the hash too.
Click to expand...
Click to collapse
My dear friend and g0d-tier researcher M3ik Shizuka was able to "spell" offline access to both obfuscated tools. I couldn't believe my eyes.
Indeed, now that I connected my device in MsmDownloadTool, it stopped exiting EDL mode every few seconds. However, to enter EDL mode, I still had to solder test points. According to the status information and logs, I was finally able to connect via Sahara.
Unfortunately, for some stages of verification and data download, the MsmDownloadTool requires authorization with the servers. Apparently, MsmDownloadTool is really the official leaked tool.
Realme Login Tool makes a GET request to check the OPT code on api2.realmelogin.com.
I am not competent in this, but I hope that knowledgeable people can figure out from the log if there is anything useful that we can learn from sniffing the COM port. So that we can eventually use this to interact with the device via EDL mode with other tools.
MsmDownloadTool logs:
Code:
=========================================================
| Msm Download Tool V2.0.67 for eMMC/UFS
|
| Build Data: Nov 2 2021
| Build Time: 20:12:20
=========================================================
[PID:10472] [TID:15296] [2023-04-21 21:16:32::0323] Start log...
[PID:10472] [TID:15296] [2023-04-21 21:16:32::0468] mac:MAC_ADDRESS
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0680] Path:D:\RMX3301export_11_A.06_2022020500280000\RMX3301export_11_A.06_2022020500280000.ofp
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0804] Project:PROJECT_CODE, Compatible:
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0805] Strorage type: UFS
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Mode:After-sales
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Filter Metadata is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Binding Metadata is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Download Config is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Download Config Signed is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Support Reset is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Cloud Flag is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Multi Project is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Erase Oder is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] WO3 is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] UFS is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] SV is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] NV is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] VC is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] OCDT is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Root is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Secsmt is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Support FC is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] -------------------
[PID:10472] [TID:11916] [2023-04-21 21:19:47::0425] Device Remove: \\?\USB#VID_05C6&PID_9008...
[PID:10472] [TID:11916] [2023-04-21 21:20:28::0540] Device Arrival: \\?\USB#VID_05C6&PID_9008...
[PID:10472] [TID:11916] [2023-04-21 21:20:28::0541] Friendly Name: Qualcomm HS-USB QDLoader 9008 (COM5)
[PID:10472] [TID:15296] [2023-04-21 21:20:35::0046] Click Button Refresh
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0202] Click Button Start, mode:After-sale, project:PROJECT_CODE
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] IsPackImage is true
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] FactoryLine is false
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] BootOnly is false
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] DisableBootWizard is false
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Download start
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Set download status ,current status: COM_DOWNLOAD.
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Open the serial device
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Open the serial device retry = 1
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0239] [COM5] Set Sahara file ok��sahara file: prog_firehose_ddr.elf.
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0254] [COM5] Attempting to send a Sahara message for communication
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0254] [COM5] Downloading Firehose protocol file via Sahara protocol
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0811] [COM5] Sahara communication succeeded
[PID:10472] [TID:13348] [2023-04-21 21:20:51::0138] [COM5] filename=ChainedTableOfDigests_PROJECT_CODE_persist_no_userdata_no
[PID:10472] [TID:13348] [2023-04-21 21:20:52::0166] [COM5] Trying to handshake via Firehose communication
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0294] [COM5] Configure the settings of Firehose communication data transmission
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0389] [COM5] Get sign data
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0574] [COM5] ID:CHIP_ID, B:enable
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0574] [COM5] old_sw_name_sign:OLD_SW_NAME_SIGN, new_sw_name_sign:NEW_SW_NAME_SIGN
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0575] [COM5] Verify Data
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0361] [COM5] FirehoseCheckRSP is ERROR, hr=1
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0361] [COM5] Rsp:
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: verify failed." /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0362] [COM5] Verify pass
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0363] [COM5] Current download task end,elapsed time:416s.
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0363] [COM5] Upload download result. chip id: CHIP_ID, result: 1, project: PROJECT_CODE
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0373] [COM5] Upload download result failed.
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0373] [COM5] Close the serial device
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] Download failed
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] Determine whether to upload the download info
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] compress file, retry time is 4
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0514] [COM5] compress file success
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0515] [COM5] start to upload
[PID:10472] [TID:15296] [2023-04-21 21:28:49::0756] Click Button Stop