• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Restore Stock Image and Lock the Bootloader (for Warranty)

Search This thread

BadCluster

Senior Member
Sep 21, 2008
331
136
45
Venice
www.giocoleria.org
--------------------------------> DISCLAIMER: <------------------------------------

Guide for pure educational purpose. If you are going to use it, you do it to your risk and danger, I will not be held responsible if your phone will not work anymore.

----------------------------------------------------------------------------------------

This tutorial is for relock the boot loader and restore original stock image on Lenovo Z5 Pro (L78031 - NO-GT version)

For security reason, it's better if you do an Nandroid Backup with the TWRP.

https://forum.xda-developers.com/z5...ow-to-unlock-bootloader-install-twrp-t3890402

I'm not responsable if this operation brick you mobile phone!

How to put the phone in EDL:
1) The phone must be Turn-OFF.
2) Press all two buttons at the same time vol+ and vol- and connect the cable USB.
3) Put the phone in EDL mode only a second before to press the button DOWNLOAD (you must be very very fast otherwise you'll have Sahara error)

Do it

1) Download a Rom: Here you find the 293 and 320 Version (if one give you an error, try the other one), Here you find 342 Version
2) Download and Install ADB Driver: Here or look the Attachments
3) Download and Install Qualcomm Flasher: Qualcomm Flasher Qfil QPST V.2.0.1.9 or look the Attachments
4) download and install Qualcomm Driver: For Windows 32 Bit - For Windows 64 Bit or look the Attachment 32 Bit - Attachments 64bit
5) Download and Install Minimal ADB fastboot from the Attachments
6) Follow this Steps:

115201rdc5mpcllmomomm7.jpg.thumb.jpg


115202eaa7a77a99sby47a.jpg.thumb.jpg


115202kotfnd8nf7ow86x7.jpg.thumb.jpg


115203h90q0tatr98tc98t.jpg.thumb.jpg


115203pa1m3usl9xvlkxld.jpg.thumb.jpg


115204bphi86kc8l6ghntn.jpg.thumb.jpg


115204nrqo63jkepxh3zqr.jpg.thumb.jpg


115205reqke55b1212r9vq.jpg.thumb.jpg


115205ov0accuapvoccjv7.jpg.thumb.jpg


115206cg83285552qh8c3c.jpg.thumb.jpg


01.png


02.png


03a.png


03.png


04.png


05.png


06.png


07.png


08.png


Now, Press all two buttons at the same time vol+ and vol- and connect the cable USB to the phone and quickly press Download button!

09.png


115211yimdb7vr1ckhmhhw.jpg.thumb.jpg


115211sd92syf1mmh3mzey.jpg.thumb.jpg


Done!

Sahara Error: https://forum.xda-developers.com/showpost.php?p=77229641&postcount=2

Sahara Error 2:
url]
 

Attachments

  • minimal_adb_fastboot_v1.4.3_setup.zip
    1,003.6 KB · Views: 721
  • adbdriver.zip
    9.2 MB · Views: 435
  • Qualcomm_Flash_Image_Loader_v2.0.1.9.zip
    3.5 MB · Views: 533
  • Qualcomm_QDLoader_HS-USB_Driver_32bit_Setup.zip
    6.1 MB · Views: 137
  • Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
    10.9 MB · Views: 411
Last edited:

fuchstruong

Member
Feb 14, 2019
5
0
hi, guy! after my phone back to stock rom, what i have to do to relock bootloader? pls, help me! when i enter to system update: "your system has been root, we are unable to provide the lastest version of the system".
 
Last edited:

checo6969

New member
Apr 18, 2017
1
0
error QFIL

hi friend, could you help me, by pressing download I get this download fail: firehose fhloader: fail the system can not find the specified file
 

fuchstruong

Member
Feb 14, 2019
5
0
hi friend, could you help me, by pressing download I get this download fail: firehose fhloader: fail the system can not find the specified file

hi guy! u try copying rom to C:\Program Files (x86)\Qualcomm\QPST\bin

---------- Post added at 02:32 AM ---------- Previous post was at 02:27 AM ----------

--------------------------------> DISCLAIMER: <------------------------------------

Guide for pure educational purpose. If you are going to use it, you do it to your risk and danger, I will not be held responsible if your phone will not work anymore.

