[RECOVERY] Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust

Breadcrust · Jan 7, 2016

Confirmed working with:

Exodus for ZUK Z1 5.1.1.

MOKEE CM Nightly 5.1.1.

Cyanogen OS OTAs thanks to @EagleEyedTom

/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards and so on. YOU are choosing to make these modifications.
* Bug reports or confirmation of working things are welcome.
*/

DO NOT USE ON AN ENCRYPTED FILE SYSTEM
For some reason I can't get my image to decrypt encrypted file systems. I lost all my data to this issue and at the moment I do not know of a fix. If you need to update or modify and encrypted partition you will have to back up EVERYTHING in your data partition and then do a complete wipe. Sorry.

This image has been recompiled with device checking disabled thank you to @TheCrazyLex for making the new .prop for the international variant.

Please note this image was compiled for the chinese variant of the ZUK Z1 it should work with the international version but zip flashing might not work properly due to device IDs. To flash zips with device specific build.props comment out all the device checks

There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.

First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.

Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.

Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type

Code:

adb devices

It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.

Code:

adb devices

You will also need to download the TWRP image from the spoiler below.

If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!

Type:

Code:

adb reboot bootloader

You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with

Code:

-i 0x2b4c

.

Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.

To check type:

Code:

fastboot -i 0x2b4c oem get-device-info

If it returns:

(bootloader) Device unlocked: true

Then you are ready to begin the flashing process.

Move the downloaded file to your platform tools folder and type:

Code:

fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE1.img

If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.

Special thanks to Anas Khan who made these awesome titles!

XDA:DevDB Information
Un-Official Breadcrust's TWRP 2.8.7.0 Recovery for ZUK Z1, ROM for the Lenovo Zuk Z1

Contributors
Breadcrust, TheCrazyLex
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: ZUK Z1
Based On: TWRP

Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2015-11-09

Created 2015-11-11
Last Updated 2016-01-17

Breadcrust · Dec 11, 2015

https://youtu.be/z5U5QIEbWtI

Please be aware if you are running the official Cyanogen OS image OTAs will not apply automatically, you will need to install the incremental ZIPs posted by Titokhan in the "How to root ZUK Z1" thread in the Help and Troubleshooting forum. They will be on your device if you have downloaded the system update but I am yet to find this directory. If anyone finds the download location please post below and test if they will apply.

I am very aware you can't install OTA updates due to the device ID mismatching. I just posted a solution in the Android Development thread HERE credit to Radii for helping me out while working on this with him. Drop us a thanks for our hard work? Means a lot to use you know Each one counts!

Klanac89 · Oct 7, 2015 at 1:27 AM

Mad props for this!

Gesendet von meinem Redmi Note 2 mit Tapatalk

plikmuny · Oct 8, 2015 at 8:06 AM

Hi Breadcrust, thanks for your wonderful work.
One doubt regarding Android 6.0 update, i saw a post on Internet about ZUK Z1 getting Marshmallow update and many users confirming it.
here is the link to this post explaining about updating procedure...http://apkmod4dl.com/howt-to/lenovo-zuk-z1.html

Can you confirm that it is working ? is Android 6.0 available for ZUK that soon ?
My ZUK is on my way, i am super excited to try new update with your recovery... Pls confirm it. Thanks in advance.

Breadcrust · Oct 8, 2015 at 11:27 AM

plikmuny said:
Hi Breadcrust, thanks for your wonderful work.
One doubt regarding Android 6.0 update, i saw a post on Internet about ZUK Z1 getting Marshmallow update and many users confirming it.
here is the link to this post explaining about updating procedure...http://apkmod4dl.com/howt-to/lenovo-zuk-z1.html

Can you confirm that it is working ? is Android 6.0 available for ZUK that soon ?
My ZUK is on my way, i am super excited to try new update with your recovery... Pls confirm it. Thanks in advance.

