Меню

Qfil ошибка download fail firehose fail fhloader fail process fail

  • #1

Any help well come ,here’s log:

Validating Application Configuration
Load APP Configuration
COM:33
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:Program FilesQualcommQPSTbinuser_prog_emmc_firehose_8x10.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:Program FilesQualcommQPSTbin
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8×26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:Temp0000000.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: C:Program FilesQualcommQPSTbin
RAWPROGRAM file path: C:Program FilesQualcommQPSTbinrawprogram0.xml
PATCH file path:C:Program FilesQualcommQPSTbinpatch0.xml
Programmer Path:C:Program FilesQualcommQPSTbinuser_prog_emmc_firehose_8x10.mbn
Process Index:0
Start Download
Program Path:C:Program FilesQualcommQPSTbinuser_prog_emmc_firehose_8x10.mbn
***** Working Folder:C:UsersLenovoAppDataRoamingQualcommQFILCOMPORT_33
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: ‘C:Program FilesQualcommQPSTbinQSaharaServer.ex’Current working dir: C:UsersLenovoAppDataRoamingQualcommQFILCOMPORT_33
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:Program FilesQualcommQPSTbinuser_prog_emmc_firehose_8x10.mbn
18:54:51: Requested ID 13, file: «C:Program FilesQualcommQPSTbinuser_prog_emmc_firehose_8x10.mbn»
18:54:51: 79996 bytes transferred in 0.015000 seconds (5.0860MBps)
18:54:51: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
18:54:51: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds…
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8×26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:UsersLenovoAppDataRoamingQualcommQFILCOMPORT_33
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
18:54:54: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:Program FilesQualcommQPSTbinfh_loader.exe —port=\.COM33 —sendxml=rawprogram0.xml —search_path=C:Program FilesQualcommQPSTbin —noprompt —showpercentagecomplete —zlpawarehost=1 —memoryname=emmc
************************************************
18:54:54: INFO: Current working dir (cwd): C:UsersLenovoAppDataRoamingQualcommQFILCOMPORT_33
18:54:54: INFO: Showing network mappings to allow debugging
18:54:54: INFO:
18:54:54: INFO: Trying to store ‘rawprogram0.xml’ in string table
18:54:54: INFO: Looking for file ‘rawprogram0.xml’
18:54:54: INFO: User wants to talk to port ‘\.COM33’
18:54:54: INFO: Took 0.00000000 seconds to open port
18:54:54: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
18:54:54: INFO: If you don’t want this, use —dontsorttags
18:54:54: INFO: Looking for file ‘gpt_main0.bin’
18:54:54: INFO: Looking for file ‘sbl1.mbn’
18:54:54: INFO: Looking for file ‘DDR’
18:54:54: INFO: Looking for file ‘rpm.mbn’
18:54:54: INFO: Looking for file ‘tz.mbn’
18:54:54: INFO: Looking for file ’emmc_appsboot.mbn’
18:54:54: INFO: Looking for file ‘oeminfo.bin’
18:54:54: INFO: Looking for file ‘NON-HLOS.bin’
18:54:54: INFO: Looking for file ‘bkbootup.img’
18:54:54: INFO: Looking for file ‘persist.img’
18:54:54: INFO: Looking for file ‘boot.img’
18:54:54: INFO: Looking for file ‘recovery.img’
18:54:54: INFO: Looking for file ‘cust’
18:54:54: INFO: Looking for file ‘cache.img’
18:54:54: INFO: Looking for file ‘system.img’
18:54:54: INFO: Looking for file ‘userdata.img’
18:54:54: INFO:
Total to be tansferd with <program> or <read> is 2.70 GB
18:54:54: INFO: Sending <configure>
18:54:54: INFO: TARGET SAID: ‘Host’s payload to target size is too large’
18:54:54: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
18:54:54: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 49152
18:54:54: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
18:54:54: INFO: In handleProgram(‘gpt_main0.bin’)
18:54:54: INFO: Looking for file ‘gpt_main0.bin’
18:54:54: INFO: =======================================================
18:54:54: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbingpt_main0.bin’}
18:54:54: INFO: {<program> (17.00 KB) 34 sectors needed at location 0 on LUN 0}
18:54:54: INFO: =======================================================
18:54:54: INFO: TARGET SAID: ‘logbuf@0xF8021118 fh@0xF801DF80’
18:54:54: INFO: TARGET SAID: ‘start 0, num 34’
18:54:54: INFO: FILE ACCESS SLOW!! 17.00 KB in 0.015 seconds ( 1.11 MBps) — Overall to target 0.010 seconds (1.66 MBps)
18:54:54: INFO: {percent files transferred 0.00%}
18:54:54: INFO: TARGET SAID: ‘Finished sector address 34’
18:54:54: INFO:
18:54:54: INFO: =======================================================
18:54:54: INFO: ==================== {SUCCESS} ========================
18:54:54: INFO: =======================================================
18:54:54: INFO: {percent files transferred 0.00%}
18:54:54: INFO: In handleProgram(‘sbl1.mbn’)
18:54:54: INFO: Looking for file ‘sbl1.mbn’
18:54:54: INFO: =======================================================
18:54:54: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbinsbl1.mbn’}
18:54:54: INFO: {<program> (512.00 KB) 1024 sectors needed at location 34 on LUN 0}
18:54:54: INFO: =======================================================
18:54:54: INFO: TARGET SAID: ‘start 34, num 1024’
18:54:54: INFO: FILE ACCESS SLOW!! 512.00 KB in 0.015 seconds ( 33.33 MBps) — Overall to target 0.109 seconds (4.59 MBps)
18:54:54: INFO: {percent files transferred 0.02%}
18:54:54: INFO: TARGET SAID: ‘Finished sector address 1058’
18:54:54: INFO:
18:54:54: INFO: =======================================================
18:54:54: INFO: ==================== {SUCCESS} ========================
18:54:54: INFO: =======================================================
18:54:54: INFO: {percent files transferred 0.02%}
18:54:54: INFO: In handleProgram(‘DDR’)
18:54:54: INFO: Looking for file ‘DDR’
18:54:54: INFO: =======================================================
18:54:54: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbinDDR’}
18:54:54: INFO: {<program> (32.00 KB) 64 sectors needed at location 8192 on LUN 0}
18:54:54: INFO: =======================================================
18:54:54: INFO: TARGET SAID: ‘start 8192, num 64’
18:54:54: INFO: FILE ACCESS SLOW!! 32.00 KB in 0.015 seconds ( 2.08 MBps) — Overall to target 0.015 seconds (2.08 MBps)
18:54:54: INFO: {percent files transferred 0.02%}
18:54:54: INFO: TARGET SAID: ‘Finished sector address 8256’
18:54:54: INFO:
18:54:54: INFO: =======================================================
18:54:54: INFO: ==================== {SUCCESS} ========================
18:54:54: INFO: =======================================================
18:54:54: INFO: {percent files transferred 0.02%}
18:54:54: INFO: In handleProgram(‘rpm.mbn’)
18:54:54: INFO: Looking for file ‘rpm.mbn’
18:54:54: INFO: =======================================================
18:54:54: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbinrpm.mbn’}
18:54:54: INFO: {<program> (500.00 KB) 1000 sectors needed at location 16384 on LUN 0}
18:54:54: INFO: =======================================================
18:54:54: INFO: TARGET SAID: ‘start 16384, num 1000’
18:54:55: INFO: FILE ACCESS SLOW!! 500.00 KB in 0.015 seconds ( 32.55 MBps) — Overall to target 0.094 seconds (5.19 MBps)
18:54:55: INFO: {percent files transferred 0.04%}
18:54:55: INFO: TARGET SAID: ‘Finished sector address 17384’
18:54:55: INFO:
18:54:55: INFO: =======================================================
18:54:55: INFO: ==================== {SUCCESS} ========================
18:54:55: INFO: =======================================================
18:54:55: INFO: {percent files transferred 0.04%}
18:54:55: INFO: In handleProgram(‘tz.mbn’)
18:54:55: INFO: Looking for file ‘tz.mbn’
18:54:55: INFO: =======================================================
18:54:55: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbintz.mbn’}
18:54:55: INFO: {<program> (500.00 KB) 1000 sectors needed at location 17384 on LUN 0}
18:54:55: INFO: =======================================================
18:54:55: INFO: TARGET SAID: ‘start 17384, num 1000’
18:54:55: INFO: FILE ACCESS SLOW!! 500.00 KB in 0.015 seconds ( 32.55 MBps) — Overall to target 0.109 seconds (4.48 MBps)
18:54:55: INFO: {percent files transferred 0.06%}
18:54:55: INFO: TARGET SAID: ‘Finished sector address 18384’
18:54:55: INFO:
18:54:55: INFO: =======================================================
18:54:55: INFO: ==================== {SUCCESS} ========================
18:54:55: INFO: =======================================================
18:54:55: INFO: {percent files transferred 0.06%}
18:54:55: INFO: In handleProgram(’emmc_appsboot.mbn’)
18:54:55: INFO: Looking for file ’emmc_appsboot.mbn’
18:54:55: INFO: =======================================================
18:54:55: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbinemmc_appsboot.mbn’}
18:54:55: INFO: {<program> (5.46 MB) 11184 sectors needed at location 18384 on LUN 0}
18:54:55: INFO: =======================================================
18:54:55: INFO: TARGET SAID: ‘start 18384, num 11184’
18:54:55: INFO: Overall to target 0.561 seconds (9.73 MBps)
18:54:55: INFO: {percent files transferred 0.25%}
18:54:55: INFO: TARGET SAID: ‘Finished sector address 29568’
18:54:55: INFO:
18:54:55: INFO: =======================================================
18:54:55: INFO: ==================== {SUCCESS} ========================
18:54:55: INFO: =======================================================
18:54:55: INFO: {percent files transferred 0.25%}
18:54:55: INFO: In handleProgram(‘oeminfo.bin’)
18:54:55: INFO: Looking for file ‘oeminfo.bin’
18:54:55: INFO: =======================================================
18:54:55: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbinoeminfo.bin’}
18:54:55: INFO: {<program> (64.00 MB) 131072 sectors needed at location 31616 on LUN 0}
18:54:55: INFO: =======================================================
18:54:55: INFO: TARGET SAID: ‘start 31616, num 131072’
18:54:57: INFO: Overall to target 2.013 seconds (13.51 MBps)
18:54:57: INFO: {percent files transferred 1.24%}
18:54:59: INFO: Overall to target 4.041 seconds (11.79 MBps)
18:54:59: INFO: {percent files transferred 1.98%}
18:55:01: INFO: Overall to target 6.100 seconds (8.01 MBps)
18:55:01: INFO: {percent files transferred 2.02%}
18:55:04: INFO: Overall to target 8.175 seconds (6.13 MBps)
18:55:04: INFO: {percent files transferred 2.07%}
18:55:05: INFO: Overall to target 9.688 seconds (6.61 MBps)
18:55:05: INFO: {percent files transferred 2.57%}
18:55:05: INFO: TARGET SAID: ‘Finished sector address 162688’
18:55:05: INFO:
18:55:05: INFO: =======================================================
18:55:05: INFO: ==================== {SUCCESS} ========================
18:55:05: INFO: =======================================================
18:55:05: INFO: {percent files transferred 2.57%}
18:55:05: INFO: In handleProgram(‘NON-HLOS.bin’)
18:55:05: INFO: Looking for file ‘NON-HLOS.bin’
18:55:05: INFO: =======================================================
18:55:05: INFO: {<program> FILE: ‘C:Program FilesQualcommQPSTbinNON-HLOS.bin’}
18:55:05: INFO: {<program> (96.00 MB) 196608 sectors needed at location 180224 on LUN 0}
18:55:05: INFO: =======================================================
18:55:05: INFO: TARGET SAID: ‘start 180224, num 196608’
18:55:07: INFO: Overall to target 2.012 seconds (4.03 MBps)
18:55:07: INFO: {percent files transferred 2.86%}
18:55:09: INFO: Overall to target 4.102 seconds (2.27 MBps)
18:55:09: INFO: {percent files transferred 2.91%}
18:55:11: INFO: Overall to target 6.146 seconds (1.72 MBps)
18:55:11: INFO: {percent files transferred 2.95%}
18:55:13: INFO: Overall to target 8.159 seconds (1.43 MBps)
18:55:13: INFO: {percent files transferred 2.99%}
18:55:15: INFO: Overall to target 10.265 seconds (1.21 MBps)
18:55:15: INFO: {percent files transferred 3.02%}
18:55:18: INFO: Overall to target 12.495 seconds (1.03 MBps)
18:55:18: INFO: {percent files transferred 3.03%}
18:55:20: INFO: Overall to target 14.726 seconds (915.93 KBps)
18:55:20: INFO: {percent files transferred 3.05%}
18:55:22: INFO: Overall to target 16.910 seconds (820.34 KBps)
18:55:22: INFO: {percent files transferred 3.06%}
18:55:24: INFO: Overall to target 18.923 seconds (750.83 KBps)
18:55:24: INFO: {percent files transferred 3.07%}
18:55:26: INFO: Overall to target 20.982 seconds (709.18 KBps)
18:55:26: INFO: {percent files transferred 3.10%}
18:55:28: INFO: Overall to target 23.041 seconds (706.22 KBps)
18:55:28: INFO: {percent files transferred 3.14%}
18:55:30: INFO: Overall to target 25.085 seconds (702.25 KBps)
18:55:30: INFO: {percent files transferred 3.19%}
18:55:32: INFO: Overall to target 27.128 seconds (695.37 KBps)
18:55:32: INFO: {percent files transferred 3.24%}
18:55:34: INFO: Overall to target 29.172 seconds (692.72 KBps)
18:55:34: INFO: {percent files transferred 3.28%}
18:55:36: INFO: Overall to target 31.231 seconds (685.47 KBps)
18:55:36: INFO: {percent files transferred 3.33%}
18:55:38: INFO: Overall to target 33.290 seconds (684.89 KBps)
18:55:38: INFO: {percent files transferred 3.38%}
18:55:40: INFO: Overall to target 35.318 seconds (679.54 KBps)
18:55:40: INFO: {percent files transferred 3.42%}
18:55:42: INFO: Overall to target 37.331 seconds (678.90 KBps)
18:55:42: INFO: {percent files transferred 3.46%}
18:55:45: INFO: Overall to target 39.406 seconds (678.47 KBps)
18:55:45: INFO: {percent files transferred 3.51%}
18:55:47: INFO: Overall to target 41.434 seconds (677.70 KBps)
18:55:47: INFO: {percent files transferred 3.56%}
18:55:49: INFO: Overall to target 43.462 seconds (677.00 KBps)
18:55:49: INFO: {percent files transferred 3.61%}
18:55:51: INFO: Overall to target 45.521 seconds (676.96 KBps)
18:55:51: INFO: {percent files transferred 3.66%}
18:55:53: INFO: Overall to target 47.580 seconds (676.92 KBps)
18:55:53: INFO: {percent files transferred 3.71%}
18:55:55: INFO: Overall to target 49.624 seconds (674.19 KBps)
18:55:55: INFO: {percent files transferred 3.75%}
18:56:09: INFO: Overall to target 64.038 seconds (532.93 KBps)
18:56:09: INFO: {percent files transferred 3.78%}
18:56:11: INFO: Overall to target 66.050 seconds (1.18 MBps)
18:56:11: INFO: {percent files transferred 5.38%}
18:56:12: INFO: Overall to target 66.877 seconds (1.44 MBps)
18:56:12: INFO: {percent files transferred 6.04%}
18:56:12: INFO: TARGET SAID: ‘Write failed Sector 248096, Errno 14’
18:56:12: INFO: TARGET SAID: ‘Finished sector address 248096’
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| ‘__| ‘__/ _ | ‘__|
| |__| | | | | (_) | |
____/_| |_| ___/|_|
18:56:12: {ERROR: Please see log}
Writing log to ‘C:UsersLenovoAppDataRoamingQualcommQFILCOMPORT_33port_trace.txt’, might take a minute
Log is ‘C:UsersLenovoAppDataRoamingQualcommQFILCOMPORT_33port_trace.txt’
Download Fail:FireHose Fail:FHLoader Fail:process fail
Finish Download

