[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series

[Captain_Throwback]

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

• Unlocked Bootloader

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:

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:

fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img

fastboot reboot

Alternate Installation Method (requires prior TWRP installation):

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. NOTE: This will only flash TWRP to the active slot!

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 recovery from the partition list and swipe to flash

Device Changelog

Current version: 3.6.0_11-0:

• Initial version

Older Device-specific versions:

N/A

TWRP Official Change Log

Frequently Asked Questions (FAQ)

Downloads

Download
Latest Official versions

Sources
TWRP
Device tree
Common tree
Kernel source

Known Issues

Device-specific

• N/A

TWRP Upstream

• N/A

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.

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.

 

[Captain_Throwback]

Frequently Asked Questions (FAQ):

1. How do I install an OTA while rooted and keep TWRP/root?
   Full Firmware zip - in Android
   Prerequisites:
   • Full Firmware zip for new software
   • TWRP installed to the current slot
   • Magisk Manager
   Steps:
   1. Put Full Firmware zip on root of internal storage
   2. Reboot the device so that the update is detected
   3. Install the update
   4. After install completes BUT BEFORE REBOOTING, install "TWRP A/B Retention Script" module by @osm0sis in Magisk Manager
   5. Install Magisk "to Inactive Slot (After OTA)" in Magisk Manager
   6. Reboot and you're updated with TWRP and root retained
   
   Full Firmware zip - Through TWRP
   Prerequisites:
   • Full Firmware zip for new software
   • TWRP_Flash_tpposite_Slot-CPTBv2.zip
   • Magisk zip (optional)
   Steps:
   1. Reboot into TWRP
   2. Navigate to Full Firmware zip and install, or sideload zip over adb
   3. Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
   4. (Optional) Reboot into TWRP and flash Magisk for root.
   
   Incremental OTA package - Through TWRP ONLY
   Prerequisites:
   • Current software stock boot.img
   • Current software stock recovery.img
   • Current software stock dtbo.img (only if modified by Magisk or custom ROM)
   • Incremental OTA zip for current software to new software
   • TWRP_Flash_tpposite_Slot-CPTBv2.zip
   • Magisk zip (optional)
   Steps:
   1. Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
   2. Boot into TWRP.
   3. Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
   4. Flash the incremental OTA zip.
   5. Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
   6. (Optional) Reboot into TWRP and flash Magisk for root.
   The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
   
   
2. What's the deal with these dynamic partitions?
   Here's Google's explanation.
   
   
3. Why can't I write to system?
   Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
   
   
4. How do I make modifications to system?
   On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
   
   
5. Can I boot the recovery image without flashing it?
   No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
   
   
6. What is fastbootd?
   Here's Google's explanation.
   
   
7. Can I back up the system/vendor partition separately?
   No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
   
   
8. Why can't I restore X partition (read-only error)?
   Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
   (I will not provide any additional details on this procedure)

 

[Captain_Throwback]

Reserved

 

[Captain_Throwback]

Big thanks to @Buffydamion for all his tireless testing and log-providing to get this TWRP in fully working order!!

Hopefully there aren't any bugs besides the upstream ones listed in the OP, but if there are, I'll do my best to figure them out.

Since I don't have the device, I'll have to rely on all of you for logs and feedback.

Enjoy!!

--Cap

 

[Volski_]

How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.

 

[Captain_Throwback]

How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.

@Dees_Troy isn't the only person on the TWRP team.

@bigbiff has been working tirelessly to add Android 10 support to TWRP, with help from @mauronofrio, @androiabledroid, myself and others. TWRP is open-source and a team effort. As you'll notice, there are still some upstream bugs that need to be fixed, which is why the official TWRP hasn't been updated yet. But it's working well enough to release it for devices that need it, and when the official TWRP is ready, these devices will have official support.

 

[N4KA]

Works fine for me. Thanks!
The data partition was already partitioned to f2fs.

Flashed magisk and have a rooted phone now. Perfect!

 

[Captain_Throwback]

Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.

I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.

--Cap

 

[Captain_Throwback]

Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.

I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.

--Cap

So I had to remove the above build as it didn't boot. Building a new one now and hopefully it'll work. I'll keep everyone posted.

 

[Captain_Throwback]

New release 20200922-14

There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.

Change Log:

• Update prebuilt kernel to source built with @aleasto's patch for f2fs
• Set data filesystem to f2fs in recovery fstab
• Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works

 

[luiscaproducer]

Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...

Any thoughts?

 

[Captain_Throwback]

Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...

Any thoughts?

That is normal for dynamic partitions. The full super partition can be written but not the individual block devices.

 

[luiscaproducer]

Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance

 

[Captain_Throwback]

Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance

That is unrelated to TWRP being official or not, lol.

TWRP upstream will soon be updated to allow read/write of the system partition, but keep in mind that verity will need to be disabled for you to change any of the content, unless you don't want your device to boot .

--Cap

P.S. If you need to make modifications to system, you should use Magisk - it's made for this exact situation.

 

[Seosam]

There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.

Change Log:
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works

Works perfect for me. Thank you

 

[Captain_Throwback]

Update 20201001-02

Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)

 

[[email protected]]

Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)

------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:

1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.

Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?

Thank you for your answers.

 

[Captain_Throwback]

------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:

1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.

Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?

Thank you for your answers.

You don't need #3, as you're flashing TWRP to both slots in #2. That zip is for keeping TWRP after flashing a full firmware zip.

To update with an incremental OTA, you have to have the stock boot and recovery images from the current firmware available to be flashed in TWRP. You have to boot to TWRP and flash both stock boot and recovery, and then you can flash the incremental OTA. Then reboot to bootloader and flash TWRP, then reboot to recovery and flash Magisk for root.

 

[[email protected]]

Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?

 

[Captain_Throwback]

Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?

Correct.

And then you need to flash the zip that flashes TWRP to the opposite slot so you keep TWRP once you reboot. You'll have to reboot back into TWRP and flash Magisk if you want to keep root.