At least it works nowFigured it out. It was a faulty driver that worked in fastbootd mode but not the bootloader for whatever reason. Manually updated the drivers in device manager and it all works now.

At least it works nowFigured it out. It was a faulty driver that worked in fastbootd mode but not the bootloader for whatever reason. Manually updated the drivers in device manager and it all works now.
Odd, but vibrations Don't really matter too much at leastInstalled and working, but for some reason, the button vibration is either causing the speakers to make a hissing sound, or it doing something terribly wrong to the vibration motors. I turned it off in settings and the sound went away.
So you mean if we gonna use TWRP, we must flash from pc again?Do you have USB debugging on and allowed the computer to use it? Otherwise I'm not too sure.
Turned on USB debugging, plugged my phone into the side port, allowed pc to use it when the popup came up, then followed the instructions.
Also just learned that if you flash the twrp. Img when you first do it it'll replace the system so don't do that.
No, so once you do 'fastboot boot twrp.img' and it boots into twrp you are going to copy the twrp.img file over to your phone, then in twrp go to install > install image > choose the twrp.img > install recovery ramdisk. The command to boot literally only boot into the recovery image, it isn't actually flashed to the device yet at that pointSo you mean if we gonna use TWRP, we must flash from pc again?
I mean if we don't flash twrp.img in TWRP
Also after I flash twrp.img what button combination to enter TWRP3, it is same button to enter recovery mode?
Oh I get it, then after I install it to recovery ramdisk then should I use "fix recovery bootloop" option or reboot the device normally?No, so once you do 'fastboot boot twrp.img' and it boots into twrp you are going to copy the twrp.img file over to your phone, then in twrp go to install > install image > choose the twrp.img > install recovery ramdisk. The command to boot literally only boot into the recovery image, it isn't actually flashed to the device yet at that point
Because you didn't read the OP.Colleagues, why after installation, the phone automatically goes into TWRP mode? Why is it not starting?
The op says nothing on how to actually keep it, so of course people are going to experiment trying to get it to work.
While I'm not 100% sure, I believe by flashing the twrp. Img it replaced the system img, so you no longer have something to boot into besides twrp. We need a recovery. Img to replace the recovery and not system.Colleagues, why after installation, the phone automatically goes into TWRP mode? Why is it not starting?
While I'm not 100% sure, I believe by flashing the twrp. Img it replaced the system img, so you no longer have something to boot into besides twrp. We need a recovery. Img to replace the recovery and not system.
I hope you did a backup before flashing? Otherwise you'll have to flash the original raw firmware and have a fresh device.
I was gonna do the same but luckily got told in a telegram group that would happen.
Known issues
Device-specific
- To boot into system from TWRP, you need to flash stock boot.img. Fix Recovery Bootloop doesn't work
Did you actually install it or just boot into it? Once you are in twrp, you have to use twrp to install the recovery img. fastboot boot twrp.img only boots from the image, it doesn't install it.
No, so once you do 'fastboot boot twrp.img' and it boots into twrp you are going to copy the twrp.img file over to your phone, then in twrp go to install > install image > choose the twrp.img > install recovery ramdisk. The command to boot literally only boot into the recovery image, it isn't actually flashed to the device yet at that point
adb reboot bootloader
adb reboot fastboot
fastboot devices
fastboot boot twrp.img
Sending 'boot.img' (98304 KB) OKAY [ 0.343s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
fastboot reboot fastboot
fastboot flash recovery twrp.img
Sending 'recovery' (98304 KB) OKAY [ 2.238s]
Writing 'recovery' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
fastboot boot twrp5S.img
*** 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
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:
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:
Code:
Code:fastboot boot twrp.img
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!
3.5.2_11-2
- Common version for all ROG 5 versions.
- Fixed decryption issue
3.5.2_11-0:
Initial version (Tested only on ROG Phone 5S, need info about ROG Phone 5).
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!
@Freak07 and @Captain_Throwback for advices
@Qtr1st and @danfrid for testing
Thanks. I'm building updated kernel at the moment. Will upload test image when twrp will be built.ZS673KS version I was just trying out anything this one booted but didn't ask for a pw