yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
As long as your device is 100% stock you'll be able to get ota's. Restoring the data partition only restores your apps and app data and doesn't touch your system.

Also, for those that have read my responses, I have successfully restored a nandriod of the boot, system image, and data. This was after a defualt wipe. It was a rooted, stock system with TWRP recovery. It was also restored over a stock, rooted system with TWRP recovery. I haven't tried restoring over a custom rom or a rooted, trwp recovery over a stock setup, etc. So ymmv.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] cawpin:
Is there any progress on having a permanent TWRP install able to flash OTAs and Magisk without reverting to stock boot image first?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Portgas D. Ace:
From my understanding, there is no recovery partition anymore for the Pixel 3. The recovery is now located inside of the boot partition. And thus you have to install the TWRP zip everytime you flash a ROM, without the possibility to get a permanent TWRP solution.

If I am wrong with this, please correct me.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NYCHitman1:
This is correct. There is no other permanent solution to this, as aforementioned.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] [Cruzer]:
I tried to restore a complete backup and failed. No boot no nothing. Had to restore from factory image. So to understand things correctly. If I wanted to switch back and forth between roms. Example from stock to custom rom backup. I would have to flash custom rom from scratch. Then restore data only and reflash twrp. And then vice versa to go back to stock. Or if I restored boot and data. I wouldn't have to reflash twrp?? Just trying to figure out best practice for someone who wants to go from one backup to another. I"m used to doing installing rom, if I don't like, restore previous rom from backup. I tried that, and just got a black screen.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
If you're not already, try backing up boot, system image, and data. I've had some luck restoring that.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] [Cruzer]:
Ok Will give that a try

Thanks.

EDIT: ok so that worked out great. Doing system image instead of system is what I did wrong. Thanks for that.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Xdevillived666:
Sort of off topic but anybody have issues using fastboot commands like flash or erase modem ? Not sure if its twrp or what, but i get remote cinnection not allowed when trying to fastboot erase modem .
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] GryphonBR:
TWRP and fastboot are different things from what I can tell. On A/B devices, TWRP does sit on the /boot partition, but fastboot in on the /bootloader, which is a different partition in my understanding.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] FcukBloat:
hi sorry one question in thread title I see twrp version is 3.2.3-2 but the download link points to 3.2.3-0 version only?

thanks

edit: nvm searching I see 3.2.3-2 is for 3 xl while blueline remained to 3.2.3-0 version.. sorry. thread title is little confusing though imho!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] LoneWanderer_97:
Guys so i flashed i basically have no os, and now twrp wont mount storage or data, so i cant just flash a rom to get out of any advice?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] frewys:
Hold down powerbutton and volume down for 15 sec and you should enter bootmenu

From here you can flash stock with the bat file but make sure you remove -W or it will erase your internal memory (pics etc)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] LoneWanderer_97:
Is there no way to get twrp to mount data and storage? Ive tried flashing factory image via fastboot but i keep getting an error its infuriating

Edit: Nvm i got it to work
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Portgas D. Ace:
[MENTION=912474]Dees_Troy[/MENTION]:

Any chance for an updated version of TWRP with the fix for the infamous "Error applying update: 18 (ErrorCode:: DownloadPayloadPubKeyVerificationError)" issue? I think the version for crosshatch (Pixel 3XL) already has those fixes included.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] roblav96:
[MENTION=912474]Dees_Troy[/MENTION] [MENTION=2638973]bigbiff[/MENTION] where can one find the source of `twrp-3.2.3-5-crosshatch.img` im unable to find any recent commits or forks on github. i booted the latest `twrp-3.2.3-5-crosshatch.img` on my Pixel 3 (blueline) no problem, but obviously there was a device code mismatch when trying to install latest DirtyUnicorns official build for blueline. id like to compile the latest `twrp-3.2.3-5` for blueline so i can start using the latest offical roms being published. thanks yaaa =]
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
TWRP does not host their code on their github, it is in the omni github under android_bootable_recovery or something like that.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] kaicat:
Same issue here, bothered me whole day
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] anyinnn:
sorry but i want 2 know when can we get updates for blueline:confused:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] kaicat:
Please update the twrp!!!!

I can't flash rom now:rolleyes:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
The sources are there for you to update it yourself. ETAs are not allowed.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] roblav96:
I just gave it a few hours trying to compile it myself, failed, so in retrospect a task that could take you a few minutes would take me a few hours, for the sake of efficiency could someone with prior knowledge and a build script push out a quickie?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] JCBiznatch:
You're not going to get that. As stated previously, there isn't going to be a push. Download the files, flash, if you need help, inbox me.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] EggZenBeanz:
I don't understand why there's no updated build for blueline and reluctance to produce one. Am I missing something in this thread?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
I don't know if it's a reluctance, it's probably more a priority elsewhere, especially with Q beta released. There's a larger user base for the XL and the current version for blueline is working relatively well. I'm sure [MENTION=912474]Dees_Troy[/MENTION] and the rest of Team win will get to it when they can.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] JCBiznatch:
It's still amazing that the smaller pixel always gets the short end of the stick. But, hey not all of us have a little guy syndrome and need a big phone. Lol
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] frewys:
My 2 cents. Activity in xl is because in the past xl was dominant but not so sure that is the case anymore

