TeamWin/Team-Win-Recovery-Project

ZUK Z2 Pro - TWRP 3.3.1

Opened this issue · 0 comments

  • I am running an official build of TWRP, downloaded from https://twrp.me/Devices/
  • I am running the latest version of TWRP
  • I have read the FAQ (https://twrp.me/FAQ/)
  • I have searched for my issue and it does not already exist

z2_row
3.3.1-0-z2_row

WHAT STEPS WILL REPRODUCE THE PROBLEM?

Have TWRP access encrypted partitions.

WHAT IS THE EXPECTED RESULT?

Mounted partitions can be accessed through USB cable via mtp or if ADB sideload activated, able to talk with the phone using the adb commands.

WHAT HAPPENS INSTEAD?

Device isn't detected by Windows (tested with Windows 10 host, but also Windows 7 VM) nor Linux host (OpenSUSE LEAP)

ADDITIONAL INFORMATION

When flashing TWRP 3.2.3-1-z2_row, device is detected by Windows/Linux. However, decrypting the partitions does not work in this release.

I have to downgrade to TWRP 3.2.3-1 if I want to completely wipe the device and load a new ROM on the phone. After installation is finished, upgrade recovery again to 3.3.1-0 to be able to access the filesystem if a ROM upgrade zip got downloaded OTA. (Running Mokee 90.0)

Did something considerable change on kernel / available drivers or modules level change between 3.2 and 3.3 ?

I don't have a recovery.log
dmesg: 413 Request Entity Too Large
dmesg.log