mi note5 pro flashing error -help me - GSM-Forum

zone3 · 11-05-2019, 14:25

error as below

Searching Device ....
Found

Product : whyred
Serial No : 60338ae5

Flash Process Started

File name : gpt_both0.bin
File Size : 33.50 KB
Uploading : gpt_both0.bin
Uploading : gpt_both0
Download Size : 536870912 bytes
sending partation (33 KB)
Verifying : OK
writing partation
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : tz.mbn
File Size : 1.87 MB
Uploading : tz
Download Size : 536870912 bytes
sending tz (1912 KB)
Verifying : OK
writing tz
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : rpm.mbn
File Size : 219.57 KB
Uploading : rpm
Download Size : 536870912 bytes
sending rpm (219 KB)
Verifying : OK
writing rpm
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : hyp.mbn
File Size : 264.00 KB
Uploading : hyp
Download Size : 536870912 bytes
sending hyp (264 KB)
Verifying : OK
writing hyp
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : tzbak.mbn
File Size : 1.87 MB
Uploading : tzbak
Download Size : 536870912 bytes
sending tzbak (1912 KB)
Verifying : OK
writing tzbak
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : rpmbak.mbn
File Size : 219.57 KB
Uploading : rpmbak
Download Size : 536870912 bytes
sending rpmbak (219 KB)
Verifying : OK
writing rpmbak
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : hypbak.mbn
File Size : 264.00 KB
Uploading : hypbak
Download Size : 536870912 bytes
sending hypbak (264 KB)
Verifying : OK
writing hypbak
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : NON-HLOS.bin
File Size : 105.20 MB
Uploading : NON-HLOS
Download Size : 536870912 bytes
sending modem (107729 KB)
Verifying : OK
writing modem
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : system.img
File Size : 2.73 GB
Uploading : system
Download Size : 536870912 bytes
ERASING SYSTEM
Verifying : Failed
Erase is not allowed in Lock State
======================================
File name : cache.img
File Size : 6.10 MB
Uploading : cache
Download Size : 536870912 bytes
ERASING CACHE
Verifying : Failed
Erase is not allowed in Lock State
======================================
File name : userdata.img
File Size : 165.18 MB
Uploading : userdata
Download Size : 536870912 bytes
ERASING USERDATA
Verifying : Failed
Erase is not allowed in Lock State
======================================
File name : recovery.img
File Size : 30.43 MB
Uploading : recovery
Download Size : 536870912 bytes
sending recovery (31165 KB)
Verifying : OK
writing recovery
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : boot.img
File Size : 25.03 MB
Uploading : boot
Download Size : 536870912 bytes
sending boot (25633 KB)
Verifying : OK
writing boot
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : vendor.img
File Size : 826.89 MB
Uploading : vendor
Download Size : 536870912 bytes
sending sparse vendor (515286 KB)
Verifying : OK
writing vendor
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : cmnlib.mbn
File Size : 212.98 KB
Uploading : cmnlib
Download Size : 536870912 bytes
sending cmnlib (212 KB)
Verifying : OK
writing cmnlib
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : keymaster.mbn
File Size : 349.02 KB
Uploading : keymaster
Download Size : 536870912 bytes
sending keymaster (349 KB)
Verifying : OK
writing keymaster
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : keymasterbak.mbn
File Size : 349.02 KB
Uploading : keymasterbak
Download Size : 536870912 bytes
sending keymasterbak (349 KB)
Verifying : OK
writing keymasterbak
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : misc.img
File Size : 8.00 KB
Uploading : misc
Download Size : 536870912 bytes
sending misc (8 KB)
Verifying : OK
writing misc
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : persist.img
File Size : 4.59 MB
Uploading : persist
Download Size : 536870912 bytes
sending persist (4696 KB)
Verifying : OK
writing persist
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : mdtp.img
File Size : 16.98 MB
Uploading : mdtp
Download Size : 536870912 bytes
sending mdtp (17390 KB)
Verifying : OK
writing mdtp
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : splash.img
File Size : 23.75 MB
Uploading : splash
Download Size : 536870912 bytes
sending splash (24316 KB)
Verifying : OK
writing splash
Verifying : Failed
Flashing is not allowed in Lock State
======================================
File name : cust.img
File Size : 504.14 MB
Uploading : cust
Download Size : 536870912 bytes
sending cust (516237 KB)
Verifying : OK
writing cust
Verifying : Failed
Flashing is not allowed in Lock State
======================================
Flashing Finished
Rebooting Device.

i think it need bootloader unlock-am i right?

**Mehmood Riaz 1** · 11-05-2019, 14:35

Flashing logs itself are answer of flashing Failure

Flashing is not allowed in Lock State

This mean it is bootloader locked device and fastboot flashing is not possible on locked bootloader.

zone3 · 11-05-2019, 14:45

Quote:

Originally Posted by Mehmood Riaz 1

Flashing logs itself are answer of flashing Failure

Flashing is not allowed in Lock State

This mean it is bootloader locked device and fastboot flashing is not possible on locked bootloader.

tried bootloader unlock-logs as success-but still in lock

Searching Device...
Found device

Reading BootLoader Status Info.
If it stuck here long time please remove usb Cable from device.

Device Serial : [ 60338ae5 ]
Verity mode : True
Device unlocked : False
Device critical unlocked : False
Charger screen enabled : True