----------------------------------------------------------------------------------------

This tutorial is for relock the boot loader and restore original stock image on Lenovo Z5 Pro (L78031 - NO-GT version)

For security reason, it's better if you do an Nandroid Backup with the TWRP.

https://forum.xda-developers.com/z5...ow-to-unlock-bootloader-install-twrp-t3890402

I'm not responsable if this operation brick you mobile phone!

How to put the phone in EDL:
1) The phone must be Turn-OFF.
2) Press all two buttons at the same time vol+ and vol- and connect the cable USB.
3) Put the phone in EDL mode only a second before to press the button DOWNLOAD (you must be very very fast otherwise you'll have Sahara error)

Do it

1) Download a Rom: Here you find the 293 and 320 Version (if one give you an error, try the other one), Here you find 342 Version
2) Download and Install ADB Driver: Here or look the Attachments
3) Download and Install Qualcomm Flasher: Qualcomm Flasher Qfil QPST V.2.0.1.9 or look the Attachments
4) download and install Qualcomm Driver: For Windows 32 Bit - For Windows 64 Bit or look the Attachment 32 Bit - Attachments 64bit
5) Download and Install Minimal ADB fastboot from the Attachments
6) Follow this Steps:

115201rdc5mpcllmomomm7.jpg.thumb.jpg


115202eaa7a77a99sby47a.jpg.thumb.jpg


115202kotfnd8nf7ow86x7.jpg.thumb.jpg


115203h90q0tatr98tc98t.jpg.thumb.jpg


115203pa1m3usl9xvlkxld.jpg.thumb.jpg


115204bphi86kc8l6ghntn.jpg.thumb.jpg


115204nrqo63jkepxh3zqr.jpg.thumb.jpg


115205reqke55b1212r9vq.jpg.thumb.jpg


115205ov0accuapvoccjv7.jpg.thumb.jpg


115206cg83285552qh8c3c.jpg.thumb.jpg


01.png


02.png


03a.png


03.png


04.png


05.png


06.png


07.png


08.png


Now, Press all two buttons at the same time vol+ and vol- and connect the cable USB to the phone and quickly press Download button!

09.png


115211yimdb7vr1ckhmhhw.jpg.thumb.jpg


115211sd92syf1mmh3mzey.jpg.thumb.jpg


Done!

Sahara Error: https://forum.xda-developers.com/showpost.php?p=77229641&postcount=2

Sahara Error 2:
url]

hi guy, if i'ld like to lock the bootloader, i can flash any stock rom or i've to flash the first stock rom of it? :confused:
 

anonOmattie

Member
Mar 3, 2019
28
11
not working :crying: i can't post the image for u to see
my cmd after entering "fastboot -i 0x2b4c oem lock" is "< waiting for any device >"
what should i do?

i have the same problem. i followed all steps from twrp and installing the stock rom, but after all the hastle im not able to lock the bootloader so i still cannot get any updates.
i have the same problem where it says waiting for device. would be nice if there will be a solution for this to get future updates soon!

---------- Post added at 05:16 PM ---------- Previous post was at 04:49 PM ----------

succesful flashed version 355
THIS IS A VERY RISKY OPERATION AND I ALMOST LOST MY PHONE!!

it didnt go as planned.
i installed twrp and created a backup (not of system, is that nesecarry?) to get to when everything got messed up.

and boi, did it get messed up...

problem 1: when trying to install the rom with QFIL for the first time i got a sahara error and the phone lost its OS. i wanted to reinstall the twrp backup as i got really freaked out about losing my phone. somehow it did not get into edl or something and i failed the installation process and ended up with a broken phone with inly TWRP installed.

problem 2: when wanting to reinstall the backup in twrp i got some error saying the \system partition was not mounted. searching online gave me a solution to this problem, but reinstalling the backup still gave errors. on startup i got a "unsuccesful encryption" error, which yielded a useless backup. also after reformatting i got again the /system not mounted error, but now with a "partition is occupied or used" error. even the solutions online wouldnt work, so my online solution was to flash the original rom with QFIL.

