TWRP 3.2.3-1 for Pixel 3 XL

Search This thread

Homeboy76

Senior Member
Aug 24, 2012
3,283
1,810
Google Pixel XL
o_O:eek: What, the 'Google' Pixel 4A and, Pixel 5 have a working Android 11 (R) TWRP. Where are they?
Not here!

I know it is flustrating, but isn't everyone patiently waiting for Android 11 (R) T.W.R.P?
 
Last edited:

Spannaa

Recognized Contributor / Themer
Sep 13, 2010
7,115
15,879
Cardiff
Huawei Nexus 6P
Google Pixel 3
Mod Edit: Quote removed since post deleted.

Wow, it's rants like that, (ending with shouting) that make devs stop developing.

@Dees_Troy owes nobody anything.

Just dug up an old post that explains:

 
Last edited by a moderator:

TNSMANI

Senior Moderator / RC-RT Committee
Staff member
Jan 8, 2014
6,428
2
10,422
Chennai
OnePlus 9 Pro
Friends,

I think that both for and against comments have already been posted and there is no need for continuing this. Please observe the Rules and post with respect and civility to the Dev and fellow users.

A dev's decision is his own and no one has a right to criticise that. If he chooses to stop developing, then that is it. He is under no obligation to anyone to do any particular thing.

If you are capable, develop on your own and also help other users. If you are not, please move on.

I hope that such posts will now stop. If not, they will be removed summarily.
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,939
7,188
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
XDA is such a great community of developers :D If you want it so bad learn how to do it yourself. They have no obligation to communicate with you about anything.

I am assuming you have a bluline, I do not. When I tried to get people testing the build that I produced, they said it didn't work. I would expect that the fixes will have to be done by someone who has a blueline.
 
  • Like
Reactions: barnettejd

Eudeferrer

Senior Member
Aug 27, 2012
717
251
Miami
We are looking for contributors.
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.
 

pro.aggro

Senior Member
Jul 22, 2011
860
420
i'm currently on du 14 (android 10) with 1.5.5 kirisakura.

i booted up twrp with fastboot, but i cant install the img because my storage is just empty.
i removed lockscreen pw, but still empty.
 
Last edited:

pro.aggro

Senior Member
Jul 22, 2011
860
420
its installed right now. maybe i need more coffee :cool:
twrp is running, root is back. but i cant mount any storage with twrp?
what am i doing wrong?
 
  • Like
Reactions: droidvet
i cant code for ****, but I am familiar with many variations of contributors...

I have BTC... and DOGE... has anyone considered setting up a donation bounty? is that a thing? I see it constantly, everywhere, for years and years...
"I cant code for ****... but I can do testing"
everyone here is a testor, if you have an account here, youve been testing... yah I know, I cant code for **** either... but what if there was a big ass project leaderboard where people could contribute eaisly and devs could apply their efforts on the projects that motivated them most effectivly

How is this NOT a defi project already???
Ill tell you why... the only problems coders CANT fix are their own...

Seriously tho? Anyone wanna start a crypto platform?
 

Rootmaster906

Senior Member
Dec 2, 2020
322
14
Nexus 6
Samsung Galaxy Note 10
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/
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"
what am i doing wrong?
 

KaosKreationz

Senior Member
Nov 9, 2020
71
14
Newaygo
Tried following instructions to install TWRP on 9 10 and even tried 11 I get TWRP to boot up in 9 and 10 but I cant seem to successfully install it as recovery or get it to retain while keeping my system installed. I either get TWRP to stay installed in boot but then lose my system or it bootloops. am i doing something wrong? how can I get the TWRP to stay on the phone and have the android os working?
 

Top Liked Posts

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