Mohd Saqib


  • #3

Try as in the post …

Process Index:0
Programmer Path:C:Program FilesQualcommQPSTbinY530-U00V100R001C900B519user_prog_emmc_firehose_8x10.mbn
Image Search Path:C:Program FilesQualcommQPSTbinY530-U00V100R001C900B519
Please select the XML file
Start Download
Program Path:C:Program FilesQualcommQPSTbinY530-U00V100R001C900B519user_prog_emmc_firehose_8x10.mbn
COM Port number:33
Sahara Connecting …
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8×26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:33
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.

at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()

at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download

  • #4

which version to use QFIL ?

Mohd Saqib


  • #5

which version to use QFIL ?

Use Latest Version
[h=2]QPST_2.7.460[/h]

  • #6

Get error :
Download Fail:Sahara Fail:QSaharaServer Fail:process fail…

  • #7

I got nothing from this,work huawei y625 passed whitout problems.I thought that someone can help with this… maybe it’s hw problem …

  • #8

huawei y530-u00 xml qfil firmware need……my phone after flash phone is dead,i m flashing this firmware Y530-U00 V100R001C900B519 but no succes pleas halp me.

Источник

гришан


  • #1

Предыстория телефона: поставили на автомобильную зарядку, он сдох. я заменил кп и контроллер заряда, он стал видится компом как HS-USB QDLoader 9008, решил попробовать прошить через QFIL

