Database Info

[RECOVERY][UNOFFICIAL] ClockworkMod Recovery v6.0.4.5 for HTC Desire

This is a completely vanilla build of latest CWM (6.0.4.5) from cyanogenmod and evervolv sources! Thank You guys!
https://github.com/Evervolv
https://github.com/CyanogenMod
Download recovery.img:
http://d-h.st/eOU

Shmarkus said:
This is a completely vanilla build of latest CWM (6.0.4.5) from cyanogenmod and evervolv sources! Thank You guys!
https://github.com/Evervolv
https://github.com/CyanogenMod
Download recovery.img:
http://d-h.st/eOU
Click to expand...
Click to collapse
How to install?

Using fastboot commands
fastboot flash recovery recovery.img

Flashing instructions
polac said:
How to install?
Click to expand...
Click to collapse
connect your phone
reboot to fastboot (in one of the following ways)
- use phone shutdown menu (if reboot to bootloader is there)
- use adb: "adb reboot bootloader"
- start phone with holding down volume down + power
flash recovery via fastboot: "fastboot flash recovery <path to recovery here>/recovery.img
You should see 2 lines: writing recovery .. OK, flashing recovery.. OK.
If You already have older version of CWM, be sure to back up system first. When something happens during flash, You don't like the new CMW version or recovery image is corrupt for some reason, You can always flash Your old recovery back.
Your phone must be rooted and bootloader unlocked.
Check out more detailed instructions at http://www.androidauthority.com/desire-clockworkmod-touch-recovery-55857/ (in Instructions paragraph)
And as always: do it on Your own risk! Happy flashing!

Hi, does anyone knows if its possible to use Flashify to flash this?
Tks

stark_br said:
Hi, does anyone knows if its possible to use Flashify to flash this?
Tks
Click to expand...
Click to collapse
I think this shouldn't be a problem, since this is a standard image and I think that flashify uses DD or similar to write appropriate partition. You should check with the app developer, though!

HTC ONE SV only restart after 10s...

Hi, y have a problem with my htc one device, i I made a bad manipulation, and after that my phone only reboot after 5s of utilisation...
The version of my device is 4.2.2 and i used the recovery team win recovery project v2.6.3.2, the phone is rooted. In fact this problem was appared when i go to the menu bootloader, and i click on the button reboot in the menu fastboot and after that, only reboot after 10s.... Please help me !
Now my phone is totaly useless....

Whats your phone version (k2u & k2ul or cricket, boost version)?
Can you boot into recovery?

old.splatterhand said:
Whats your phone version (k2u & k2ul or cricket, boost version)?
Can you boot into recovery?
Click to expand...
Click to collapse
Yes, i can boot in recovery mod, and my version of my phone is 4.2.2 official. I have K2_UL, and i don't know the boost version. But my boot version is HBOOT : 2.21.0000 And radio : 1.18.40a.00.05

Ok, follow the Link in my signature to my index thread. You will find a Link to a stock 4.2.2 rom for k2ul. Flash this with twrp recovery (make a full wipe before) and don't forget to flash boot.img with fastboot cmd if you are S-on.

old.splatterhand said:
Ok, follow the Link in my signature to my index thread. You will find a Link to a stock 4.2.2 rom for k2ul. Flash this with twrp recovery (make a full wipe before) and don't forget to flash boot.img with fastboot cmd if you are S-on.
Click to expand...
Click to collapse
ok i found it : http://forum.xda-developers.com/showthread.php?t=2684620
[ROM][OTA UPDATE] DreamBeats Rom v2.2 K2_U/UL 4.2.2 OC UV MODS
This rom is official ?

and i have a question, i have install sdk on my pc, but i don't found Fastboot. How to download it ? And the link for download [ROM][OTA UPDATE] DreamBeats Rom v2.2 K2_U/UL 4.2.2 OC UV MODS is broken :/ And how to flash the rom via the cmd ? I'm a noob in this domain....

I'm on my phone, can't give you links right now or explain how to setup fastboot. But the web or xda are full of guides for that.
This rom was removed because it's against the rules of xda. Look for "stock odexed 4.2.2" rom in my index thread.

