Sunday, 4 October 2015

Un-Official Breadcrust's TWRP 2.8.7.0 Recovery for ZUK Z1




Quote:









/*
* 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.
*/




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 - DOWNLOAD LINK
Android File Host MD5 = 62b72d5129591d6759bb1917868594f4




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:


Quote:









(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.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.



No comments:

Post a Comment