лог:

HTML: 

Process Index:0
Programmer Path:C:123VIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
Image Search Path:C:123VIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovo
Please select the XML file
Start Download
Program Path:C:123VIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:3
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.

в QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()

в QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
Start Download
Program Path:C:123VIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol

в QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)

в QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download

Собственно что предпринимал: менял дрова, версии прошивальщиков, прошивки, шнурки, компы с разными windows. на одном из компов на 10 windows он почти прошивается, но потом в самом конце вновь выпадает эта ошибка NOP: Fail Code: 10

GreyDog


  • #2

Так вы бы и приложили тот лог, где «почти прошивается».

купить чтобы получить доступ к скрытому контенту.

свежий QFIL. Попробуйте им. Что-то такое показывали, но не соображу..

гришан


  • #3

Так вы бы и приложили тот лог, где «почти прошивается».

купить чтобы получить доступ к скрытому контенту.

свежий QFIL. Попробуйте им. Что-то такое показывали, но не соображу..

попробовал зашить свежим QFIL , вот чего получилось (прошивка VIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovo )

Код: 

Start Download
Program Path:C:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
***** Working Folder:C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
Binary build date: Mar 26 2017 @ 22:09:19
QSAHARASERVER CALLED LIKE THIS: 'C:Program Files (x86)QualcommQPSTbinQSaharaServer.ex'Current working dir: C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
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:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
17:08:37: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
17:08:37: ERROR: function: sahara_main:924 Sahara protocol error
17:08:37: ERROR: function: main:303 Uploading  Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
Start Download
Program Path:C:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
***** Working Folder:C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
Binary build date: Mar 26 2017 @ 22:09:19
QSAHARASERVER CALLED LIKE THIS: 'C:Program Files (x86)QualcommQPSTbinQSaharaServer.ex'Current working dir: C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
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:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn
17:09:07: Requested ID 13, file: "C:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovoprog_emmc_firehose_8936.mbn"
17:09:07: 95292 bytes transferred in 0.062000 seconds (1.4658MBps)
17:09:07: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
17:09:07: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Serial Number:97873860
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
***** Working Folder:C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
Base Version: 17.03.10.18.52
Binary build date: Mar 26 2017 @ 22:09:16
Incremental Build version: 17.03.26.22.09.16
17:09:11: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:Program Files (x86)QualcommQPSTbinfh_loader.exe --port=\.COM17 --sendxml=rawprogram_unsparse.xml --search_path=C:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_Lenovo --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc 
************************************************
17:09:11: INFO: Current working dir (cwd): C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
17:09:11: INFO: Showing network mappings to allow debugging
17:09:11: INFO: 
17:09:11: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
17:09:11: INFO: Looking for file 'rawprogram_unsparse.xml'
17:09:11: INFO: User wants to talk to port '\.COM17'
17:09:11: INFO: Took       0.00000000 seconds to open port
17:09:11: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
17:09:11: INFO: If  you don't want this, use --dontsorttags
17:09:11: INFO: Looking for file 'NON-HLOS.bin'
17:09:11: INFO: Looking for file 'sbl1.mbn'
17:09:11: INFO: Looking for file 'sbl1.mbn'
17:09:11: INFO: Looking for file 'rpm.mbn'
17:09:11: INFO: Looking for file 'rpm.mbn'
17:09:11: INFO: Looking for file 'tz.mbn'
17:09:11: INFO: Looking for file 'tz.mbn'
17:09:11: INFO: Looking for file 'hyp.mbn'
17:09:11: INFO: Looking for file 'hyp.mbn'
17:09:11: INFO: Looking for file 'sec.dat'
17:09:11: INFO: Looking for file 'emmc_appsboot.mbn'
17:09:11: INFO: Looking for file 'emmc_appsboot.mbn'
17:09:11: INFO: Looking for file 'splash.img'
17:09:11: INFO: Looking for file 'boot.img'
17:09:11: INFO: Looking for file 'recovery.img'
17:09:11: INFO: Looking for file 'system_1.img'
17:09:11: INFO: Looking for file 'system_2.img'
17:09:11: INFO: Looking for file 'system_3.img'
17:09:11: INFO: Looking for file 'system_4.img'
17:09:11: INFO: Looking for file 'system_5.img'
17:09:11: INFO: Looking for file 'system_6.img'
17:09:11: INFO: Looking for file 'system_7.img'
17:09:11: INFO: Looking for file 'system_8.img'
17:09:11: INFO: Looking for file 'system_9.img'
17:09:11: INFO: Looking for file 'system_10.img'
17:09:11: INFO: Looking for file 'system_11.img'
17:09:11: INFO: Looking for file 'system_12.img'
17:09:11: INFO: Looking for file 'system_13.img'
17:09:11: INFO: Looking for file 'system_14.img'
17:09:11: INFO: Looking for file 'system_15.img'
17:09:11: INFO: Looking for file 'system_16.img'
17:09:11: INFO: Looking for file 'system_17.img'
17:09:11: INFO: Looking for file 'system_18.img'
17:09:11: INFO: Looking for file 'system_19.img'
17:09:11: INFO: Looking for file 'system_20.img'
17:09:11: INFO: Looking for file 'cache_1.img'
17:09:11: INFO: Looking for file 'cache_2.img'
17:09:11: INFO: Looking for file 'cache_3.img'
17:09:11: INFO: Looking for file 'cache_4.img'
17:09:11: INFO: Looking for file 'userdata_1.img'
17:09:11: INFO: Looking for file 'userdata_2.img'
17:09:11: INFO: Looking for file 'userdata_3.img'
17:09:11: INFO: Looking for file 'userdata_4.img'
17:09:11: INFO: Looking for file 'userdata_5.img'
17:09:11: INFO: Looking for file 'userdata_6.img'
17:09:11: INFO: Looking for file 'userdata_7.img'
17:09:11: INFO: Looking for file 'userdata_8.img'
17:09:11: INFO: Looking for file 'userdata_9.img'
17:09:11: INFO: Looking for file 'userdata_10.img'
17:09:11: INFO: Looking for file 'userdata_11.img'
17:09:11: INFO: Looking for file 'userdata_12.img'
17:09:11: INFO: Looking for file 'userdata_13.img'
17:09:11: INFO: Looking for file 'userdata_14.img'
17:09:11: INFO: Looking for file 'userdata_15.img'
17:09:11: INFO: Looking for file 'userdata_16.img'
17:09:11: INFO: Looking for file 'userdata_17.img'
17:09:11: INFO: Looking for file 'userdata_18.img'
17:09:11: INFO: Looking for file 'userdata_19.img'
17:09:11: INFO: Looking for file 'userdata_20.img'
17:09:11: INFO: Looking for file 'userdata_21.img'
17:09:11: INFO: Looking for file 'userdata_22.img'
17:09:11: INFO: Looking for file 'userdata_23.img'
17:09:11: INFO: Looking for file 'userdata_24.img'
17:09:11: INFO: Looking for file 'userdata_25.img'
17:09:11: INFO: Looking for file 'userdata_26.img'
17:09:11: INFO: Looking for file 'userdata_27.img'
17:09:11: INFO: Looking for file 'userdata_28.img'
17:09:11: INFO: Looking for file 'userdata_29.img'
17:09:11: INFO: Looking for file 'userdata_30.img'
17:09:11: INFO: Looking for file 'userdata_31.img'
17:09:11: INFO: Looking for file 'userdata_32.img'
17:09:11: INFO: Looking for file 'userdata_33.img'
17:09:11: INFO: Looking for file 'userdata_34.img'
17:09:11: INFO: Looking for file 'userdata_35.img'
17:09:11: INFO: Looking for file 'userdata_36.img'
17:09:11: INFO: Looking for file 'userdata_37.img'
17:09:11: INFO: Looking for file 'userdata_38.img'
17:09:11: INFO: Looking for file 'userdata_39.img'
17:09:11: INFO: Looking for file 'userdata_40.img'
17:09:11: INFO: Looking for file 'userdata_41.img'
17:09:11: INFO: Looking for file 'userdata_42.img'
17:09:11: INFO: Looking for file 'userdata_43.img'
17:09:11: INFO: Looking for file 'userdata_44.img'
17:09:11: INFO: Looking for file 'userdata_45.img'
17:09:11: INFO: Looking for file 'userdata_46.img'
17:09:11: INFO: Looking for file 'userdata_47.img'
17:09:11: INFO: Looking for file 'userdata_48.img'
17:09:11: INFO: Looking for file 'userdata_49.img'
17:09:11: INFO: Looking for file 'userdata_50.img'
17:09:11: INFO: Looking for file 'userdata_51.img'
17:09:11: INFO: Looking for file 'userdata_52.img'
17:09:11: INFO: Looking for file 'userdata_53.img'
17:09:11: INFO: Looking for file 'userdata_54.img'
17:09:11: INFO: Looking for file 'userdata_55.img'
17:09:11: INFO: Looking for file 'userdata_56.img'
17:09:11: INFO: Looking for file 'userdata_57.img'
17:09:11: INFO: Looking for file 'userdata_58.img'
17:09:11: INFO: Looking for file 'userdata_59.img'
17:09:11: INFO: Looking for file 'userdata_60.img'
17:09:11: INFO: Looking for file 'userdata_61.img'
17:09:11: INFO: Looking for file 'userdata_62.img'
17:09:11: INFO: Looking for file 'userdata_63.img'
17:09:11: INFO: Looking for file 'userdata_64.img'
17:09:11: INFO: Looking for file 'userdata_65.img'
17:09:11: INFO: Looking for file 'userdata_66.img'
17:09:11: INFO: Looking for file 'userdata_67.img'
17:09:11: INFO: Looking for file 'userdata_68.img'
17:09:11: INFO: Looking for file 'userdata_69.img'
17:09:11: INFO: Looking for file 'userdata_70.img'
17:09:11: INFO: Looking for file 'userdata_71.img'
17:09:11: INFO: Looking for file 'userdata_72.img'
17:09:11: INFO: Looking for file 'userdata_73.img'
17:09:11: INFO: Looking for file 'userdata_74.img'
17:09:11: INFO: Looking for file 'userdata_75.img'
17:09:11: INFO: Looking for file 'userdata_76.img'
17:09:11: INFO: Looking for file 'userdata_77.img'
17:09:11: INFO: Looking for file 'userdata_78.img'
17:09:11: INFO: Looking for file 'userdata_79.img'
17:09:11: INFO: Looking for file 'userdata_80.img'
17:09:11: INFO: Looking for file 'userdata_81.img'
17:09:11: INFO: Looking for file 'userdata_82.img'
17:09:11: INFO: Looking for file 'userdata_83.img'
17:09:11: INFO: Looking for file 'userdata_84.img'
17:09:11: INFO: Looking for file 'userdata_85.img'
17:09:11: INFO: Looking for file 'userdata_86.img'
17:09:11: INFO: Looking for file 'userdata_87.img'
17:09:11: INFO: Looking for file 'userdata_88.img'
17:09:11: INFO: Looking for file 'gpt_main0.bin'
17:09:11: INFO: Looking for file 'gpt_backup0.bin'
17:09:11: INFO: 
Total to be tansferd with <program> or <read> is 2.74 GB
17:09:11: INFO: Sending <configure>
17:09:11: INFO: TARGET SAID: 'Host's payload to target size is too large'
17:09:11: INFO: TARGET SAID: 'logbuf@0x0801DC08 fh@0x0801AA70'
17:09:11: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 16384
17:09:11: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 16384
17:09:11: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
17:09:11: INFO: In handleProgram('NON-HLOS.bin')
17:09:11: INFO: Looking for file 'NON-HLOS.bin'
17:09:11: INFO: =======================================================
17:09:12: INFO: {<program> FILE: 'C:rrrVIBEUI_V3.1_1627_5.419.1_ST_P1c72_LenovoNON-HLOS.bin'}
17:09:12: INFO: {<program> (64.00 MB) 131072 sectors needed at location 131072 on LUN 0}
17:09:12: INFO: =======================================================
17:09:12: INFO: TARGET SAID: 'logbuf@0x0801DC08 fh@0x0801AA70'
17:09:12: INFO: TARGET SAID: 'start 131072, num 131072'
17:09:14: INFO: Overall to target  2.012 seconds (11.87 MBps)
17:09:14: INFO: {percent files transferred   0.85%}
17:09:16: INFO: Overall to target  4.025 seconds (11.85 MBps)
17:09:16: INFO: {percent files transferred   1.70%}
17:09:17: INFO: Overall to target  5.351 seconds (11.96 MBps)
17:09:17: INFO: {percent files transferred   2.28%}
17:09:17: INFO: TARGET SAID: 'Write failed Sector 131072, Errno 14'
17:09:17: INFO: TARGET SAID: 'Finished sector address 131072'
	 _____                    
	|  ___|                   
	| |__ _ __ _ __ ___  _ __ 
	|  __| '__| '__/ _ | '__|
	| |__| |  | | | (_) | |   
	____/_|  |_|  ___/|_|  