It's just habit for the posters to go there ?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ktdt00:
Seems like you need to Make both... This guide is pretty straight forward. https://xdaforums.com/showthread.php?t=1943625.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
Yep, that is the guide I followed and I showed what the output was.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] rczrider:
Isn't the only difference the resolution of the screen? It seems like it would be incredibly simple to change that single parameter in the XL / crosshatch source and spit out TWRP image for blueline. Now, I say that with complete ignorance of the process, though, so maybe it's not actually that simple.

To add: I don't mean any of it as a criticism of any dev or team. We are not entitled to TWRP. Most of us are users and contribute nothing but comments (good or bad). It's only by the passion and kindness of devs that we even have options like recoveries, ROMs, and kernels. I'm only commenting by way of discussion, since I clearly don't have a grasp on what goes into the development of TWRP.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] laupuy:
Great news, twrp 3.3.0.0 is out https://dl.twrp.me/blueline/

For information and changelog https://www.xda-developers.com/twrp-3-3-0-release/
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] SacredDeviL666:
have you had any success flashing it over 3.2.3 with installer zip of 3.3.0. I got a system corrupt error with red exclamation.

Probably need to follow the initial process of booting to temp twrp img and flash? better to wait for the op to be updated with new flashing proceedure if any.

Edit:- Success with below steps, not necessary you need to do all these steps as i had to because of system corrupt error.

flash vendor images, flashed stock boot img, temp booted twrp 3.3.0 img, flashed twrp 3.3.0 installer, dirty flashed the rom i am on, reflashed the twrp 3.3.0 zip installer and booted fine :good: if you are trying 3.3.0 installer zip directly before getting the error try with the bold/highlighted steps and see.

MTP is working with TWRP 3.3.0 recovery so :angel:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
I got it to work by

1) Flash boot.img of rom I am on

2) Temp boot twrp image

3) Flash installer

4) Done (unless you want Magisk)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
OK, apparently you just temp boot, then go to advanced->Install Recovery Ramdisk and chose the 3.3.0.0 image. MTP working and it fixes the keys issue on some custom roms.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Spannaa:
Yep, saw this on the DU Discord earlier.

Great to finally have MTP in recovery.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
The old way still works too, temp boot and using installer zip.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Spannaa:
Yes, saw that too, but there won't be an installer zip for the next version.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
Just make sure after rom install to boot to system, then go back and temp boot twrp or it will not stick.

Was my initial experience, but I will admit I did not attempt to replicate. Could have been a fluke.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Chezbel:
I booted to TWRP and installed the new version. When I tried to reboot to system it kept going back to TWRP, but after powering off and back on everything was fine.

EDIT:I did everything from my phone, no PC.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
I booted the device into twrp 3.2.3.0, flashed the 3.3.0.0 zip. Then used in twrp/advanced/fix recovery boot loop. Every thing works fine. No need for a pc if you have twrp installed on your device. I did remove security before booting into twrp, but I don't think that's necessary.

Just powering up the device didn't work for me.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] mistermojorizin:
Did you have to flash kernel and magisk after flashing twrp?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
I flashed magisk, but I might not have had to. I did have kiri kernel which did survive the flash so root might have also.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] mistermojorizin:
Did you flash magisk after doing fix recovery boot loop?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
Yes.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] choiia:
Bootet into TWRP 3.2.3.0.

Flashed TWRP 3.3.0.0 Installer.zip.

Bootet into System -> Root gone -> Bootet TWRP 3.3.0.0

Flashed Sultan Kernel -> Flashed Magisk -> Now, Everything is fine again!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Xdevillived666:
Does newest twrp work with Android q?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] UncertainSpin:
After updating to TWRP 3.3.0.0, I can no longer access any device via ADB while in recovery mode if the file system is encrypted.

Was this intentional? I see nothing about "twrp decrypt" being deprecated, and this command is now useless without a way to provide it while the device is encrypted.

Before: Flash TWRP, Set Lockscreen Password/PIN, reboot recovery, ADB shell, twrp decrypt "password" -> ADB access in recovery mode

Now: Flash TWRP, Set Lockscreen Password/PIN, reboot recovery, *No ADB Access*

This change/bug eliminates all recovery-based programmatic access to any device with a lockscreen. Let us know if you guys plan to fix this?

Thanks as always for the continued work.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
You should get a prompt to decrypt once twrp boots.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] UncertainSpin:
Yes, but this is a major change that kills programmatic access.

twrp decrypt

is now totally useless if the only option is "use the prompt". For automation, we cannot manually type a password every time.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NYCHitman1:
This isn't anything new. This has always been the case on A/B devices that set passwords in userspace.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] UncertainSpin:
Is the Pixel 2 (9.0) not an A/B device like this? If so, your assertion doesn't seem to fit.

On the Pixel 2:

3.2.3-x - Decrypt does not work with the correct password, known bug. ADB still works though.

