[RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 3

Search This thread

Captain_Throwback

Recognized Developer
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
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 flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
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.5.1_10-0:
  • Initial version
Older Device-specific versions:

TWRP Official Change Log

Frequently Asked Questions (FAQ)


Downloads

Known Issues
Device-specific
  • N/A
TWRP Upstream
  • Password/PIN decryption not working on Android 11 (default password and Pattern work fine) - Fixed as of official 3.5.0 release
  • ADB Sideload doesn't work, and Cancel button doesn't function either - Fixed as of 20201118-01 release
  • Secondary users aren't detected and don't decrypt - Fixed as of 20201118-01 release
  • Fastbootd unavailable - Fixed as of 20201118-01 release
We need your help!
Join the TWRP Testing group on Slack to help us test TWRP prior to official releases!
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, or find us in our IRC channel below. 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 via #twrp on Freenode with your IRC client or just click this link.
 

Attachments

  • TWRP_Flash_to_Opposite_Slot-CPTBv2.zip
    1.6 KB · Views: 640
Last edited:

Captain_Throwback

Recognized Developer
TWRP Official Change Log
Current version: 3.5.1:
TeamWin has prepared a mini release before Android-11 support.

Android 9 Branch only:
  • Build fixes in 7.1 tree - CaptainThrowback
  • SAR Update script name for clarity - CaptainThrowback
  • SAR: Don't follow symbolic links for block devices - bigbiff

Android 9 and Android 10 Branches:
  • Wrappedkey support running only on FBE devices - CaptainThrowback
  • TWRP App log information reduced - epicX67
  • Refresh details after system wipe and adb sideload - AdrianDC
  • Chinese translation updates - betaxb
  • Support keymaster 2 - PeterCxy
  • add tzdata to TWRP for timezones - CaptainThrowback
  • ParitionManager: support delayed adopted storage mount - PeterCxy
  • Support to start terminal from file manager directory - AndroiableDroid
  • Nano support - nebrassy
  • Add nano support to open files from file manager - CaptainThrowback
  • Include new magisk apk support to be installed by TWRP - ianmacd
  • Add support to change directory name where TWRP stores backups - epicX67
  • Add bash support - not the default shell - DarthJabba9
  • ORS support to format data - AdrianDC
  • Add support to flash both slots when flashing an image - epicX67
  • NL translation updates - ianmacd
  • Cleanup
    • Installation cleanup - remove dupe PackageExtractFn - klabit87
    • Remove logd-reinit service - CaptainThrowback
  • Fixes
    • Restore system root context - bigbiff
    • Only include keymaster 2 if tree supports it - CaptainThrowback
    • Strip lines containing '--' in language_helper.py - ianmacd
    • Unlocalized string fix - ianmacd
Older versions:

3.5.0:
For this release we are breaking down new support for devices based on android trees and device compatibility. For Pie and earlier devices, they will be built out of the android-9.0 branch. For devices that
are released with Android Version 10, they will be supported under the android-10 branch. The separation became apparent when a lot of functionality was dropped in the android-10 release last year.

You will notice a new version scheme. Devices that are built in the android-9 tree will be suffixed with 3.5.0_9.
Devices built in the android-10 tree will be suffixed with 10 like 3.5.0_10. Each device tree update will have a
final suffix for any updates made for the device like 3.5.0_10-1.

Android 9 only
  • Fix building in android-5.1 trees - CaptainThrowback
  • New QTI Haptics Support - AndroidableDroid
  • New TSPDriver Haptics Support - LameMonster82
  • Selinux restore issues - AndroidableDroid
  • OEM build fixes - Fighter19
  • More file extension support in Gui file selector - Mauronofrio
  • FBE Fixes - CaptainThrowback
  • Ozip Decryption - Mauronofrio
  • Don't use persist for recovery logs - bigbiff
  • Delay touch startup if necessary - bigbiff
  • Spanish translation Updates - R0rt1z2
  • Fix cache wiping on Slot A only devices - AndroidableDroid
  • Exclude dumpsys directory from backups - DarthJabba9
  • Gerrman translation Updates - 4ndyZ
  • HW Rotation during runtime (does not affect touch panel) - webgeek1234
  • API 24 fixes - AndroidableDroid
  • vold_decrypt error on unmount - CaptainThrowback
  • Multiuser - warn when users are not decrypted - noahajac
  • FDE encryption fixes - CaptainThrowback
  • Crypto state fixes - nebrassy
  • Chinese translation Updates - Whyle
  • Theme updates to match android-10 release: CaptainThrowback
  • Move TWRP App install to Advanced page - Dees_Troy
  • Update Russian Translation - f2065
Android 10
  • Omni 10 minimal support: CaptainThrowback
  • General Bringup: Bigbiff, Mauronofrio, AndroidableDroid, CaptainThrowback, ianmacd, DarthJabba9
  • Encryption support: Bigbiff, Mauronofrio, CaptainThrowback
  • Fastbootd support: Bigbiff
  • Install Support: Bigbiff, CaptainThrowback
  • Magisk Support: Bigbiff
  • Backuptool Support: Chaosmaster
  • Apex support: Bigbiff
  • Dynamic Partition Support: Bigbiff
3.4.0:
System As Root (SAR)
  • Fix backup and restore using SAR - dianlujitao
  • System mount point - Chaosmaster
  • ORS - Chaosmaster
  • Zip install - Chaosmaster
  • system_root bind mount to /system - Chaosmaster
  • Autodetection of SAR - Chaosmaster
Digest
  • fix creation of digests for sub-partitions (was bugfix applied to many devices since last year) - Bigbiff
Encryption
  • ext4Crypt Wrapped Key Update - Peter Cai
  • Fix upgrading encryption key if export fails - Peter Cai
  • Fix wrapped key support for devices without metadata partition - mauronofrio
  • Don't skip decryption when using block map file in order to write to /data in ORS - CaptainThrowback
  • FDE - Decrypt master key first - AndroidableDroid
  • vold_decrypt - set Android version and patch level automatically - CaptainThrowback
  • Set wrapped decrypt support by twrp flag - Peter Cai
  • Don't try wrapped support unless needed - mauronofrio
  • restore ext4 policy on /data/cache - Bigbiff
  • multiuser decryption - Noah Jacobson
  • FDE retry - AndroidableDroid
TWRP App
  • unmount system after checking for app - Bigbiff
Prebuilt updates
Compilation Fixes
  • TW_EXFAT_FUSE compilation fixes - Bigbiff
  • libuuid - cryptomilk
  • 'system/etc/ld.config.txt' not found error - Martin Dünkelmann
Language Updates
  • Portugal - Vasco Machado
  • Dutch - Ian Macdonald
  • Turkish - Fatih Fırıncı
  • Localisation of Backup_Tar - Ian Macdonald
ld.config.txt
  • updates for 8.x trees - CaptainThrowback
  • fix search path for /sbin - CaptainThrowback
  • /sbin should come first in search path - Ian Macdonald
General Bugs
  • Fix persistent log storage - SyberHexen
  • Compress Persistent Logs - Bigbiff
  • FB2PNG compilation errors - Bigbiff
  • exclude per_boot from backups - Darth9
  • Unmount all directories that point to same block device - AndroidableDroid
  • Blank screen fixes - Sean hoyt
  • Toolbox is default on android-9+ - mauronofrio
Cleanup
  • Typo fix in comment - VDavid003
  • newlines in ext4crypt - CaptainThrowback
  • TW_OEM_BUILD compilation issue - Patrick Zacharias
  • Fix Dependency requirements - Dees_Troy
  • Fix Symbolic links for BB and Toolbox - Dees_Troy
Bootloader Message
  • cleanup - Alessandro Astone
  • add configurable offsets
Error Cleanup
  • uevent errors and decryption error - mauronofrio
  • using copy_file to copy files from /etc - CaptainThrowback
  • ueventd access to /acct - early directory creation in init - cryptomilk
Haptics
  • TSP Driver - LameMonster82
  • QTI Input - AndroidableDroid
update_engine
  • read all asserts - Hernán Castañón
Resetprop
  • Add Resetprop from Magisk - CaptainThrowback & mauronofrio
  • compile from source - Chaosmaster
  • fix for android-7 and earlier - Chaosmaster
  • cleanup for spaces in properties - AndroidableDroid
Properties
  • Add Property override - Chaosmaster
Backuptool
  • mount system and vendor for A/B installs for backuptool - Chaosmaster
twrpTar
  • fix backup freezes when pigz and openaes are used - Fabrice Bellet
Zip Installs
  • Info for A/B zip installing to inactive slot - Chaosmaster
  • Reboot to system button now allows to be rebooted to different partitions after zip install
  • progressbar rework - Chaosmaster
Magisk updates
  • update binaries from source - AndroidableDroid
A/B Updater Zip Template
  • rewrite A/B installer zip from scratch using a new generic template and latest magiskboot - osm0sis
  • installer zip support for recovery_a/recovery_b partition ramdisks on newer 2SI SAR A/B devices - osm0sis
  • generate installer zips for all prod A/B devices - bigbiff
  • improve installer zip dump/write speed and add more error catching - arter97 & osm0sis
OZIP Encryption Support
  • add OZIP encryption - mauronofrio
File Selector
  • Support for more extensions in File Selector - mauronofrio
3.3.1:
  • Fix selinux issues during formatting - dianlujitao
  • Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
  • Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
  • Add option to uninstall TWRP app from /system - Dees_Troy
  • Create digest for subpartitions - bigbiff
3.3.0:
  • Merge AOSP 9.0 r3 (Dees_Troy)
  • Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
  • Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
  • vold decrypt updates (nijel8, CaptainThrowback)
  • Support vibration on LED class devices (notsyncing)
  • Metadata decrypt support for Pixel 3 (Dees_Troy)
  • Support rotating the display via build flag (vladimiroltean)
  • Reboot to EDL mode button (mauronofrio)
  • Support MTP on FFS devices (bigbiff)
  • Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
  • Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
  • Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
  • TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
  • Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
  • Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
3.2.3:
  • Fix automatic installing of OTA zips on encrypted devices
  • Remove SuperSU from TWRP
  • Support both md5 and md5sum file extensions when doing MD5 checking for zip files
3.2.2:
  • adb backup fixes
  • OTA style update zips will now install automatically without prompting for decrypt
  • minor tweaks to handling date/time on Qualcomm devices
  • updates to some language translations
3.2.1:
  • minui fixes (cryptomilk)
  • Better android-8.0 compatibility in ROM trees (Dees_Troy)
  • Fix missing library in android-8.0 (nkk71)
  • Fix inconsistent SDCard naming (DevUt)
  • Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
3.2.0:
  • Allow restoring adb backups in the TWRP GUI (bigbiff)
  • Fix gzip backup error in adb backups (bigbiff)
  • Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
  • Better support for installing Android 8.0 based zips due to legacy props (nkk71)
  • Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
  • Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
  • Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
  • v2 fstab support (Dees_Troy)
  • Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
  • Various other minor bugfixes and tweaks
3.1.1:
  • Backups will now include adopted storage keys (Dees_Troy)
  • Fixed an adb restore issue (bigbiff)
  • Fixed rebooting when no OS is present (Dees_Troy)
  • Fixed line wrapping in the GUI terminal (_that)
  • Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
3.1.0:
  • vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
  • adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
  • tweak MTP startup routines (mdmower)
  • support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
  • support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
  • better indicate to users that internal storage is not backed up (Dees_Troy)
  • improve automatic determination of TW_THEME (mdmower)
  • minimal getcap and setcap support (_that)
  • try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
  • shut off backlight with power key (mdmower)
  • timeout during FDE decrypt (Dees_Troy and nkk71)
  • support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
  • boot slot support (Dees_Troy)
  • TWRP app install prompt during reboot (Dees_Troy)
  • support for AB OTA zips (Dees_Troy)
  • support new Android 7.x log command (Dees_Troy)
  • update recovery sources to AOSP 7.1 (Dees_Troy)
  • numerous bugfixes and improvements by too many people to mention
3.0.3:
3.0.2:
  • Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
  • Add Greek translation to some builds.
3.0.1:
  • 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
3.0.0:
  • Completely new theme - Much more modern and much nicer looking (by z31s1g)
  • True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
  • Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
  • Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
  • Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
  • Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
  • SuperSU prompt will no longer display if a Marshmallow ROM is installed
  • Update exfat, exfat fuse, dosfstools (by mdmower)
  • Update AOSP base to 6.0
  • A huge laundry list of other minor fixes and tweaks
Additional Notes
  • WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
  • Notes for themers: In addition to the updated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
  • Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
  • We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
2.8.7.0:
  • Initial ground work for software drawn keyboard (_that)
  • Fix handling of wiping internal storage on datamedia devices (xuefer)
  • Allow DataManager to set and read values from the system properties (xuefer)
  • Fix crash when taking screenshots on arm64 devices (xuefer)
  • Fix error message after an ORS script completes (Dees_Troy)
  • Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
  • Add system read only option – more details below (Dees_Troy)
  • Add resize2fs and GUI option to run resize2fs (Dees_Troy)
  • Fix crash loop caused by empty lines in AOSP recovery command file (_that)
  • Prevent duplicate page overlays such as multiple lock screens (mdmower)
Additional Notes
  • Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
  • System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
  • resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
  • This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
 
Last edited:

Captain_Throwback

Recognized Developer
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:Steps:
    1. Reboot into TWRP
    2. Navigate to Full Firmware zip and install, or sideload zip over adb
    3. Flash TWRP_Flash_to_Opposite_Slot-CPTBv2.zip to retain TWRP.
    4. (Optional) Reboot into TWRP and flash Magisk for root.

    Incremental OTA package - Through TWRP ONLY
    Prerequisites (for stock images, see attachments to this post):
    • 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_to_Opposite_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_to_Opposite_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)
 