17:09:17: {ERROR: Please see log}
Writing log to 'C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17port_trace.txt', might take a minute
Log is 'C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17port_trace.txt'
Download Fail:FireHose Fail:FHLoader Fail:Process fail
Finish Download

гришан


  • #4

так же попробовал зашить прошивкой P1a42_S288_160721_ROW_RAW_QFIL
получилось примерно тоже самое:

Код: 

Start Download
Program Path:C:rrr161022-联想P1c72_VIBEUI_V3.1_1627_6.0-电商prog_emmc_firehose_8936.mbn
***** Working Folder:C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
Binary build date: Mar 26 2017 @ 22:09:19
QSAHARASERVER CALLED LIKE THIS: 'C:Program Files (x86)QualcommQPSTbinQSaharaServer.ex'Current working dir: C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
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:rrr161022-??P1c72_VIBEUI_V3.1_1627_6.0-??prog_emmc_firehose_8936.mbn
17:11:25: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
17:11:25: ERROR: function: sahara_main:924 Sahara protocol error
17:11:25: ERROR: function: main:303 Uploading  Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
Programmer Path:C:rrrP1a42_S288_160721_ROW_RAW_QFILprog_emmc_firehose_8936.mbn
Image Search Path: C:rrrP1a42_S288_160721_ROW_RAW_QFIL
Invalid RAWPROGRAM file path ignored: C:rrrP1a42_S288_160721_ROW_RAW_QFILrawprogram_unsparse.xml Ignored
PATCH file path ignored: C:rrrP1a42_S288_160721_ROW_RAW_QFILpatch0.xml
PATCH file path:C:rrrP1a42_S288_160721_ROW_RAW_QFILpatch0.xml
Image Search Path: C:rrrP1a42_S288_160721_ROW_RAW_QFIL
RAWPROGRAM file path: C:rrrP1a42_S288_160721_ROW_RAW_QFILrawprogram0.xml
PATCH file path:C:rrrP1a42_S288_160721_ROW_RAW_QFILpatch0.xml
Start Download
Program Path:C:rrrP1a42_S288_160721_ROW_RAW_QFILprog_emmc_firehose_8936.mbn
***** Working Folder:C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
Binary build date: Mar 26 2017 @ 22:09:19
QSAHARASERVER CALLED LIKE THIS: 'C:Program Files (x86)QualcommQPSTbinQSaharaServer.ex'Current working dir: C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
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:rrrP1a42_S288_160721_ROW_RAW_QFILprog_emmc_firehose_8936.mbn
17:13:19: Requested ID 13, file: "C:rrrP1a42_S288_160721_ROW_RAW_QFILprog_emmc_firehose_8936.mbn"
17:13:19: 95292 bytes transferred in 0.093000 seconds (0.9772MBps)
17:13:19: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
17:13:19: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Serial Number:97873860
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
***** Working Folder:C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
Base Version: 17.03.10.18.52
Binary build date: Mar 26 2017 @ 22:09:16
Incremental Build version: 17.03.26.22.09.16
17:13:23: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:Program Files (x86)QualcommQPSTbinfh_loader.exe --port=\.COM17 --sendxml=rawprogram0.xml --search_path=C:rrrP1a42_S288_160721_ROW_RAW_QFIL --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc 
************************************************
17:13:23: INFO: Current working dir (cwd): C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17
17:13:23: INFO: Showing network mappings to allow debugging
17:13:23: INFO: 
17:13:23: INFO: Trying to store 'rawprogram0.xml' in string table
17:13:23: INFO: Looking for file 'rawprogram0.xml'
17:13:23: INFO: User wants to talk to port '\.COM17'
17:13:23: INFO: Took       0.00000000 seconds to open port
17:13:23: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
17:13:23: INFO: If  you don't want this, use --dontsorttags
17:13:23: INFO: Looking for file 'NON-HLOS.bin'
17:13:23: INFO: Looking for file 'sbl1.mbn'
17:13:23: INFO: Looking for file 'sbl1.mbn'
17:13:23: INFO: Looking for file 'rpm.mbn'
17:13:23: INFO: Looking for file 'rpm.mbn'
17:13:23: INFO: Looking for file 'tz.mbn'
17:13:23: INFO: Looking for file 'tz.mbn'
17:13:23: INFO: Looking for file 'hyp.mbn'
17:13:23: INFO: Looking for file 'hyp.mbn'
17:13:23: INFO: Looking for file 'emmc_appsboot.mbn'
17:13:23: INFO: Looking for file 'emmc_appsboot.mbn'
17:13:23: INFO: Looking for file 'boot.img'
17:13:23: INFO: Looking for file 'recovery.img'
17:13:23: INFO: Looking for file 'system.img'
17:13:23: INFO: Looking for file 'cache.img'
17:13:23: INFO: Looking for file 'preload.img'
17:13:23: INFO: Looking for file 'userdata_1.img'
17:13:23: INFO: Looking for file 'userdata_2.img'
17:13:23: INFO: Looking for file 'userdata_3.img'
17:13:23: INFO: Looking for file 'userdata_4.img'
17:13:23: INFO: Looking for file 'userdata_5.img'
17:13:23: INFO: Looking for file 'userdata_6.img'
17:13:23: INFO: Looking for file 'userdata_7.img'
17:13:23: INFO: Looking for file 'userdata_8.img'
17:13:23: INFO: Looking for file 'userdata_9.img'
17:13:23: INFO: Looking for file 'userdata_10.img'
17:13:23: INFO: Looking for file 'userdata_11.img'
17:13:23: INFO: Looking for file 'userdata_12.img'
17:13:23: INFO: Looking for file 'userdata_13.img'
17:13:23: INFO: Looking for file 'userdata_14.img'
17:13:23: INFO: Looking for file 'userdata_15.img'
17:13:23: INFO: Looking for file 'userdata_16.img'
17:13:23: INFO: Looking for file 'userdata_17.img'
17:13:23: INFO: Looking for file 'userdata_18.img'
17:13:23: INFO: Looking for file 'userdata_19.img'
17:13:23: INFO: Looking for file 'userdata_20.img'
17:13:23: INFO: Looking for file 'userdata_21.img'
17:13:23: INFO: Looking for file 'userdata_22.img'
17:13:23: INFO: Looking for file 'userdata_23.img'
17:13:23: INFO: Looking for file 'userdata_24.img'
17:13:23: INFO: Looking for file 'userdata_25.img'
17:13:23: INFO: Looking for file 'userdata_26.img'
17:13:23: INFO: Looking for file 'userdata_27.img'
17:13:23: INFO: Looking for file 'userdata_28.img'
17:13:23: INFO: Looking for file 'userdata_29.img'
17:13:23: INFO: Looking for file 'userdata_30.img'
17:13:23: INFO: Looking for file 'userdata_31.img'
17:13:23: INFO: Looking for file 'userdata_32.img'
17:13:23: INFO: Looking for file 'userdata_33.img'
17:13:23: INFO: Looking for file 'userdata_34.img'
17:13:23: INFO: Looking for file 'userdata_35.img'
17:13:23: INFO: Looking for file 'userdata_36.img'
17:13:23: INFO: Looking for file 'userdata_37.img'
17:13:23: INFO: Looking for file 'userdata_38.img'
17:13:23: INFO: Looking for file 'userdata_39.img'
17:13:23: INFO: Looking for file 'userdata_40.img'
17:13:23: INFO: Looking for file 'userdata_41.img'
17:13:23: INFO: Looking for file 'userdata_42.img'
17:13:23: INFO: Looking for file 'userdata_43.img'
17:13:23: INFO: Looking for file 'userdata_44.img'
17:13:23: INFO: Looking for file 'userdata_45.img'
17:13:23: INFO: Looking for file 'userdata_46.img'
17:13:23: INFO: Looking for file 'userdata_47.img'
17:13:23: INFO: Looking for file 'userdata_48.img'
17:13:23: INFO: Looking for file 'userdata_49.img'
17:13:23: INFO: Looking for file 'userdata_50.img'
17:13:23: INFO: Looking for file 'userdata_51.img'
17:13:23: INFO: Looking for file 'userdata_52.img'
17:13:23: INFO: Looking for file 'userdata_53.img'
17:13:23: INFO: Looking for file 'userdata_54.img'
17:13:23: INFO: Looking for file 'userdata_55.img'
17:13:23: INFO: Looking for file 'userdata_56.img'
17:13:23: INFO: Looking for file 'userdata_57.img'
17:13:23: INFO: Looking for file 'userdata_58.img'
17:13:23: INFO: Looking for file 'userdata_59.img'
17:13:23: INFO: Looking for file 'userdata_60.img'
17:13:23: INFO: Looking for file 'userdata_61.img'
17:13:23: INFO: Looking for file 'userdata_62.img'
17:13:23: INFO: Looking for file 'userdata_63.img'
17:13:23: INFO: Looking for file 'userdata_64.img'
17:13:23: INFO: Looking for file 'userdata_65.img'
17:13:23: INFO: Looking for file 'userdata_66.img'
17:13:23: INFO: Looking for file 'userdata_67.img'
17:13:23: INFO: Looking for file 'userdata_68.img'
17:13:23: INFO: Looking for file 'userdata_69.img'
17:13:23: INFO: Looking for file 'userdata_70.img'
17:13:23: INFO: Looking for file 'userdata_71.img'
17:13:23: INFO: Looking for file 'userdata_72.img'
17:13:23: INFO: Looking for file 'userdata_73.img'
17:13:23: INFO: Looking for file 'userdata_74.img'
17:13:23: INFO: Looking for file 'userdata_75.img'
17:13:23: INFO: Looking for file 'userdata_76.img'
17:13:23: INFO: Looking for file 'userdata_77.img'
17:13:23: INFO: Looking for file 'userdata_78.img'
17:13:23: INFO: Looking for file 'userdata_79.img'
17:13:23: INFO: Looking for file 'userdata_80.img'
17:13:23: INFO: Looking for file 'userdata_81.img'
17:13:23: INFO: Looking for file 'userdata_82.img'
17:13:23: INFO: Looking for file 'userdata_83.img'
17:13:23: INFO: Looking for file 'userdata_84.img'
17:13:23: INFO: Looking for file 'userdata_85.img'
17:13:23: INFO: Looking for file 'userdata_86.img'
17:13:23: INFO: Looking for file 'userdata_87.img'
17:13:23: INFO: Looking for file 'userdata_88.img'
17:13:23: INFO: Looking for file 'gpt_main0.bin'
17:13:23: INFO: Looking for file 'gpt_backup0.bin'
17:13:23: INFO: 
Total to be tansferd with <program> or <read> is 3.77 GB
17:13:23: INFO: Sending <configure>
17:13:23: INFO: TARGET SAID: 'Host's payload to target size is too large'
17:13:23: INFO: TARGET SAID: 'logbuf@0x0801DC08 fh@0x0801AA70'
17:13:23: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 16384
17:13:23: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 16384
17:13:23: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
17:13:23: INFO: In handleProgram('NON-HLOS.bin')
17:13:23: INFO: Looking for file 'NON-HLOS.bin'
17:13:23: INFO: =======================================================
17:13:23: INFO: {<program> FILE: 'C:rrrP1a42_S288_160721_ROW_RAW_QFILNON-HLOS.bin'}
17:13:23: INFO: {<program> (64.00 MB) 131072 sectors needed at location 131072 on LUN 0}
17:13:23: INFO: =======================================================
17:13:23: INFO: TARGET SAID: 'logbuf@0x0801DC08 fh@0x0801AA70'
17:13:23: INFO: TARGET SAID: 'start 131072, num 131072'
17:13:25: INFO: Overall to target  2.013 seconds (11.78 MBps)
17:13:25: INFO: {percent files transferred   0.61%}
17:13:27: INFO: Overall to target  4.025 seconds (12.17 MBps)
17:13:27: INFO: {percent files transferred   1.27%}
17:13:28: INFO: Overall to target  5.226 seconds (12.25 MBps)
17:13:28: INFO: {percent files transferred   1.66%}
17:13:28: INFO: TARGET SAID: 'Write failed Sector 131072, Errno 14'
17:13:28: INFO: TARGET SAID: 'Finished sector address 131072'
	 _____                    
	|  ___|                   
	| |__ _ __ _ __ ___  _ __ 
	|  __| '__| '__/ _ | '__|
	| |__| |  | | | (_) | |   
	____/_|  |_|  ___/|_|  
