Related
Hello,
Does anyone know how I can install the security update for December on Android One EU device?
My Software is 1.06.401.14.
I received an update.zip but installation aborted. My System is rooted with Magisk.
I had a look into the zip and found a META-INF Folder; compatibility.zip; payload.bin
payload_properties.txt
Code:
FILE_HASH=Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=
FILE_SIZE=88714324
METADATA_HASH=Kleu845IDwsBg9YKK9sxRLgzsV6kQcw0Qu2aikz/UuA=
METADATA_SIZE=466479
HTC_SCRIPT_VERSION=AB_O80QCT.00.000.007
POST_DESCRIPTION=1.09.401.2 9.0_g CL1008231 release-keys
POST_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/1008231.2:user/release-keys
HTC_CID=HTC__001,HTC__034,HTC__M27,HTC__002
HTC_MID=2Q3F20000
HTC_DEVICE=htc_ocla1_sprout
PRE_DESCRIPTION=1.06.401.14 9.0_g CL990708 release-keys
PRE_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys
PRE_TASKID=515519
care_map.txt
Code:
system
90,0,32767,32768,32770,32945,32947,33452,65534,65536,65538,66043,71519,98304,98306,98481,98483,98988,131071,131072,131074,131579,133736,163840,163842,164017,164019,164524,196607,196608,196610,197115,198114,229376,229378,229553,229555,230060,262142,262144,262146,262651,263103,294912,294914,295089,295091,295596,327678,327680,327682,328187,328209,360448,360450,360955,393214,393216,393218,393723,425982,425984,425986,426491,458750,458752,458754,459259,491518,491520,491522,492027,524286,524288,524290,524795,557054,557056,557058,557563,564954,589824,589826,622592,622594,655360,655362,688128,688130,688635,709641
The data seem to be inside payload.bin. Does anybody know how to extract the payload.bin? Maybe then I can install the *.img manually.
MC_Ohr said:
Hello,
Does anyone know how I can install the security update for December on Android One EU device?
My Software is 1.06.401.14.
I received an update.zip but installation aborted. My System is rooted with Magisk.
I had a look into the zip and found a META-INF Folder; compatibility.zip; payload.bin
payload_properties.txt
Code:
FILE_HASH=Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=
FILE_SIZE=88714324
METADATA_HASH=Kleu845IDwsBg9YKK9sxRLgzsV6kQcw0Qu2aikz/UuA=
METADATA_SIZE=466479
HTC_SCRIPT_VERSION=AB_O80QCT.00.000.007
POST_DESCRIPTION=1.09.401.2 9.0_g CL1008231 release-keys
POST_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/1008231.2:user/release-keys
HTC_CID=HTC__001,HTC__034,HTC__M27,HTC__002
HTC_MID=2Q3F20000
HTC_DEVICE=htc_ocla1_sprout
PRE_DESCRIPTION=1.06.401.14 9.0_g CL990708 release-keys
PRE_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys
PRE_TASKID=515519
care_map.txt
Code:
system
90,0,32767,32768,32770,32945,32947,33452,65534,65536,65538,66043,71519,98304,98306,98481,98483,98988,131071,131072,131074,131579,133736,163840,163842,164017,164019,164524,196607,196608,196610,197115,198114,229376,229378,229553,229555,230060,262142,262144,262146,262651,263103,294912,294914,295089,295091,295596,327678,327680,327682,328187,328209,360448,360450,360955,393214,393216,393218,393723,425982,425984,425986,426491,458750,458752,458754,459259,491518,491520,491522,492027,524286,524288,524290,524795,557054,557056,557058,557563,564954,589824,589826,622592,622594,655360,655362,688128,688130,688635,709641
The data seem to be inside payload.bin. Does anybody know how to extract the payload.bin? Maybe then I can install the *.img manually.
Click to expand...
Click to collapse
Check this out
https://github.com/erfanoabdi/imgpatchtools
MC_Ohr said:
Hello,
Does anyone know how I can install the security update for December on Android One EU device?
My Software is 1.06.401.14.
I received an update.zip but installation aborted. My System is rooted with Magisk.
I had a look into the zip and found a META-INF Folder; compatibility.zip; payload.bin
payload_properties.txt
Code:
FILE_HASH=Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=
FILE_SIZE=88714324
METADATA_HASH=Kleu845IDwsBg9YKK9sxRLgzsV6kQcw0Qu2aikz/UuA=
METADATA_SIZE=466479
HTC_SCRIPT_VERSION=AB_O80QCT.00.000.007
POST_DESCRIPTION=1.09.401.2 9.0_g CL1008231 release-keys
POST_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/1008231.2:user/release-keys
HTC_CID=HTC__001,HTC__034,HTC__M27,HTC__002
HTC_MID=2Q3F20000
HTC_DEVICE=htc_ocla1_sprout
PRE_DESCRIPTION=1.06.401.14 9.0_g CL990708 release-keys
PRE_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys
PRE_TASKID=515519
care_map.txt
Code:
system
90,0,32767,32768,32770,32945,32947,33452,65534,65536,65538,66043,71519,98304,98306,98481,98483,98988,131071,131072,131074,131579,133736,163840,163842,164017,164019,164524,196607,196608,196610,197115,198114,229376,229378,229553,229555,230060,262142,262144,262146,262651,263103,294912,294914,295089,295091,295596,327678,327680,327682,328187,328209,360448,360450,360955,393214,393216,393218,393723,425982,425984,425986,426491,458750,458752,458754,459259,491518,491520,491522,492027,524286,524288,524290,524795,557054,557056,557058,557563,564954,589824,589826,622592,622594,655360,655362,688128,688130,688635,709641
The data seem to be inside payload.bin. Does anybody know how to extract the payload.bin? Maybe then I can install the *.img manually.
Click to expand...
Click to collapse
Send me the ota zip and I will decrypt it withhtc ruu decrypt tool and pull the boot.img and we can patch it and upload it for others.
twinnfamous said:
Send me the ota zip and I will decrypt it withhtc ruu decrypt tool and pull the boot.img and we can patch it and upload it for others.
Click to expand...
Click to collapse
I tried with htc decrypt tool by @nkk71 and @Captain_Throwback but the payload.bin stays untouched. Is there any other way to extract?
I tried out to boot from slot_b but it did not work. I`m afraid that I have to restore to stock and start from the beginning again...
Did anyone with android one device installed the security update successfully? What softwarenumber abe youon now?
So I found the log of update_engine. There is a hash check of the boot partition.
Code:
[1231/141321:INFO:main.cc(115)] Chrome OS Update Engine starting
[1231/141321:INFO:boot_control_android.cc(65)] Loaded boot control hidl hal.
[1231/142402:INFO:update_attempter_android.cc(201)] Using this install plan:
[1231/142402:INFO:install_plan.cc(71)] InstallPlan: new_update, payload type: unknown, source_slot: A, target_slot: B, url: file:///data/ota_package/update.zip, payload size: 88714324, payload hash: Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=, metadata size: 466479, metadata signature: , hash_checks_mandatory: true, powerwash_required: false
[1231/142402:WARNING:htc_utils.cc(151)] HTC_SCRIPT_VERSION=AB_O80QCT.00.000.007
[1231/142402:WARNING:htc_utils.cc(152)] POST_DESCRIPTION=1.09.401.2 9.0_g CL1008231 release-keys
[1231/142402:WARNING:htc_utils.cc(153)] POST_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/1008231.2:user/release-keys
[1231/142402:WARNING:htc_utils.cc(105)] HTC_CID=HTC__001,HTC__034,HTC__M27,HTC__002; ro.cid=HTC__034
[1231/142402:WARNING:htc_utils.cc(82)] HTC__034 matches...
[1231/142402:WARNING:htc_utils.cc(116)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] HTC_MID=2Q3F20000; ro.mid=2Q3F20000
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] HTC_DEVICE=htc_ocla1_sprout; ro.product.device=htc_ocla1_sprout
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] PRE_DESCRIPTION=1.06.401.14 9.0_g CL990708 release-keys; ro.build.description=1.06.401.14 9.0_g CL990708 release-keys
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] PRE_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys; ro.build.fingerprint=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] PRE_TASKID=515519; ro.aa.taskid=515519
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:INFO:cpu_limiter.cc(71)] Setting cgroup cpu shares to 2
[1231/142402:ERROR:utils.cc(193)] fd >= 0 failed: No such file or directory
[1231/142402:ERROR:cpu_limiter.cc(74)] Failed to change cgroup cpu shares to 2 using /sys/fs/cgroup/cpu/update-engine/cpu.shares
[1231/142402:INFO:update_attempter_android.cc(393)] Marking booted slot as good.
[1231/142402:INFO:update_attempter_android.cc(408)] Scheduling an action processor start.
[1231/142402:INFO:action_processor.cc(46)] ActionProcessor: starting InstallPlanAction
[1231/142402:INFO:action_processor.cc(116)] ActionProcessor: finished InstallPlanAction with code ErrorCode::kSuccess
[1231/142402:INFO:action_processor.cc(143)] ActionProcessor: starting DownloadAction
[1231/142402:INFO:install_plan.cc(71)] InstallPlan: new_update, payload type: unknown, source_slot: A, target_slot: B, url: file:///data/ota_package/update.zip, payload size: 88714324, payload hash: Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=, metadata size: 466479, metadata signature: , hash_checks_mandatory: true, powerwash_required: false
[1231/142402:INFO:download_action.cc(179)] Marking new slot as unbootable
[1231/142402:INFO:multi_range_http_fetcher.cc(45)] starting first transfer
[1231/142402:INFO:multi_range_http_fetcher.cc(74)] starting transfer of range 3946+88714324
[1231/142402:INFO:delta_performer.cc(202)] Completed 0/? operations, 16384/88714324 bytes downloaded (0%), overall progress 0%
[1231/142402:INFO:delta_performer.cc(542)] Manifest size in payload matches expected value from Omaha
[1231/142402:INFO:delta_performer.cc(1412)] Verifying metadata hash signature using public key: /etc/update_engine/update-payload-key.pub.pem
[1231/142402:INFO:payload_verifier.cc(93)] signature blob size = 264
[1231/142402:INFO:payload_verifier.cc(112)] Verified correct signature 1 out of 1 signatures.
[1231/142402:INFO:delta_performer.cc(1455)] Metadata hash signature matches value in Omaha response.
[1231/142403:INFO:delta_performer.cc(1475)] Detected a 'delta' payload.
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old system sha256: SzmK3XVHUFtJDoc+dX9vaiAGZOf4LQLkVANqfoX8aYM= size: 2952790016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new system sha256: rEbITUaIVARqP7NyPwGdYise+S1bgUH6i/8tJe281sY= size: 2952790016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old vendor sha256: pN048+oMXhrsVEpgo9XEJD5P3RPItj9tCaugByFMsdc= size: 838860800
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new vendor sha256: MLf9+C36UzOJlYvtrMj5KFgX5qwTNwJpckDDzzJbW9Q= size: 838860800
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old xbl sha256: 7ZOdUYruCVjIfkRCghobVnVbkfa0qSxMWn2HIekTYaE= size: 3080192
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new xbl sha256: 5+SV0zuYEE3AEu/OudE+hfEcs5bdIKPMazgW/T8mXVI= size: 3084288
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old hosd sha256: IRSk31oyN/2qIFspIkdZT7GM5LxCNyz6tfT3mDNBUEg= size: 55889920
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new hosd sha256: q/svW0eAUbGBCj4++K+i26iR2HMqTn9Y+BJu69ULVtg= size: 55894016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old abl sha256: EJVxhBLKjjxEaTcTCIguE0pR+XMnMRkjHDskCBcSKmo= size: 143360
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new abl sha256: JBPuhtgk7UQ2nEYIb6e9el416xA5UA3IjZ1hOshwdmM= size: 147456
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old rpm sha256: c3WMA2MpUBxJOTzyX/wQQH7Z9COQtVQgY4hGpv1+waA= size: 221184
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new rpm sha256: qifOkTY4PUUjDLHuJYbDDFU1EevI33a5JNBS0EYrnDU= size: 225280
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old pmic sha256: emQfsgD2M2NqhDR/05h+eG0s/bx2vXp0gRSZd5S6gIE= size: 36864
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new pmic sha256: pmM/rwlD9WdyVBFSRvTzo+QYKPeAcopyg4kOcxfnYsU= size: 40960
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old boot sha256: Nj8nwvZ8vEWKwTESh6U+VsN1TuKUmwzYYtwUTcGjvPg= size: 55943168
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new boot sha256: LZwSja8jFa2XwgTfVsOx4r5zMUBT2pv7o6GCvt9uCpU= size: 55947264
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old dsp sha256: cbh7/JbA4pEzDeKqfxf88C3kmR29Rm9t/bS8UINoDcg= size: 16777216
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new dsp sha256: cbh7/JbA4pEzDeKqfxf88C3kmR29Rm9t/bS8UINoDcg= size: 16777216
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old radio sha256: VcolpgB2otdbuQKsZsm43XxtF+wcu8oJS9HkQIY/WWw= size: 62337024
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new radio sha256: 27kNwK+qLEi0MdrM7/hFhlahRzg70it5h9kh6LAMMeY= size: 62337024
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old tz sha256: yWyBuoTv2M+tQSxDTfMmJM2n2q6nIhulMrB3sZ+jsVA= size: 1953792
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new tz sha256: HW1NRgU5N1to4CAeZR1e3irSHkYH8RLD1r/r4Xu5OiI= size: 1957888
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old hyp sha256: Hn0RBVarof+yc5EyaH9zNtDHkG8Ode96TfRmfKt0VEQ= size: 266240
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new hyp sha256: 2J68uFWVRIK0zhkEmek3NmGIRmjk1VuXBmF1Yl5u/fY= size: 270336
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old devcfg sha256: sJa43eqyYdFwno2Ybp5I5g8zjKyYphi+J5L53+WeCUI= size: 45056
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new devcfg sha256: glQk7DOZxJbhP6UJA/j1+BUhw0KBQcQddjNhwhoEdDg= size: 49152
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old cmnlib sha256: KGyqdUERnMSlmFMP50PnDA1uvjWvjOOpp7ZKjaqJJk0= size: 217088
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new cmnlib sha256: 4qjItJNTjy5szo8SFXkbNSSdmm5NarEOjIB26q3dOJA= size: 221184
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old cmnlib64 sha256: mqbqjxPFSfYrKJujRULExhM/No+utcO3QqkPTf5d1Ws= size: 262144
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new cmnlib64 sha256: lRNo5nuiENQZXkX1c3hJhz/oc9Whh8nHI+tiuQLAzXw= size: 266240
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old keymaster sha256: KEcfQcnCfsZ6qFfiWTHYSKfT9cpin9CTtIU+5mgcF9s= size: 278528
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new keymaster sha256: 4bprlshY7JPC5LUsRhoxCLjDg9gl5w6sfCZqFkfHx60= size: 282624
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old lockbooter sha256: VtbPjUhr3SClK5ThAby5q8vJs8cGctJ4d+3/m9hnIG4= size: 86016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new lockbooter sha256: 1sl80Aby2MFL9JElaFezl0KWT4mm8w9n7p7JzPWEOIE= size: 90112
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old bluetooth sha256: HmhjTBICwVt0g2tSOedZXEbv4RKk6brzSmBDJKZgNQ0= size: 503808
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new bluetooth sha256: b4bYyd+Ff4w896RlM4SD24/kuxdSKdj3cOKyRg44U9w= size: 503808
[1231/142403:INFO:delta_performer.cc(365)] Applying 3445 operations to partition "system"
[1231/142403:INFO:delta_performer.cc(653)] Starting to apply update payload operations
[1231/142428:INFO:delta_performer.cc(202)] Completed 890/6357 operations (14%), 5488640/88714324 bytes downloaded (6%), overall progress 10%
[1231/142438:INFO:delta_performer.cc(202)] Completed 2035/6357 operations (32%), 7372800/88714324 bytes downloaded (8%), overall progress 20%
[1231/142501:INFO:delta_performer.cc(202)] Completed 2798/6357 operations (44%), 15613952/88714324 bytes downloaded (17%), overall progress 30%
[1231/142523:INFO:delta_performer.cc(202)] Completed 3406/6357 operations (53%), 24854528/88714324 bytes downloaded (28%), overall progress 40%
[1231/142524:INFO:delta_performer.cc(202)] Completed 3437/6357 operations (54%), 40812544/88714324 bytes downloaded (46%), overall progress 50%
[1231/142525:INFO:delta_performer.cc(365)] Applying 2278 operations to partition "vendor"
[1231/142525:INFO:delta_performer.cc(202)] Completed 3815/6357 operations (60%), 54706176/88714324 bytes downloaded (61%), overall progress 60%
[1231/142529:INFO:delta_performer.cc(202)] Completed 4959/6357 operations (78%), 55050240/88714324 bytes downloaded (62%), overall progress 70%
[1231/142545:INFO:delta_performer.cc(202)] Completed 5722/6357 operations (90%), 63242240/88714324 bytes downloaded (71%), overall progress 80%
[1231/142546:INFO:delta_performer.cc(365)] Applying 7 operations to partition "xbl"
[1231/142546:INFO:delta_performer.cc(365)] Applying 12 operations to partition "hosd"
[1231/142559:INFO:delta_performer.cc(365)] Applying 2 operations to partition "abl"
[1231/142559:INFO:delta_performer.cc(365)] Applying 4 operations to partition "rpm"
[1231/142559:INFO:delta_performer.cc(365)] Applying 2 operations to partition "pmic"
[1231/142559:INFO:delta_performer.cc(365)] Applying 12 operations to partition "boot"
[1231/142600:ERROR:delta_performer.cc(1057)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
[1231/142600:ERROR:delta_performer.cc(1062)] Expected: sha256|hex = 56364358B930F09705B1DA54779402C9B59A5DA333F9B860B3AB401EF5BDD9EE
[1231/142600:ERROR:delta_performer.cc(1065)] Calculated: sha256|hex = 42AB021164B5015BFD12278AE756BC5FD599C982B3944303745F748905BB944C
[1231/142600:ERROR:delta_performer.cc(1076)] Operation source (offset:size) in blocks: 0:4312,4313:1270,5584:8,5597:2188,7786:1042,8833:64,8900:1183,10088:79,10168:2,10175:1,10177:1170,11348:2310
[1231/142600:ERROR:delta_performer.cc(1242)] ValidateSourceHash(source_hasher.raw_hash(), operation, error) failed.
[1231/142600:ERROR:delta_performer.cc(289)] Failed to perform SOURCE_BSDIFF operation 5750, which is the operation 0 in partition "boot"
[1231/142600:ERROR:download_action.cc(274)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
[1231/142600:INFO:delta_performer.cc(305)] Discarding 6446230 unused downloaded bytes
[1231/142600:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
[1231/142600:INFO:multi_range_http_fetcher.cc
Gesendet von meinem HTC U11 life mit Tapatalk
MC_Ohr said:
So I found the log of update_engine. There is a hash check of the boot partition.
Code:
[1231/141321:INFO:main.cc(115)] Chrome OS Update Engine starting
[1231/141321:INFO:boot_control_android.cc(65)] Loaded boot control hidl hal.
[1231/142402:INFO:update_attempter_android.cc(201)] Using this install plan:
[1231/142402:INFO:install_plan.cc(71)] InstallPlan: new_update, payload type: unknown, source_slot: A, target_slot: B, url: file:///data/ota_package/update.zip, payload size: 88714324, payload hash: Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=, metadata size: 466479, metadata signature: , hash_checks_mandatory: true, powerwash_required: false
[1231/142402:WARNING:htc_utils.cc(151)] HTC_SCRIPT_VERSION=AB_O80QCT.00.000.007
[1231/142402:WARNING:htc_utils.cc(152)] POST_DESCRIPTION=1.09.401.2 9.0_g CL1008231 release-keys
[1231/142402:WARNING:htc_utils.cc(153)] POST_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/1008231.2:user/release-keys
[1231/142402:WARNING:htc_utils.cc(105)] HTC_CID=HTC__001,HTC__034,HTC__M27,HTC__002; ro.cid=HTC__034
[1231/142402:WARNING:htc_utils.cc(82)] HTC__034 matches...
[1231/142402:WARNING:htc_utils.cc(116)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] HTC_MID=2Q3F20000; ro.mid=2Q3F20000
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] HTC_DEVICE=htc_ocla1_sprout; ro.product.device=htc_ocla1_sprout
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] PRE_DESCRIPTION=1.06.401.14 9.0_g CL990708 release-keys; ro.build.description=1.06.401.14 9.0_g CL990708 release-keys
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] PRE_FINGERPRINT=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys; ro.build.fingerprint=htc/ocla1_sprout_00401/htc_ocla1_sprout:8.0.0/OPR6.170623.013/990708.14:user/release-keys
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:WARNING:htc_utils.cc(105)] PRE_TASKID=515519; ro.aa.taskid=515519
[1231/142402:WARNING:htc_utils.cc(111)] Pass checking...
[1231/142402:INFO:cpu_limiter.cc(71)] Setting cgroup cpu shares to 2
[1231/142402:ERROR:utils.cc(193)] fd >= 0 failed: No such file or directory
[1231/142402:ERROR:cpu_limiter.cc(74)] Failed to change cgroup cpu shares to 2 using /sys/fs/cgroup/cpu/update-engine/cpu.shares
[1231/142402:INFO:update_attempter_android.cc(393)] Marking booted slot as good.
[1231/142402:INFO:update_attempter_android.cc(408)] Scheduling an action processor start.
[1231/142402:INFO:action_processor.cc(46)] ActionProcessor: starting InstallPlanAction
[1231/142402:INFO:action_processor.cc(116)] ActionProcessor: finished InstallPlanAction with code ErrorCode::kSuccess
[1231/142402:INFO:action_processor.cc(143)] ActionProcessor: starting DownloadAction
[1231/142402:INFO:install_plan.cc(71)] InstallPlan: new_update, payload type: unknown, source_slot: A, target_slot: B, url: file:///data/ota_package/update.zip, payload size: 88714324, payload hash: Pcz1Sw3IChOxEJWNniwpI8pSS0aN3nP+KlZMHKn5Z4E=, metadata size: 466479, metadata signature: , hash_checks_mandatory: true, powerwash_required: false
[1231/142402:INFO:download_action.cc(179)] Marking new slot as unbootable
[1231/142402:INFO:multi_range_http_fetcher.cc(45)] starting first transfer
[1231/142402:INFO:multi_range_http_fetcher.cc(74)] starting transfer of range 3946+88714324
[1231/142402:INFO:delta_performer.cc(202)] Completed 0/? operations, 16384/88714324 bytes downloaded (0%), overall progress 0%
[1231/142402:INFO:delta_performer.cc(542)] Manifest size in payload matches expected value from Omaha
[1231/142402:INFO:delta_performer.cc(1412)] Verifying metadata hash signature using public key: /etc/update_engine/update-payload-key.pub.pem
[1231/142402:INFO:payload_verifier.cc(93)] signature blob size = 264
[1231/142402:INFO:payload_verifier.cc(112)] Verified correct signature 1 out of 1 signatures.
[1231/142402:INFO:delta_performer.cc(1455)] Metadata hash signature matches value in Omaha response.
[1231/142403:INFO:delta_performer.cc(1475)] Detected a 'delta' payload.
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old system sha256: SzmK3XVHUFtJDoc+dX9vaiAGZOf4LQLkVANqfoX8aYM= size: 2952790016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new system sha256: rEbITUaIVARqP7NyPwGdYise+S1bgUH6i/8tJe281sY= size: 2952790016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old vendor sha256: pN048+oMXhrsVEpgo9XEJD5P3RPItj9tCaugByFMsdc= size: 838860800
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new vendor sha256: MLf9+C36UzOJlYvtrMj5KFgX5qwTNwJpckDDzzJbW9Q= size: 838860800
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old xbl sha256: 7ZOdUYruCVjIfkRCghobVnVbkfa0qSxMWn2HIekTYaE= size: 3080192
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new xbl sha256: 5+SV0zuYEE3AEu/OudE+hfEcs5bdIKPMazgW/T8mXVI= size: 3084288
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old hosd sha256: IRSk31oyN/2qIFspIkdZT7GM5LxCNyz6tfT3mDNBUEg= size: 55889920
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new hosd sha256: q/svW0eAUbGBCj4++K+i26iR2HMqTn9Y+BJu69ULVtg= size: 55894016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old abl sha256: EJVxhBLKjjxEaTcTCIguE0pR+XMnMRkjHDskCBcSKmo= size: 143360
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new abl sha256: JBPuhtgk7UQ2nEYIb6e9el416xA5UA3IjZ1hOshwdmM= size: 147456
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old rpm sha256: c3WMA2MpUBxJOTzyX/wQQH7Z9COQtVQgY4hGpv1+waA= size: 221184
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new rpm sha256: qifOkTY4PUUjDLHuJYbDDFU1EevI33a5JNBS0EYrnDU= size: 225280
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old pmic sha256: emQfsgD2M2NqhDR/05h+eG0s/bx2vXp0gRSZd5S6gIE= size: 36864
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new pmic sha256: pmM/rwlD9WdyVBFSRvTzo+QYKPeAcopyg4kOcxfnYsU= size: 40960
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old boot sha256: Nj8nwvZ8vEWKwTESh6U+VsN1TuKUmwzYYtwUTcGjvPg= size: 55943168
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new boot sha256: LZwSja8jFa2XwgTfVsOx4r5zMUBT2pv7o6GCvt9uCpU= size: 55947264
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old dsp sha256: cbh7/JbA4pEzDeKqfxf88C3kmR29Rm9t/bS8UINoDcg= size: 16777216
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new dsp sha256: cbh7/JbA4pEzDeKqfxf88C3kmR29Rm9t/bS8UINoDcg= size: 16777216
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old radio sha256: VcolpgB2otdbuQKsZsm43XxtF+wcu8oJS9HkQIY/WWw= size: 62337024
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new radio sha256: 27kNwK+qLEi0MdrM7/hFhlahRzg70it5h9kh6LAMMeY= size: 62337024
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old tz sha256: yWyBuoTv2M+tQSxDTfMmJM2n2q6nIhulMrB3sZ+jsVA= size: 1953792
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new tz sha256: HW1NRgU5N1to4CAeZR1e3irSHkYH8RLD1r/r4Xu5OiI= size: 1957888
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old hyp sha256: Hn0RBVarof+yc5EyaH9zNtDHkG8Ode96TfRmfKt0VEQ= size: 266240
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new hyp sha256: 2J68uFWVRIK0zhkEmek3NmGIRmjk1VuXBmF1Yl5u/fY= size: 270336
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old devcfg sha256: sJa43eqyYdFwno2Ybp5I5g8zjKyYphi+J5L53+WeCUI= size: 45056
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new devcfg sha256: glQk7DOZxJbhP6UJA/j1+BUhw0KBQcQddjNhwhoEdDg= size: 49152
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old cmnlib sha256: KGyqdUERnMSlmFMP50PnDA1uvjWvjOOpp7ZKjaqJJk0= size: 217088
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new cmnlib sha256: 4qjItJNTjy5szo8SFXkbNSSdmm5NarEOjIB26q3dOJA= size: 221184
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old cmnlib64 sha256: mqbqjxPFSfYrKJujRULExhM/No+utcO3QqkPTf5d1Ws= size: 262144
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new cmnlib64 sha256: lRNo5nuiENQZXkX1c3hJhz/oc9Whh8nHI+tiuQLAzXw= size: 266240
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old keymaster sha256: KEcfQcnCfsZ6qFfiWTHYSKfT9cpin9CTtIU+5mgcF9s= size: 278528
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new keymaster sha256: 4bprlshY7JPC5LUsRhoxCLjDg9gl5w6sfCZqFkfHx60= size: 282624
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old lockbooter sha256: VtbPjUhr3SClK5ThAby5q8vJs8cGctJ4d+3/m9hnIG4= size: 86016
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new lockbooter sha256: 1sl80Aby2MFL9JElaFezl0KWT4mm8w9n7p7JzPWEOIE= size: 90112
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo old bluetooth sha256: HmhjTBICwVt0g2tSOedZXEbv4RKk6brzSmBDJKZgNQ0= size: 503808
[1231/142403:INFO:delta_performer.cc(380)] PartitionInfo new bluetooth sha256: b4bYyd+Ff4w896RlM4SD24/kuxdSKdj3cOKyRg44U9w= size: 503808
[1231/142403:INFO:delta_performer.cc(365)] Applying 3445 operations to partition "system"
[1231/142403:INFO:delta_performer.cc(653)] Starting to apply update payload operations
[1231/142428:INFO:delta_performer.cc(202)] Completed 890/6357 operations (14%), 5488640/88714324 bytes downloaded (6%), overall progress 10%
[1231/142438:INFO:delta_performer.cc(202)] Completed 2035/6357 operations (32%), 7372800/88714324 bytes downloaded (8%), overall progress 20%
[1231/142501:INFO:delta_performer.cc(202)] Completed 2798/6357 operations (44%), 15613952/88714324 bytes downloaded (17%), overall progress 30%
[1231/142523:INFO:delta_performer.cc(202)] Completed 3406/6357 operations (53%), 24854528/88714324 bytes downloaded (28%), overall progress 40%
[1231/142524:INFO:delta_performer.cc(202)] Completed 3437/6357 operations (54%), 40812544/88714324 bytes downloaded (46%), overall progress 50%
[1231/142525:INFO:delta_performer.cc(365)] Applying 2278 operations to partition "vendor"
[1231/142525:INFO:delta_performer.cc(202)] Completed 3815/6357 operations (60%), 54706176/88714324 bytes downloaded (61%), overall progress 60%
[1231/142529:INFO:delta_performer.cc(202)] Completed 4959/6357 operations (78%), 55050240/88714324 bytes downloaded (62%), overall progress 70%
[1231/142545:INFO:delta_performer.cc(202)] Completed 5722/6357 operations (90%), 63242240/88714324 bytes downloaded (71%), overall progress 80%
[1231/142546:INFO:delta_performer.cc(365)] Applying 7 operations to partition "xbl"
[1231/142546:INFO:delta_performer.cc(365)] Applying 12 operations to partition "hosd"
[1231/142559:INFO:delta_performer.cc(365)] Applying 2 operations to partition "abl"
[1231/142559:INFO:delta_performer.cc(365)] Applying 4 operations to partition "rpm"
[1231/142559:INFO:delta_performer.cc(365)] Applying 2 operations to partition "pmic"
[1231/142559:INFO:delta_performer.cc(365)] Applying 12 operations to partition "boot"
[1231/142600:ERROR:delta_performer.cc(1057)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
[1231/142600:ERROR:delta_performer.cc(1062)] Expected: sha256|hex = 56364358B930F09705B1DA54779402C9B59A5DA333F9B860B3AB401EF5BDD9EE
[1231/142600:ERROR:delta_performer.cc(1065)] Calculated: sha256|hex = 42AB021164B5015BFD12278AE756BC5FD599C982B3944303745F748905BB944C
[1231/142600:ERROR:delta_performer.cc(1076)] Operation source (offset:size) in blocks: 0:4312,4313:1270,5584:8,5597:2188,7786:1042,8833:64,8900:1183,10088:79,10168:2,10175:1,10177:1170,11348:2310
[1231/142600:ERROR:delta_performer.cc(1242)] ValidateSourceHash(source_hasher.raw_hash(), operation, error) failed.
[1231/142600:ERROR:delta_performer.cc(289)] Failed to perform SOURCE_BSDIFF operation 5750, which is the operation 0 in partition "boot"
[1231/142600:ERROR:download_action.cc(274)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
[1231/142600:INFO:delta_performer.cc(305)] Discarding 6446230 unused downloaded bytes
[1231/142600:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
[1231/142600:INFO:multi_range_http_fetcher.cc
Gesendet von meinem HTC U11 life mit Tapatalk
Click to expand...
Click to collapse
I've noticed on Oreo firmware for u11 and u11 life if bootloader is unlocked the system will show modified even if nothing was altered. That means the only way would be to lock bootloader and ruu back to stock. It sucks because if we can't get boot.img to patch then there will be no root on the new update you are trying to update to.
twinnfamous said:
I've noticed on Oreo firmware for u11 and u11 life if bootloader is unlocked the system will show modified even if nothing was altered. That means the only way would be to lock bootloader and ruu back to stock. It sucks because if we can't get boot.img to patch then there will be no root on the new update you are trying to update to.
Click to expand...
Click to collapse
I have now flashed the boot_signed.img and was able to take the update. The new factory Image is also online on easy firmware, so I'm downloading. When it´s finished I will patch and upload again.
MC_Ohr said:
I have now flashed the boot_signed.img and was able to take the update. The new factory Image is also online on easy firmware, so I'm downloading. When it´s finished I will patch and upload again.
Click to expand...
Click to collapse
Ok cool
Root Elephone U Pro
Foreword:
It was a long way to get root on the U Pro and dangerous , i could brick my phone , but finally its done!
It wasn't my own work at all. We all shared ideas and thoughts . We that are
Mr. Fünke (not an xda member) @Maherabed1986 @lKinder_Bueno @dypak and me @skeleton1911 .
so thanks goes also to them.
In the last days we spent hours and hours to get not only root . ( but this is another chapter, soon more )
Took the last OTA 20180227 Build and extracted the payload.bin (in it are all images etc.) Surprise
the System has a second partition table of all images . called _a and _b ( example: boot_a.img , boot_b.img)
thats a good thing, because if one gets damaged the Bootloader will boot the other Partition.
i could write many more but lets come to the Topic.
Code:
[SIZE="3"][COLOR="Red"]#/Disclaimer[/COLOR]
* I am not responsible for anything/bricked devices, dead SD cards,
* thermonuclear war, or exploding cars.
[/SIZE]
What do we need for Root our U Pro
1. QPST flashtools (qualcomm)
2. Qualcomm Drivers for the Device
3. a firehose file for SDM660
4. rawprogram_unsparse and patch0.xml
6. patched_boot.img
7.ADB
8.unlocked bootloader
Uploaded all here: https://1drv.ms/u/s!Am93l3qEx-D_hJZQQpXbjL45aKcUiQ only for 20180227
TOOL FILES https://1drv.ms/u/s!Am93l3qEx-D_hOcLmv0inQJ-vrVdLg
IF YOU USE QFIL FLASHTOOLS YOU DONT NEED TO UNLOCK THE BOOTLOADER:
THIS IS ONLY NECCESARY IF YOU WANT TO USE FASTBOOT COMMANDS: SINCE 20180423 BASE
(files are at the bottom of this post)
Also enable USB Debugging in settings/system/developer settings
(tap 7 times on the build number in settings/system/phone info if you dont have developer settings)
we need an unlocked bootloader
Enable OEM unlock in developer settings..
If you unlocked the bootloader , that will wipe your userdata and
you have the google protection password screen.
Notice: if your password dont work , no panic! just enter 30 times a wrong password with minimal 5 letters and the phone will make a factory reset.
for unlock bootloader do:
Code:
adb shell
Code:
reboot bootloader
and
Code:
fastboot flashing unlock
that will wipe userdata!
after that you can enter recovery via bootloader or it reboots itself to it . when you see the red android icon . hold power and vol- 5 seconds and then slide to vol+ and back to vol- or try : press power and then click on vol+
that will enter recovery, then reboot , you will have to enter the google password 30times (look above)
After the phone is back on Homescreen , enable usb debugging again and use adb
Code:
adb shell
Code:
reboot edl
1. install ADB . (newest ADB files are in the zip) . copy the "adb" folder to C:/
2. install the QPST/QFIL Flashtool
3. install Qualcomm Drivers
-----------------------------------------------------------------
Connect your phone to pc
when all is installed open a command (cmd) and go to your adb folder
Code:
C:\>cd adb
we need to reboot the phone to the EDL mode (emergency download mode) to use the Flashtool :
Code:
adb shell
reboot edl
phone will reboot to edl mode ( black screen, no led)
Now check your device manager . the COM & LTP port should show "Qualcomm HS-USB QDLoader 9008"
if not then update the driver and choose it from your internal list. or google for it
if the driver is fine, open the QPST/QFIL FLashtool in
Code:
C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe
prepare the Flashtool:
in Select Build Type:
choose: Flat Build
in Select Programmer:
browse and choose the "prog_emmc_ufs_firehose_Sdm660_ddr.elf" file
( you cant see it change to "all files" )
Load XML:
now choose the rawprogram_unsparse.xml and right after the patch0.xml
you can press the "download button"
wait a bit , at the end of the flashing procedure it will make an error, thats normal because i left the patch0.xml empty.
after all disconnect the cable and hold Power button a few seconds. phone will reboot and you have root.
install magisk manager.apk from magisk thread .
enjoy
This is the boot.img of the boot_b partition and will root the system_b.
the system_a is untouched , also the boot_a.img . so if an OTA will come you can install it with no problem.
BTW after you installed magisk manager.apk , choose install again and direct download to get magisk files into system.
IF YOU USE QFIL FLASHTOOLS YOU DONT NEED TO UNLOCK THE BOOTLOADER:
THIS IS ONLY NECCESARY IF YOU WANT TO USE FASTBOOT COMMANDS: SINCE 20180423 BASE
20180227 Root Boot.img
Flashable via QFIL Flashtools only!
you dont need to be unlock. just install qfil and its drivers...
Go here: https://1drv.ms/u/s!Am93l3qEx-D_hJZPwPoJzH4zTrkLqQ
20180423 Root Boot.img
use QFil flashtools when you dont want to unlock your bootloader- (unlocking bootloader will wipe your data)
if you want fastboot commands unlock the bootloader and flash the boot.img via fastboot . ( you have to be in bootloader mode )
for this place only the boot.img to your adb folder and do this commands
GO here: https://1drv.ms/u/s!Am93l3qEx-D_hJZODc_2yG3Kl-VTow
20180511 Root Boot.img
Rooted Boot.img .- https://1drv.ms/u/s!Am93l3qEx-D_hJZv4OOlKoGa6BFxdA
you can use this with the files above ( raw.xml etc for QFIL , or flash it via fastboot if you are unlocked
go to bootloader mode with
Code:
adb shell
reboot bootloader
then
Code:
fastboot flash boot_a boot.img
and
Code:
fastboot flash boot_b boot.img
thats all.
easy to do
after install magisk manager to activate root
maybe some of you are interested in the partitions and sectors of the U pro to take out a dump or make a rawprogram_unparse.xml for a fullrom
i took them out with adb for you :
Code:
Number Start End Size File system Name Flags
1 131072s 138239s 7168s xbl_a
2 138240s 145407s 7168s xbl_b
3 145408s 153599s 8192s tz_a
4 153600s 161791s 8192s tz_b
5 161792s 162815s 1024s rpm_a
6 162816s 163839s 1024s rpm_b
7 163840s 164863s 1024s hyp_a
8 164864s 165887s 1024s hyp_b
9 165888s 166911s 1024s pmic_a
10 166912s 167935s 1024s pmic_b
11 167936s 172031s 4096s fsg
12 262144s 393215s 131072s boot_a
13 393216s 524287s 131072s boot_b
14 524288s 6815743s 6291456s ext4 system_a
15 6815744s 13107199s 6291456s ext4 system_b
16 13107200s 14745599s 1638400s ext4 vendor_a
17 14745600s 16383999s 1638400s ext4 vendor_b
18 16384000s 16386047s 2048s keymaster_a
19 16386048s 16388095s 2048s keymaster_b
20 16388096s 16390143s 2048s cmnlib_a
21 16390144s 16392191s 2048s cmnlib64_a
22 16392192s 16394239s 2048s cmnlib_b
23 16394240s 16396287s 2048s cmnlib64_b
24 16396288s 16404479s 8192s mdtpsecapp_a
25 16404480s 16412671s 8192s mdtpsecapp_b
26 16412672s 16478207s 65536s mdtp_a
27 16478208s 16543743s 65536s mdtp_b
28 16543744s 16769023s 225280s fat16 modem_a
29 16769024s 16994303s 225280s fat16 modem_b
30 16994304s 17027071s 32768s ext4 dsp_a
31 17027072s 17059839s 32768s ext4 dsp_b
32 17059840s 17061887s 2048s abl_a
33 17061888s 17063935s 2048s abl_b
34 17063936s 17065983s 2048s dip
35 17065984s 17065991s 8s devinfo
36 17065992s 17066503s 512s apdp
37 17066504s 17067015s 512s msadp
38 17067016s 17067017s 2s dpo
39 17067024s 17133871s 66848s splash
40 17133872s 17133879s 8s limits
41 17133880s 17135927s 2048s toolsfv
42 17170432s 17186815s 16384s logfs
43 17301504s 17303551s 2048s ddr
44 17303552s 17303583s 32s sec
45 17303584s 17305631s 2048s bluetooth_a
46 17305632s 17307679s 2048s bluetooth_b
47 17432576s 17436671s 4096s prodinfo
48 17436672s 17457151s 20480s ext4 factory
49 17457152s 17477631s 20480s ext4 factorybak
50 17477632s 17477633s 2s fsc
51 17477640s 17477655s 16s ssd
52 17477656s 17481751s 4096s modemst1
53 17481752s 17485847s 4096s modemst2
54 17485848s 17551383s 65536s ext4 persist
55 17551384s 17553431s 2048s misc
56 17553432s 17554455s 1024s keystore
57 17554456s 17556503s 2048s devcfg_a
58 17556504s 17558551s 2048s devcfg_b
59 17558552s 17559575s 1024s frp
60 17559576s 17690647s 131072s logdump
61 17690648s 17694743s 4096s sti
6
2 17825792s 17826047s 256s storsec
63 17956864s 18219007s 262144s rawdump
64 18219008s 18219135s 128s vbmeta_a
65 18219136s 18219263s 128s vbmeta_b
66 18350080s 244277214s 225927135s userdata
Code:
[SIZE="3"]1|U_Pro:/ # ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name
total 0
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 abl_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 abl_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 apdp -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 bluetooth_a -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 bluetooth_b -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 boot_a -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 boot_b -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib64_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib64_b -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib_a -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib_b -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 ddr -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devcfg_a -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devcfg_b -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devinfo -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dip -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dpo -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dsp_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dsp_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 factory -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 factorybak -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 frp -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 fsc -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 hyp_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 hyp_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keymaster_a -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keymaster_b -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keystore -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 logdump -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 logfs -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtp_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtp_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtpsecapp_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtpsecapp_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 misc -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modem_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modem_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modemst1 -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modemst2 -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 msadp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 pmic_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 pmic_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 prodinfo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 rawdump -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 rpm_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 rpm_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 sec -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 splash -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 ssd -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 sti -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 19
70-01-08 10:22 storsec -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 system_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 system_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 toolsfv -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 tz_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 tz_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 userdata -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vbmeta_a -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vbmeta_b -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vendor_a -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vendor_b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 xbl_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 xbl_b -> /dev/block/mmcblk0p2[/SIZE]
Great job buddy very clear explaining
Wish you the best as always
skeleton1911 said:
Root Elephone U Pro
Foreword:
It was a long way to get root on the U Pro and dangerous , i could brick my phone , but finally its done!
It wasn't my own work at all. We all shared ideas and thoughts . We that are
Mr. Fünke (not an xda member) @Maherabed1986 @lKinder_Bueno @dypak and me @skeleton1911 .
so thanks goes also to them.
In the last days we spent hours and hours to get not only root . ( but this is another chapter, soon more )
Took the last OTA 20180227 Build and extracted the payload.bin (in it are all images etc.) Surprise
the System has a second partition table of all images . called _a and _b ( example: boot_a.img , boot_b.img)
thats a good thing, because if one gets damaged the Bootloader will boot the other Partition.
i could write many more but lets come to the Topic.
Code:
[SIZE="3"][COLOR="Red"]#/Disclaimer[/COLOR]
* I am not responsible for anything/bricked devices, dead SD cards,
* thermonuclear war, or exploding cars.
[/SIZE]
What do we need for Root our U Pro
1. QPST flashtools (qualcomm)
2. Qualcomm Drivers for the Device
3. a firehose file for SDM660
4. rawprogram_unsparse and patch0.xml
5. python-2.7.13.amd64
6. patched_boot.img
7.ADB
Uploaded all here: https://androidfilehost.com/?fid=673956719939832819
Also enable USB Debugging in settings/system/developer settings
(tap 7 times on the build number in settings/system/phone info if you dont have developer settings)
we dont need an unlocked bootloader.
If you unlocked the bootloader already and dont locked it again the flashtool will do it , that could wipe all userdata and
you have the google protection password screen.
Notice: if your password dont work , no panic! just enter 30 times a wrong password with minimal 5 letters and the phone will make a factory reset.
1. install ADB . (newest ADB files are in the zip) . copy the "adb" folder to C:/
2. install the QPST/QFIL Flashtool
3. install python 2.7.13
4. install Qualcomm Drivers
-----------------------------------------------------------------
Connect your phone to pc
when all is installed open a command (cmd) and go to your adb folder
Code:
C:\>cd adb
we need to reboot the phone to the EDL mode (emergency download mode) to use the Flashtool :
Code:
adb shell
reboot edl
phone will reboot to edl mode ( black screen, no led)
Now check your device manager . the COM & LTP port should show "Qualcomm HS-USB QDLoader 9008"
if not then update the driver and choose it from your internal list. or google for it
if the driver is fine, open the QPST/QFIL FLashtool in
Code:
C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe
prepare the Flashtool:
in Select Build Type:
choose: Flat Build
in Select Programmer:
browse and choose the "prog_emmc_ufs_firehose_Sdm660_ddr.elf" file
( you cant see it change to "all files" )
Load XML:
now choose the rawprogram_unsparse.xml and right after the patch0.xml
you can press the "download button"
wait a bit , at the end of the flashing procedure it will make an error, thats normal because i left the patch0.xml empty.
after all disconnect the cable and hold Power button a few seconds. phone will reboot and you have root.
install magisk manager.apk from magisk thread .
enjoy
This is the boot.img of the boot_b partition and will root the system_b.
the system_a is untouched , also the boot_a.img . so if an OTA will come you can install it with no problem.
BTW after you installed magisk manager.apk , choose install again and direct download to get magisk files into system.
Click to expand...
Click to collapse
Hello skeleton
Thanks for the perfect job!
May you can help me, I've done all steps and all went fine except after magisk manager installation I've to choose download zip only or patch boot.img. I tried both but only download is for twrp and patching boot.img I can only patch it on as card ?
What's the next step ?
Laptapper said:
Hello skeleton
Thanks for the perfect job!
May you can help me, I've done all steps and all went fine except after magisk manager installation I've to choose download zip only or patch boot.img. I tried both but only download is for twrp and patching boot.img I can only patch it on as card ?
What's the next step ?
Click to expand...
Click to collapse
In magisk manager tap on install , a new window pops up. Choose directly install.
That's all. After it downloaded and flashed the file you can reboot.
Wait.
Do you see direct install?
Gesendet von meinem U_Pro mit Tapatalk
No I didn't see direct install
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
skeleton1911 said:
In magisk manager tap on install , a new window pops up. Choose directly install.
That's all. After it downloaded and flashed the file you can reboot.
Wait.
Do you see direct install?
Gesendet von meinem U_Pro mit Tapatalk
Click to expand...
Click to collapse
No I didn't see direct install.
Laptapper said:
No I didn't see direct install
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
No I didn't see direct install.
Click to expand...
Click to collapse
What build number you are on?
You are on 20180227 build?
If so. Flash the boot.img again. And reboot.
Gesendet von meinem U_Pro mit Tapatalk
Success! I have gotten my UPro rooted! Thanks so much Skeleton! I'm new to it, I did something wrong at my first attempt, the flushing stopped, wrong path
on my pc or something, but it gave me a scare when I had to enter like, x10 a pin and at some point there was some warnings that the phone will be locked out after 9 more trials. I've managed to shut it off and go manually to recovery and do factory reset. The second time was the charm, the end of the flushing hangs on some error(as you predicted) and then this big relief, the phone comes to life!
https://drive.google.com/file/d/1RYP40jVhYsQXAu8ZBxz_zrByGxEIXtzw/view?usp=sharing
mzsquared said:
Success! I have gotten my UPro rooted! Thanks so much Skeleton! I'm new to it, I did something wrong at my first attempt, the flushing stopped, wrong path
on my pc or something, but it gave me a scare when I had to enter like, x10 a pin and at some point there was some warnings that the phone will be locked out after 9 more trials. I've managed to shut it off and go manually to recovery and do factory reset. The second time was the charm, the end of the flushing hangs on some error(as you predicted) and then this big relief, the phone comes to life!
https://drive.google.com/file/d/1RYP40jVhYsQXAu8ZBxz_zrByGxEIXtzw/view?usp=sharing
Click to expand...
Click to collapse
yep . that it hangs at the end of the flashtool is normal. because i left the patch0.xml empty...
also you didnt reboot to recovery. just enter the password . 10 times and phone display. please reboot info. after that another 10 times. phone displays a reboot info. after that it shows that it will reboot itself and delete userdata after another 10 times .... that is not part of my mistaken. its because of googles protection laws....
skeleton1911 said:
In magisk manager tap on install , a new window pops up. Choose directly install.
That's all. After it downloaded and flashed the file you can reboot.
Wait.
Do you see direct install?
Gesendet von meinem U_Pro mit Tapatalk
Click to expand...
Click to collapse
I used Total Commander from Google Play, had MagiskAPK on mu sd card, Total Commander asks for permission to install "other sources app" and it's done.
mzsquared said:
I used Total Commander from Google Play, had MagiskAPK on mu sd card, Total Commander asks for permission to install "other sources app" and it's done.
Click to expand...
Click to collapse
thanks. but thats not the problem of @Laptapper.
i think he is not on the latest build. because we have _a and _b system.
the latest build is on _b . also the root is only in _b
he could use cmd and adb in bootlader mode
fastboot set_active b
Setting current slot to 'b'...
but that will not work . the bootloader in the u pro is a bit strange. tested many things
Did u finally get root?
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
skeleton1911 said:
thanks. but thats not the problem of @Laptapper.
i think he is not on the latest build. because we have _a and _b system.
the latest build is on _b . also the root is only in _b
he could use cmd and adb in bootlader mode
fastboot set_active b
Setting current slot to 'b'...
but that will not work . the bootloader in the u pro is a bit strange. tested many things
Click to expand...
Click to collapse
Same boat. I could not get root.
abbas said:
Did u finally get root?
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
Same boat. I could not get root.
Click to expand...
Click to collapse
Strange . For many users it works. For some not.
One user told me that he installed the ota with the fota app.
And then he flashed the ota.zip again. So he did installed it twice.
For him the root also don't work.
So maybe _a and _b partitions are the same now.
And the system is running in _a partition now.
The root only goes to _b partition.
That could be an explaining for it..
Also can you send me the Qfil log ?
skeleton1911 said:
Strange . For many users it works. For some not.
One user told me that he installed the ota with the fota app.
And then he flashed the ota.zip again. So he did installed it twice.
For him the root also don't work.
So maybe _a and _b partitions are the same now.
And the system is running in _a partition now.
The root only goes to _b partition.
That could be an explaining for it..
Also can you send me the Qfil log ?
Click to expand...
Click to collapse
Thanks for your help. This is my log
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM:
rawprogram_unsparse.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: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Programmer Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
Process Index:0
Image Search Path: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Start Download
Program Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
22:52:17: Requested ID 13, file: "C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
22:52:18: 629284 bytes transferred in 0.313000 seconds (1.9174MBps)
22:52:18: File transferred successfully
22:52:18: 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
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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
22:52:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=rawprogram_unsparse.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:22: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:22: INFO: Showing network mappings to allow debugging
22:52:22: INFO:
22:52:22: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
22:52:22: INFO: Looking for file 'rawprogram_unsparse.xml'
22:52:22: INFO: User wants to talk to port '\\.\COM10'
22:52:22: INFO: Took 0.00000000 seconds to open port
22:52:22: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:52:22: INFO: If you don't want this, use --dontsorttags
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO:
Total to be tansferd with <program> or <read> is 47.79 MB
22:52:22: INFO: Sending <configure>
22:52:22: INFO: TARGET SAID: 'UFS DEVICE RESET'
22:52:22: INFO: TARGET SAID: 'Binary build date: Dec 8 2017 @ 13:33:11'
22:52:22: INFO: TARGET SAID: 'Chip serial num: 0 (0x0)'
22:52:22: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
22:52:22: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
22:52:22: INFO: In handleProgram('boot.img')
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO: =======================================================
22:52:22: INFO: {<program> FILE: 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'}
22:52:22: INFO: {<program> (47.79 MB) 97883 sectors needed at location 393216 on LUN 0}
22:52:22: INFO: =======================================================
22:52:23: INFO: TARGET SAID: 'start 393216, num 97883'
22:52:24: INFO: Overall to target 1.391 seconds (34.36 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: TARGET SAID: 'Finished programming start_sector 491099 and TotalSectorsToProgram 97883'
22:52:24: INFO:
22:52:24: INFO: =======================================================
22:52:24: INFO: ==================== {SUCCESS} ========================
22:52:24: INFO: =======================================================
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: ==============================================================
22:52:24: INFO: Files used and their paths
22:52:24: INFO: 1 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
22:52:24: INFO: 2 'C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml'
22:52:24: INFO: 3 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'
22:52:24: INFO: _ (done)
22:52:24: INFO: | |
22:52:24: INFO: __| | ___ _ __ ___
22:52:24: INFO: / _` |/ _ \| '_ \ / _ \
22:52:24: INFO: | (_| | (_) | | | | __/
22:52:24: INFO: \__,_|\___/|_| |_|\___|
22:52:24: INFO: {All Finished Successfully}
22:52:24: INFO: Overall to target 1.657 seconds (28.84 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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
22:52:27: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=patch0.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:27: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:27: INFO: Showing network mappings to allow debugging
22:52:28: INFO:
22:52:28: INFO: Trying to store 'patch0.xml' in string table
22:52:28: INFO: Looking for file 'patch0.xml'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML packet not formed correctly. Ran out of room looking for TAG}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML is not formatted correctly. Could not find closing />
}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
skeleton1911 said:
thanks. but thats not the problem of @Laptapper.
i think he is not on the latest build. because we have _a and _b system.
the latest build is on _b . also the root is only in _b
he could use cmd and adb in bootlader mode
fastboot set_active b
Setting current slot to 'b'...
but that will not work . the bootloader in the u pro is a bit strange. tested many things
Click to expand...
Click to collapse
Hello skeleton
Many thanks for your private chat support! I've tried a lot of things alone but only in case of your know-how to get a bricked phone working again.
I've got root now :highfive:
For me it's clear now that the problem was in my manually update of the full it's file. The phone has booted alone after the update and so I think it changed from image a to b.
I've done the update again and it has booted again.
Then I've removed all flashing software from Windows 10 and deleted old drivers. Complete clean up with registry clean with temp clean........
Then I've installed all of your tools again except python , here I took python 3 (by the way: we've talked about my short flashing time.....it was exactly short as before).
So may be also python could be the problem before but I guess it was the full ota.
Anyway ....for those who had problems like me try to flash the ota again (if before was done) or because better AND clean up all and then try again.
Many thanks again to the elephone u pro conqueror skeleton
Hopefully he will go further on with a full rom with twrp. And for this I've send him some dollars and I'll hope the other users will do it like me.
Laptapper said:
Hello skeleton
Many thanks for your private chat support! I've tried a lot of things alone but only in case of your know-how to get a bricked phone working again.
I've got root now :highfive:
For me it's clear now that the problem was in my manually update of the full it's file. The phone has booted alone after the update and so I think it changed from image a to b.
I've done the update again and it has booted again.
Then I've removed all flashing software from Windows 10 and deleted old drivers. Complete clean up with registry clean with temp clean........
Then I've installed all of your tools again except python , here I took python 3 (by the way: we've talked about my short flashing time.....it was exactly short as before).
So may be also python could be the problem before but I guess it was the full ota.
Anyway ....for those who had problems like me try to flash the ota again (if before was done) or because better AND clean up all and then try again.
Many thanks again to the elephone u pro conqueror skeleton
Hopefully he will go further on with a full rom with twrp. And for this I've send him some dollars and I'll hope the other users will do it like me.
Click to expand...
Click to collapse
Thank you very much i appreciate it
abbas said:
Thanks for your help. This is my log
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM:
rawprogram_unsparse.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: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Programmer Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
Process Index:0
Image Search Path: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Start Download
Program Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
22:52:17: Requested ID 13, file: "C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
22:52:18: 629284 bytes transferred in 0.313000 seconds (1.9174MBps)
22:52:18: File transferred successfully
22:52:18: 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
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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
22:52:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=rawprogram_unsparse.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:22: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:22: INFO: Showing network mappings to allow debugging
22:52:22: INFO:
22:52:22: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
22:52:22: INFO: Looking for file 'rawprogram_unsparse.xml'
22:52:22: INFO: User wants to talk to port '\\.\COM10'
22:52:22: INFO: Took 0.00000000 seconds to open port
22:52:22: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:52:22: INFO: If you don't want this, use --dontsorttags
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO:
Total to be tansferd with <program> or <read> is 47.79 MB
22:52:22: INFO: Sending <configure>
22:52:22: INFO: TARGET SAID: 'UFS DEVICE RESET'
22:52:22: INFO: TARGET SAID: 'Binary build date: Dec 8 2017 @ 13:33:11'
22:52:22: INFO: TARGET SAID: 'Chip serial num: 0 (0x0)'
22:52:22: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
22:52:22: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
22:52:22: INFO: In handleProgram('boot.img')
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO: =======================================================
22:52:22: INFO: {<program> FILE: 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'}
22:52:22: INFO: {<program> (47.79 MB) 97883 sectors needed at location 393216 on LUN 0}
22:52:22: INFO: =======================================================
22:52:23: INFO: TARGET SAID: 'start 393216, num 97883'
22:52:24: INFO: Overall to target 1.391 seconds (34.36 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: TARGET SAID: 'Finished programming start_sector 491099 and TotalSectorsToProgram 97883'
22:52:24: INFO:
22:52:24: INFO: =======================================================
22:52:24: INFO: ==================== {SUCCESS} ========================
22:52:24: INFO: =======================================================
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: ==============================================================
22:52:24: INFO: Files used and their paths
22:52:24: INFO: 1 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
22:52:24: INFO: 2 'C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml'
22:52:24: INFO: 3 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'
22:52:24: INFO: _ (done)
22:52:24: INFO: | |
22:52:24: INFO: __| | ___ _ __ ___
22:52:24: INFO: / _` |/ _ \| '_ \ / _ \
22:52:24: INFO: | (_| | (_) | | | | __/
22:52:24: INFO: \__,_|\___/|_| |_|\___|
22:52:24: INFO: {All Finished Successfully}
22:52:24: INFO: Overall to target 1.657 seconds (28.84 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
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
22:52:27: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=patch0.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:27: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:27: INFO: Showing network mappings to allow debugging
22:52:28: INFO:
22:52:28: INFO: Trying to store 'patch0.xml' in string table
22:52:28: INFO: Looking for file 'patch0.xml'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML packet not formed correctly. Ran out of room looking for TAG}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML is not formatted correctly. Could not find closing />
}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
Click to expand...
Click to collapse
Flash was fine.
look a post above . maybe thats also the solution for you
The root is good on my Upro, carved some space out on my Fat32 microSD to make Ext4 partition and it mounts with LinkSD Plus better then in Nougat where it was always little tricky. My next thing with Upro will be finding ways to extend the LTE bands, lots of threads on XDA about it to dig in.
https://drive.google.com/file/d/1MDw0itjMOznzbHDpRuHbOIFMPn0CVrXj/view?usp=sharing
skeleton1911 said:
Flash was fine.
look a post above . maybe thats also the solution for you
Click to expand...
Click to collapse
Finally done. I just reinstalled the OTA, installed Phyton 3.0.1 and voila, it is done. Thanks to everyone.
https://drive.google.com/file/d/1MDw0itjMOznzbHDpRuHbOIFMPn0CVrXj/view?usp=sharing[/QUOTE]
No Cache partition in Oreo? The storage shows the entire internal used for Cache.
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode.
To make sure this guide will work as expect, following requirements are needed:
- Know how to trigger the phone to EDL mode, and you can force reboot the phone (Required for Driver Changing)
- Qualcomm EDL mode doesn't require service authentication, or specially modded (e.g. Lumia Emergency Files)
- Firehose file for your SoC and storage type (eMMC or UFS storage)
- Latest Qualcomm USB Drivers (at least 2.1.2.0 or newer, you can check yourself in Device Manager) and QPST Tool
Driver version is pretty important. If older than 2.1.2.0, it won't support partition dumping properly.
You may need to reboot your Windows PC to Disable Driver Signature Enforcement mode to allow you use the driver.
I won't provide any download link of the proper drivers, please find yourself.
Click to expand...
Click to collapse
For non-Android Smartphones, HP Elite X3 (At least for prototype unit) is confirmed working with this method.
Most of Android Smartphones should work as well.
Step 1: Trigger the phone to EDL mode
Following methods can be used as reference:
- Connect your phone to PC with a specific key pressed
e.g. TCL / Alcatel / Blackberry Android Smartphones can use Volume Down key to trigger to EDL mode
- EDL cable (DIY or order it on eBay / AliExpress, keyword: Xiaomi EDL cable)
e.g. Smartisan Smartphones that made recently can use EDL cable to unlock the bootloader.
- Fastboot command
e.g. Few Xiaomi Phones
- Wire trick
If you know where's the test point / components (like resistant) on CLK pin of eMMC/UFS storage is connected as well, short it to the GND will trigger your phone to EDL mode.
This will be usable for almost every Qualcomm devices, once you have schematic provided by the manufacturer.
- Erase aboot / abl / xbl / UEFI from your phone
This method is dangerous, do it at your own risk!
Step 2: Change the Driver to Qualcomm HS-USB QDLoader 9008
Skip this step if it's already indicated as HS-USB QDLoader 9008 in Device Manager, "Ports (COM or LPT)" category.
If it's indicated as HS-USB Diagnostics 9008 in "Ports (COM or LPT)" category, or "QHSUSB__BULK" in "Universal Serial Bus devices" category, you must update the driver to Qualcomm HS-USB QDLoader 9008, then reboot your phone to Qualcomm EDL mode again to ensure the EDL port will not throttle.
To reboot your phone, you need to perform hard reboot until you see the port disappeared immediately or refresh (in case the phone is bricked).
Step 3: Open QFIL, load Firehose file
You must choose correct storage type in right down corner.
In many cases keep it as "emmc" for default, otherwise choose "ufs" for flagship devices. In this case we choose emmc.
Then choose "Flat Build" as Build Type, and select the firehose file for your phone. If there's no firehose file specifically for your device, you may want to choose another firehose file for the same SoC, same storage type for different phone.
For example, I used the "prog_emmc_firehose_8996_ddr.elf" for ZUK Z2 on HP Elite X3 and it works perfectly.
In many cases, you can obtain firehose file for your phone from stock firmware.
Click to expand...
Click to collapse
Step 4: Open Partition Manager
Now choose "Tools" - "Partition Manager", and please pay attention to the Status box.
When it indicates:
Code:
2019-07-18 20:04:19.775 20:04:19: Sahara protocol completed
2019-07-18 20:04:19.776 Sending Programmer Finished
2019-07-18 20:04:19.776 Switch To FireHose
2019-07-18 20:04:19.777 Wait for 3 seconds...
If you didn't see the output above, then the firehose file is incorrect or the EDL port is throttled. Reboot your phone to EDL mode again.
Then you've partially succeeded, just wait for the Partition Manager appears.
This is the partition table of your phone. Please take note on the Start LBA and LBA number of the last partition.
Take HP Elite X3 partition table for example, the last partition is "Data", it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors. Multiple the sector numbers with 512 will get the total bytes of the eMMC storage, in this case, the capacity of eMMC storage is 62,537,055,744 bytes.
You'll need the number 122,142,687 for later use.
If you don't want to dump userdata partition, just use the Start LBA value of userdata partition and convert it to decimal values - the overall dump will not contain actual userdata.
Don't close Partition Manager, we need to keep it for later use.
Now choose either Step 5A or 5B as your wish.
Step 5A: Dump the storage
Please copy following path to your File Explorer:
Code:
%AppData%\Qualcomm\QFIL
This will redirect you to C:\Users\[your_user_name]\AppData\Roaming\Qualcomm\QFIL .
Find the COMPORT_XX directory respective to your exact COM port - in this case, I choose COMPORT_8 for example.
And open a command prompt or PowerShell window here.
Execute following command here, remember to change the COM port number and num_sectors to your exact number, or the actual path of fh_loader.exe and your dump if possible:
Note, this command will not create the path of your dump for you, you must create yourself.
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\your\dump --convertprogram2read --sendimage=full_dump.bin --start_sector=0 --lun=0 --num_sectors=122142687 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Now just wait for dumping procedure complete.
Expected output should look like this:
Code:
20:45:50: INFO: Current working dir (cwd): C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\
20:45:50: INFO: Showing network mappings to allow debugging
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: User specified --num_sectors=524288 but file only has 524288 sectors. **Ignoring --num_sectors
20:45:50: INFO: User wants to talk to port '\\.\COM8'
20:45:50: INFO: Took 0.00000000 seconds to open port
20:45:50: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
20:45:50: INFO: If you don't want this, use --dontsorttags
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Couldn't find the file 'full_dump.bin', returning NULL
20:45:50: INFO: Sending <configure>
20:45:50: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
20:45:50: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
20:45:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
20:45:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
20:45:50: INFO: In handleRead('full_dump.bin')
20:45:50: INFO: Looking for file 'full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:50: WARNING: Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'full_dump.bin'
20:45:50: INFO: =======================================================
20:45:50: INFO: <read> (262144.0KB) 524288 sectors from location 0 FILE: 'full_dump.bin'
20:45:50: INFO: =======================================================
20:45:52: INFO: Overall to target 2.000 seconds (32.34 MBps)
20:45:54: INFO: Overall to target 4.000 seconds (32.38 MBps)
20:45:56: INFO: Overall to target 6.000 seconds (32.37 MBps)
20:45:58: INFO: Overall to target 7.844 seconds (32.64 MBps)
20:45:58: INFO: TARGET SAID: 'Finished reading from sector address 0 to 524288'
20:45:58: INFO: =======================================================
20:45:58: INFO: ===================== SUCCESS =========================
20:45:58: INFO: =======================================================
20:45:58: INFO: ==============================================================
20:45:58: INFO: Files used and their paths
20:45:58: INFO: 1 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
20:45:58: INFO: 2 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\full_dump.bin'
(_)
__ ____ _ _ __ _ __ _ _ __ __ _
\ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
\ V V / (_| | | | | | | | | | | (_| |
\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
__/ |
|___/
20:45:58: INFO: ==============================================================
20:45:58: INFO: NOTE: There were WARNINGS!! Repeated here, but please see log for more detail
Couldn't find the file 'full_dump.bin', returning NULL
User specified --num_sectors=524288 but file only has 524288 sectors. **Ignoring --num_sectors
Couldn't find the file 'full_dump.bin', returning NULL
Previous Filesize is 0 bytes. Therefore reading size of partition!! Please check 'full_dump.bin'
NOTE: There were WARNINGS!! Repeated above, but please see log for more detail
20:45:58: INFO: ==============================================================
20:45:58: INFO: _ (done)
20:45:58: INFO: | |
20:45:58: INFO: __| | ___ _ __ ___
20:45:58: INFO: / _` |/ _ \| '_ \ / _ \
20:45:58: INFO: | (_| | (_) | | | | __/
20:45:58: INFO: \__,_|\___/|_| |_|\___|
20:45:58: INFO: {All Finished Successfully}
20:45:58: INFO: Overall to target 7.969 seconds (32.12 MBps)
Writing log to 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt', might take a minute
Log is 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
You can use 7-Zip archiver to open this dump and extract any partition you want.
Step 5B: Write the dump back to storage
Open Partition Manager, and don't close it.
Please copy following path to your File Explorer:
Code:
%AppData%\Qualcomm\QFIL
This will redirect you to C:\Users\[your_user_name]\AppData\Roaming\Qualcomm\QFIL .
Find the COMPORT_XX directory respective to your exact COM port - in this case, I choose COMPORT_8 for example.
And open a command prompt or PowerShell window here.
Execute following command here, remember to change the COM port number and num_sectors to your exact number, or the actual path of fh_loader.exe and your dump if possible:
In this case, the dump is located at D:\path\to\your\dump\full_dump.bin .
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\your\dump --sendimage=full_dump.bin --start_sector=0 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Now just wait for the procedure complete.
The output should look like this:
Code:
20:05:30: INFO: Current working dir (cwd): C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\
20:05:30: INFO: Showing network mappings to allow debugging
20:05:30: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO: User wants to talk to port '\\.\COM8'
20:05:31: INFO: Took 0.01600000 seconds to open port
20:05:31: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
20:05:31: INFO: If you don't want this, use --dontsorttags
20:05:31: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO:
Total to be tansferd with <program> or <read> is 36.09 GB
20:05:31: INFO: Sending <configure>
20:05:31: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
20:05:31: INFO: TARGET SAID: 'Calling hotplug_poll_device('MMC')'
20:05:31: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
20:05:31: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
20:05:31: INFO: In handleProgram('full_dump.bin')
20:05:31: INFO: Looking for file 'full_dump.bin'
20:05:31: INFO: =======================================================
20:05:31: INFO: {<program> FILE: 'D:\path\to\your\dump\full_dump.bin'}
20:05:31: INFO: {<program> (36.09 GB) 75685888 sectors needed at location 0 on LUN 0}
20:05:31: INFO: =======================================================
20:05:31: INFO: TARGET SAID: 'start 0, num 75685888'
20:05:33: INFO: Overall to target 2.031 seconds (26.59 MBps)
20:05:33: INFO: {percent files transferred 0.15%}
20:05:35: INFO: Overall to target 4.063 seconds (26.34 MBps)
20:05:35: INFO: {percent files transferred 0.29%}
20:05:37: INFO: Overall to target 6.094 seconds (26.26 MBps)
20:05:37: INFO: {percent files transferred 0.43%}
20:05:39: INFO: Overall to target 8.110 seconds (26.26 MBps)
20:05:39: INFO: {percent files transferred 0.58%}
20:05:41: INFO: Overall to target 10.125 seconds (26.27 MBps)
20:05:41: INFO: {percent files transferred 0.72%}
20:05:43: INFO: Overall to target 12.141 seconds (26.27 MBps)
20:05:43: INFO: {percent files transferred 0.86%}
20:05:45: INFO: Overall to target 14.141 seconds (26.31 MBps)
20:05:45: INFO: {percent files transferred 1.01%}
20:05:47: INFO: Overall to target 16.156 seconds (26.49 MBps)
20:05:47: INFO: {percent files transferred 1.16%}
20:05:49: INFO: Overall to target 18.172 seconds (26.52 MBps)
20:05:49: INFO: {percent files transferred 1.30%}
20:05:51: INFO: Overall to target 20.188 seconds (26.55 MBps)
20:05:51: INFO: {percent files transferred 1.45%}
20:05:53: INFO: Overall to target 22.188 seconds (26.59 MBps)
20:05:53: INFO: {percent files transferred 1.60%}
20:05:55: INFO: Overall to target 24.188 seconds (26.62 MBps)
20:05:55: INFO: {percent files transferred 1.74%}
20:05:57: INFO: Overall to target 26.188 seconds (26.62 MBps)
20:05:57: INFO: {percent files transferred 1.89%}
20:05:59: INFO: Overall to target 28.188 seconds (26.61 MBps)
20:05:59: INFO: {percent files transferred 2.03%}
20:06:01: INFO: Overall to target 30.235 seconds (26.59 MBps)
20:06:01: INFO: {percent files transferred 2.18%}
20:06:03: INFO: Overall to target 32.266 seconds (26.56 MBps)
20:06:03: INFO: {percent files transferred 2.32%}
20:06:05: INFO: Overall to target 34.281 seconds (26.57 MBps)
20:06:05: INFO: {percent files transferred 2.47%}
20:06:07: INFO: Overall to target 36.328 seconds (26.56 MBps)
20:06:07: INFO: {percent files transferred 2.61%}
20:06:09: INFO: Overall to target 38.328 seconds (26.56 MBps)
20:06:09: INFO: {percent files transferred 2.75%}
20:06:11: INFO: Overall to target 40.360 seconds (26.56 MBps)
20:06:11: INFO: {percent files transferred 2.90%}
20:06:13: INFO: Overall to target 42.391 seconds (26.56 MBps)
20:06:13: INFO: {percent files transferred 3.05%}
(ignored too many logs)
20:28:17: INFO: Overall to target 1366.235 seconds (26.33 MBps)
20:28:17: INFO: {percent files transferred 97.33%}
20:28:19: INFO: Overall to target 1368.266 seconds (26.33 MBps)
20:28:19: INFO: {percent files transferred 97.48%}
20:28:21: INFO: Overall to target 1370.281 seconds (26.33 MBps)
20:28:21: INFO: {percent files transferred 97.63%}
20:28:23: INFO: Overall to target 1372.313 seconds (26.33 MBps)
20:28:23: INFO: {percent files transferred 97.78%}
20:28:25: INFO: Overall to target 1374.313 seconds (26.33 MBps)
20:28:25: INFO: {percent files transferred 97.93%}
20:28:27: INFO: Overall to target 1376.344 seconds (26.34 MBps)
20:28:27: INFO: {percent files transferred 98.08%}
20:28:29: INFO: Overall to target 1378.344 seconds (26.34 MBps)
20:28:29: INFO: {percent files transferred 98.22%}
20:28:31: INFO: Overall to target 1380.360 seconds (26.34 MBps)
20:28:31: INFO: {percent files transferred 98.37%}
20:28:33: INFO: Overall to target 1382.375 seconds (26.34 MBps)
20:28:33: INFO: {percent files transferred 98.51%}
20:28:35: INFO: Overall to target 1384.406 seconds (26.34 MBps)
20:28:35: INFO: {percent files transferred 98.66%}
20:28:37: INFO: Overall to target 1386.438 seconds (26.34 MBps)
20:28:37: INFO: {percent files transferred 98.80%}
20:28:39: INFO: Overall to target 1388.438 seconds (26.34 MBps)
20:28:39: INFO: {percent files transferred 98.94%}
20:28:41: INFO: Overall to target 1390.453 seconds (26.34 MBps)
20:28:41: INFO: {percent files transferred 99.09%}
20:28:43: INFO: Overall to target 1392.485 seconds (26.34 MBps)
20:28:43: INFO: {percent files transferred 99.25%}
20:28:45: INFO: Overall to target 1394.516 seconds (26.34 MBps)
20:28:45: INFO: {percent files transferred 99.40%}
20:28:47: INFO: Overall to target 1396.531 seconds (26.34 MBps)
20:28:47: INFO: {percent files transferred 99.55%}
20:28:49: INFO: Overall to target 1398.750 seconds (26.33 MBps)
20:28:49: INFO: {percent files transferred 99.66%}
20:28:51: INFO: Overall to target 1400.766 seconds (26.33 MBps)
20:28:51: INFO: {percent files transferred 99.81%}
20:28:53: INFO: Overall to target 1402.797 seconds (26.33 MBps)
20:28:53: INFO: {percent files transferred 99.96%}
20:28:54: INFO: Overall to target 1403.422 seconds (26.33 MBps)
20:28:54: INFO: {percent files transferred 100.00%}
20:28:54: INFO: TARGET SAID: 'Finished programming start_sector 75685888 and TotalSectorsToProgram 75685888'
20:28:54: INFO:
20:28:54: INFO: =======================================================
20:28:54: INFO: ==================== {SUCCESS} ========================
20:28:54: INFO: =======================================================
20:28:54: INFO: {percent files transferred 100.00%}
20:28:54: INFO: ==============================================================
20:28:54: INFO: Files used and their paths
20:28:54: INFO: 1 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
20:28:54: INFO: 2 'D:\path\to\your\dump\full_dump.bin'
20:28:54: INFO: _ (done)
20:28:54: INFO: | |
20:28:54: INFO: __| | ___ _ __ ___
20:28:54: INFO: / _` |/ _ \| '_ \ / _ \
20:28:54: INFO: | (_| | (_) | | | | __/
20:28:54: INFO: \__,_|\___/|_| |_|\___|
20:28:54: INFO: {All Finished Successfully}
20:28:54: INFO: Overall to target 1403.578 seconds (26.33 MBps)
20:28:54: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt', might take a minute
Log is 'C:\Users\HikariCal\AppData\Roaming\Qualcomm\QFIL\COMPORT_8\port_trace.txt'
If you only want to write back only one specific partition, you need to specify the start_sector value to the decimal value of a partition's Start LBA.
Always keep the Partition Manager window opened!
Step 6: Quit Partition Manager
After everything dumped, you can close Partition Manager, the QFIL will reboot your phone back to EDL mode or reboot your phone back to normal mode.
Then you can force reboot your phone or mess up your phone as you want.
reserved
Awesome Guide!
Qualcomm HS-USB QD loader 9008 drivers showing briefly in device manager
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.
user agent said:
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.
Click to expand...
Click to collapse
I remember Galaxy Note 3 can remove the battery right?
In may cases, Qualcomm based phone can stay at EDL mode without battery.
the partitiion maneger do not appear
Hey, Thank you so much for prividing this GUIDE!
I just try to maake a backup of my data. I followed the steps above but the partition manager do not appear. Anyone know what is the problem? Log see below. Thank you for any coming tipps!
2020-04-19 23:31:12.778 Validating Application Configuration
2020-04-19 23:31:12.790 Load APP Configuration
2020-04-19 23:31:12.810 COM:12
2020-04-19 23:31:12.810 PBLDOWNLOADPROTOCOL:0
2020-04-19 23:31:12.810 PROGRAMMER:True
2020-04-19 23:31:12.810 PROGRAMMER:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:31:12.810 RESETSAHARASTATEMACHINE:False
2020-04-19 23:31:12.810 SAHARAREADSERIALNO:False
2020-04-19 23:31:12.810 SEARCHPATH:\Firefox_download\01\images
2020-04-19 23:31:12.810 ACKRAWDATAEVERYNUMPACKETS:False
2020-04-19 23:31:12.810 ACKRAWDATAEVERYNUMPACKETS:100
2020-04-19 23:31:12.810 MAXPAYLOADSIZETOTARGETINBYTES:False
2020-04-19 23:31:12.810 MAXPAYLOADSIZETOTARGETINBYTES:49152
2020-04-19 23:31:12.810 DEVICETYPE:ufs
2020-04-19 23:31:12.810 PLATFORM:8x26
2020-04-19 23:31:12.810 VALIDATIONMODE:0
2020-04-19 23:31:12.811 RESETAFTERDOWNLOAD:False
2020-04-19 23:31:12.811 MAXDIGESTTABLESIZE:8192
2020-04-19 23:31:12.811 SWITCHTOFIREHOSETIMEOUT:30
2020-04-19 23:31:12.811 RESETTIMEOUT:200
2020-04-19 23:31:12.811 RESETDELAYTIME:2
2020-04-19 23:31:12.811 METABUILD:
2020-04-19 23:31:12.811 METABUILD:
2020-04-19 23:31:12.811 FLATBUILDPATH:C:\
2020-04-19 23:31:12.811 FLATBUILDFORCEOVERRIDE:True
2020-04-19 23:31:12.811 QCNPATH:C:\Temp\00000000.qcn
2020-04-19 23:31:12.811 QCNAUTOBACKUPRESTORE:False
2020-04-19 23:31:12.811 SPCCODE:000000
2020-04-19 23:31:12.811 ENABLEMULTISIM:False
2020-04-19 23:31:12.811 AUTOPRESERVEPARTITIONS:False
2020-04-19 23:31:12.811 PARTITIONPRESERVEMODE:0
2020-04-19 23:31:12.811 PRESERVEDPARTITIONS:0
2020-04-19 23:31:12.811 PRESERVEDPARTITIONS:
2020-04-19 23:31:12.811 ERASEALL:False
2020-04-19 23:31:12.812 Load ARG Configuration
2020-04-19 23:31:12.888 Validating Download Configuration
2020-04-19 23:31:12.890 Image Search Path: D:\Firefox_download\01\images
2020-04-19 23:31:12.895 Programmer Path:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:31:13.548 Process Index:0
2020-04-19 23:31:13.567 Qualcomm Flash Image Loader (QFIL) 2.0.2.3
2020-04-19 23:32:56.567 Start Download
2020-04-19 23:32:56.588 Program Path:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:32:56.593 ***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:32:57.013 Binary build date: Apr 27 2018 @ 03:04:33
2020-04-19 23:32:57.015 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\QUALCOMM\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:32:57.018 Sahara mappings:
2020-04-19 23:32:57.020 2: amss.mbn
2020-04-19 23:32:57.020 6: apps.mbn
2020-04-19 23:32:57.021 8: dsp1.mbn
2020-04-19 23:32:57.022 10: dbl.mbn
2020-04-19 23:32:57.022 11: osbl.mbn
2020-04-19 23:32:57.023 12: dsp2.mbn
2020-04-19 23:32:57.023 16: efs1.mbn
2020-04-19 23:32:57.024 17: efs2.mbn
2020-04-19 23:32:57.024 20: efs3.mbn
2020-04-19 23:32:57.025 21: sbl1.mbn
2020-04-19 23:32:57.025 22: sbl2.mbn
2020-04-19 23:32:57.026 23: rpm.mbn
2020-04-19 23:32:57.027 25: tz.mbn
2020-04-19 23:32:57.027 28: dsp3.mbn
2020-04-19 23:32:57.028 29: acdb.mbn
2020-04-19 23:32:57.030 30: wdt.mbn
2020-04-19 23:32:57.031 31: mba.mbn
2020-04-19 23:32:57.032 13: D:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf
2020-04-19 23:32:57.032
2020-04-19 23:32:57.033 23:32:56: Requested ID 13, file: "D:\Firefox_download\01\images\prog_ufs_firehose_sdm845_ddr.elf"
2020-04-19 23:32:57.033
2020-04-19 23:32:57.034 23:32:57: 715496 bytes transferred in 0.391000 seconds (1.7451MBps)
2020-04-19 23:32:57.034
2020-04-19 23:32:57.035
2020-04-19 23:32:57.035
2020-04-19 23:32:57.036 23:32:57: File transferred successfully
2020-04-19 23:32:57.036
2020-04-19 23:32:57.036
2020-04-19 23:32:57.037
2020-04-19 23:32:57.038 23:32:57: Sahara protocol completed
2020-04-19 23:32:57.038 Sending Programmer Finished
2020-04-19 23:32:57.039 Switch To FireHose
2020-04-19 23:32:57.039 Wait for 3 seconds...
2020-04-19 23:33:00.041 Max Payload Size to Target:49152 Bytes
2020-04-19 23:33:00.041 Device Type:ufs
2020-04-19 23:33:00.042 Platform:8x26
2020-04-19 23:33:00.043 Disable Ack Raw Data Every N Packets
2020-04-19 23:33:00.044 Skip Write:False
2020-04-19 23:33:00.044 Always Validate:False
2020-04-19 23:33:00.045 Use Verbose:False
2020-04-19 23:33:00.050 ***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12
2020-04-19 23:33:00.124
2020-04-19 23:33:00.126 Base Version: 18.02.16.18.26
2020-04-19 23:33:00.131 Binary build date: Apr 27 2018 @ 03:04:29
2020-04-19 23:33:00.131 Incremental Build version: 18.04.27.03.04.29
2020-04-19 23:33:00.138
2020-04-19 23:33:00.138 23:33:00: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2020-04-19 23:33:00.139 ************************************************
2020-04-19 23:33:00.140 C:\Program Files (x86)\QUALCOMM\QPST\bin\fh_loader.exe --port=\\.\COM12 --search_path=C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12 --convertprogram2read --sendimage=fh_gpt_header_0 --start_sector=1 --lun=0 --num_sectors=1 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
2020-04-19 23:33:00.142 ************************************************
2020-04-19 23:33:00.142
2020-04-19 23:33:00.143 23:33:00: INFO: Current working dir (cwd): C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\
2020-04-19 23:33:00.144 23:33:00: INFO: Showing network mappings to allow debugging
2020-04-19 23:33:00.145 23:33:00: INFO: Looking for file 'fh_gpt_header_0'
2020-04-19 23:33:00.147
2020-04-19 23:33:00.147
2020-04-19 23:33:00.148 (_)
2020-04-19 23:33:00.149 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.150 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.151 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.151 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.152 __/ |
2020-04-19 23:33:00.153 |___/
2020-04-19 23:33:00.153
2020-04-19 23:33:00.154
2020-04-19 23:33:00.154 23:33:00: WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL
2020-04-19 23:33:00.156
2020-04-19 23:33:00.156
2020-04-19 23:33:00.157 (_)
2020-04-19 23:33:00.158 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.158 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.159 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.160 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.160 __/ |
2020-04-19 23:33:00.161 |___/
2020-04-19 23:33:00.161
2020-04-19 23:33:00.162
2020-04-19 23:33:00.163 23:33:00: WARNING: User specified --num_sectors=1 but file only has 1 sectors. **Ignoring --num_sectors
2020-04-19 23:33:00.163
2020-04-19 23:33:00.164
2020-04-19 23:33:00.164 23:33:00: INFO: User wants to talk to port '\\.\COM12'
2020-04-19 23:33:00.165 23:33:00: INFO: Took 0.01500000 seconds to open port
2020-04-19 23:33:00.166 23:33:00: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
2020-04-19 23:33:00.167 23:33:00: INFO: If you don't want this, use --dontsorttags
2020-04-19 23:33:00.167
2020-04-19 23:33:00.168 23:33:00: INFO: Looking for file 'fh_gpt_header_0'
2020-04-19 23:33:00.171
2020-04-19 23:33:00.172
2020-04-19 23:33:00.172 (_)
2020-04-19 23:33:00.173 __ ____ _ _ __ _ __ _ _ __ __ _
2020-04-19 23:33:00.174 \ \ /\ / / _` | '__| '_ \| | '_ \ / _` |
2020-04-19 23:33:00.174 \ V V / (_| | | | | | | | | | | (_| |
2020-04-19 23:33:00.175 \_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |
2020-04-19 23:33:00.176 __/ |
2020-04-19 23:33:00.177 |___/
2020-04-19 23:33:00.178
2020-04-19 23:33:00.179
2020-04-19 23:33:00.179 23:33:00: WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL
2020-04-19 23:33:00.180 23:33:00: INFO: Sending <configure>
2020-04-19 23:33:00.181
2020-04-19 23:33:00.181 23:33:00: INFO: TARGET SAID: 'INFO: Binary build date: Dec 27 2019 @ 18:17:54'
2020-04-19 23:33:00.182
2020-04-19 23:33:00.182 23:33:00: INFO: TARGET SAID: 'INFO: Binary build date: Dec 27 2019 @ 18:17:54
2020-04-19 23:33:00.183 '
2020-04-19 23:33:00.184
2020-04-19 23:33:00.184 23:33:00: INFO: TARGET SAID: 'INFO: Chip serial num: 2650911984 (0x9e01b4f0)'
2020-04-19 23:33:00.185
2020-04-19 23:33:00.186 23:33:00: INFO: TARGET SAID: 'INFO: Supported Functions (14):'
2020-04-19 23:33:00.187
2020-04-19 23:33:00.188 23:33:00: INFO: TARGET SAID: 'INFO: program'
2020-04-19 23:33:00.188
2020-04-19 23:33:00.189 23:33:00: INFO: TARGET SAID: 'INFO: read'
2020-04-19 23:33:00.190
2020-04-19 23:33:00.190 23:33:00: INFO: TARGET SAID: 'INFO: nop'
2020-04-19 23:33:00.191
2020-04-19 23:33:00.191 23:33:00: INFO: TARGET SAID: 'INFO: patch'
2020-04-19 23:33:00.192
2020-04-19 23:33:00.192 23:33:00: INFO: TARGET SAID: 'INFO: configure'
2020-04-19 23:33:00.193
2020-04-19 23:33:00.194 23:33:00: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
2020-04-19 23:33:00.194
2020-04-19 23:33:00.195 23:33:00: INFO: TARGET SAID: 'INFO: erase'
2020-04-19 23:33:00.196
2020-04-19 23:33:00.196 23:33:00: INFO: TARGET SAID: 'INFO: power'
2020-04-19 23:33:00.197
2020-04-19 23:33:00.198 23:33:00: INFO: TARGET SAID: 'INFO: firmwarewrite'
2020-04-19 23:33:00.198
2020-04-19 23:33:00.199 23:33:00: INFO: TARGET SAID: 'INFO: getstorageinfo'
2020-04-19 23:33:00.199
2020-04-19 23:33:00.200 23:33:00: INFO: TARGET SAID: 'INFO: benchmark'
2020-04-19 23:33:00.201
2020-04-19 23:33:00.201 23:33:00: INFO: TARGET SAID: 'INFO: emmc'
2020-04-19 23:33:00.202
2020-04-19 23:33:00.202 23:33:00: INFO: TARGET SAID: 'INFO: ufs'
2020-04-19 23:33:00.203
2020-04-19 23:33:00.203 23:33:00: INFO: TARGET SAID: 'INFO: fixgpt'
2020-04-19 23:33:00.204
2020-04-19 23:33:00.205 23:33:00: INFO: TARGET SAID: 'INFO: End of supported functions 14'
2020-04-19 23:33:00.205
2020-04-19 23:33:00.207 23:33:00: INFO: TARGET SAID: 'ERROR: Only nop and sig tag can be recevied before authentication.'
2020-04-19 23:33:00.208 23:33:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
2020-04-19 23:33:00.210 23:33:00: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2020-04-19 23:33:00.211 23:33:00: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
2020-04-19 23:33:00.211
2020-04-19 23:33:00.212 Writing log to 'C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\port_trace.txt', might take a minute
2020-04-19 23:33:00.213
2020-04-19 23:33:00.213
2020-04-19 23:33:00.214 Log is 'C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_12\port_trace.txt'
2020-04-19 23:33:00.215
2020-04-19 23:33:00.215 Download Fail:FireHose Fail:FHLoader Fail:FHLoader Failrocess fail
2020-04-19 23:33:00.225 Finish Get GPT
the other Log is attached here.
View attachment port_trace.txt
Excuse me, do you happen to have any official documentation on EDL?
Sorry for the slight offtopic.
Phone stuck in EDL Mode
Hello hikari, my device Nokia 4.2 (TA-1152) is stuck in EDL MODE after dumping the boot image file.
Can you please help me to exit from EDL mode?
Hi! even with another firehose, Crosscall Core-X3 won't accept entering Sahara mode. wrong 'pkhash'.
Recovery show HS8917QC, modem show 8937. I tried many of each without success. I don't know which one is relevant.
[ro.product.device]: [HS8917QC]
[ro.hmct.modem.version]: [MSM8937.LA.3.0.1-00490-STD.PROD-1]
[ro.fota.oem]: [hisense8917_8.1]
[ro.fota.platform]: [MSM8917_8.1]
[ro.bootimage.build.fingerprint]: [CROSSCALL/L750/HS8917QC:8.1.0....]
[gsm.version.baseband]: [MPSS.JO.3.0-00464-8937_GENNS_PACK-1]
[gsm.version.baseband1]: [MPSS.JO.3.0-00464-8937_GENNS_PACK-1]
fastboot getvar all : https://pastebin.com/pmPDpeJ8
Of course no firehose neither full image is available for this exotic device.
Bless you.
Thank you for providing the instructions!
I'd like to extract LeEco Le Max 2 (X820) but QFIL won't bring me the Partition Table.
Device recognized as "Qualcomm HS-USB QDLoader 9008 (COM12)" in Device Manager.
QFIL tells me 10:52:37: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
(Log attached.)
I used "prog_emmc_firehose_8996_ddr.elf" because I didn't find a firehose for X820. May this error be caused by a wrong firehose file? If yes, is it safe to have a try with one of the firmware image files without bricking the device or destroying data?
Length Name
------ ----
16777216 adspso.bin
405504 BTFM.bin
201304 cmnlib.mbn
256008 cmnlib64.mbn
1048576 ddr.mbn
39976 devcfg.mbn
296 devinfo.bin
793040 emmc_appsboot.mbn
264120 hyp.mbn
226008 keymaster.mbn
85004288 NON-HLOS.bin
42728 pmic.elf
229540 rpm.mbn
1634304 tz.mbn
1836136 xbl.elf
Or is it more likely that this model just doesn't respond?
Anyone ever tried this on an ROG phone 2?
Step 3: Open QFIL, load Firehose file
Hello everyone. I have nokia 1.4 TA-1322. I have downloaded several firmwares from the different websites but the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
hikari_calyx said:
This is the partition table of your phone. Please take note on the Start LBA and LBA number of the last partition.
Take HP Elite X3 partition table for example, the last partition is "Data", it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors. Multiple the sector numbers with 512 will get the total bytes of the eMMC storage, in this case, the capacity of eMMC storage is 62,537,055,744 bytes.
Click to expand...
Click to collapse
Hello, my partitions on my phone are wildly different compared to these. The userdata partition says it's only about 3,933,729,792 bytes. It's a 32GB phone, any reasons why it's so tiny?
Thanks for taking time to write all this out and help out a lot of people. Everything made sense until I got to
"it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors"
I don't think this is common knowledge. Could you please explain or just point me in the right direction to understand how adding 0x01E20000 and 0x0565BFDF resulted in 0x0747BFDF, and how we translate that string of characters into 122,142,687?
Thank you!
Hello everyone. I have a bricked Asus Zenfone 8 and I'm trying to recover userdata partitiion from it using 9008 mode. I have correct Firehose file and everything should work fine. I've easily recovered data from system partition using this manual, but I have problem with userdata. This partition is huge, around 230 GB, and phone just disconnects from PC in the middle of the process. First time it downloaded 98GB, second time - 60GB, so I don't think this is because of broken flash memory or smth. What can be a reason of this problem and how to solve that? Thanks for any reply!
Cirrus9 said:
Thanks for taking time to write all this out and help out a lot of people. Everything made sense until I got to
"it's Start LBA and LBA number are 0x01E20000 and 0x0565BFDF. Add both of them will get the total sector numbers of whole eMMC storage - in this case, 0x0747BFDF, or 122,142,687 sectors"
I don't think this is common knowledge. Could you please explain or just point me in the right direction to understand how adding 0x01E20000 and 0x0565BFDF resulted in 0x0747BFDF, and how we translate that string of characters into 122,142,687?
Thank you!
Click to expand...
Click to collapse
Hi. This string of characters is hexadecimal numeral system. You can use standart Windows calculator in programmer mode to convert these numbers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you! Learned something new today!
Hi! This guide is great. I have an issue with the firehose file where I found the right firehose file from my device using firehose finder on GitHub. However, that file is in .bin format instead of .elf. How can I convert it, and is that safe?
kjullian19 said:
However, that file is in .bin format instead of .elf. How can I convert it, and is that safe?
Click to expand...
Click to collapse
Firehose loaders are technically ELF 32 or 64 bit files but may be named elf, bin, img, mbn, whatever.
Use a hex editor and look at the start of the file.
It should be 7f 45 4c 46
Or use my elfview.exe (in the sig) to check it out.
Or use my qcomview.exe (in the sig) to check it out.
Code:
C:\>elfview /p motog.bin
# Type Flags Size Offset Address
-- ------- ----- ------- ------ --------
0 null 7 1016 000000 00000000
1 null 2.2 7384 001000 4602c000
2 load RWZ 0 06b4b0 0c100000
3 load RX 7772 0549f0 0c119000
4 load RWZ 0 056850 0c11c000
5 load RWZ 0 06b4b0 0c11e000
6 load RWZ 0 0549f0 0c219000
7 load RX 301376 003000 0c225000
8 load RWZ 0 04c940 0c276c00
9 load RW 32932 04c940 0c279c00
10 load RWZ 0 0549f0 0c286c00
11 load RWX 85080 056850 0c29b000
12 load 1RWX 84 06b4b0 0c2c9000
13 load 1RWX 29168 06b504 0c2c9054
14 load 1RWX 1496 0726f4 0c2d0244
15 load 5RX 139264 072ccc 0c350000
16 load RWZ 0 0549f0 45e11000
C:\>qcomview /h motog.bin
64 bit ELF, Version 6, SHA384
0 00000000 000003f8 a3836cd6c3e2dbed 5dd00c97349c8598 92a5051c08ae65d4 171ba1ece407a7b2 1cdf27a97ff437c7 0488bb944956fbc2 Ok
1 00001000 00001cd8
2 0006b4b0 00000000
3 000549f0 00001e5c 3972d9e5346b52cc e71c31a437500b8f 57f2fc8124e97cd5 b2f70a4829e98196 03d89d4b946261e2 9b2a58949b92b7dc Ok
4 00056850 00000000
5 0006b4b0 00000000
6 000549f0 00000000
7 00003000 00049940 503b424c75f6d657 e4363c830deeebee afe0ac82ce04dfec e8ac03fb47b129a3 fc221acc0d515b22 ed17d86b0f6b585c Ok
8 0004c940 00000000
9 0004c940 000080a4 2f7aec3605fbce70 ec0c83a703435845 e969988f390787d7 aa8d0a13a6d9e06f ee2af4e9b86b8a75 fc81fbe1017d1c64 Ok
10 000549f0 00000000
11 00056850 00014c58 fec3a6b9f6d71a18 aadd3f722fc73bea d3197c24c397d55d 4f3d4a9c25661db1 152c60664fcbe4a6 c2441120afc4b3c9 Ok
12 0006b4b0 00000054 db139c6f70d88269 a61cb1a7be2ce363 55faf1ff1c3b9c3d 27cd8d65bef7f710 9bc83c6255ea8104 6d7ac582cc778f15 Ok
13 0006b504 000071f0 a27a7dc0040a1bfa 8e24e4a42bead90e ae10a91c37d19105 bce9da69383004ea c933b87ac4a88653 ccbb4a6b1407d15d Ok
14 000726f4 000005d8 8dcaae787361a3c4 3bad6d344641d061 35170b5a30607e20 a30cd23884bbc0b0 790681aa36a1fe60 98501a103b62088a Ok
15 00072ccc 00022000 1f939df47e7fae80 2c127e10474ff9e6 2faecd5fab873bf8 928cab0a5ef28261 5d4b19cc57cca817 37fa9fad42971c40 Ok
16 000549f0 00000000
Thanks Renate. I'm new to this stuff, so you might have to ELI5, I'm not seeing 7f 45 4c 46 in your log.
Ultimately, I need to learn how to convert the binary file into a compatible .elf file. Will either elfview or qcomview do that?
Thanks again and sorry for the dumb questions
I bought a Lenovo Legion Y700 a few weeks ago. Is a global rom without gaming features and this makes me very regretful. Legion gaming, Legion Assistant and Floating display button is what I need. So I tried to download stock firmware : TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst.zip(Others firmware zip same).
But keep getting problems like Download Fail: FireHose Fail: FHLoader Fail: Process fail. I have tried many versions of QPST and QFIL. None of them work.
Current phone is Lenovo version 13.0.586 ST but not ZUI version. Some items in the phone setting are missing too.
My main solution is to have gaming features.
Is this firmware for gaming features? Can I separately download these gaming features?
Edit*: I think my attach file not showing up.
This is QFIL log
----------------------------------------------------------------------------------------------------------------------------------------------------
Validating Application Configuration
Load APP Configuration
COM:4
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
SEARCHPATH:C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM:
rawprogram_unsparse0.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
METABUILD:C:\Users\zeras\OneDrive\Desktop\TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst\contents.xml
METABUILD:asic
METABUILDPROGRAMMER:C:\Users\zeras\OneDrive\Desktop\TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst\prog_firehose_ddr.elf
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: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
Invalid Device Type emmc, Ignored
Meta Build Content XML Path: C:\Users\zeras\OneDrive\Desktop\TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst\contents.xml
Process Index:0
Image Search Path: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Image Search Path: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
***** Working Folder:C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
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\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
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 Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
02:12:43: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf"
02:12:43: 708116 bytes transferred in 0.156000 seconds (4.3289MBps)
02:12:43: File transferred successfully
02:12:43: 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
***** Working Folder:C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
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
02:12:46: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram_unsparse0.xml --search_path=C:\Program Files (x86)\Qualcomm\QPST\bin --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
02:12:46: INFO: Current working dir (cwd): C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\
02:12:46: INFO: Showing network mappings to allow debugging
02:12:46: INFO:
02:12:46: INFO: Trying to store 'rawprogram_unsparse0.xml' in string table
02:12:46: INFO: Looking for file 'rawprogram_unsparse0.xml'
02:12:46: INFO: User wants to talk to port '\\.\COM4'
02:12:46: INFO: Took 0.00000000 seconds to open port
02:12:46: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
02:12:46: INFO: If you don't want this, use --dontsorttags
02:12:46: INFO: Looking for file 'recovery.img'
02:12:46: INFO: SectorSizeInBytes changed to 4096
02:12:46: INFO: Looking for file 'vbmeta_system.img'
02:12:46: INFO: Looking for file 'metadata.img'
02:12:46: INFO: Looking for file 'super_1.img'
02:12:46: INFO: Looking for file 'super_2.img'
02:12:46: INFO: Looking for file 'super_3.img'
02:12:47: INFO: Looking for file 'super_4.img'
02:12:47: INFO: Looking for file 'super_5.img'
02:12:47: INFO: Looking for file 'userdata_1.img'
02:12:47: INFO: Looking for file 'userdata_2.img'
02:12:47: INFO: Looking for file 'userdata_3.img'
02:12:47: INFO: Looking for file 'userdata_4.img'
02:12:47: INFO: Looking for file 'userdata_5.img'
02:12:47: INFO: Looking for file 'userdata_6.img'
02:12:47: INFO: Looking for file 'userdata_7.img'
02:12:47: INFO: Looking for file 'userdata_8.img'
02:12:47: INFO: Looking for file 'userdata_9.img'
02:12:47: INFO: Looking for file 'userdata_10.img'
02:12:47: INFO: Looking for file 'gpt_main0.bin'
02:12:47: INFO: Looking for file 'gpt_backup0.bin'
02:12:47: INFO:
Total to be tansferd with <program> or <read> is 5.21 GB
02:12:47: INFO: Sending <configure>
02:12:47: INFO: TARGET SAID: 'INFO: Binary build date: Feb 22 2022 @ 11:58:16'
02:12:47: INFO: TARGET SAID: 'INFO: Binary build date: Feb 22 2022 @ 11:58:16
'
02:12:47: INFO: TARGET SAID: 'INFO: Chip serial num: 853016817 (0x32d800f1)'
02:12:47: INFO: TARGET SAID: 'INFO: Supported Functions (15):'
02:12:47: INFO: TARGET SAID: 'INFO: program'
02:12:47: INFO: TARGET SAID: 'INFO: read'
02:12:47: INFO: TARGET SAID: 'INFO: nop'
02:12:47: INFO: TARGET SAID: 'INFO: patch'
02:12:47: INFO: TARGET SAID: 'INFO: configure'
02:12:47: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
02:12:47: INFO: TARGET SAID: 'INFO: erase'
02:12:47: INFO: TARGET SAID: 'INFO: power'
02:12:47: INFO: TARGET SAID: 'INFO: firmwarewrite'
02:12:47: INFO: TARGET SAID: 'INFO: getstorageinfo'
02:12:47: INFO: TARGET SAID: 'INFO: benchmark'
02:12:47: INFO: TARGET SAID: 'INFO: emmc'
02:12:47: INFO: TARGET SAID: 'INFO: ufs'
02:12:47: INFO: TARGET SAID: 'INFO: fixgpt'
02:12:47: INFO: TARGET SAID: 'INFO: getsha256digest'
02:12:47: INFO: TARGET SAID: 'INFO: End of supported functions 15'
02:12:47: INFO: TARGET SAID: 'INFO: Calling handler for configure'
02:12:47: INFO: TARGET SAID: 'INFO: Storage type set to value eMMC'
02:12:47: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
02:12:47: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
02:12:47: INFO: In handleProgram('recovery.img')
02:12:47: INFO: Looking for file 'recovery.img'
02:12:47: INFO: =======================================================
02:12:47: INFO: {<program> FILE: 'C:\Program Files (x86)\Qualcomm\QPST\bin\recovery.img'}
02:12:47: INFO: {<program> (100.00 MB) 25600 sectors needed at location 64264 on LUN 0}
02:12:47: INFO: =======================================================
02:12:47: INFO: TARGET SAID: 'INFO: Calling handler for program'
02:12:47: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 1 partition 0'
02:12:47: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:1 partition:0 error:0'
02:12:47: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 344493556'
02:12:47: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:1, lun:0 error:3'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
02:12:47: {ERROR: program FAILED - Please see log}
Writing log to 'C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
ZERASIAN said:
I bought a Lenovo Legion Y700 a few weeks ago. Is a global rom without gaming features and this makes me very regretful. Legion gaming, Legion Assistant and Floating display button is what I need. So I tried to download stock firmware : TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst.zip(Others firmware zip same).
But keep getting problems like Download Fail: FireHose Fail: FHLoader Fail: Process fail. I have tried many versions of QPST and QFIL. None of them work.
Current phone is Lenovo version 13.0.586 ST but not ZUI version. Some items in the phone setting are missing too.
My main solution is to have gaming features.
Is this firmware for gaming features? Can I separately download these gaming features?
Edit*: I think my attach file not showing up.
This is QFIL log
----------------------------------------------------------------------------------------------------------------------------------------------------
Validating Application Configuration
Load APP Configuration
COM:4
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
SEARCHPATH:C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM:
rawprogram_unsparse0.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
METABUILD:C:\Users\zeras\OneDrive\Desktop\TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst\contents.xml
METABUILD:asic
METABUILDPROGRAMMER:C:\Users\zeras\OneDrive\Desktop\TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst\prog_firehose_ddr.elf
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: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
Invalid Device Type emmc, Ignored
Meta Build Content XML Path: C:\Users\zeras\OneDrive\Desktop\TB-9707F_CN_OPEN_USER_Q00235.1_R_ZUI_13.0.586_ST_220222_qpst\contents.xml
Process Index:0
Image Search Path: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Image Search Path: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse0.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
***** Working Folder:C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
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\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
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 Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf
02:12:43: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_firehose_ddr.elf"
02:12:43: 708116 bytes transferred in 0.156000 seconds (4.3289MBps)
02:12:43: File transferred successfully
02:12:43: 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
***** Working Folder:C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
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
02:12:46: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram_unsparse0.xml --search_path=C:\Program Files (x86)\Qualcomm\QPST\bin --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
02:12:46: INFO: Current working dir (cwd): C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\
02:12:46: INFO: Showing network mappings to allow debugging
02:12:46: INFO:
02:12:46: INFO: Trying to store 'rawprogram_unsparse0.xml' in string table
02:12:46: INFO: Looking for file 'rawprogram_unsparse0.xml'
02:12:46: INFO: User wants to talk to port '\\.\COM4'
02:12:46: INFO: Took 0.00000000 seconds to open port
02:12:46: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
02:12:46: INFO: If you don't want this, use --dontsorttags
02:12:46: INFO: Looking for file 'recovery.img'
02:12:46: INFO: SectorSizeInBytes changed to 4096
02:12:46: INFO: Looking for file 'vbmeta_system.img'
02:12:46: INFO: Looking for file 'metadata.img'
02:12:46: INFO: Looking for file 'super_1.img'
02:12:46: INFO: Looking for file 'super_2.img'
02:12:46: INFO: Looking for file 'super_3.img'
02:12:47: INFO: Looking for file 'super_4.img'
02:12:47: INFO: Looking for file 'super_5.img'
02:12:47: INFO: Looking for file 'userdata_1.img'
02:12:47: INFO: Looking for file 'userdata_2.img'
02:12:47: INFO: Looking for file 'userdata_3.img'
02:12:47: INFO: Looking for file 'userdata_4.img'
02:12:47: INFO: Looking for file 'userdata_5.img'
02:12:47: INFO: Looking for file 'userdata_6.img'
02:12:47: INFO: Looking for file 'userdata_7.img'
02:12:47: INFO: Looking for file 'userdata_8.img'
02:12:47: INFO: Looking for file 'userdata_9.img'
02:12:47: INFO: Looking for file 'userdata_10.img'
02:12:47: INFO: Looking for file 'gpt_main0.bin'
02:12:47: INFO: Looking for file 'gpt_backup0.bin'
02:12:47: INFO:
Total to be tansferd with <program> or <read> is 5.21 GB
02:12:47: INFO: Sending <configure>
02:12:47: INFO: TARGET SAID: 'INFO: Binary build date: Feb 22 2022 @ 11:58:16'
02:12:47: INFO: TARGET SAID: 'INFO: Binary build date: Feb 22 2022 @ 11:58:16
'
02:12:47: INFO: TARGET SAID: 'INFO: Chip serial num: 853016817 (0x32d800f1)'
02:12:47: INFO: TARGET SAID: 'INFO: Supported Functions (15):'
02:12:47: INFO: TARGET SAID: 'INFO: program'
02:12:47: INFO: TARGET SAID: 'INFO: read'
02:12:47: INFO: TARGET SAID: 'INFO: nop'
02:12:47: INFO: TARGET SAID: 'INFO: patch'
02:12:47: INFO: TARGET SAID: 'INFO: configure'
02:12:47: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
02:12:47: INFO: TARGET SAID: 'INFO: erase'
02:12:47: INFO: TARGET SAID: 'INFO: power'
02:12:47: INFO: TARGET SAID: 'INFO: firmwarewrite'
02:12:47: INFO: TARGET SAID: 'INFO: getstorageinfo'
02:12:47: INFO: TARGET SAID: 'INFO: benchmark'
02:12:47: INFO: TARGET SAID: 'INFO: emmc'
02:12:47: INFO: TARGET SAID: 'INFO: ufs'
02:12:47: INFO: TARGET SAID: 'INFO: fixgpt'
02:12:47: INFO: TARGET SAID: 'INFO: getsha256digest'
02:12:47: INFO: TARGET SAID: 'INFO: End of supported functions 15'
02:12:47: INFO: TARGET SAID: 'INFO: Calling handler for configure'
02:12:47: INFO: TARGET SAID: 'INFO: Storage type set to value eMMC'
02:12:47: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
02:12:47: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
02:12:47: INFO: In handleProgram('recovery.img')
02:12:47: INFO: Looking for file 'recovery.img'
02:12:47: INFO: =======================================================
02:12:47: INFO: {<program> FILE: 'C:\Program Files (x86)\Qualcomm\QPST\bin\recovery.img'}
02:12:47: INFO: {<program> (100.00 MB) 25600 sectors needed at location 64264 on LUN 0}
02:12:47: INFO: =======================================================
02:12:47: INFO: TARGET SAID: 'INFO: Calling handler for program'
02:12:47: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 1 partition 0'
02:12:47: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:1 partition:0 error:0'
02:12:47: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 344493556'
02:12:47: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:1, lun:0 error:3'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
02:12:47: {ERROR: program FAILED - Please see log}
Writing log to 'C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\zeras\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
Click to expand...
Click to collapse
Did you ever find a solution to this? I am in the same boat as you. I got the 'global' version instead of the stock rom by mistake by the seller and I have tried so many times to fix it. I feel like giving up at this point but nothing really works:/ Thank you in advance.
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga
{
"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"
}
Features:
Free auth bypass (EDL Mobile)
No need credit balance or activation
Free unlock EDL Auth device and flash
Only need to boot the device in EDL mode
What's newAdded EDL Auth-Supported Devices
- Redmi Note 9 4G / Redmi 9T (lime)
- Redmi Note 8 (ginkgo)
- Redmi Note 8T (willow)
- Redmi Note 5 Pro (whyred)
- Redmi Note 6 Pro (tulip)
- Redmi Note 7 Pro (violet)
- Redmi Note 7 (lavendar)
- Mi 8 (dipper)
- Mi 8 Lite (platina)
- Mi 8 SE(srius)
- Mi 8 EE(equuleus)
- Mi 8 Pro/UD(ursa)
- Mi 9 SE (grus)
- Mi CC9 (pyxis)
- Mi CC9E (laurus)
- Mi 6X (wayne)
- Mi Max 3 (nitrogen)
- Mi 5X (tiffany)
- Mi A2 Lite (daisy)
- Redmi 6 Pro (sakura)
- Redmi 7A (pine)
- Redmi 8 (olive)
- Redmi 8A (olivelite)
- Redmi 8 Pro/DUAL (olivewood)
- Redmi S2 (ysl)
I have successully tested this tool to flash Redmi 8A, Redmi 8A Dual and Redmi 7A, Redmi Note 7, Poco F1 and Redmi 9T.
You can read more about it in the below post as a reference.
[GUIDE] No Auth Xiaomi Redmi 8A, Redmi 8A Dual and Redmi 7A EDL Flashing using Mi Flash Tool.
[GUIDE] Xiaomi Redmi 8A EDL Flashing using Mi Flash Tool. (Also works for Redmi 7A). This tutorial has been successfully tested with Redmi 8A, Redmi 8A Dual and Redmi 7A all featuring a Qualcomm SDM439 Chipset. WARNING: DO NOT SHORT THE TEST...
forum.xda-developers.com
Also you can check No auth collection for your phone if available here
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Please test on your Qualcomm based Xiaomi phone and let me know about it.
Redmi k20 pro stuck in edl how can i flash wihout authorised account
mirasif said:
Redmi k20 pro stuck in edl how can i flash wihout authorised account
Click to expand...
Click to collapse
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
mvikrant97 said:
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
View attachment 5919599
Click to expand...
Click to collapse
How can i contact u
mvikrant97 said:
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
View attachment 5919599
Click to expand...
Click to collapse
can you help me? my RedMi K20 Pro(raphael) stuck on "cannot read hello packet". Please help me.. m
Can this work on poco f3? // If not can you add support for poco f3 on next update?
**C007** said:
Can this work on poco f3? // If not can you add support for poco f3 on next update?
Click to expand...
Click to collapse
Please try it for your phone.
I'm not the developer of the software.
I just shared what I found on the internet.
mvikrant97 said:
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by ZesugaView attachment 5918703Features:
Free auth bypass (EDL Mobile)
No need credit balance or activation
Free unlock EDL Auth device and flash
Only need to boot the device in EDL mode
What's newAdded EDL Auth-Supported Devices
- Redmi Note 9 4G / Redmi 9T (lime)
- Redmi Note 8 (ginkgo)
- Redmi Note 8T (willow)
- Redmi Note 5 Pro (whyred)
- Redmi Note 6 Pro (tulip)
- Redmi Note 7 Pro (violet)
- Redmi Note 7 (lavendar)
- Mi 8 (dipper)
- Mi 8 Lite (platina)
- Mi 8 SE(srius)
- Mi 8 EE(equuleus)
- Mi 8 Pro/UD(ursa)
- Mi 9 SE (grus)
- Mi CC9 (pyxis)
- Mi CC9E (laurus)
- Mi 6X (wayne)
- Mi Max 3 (nitrogen)
- Mi 5X (tiffany)
- Mi A2 Lite (daisy)
- Redmi 6 Pro (sakura)
- Redmi 7A (pine)
- Redmi 8 (olive)
- Redmi 8A (olivelite)
- Redmi 8 Pro/DUAL (olivewood)
- Redmi S2 (ysl)
I have successully tested this tool to flash Redmi 8A, Redmi 8A Dual and Redmi 7A, Redmi Note 7, Poco F1 and Redmi 9T.
You can read more about it in the below post as a reference.
[GUIDE] No Auth Xiaomi Redmi 8A, Redmi 8A Dual and Redmi 7A EDL Flashing using Mi Flash Tool.
[GUIDE] Xiaomi Redmi 8A EDL Flashing using Mi Flash Tool. (Also works for Redmi 7A). This tutorial has been successfully tested with Redmi 8A, Redmi 8A Dual and Redmi 7A all featuring a Qualcomm SDM439 Chipset. WARNING: DO NOT SHORT THE TEST...
forum.xda-developers.com
Also you can check No auth collection for your phone if available here
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Please test on your Qualcomm based Xiaomi phone and let me know about it.
Click to expand...
Click to collapse
i need edl bypass for poco x3 pro
Can u revive poco x3 nfc (surya) stuck on edl mode ?
hamawolf98k said:
i need edl bypass for poco x3 pro
Click to expand...
Click to collapse
It does not support your phone.
Ojha Baba said:
Can u revive poco x3 nfc (surya) stuck on edl mode ?
Click to expand...
Click to collapse
Yes but it will need a different tool.
This will not work.
mvikrant97 said:
Please try using mi flash that I have uploaded already in this post or
or else I have a paid tool (screenshot below) but I will help you for free.
View attachment 5919599
Click to expand...
Click to collapse
sir can you help me in my redmi note 9 pro I need authorize account to flash, youre mi flash tool didnt work hopefully you can help me
dark2133 said:
sir can you help me in my redmi note 9 pro I need authorize account to flash, youre mi flash tool didnt work hopefully you can help me
Click to expand...
Click to collapse
If your device is Curtana which has Snapdragon 720 then it can be done using paid tool only at the moment.
mvikrant97 said:
If your device is Curtana which has Snapdragon 720 then it can be done using paid tool only at the moment.
View attachment 5940667
Click to expand...
Click to collapse
Paid It
can you help with redmi note 8 im getting error on that modded miflasher as well via qfil
ERROR: sparse_open:2628 Unknown chunk type cac2
tonystark006 said:
can you help with redmi note 8 im getting error on that modded miflasher as well via qfil
ERROR: sparse_open:2628 Unknown chunk type cac2
Click to expand...
Click to collapse
Redmi Note 8 (ginkgo)
Is it this device?
mvikrant97 said:
Redmi Note 8 (ginkgo)
Is it this device?
Click to expand...
Click to collapse
yes ginkgo
2023-06-27 14:29:03.703 Image Search Path: C:\12.5\images
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0.xml
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0_xiaomi.xml
2023-06-27 14:29:03.703 PATCH file path:C:\12.5\images\patch0.xml
2023-06-27 14:29:18.218 Start Download
2023-06-27 14:29:18.223 Program Path:C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.223 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Binary build date: Apr 27 2018 @ 03:04:33
2023-06-27 14:29:18.418 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Sahara mappings:
2023-06-27 14:29:18.418 2: amss.mbn
2023-06-27 14:29:18.418 6: apps.mbn
2023-06-27 14:29:18.426 8: dsp1.mbn
2023-06-27 14:29:18.426 10: dbl.mbn
2023-06-27 14:29:18.426 11: osbl.mbn
2023-06-27 14:29:18.426 12: dsp2.mbn
2023-06-27 14:29:18.426 16: efs1.mbn
2023-06-27 14:29:18.426 17: efs2.mbn
2023-06-27 14:29:18.426 20: efs3.mbn
2023-06-27 14:29:18.434 21: sbl1.mbn
2023-06-27 14:29:18.435 22: sbl2.mbn
2023-06-27 14:29:18.435 23: rpm.mbn
2023-06-27 14:29:18.435 25: tz.mbn
2023-06-27 14:29:18.435 28: dsp3.mbn
2023-06-27 14:29:18.435 29: acdb.mbn
2023-06-27 14:29:18.435 30: wdt.mbn
2023-06-27 14:29:18.435 31: mba.mbn
2023-06-27 14:29:18.435 13: C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: Requested ID 13, file: "C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf"
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: 591740 bytes transferred in 0.109000 seconds (5.1773MBps)
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: File transferred successfully
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: Sahara protocol completed
2023-06-27 14:29:18.451 Sending Programmer Finished
2023-06-27 14:29:18.451 Switch To FireHose
2023-06-27 14:29:18.466 Wait for 3 seconds...
2023-06-27 14:29:21.485 Max Payload Size to Target:49152 Bytes
2023-06-27 14:29:21.485 Device Type:emmc
2023-06-27 14:29:21.485 Platform:8x26
2023-06-27 14:29:21.493 Disable Ack Raw Data Every N Packets
2023-06-27 14:29:21.493 Skip Write:False
2023-06-27 14:29:21.501 Always Validate:False
2023-06-27 14:29:21.501 Use Verbose:False
2023-06-27 14:29:21.509 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:21.728
2023-06-27 14:29:21.743 Base Version: 18.02.16.18.26
2023-06-27 14:29:21.743 Binary build date: Apr 27 2018 @ 03:04:29
2023-06-27 14:29:21.743 Incremental Build version: 18.04.27.03.04.29
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml,rawprogram0_xiaomi.xml --search_path=C:\12.5\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: Current working dir (cwd): C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2023-06-27 14:29:21.743 14:29:21: INFO: Showing network mappings to allow debugging
2023-06-27 14:29:21.759 14:29:21: INFO:
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759 14:29:21: INFO: Trying to store 'rawprogram0.xml' in string table
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'rawprogram0.xml'
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'metadata.img'
2023-06-27 14:29:21.759 14:29:21: INFO: Reading through sparse file 'metadata.img' and pulling out relevant header information...
2023-06-27 14:29:21.759 14:29:21: INFO: File metadata.img is a sparse file, being split up into 2 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'cust.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'cust.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File cust.img is a sparse file, being split up into 10 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'vendor.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File vendor.img is a sparse file, being split up into 13 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'system.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File system.img is a sparse file, being split up into 39 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'userdata.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 _____
2023-06-27 14:29:21.790 | ___|
2023-06-27 14:29:21.790 | |__ _ __ _ __ ___ _ __
2023-06-27 14:29:21.790 | __| '__| '__/ _ \| '__|
2023-06-27 14:29:21.790 | |__| | | | | (_) | |
2023-06-27 14:29:21.790 \____/_| |_| \___/|_|
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 14:29:21: {ERROR: Unknown chunk type cac2
2023-06-27 14:29:21.790 }
2023-06-27 14:29:21.790
2023-06-27 14:29:21.806 Writing log to 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Log is 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Download Fail:FireHose Fail:FHLoader Failrocess fail
2023-06-27 14:29:21.806 Finish Download
here is the full error message
tonystark006 said:
2023-06-27 14:29:03.703 Image Search Path: C:\12.5\images
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0.xml
2023-06-27 14:29:03.703 RAWPROGRAM file path: C:\12.5\images\rawprogram0_xiaomi.xml
2023-06-27 14:29:03.703 PATCH file path:C:\12.5\images\patch0.xml
2023-06-27 14:29:18.218 Start Download
2023-06-27 14:29:18.223 Program Path:C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.223 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Binary build date: Apr 27 2018 @ 03:04:33
2023-06-27 14:29:18.418 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:18.418 Sahara mappings:
2023-06-27 14:29:18.418 2: amss.mbn
2023-06-27 14:29:18.418 6: apps.mbn
2023-06-27 14:29:18.426 8: dsp1.mbn
2023-06-27 14:29:18.426 10: dbl.mbn
2023-06-27 14:29:18.426 11: osbl.mbn
2023-06-27 14:29:18.426 12: dsp2.mbn
2023-06-27 14:29:18.426 16: efs1.mbn
2023-06-27 14:29:18.426 17: efs2.mbn
2023-06-27 14:29:18.426 20: efs3.mbn
2023-06-27 14:29:18.434 21: sbl1.mbn
2023-06-27 14:29:18.435 22: sbl2.mbn
2023-06-27 14:29:18.435 23: rpm.mbn
2023-06-27 14:29:18.435 25: tz.mbn
2023-06-27 14:29:18.435 28: dsp3.mbn
2023-06-27 14:29:18.435 29: acdb.mbn
2023-06-27 14:29:18.435 30: wdt.mbn
2023-06-27 14:29:18.435 31: mba.mbn
2023-06-27 14:29:18.435 13: C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: Requested ID 13, file: "C:\Users\Hanzen\Desktop\prog_emmc_firehose_Redmi_Note_8.elf"
2023-06-27 14:29:18.435
2023-06-27 14:29:18.435 14:29:18: 591740 bytes transferred in 0.109000 seconds (5.1773MBps)
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: File transferred successfully
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451
2023-06-27 14:29:18.451 14:29:18: Sahara protocol completed
2023-06-27 14:29:18.451 Sending Programmer Finished
2023-06-27 14:29:18.451 Switch To FireHose
2023-06-27 14:29:18.466 Wait for 3 seconds...
2023-06-27 14:29:21.485 Max Payload Size to Target:49152 Bytes
2023-06-27 14:29:21.485 Device Type:emmc
2023-06-27 14:29:21.485 Platform:8x26
2023-06-27 14:29:21.493 Disable Ack Raw Data Every N Packets
2023-06-27 14:29:21.493 Skip Write:False
2023-06-27 14:29:21.501 Always Validate:False
2023-06-27 14:29:21.501 Use Verbose:False
2023-06-27 14:29:21.509 ***** Working Folder:C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2023-06-27 14:29:21.728
2023-06-27 14:29:21.743 Base Version: 18.02.16.18.26
2023-06-27 14:29:21.743 Binary build date: Apr 27 2018 @ 03:04:29
2023-06-27 14:29:21.743 Incremental Build version: 18.04.27.03.04.29
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743 C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml,rawprogram0_xiaomi.xml --search_path=C:\12.5\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2023-06-27 14:29:21.743 ************************************************
2023-06-27 14:29:21.743
2023-06-27 14:29:21.743 14:29:21: INFO: Current working dir (cwd): C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2023-06-27 14:29:21.743 14:29:21: INFO: Showing network mappings to allow debugging
2023-06-27 14:29:21.759 14:29:21: INFO:
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759
2023-06-27 14:29:21.759 14:29:21: INFO: Trying to store 'rawprogram0.xml' in string table
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'rawprogram0.xml'
2023-06-27 14:29:21.759 14:29:21: INFO: Looking for file 'metadata.img'
2023-06-27 14:29:21.759 14:29:21: INFO: Reading through sparse file 'metadata.img' and pulling out relevant header information...
2023-06-27 14:29:21.759 14:29:21: INFO: File metadata.img is a sparse file, being split up into 2 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'cust.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'cust.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File cust.img is a sparse file, being split up into 10 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'vendor.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File vendor.img is a sparse file, being split up into 13 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'system.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
2023-06-27 14:29:21.774 14:29:21: INFO: File system.img is a sparse file, being split up into 39 separate XML tags
2023-06-27 14:29:21.774 14:29:21: INFO: Looking for file 'userdata.img'
2023-06-27 14:29:21.774 14:29:21: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 _____
2023-06-27 14:29:21.790 | ___|
2023-06-27 14:29:21.790 | |__ _ __ _ __ ___ _ __
2023-06-27 14:29:21.790 | __| '__| '__/ _ \| '__|
2023-06-27 14:29:21.790 | |__| | | | | (_) | |
2023-06-27 14:29:21.790 \____/_| |_| \___/|_|
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790
2023-06-27 14:29:21.790 14:29:21: {ERROR: Unknown chunk type cac2
2023-06-27 14:29:21.790 }
2023-06-27 14:29:21.790
2023-06-27 14:29:21.806 Writing log to 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Log is 'C:\Users\Hanzen\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
2023-06-27 14:29:21.806
2023-06-27 14:29:21.806 Download Fail:FireHose Fail:FHLoader Failrocess fail
2023-06-27 14:29:21.806 Finish Download
here is the full error message
Click to expand...
Click to collapse
Extract and Replace the fh_loader with the attached file in xiaomi flash tool
If the above loader does not work please see this post below
phone stuck in edl mode please help
Happened to me while installing eu rom with mi flash.
forum.xda-developers.com