Development [RECOVERY] TWRP for ZenFone 8

Search This thread

Captain_Throwback

Recognized Developer
Hi, I have acutally the same problem
I am on latest stock Firmware Android 12 and no Password / PIN / is set
If I wipe Data in TWRP then my Storage is encrypted
But if I reboot once into system, I can't access the Data on my Phone in TWRP
Even if I try to save logs from TWRP they are not saved on the Phone
Am I something missing out?
If you Format Data while on 12, then it's expected that TWRP won't be able to decrypt. The current official version can only decrypt if the keys are upgraded from A11.

If you want to try a version that might decrypt on 12 if no password is set, even after you format data in TWRP, see the test version attached here.

NOTE: This version will have to be installed either from existing TWRP or in Android through Magisk/EXKM/FKM. If rooted, root will need to be reinstalled after the zip is flashed.
 

Attachments

  • twrp-installer-3.6.1_12-0_CPTB-20220413-01-I006D.zip
    33.2 MB · Views: 113

dvklin

Member
Apr 13, 2022
12
0
If you Format Data while on 12, then it's expected that TWRP won't be able to decrypt. The current official version can only decrypt if the keys are upgraded from A11.

If you want to try a version that might decrypt on 12 if no password is set, even after you format data in TWRP, see the test version attached here.

NOTE: This version will have to be installed either from existing TWRP or in Android through Magisk/EXKM/FKM. If rooted, root will need to be reinstalled after the zip is flashed.
How can I get root again after flashing into twrp, please tell me thank you. I tried to patch the boot after flashing twrp, but after flashing in twrp, it was gone. But to flash into twrp, root is gone, I can't have root and twrp at the same time
 
I don't use LineageOS, so I have no idea about the issue and what exactly needs to be "fixed". Since it works fine on stock, I have to assume the issue is with LOS, and since they provide their own recovery, there doesn't seem to be a need for anything additional on TWRP's end.

If someone wants to push a fix to Gerrit for this, and it doesn't negatively impact anything else, I'll gladly review and merge it.
Im sure, there is no need to fix anything. I have TWRP and LOS running since January.

Its more that flashing LOS overwrites TWRP with LOS Recovery.

Read here how to circumvent that. I'm not that deep into recoveries so im not sure if that has any downsides.
 

bnsmb

Senior Member
Aug 22, 2017
100
27
Frankfurt
Hi

is it possible to install TWRP using a CLI command in the adb shell after booting from the TWRP image?

regards

Bernd
 

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    Code:
    *** Disclaimer ***
    
    All flashing is done at your own risk!
    While nothing from this thread should break your device,
    don't come back here blaming anyone if it does!

    Introduction
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Images


    Prerequisites

    Installation instructions
    Fastboot Install Method:
    You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.

    Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed

    On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
    Code:
    adb reboot bootloader
    You should now be in fastboot mode.

    Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
    Code:
    fastboot boot twrp.img
    Now you are booted into TWRP, but it is NOT permanently installed. To install it permanently, use the "Flash current TWRP" option in the Advanced menu. This will install the currently booted TWRP permanently to both slots. NOTE: If you were previously rooted, you will need to re-install the root apk/zip as the TWRP install will overwrite it!

    Alternate Installation Method (requires prior TWRP installation, or if fastboot booted into TWRP already, start at step 3):
    TWRP Image Install method:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
    1. Download the latest version of TWRP appropriate for your device/firmware
    2. Reboot to TWRP
    3. Hit Install and tap the "Install Image" button in the lower right
    4. Browse to the location of the TWRP image on your device and select it
    5. Select "Install Recovery Ramdisk" from the partition list and swipe to flash
    6. (Optional) If previously rooted, re-install root apk/zip, as the TWRP install will overwrite root.

    Device Changelog

    TWRP Official Change Log

    Downloads


    Known Issues
    Device-specific
    • USB-OTG not working
    • Battery Status not working
    TWRP Upstream
    • Android 12 decryption only works if no password/PIN/pattern is set (i.e. only default password)

    Bug Reporting
    If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
    4rev3d.jpg

    If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    Additional Help/Support
    Live support is available on Zulip.
    6
    Maybe 3 to be safe