17:13:28: {ERROR: Please see log}
Writing log to 'C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17port_trace.txt', might take a minute
Log is 'C:UsersgrishaAppDataRoamingQualcommQFILCOMPORT_17port_trace.txt'
Download Fail:FireHose Fail:FHLoader Fail:Process fail
Finish Download

гришан


  • #5

как доберусь до компа на котором «почти прошился» зашью новой версией QFIL и скину лог

GreyDog


  • #6

Попробуйте родную китайку поставить. Например эту P1c72_USR_ST1613_5.221.1_1603221223_Q202531.2_CN. Очень похоже что вы самопалки пытаетесь поставить и потому QFIL ругается. В аттаче лог загрузки оригинальной китайки (только что сделал).
Или что-то с флешкой. Есть еще один вариант для проверки, оставим на завтра.

  • 8,4 КБ
    Просмотры: 34

гришан


  • #7

прошил на другом компе, но там похоже все тоже самое, просто загрузочная полоска доходила до конца)). прошил на нем старым и новым QPST, вот логи:

  • 39,9 КБ
    Просмотры: 15

  • 12,1 КБ
    Просмотры: 6

гришан


  • #8

Попробуйте родную китайку поставить. Например эту P1c72_USR_ST1613_5.221.1_1603221223_Q202531.2_CN.