old.splatterhand said:
I'm on my phone, can't give you links right now or explain how to setup fastboot. But the web or xda are full of guides for that.
This rom was removed because it's against the rules of xda. Look for "stock odexed 4.2.2" rom in my index thread.
Click to expand...
Click to collapse
Damn it i have download the rom stock, and after dat i'm lost.. I d'ont understood how to install it via fastboot, i need a tutoriel

You flash the rom in recovery (this rom for k2ul).
After that, extract (only!) boot.img and copy it to your fastboot folder.
Flash the boot.img with fastboot with the following command:
Code:
fastboot flash boot boot.img
Wipe Cache and Dalvik Cache afterwards.
You will find all you need for fastboot in this Android.zip from attachment. Unzip it in a folder called fastboot and start cmd window there and you are good to go.
You can check before flashing boot.img if the phone is recognized with fastboot cmd
Code:
fastboot devices

old.splatterhand said:
You flash the rom in recovery (this rom for k2ul).
After that, extract (only!) boot.img and copy it to your fastboot folder.
Flash the boot.img with fastboot with the following command:
Code:
fastboot flash boot boot.img
Wipe Cache and Dalvik Cache afterwards.
You will find all you need for fastboot in this Android.zip from attachment. Unzip it in a folder called fastboot and start cmd window there and you are good to go.
You can check before flashing boot.img if the phone is recognized with fastboot cmd
Code:
fastboot devices
Click to expand...
Click to collapse
ok thanks, but the problem when i installed the driver for my HTC, i'm on window 8.64bits, the installshield don't worked. He have a problem of compatibilities. Because, when y used fastboot i have a trobleshooting : waiting for device

This is a problem you have to solve yourself, as i don't have Win 8.1.
But if you do a search here on xda there are a plenty of threads about drivers and windows.
Just a few:
http://forum.xda-developers.com/showthread.php?t=2714921
http://forum.xda-developers.com/showthread.php?t=2217396
http://forum.xda-developers.com/showthread.php?t=2633904
Another chance is to try other usb
ports or another PC.

I have same problem
MrPixel67 said:
Hi, y have a problem with my htc one device, i I made a bad manipulation, and after that my phone only reboot after 5s of utilisation...
The version of my device is 4.2.2 and i used the recovery team win recovery project v2.6.3.2, the phone is rooted. In fact this problem was appared when i go to the menu bootloader, and i click on the button reboot in the menu fastboot and after that, only reboot after 10s.... Please help me !
Now my phone is totaly useless....
Click to expand...
Click to collapse
I have a cricket HTC One SV i decided to boot my phone into recovery and wipe everything off it. now when i start it up it says HTC one and kinda freezes, but i can access fastboot and all lol i need to figure out how to make my phone work again.

I'm sorry, but i can't help you in this case, because there is no rom or backup for cricket which you can flash.

old.splatterhand said:
I'm sorry, but i can't help you in this case, because there is no rom or backup for cricket which you can flash.
Click to expand...
Click to collapse
Ok, after flash my phone with fastboot, i send the command fastboot flash boot boot.img, and the second command, the phone reboot cycles againt after 30s....

What means "after 30 seconds"? Does it boot into android os?
Try to restore this backup for k2ul: http://forum.xda-developers.com/showthread.php?t=2516661

old.splatterhand said:
What means "after 30 seconds"? Does it boot into android os?
Try to restore this backup for k2ul: http://forum.xda-developers.com/showthread.php?t=2516661
Click to expand...
Click to collapse
How to restor the back up with the command on fastboot ?

This is not for fastboot. This is for Twrp recovery.
And please answer my question from my lrevious post.

old.splatterhand said:
This is not for fastboot. This is for Twrp recovery.
And please answer my question from my lrevious post.
Click to expand...
Click to collapse
Yes, my phone boot on android interface, but 30s after the boot, the phone reboot cycle...

Ok, the wait with the backup and try this first (each step for its own):
- boot without simcard and see if it still reboots
- boot without sdcard and see if it still reboots
- boot while phone is plugged to a charger and see if it still reboots
Post the results here.

