[14-04-19] UMTv2 / UMTPro - QcFire v4.1 - Improved Vivo Remove Locks and more...

[U.M.T]

Please provide us log or something like that, otherwise we can not see what exactly happened.

Br,
UMT

[Hamid.Hamidkhan]

my umt card expaird date my card not update what is the problem

[allumts]

Originally Posted by Hamid.Hamidkhan

my umt card expaird date my card not update what is the problem

Buy 1 year activaction and all turn back to work

[nksonu_jobner]

Operation : Reset Locks (Vivo)
Checking for existing devices...Not Found
Turn Off phone, hold Vol UP + Vol DOWN and insert USB cable.
Some phones may need Special Boot Cable or TestPoint for EDL mode.
Found Port : Qualcomm HS-USB QDLoader 9008 (COM8)
Driver Info : HS Corporation, ghsser.sys, 10.2104.1.2
Connecting to phone...OK
Waiting for response...OK
Init Handshake Sequence...OK
Hardware ID : E1A00900 [8953] 00000000
OPK_DATA : 30315EBED1DD09CEAAE927CAE0EE967076BC178CA33718DB4F FF8F02A0E7FAD2
Initializing Protocol...OK
Using Auto Loader Selection [1]
Preparing Loader...Done
Sending Loader [8953_003]...Done
Executing Loader...OK
Detecting Chip Type...OK
Hardware : 8953, eMMC, 64 GB
LU Count : 1 [0x0747C000]
Payload Info : In: 262144 [4096], Out: 1048576, Sector Size: 512
Reading Partition Table...OK
Reading Device Information...OK
Device : vivo vivo 1716 [msm8953]
Software : OPM1.171019.026 release-keys, eng.compil.20190318.212607 [Mon Mar 18 21:26:07 CST 2019]
Android Ver. : 8.1.0
Patch Level : 2019-03-01
USERDATA : Encrypted
Reading Extended Information...OK
Model : vivo 1716
Product : PD1708F_EX
Cust. Name : PD1708F_EX-IN
Version : PD1708F_EX_A_3.9.1
Resetting Locks (Vivo)...Done
Please wait for phone to reboot.
Operation Finished.
QcFire Ver. 4.1

[U.M.T]

Originally Posted by kundicom

Now all box and dongle just make money

Sent from my SM-G615F using Tapatalk

And we are sure that our users don't maky any kind of money.

Most of our user are doing charity work.

Br,
UMT

[allumts]

Originally Posted by U.M.T

And we are sure that our users don't maky any kind of money.

Most of our user are doing charity work.

Br,
UMT

Ahahah yes i agree with you 100%.

All box and dongle must be with credits and renew, only in this way somebody END of killed marketing getting out work for very Chip price.

Must remain in the market only "PROFESSIONAL TECHNICIAN"

[01Relocked]

Originally Posted by U.M.T

Please provide us log or something like that, otherwise we can not see what exactly happened.

Br,
UMT

see readed firmware examples below

everyones here knows how UMT QcFire Name their readed firmware files, always end up in error

log says read firmware ok

Operation	: Read Firmware
Checking for existing devices...Found
Port	: Qualcomm HS-USB QDLoader 9008 (COM3)
Driver Info	: HS Corporation, ghsser.sys, 10.2104.1.2
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID	: E1009600 [8909] 00000400
OPK_DATA	: D64F31F1F574B2C3A0A679CA104A03C0F20B4833F5E2F96A2B56AA09B374C8A6
Initializing Protocol...OK
Using Auto Loader Selection [1]
Preparing Loader...Done
Sending Loader [8909_044]...Done
Executing Loader...OK
Detecting Chip Type...OK
Hardware	: 8909, eMMC, 8 GB
LU Count	: 1 [0x00E90000] 
Payload Info	: In: 262144 [4096], Out: 1048576, Sector Size: 512
Reading Partition Table...OK
USERDATA	: Normal
Reading Device Information...OK
Device	: ZTE Z835 [msm8909]
Software	: Z835V1.0.0B13, 20170702.034315 [2017年 07月 02日 星期日 03:43:10 CST]
Android Ver.	: 7.1.1
Patch Level	: 2017-07-01
Reading [sbl1]...Done
Reading [rpm]...Done
Reading [tz]...Done
Reading [sec]...Done
Reading [splash]...Done
Reading [aboot]...Done
Reading [modem]...Done
Reading [boot]...Done
Reading [recovery]...Done
Reading [misc]...Done
Reading [persist]...Done
Reading [cache]...Done
Reading [system]...Done
Reading [gpt_main0]...Done
Reading [gpt_back0]...Done
Saved to	: C:\UMTool\QcFire\Read\ZTE_Z835_Z835V1.0.0B13_2017-07-01\
Operation Finished.
QcFire Ver. 4.1