прошивка есть только здесь:

купить чтобы получить доступ к скрытому контенту.

но никак не могу зарегаться в этой китайской системе, не приходит код проверки в смс, если у Вас есть эта прошивка и возможность куда-нибудь залить её, буду очень признателен!

GreyDog


  • #9

Закинул

купить чтобы получить доступ к скрытому контенту.

(временно).
У вас затык в одном и том же месте, при загрузке модема (non-hlos). Или из-за его размера (а там 100% неродной модем, а бекап. родной модем <64MB) или что-то с флешкой.

гришан


  • #10

Закинул

купить чтобы получить доступ к скрытому контенту.

(временно).
У вас затык в одном и том же месте, при загрузке модема (non-hlos). Или из-за его размера (а там 100% неродной модем, а бекап. родной модем <64MB) или что-то с флешкой.

спасибо, но к сожалению все тоже самое

  • 11,9 КБ
    Просмотры: 7

GreyDog


  • #11

Надо флешку смотреть. Продолжим в ЛС.

гришан


  • #12

если кому интересно чем все закончилось, восстановить не удалось, предположительно проблема в дохлом nand.

Источник
Автор
Сообщение

[ТС]

 Заголовок сообщения: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 27 фев 2020, 17:32 
Интересующийся
Интересующийся
Аватара пользователя