Attachments

  • 17.0823.2012.122-stock_boot_dtbo_recovery_images.zip
    36.7 MB · Views: 128
  • 17.0823.2012.131-stock_boot_dtbo_recovery_images.zip
    36.7 MB · Views: 36
  • 17.0823.2102.143-stock_boot_dtbo_recovery_images.zip
    36.7 MB · Views: 19
  • 18.0410.2101.80-stock_boot_dtbo_recovery_images.zip
    44.7 MB · Views: 1
  • 18.0410.2102.96-stock_boot_dtbo_recovery_images.zip
    44.7 MB · Views: 10
  • 18.0410.2102.98-stock_boot_dtbo_recovery_images.zip
    44.7 MB · Views: 9
  • 18.0410.2102.107-stock_boot_dtbo_recovery_images.zip
    45.5 MB · Views: 1
Last edited:

Monsibd

Member
Aug 14, 2018
6
0
about twrp

hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
 
Last edited:

Captain_Throwback

Recognized Developer
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.
 

Captain_Throwback

Recognized Developer
sup guys. been a long time that i havent installed twrp.

jiz wanna ask if i have twrp if OTA is still possible?
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.

EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.
 
Last edited:

Monsibd

Member
Aug 14, 2018
6
0
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.

hey there, thank you so much my man you fixed my mobile! you rock!! :D <3