old.splatterhand said:
Ok, the wait with the backup and try this first (each step for its own):
- boot without simcard and see if it still reboots
- boot without sdcard and see if it still reboots
- boot while phone is plugged to a charger and see if it still reboots
Post the results here.
Click to expand...
Click to collapse
ok i have try this, and after 30s always reboot againt and againt cycle reboot :'(

[EXPERIMENTAL] [RECOVERY] [TWRP] Vivo V3 (non-max) Custom Recovery

[size=+2]TWRP Custom Recovery for Vivo V3[/size]
This is an experimental custom recovery for Vivo V3 based on TWRP version 3.0.2-0. You can use this recovery to flash custom ROMs and other flashable ZIPs. Full root access is available via an ADB shell.
Important - read before flashing
This is an experimental recovery. Whilst it will not prevent your device from booting back in to its normal ROM, I am not responsible for anything that goes wrong. If you flash this recovery to your device you will no longer be able to receive OTA updates for Funtouch OS and will have to install ROM updates manually unless you flash back to original stock recovery.
DOWNLOAD LINK
TWRP Custom Recovery
Flashing Instructions
1. Go to Settings, then More Settings, About Phone, and then tap Software version 10 times. It should now say that you are a developer.
2. Go to Settings, then More Settings, Developer Options. Turn on USB Debugging and Enable OEM Unlock.
3. Connect your phone to your computer. Authorize the USB debugging request on your phone screen.
4. If you haven't already, install ADB/Fastboot drivers. See here for further instructions: http://forum.xda-developers.com/showthread.php?t=2317790
5. Place the TWRP file from the download links above in your current directory
6. Completely power off your phone.
7. Hold the VOLUME DOWN and POWER buttons together until you see a black screen with FASTBOOT options.
8. In a command line window (or using Minimal ADB Fastboot if you used the above instructions), run this command:
Code:
fastboot flash recovery recovery-v3.img
9. If all went well the custom recovery has now been flashed. Use the volume buttons on your phone to select "RECOVERY" from the FASTBOOT options on-screen, then press the power button to confirm. You should now be in recovery mode! Congratulations!
Going back to stock recovery
Currently I have no original recovery image, so you will not be able to go back to stock recovery unless Vivo release it (unlikely).

Note to testers:
You can make a backup of the stock V3 recovery by flashing this TWRP recovery like so:
Code:
fastboot flash boot recovery-v3.img
fastboot reboot
This flashes the recovery to your boot partition rather than the recovery partition. You'll then be able to make a backup of the stock recovery in TWRP. After saving a copy to your SD card, flash back to your original boot partition like so:
Code:
fastboot flash boot boot-original-v3-1.8.20.img
fastboot reboot
Afterwards you can flash this TWRP to your recovery partition as normal and then you also have a stock recovery file too. Please upload it to this forum if you make a backup of stock.
The original stock boot image can be downloaded here if you need it: https://drive.google.com/file/d/0B0TtHsl8vcaLYTJhZHNHTFVfdGs/view?usp=sharing

hi
sorry for my bad english
i am tried with my v3 but when press the recovery button reboot to agin fastboot mode i analyse the recovery it is v3 max recovery img plz upload the device tree i will develiop the recovery
vivo v3 are sd 616 chip set and v3 max are sd652
---------- Post added at 01:57 AM ---------- Previous post was at 01:56 AM ----------
provide step for making the recovery for v3 max i will port to this v3

prabaecepct said:
sorry for my bad english
i am tried with my v3 but when press the recovery button reboot to agin fastboot mode i analyse the recovery it is v3 max recovery img plz upload the device tree i will develiop the recovery
vivo v3 are sd 616 chip set and v3 max are sd652
---------- Post added at 01:57 AM ---------- Previous post was at 01:56 AM ----------
provide step for making the recovery for v3 max i will port to this v3
Click to expand...
Click to collapse
Hello.
Making of custom recovery can be very difficult to explain but this thread tells you how to build TWRP recovery from source code.
Some pointers for building for Vivo V3 SD616:
1. Use Omni 5.1 sources instead of CM (see thread for more info)
2. Download latest V3 firmware from www.vivoglobal.com. Extract boot.img from the ZIP file and then use software called Android Image Kitchen (or similar) to extract the contents of boot.img.
3. From boot.img, find fstab.qcom file and make a note of its contents. You will need this information to make recovery.fstab file for TWRP.
4. From boot.img, find the "device fingerprint" and make a note of it. It's usually in default.prop file or can be somewhere else.
5. Make a note of the kernel command line options from the boot.img zImage split as they may be useful.
Finally:
If you manage to compile a full TWRP recovery for your phone but it does not boot, simply replacing the kernel from boot.img of latest firmware into the TWRP image may fix this. (again use Android Image Kitchen or similar).
I hope this helps. Sorry I can't be of more assistance.

