[RECOVERY][K920] Unofficial TWRP 3.2.1 (2018/02/24)

[Electry]

Team Win Recovery Project
for Lenovo Vibe Z2 Pro

The only true recovery built straight from 8.1 source code.
​

Key features:

• Based on android-8.1 TWRP sources and LineageOS 15.1
• "eng" build (no adb authorization required, ro.secure=0)
• Full /data HW decryption support (PIN/password/pattern)
• Full adb support - sideload, etc...
• Full SELinux support
• OTA updates support
• MTP & USB-OTG support
• F2FS support

List of partitions:

• System - /system
• Data - /data
• Persist - /persist
• Preload - /preload
• Firmware - /modem
• Bootloader - /aboot
• Boot (kernel) - /boot
• Recovery - /recovery
• Splash - /splash
• Misc - /misc
• FS Golden - /fsg
• ESF (NV Data) - /modemst1 & /modemst2
• MRD Data - /mrd

How to enter recovery?

Hold the POWER button and BOTH VOLUME buttons simultaneously until you see the TWRP logo.​

Downloads

TWRP_3.2.1-0_K920.img (2018/02/24) [15.5 MB] | Google Drive Mirror
TWRP_3.1.1-0_K920.img (2017/10/15) [12.7 MB]
TWRP_3.1.0-0_K920.img (2017/03/21) [12.7 MB]
TWRP_3.0.3-0_K920.img (2017/01/24) [14.7 MB]
TWRP_3.0.2-2_K920.img (2016/11/26) [13.3 MB]
TWRP_3.0.2-1_K920.img (2016/10/08) [10.7 MB]
TWRP_3.0.2-0_K920.img (2016/09/04) [10.7 MB]​

I am not responsible for anything that happens to your phone or computer. You have to understand what you are doing.​

Sources

Manifest: https://github.com/K920/android/tree/master/twrp
Device tree: https://github.com/K920/android_device_lenovo_kingdom/tree/twrp​

Dev Info

To build with 15.1 sources requires:

export ALLOW_MISSING_DEPENDENCIES=true
repopick -t oreo-lineage-build (omnirom)
Manual removal of "vendor" under out/.../recovery/root/​

Screenshots​

 

[Electry]

FAQ:
How do I flash this TWRP .img? (with PC)

1. If you haven't already, install ADB+Fastboot with drivers (I recommend this installer)
2. Enable ADB debugging on your phone (in Settings->Developer Options)
3. After connecting the phone to the PC, pop up may appear, tick Always allow from this computer and click OK
4. Extract downloaded recovery zip and copy .img file to C:/adb
5. Now open cmd line (press Start+R, type "cmd", press OK) and go to C:/adb (type "cd C:/adb" and hit Enter)
6. Reboot into bootloader (fastboot mode) (type "adb reboot-bootloader")
7. Your phone should now reboot into the bootloader (Little green android logo in the middle of the screen)
8. Flash the recovery.img (type "fastboot flash recovery recovery.img")
9. Finally, reboot!
10. Done!

Do I have to have unlocked bootloader?

Yes!​

Whenever I try to flash something, I'm getting ERROR 7. Help!

Reboot->Recovery, also make sure that your flashable zip isn't corrupted.​

I have formatted encrypted /data partition, now I can't mount it.

Reboot->Recovery​

Wrong password?!?

Reboot->Recovery​

Does this work on CN variants?

Yes!​

I can't flash my favorite ROM/.zip/we, this is not a kingdom_row device! (3.0.3+)

Yes, that's right. For the sake of using the same device tree as official Lineage OS, we're using common 'kingdom' device name. Many flashable .zips include safety mechanism to prevent them being flashed on unsupported device. If this is the case, ask the creator of your .zip to assert also on 'kingdom' device name. (e.g. by using TARGET_OTA_ASSERT_DEVICE), or edit the updater-script by yourself.​

 

[Alexander_Gostev]

reserved

Installation error - android\google\update-binary
CM13 (03092016)

 

