That option doesn't apply on this device, since it's a GKI device and doesn't use skip_initramfs. You shouldn't have an issue booting up unless you flashed the TWRP image to the boot partition.Hello, thanks in advance for your work porting twrp to zf8. I tried a lot and finally got it running together with LOS18.1-20220107, had a lot to fight with the vender_boot.img and boot.img, if anybody needs help, i'd share my experiences...
One question: on https://twrp.me/asus/zenfone8.html you mention as last step:
"NOTE: You also need to use the "Fix Recovery Bootloop" option present in the same Advanced Tab. Use that option after you have installed the recovery ramdisk successfully to avoid boot loops happening from installing TWRP Permanently."
I wanted to do this cause it was exactly my problem, that twrp always booted to itself, not to the OS. I couldn't find that option though, what am i missing?
What boot.img are you refering to?
I tried flashing vendor boot (fastboot flash vendor_boot .\sake_vendor_boot.img) like stated here and than booting into twrp (fastboot boot .\twrp.img) like stated here. But after reboot it stucks at ASUS logo, till I hardrestartet it. Happens everytime. booting to TWRP without flashing vendor results in the same outcome.
Btw. I had the same outcome even bevor flashing LOS recovery and LOS.
What do you mean, installing vendor_boot? There's nothing in the instructions about that.Hey there,
Today I tried to install "twrp-3.6.0_11-0-I006D.img" on my Zenfone 8 which was initially loaded with WW-31.1004.0404.81 (Android 12 official version from Asus website - link : https://www.asus.com/UK/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_BIOS/) and it seems that my phone is bootlooping.
I followed every step, installing the Vendor_boot and then the TWRP image.
How can I exit this loop?
Actually I spent the 2 last days trying to install LineageOS 18.1, and on some site it was requested to install Vendor_boot before TWRP.
Well that's outside of this thread. And I know LineageOS instructions say to use their recovery to install, so I can't help you with that.
I found the step about vendor_boot on https://lineageosroms.com/sake/, pre-installation steps.
I got it running. After a lot of try and error that's what I found:
Currently (Jan. 22) the LOS vendor image is NOT compatible with TWRP! If you first flash the vendor image and then ether flash or boot TWRP it will just stuck an the ASUS logo.
I don't know if that's could be a issue in future but for now, I reflashed the original vendor extracted from an update unsing this payload dumper. And then followed the TWRP instructions.
Here my steps:
With unlocked BL, booting to BL already done and working adb/fastboot drivers
- (Reflashing original vendor (only needed on non stock devices))
- fastboot flash vendor_boot vendor_boot.img
- Booting TWRP:
- fastboot boot <TWRP Image>.img
- (Doing a faktory reset if needed)
- Sideloading LOS (TWRP flashes it to the inactiveslot)
- In TWRP: Advanced -> ADB Sideload -> Swipe to Start Sideload
- On PC: adb sideload <LOS Image>.zip
- Let TWRP flash itself
- In TWRP: Advanced -> "Flash current TWRP"
- If further packages are needed (like gapps oder magisk)
- Change slot (In TWRP: Reboot -> Slot x) or reboot to recovery
- Either sideload them oder adb push them to sdcard and use TWRPs install method.
- Sideload: see 4.
- ADB Push: adb push <package> \sdcard
- Reboot to system.
For reference: My images
- LOS: 18.1-20220121 lineage-18.1-20220121-nightly-sake-signed.zip
- TWRP: v3.6.0_11 twrp-3.6.0_11-0-I006D.img
- Stock Rom: Version WW-184.108.40.206 from 2021/12/17
I believe the with every LOS update its required to let TWRP reflash itselve, otherwise the original LOS recovery will be used. I read somewhere that TWRP does this by itself when flashing, but I am not sure if this is really the case.
But as stated, I'm not sure if that's the correct way. Unfortunately didn't get answers till now.
Edit: Format, links and commands
I wonder if OrangeFox would work better. It seems TWRP is not much of help anymore with most custom ROMs.
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.
Hi, I have acutally the same problem
*** 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!
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.
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:
You should now be in fastboot mode.Code:
adb reboot bootloader
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:
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!Code:
fastboot boot twrp.img
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 220.127.116.11 or higher installed.
- Download the latest version of TWRP appropriate for your device/firmware
- Reboot to TWRP
- Hit Install and tap the "Install Image" button in the lower right
- Browse to the location of the TWRP image on your device and select it
- Select "Install Recovery Ramdisk" from the partition list and swipe to flash
- (Optional) If previously rooted, re-install root apk/zip, as the TWRP install will overwrite root.
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!