[Recovery] Unofficial TWRP 3.0.2-0 for ZUK Z1

[crian]

It's needed?
I use to l to connect via fastboot,
But never used with adb

If you haven't installed the correct adb driver you need to specify the vendor id.
Take a look at the description of breadcrust's Twrp thread.
Is your computer running Windows or Linux?

 

[bartito]

If you haven't installed the correct adb driver you need to specify the vendor id.
Take a look at the description of breadcrust's Twrp thread.
Is your computer running Windows or Linux?

I'm using Ubuntu (Linux)
I'm not using vendor ID with other Twrp versions
And also don't using vendor ID when connecting via adb and the phone running in normal mode

 

[crian]

I'm using Ubuntu (Linux)
I'm not using vendor ID with other Twrp versions
And also don't using vendor ID when connecting via adb and the phone running in normal mode

Try to create a udev rule or simply make this:
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in and save the file
- run on terminal "adb kill-server" and "adb start-server"

For udev take a look at this https://wiki.cyanogenmod.org/w/UDEV

 

[mCdroid09]

Thank you for this

hello bro, my current os is zui its rooted the bootloader is unlock the question is, can i flash this directly on flashify and flash cos? Thank you, hoping for your fast respond

 

[bartito]

Try to create a udev rule or simply make this:
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in and save the file
- run on terminal "adb kill-server" and "adb start-server"

For udev take a look at this https://wiki.cyanogenmod.org/w/UDEV

works! Thanks!

 

[enyx.es]

When i install gapps aroma version is this recovery the console stays at background and make impossible read the aroma options

Enviado desde mi Z1 mediante Tapatalk

 

[allouh]

Would latest OTA update work with this recovery or will i face problem?

 

[quocviethp1909]

thanks

Hey folks,

As you may have noticed, TWRP 3.0.0 is out and brings a plethora of changes.

Screens are shamelessly taken from AndroidPolice

I managed to compile TWRP for our white Chinese phones. You can grab it from the link below. Flashing a custom recovery is always risky. Make a backup of your current recovery first!

DOWNLOAD

To flash it use Flashify, raw image flash in TWRP or enter the fastboot mode and execute the following command:

fastboot -i 0x2b4c flash recovery TWRP-3.0.0-ham.img

If you want to play with it by yourself, fork the source from my GitHub and try to fix something if it's broken

https://github.com/eagleeyetom/android_device_zuk_ham

Here's the recent source:
https://github.com/omnirom/android_bootable_recovery/tree/android-6.0

I will keep this thread updated once the new releases arrive. If it's stable enough, it's worth to speak with Dees_Troy to include it as official.

Working:
- Installation
- Wiping
- Sideloading
- MTP

Not Working:
-USB-OTG

Not tested:
-Encryption

Credits:
Diogo Ferreira for maintaining the CM wonderfully
@MrColdbird and @JoaoPaulo for their TWRP config

Enjoy!

XDA:DevDB Information
TeamWin Recovery Project 3.0, Tool/Utility for the Lenovo Zuk Z1

Contributors
eagleeyetom

Version Information
Status: Beta

Created 2016-02-07
Last Updated 2016-02-08

thanks very much

 

[bartito]

In the past I suffered a issue with this TWRP version and can't connect via adb with the phone while in recovery.

Advised to add the device id to the adb_usb.ini file (http://forum.xda-developers.com/showpost.php?p=65662688&postcount=43) and it seems to work fine... but not... the problem continues...

Imagine this scenario:

1) Phone configured and provided permission to connect (in normal mode) from the PC to the device using adb commands
2) Reboot into recovery
3) Connect PC with the phone using adb (it connects)
4) Disconnect the cable
5) Wipe the device
6) Connect PC with the phone using adb (it doesn't connect and the issue related here is displayed)

Also imagine this scenario:

1) Phone configured but never before provided permission to connect (in normal mode) from the PC to the device using adb commands
2) Reboot into recovery
3) Connect PC with the phone using adb (it doesn't connect and the issue related here is displayed)

 

[eagleeyetom]

A new version of the recovery is out!
*fanfares*
Here's a brief changelog:

• support new CM 13.0 pattern encryption (sultanqasim)
• fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
• libtar updated to latest upstream and fixes (jcadduono)
• fixes for loading custom themes (_that)
• TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
• translation updates – added Italian, Czech and Polish and significant updates to Dutch
• progress bar improvements – progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
• fix input box text display (Dees_Troy)
• Reboot option after zip install complete (bigbiff)
• Other mostly invisible bug fixes and improvements

As far as I tested, the archive encryption works. You can set a password and TWRP asks for it when you want to restore the data. Putting a wrong one obviously doesn't work. I still don't have an USB-C pendrive (nor plan to get one TBH), so I'm leaving the MTP as a WIP. I will play with AROMA a bit to see why it's overlaying - possibly it's a recovery bug. We'll see.

Links to the download are in the OP. Enjoy!

 

[Kontex]

@eagleeyetom Please Update version numbers in the text to 3.0.1 instead of 3.0.0. Please update the download link which still leads to version 3.0.0 To make life easier in the future simply write the version number only in title and in the dowloadlink. Thanks for your work.

 

[eagleeyetom]

@eagleeyetom Please Update version numbers in the text to 3.0.1 instead of 3.0.0. Please update the download link which still leads to version 3.0.0 To make life easier in the future simply write the version number only in title and in the dowloadlink. Thanks for your work.

I will post it soon. I noticed that there are some bugs in the build, so I want to squeeze them before making it public. Stay tuned, I will deliver it shortly.

 

[omgtehchap]

There's a bug with the device name, it recognizes it as Z1 and not as ham and doesn't let me flash cyanogenmod nightlies.

Good work and awesome speed man, I'm sure you're gonna fix it

 

[eagleeyetom]

There's a bug with the device name, it recognizes it as Z1 and not as ham and doesn't let me flash cyanogenmod nightlies.

Good work and awesome speed man, I'm sure you're gonna fix it

Yeah, I know. I was trying to re-write a device tree to make it easy to maintain. However my tree doesn't work with AROMA, so I decided to stick with the CM one. I'm uploading my build as we speak. Everything should work just like with the previous version.

 

[bartito]

Anyone has tried to access a crypted phone using this new TWRP version?
I have tried 3.0.1 in my development device (a Nexus 4) and the recovery always says that impossible to access
the data. I have tried the password some times and I'm pretty sure that I haven't introduced a typo but it doens't work at all...

 

[btme]

Anyone has tried to access a crypted phone using this new TWRP version?

I did, didn't work.

 

[bartito]

I did, didn't work.

Really I'm not sure why developers (I'm not refering to the OP) are adding lines to the changelog without trying it

 

[Kontex]

Really I'm not sure why developers (I'm not refering to the OP) are adding lines to the changelog without trying it

I think not all developers are using an encrpyted phone that is why they can not test it. Developers are Users too. - I can confirm. With 5.1 Android encrypted phones don't work.

 

[eagleeyetom]

Version 3.0.2-0 is out. I've spent a couple of hours trying to figure out what is wrong with AROMA. It works with Aroma File Manager, but OpenGapps craps itself. I guess we have to use the standard packages - at least for now. This version is compiled on CM sources, as Omni one gives some bad looking error with system unmount.

Bugs remain the same. If you have ideas how to improve the recovery, feel free to mess with the source.

Oh before I forget - I've added an ability to backup/restore firmware, splash and persist partitions. This should be useful if you plan to mess around with radios.

Enjoy!

 

[lolakuo95]

Good job!!!!

Sent from my Z1 using XDA-Developers mobile app