Зарегистрирован: 04 май 2017, 12:11
Наличности на руках:
159.77

Сообщения: 100
Откуда: Харьков

Приветствую!
Redmi 3s при включении появляется логотип Mi и сразу выключается.
Более подробно:
Redmi 3s глобальная версия, прошивка в последнее время не обновлялась, состояние нормальное, один хозяин, перед отказом иногда выскакивала ошибка, чего-то про «компонент безопасности ядра».
Потом просто выключился. При длительном удержании кнопки — включается, на экране появляется логотип Mi и сразу выключается. В fastboot переводится.
В recovery (громкость «+» и вкл) не входит. При подключении к компу через USB — определяется, индикатор заряда не горит, процесс заряда на экране не отображается.
При подключении на зарядку — индикатор заряда не горит, процесс заряда на экране не отображается.
На батарее 3,85в, батарею отключал от платы и подключал, не помогло.
Насколько могу судить из информации в инете, этот смартфон может включаться от зарядки, при отключенной батареи.
При отсоединенной батареи и подключенной к USB зарядке — ведет себя так же : логотип и выключается.
Прошу помочь советом в поиске неисправности (посылание в СЦ и к мусорному ведру в качестве совета не катит :-) )

P.S. При подключении к компу через USB — определяется как «Qualcomm HS-USB Diagnostics 900E»
От 1А-зарядки потребляет ток 550мА

