• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

TWRP 3.2.3-1 for Pixel 3 XL

Search This thread

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,548
KC MO
www.teamw.in
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.

Installation:
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:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/

Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/
 
Last edited:

PewPewK

Senior Member
Dec 23, 2013
140
45
Seattle
hello, after flash twrp, bootloader enter reason shows "combo key", and cant enter nomal OS. How to solve it?

Did you flash it? The instructions say specifically to not flash TWRP using fastboot.

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.

You need to fastboot boot twrp.img, then use the twrp_installer.zip INSIDE TWRP to install correctly.

If you can't boot, flash the stock boot.img to boot_a and boot_b and you should be back to normal.

---------- Post added at 12:11 AM ---------- Previous post was at 12:05 AM ----------



I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.

This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.

Others having this issue?
 
  • Like
Reactions: NinjaPlease

freddienuxx

Senior Member
Dec 11, 2012
1,625
305
OnePlus 8 Pro
OnePlus 8T
Yup. You have to wait for a modified boot.img/kernel I totally forgot about that
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.



You need to fastboot boot twrp.img, then use the twrp_installer.zip INSIDE TWRP to install correctly.

If you can't boot, flash the stock boot.img to boot_a and boot_b and you should be back to normal.

---------- Post added at 12:11 AM ---------- Previous post was at 12:05 AM ----------



I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.

This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.

Others having this issue?

Sent from my Pixel 3 XL using Tapatalk
 
  • Like
Reactions: tapa123 and ridobe

jiao322528

Member
Nov 8, 2009
16
0
Shanghai
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.



You need to fastboot boot twrp.img, then use the twrp_installer.zip INSIDE TWRP to install correctly.

If you can't boot, flash the stock boot.img to boot_a and boot_b and you should be back to normal.

---------- Post added at 12:11 AM ---------- Previous post was at 12:05 AM ----------



I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.

This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.

Others having this issue?

It was partition issues. I changed boot a to b, of course it is black...now everything is ok, but same problem as yours. Thank god!
 
Last edited:

ridobe

Senior Member
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.

Where? I think you mean ADB. How else are you going to flash it?

edit: I see what you mean. Boot, then flash with the booted TWRP. NEVER MIND...CARRY ON.

---------- Post added at 07:42 AM ---------- Previous post was at 07:27 AM ----------

I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.

This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.

Others having this issue?

Yup. Same problem. This also happened on the P2/P2xl. You needed to flash a custom kernel as well. We'll have to wait for that. Until then, do all of your flashing during the "booted" TWRP.

edit: so yeah, pretty much what @freddienuxx said. I'm not having a good morning guys.
 
Last edited:
  • Like
Reactions: TonikJDK

virtyx

Senior Member
Jan 3, 2011
2,505
650
If I recall the pixel 2 XL was the same if you were on stock kernel but touch was fine with a custom kernel. At least we can put magisk on

i flashed magisk 17.3 in TWRP but now when i set a pin it says incorrect pin when i try to unlock (but still unlocks the phone) and it also wont let me use a fingerprint.

given i have decrypted... i cant even add a finger print to unlock.
 

Ariel_PR

Member
Feb 6, 2013
47
8
I also have no touch on 3XL 128gb. TWRP works fine when I boot it through fastboot but after I install it (and reboot) the touch stops working.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 96
    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.

    Installation:
    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:
    https://twrp.me/google/googlepixel3.html
    https://dl.twrp.me/blueline/

    Pixel 3 XL:
    https://twrp.me/google/googlepixel3xl.html
    https://dl.twrp.me/crosshatch/
    60
    FYI, I was able to get decrypt working on the Pixel 4 yesterday. You can follow my code commits at my github https://github.com/bigbiff

    When I am done with flame and coral, I will try to update Pixel 3 XL. I don't have blueline/Pixel 3 so I will need testing for that.

    My patchsets might take a few months to go into the official mainline. We are anticipating having one release for all existing devices on the android-9.0 branch for TWRP. I am hoping to have SAR and multi-user encryption patches for this release.

    Currently the android-10.0 branch is a WIP. It was enough to get flame booting a GUI and hopes that other people will test their devices out. My encryption, super and apex patchsets are based on android-10.0.

    I anticipate not doing any more backwards compatibility for android-10.0 branch. We will have to come up with a decent release scheme for any device that isn't compiling under android-10 trees. For now I anticipate cherry-picking patches from android-9.0 to android-10.0 for features and bugs.
    33
    Hello, I have been able to fix touch in TWRP by loading the correct kernel modules on init. I uploaded 3.2.3-1 to https://twrp.me

    Please let me know if you encounter any issues. I am currently looking at why the dwc3 controller doesn't seem to initialize properly when fastbooting TWRP. This is the reason adb doesn't work in fastbooted TWRP.
    28
    @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

    I am working on having the target log compressed in the stored partition such as persist to reduce the amount of space it takes. I am close to pushing a patchset to gerrit.
    23
    Currently we are still targeting Android 9 for the time being. I might release some test builds for crosshatch soon.