however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
 
Last edited:

Captain_Throwback

Recognized Developer
hey there, thank you so much my man you fixed my mobile! you rock!! :D <3


however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
Where is the recovery log from the TWRP boot where it was prompting for password? The OP clearly states that a log should be included with any issues. Do me a favor and try flashing the TWRP attached and let me know if it boots.

https://drive.google.com/file/d/1-2qBUqYv0AWnvqDmxIY2DqRqwG5dSwHg/view?usp=drivesdk

If it does, I can adjust the TWRP image linked in the OP. If it doesn't, I'll definitely need a log to understand the issue, and your device details.
 

Captain_Throwback

Recognized Developer
So I did some testing, and it appears that if you're not on the latest .58 firmware, then TWRP may not boot successfully. Can anyone that has had an issue with booting TWRP please report their device variant and firmware version? If you're not on the latest, please update and then try TWRP.

WW 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/...US_I003_1-ASUS-17.0823.2007.58-1.1.9-user.zip
CN 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS661KS/UL-ASUS_I003_1-CN-17.0823.2007.58-1.1.45-user.zip

If that doesn't work, let me know.


EDIT: Actually I need to check again. I think I broke my TWRP tree so it may not be the kernel at all :/
 
Last edited:

Monsibd

Member
Aug 14, 2018
6
0
Hey sorry for taking such a long time to reply, life happened to me.