Последний раз редактировалось roman555 27 фев 2020, 22:38, всего редактировалось 3 раз(а).

Не в сети

Профиль    

 

LanDLorD

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 27 фев 2020, 19:45 


Зарегистрирован: 10 фев 2020, 15:22
Наличности на руках:
60.00

Сообщения: 46
Откуда: Волгодонск

В моем случае было да варианта, в первом прошился аппарат и заработал, во втором решилось только заменой памяти, так как это одна из распространённых неисправностей

Не в сети

Профиль    

 

roman555
[ТС]

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 29 фев 2020, 00:38 


Зарегистрирован: 04 май 2017, 12:11
Наличности на руках:
159.77

Сообщения: 100
Откуда: Харьков

Поскольку загрузчик заблокирован, решил прошить через EDL. Софтово в EDL не перевелся, только через тест-поинт.
Прошивка global miui 9 заливалась с помощью miflash beta долго, примерно 20 минут, с полной очисткой, успешно (success).
Но смарт не перегрузился. Теперь не реагирует на кнопку включения вообще, при подключении к компу — сразу 9008.
Попробовал прошить другую версию, во второй раз на прошивку ушло 4 минуты, опять успех, ну и по прежнему не включается.
:-(
Всё, флеш неисправна?

P.S. Про 9008 погорячился. Глюк какой-то с 9008 : после перезагрузки компа, определяется как USB девайс с ошибкой. В 9008 по прежнему нужно входить через тест-поинт. Попробую прошить другой версией.

Не в сети

Профиль    

 

roman555
[ТС]

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 29 фев 2020, 14:38 


Зарегистрирован: 04 май 2017, 12:11
Наличности на руках:
159.77

Сообщения: 100
Откуда: Харьков

Все таки смарт постоянно в состоянии порт 9008, похоже sbl не читается.
Попробовал прошить через QFIL, начинает шить и выдает ошибку записи в сектор.
Пробовал редактировать rawprogram0.xml, убирал строки последовательно: NON-HLOS.bin, sbl1 — ошибка записи возникает в других местах, так что sblbak тоже не прошился.
Лог в окне программы:

Лог port_trace

Miflash, разные версии, шьет без ошибок, но толку — никакого, удивительная программа 🙂
Для примера лог Мифлеш (rawprogram0.xml без NON-HLOS.bin, — эта часть начинает шиться первой, тоже с таймаутом)

попутно возник вопрос — можно ли в emmc бэд-секторы скрыть (или пометить чтобы не использовались)?
Или это уже не имеет смысла, даже если и есть такие инструменты, поскольку флеш уже выработала свой ресурс?

Последний раз редактировалось roman555 29 фев 2020, 18:49, всего редактировалось 2 раз(а).

Не в сети

Профиль    

 

felix2604

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 29 фев 2020, 15:00 


Зарегистрирован: 06 сен 2014, 00:07
Наличности на руках:
1,485.01

Сообщения: 1314
Откуда: Санкт-Петербург

Шейте Miui 7, с ним аппарат заведётся, может минут 10 повисеть на заставке, но потом загрузит начальное меню.
На RN2 такое же поведениие было пока не прошил ранние прошивки.

Не в сети

Профиль    

 

roman555
[ТС]

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 29 фев 2020, 18:38 


Зарегистрирован: 04 май 2017, 12:11
Наличности на руках:
159.77

Сообщения: 100
Откуда: Харьков

felix2604 писал(а):

Шейте Miui 7, с ним аппарат заведётся, может минут 10 повисеть на заставке, но потом загрузит начальное меню.
На RN2 такое же поведениие было пока не прошил ранние прошивки.

Miflash «зашил» 7.5.9.0 — не помогло. Такое впечатление, что шьет только до «time out», а потом делает вид, что шьет. Ведь нет никакой возможности сделать верификацию программно. Про jtag программаторы — в курсе, но такой штуки нет.

Не в сети

Профиль    

 

felix2604

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 01 мар 2020, 01:05 


Зарегистрирован: 06 сен 2014, 00:07
Наличности на руках:
1,485.01

Сообщения: 1314
Откуда: Санкт-Петербург

Прошивка через тестпоинт или фастбут?
Я через тестпоинт реанимировал.
Софт MiFlash.
Изначально с помощью emmcdl очистил флешку, а потом столкнулся с 9008 при загрузке прошивок.
———- Добавлено спустя 3 минуты 16 секунд: ———-
V7.5.8.0 проверьте, с опцией clear all

Не в сети

Профиль    

 

roman555
[ТС]

 Заголовок сообщения: Re: Redmi 3s выключается после Mi лого

СообщениеДобавлено: 01 мар 2020, 15:15 


Зарегистрирован: 04 май 2017, 12:11
Наличности на руках:
159.77

Сообщения: 100
Откуда: Харьков

Спасибо за ответы. Прошивка через edl. Сейчас тестпоинт замыкать уже не обязательно — смарт все время в edl (порт 9008). В фастбут после самой первой прошивки перестал заходить, полностью окирпичился. Но и ранее от фастбута толку не было — загрузчик был заблокированный.

emmcdl таблицы разделов не вычитала. При чтении секторов — в дампе только периодически ER17 и нули.
7.5.8.0 не прошилась — как обычно miflash выдала «успех», но смарт по прежнему — кирпич.

Не в сети

Профиль    

 
Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Qemu ошибка подключения к графической консоли
  • Qe 22d ошибка e1

    • ➤