I'll be honest that post looks like a load of bollocks. The Android 6.0 source hasn't been released yet. Wait for Cyanogen 13 don't jump the gun and brick your phone.

Sent from my Z1 using Tapatalk

LethalOne · Oct 8, 2015 at 12:09 PM

This recovery is useless

Cannot flash ZIP with CyanogenMod:

cm-12.1-YOG4PAS2WM-ham-signed.zip

Error appears.

Breadcrust · Oct 8, 2015

LethalOne said:
This recovery is useless

Cannot flash ZIP with CyanogenMod:

cm-12.1-YOG4PAS2WM-ham-signed.zip

Error appears.

Worked for everyone else mate. You can't flash incremental OTAs over ZUI ROMs

It would also help if you told me the error instead of just saying it doesn't work. Especially considering other people have no issues.

Sent from my Z1 using Tapatalk

LethalOne · Oct 8, 2015 at 12:38 PM

Ah. Thanks for info.

But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.

Breadcrust · Oct 8, 2015 at 12:58 PM

LethalOne said:
Ah. Thanks for info.

But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.

It will flash any ZIP just like any other TWRP it has not been modified in any way. If it will not flash I think there is an error with the ZIP or its user error

LethalOne said:
Ah. Thanks for info.

But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.

Sent from my Z1 using Tapatalk

plikmuny · Oct 8, 2015 at 3:44 PM

Android 6.0 source code is released 2 days back already. source: cnx/software.com
i think it takes more time for CM 13 Rom for ZUK Z1...

Breadcrust · Oct 8, 2015 at 4:23 PM

I found that out off my Dad when I got home, looks dodgy though.

eagleeyetom · Oct 9, 2015 at 7:46 AM

It is dodgy and might be just a themed CM. We have to wait for the kernel source to come up first and then we can think about porting an AOSP. We must wait for an official CM though.

mk1129 · Oct 10, 2015

Thanks a lot for your work!!

.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s

.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c flash recovery temp\z1.twrp.2.8.7.0.By.Breadcrust-UPDATE2.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY [ 0.268s]
writing 'recovery'...
FAILED (remote: Invalid data)
finished. total time: 0.385s

.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c boot temp\z1.twrp.2.8.7.0.By.Breadcrust-UPDATE2.img
downloading 'boot.img'...
OKAY [ 0.309s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.313s

Both failed... in bootloader mode (penguin logo). Any idea?
Maybe it's because I've updated to ZUI 1.0.062. with OTA...

Breadcrust · Oct 12, 2015 at 1:45 PM

mk1129 said:
Thanks a lot for your work!!

Both failed... in bootloader mode (penguin logo). Any idea?
Maybe it's because I've updated to ZUI 1.0.062. with OTA...

Most likely an issue to do with ZUI I was working through some installation issues with someone the other night and when we got it working it was through booting the image instead of flashing due to the broken boot loader switch in CM. So I'd bet its the OS stopping you.

Sent from my Z1 using Tapatalk

plikmuny · Oct 13, 2015 at 4:42 PM

Breadcrust said:
There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.

FAQ

Q: Does this work for ZUI devices? A: No, I don't think so. You're welcome to test it and report back but so far I have only tested it with Cyanogen OS
Q: What can I get with this I can't with Cyanogen OS Recovery? A: You can flash unsigned ZIPs such as SuperSU or Xposed (Although I don't recommend doing this as I put my phone into a bootloop installing Xposed)

What will I need?

First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.

Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.

If Windows is giving you an error claiming the best driver is already installed right click Z1 or whatever it is named in Device Manager and click Update Driver.

Then click "Browse my computer for driver software" then click "Have disk" once you have done this browse to the extracted USB driver and open the .inf file it will show you three options select ADB device (Top one). Click yes to any warning and it should be mounted!

Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type

Code:

adb devices

It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.

Code:

adb devices

You will also need to download the TWRP image from the spoiler below.

Download

