TWRP 3.2.3-1 for Pixel 3 XL

[bigbiff]

Awesome, yeah I figured as much - I forked your branch which is only two days old!

I'm really super keen to get it working though, I don't mind doing parallel work - you know the "official" rules better than I do, I'm just happy to help.

So take a look at my fork for some tips if you like, I made a push recently.

EDIT: Nevermind the following rant. Things started being predictable and sane now that I'm using android-11.0.0_r46 tag for dependencies (latest October 2021 update is built against r46).

Spoiler

Recent findings, and some questions for you if you don't mind:
- Is it a requirement (or even possible?) to have SELinux enforcing under Recovery? I've been trying to get that working for stock kernel compat (obviously can't add permissive to commandline) but now I'm wondering if it we should just call setenforce 0 early - is that enough? I did notice the permissive.sh script but I have't investigated when/where that's called yet.
- I was talking to flex and he said he thinks it's practically impossible to "fastboot boot" a modified stock kernel; you need some kernel hacks to get it to mark as a successful boot. Is this something TWRP can fix, or does everyone build TWRP with a custom zImage (like I'm already doing)?
- I removed some prebuilts in the tree and added some required dependencies. Namely missing sepolicy for pixel and the included kernel modules for touch. Do you know where those touch modules came from? Are they source-built from CAF maybe? Using the modules from crosshatch-kernel instead like I do seems to work fine, regardless of kernel I'm using. Not a big deal, but I'm curious if there's better/newer blobs compared to crosshatch-kernel prebuilts from android11-release branch.

Anyway, take a look at recent commits: the commit messages should be descriptive enough for you to decide if anything is interesting or not: https://github.com/cosmicdan/android_device_google_crosshatch/commits/android-11

If you could take a look at these two commits, I believe they're both important:

Add no-sdcard related TWRP flags · cosmicdan/android_device_google_crosshatch@a54eaea

For building TWRP for the Pixel 3 and 3 XL ONLY. Contribute to cosmicdan/android_device_google_crosshatch development by creating an account on GitHub.

github.com

Add Kernel DTBO to backup partitions · cosmicdan/android_device_google_crosshatch@4aff00c

For building TWRP for the Pixel 3 and 3 XL ONLY. Contribute to cosmicdan/android_device_google_crosshatch development by creating an account on GitHub.

github.com

The immediate two problems I can see are:
- Data not being mounted (I might take a look at that)
- Fastbootd not working (no USB device). I noticed you did a lot of the work for that in TWRP so you'll probably figure that out before I do

Thanks for your work!

EDIT: Just to be clear, I'm more than happy for you to re-author my changes as your own - no stress or drama here, it's not my original code or anything lol all I want is a working TWRP

I haven't looked at your tree. I am using my branch and trying to figure out why the device doesn't work with the legacy encryption option mode.

 

[CosmicDan]

I haven't looked at your tree. I am using my branch and trying to figure out why the device doesn't work with the legacy encryption option mode.

Fair enough, I couldn't figure it out. I tried with TW_INCLUDE_CRYPTO_FBE and also TW_CRYPTO_USE_SYSTEM_VOLD - both resulted in build errors that were beyond me. Maybe they're TODO at TWRP's end or there's some missing dependencies.

I'll let you get on with it, I don't intend to do any more - they're only little tweaks to make an initial GSI setup easier (e.g. mounting system and resizing it, flashing gapps, etc) and all I really did was get it booting/compile-able anyway with the twrp dependency file.

Good luck and thank you!

 

[rossmurray]

With Google recently dropping official support on the Pixel 3 XL what is the status on A12 in relation to TWRP? Are the same issues you've had with A11 also a factor with this newer version?

 

[adeptustech]

The faster we get twrp up for a12, the faster we can start developing all of our new a12 ROMs & making some massive tweaks.

 

[wonderlandpoet]

Thanks here is a new test build. I was able to replicate it locally and now the time is correct on backups:

https://build.twrp.me/test/crosshatch/twrp-3.4.0-0-test2-crosshatch.img

Hopefully someone can assist me with, I have rooted in the past and this is by far the most complicated root I've ever done. I have flashed pretty much ever TWRP and nothing, then I found this. I flashed this after I noticed I did not have the rom on my SD so I rebooted the system and boot loop. What am I missing or doing wrong. It is a Pixel 3 XL for Verizon. I should mention I have the rooted right now with Magisk.

 

[swieder711]

Hopefully someone can assist me with, I have rooted in the past and this is by far the most complicated root I've ever done. I have flashed pretty much ever TWRP and nothing, then I found this. I flashed this after I noticed I did not have the rom on my SD so I rebooted the system and boot loop. What am I missing or doing wrong. It is a Pixel 3 XL for Verizon. I should mention I have the rooted right now with Magisk.

There is no TWRP support on the Pixel 3 when running Android 11 or 12.

Also, if your phone came from Vz then it cannot be bootloader unlocked or rooted.

 

[wonderlandpoet]

There is no TWRP support on the Pixel 3 when running Android 11 or 12.

Also, if your phone came from Vz then it cannot be bootloader unlocked or rooted.

I currently have the bootloader unlocked and it is rooted with Magisk, my issue is getting twrp to flash and work, it gets stuck on the logo and or the touchscreen wont work.

 

[wonderlandpoet]

I currently have the bootloader unlocked and it is rooted with Magisk, my issue is getting twrp to flash and work, it gets stuck on the logo and or the touchscreen wont work.