3.3.0-0 - TWRP successfully decrypts from ADB and prompt. ADB works while encrypted.

On the Pixel 3:

3.2.3-x - Decrypt does not work with the correct password, known bug. ADB still works though.

3.3.0-0 - TWRP successfully decrypts from prompt, but ADB does not work while encrypted.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] kkjb:
My question just unlocked and using 3.3.0-0 wierd factory wipe, but if I include system to allow flashing new rom. /sdcard is erased too! I can't even do factory image flash. At end of bat all get odd wipe failure must use 3.3.0-0 and adb sideload to bring it back. So now kinda waiting...rooted magisk 19.1, April image. I don't encript. Return to 3.2.3 ? Ideas ?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] linqdesires:
Q beta 3 here and twrp is not even booting.

>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.523s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] wangdaning:
Must be some changes to the Q boot.img. I doubt it will get fixed until Q is actually released. The official release might be completely different than the one on Q beta.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ncnx700:
For some reason, I cannot get TWRP 3.3.0-0 to decrypt my Pixel 3. I type the PIN number I set during setup and it fails every time. I've tried loading twrp with 'fastboot boot twrp.img' (i renamed the twrp file) and it will properly boot from the bootloader. However, no matter how many times I try, TWRP will not decrypt the phone. I've loaded it about a half dozen times and have had the same results. I'm on the May 2019 security patch, Android Pie.

Edit: just tried setting a dummy password 'password' instead of a PIN and it still failed. Not sure what to do.

Edit 2: just tried using twrp image 3.2.3-0 with no luck. Same exact problem. Bootloader IS unlocked. Most recent version of Android. I'm currently unable to get it to decrypt the system and I've tried everything from different PINs to different passwords. If nobody has a good solution I'll just remove lockscreen security until I get my kernel of choice and magisk installed.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] linqdesires:
yeah, same here.

Android P may 2019 security patch image installed and twrp 3.3.0 is not decrypting anymore
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Xdevillived666:
Remove pin and try again.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] qtotter:
I can modify /system/system/etc/hosts using TWRP (with "adb shell"), but the modification doesn't work on Android. Am I missing something? I also tried the same using the file manager function of TWRP (copied a working hosts into /system/system/etc and changed the permission), but the result was the same. I tried 9.0.0 (PQ3A.190505.002, May 2019) and the older builds, also TWRP 3.2.3 and 3.3.0, but the results were the same.

If I root it with Magisk and do the same on Android, it works like other Pie devices, but this kills my payment app even after uninstalling Magisk...

Also, I can make backups with TWRP, but it goes blank after restoring the backup and rebooting into system. This function is not working yet?

I've been using Pixel 3 only for a day. Sorry, if I miss important points. I'd appreciate any insights. Thanks.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] drocny87:
I've noticed when I do a restore from a backup rom I get a blank screen as well. To boot up I have to reflash the rom and it boots up normal
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] qtotter:
Thanks for your comment, but I'd like to use the stock ROM...
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] drocny87:
If your gonna restore a backup of your stock rom I believe you can just reflash the stock rom and edit the flash-all.bat file by removing the -w from the script to save your data.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] qtotter:
I'd like to backup and restore modified stock system. Not as it is as stock...
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] GohanBurner:
Can we get the fixed TWRP that Pixel 3 XL got? 3.3.0-1 I believe it was. I'm going to revert to April.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] AndroidGX:
Not sure why, but since few times I boot now in TWRP (initially I reverted from Q to Pie), it looks like now my schema to unlock my device is always wrong (although it is of course the good one..), any idea on how to solve this?

Tried to wipe data, deleting and re-doing all my security stuffs (schema and finger prints, etc), but issue is still there.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Spannaa:
From the Pixel 3XL TWRP thread:

So I guess, until TWRP is updated, you'd need to use the same method of updating the Pixel 3 to the May images.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] AndroidGX:
OMG, Spannaa! long time no see! hope you are well mate :highfive: (since Galaxy S3, or S5, can't remember, hehe)

Thank you very much for your answer, I'll check that :good:

Cheers'
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Spannaa:
I'm good thanks, hope you are too.

It was the S2 - I've still got mine!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] onesolo:
When can we see v3.3.1.0 like on XL ?!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dees_Troy:
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/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dees_Troy:
Reserved!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mrbracht:
Thank you. [emoji5]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] freddienuxx:
Thank you so much so appreciated what you do brotha. Grateful
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jiao322528:
hello, after flash twrp, bootloader enter reason shows "combo key", and cant enter nomal OS. How to solve it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PewPewK:
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?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] freddienuxx:
Yup. You have to wait for a modified boot.img/kernel I totally forgot about that
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jiao322528:
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!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
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 ----------

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 [MENTION=5001535]freddienuxx[/MENTION] said. I'm not having a good morning guys.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
It's seems everything is working properly on the Pixel 3 but not the 3 XL.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
non responsive touch on p3xl 128gb

bootable working fine
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Reuben_skelz92:
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
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] canada2005:
A start in the right direction. Thanks Dees_Troy!