Development [RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 5 & ROG Phone 5S
- Thread starter mikalovtch
- Start date
Yes, but seems that after A12 update got stuck with extracttarfork() process ended with error=255 when trying to full backup....
Captain_Throwback
Recognized Developer
My advice is just go ahead and back everything up and downgrade with the firmware provided on the official Asus website for downgrade then you can downgrade to any firmware that you want I am on 210 TWRP working great read write script working great bloatware gone working great
I'm actually on Android 12 now TWRP working perfectly through magisk. Everything working good on Android 12. I was able to flash what I needed to flash without any issues. So if anybody's having trouble with the black screen when you try to boot into it via fastboot, just install it with magisk as mentioned above in some of the comments works perfect
Are you using adb sideload option in twrp for flashing purposes? Because if password-protected it won't decrypt.
Or is OTG working for flashing?. I haven't tried via otg
It works perfect for me password and everything just flash it with magic flash the installer with magic and that's it boot into recovery you don't need a PC I flashed my zip files directly after I enter my password that's the only way it would work booting it through fast boot gave me the black screen this was the only thing that worked for me
Thanks for the answer. Last time when i was in android 12 i did the same as you did. Twrp booted fine but i couldn't decrypt with my pattern. Later i downgraded and now i am on android 11. I really missed gravity box in a12 haha.
Hi guys, could you tell me the exact procedure (without the black screen) to root the Rog 5s, with android 12? Thanks
Flash magisk patched boot.img (Should match your firmware version) via fastboot to get rooted. Then once rooted flash twrp installer.zip (download from official twrp link) from magisk.
My device is the 5S/ZS676KS (512GB), purchased from the ASUS site. I installed TWRP 3.6.1 using the zip on Magisk, and when the screen goes to standby automatically or by pressing the power button, it doesn't turn back on. ADB still works, though, and I see that it's trying to unblank the screen. It happens on both the latest A11 (18-1220.2202.206) and A12 (31.0810.1226.77) builds as the base boot.img. The only other change to the images were patching them with Magisk v24.3. Here are recovery.log and logcat for TWRP running on the A12 base.
EDIT: for some reason my recovery.log is not saving when uploaded directly. I have put it in a zip instead.
EDIT: for some reason my recovery.log is not saving when uploaded directly. I have put it in a zip instead.
I downloaded twrp 3.61 img, renamed to twrp.img, put it on device (5) storage but fastboot boot twrp.img doesn't load twrp at all. Says 'downloading boot.img', reboots twice and dumps me back in a regular boot to Android 12. Removed PIN and fingerprints to no avail. In security settings, it still says 'encrypted' under 'encryption and credentials'. Do what now?
I am running on Android 12 Version WW-31.0810.1226.77 with root access gained from patching the boot.img with Magisk version 24.3. Similar to # 153, I could not get booted into TWRP 3.6.1. I saw a black screen and then got booted into Andriod 12 operating system as normal after executing the command "fastboot boot twrp.img".
It wont flash that way. Flash TWRP using Magisk from inside Android OS.
NOTE: If you are on A12 then... its pointless anyway. TWRP dont work on A12.
Thanks. I will wait for an official release that supports Android 12 and hope that it will not take long.
When i boot to recovery (using code : fastboot boot twrp.img) it boot into black screen not booting into twrp
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
14Code:
*** 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
Images
Prerequisites
Installation instructions
Device Changelog
Current version: 3.5.2_11-2:
Device Changelog
Known issues
Bug reporting
Additional Help/Support
Credits
7Here's my trip around the sun;
Downloaded the file twrp-3.5.2_11-2zs673ks.img and renamed it to just twrp.img. (So it's easier to type in CMD).
Placed it on the root of my C: Drive where I keep all my flash files.
Shut down phone, Then Volume up and power to go to fastboot mode. That's the screen where it shows some options like Power On, Recovery Mode and Reboot. Just stay there, dont select anything.
Connected the cable via side USB port and executed the following commands;
First command to check connectivity, second command is to boot to TWRP.
No flashing !! remember always; new TWRP cannot be flashed through fastboot because recovery is a part of the existing partition, not a separate one like it used to be on Android 8 and below.
Once you execute the above command, be patient. Your phone will come back to bootloader screen making it look like it failed. Just wait, it will reboot again and it will go to TWRP. Now you can enter you pin code, and enter the recovery.
I flashed a kernel, I cleared my dalvik cache .. everything went well.
Now if you want to keep TWRP permanent;
Copy the twrp.img to your phone memory, preferably downloads folder of the phone, and follow the above steps mentioned - again up to entering TWRP.
In TWRP, select advanced, and you will see the below screen -
Select the option - Install Recovery Ramdisk and it will ask where your TWRP.img is, and point it to the file you earlier saved in the phone / downloads folder. This will flash TWRP within the kernel making it permanent along with your kernel.
That's it, reboot and enjoy.
EDIT : How to get to TWRP again;
From CMD - send adb reboot recovery or
shut down phone, Volume UP + Power .. In bootloader press volume down until you see recovery mode, and then press the power button once to select it.4
Thanks. I'm building updated kernel at the moment. Will upload test image when twrp will be built.33
Flashing a custom kernel also won't install / restore Magisk. The custom builds are meant to retain Magisk, but don't actually perform any of the installation.
You can install TWRP over a custom kernel and the kernel will remain, but Magisk will be gone and need to be reinstalled. At this point, the app will only allow you to patch a supported image (img / tar, but also supports win without saying it) and the custom kernels include none of those. This means you need a Magisk recovery zip or need a backup of the kernel to patch with Magisk.
You can also install a custom kernel over TWRP, but you would need to already have Magisk patched in after installing TWRP or install it after the kernel (see above).
TL;DR
Edit: there was an even easier way
Have a copy of Magisk apk, the kernel zip from this thread, and the twrp image (just in case) on your sdcard.
Boot TWRP and do Advanced -> Flash current TWRP
Install Magisk through TWRP
Reboot to system
Install the kernel zip
You'll have all three installed and running
