Redmi 6 pro efs functions failed - GSM-Forum

speedstarrr · 12-15-2018, 11:14

Device : Xiaomi Redmi 6 Pro
Operation : Full Reset EFS
Checking for existing devices...Found
Port : Qualcomm HS-USB QDLoader 9008 (COM39)
Driver Info : Qualcomm Incorporated, qu_usb_serial.sys, 2.1.2.0
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID : E1600400 [8953] 00000000
OPK_DATA : 079E496E26A477B120DFCD85DF7E4AD067164D8292DDD37993 0D5891E3D8240B
Initializing Protocol...OK
Preparing Loader...Done
Sending Loader [Mi6Pro]...Write Error!
Please use correct loader and check USB port / cable.
Operation Finished.
QcFire Ver. 3.5

Tested with 3 different cable 2 from samsung original box
Tested with tp non tp method also different usb ports but always failed on this point.

Someone bricked imei on device (00000000000000) i have qcn backup from other handset and trying to repair imei numbers

Regards

**U.M.T** · 12-15-2018, 11:25

Do not select any model, and try again.

You can also try to repair IMEI in UMT GSM with diag port.

Br,
UMT

speedstarrr · 12-15-2018, 12:17

Operation : Backup EFS
Checking for existing devices...Found
Port : Qualcomm HS-USB QDLoader 9008 (COM39)
Driver Info : Qualcomm Incorporated, qu_usb_serial.sys, 2.1.2.0
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID : E1600400 [8953] 00000000
OPK_DATA : 079E496E26A477B120DFCD85DF7E4AD067164D8292DDD37993 0D5891E3D8240B
Initializing Protocol...OK
Using Auto Loader Selection [1]
Preparing Loader...Done
Sending Loader [8953]...Write Error!
Please use correct loader and check USB port / cable.
Operation Finished.
QcFire Ver. 3.5

This is report of default loader

speedstarrr · 12-15-2018, 12:37

Port : ADB Interface
Baud Rate : Not Applicable
Device : Qualcomm Android
Operation : Reset EFS
Searching for Device... Found
Model : Redmi 6 Pro
Version : 8.1.0
Hardware : qcom
Baseband : 953_GEN_PACK-1.152683.0.158868.2
CPU : arm64-v8a
SIM Card : ABSENT,ABSENT
Type : Unknown
MEID(1) : Null/Empty
Root : Rooted
Gettting Partition Data... Not Found
Creating EFS Backup (zip)... Pull Err!
Operation Failed.
Elapsed Time: 00:20
[Module Ver. 5.2]
Log Saved to Logs\181215_133629.log
Also report for efs backup etc all other imei repair functions did not work

speedstarrr · 12-17-2018, 23:27

long silence from team also bug report deleted will you release working solution or not?

**U.M.T** · 12-18-2018, 06:20

No, it will not be fixed.

It is not supported with new anti level, and will not be supported until Xiaomi Release loader for Anti 4 level.

Br,
UMT

speedstarrr · 12-18-2018, 11:25

C:\Windows\system32>cd..

C:\Windows>cd..

C:\>cd adb

C:\adb>fastboot getvar anti
anti:
finished. total time: 0.005s

C:\adb>

Antirollback level is none so device never reach that position i just wrote before about it device chip and loader type looking wrong many users reported that but seems umt doesnt care about this product anymore

ROhan464 · 03-26-2019, 15:34

1st umt qfire tool se Reset EFS
then restore EFS file orignel
then restore qcn file origneal but phale dig port banani hogi tabhi hoga

101% done if you have change imei so not posible tight secorty xiaomi compney i have 50 time try so don't try west time origneal hi chalenge

12-15-2018, 11:14	#1 (permalink)
speedstarrr No Life Poster Join Date: Apr 2006 Posts: 598 Member: 255072 Status: Offline Thanks Meter: 46	Redmi 6 pro efs functions failed Device : Xiaomi Redmi 6 Pro Operation : Full Reset EFS Checking for existing devices...Found Port : Qualcomm HS-USB QDLoader 9008 (COM39) Driver Info : Qualcomm Incorporated, qu_usb_serial.sys, 2.1.2.0 Opening Port...OK Init Handshake Sequence...OK Hardware ID : E1600400 [8953] 00000000 OPK_DATA : 079E496E26A477B120DFCD85DF7E4AD067164D8292DDD37993 0D5891E3D8240B Initializing Protocol...OK Preparing Loader...Done Sending Loader [Mi6Pro]...Write Error! Please use correct loader and check USB port / cable. Operation Finished. QcFire Ver. 3.5 Tested with 3 different cable 2 from samsung original box Tested with tp non tp method also different usb ports but always failed on this point. Someone bricked imei on device (00000000000000) i have qcn backup from other handset and trying to repair imei numbers Regards

