So I'm going to be that guy. Pixel 4, Pixel 5, Pixel 3a and Pixel 4A all have working TWRP. Why exactly are we left out? Is this some serious coding issue xxxxxxxxx ? I mean it's been over a year and every other device is getting updates. I'm just wondering if there's any good reason or if we should just stop hoping and buy a new phone.
I don't like to be demanding or anything of people that are doing stuff for free. But a little bit of communication would be amazing deez troy
Mod Edit: certain words deleted
How I wish I could! Unfortunately, my knowledge of development is next to zero. However, I'm always willing to contribute by testing. I know that doesn't help a lot, since I don't have the knowledge to do the really hard work of development, but I can always be a guinea pig and test it out! Lol.
flashed 3.5 twrp on my android 11 and it stays on twrp splash screen for over an hour. tried flashing versions lower than 3.5 and it keeps saying "failed. invalid perimeter"ADB does not work! On the Pixel 3XL, TWRP takes a while to boot up. Be patient, it will boot!
Note, I don't own a Pixel 3 XL, just the regular Pixel 3 (blueline). I personally won't be able to fix ADB. If you have some talent with init scripts and fixing ADB, feel free to work on it and submit a patch.
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You will either have to transfer files while in Android or use a USB OTG cable and a thumb drive.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
3.2.3-1: Fix touch when TWRP is installed on the 3 XL
Pixel 3 XL:
TWRP doesn't work with Android 11 on this device.
@Dees_Troy and other TWRP Devs: please do check this thread https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904.
Implementing TWRP to use the /persist partition to store logs and caches can cause major issues. Essentially, this partition is only 40MB in size and the logs (for those who make nandroid backups, in particular) can run larger than 20MB, thereby corrupting the factory calibration and configuration files on Pixel phones. Suggestion would be to not write to this partition at all, if possible - or to put a check to clear log files if they exceed a certain date or size.
Related bug report was filed by someone here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1506