Abnormal read firmware QcFire (Example: ZTE Maven 3):


Just check out file sizes

Normal read firmware NCKDongle (Example: Same ZTE Maven 3):


just check out file sizes

when trying to write back firmware, Qcfire or NCKDongle backup it presents this error:

Operation	: Flash
Checking for existing devices...Found
Port	: Qualcomm HS-USB QDLoader 9008 (COM3)
Driver Info	: HS Corporation, ghsser.sys, 10.2104.1.2
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID	: E1009600 [8909] 00000400
OPK_DATA	: D64F31F1F574B2C3A0A679CA104A03C0F20B4833F5E2F96A2B56AA09B374C8A6
Initializing Protocol...OK
Using Auto Loader Selection [1]
Preparing Loader...Done
Sending Loader [8909_044]...Done
Executing Loader...OK
Detecting Chip Type...OK
Hardware	: 8909, eMMC, 8 GB
LU Count	: 1 [0x00E90000] 
Payload Info	: In: 262144 [4096], Out: 1048576, Sector Size: 512
Writing [sbl1.mbn] -> [sbl1] ...Done
Writing [ddr.img] -> [DDR] ...Failed
Operation Finished.
QcFire Ver. 4.1

otherwise with NCK Dongle it writes okay, but only using nck read firmware copy because QcFire Read firmware copy is damaged, not useful.

this errors is not only tied to ZTE maven 3, also it happens with others

File sizes comparison QcFire Firmware copy vs NCK Dongle Firmware copy:



as we can see, copys made with QcFire are somehow incomplete, firmware is around 1.36GB, but NCK Dongle has dumped firmware okay with a size of 3.06 GB, Read/Write error in EDL exploits with QcFire as a result.
also using QcFire firmware copy, noticed that QcFire can't write system partition, it only skips and reboot device.


BTW, FORMAT CHIP OPTION IS NOT WORKING, ALSO IT DOESN'T SAVE LOGS, JUST IS THERE LIKE A BUTTON WITH NO FUNCTION, THIS IS A THING THAT ON YOUR OWN YOU CAN TEST, HONESTL IT DOESN'T WORK AND OTHER USER CAN CONFIRM THIS IF YOU MAKE A POLL.

[shahjadios]

brother i m agree for activation policy but have one request please add opp new models like oppo A3s, R15,A5,A7,R15x etc etc thanks for supporting...

[U.M.T]

Originally Posted by 01Relocked

see readed firmware examples below

everyones here knows how UMT QcFire Name their readed firmware files, always end up in error

log says read firmware ok

Operation	: Read Firmware
Checking for existing devices...Found
Port	: Qualcomm HS-USB QDLoader 9008 (COM3)
Driver Info	: HS Corporation, ghsser.sys, 10.2104.1.2
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID	: E1009600 [8909] 00000400
OPK_DATA	: D64F31F1F574B2C3A0A679CA104A03C0F20B4833F5E2F96A2B56AA09B374C8A6
Initializing Protocol...OK
Using Auto Loader Selection [1]
Preparing Loader...Done
Sending Loader [8909_044]...Done
Executing Loader...OK
Detecting Chip Type...OK
Hardware	: 8909, eMMC, 8 GB
LU Count	: 1 [0x00E90000] 
Payload Info	: In: 262144 [4096], Out: 1048576, Sector Size: 512
Reading Partition Table...OK
USERDATA	: Normal
Reading Device Information...OK
Device	: ZTE Z835 [msm8909]
Software	: Z835V1.0.0B13, 20170702.034315 [2017年 07月 02日 星期日 03:43:10 CST]
Android Ver.	: 7.1.1
Patch Level	: 2017-07-01
Reading [sbl1]...Done
Reading [rpm]...Done
Reading [tz]...Done
Reading [sec]...Done
Reading [splash]...Done
Reading [aboot]...Done
Reading [modem]...Done
Reading [boot]...Done
Reading [recovery]...Done
Reading [misc]...Done
Reading [persist]...Done
Reading [cache]...Done
Reading [system]...Done
Reading [gpt_main0]...Done
Reading [gpt_back0]...Done
Saved to	: C:\UMTool\QcFire\Read\ZTE_Z835_Z835V1.0.0B13_2017-07-01\
Operation Finished.
QcFire Ver. 4.1