12-15-2018, 11:25	#2 (permalink)
U.M.T Product Manager Join Date: Sep 2015 Location: Inside UMT Posts: 9,406 Member: 2465108 Status: Offline Sonork: No More Used Thanks Meter: 13,432	Do not select any model, and try again. You can also try to repair IMEI in UMT GSM with diag port. Br, UMT

12-15-2018, 12:17	#3 (permalink)
speedstarrr No Life Poster Join Date: Apr 2006 Posts: 598 Member: 255072 Status: Offline Thanks Meter: 46	Operation : Backup EFS Checking for existing devices...Found Port : Qualcomm HS-USB QDLoader 9008 (COM39) Driver Info : Qualcomm Incorporated, qu_usb_serial.sys, 2.1.2.0 Opening Port...OK Init Handshake Sequence...OK Hardware ID : E1600400 [8953] 00000000 OPK_DATA : 079E496E26A477B120DFCD85DF7E4AD067164D8292DDD37993 0D5891E3D8240B Initializing Protocol...OK Using Auto Loader Selection [1] Preparing Loader...Done Sending Loader [8953]...Write Error! Please use correct loader and check USB port / cable. Operation Finished. QcFire Ver. 3.5 This is report of default loader

12-15-2018, 12:37	#4 (permalink)
speedstarrr No Life Poster Join Date: Apr 2006 Posts: 598 Member: 255072 Status: Offline Thanks Meter: 46	Port : ADB Interface Baud Rate : Not Applicable Device : Qualcomm Android Operation : Reset EFS Searching for Device... Found Model : Redmi 6 Pro Version : 8.1.0 Hardware : qcom Baseband : 953_GEN_PACK-1.152683.0.158868.2 CPU : arm64-v8a SIM Card : ABSENT,ABSENT Type : Unknown MEID(1) : Null/Empty Root : Rooted Gettting Partition Data... Not Found Creating EFS Backup (zip)... Pull Err! Operation Failed. Elapsed Time: 00:20 [Module Ver. 5.2] Log Saved to Logs\181215_133629.log Also report for efs backup etc all other imei repair functions did not work

12-17-2018, 23:27	#5 (permalink)
speedstarrr No Life Poster Join Date: Apr 2006 Posts: 598 Member: 255072 Status: Offline Thanks Meter: 46	long silence from team also bug report deleted will you release working solution or not?

12-18-2018, 06:20	#6 (permalink)
U.M.T Product Manager Join Date: Sep 2015 Location: Inside UMT Posts: 9,406 Member: 2465108 Status: Offline Sonork: No More Used Thanks Meter: 13,432	No, it will not be fixed. It is not supported with new anti level, and will not be supported until Xiaomi Release loader for Anti 4 level. Br, UMT

12-18-2018, 11:25	#7 (permalink)
speedstarrr No Life Poster Join Date: Apr 2006 Posts: 598 Member: 255072 Status: Offline Thanks Meter: 46	C:\Windows\system32>cd.. C:\Windows>cd.. C:\>cd adb C:\adb>fastboot getvar anti anti: finished. total time: 0.005s C:\adb> Antirollback level is none so device never reach that position i just wrote before about it device chip and loader type looking wrong many users reported that but seems umt doesnt care about this product anymore

03-26-2019, 15:34	#8 (permalink)
ROhan464 Freak Poster Join Date: Apr 2010 Location: Gautam Buddha Nagar Age: 35 Posts: 301 Member: 1291309 Status: Offline Sonork: [email protected] Thanks Meter: 58	1st umt qfire tool se Reset EFS then restore EFS file orignel then restore qcn file origneal but phale dig port banani hogi tabhi hoga 101% done if you have change imei so not posible tight secorty xiaomi compney i have 50 time try so don't try west time origneal hi chalenge