I should mention it is running Verizon service but the phone was purchased from Straight Talk with no service plan.

 

[dishe2]

Sorry for the noob Q, but will installing TWRP on my Pixel help prevent this new randomly dying Pixel thing that's been going on with the 3 for the last couple of months?

Some Pixel 3 devices are stuck on EDL mode, and nobody knows why

There are growing reports from Pixel 3 owners that their devices have bricked and are stuck in EDL mode, though nobody knows why.

www.xda-developers.com

I just picked this up and made sure to get a bootloader unlockable version so that I could use custom ROMs to keep the software relevant, but now I'm confused as to what's going on. First I find out that random P3/P3XLs are dying overnight and having their bootloader corrupted (goes into EDL mode and no way out). Then looking here I see that TWRP only works on Android 9 and 10, so I'm just confused. I thought a used Pixel would be the kind of thing for longevity after EOL, but now I'm second guessing it all. What do you guys think?

 

[Spannaa]

Sorry for the noob Q, but will installing TWRP on my Pixel help prevent this new randomly dying Pixel thing that's been going on with the 3 for the last couple of months?

Some Pixel 3 devices are stuck on EDL mode, and nobody knows why

There are growing reports from Pixel 3 owners that their devices have bricked and are stuck in EDL mode, though nobody knows why.

www.xda-developers.com

I just picked this up and made sure to get a bootloader unlockable version so that I could use custom ROMs to keep the software relevant, but now I'm confused as to what's going on. First I find out that random P3/P3XLs are dying overnight and having their bootloader corrupted (goes into EDL mode and no way out). Then looking here I see that TWRP only works on Android 9 and 10, so I'm just confused. I thought a used Pixel would be the kind of thing for longevity after EOL, but now I'm second guessing it all. What do you guys think?

Since there is no working TWRP for the Pixel 3 running Android 11 or 12 and the article says "there’s currently no way to recover the Pixel 3 or 3 XL from EDL mode." then I think you can safely assume that installing TWRP won't help you.

 

[dishe2]

Since there is no working TWRP for the Pixel 3 running Android 11 or 12 and the article says "there’s currently no way to recover the Pixel 3 or 3 XL from EDL mode." then I think you can safely assume that installing TWRP won't help you.

Can't I downgrade to an earlier build?

And the idea is to provent whatever bug is causing the bootloader to delete itself, not just to recover from edl mode.
I'm wondering if people who have run a modified bootloader are less likely to get it.

 

[Spannaa]

Can't I downgrade to an earlier build?

You could - Android 10 would be the latest with TWRP.

Personally, I wouldn't bother as there's no reason to think it would help and you'd be running an old, insecure rom.

I'll stick to Android 12 on my Pixel 3 and if it dies, so be it - it's over three years old and the battery isn't great anymore.

 

[dishe2]

So if I'm understanding correctly, there aren't any custom roms past A10?
Dang, I got the bootloader unlockable version on purpose to keep support past Google's EOL, but what's the point if the customs are stuck on 2 versions ago?

 

[Spannaa]

So if I'm understanding correctly, there aren't any custom roms past A10?
Dang, I got the bootloader unlockable version on purpose to keep support past Google's EOL, but what's the point if the customs are stuck on 2 versions ago?

There are, but I stopped using custom roms when Dirty Unicorns stopped.

Check out the Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth forum

 

[Homeboy76]

There are, but I stopped using custom roms when Dirty Unicorns stopped.

Check out the Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth forum

So if I'm understanding correctly, there aren't any custom roms past A10?
Dang, I got the bootloader unlockable version on purpose to keep support past Google's EOL, but what's the point if the customs are stuck on 2 versions ago?

Google will be releasing one last Pixel 3 and 3 XL update in Q1 of 2022 Abner Li - Nov. 2nd 2021 11:24 am

 

[NepoRood]

So if I'm understanding correctly, there aren't any custom roms past A10?
Dang, I got the bootloader unlockable version on purpose to keep support past Google's EOL, but what's the point if the customs are stuck on 2 versions ago?

This is totally OT, however, I still support the Pixel 3XL, I have a solid Android 12 build running on it right now. LineageOS also supports, so you can keep an eye out there too.

After getting my 2 cents; This is a recovery chat, not a ROM chat, my fellow members. Hopefully no one will call a FSM on us...

 

[dishe2]

This is totally OT, however, I still support the Pixel 3XL, I have a solid Android 12 build running on it right now. LineageOS also supports, so you can keep an eye out there too.

After getting my 2 cents; This is a recovery chat, not a ROM chat, my fellow members. Hopefully no one will call a FSM on us...

Thank you and sorry for veering off course. I guess I don't quite understand how the recovery works then, so I hope this still counts as relevant?
Don't you need twrp to flash custom roms? If this recovery does not support a12, how do such Roms exist?

 

[NepoRood]

Thank you and sorry for veering off course. I guess I don't quite understand how the recovery works then, so I hope this still counts as relevant?
Don't you need twrp to flash custom roms? If this recovery does not support a12, how do such Roms exist?

It happens. TWRP isn't the only way, you just needs to browse the custom ROM threads, see what's happening there

 

[entux]

Are there any solutions ot a non-response touch screen? I'm on lineage 19.1.

 

[justDave]

Are there any solutions ot a non-response touch screen? I'm on lineage 19.1.

I believe this thread is obsolete. Maybe post here. That said, I haven't had any touch issues. Are you using the right TWRP for your device?