Abnormal read firmware QcFire (Example: ZTE Maven 3):

Just check out file sizes

Normal read firmware NCKDongle (Example: Same ZTE Maven 3):

just check out file sizes

when trying to write back firmware, Qcfire or NCKDongle backup it presents this error:

Operation	: Flash
Checking for existing devices...Found
Port	: Qualcomm HS-USB QDLoader 9008 (COM3)
Driver Info	: HS Corporation, ghsser.sys, 10.2104.1.2
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID	: E1009600 [8909] 00000400
OPK_DATA	: D64F31F1F574B2C3A0A679CA104A03C0F20B4833F5E2F96A2B56AA09B374C8A6
Initializing Protocol...OK
Using Auto Loader Selection [1]
Preparing Loader...Done
Sending Loader [8909_044]...Done
Executing Loader...OK
Detecting Chip Type...OK
Hardware	: 8909, eMMC, 8 GB
LU Count	: 1 [0x00E90000] 
Payload Info	: In: 262144 [4096], Out: 1048576, Sector Size: 512
Writing [sbl1.mbn] -> [sbl1] ...Done
Writing [ddr.img] -> [DDR] ...Failed
Operation Finished.
QcFire Ver. 4.1

otherwise with NCK Dongle it writes okay, but only using nck read firmware copy because QcFire Read firmware copy is damaged, not useful.

this errors is not only tied to ZTE maven 3, also it happens with others

File sizes comparison QcFire Firmware copy vs NCK Dongle Firmware copy:


as we can see, copys made with QcFire are somehow incomplete, firmware is around 1.36GB, but NCK Dongle has dumped firmware okay with a size of 3.06 GB, Read/Write error in EDL exploits with QcFire as a result.
also using QcFire firmware copy, noticed that QcFire can't write system partition, it only skips and reboot device.


BTW, FORMAT CHIP OPTION IS NOT WORKING, ALSO IT DOESN'T SAVE LOGS, JUST IS THERE LIKE A BUTTON WITH NO FUNCTION, THIS IS A THING THAT ON YOUR OWN YOU CAN TEST, HONESTL IT DOESN'T WORK AND OTHER USER CAN CONFIRM THIS IF YOU MAKE A POLL.

Thanks for you detailed information.

Here are a few things:
- Firmware read by QcFire are encrypted by default, and had smaller size than dump. This option is to save user's HDD space. However this Encrypted Firmware is only supported with QcFire. You can not use this firmware with other tools.

- About write error on DDR, you may try to untick this partiton and check flashing.

- About error on System flashing, it should not occur with QcFire read firmware. However some issue has been reported with some large sparse system.img flashing.

- About Format Chip, for security reason, and to avoid users crying later, we have given 3 questions to go thru. Read it carefully. First you have to say OK, then NO, then again YES.

So next time, read carefully, understand and then complaint. If there is a bug, we will fix it as its our work.

I think you have got your answer.

Br,
UMT

[01Relocked]

Originally Posted by U.M.T

Thanks for you detailed information.

Here are a few things:
- Firmware read by QcFire are encrypted by default, and had smaller size than dump. This option is to save user's HDD space. However this Encrypted Firmware is only supported with QcFire. You can not use this firmware with other tools.

- About write error on DDR, you may try to untick this partiton and check flashing.

- About error on System flashing, it should not occur with QcFire read firmware. However some issue has been reported with some large sparse system.img flashing.

- About Format Chip, for security reason, and to avoid users crying later, we have given 3 questions to go thru. Read it carefully. First you have to say OK, then NO, then again YES.

So next time, read carefully, understand and then complaint. If there is a bug, we will fix it as its our work.

I think you have got your answer.

Br,
UMT

as my request, made qcfire firmware backup with their original size, no compression and compatible with other tools, since the reason to do a backup is not only to use it with QcFire but also with other tools in case of error, hoping next update comes as I need it

regards

[U.M.T]

It is already there. Just tick Plain Mode in Partition selection window.

Br,
UMT

[young_master]

nice update umt the best

[sarce_1]

its also No support VIVO NEX ?