solution:
trying to flash the rom resulted in a 1: sahara error, 2: a file not found error and 3: a phone not in EDL error.
when using the QFIL flasher provided by BadCluster i got the first two errors, and there was no quick way of resolving this problem. the post from @Nikorasu of another QFIL programm being used led to to the last error. this was good news as the file not found had been gone and now the only thing i had to do was putting the phone in EDL mode. MANY thanks to Nikorasu!!

trying to flash now resulted in an error where QFIL tried to put the phone in EDL mode, but failed to do so. a article online provided me with the following ADB commands to use. try to open to the bootloader/twrp recovery menu, and using the ADB cmd try to see if your device is connected (command "adb devices"). if so, type the command "adb reboot edl" and the phone will reboot in EDL mode. this was the only thing left to flash the stock rom back.

moral of the story!
1. only do this if you can miss the phone, this will save you a LOT of stress!
2. only do this if you can afford losing your phone!
3. in my case, the TWRP backup was pretty useles. only do this if you can afford to lose data!
4. THE MOST IMPORTANT ONE: NEVER GIVE UP! using the internet you can google every error and eventually get to a solution.

if you have any questions please ask
 
  • Like
Reactions: AMZMA

maxihinz

Member
Nov 13, 2010
24
0
Well there is no way i can flash the original rom in this device. Is there anybody wanting to do it remotely? I just keep getting the error firehose fhloader: fail the system can not find the specified file
 

anonOmattie

Member
Mar 3, 2019
28
11
  • Like
Reactions: erdalbadak

mahegbangar007

New member
Oct 8, 2015
3
0
Can you send me Z5 Pro, persist img, modemst1 and modemst2 img file because I just found out how to unbrick Z5 pro phone after it get bricked down while flashing ROM through qfil, when I was flashing ROM through qfil that time I have selected erase all before download after that my phone has dead it as not booting up full now I have just unbrick my phone using Z5 persist img I need Z5 pro ROM persist img and modemst1 and modemst2 img so that my phone will working full now sensors and sim card are not working due to this three file missing please send me these three img file.
 

anonOmattie

Member
Mar 3, 2019
28
11
Yes! This was the right tool to flash my device too.

Thank you very much

very good tohear! enjoiy your lenovo z5 pro

Can you send me Z5 Pro, persist img, modemst1 and modemst2 img file because I just found out how to unbrick Z5 pro phone after it get bricked down while flashing ROM through qfil, when I was flashing ROM through qfil that time I have selected erase all before download after that my phone has dead it as not booting up full now I have just unbrick my phone using Z5 persist img I need Z5 pro ROM persist img and modemst1 and modemst2 img so that my phone will working full now sensors and sim card are not working due to this three file missing please send me these three img file.

please take a look here:
https://www.mediafire.com/folder/c8x7kcznzwi6b,926v3389w8x7c,u7wu7b08zholk/shared
your files are in here.
 

SrCDA

Member
Mar 12, 2019
34
49
help-me

hello, please help me, I bought a lenovo z5 pro gt and tried to unlock the bootloader using the method that you spoke of the site of zuk, choose option Z2 pro and put the serial I got the file by email and I used the command: fastboot flash unlock unlock_bootloader.img, the cell unlock the bootloader but now he does not want to call anymore he got in bootloop n know what to do already tried to use the QFIL + FIRMWARE Stock of lenovo z5 pro gt (L78032)
QFIL LOG VVVVVVV




01:22:15: DEBUG: XML FILE (103 bytes): CharsInBuffer=709-103=606
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for program" /></data>
-------------------------------------------------------------------------------------------

01:22:15: INFO: TARGET SAID: 'INFO: Calling handler for program'
01:22:15: DEBUG: XML FILE (126 bytes): CharsInBuffer=606-126=480
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the SDCC Device slot 1 partition 0" /></data>
-------------------------------------------------------------------------------------------

01:22:15: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 1 partition 0'
01:22:15: DEBUG: XML FILE (131 bytes): CharsInBuffer=480-131=349
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device:1 slot:1 partition:0 error:0" /></data>
-------------------------------------------------------------------------------------------

01:22:15: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:1 partition:0 error:0'
01:22:15: DEBUG: XML FILE (123 bytes): CharsInBuffer=349-123=226
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: OPEN handle NULL and no error, weird 344377924" /></data>
-------------------------------------------------------------------------------------------