hi i am upload the orinal stock recovery
plz bulid to the twrp our vivo v3
https://docs.google.com/uc?export=download&confirm=2Gic&id=0B-Tl2AxV63-aOFNYTGZvMXQzQ3c

prabaecepct said:
hi i am upload the orinal stock recovery
plz bulid to the twrp our vivo v3
https://docs.google.com/uc?export=download&confirm=2Gic&id=0B-Tl2AxV63-aOFNYTGZvMXQzQ3c
Click to expand...
Click to collapse
Please try this one based on your stock recovery
https://drive.google.com/open?id=0B0TtHsl8vcaLR25fZkR1YkloUTA

Hi i flashed only stock recovery are booting

Can i flash this recovery for vivo y51l

Simple answer no
nimesh.batra93 said:
Can i flash this recovery for vivo y51l
Click to expand...
Click to collapse
you will brick your phone , Only flash your phone`s compatible ROMs and Recoveries i.e those of your phone model and cpu structure . Also Vivo has not open sourced its development as other phone makers so making it custom friendly is freakin pain in the >> A$% . anyhow :good: keep your hopes up someone might just make a custom rom for VIVO once they hack into it. Till then stay away from anything that is not VIVO

For those who need the official VIVO V3 (non-max) recovery, I have the latest version here:
Original recovery image (Global ROM, non max)

Hy @liamcrayden,
do i need to unlock bootloader before i flash the twrp?

Hy @liamcrayden @prabaecepct ,
Seem that i can't install twrp to this devices before unlock it's bootloader.
I've tried to enabled developer option > enable usb debugging > enable OEM unlock
Went to fastboot mode and type : " fastboot oem unlock "
And it just give error message "FAILED (remote: unknown command or device is lock)"
My Software Version is PD1524F_EX_A_1.12.14 Lolipop 5.11 Funtouch OS 2.5
Do i need to downgrade my version?
Really apprecited if anyone can help me.

langithitam said:
Hy @liamcrayden @prabaecepct ,
Seem that i can't install twrp to this devices before unlock it's bootloader.
I've tried to enabled developer option > enable usb debugging > enable OEM unlock
Went to fastboot mode and type : " fastboot oem unlock "
And it just give error message "FAILED (remote: unknown command or device is lock)"
My Software Version is PD1524F_EX_A_1.12.14 Lolipop 5.11 Funtouch OS 2.5
Do i need to downgrade my version?
Really apprecited if anyone can help me.
Click to expand...
Click to collapse
I can finally unlock my Vivo V3 (Not Max). See attachment below.

Sithu Htun said:
I can finally unlock my Vivo V3 (Not Max). See attachment below.
Click to expand...
Click to collapse
Finally I am also unlocked.
Sent from my Vivo vivo V3 using XDA Labs

Sithu Htun said:
I can finally unlock my Vivo V3 (Not Max). See attachment below.
Click to expand...
Click to collapse
I flashed supersu using TWRP but its showing device not rooted

Can anyone provide me the twrp.img file for Vivo Y12

[Guide] BQ Aquaris M10 (freezerhd) twrp & root

Hi,
as I did not find an English guide for rooting a BQ Aquaris M10 tablet and had some problems when trying to root my tablet, I want to post an guide how to root this tablet.
First of all:
- This guide is just from my experience and is not thoroughly tested. It's on your own if you risk bricking your device.
- If you get stuck in the process, in nearly all cases you can revert to stock with the MTK flash tool (can be found on mibqyyo.com) and the images provided by BQ on their website.
- I could not unlock the bootloader with the 1.X-Images (Lollipop), as the VolumeUp-Button didn't work in fastboot-mode and you need this button to confirm the unlock.
- Booting into recovery from start with VolumeUp and Power-Button. This doesn't work with the 1.X-images, too.
- This guide is not intended for users without experience in unlocking/rooting a device. If you don't know how to use adb, fastboot, recovery and things like that, don't try it!
- You will loose all your data during this process!!
Guide:
Modify boot.img, flash new firmware
SuperSU in systemless mode doesn't work on stock image, as the SuperSU installer can't extract boot.img. You have to repack boot.img.
I tried a SuperSU installer without systemless-mode, but device didn't even boot anymore afterwards.
This guide is derived from a Spanish tutorial on the HTCmania-forum ("Root M10 HD Marshmallow") by yquepongo. Thanks to him!
Get a firmware for your device from the BQ-website (should be Marshmallow, see above) and unzip it to a directory.
Extract the boot-verified.img in the firmware directory with a bootimg-extractor. There are various tools available.
I used bootimg.exe, because this was explained in the mentioned thread and I even used it with wine on Linux and it went well.
Search for cpiolist.txt in your extracted boot-verified.img and delete the first two lines:
mode:mtk
mtk_header_name:ROOTFS
Repack boot-verified.img and put it back in the firmware directory.
Flash the modified firmware with the MTK flash tool according to the tutorial on .mibqyyo.com (Title "Hard Reset for the smartphone range Aquaris and Aquaris E"). In short: Disconnect device, start Tool, load scatter file from firmware directory, choose firmware upgrade, start download, connect the device in power off state, download will start automatically.
This will delete all your data and put the device back to factory rom (hard reset)!!!
If you don't want to flash the complete firmware, you can flash only the boot-verified.img with "Download only" in the flash tool. I didn't try this and don't know if this is working.
Start your device, don't activate any security settings to prevent encryption of data partition.
Unlock bootloader, flash TWRP, install SuperSU
Enable developer settings on device and activate "OEM unlock" in developer settings.
Reboot into fastboot (adb reboot bootloader) and unlock bootloader (fastboot oem-unlock).
This will delete all your data!!! Reboot your system afterwards to make sure everything is still ok.
Do not activate any security settings and make sure your data partition is not encrypted!
The existing TWRP-image can't handle an encrypted data partition, you will end in a boot loop and have to start the whole process again!
Double check, your data partition isn't encrypted. (Settings - Security)
Reboot into fastboot (adb reboot bootloader) and flash the TWRP-image from the TWRP-site (fastboot flash recovery twrpxxx.img)
After reboot TWRP should start.
If you have checked that everything is ok (I would recommend a reboot into normal mode), you can install SuperSU with the standard-installer-zip in TWRP.
If you didn't modify your boot.img, the installer will give a warning that it cannot extract boot.img and you will not find any SuperSU on your system.
If you get stuck in bootloop afterwards you can start anew and try it with another image flashed with MTK flash tool. (Firmware 2.2.0 from December 2016 for freezerhd worked in my case)
Maybe some steps could be shortened, but I haven't tried it.

hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: unlokied-new.img
Setting up work folders . . .
Splitting image to "/split_img/" . . .
Android boot magic not found.
Error!. . .
Click to expand...
Click to collapse
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless

i opened a separate theme for this : https://forum.xda-developers.com/android/general/root-help-to-root-twrp-recovery-bq-t3536170

dreas74 said:
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
Click to expand...
Click to collapse
Sorry, but I can't help you there, as the M8 seems to be too different to the M10: I didn't have to unlock the boot.img, it was easy to unpack.

hi zrfl,
thanks for your reply. i contacted the developer osmOsis from the android image kitchen.
he will implement the bq specials in his tools.
more in the AIK thread: https://forum.xda-developers.com/showthread.php?t=2073775&page=108

this is the only way to root this device !!
thanks a lot ...

Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks

ZazOufUmI said:
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
Click to expand...
Click to collapse
Sorry, I have done this a long time ago and don't know what could be wrong:
You have the correct message, so unlock was successfull
You try to reboot in fastboot, so you flashed TWRP correctly in fastboot-mode
And I don't have the device at hand to try it myself. But I do have a few suggestions, what you could try:
Don't try to shorten procedure with unlock and flashing of TWRP at once. I'm not sure, but I think I had problems when I tried this. So do a normal reboot after unlock, before booting again into fastboot and flashing TWRP. (Now you have done this already )
I don't remember the proper boot command after flashing of TWRP. But
Code:
fastboot reboot-bootloader
doesn't make sense: You are already in bootloader.
Is there a boot-option in the bootloader where you could choose recovery?
Otherwise better power off and use the key-combination for booting into recovery: VolumeUp+Power.
I think, you have to repeat the procedure, as recovery seems to be overwritten: Boot into fastboot, flash TWRP, reboot into recovery. And avoid normal booting before first boot into TWRP!
Did you use the newest TWRP 3.1.0 from March 8th? I haven't tried this yet, so there could be the problem. You could try the previous one: 3.0.2 from last year.

Thanks, I succeed with the combo key (power + vol up) directly after the reboot process

Perfect it's working great now !

I did exactly what you wrote but SuperSU won't install because it cannot extract the ramdisk...

Hi @zrfl
Thanks for your posting!
I did as you suggested and successfully unlocked bootloader and installed TWRP 3.1.1. Your hint to modify the boot-verified was extremely helpful, as I wouldn't be able to unlock the bootloader otherwise.
However, I did not manage to install super su. And boy, I tried many different versions od regular/system/systemless supersu, each flashed according to the respective how-to.
I ended up either in a bootloop, or get stuck on the Android logo at boot.
Flashing goes well until this step:
"Decompressing ramdisk
--- Failure, aborting"
I checked ramdisk compression of boot with Carliv image Kitchen and it tells me that it already is set to "gz" and not another compression TWRP can't handle.
Please help me on how to flash SuperSu.
Thanks and best
Tom

There is something wrong: TWRP does not need a modified boot.img.
Maybe newer ROM-versions are different.

Solution for geting root on BQ M10 FHD on stock rom 2.6.2: Start with a fresh system and install magisk beta (not stable), reboot and root is granted!
tanks a lot to @scafroglia93!

Are there any Custom ROM's
For this Tablet like CM/LineageOS AOSP etc?
Googling reveals nothing and Considering all the kernel mods like hardcore and Ubuntu touch I find it hard to believe that nobody has built one of the later.

I've been searching for custom ROMs too. Apparently, there are none available at present. However, I'd highly appreciate lineage rom.

TWRP build by shakalaca

seen on official zentalk forum.
On the first post, search for TWRP, there will be a mega download link.
after unlocking bootloader, flash in fastboot
fastboot flash boot twrp-3.2.xxxxxxxxxxx.img
note: Flash to boot partition only. and download the corresponding version of twrp per your rom version.
Boot your phone and press Power+VolDown before you see the ROG Phone logo and release after.
I don't have permission to post the files or link it so here's the original link.
https://www.asus.com/zentalk/tw/thread-362963-1-1.html

freefrank said:
seen on official zentalk forum.
On the first post, search for TWRP, there will be a mega download link.
after unlocking bootloader, flash in fastboot
fastboot flash boot twrp-3.2.xxxxxxxxxxx.img
note: Flash to boot partition only. and download the corresponding version of twrp per your rom version.
Boot your phone and press Power+VolDown before you see the ROG Phone logo and release after.
I don't have permission to post the files or link it so here's the original link.
https://www.asus.com/zentalk/tw/thread-362963-1-1.html
Click to expand...
Click to collapse
Do you have pictures? Root? Any bugs?

Swarai said:
Do you have pictures? Root? Any bugs?
Click to expand...
Click to collapse
Only good for flashing off USB device. Nothing else works.

Can somebody create a fastboot bootable TWRP image and/or a zip file to inject TWRP into the stock boot image like it's used on the Moto Z2 force for example? I don't care about encryption and always have an unencrypted data partition.
Or could someone tell me how to create it myself?
That way we wouldn't have to wait for a modded boot image.
Kind regards