[Electry]

Installation error - android\google\update-binary
CM13 (03092016)

It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).

 

[Alexander_Gostev]

It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).

Thanks, I understood and flashed through recoveri.
How do the two systems?

 

[Electry]

Updated to 3.0.2-1

/persist is now mounted RW

 

[HellAngelxxx]

thx, good work

 

[seekator]

Hello
After last update of CM 14.1 via OTA (20161104) I cannot re-flash TWRP when I trying to do that via TWRP i see error http://i.imgur.com/tJ4IZXf.png. Is it a problem with permissions or with something else ? Thx

 

[GuestK00219]

yes it's not working. you can use "fastboot flash recovery recovery.img"

Sent from my K920 using Tapatalk

 

[nodylex]

Hello friends,
I try to flash it but got this:

c:\adb>fastboot flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (17332 KB)...
OKAY [ 0.547s]
writing 'recovery'...
FAILED (remote: invalid data)
finished. total time: 0.758s

My phone is lenovo K920
Android version 5.0.2
Anyone can help me?
Thank you.

 

[remont5]

Do first unlock bootloader

Wysłane z mojego K920 przy użyciu Tapatalka

 

[Alexander_Gostev]

Updated to 3.0.2-1

/persist is now mounted RW

https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
не рабочая ссылка!
broken links!

 

[Electry]

https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
?? ??????? ??????!
broken links!

wtf? they're not broken

 

[Alexander_Gostev]

wtf? they're not broken

link does not boot at all, you can move?
ссылка не грузиться вобще, можете перезалить?

 

[seekator]

Hi all,
As I got instruction few posts before I tried to copy last version of twrp via ADB but it does not work. Installed TWRP 3.0.2-1 ,
When i try to push it via ADB I see an error -------------------------------------Ä»αÑñѽѡ¿Ñ ΓѽÑΣ«¡á
List of devices attached
89355fd4 recovery

-------------------------------------ÅÑαѺáúαπº¬á ó bootloader
-------------------------------------çá»π߬ root-shell
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.458s]
booting...
OKAY [ 0.019s]
finished. total time: 0.477s
-------------------------------------Åα«Φ¿ó¬á recovery
failed to copy 'fw\twrp.img' to '/sdcard/twrp.img': Read-only file system
CANNOT LINK EXECUTABLE "/system/bin/sh": library "libNimsWrap.so" not found
-------------------------------------ÅÑαѺáúαπº¬á ó recovery
-------------------------------------çáóÑαΦÑ¡«
-------------------------------------ì᪼¿ΓÑ ½εíπε ¬½áó¿Φπ.
internal mem is Read only mode ????
ROOT for ADB , USB enabled.
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx

 

[Electry]

Hi all,
...
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx

no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.

ps: I'm uploading 3.0.3-0 with F2FS support.

 

[Kurbatos]

Electry possible to make re-initialization of the system partition? To release the space not used by the system. She's stock was designed for Roma. A cm (lineage) is much easier.
And what topics can be done f2fs?

Отправлено с моего K920 (ROW) через Tapatalk
Sorry my google English)

 

[seekator]

no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.

ps: I'm uploading 3.0.3-0 with F2FS support.

OK Thanks . When you mentioned about unsupported script I have taken a look on it and .... Yep I used wrong zip with adb . When I tried right one I had another output . Strange, I had TWRP, ROOT but locked bootloader.
Then QPST to version 143 ,update to lollipop, bootloader , root, yours TWRP and I have last recovery, LineageOS :good:

UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .

 

[Electry]

UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .

That's an issue with gapps. TWRP 3.0.3-0 uses toybox instead of busybox and the 'unzip' executable/link is missing. Check my 2nd post (FAQ) there is a way around it, but you can just use 3.0.2-2 if that's easier.

EDIT: I've rebuild 3.0.3-0 with busybox included, so this shouldn't be an issue anymore.

 

[Kroeber]

whats new in TWRP 3.2.0-0? when the official release of twrp for our k920?