01:22:15: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 344377924'
01:22:15: DEBUG: XML FILE (132 bytes): CharsInBuffer=226-132=94
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open device, type:eMMC, slot:1, lun:0 error:3" /></data>
-------------------------------------------------------------------------------------------

01:22:15: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:1, lun:0 error:3'
01:22:15: DEBUG: XML FILE (94 bytes): CharsInBuffer=94-94=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
-------------------------------------------------------------------------------------------

01:22:15: DEBUG: Response was 'NAK'


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


01:22:15: {ERROR: handleProgram:8866 program FAILED - Please see log my filehouse error something like that.
 

SrCDA

Member
Mar 12, 2019
34
49
Hi, I have a Lenovo z5 pro gt tutorial. I have been able to do unbrick using this tut

Hi, I have a Lenovo z5 pro gt tutorial. I have been able to do unbrick using this tututorial + your lenovo z5 pro tutorial, create a post here on the site to help others I was already desperate
club.lenovo.cn/detail/5433752

---------- Post added at 04:16 PM ---------- Previous post was at 03:56 PM ----------

Hi, I have a Lenovo z5 pro gt tutorial. I have been able to do unbrick using this tututorial + your lenovo z5 pro tutorial, create a post here on the site to help others I was already desperate
club.lenovo.cn/detail/5433752

I can also unlock the bootloader but when I did the process the unload bootloader was unlocked and unbrick
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    --------------------------------> DISCLAIMER: <------------------------------------

    Guide for pure educational purpose. If you are going to use it, you do it to your risk and danger, I will not be held responsible if your phone will not work anymore.

    ----------------------------------------------------------------------------------------

    This tutorial is for relock the boot loader and restore original stock image on Lenovo Z5 Pro (L78031 - NO-GT version)

    For security reason, it's better if you do an Nandroid Backup with the TWRP.

    https://forum.xda-developers.com/z5...ow-to-unlock-bootloader-install-twrp-t3890402

    I'm not responsable if this operation brick you mobile phone!

    How to put the phone in EDL:
    1) The phone must be Turn-OFF.
    2) Press all two buttons at the same time vol+ and vol- and connect the cable USB.
    3) Put the phone in EDL mode only a second before to press the button DOWNLOAD (you must be very very fast otherwise you'll have Sahara error)

    Do it

    1) Download a Rom: Here you find the 293 and 320 Version (if one give you an error, try the other one), Here you find 342 Version
    2) Download and Install ADB Driver: Here or look the Attachments
    3) Download and Install Qualcomm Flasher: Qualcomm Flasher Qfil QPST V.2.0.1.9 or look the Attachments
    4) download and install Qualcomm Driver: For Windows 32 Bit - For Windows 64 Bit or look the Attachment 32 Bit - Attachments 64bit
    5) Download and Install Minimal ADB fastboot from the Attachments
    6) Follow this Steps:

    115201rdc5mpcllmomomm7.jpg.thumb.jpg


    115202eaa7a77a99sby47a.jpg.thumb.jpg


    115202kotfnd8nf7ow86x7.jpg.thumb.jpg


    115203h90q0tatr98tc98t.jpg.thumb.jpg


    115203pa1m3usl9xvlkxld.jpg.thumb.jpg


    115204bphi86kc8l6ghntn.jpg.thumb.jpg


    115204nrqo63jkepxh3zqr.jpg.thumb.jpg


    115205reqke55b1212r9vq.jpg.thumb.jpg


    115205ov0accuapvoccjv7.jpg.thumb.jpg


    115206cg83285552qh8c3c.jpg.thumb.jpg


    01.png


    02.png


    03a.png


    03.png


    04.png


    05.png


    06.png


    07.png


    08.png


    Now, Press all two buttons at the same time vol+ and vol- and connect the cable USB to the phone and quickly press Download button!

    09.png


    115211yimdb7vr1ckhmhhw.jpg.thumb.jpg


    115211sd92syf1mmh3mzey.jpg.thumb.jpg


    Done!

    Sahara Error: https://forum.xda-developers.com/showpost.php?p=77229641&postcount=2

    Sahara Error 2:
    url]
    1
    not working :crying: i can't post the image for u to see
    my cmd after entering "fastboot -i 0x2b4c oem lock" is "< waiting for any device >"
    what should i do?

    i have the same problem. i followed all steps from twrp and installing the stock rom, but after all the hastle im not able to lock the bootloader so i still cannot get any updates.
    i have the same problem where it says waiting for device. would be nice if there will be a solution for this to get future updates soon!

    ---------- Post added at 05:16 PM ---------- Previous post was at 04:49 PM ----------

    succesful flashed version 355
    THIS IS A VERY RISKY OPERATION AND I ALMOST LOST MY PHONE!!

    it didnt go as planned.
    i installed twrp and created a backup (not of system, is that nesecarry?) to get to when everything got messed up.

    and boi, did it get messed up...

    problem 1: when trying to install the rom with QFIL for the first time i got a sahara error and the phone lost its OS. i wanted to reinstall the twrp backup as i got really freaked out about losing my phone. somehow it did not get into edl or something and i failed the installation process and ended up with a broken phone with inly TWRP installed.

    problem 2: when wanting to reinstall the backup in twrp i got some error saying the \system partition was not mounted. searching online gave me a solution to this problem, but reinstalling the backup still gave errors. on startup i got a "unsuccesful encryption" error, which yielded a useless backup. also after reformatting i got again the /system not mounted error, but now with a "partition is occupied or used" error. even the solutions online wouldnt work, so my online solution was to flash the original rom with QFIL.

    solution:
    trying to flash the rom resulted in a 1: sahara error, 2: a file not found error and 3: a phone not in EDL error.
    when using the QFIL flasher provided by BadCluster i got the first two errors, and there was no quick way of resolving this problem. the post from @Nikorasu of another QFIL programm being used led to to the last error. this was good news as the file not found had been gone and now the only thing i had to do was putting the phone in EDL mode. MANY thanks to Nikorasu!!

    trying to flash now resulted in an error where QFIL tried to put the phone in EDL mode, but failed to do so. a article online provided me with the following ADB commands to use. try to open to the bootloader/twrp recovery menu, and using the ADB cmd try to see if your device is connected (command "adb devices"). if so, type the command "adb reboot edl" and the phone will reboot in EDL mode. this was the only thing left to flash the stock rom back.

    moral of the story!
    1. only do this if you can miss the phone, this will save you a LOT of stress!
    2. only do this if you can afford losing your phone!
    3. in my case, the TWRP backup was pretty useles. only do this if you can afford to lose data!
    4. THE MOST IMPORTANT ONE: NEVER GIVE UP! using the internet you can google every error and eventually get to a solution.

    if you have any questions please ask
    1
    Well there is no way i can flash the original rom in this device. Is there anybody wanting to do it remotely? I just keep getting the error firehose fhloader: fail the system can not find the specified file

    I had the same error, but another version of QFIL solved this for me.
    someone posted this in another topic:
    https://mega.nz/#!al0WlKTK!Zi23HafWA1uWVjc8kmEMQntW81LuW4_AXMo7BOSVkck

    I used this version to successfully flash my device.
    1
    My Z5 Pro, after trying GSI ROMs, restored to pie stock firmware via QFIL and bootloader locked still get red warning screen "device corrupted" after bootloader. However it can boot up and catch OTA.
    If I flashed oreo stock ROM using QFIL, there is no warning just booting. But updated to pie through OTA, red warning appears.

    I don't get warning screen when booting into recovery, no matter stock recovery or TWRP. It only appears when booting into system.

    Even I tried QFIL "erase all" and erase QCN to flash the initial ROM, then manually restored persist, modem, and EFS to get networks back. There is still the red warning with pie firmware.

    I can`t figure out what is the broken partitiom leads to the warning. Hope someone know the solution, or any way restoring deeper.


    I've had that problem with my Lenovo Z5 Pro and I solved it connecting the phone to PC, opening CMD inside ADB folder and typing:

    adb reboot "dm-verity enforcing"

    And that red warning vanished, but the yellow one persists.
    1
    What site did you download the file from? zui.com/iunlock?

    Are you using USB 2.0 or 3.0? I've experienced an issue with my phone, that I couldn't use adb with USB 3.0 controller so I need to use another PC with USB 2.0 instead. Try it out, maybe that works.