Android File Host for Z1 TWRP V1.2 - DOWNLOAD LINK
Android File Host MD5 for V1.2 = 3b6fa140737b769f838169e997f58975

~~Android File Host for Z1 TWRP V1.1 - DOWNLOAD LINK~~
~~Android File Host MD5 for V1.1 = 596816b87a45d78bed4063ac62fac137~~ - Compiling issue, uploaded without thorough test.

Android File Host for Z1 TWRP V1.0 - DOWNLOAD LINK
Android File Host MD5 for V1.0 = 62b72d5129591d6759bb1917868594f4 - Outdated, filled with bugs.

If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!

Guide

Type:

Code:

adb reboot bootloader

You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with

Code:

-i 0x2b4c

.

Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.

To check type:

Code:

fastboot -i 0x2b4c oem get-device-info

If it returns:

Then you are ready to begin the flashing process.

Move the downloaded file to your platform tools folder and type:

Code:

fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE1.img

If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.

Not working for me. Mine struck at infinite when I type get bootlock info..... I have to reboot my phone.
Mine came with CM 12.1. When I skip this step and go straight away to flash custom recovery, it says flashing failed, device locked!!!
But I have already enabled OEM bootloader unlock option and I am sure that bootloader already unlocked and enabled for tweaking. What should I do now?
I have all the drivers installed and I reinstalled twice just incase... But no help.

Anyone guide me on how to successfully flash custom recovery and root my device?

Thanks in advance

Breadcrust · Oct 14, 2015 at 11:37 AM

plikmuny said:
Not working for me. Mine struck at infinite when I type get bootlock info..... I have to reboot my phone.
Mine came with CM 12.1. When I skip this step and go straight away to flash custom recovery, it says flashing failed, device locked!!!
But I have already enabled OEM bootloader unlock option and I am sure that bootloader already unlocked and enabled for tweaking. What should I do now?
I have all the drivers installed and I reinstalled twice just incase... But no help.

Anyone guide me on how to successfully flash custom recovery and root my device?

Thanks in advance

Any fastboot errors are caused by the device as fastboot will never stop you flashing an image even if it's not supposed to be flashed like flashing recovery to system. Open a thread and appeal there I unfortunately can't help on that front. People do seem to be having issues with the international device I am starting to think it's different in someway for the Chinese one. Maybe the USB id is different.

Sent from my Z1 using Tapatalk

plikmuny · Oct 14, 2015 at 5:22 PM

Breadcrust said:
Any fastboot errors are caused by the device as fastboot will never stop you flashing an image even if it's not supposed to be flashed like flashing recovery to system. Open a thread and appeal there I unfortunately can't help on that front. People do seem to be having issues with the international device I am starting to think it's different in someway for the Chinese one. Maybe the USB id is different.

Sent from my Z1 using Tapatalk

Thanks for your Kind reply. How do i find out what my Device ID is ? I mean, how did you come to know that the device ID of Chinese ZUK Z1 is 0x2b4c ?
Sorry for being noob.

Breadcrust · Oct 14, 2015 at 6:05 PM

plikmuny said:
Thanks for your Kind reply. How do i find out what my Device ID is ? I mean, how did you come to know that the device ID of Chinese ZUK Z1 is 0x2b4c ?
Sorry for being noob.

Paul O'Brien at MoDaCo found it

Sent from my Z1 using Tapatalk

plikmuny · Apr 12, 2012 135 12 0

Breadcrust said:
Paul O'Brien at MoDaCo found it

Sent from my Z1 using Tapatalk

Can you tell me what it shows when you type adb devices ?

i am curious... that might help me with my Problem.

Thanks in advance.

Breadcrust · Oct 15, 2015 at 9:53 PM

plikmuny said:
Can you tell me what it shows when you type adb devices ?

i am curious... that might help me with my Problem.

Thanks in advance.

D:\AndroidSDK\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
c783ecb7 device

[RECOVERY] Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Developer Committee Lead / Retired Senior

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member