Executing exploit : Done

Unlocking Bootloader...

Bootloader Unlock Success

Rebooting device

still in lock-so what to do as a next step?

**Mehmood Riaz 1** · 11-05-2019, 16:30

If you need to flash this device, why don't you flash it in EDL mode with test points ?

11-05-2019, 14:25	#1 (permalink)
zone3 No Life Poster Join Date: Jan 2009 Posts: 3,260 Member: 946381 Status: Offline Thanks Meter: 150	mi note5 pro flashing error -help me error as below Searching Device .... Found Product : whyred Serial No : 60338ae5 Flash Process Started File name : gpt_both0.bin File Size : 33.50 KB Uploading : gpt_both0.bin Uploading : gpt_both0 Download Size : 536870912 bytes sending partation (33 KB) Verifying : OK writing partation Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : tz.mbn File Size : 1.87 MB Uploading : tz Download Size : 536870912 bytes sending tz (1912 KB) Verifying : OK writing tz Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : rpm.mbn File Size : 219.57 KB Uploading : rpm Download Size : 536870912 bytes sending rpm (219 KB) Verifying : OK writing rpm Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : hyp.mbn File Size : 264.00 KB Uploading : hyp Download Size : 536870912 bytes sending hyp (264 KB) Verifying : OK writing hyp Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : tzbak.mbn File Size : 1.87 MB Uploading : tzbak Download Size : 536870912 bytes sending tzbak (1912 KB) Verifying : OK writing tzbak Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : rpmbak.mbn File Size : 219.57 KB Uploading : rpmbak Download Size : 536870912 bytes sending rpmbak (219 KB) Verifying : OK writing rpmbak Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : hypbak.mbn File Size : 264.00 KB Uploading : hypbak Download Size : 536870912 bytes sending hypbak (264 KB) Verifying : OK writing hypbak Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : NON-HLOS.bin File Size : 105.20 MB Uploading : NON-HLOS Download Size : 536870912 bytes sending modem (107729 KB) Verifying : OK writing modem Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : system.img File Size : 2.73 GB Uploading : system Download Size : 536870912 bytes ERASING SYSTEM Verifying : Failed Erase is not allowed in Lock State ====================================== File name : cache.img File Size : 6.10 MB Uploading : cache Download Size : 536870912 bytes ERASING CACHE Verifying : Failed Erase is not allowed in Lock State ====================================== File name : userdata.img File Size : 165.18 MB Uploading : userdata Download Size : 536870912 bytes ERASING USERDATA Verifying : Failed Erase is not allowed in Lock State ====================================== File name : recovery.img File Size : 30.43 MB Uploading : recovery Download Size : 536870912 bytes sending recovery (31165 KB) Verifying : OK writing recovery Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : boot.img File Size : 25.03 MB Uploading : boot Download Size : 536870912 bytes sending boot (25633 KB) Verifying : OK writing boot Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : vendor.img File Size : 826.89 MB Uploading : vendor Download Size : 536870912 bytes sending sparse vendor (515286 KB) Verifying : OK writing vendor Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : cmnlib.mbn File Size : 212.98 KB Uploading : cmnlib Download Size : 536870912 bytes sending cmnlib (212 KB) Verifying : OK writing cmnlib Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : keymaster.mbn File Size : 349.02 KB Uploading : keymaster Download Size : 536870912 bytes sending keymaster (349 KB) Verifying : OK writing keymaster Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : keymasterbak.mbn File Size : 349.02 KB Uploading : keymasterbak Download Size : 536870912 bytes sending keymasterbak (349 KB) Verifying : OK writing keymasterbak Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : misc.img File Size : 8.00 KB Uploading : misc Download Size : 536870912 bytes sending misc (8 KB) Verifying : OK writing misc Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : persist.img File Size : 4.59 MB Uploading : persist Download Size : 536870912 bytes sending persist (4696 KB) Verifying : OK writing persist Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : mdtp.img File Size : 16.98 MB Uploading : mdtp Download Size : 536870912 bytes sending mdtp (17390 KB) Verifying : OK writing mdtp Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : splash.img File Size : 23.75 MB Uploading : splash Download Size : 536870912 bytes sending splash (24316 KB) Verifying : OK writing splash Verifying : Failed Flashing is not allowed in Lock State ====================================== File name : cust.img File Size : 504.14 MB Uploading : cust Download Size : 536870912 bytes sending cust (516237 KB) Verifying : OK writing cust Verifying : Failed Flashing is not allowed in Lock State ====================================== Flashing Finished Rebooting Device. i think it need bootloader unlock-am i right?

11-05-2019, 14:35	#2 (permalink)
Mehmood Riaz 1 Product Manager Join Date: Mar 2012 Location: Some Where Posts: 3,652 Member: 1737175 Status: Offline Sonork: 100.1667675 Thanks Meter: 10,531	Flashing logs itself are answer of flashing Failure Flashing is not allowed in Lock State This mean it is bootloader locked device and fastboot flashing is not possible on locked bootloader.

11-05-2019, 16:30	#4 (permalink)
Mehmood Riaz 1 Product Manager Join Date: Mar 2012 Location: Some Where Posts: 3,652 Member: 1737175 Status: Offline Sonork: 100.1667675 Thanks Meter: 10,531	If you need to flash this device, why don't you flash it in EDL mode with test points ?