I am on the latest firmware (cn_17.0823.2007.58)


I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:


Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?

Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
 
Last edited:

chacho_2me

Senior Member
Aug 19, 2011
816
97
ASUS ROG Phone 3
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.

EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.


so basically installing twrp can still be overwritten when flashing original firmware from asus
.thanx sir
 

Captain_Throwback

Recognized Developer
Hey sorry for taking such a long time to reply, life happened to me.

I am on the latest firmware (cn_17.0823.2007.58)


I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:


Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?

Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
So maybe there is some difference with the CN device that's causing this issue. Everyone it's working for is running WW firmware. Not sure what's different with the CN firmware, but that's unsettling.

Since the full firmware file is available, you can just use payload dumper to get the stock recovery image.

And yes, a clean flash with logs would be great, thanks!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Official TWRP is now available!
    7
    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
    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 flash recovery_a twrp.img
    fastboot flash recovery_b twrp.img
    Code:
    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.5.1_10-0:
    • Initial version
    Older Device-specific versions:

    TWRP Official Change Log

    Frequently Asked Questions (FAQ)


    Downloads

    Known Issues
    Device-specific
    • N/A
    TWRP Upstream
    • Password/PIN decryption not working on Android 11 (default password and Pattern work fine) - Fixed as of official 3.5.0 release
    • ADB Sideload doesn't work, and Cancel button doesn't function either - Fixed as of 20201118-01 release
    • Secondary users aren't detected and don't decrypt - Fixed as of 20201118-01 release
    • Fastbootd unavailable - Fixed as of 20201118-01 release
    We need your help!
    Join the TWRP Testing group on Slack to help us test TWRP prior to official releases!
    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, or find us in our IRC channel below. 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 via #twrp on Freenode with your IRC client or just click this link.
    6
    New TWRP update (3.5.1) is out! See OP change log for details/updates.
    4
    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:Steps:
      1. Reboot into TWRP
      2. Navigate to Full Firmware zip and install, or sideload zip over adb
      3. Flash TWRP_Flash_to_Opposite_Slot-CPTBv2.zip to retain TWRP.
      4. (Optional) Reboot into TWRP and flash Magisk for root.

      Incremental OTA package - Through TWRP ONLY
      Prerequisites (for stock images, see attachments to this post):
      • 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_to_Opposite_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_to_Opposite_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)
    4
    Hello! Does this TWRP install permanently and does it see Data on Rog Phone 3? On HTC U12+ TWRP doesn't see Data..
    A few of things, since you're comparing two completely different devices:
    1. On the HTC U12+, TWRP can decrypt data perfectly fine on stock Oreo, and on newer Android version GSIs. The only thing it can't decrypt is HTC's stock Pie ROM, because they put some non-standard stuff in it.
    2. The HTC U12+ uses Full-Disk Encryption (FDE), not File-Based Encryption (FBE), like most newer devices.
    3. The HTC U12+ doesn't have a recovery partition, so installing TWRP is a completely different experience on that device.
    4. The HTC U12+ doesn't use dynamic partitions (this isn't really related to TWRP; now I'm just showing off)
    That being said, I will now answer your questions (since you felt the need to qualify your question by mentioning an unrelated device, I felt I should at least clarify your inaccuracy):
    1. Does this TWRP install permanently?
      • If you follow the instructions in the OP and read the FAQ, then you would already know the answer to this. Hint: "fastboot boot" only boots TWRP without installing it, but "fastboot flash" installs it permanently, and only one of those is possible on this device.
    2. Does [TWRP] see Data on Rog Phone 3?
      • If it's not listed in the "Known Issues" section of the OP, then it's not an issue.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone