yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
[MENTION=912474]Dees_Troy[/MENTION] - So, seeing as 33.0 is official, are you going to be creating a new TWRP 33.0 thread for the various supported devices, or would it be easier for other users / mods to do so on your behalf?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] g0at1:
Actually, that was my understanding from Magisk changelog...

Anyway, I'll try that soon.

Thanks for clarifying.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
I was able to upgrade to 3.3, there was one weird thing. Booted the 3.3 img, flashed the 3.3 zip, flashed kernel, flashed magisk, and reboot to system. It wouldn't boot, got stuck on the last stage of the google boot screen and I let it sit there for about 5 minutes. Plugged in the phone and did adb reboot, and it booted fine. So not sure why it wouldn't boot the first time, but everything seems to be working fine.

So when I update next time, do I just download the .img, go to recovery, pick "install to recovery ramdisk" and select the .img file, and that's it? No need to flash kernel and magisk and it'll just preserve everything?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
When you install an OTA a new boot.img is installed, so you'll need to install a custom kernel if you use one, TWRP, then Magisk, in that order. TWRP will be installed using "install to recovery ramdisk".
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
What about if i'm just installing a new version of TWRP, no OTA?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Yah I'm still in the dark about the future path of TWRP. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigknowz:
Flashing sequence

Is this based on the new features of 3.3? Most Custom ROM instructions are TWRP, Magisk, Kernel. Thanks.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
You will still have to flash Magisk to avoid a TWRP bootloop after flashing TWRP to the recovery ramdisk. The TWRP bootloop was what I encountered after upgrading. Flashing Magisk resolved the bootloop.

You're joking, right?

What 3.3.0-0 does is virtually restore the TWRP install process to the way it was before Google introduced seamless update devices. With recent devices (within the last five years or so) you only had to download the image and flash it to the recovery partition using the "Install Image" feature. With 3.3.0-0 the "Install Image" feature actually becomes useful on devices with seamless updates. With TWRP the only difference between most devices out there and a device with seamless updates is the location of the recovery. Most devices have a separate recovery partition while seamless update devices use a ramdisk in boot.img instead. Thus when installing a TWRP image with 3.3.0-0 or later you'll have a choice of the recovery partition (for most devices) or the recovery ramdisk (for seamless update devices).

Because TWRP can now install images to the recovery ramdisk, the zip files we needed to properly install TWRP are no longer required.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Actually what I meant was I've not seen this for myself. I get what your saying about the old way like my 6p where you just install and forget about it unless you update it. So I guess once the interim zip version is installed, the subsequent updates will be from within TWRP?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
The order I believe should be kernel, TWRP, Magisk, and here's why. Custom kernels are packaged as boot images, and are drop in replacements for the stock boot image. If the custom boot image were not installed first, TWRP and Magisk would make their changes to the stock boot image, which would then be overwritten by the custom boot image. So you would have your custom kernel, but no TWRP and no Magisk. I would however not take my word for it, as I do not use a custom kernel. There may well be advancements in kernel installations I am not aware of.

Exactly. The 3.3.0-0 zip is provided as a convenience and nothing more. It's not actually required so long as you have a copy of the recovery image on the PC. This is because with fastboot you can boot into the TWRP image on the PC, then navigate to the recovery image on the device, and install the image that way. It should be crystal clear on the website, but the XDA Portal article regarding the release of 3.3.0-0 makes it clear that future versions of TWRP will not have the zip file at all. Either fastboot and a PC, or a version of TWRP with the ability to install images to the ramdisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
So all installed with zip but still a bit confused about something. Do we still need to flash the custom kernel (if installed) and Magisk once we have installed TWRP using the ramdisk option or will it be stand alone at that point?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
If the kernel is already installed when installing TWRP you shouldn't need to install the kernel again unless it's updated. Magisk will likely have to be installed again. I had to flash Magisk after flashing TWRP to avoid the TWRP bootloop I encountered.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I can definitely confirm [emoji4] Just reflashed the TWRP 3.3.img to the recovery ramdisk and flashed the Magisk.zip. Booted up without a hitch. The custom kernel was preserved.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
What if you want to run a custom recovery but no root?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Try it because I don't see anyone here trying without root.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
I think it'll work fine. Example: many users, including myself, have flashed custom roms, followed by twrp, then let the rom boot up, then go back to twrp to flash root, and twrp is fine :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
Yes, you can use a custom recovery without root.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
Not sure what I did wrong then.

I flashed a ROM, went to advanced>patch recovery ramdisk, chose 3.3.0 image. Got the message that it was patched successfully, booted up into system, but when I tried to reboot into recovery I was on stock recovery.

I must have done something wrong, but I can't imagine what it could be
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Most likely what you did wrong is not immediately reboot into recovery. On the P2XL this could be different, but on most devices, booting into Android allowes a script to run which restores the stock recovery.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
I have always made it a point to boot into TWRP once I've installed it. While I do have a 2 XL, I'm not sure if this is proprietary to the 2 XL, but it's been a "superstitious" thing I've done since the 6P :p
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
I'll have to try that, I think I might've tried that too, but I can't remember for sure, since I tried a few different things with the same result. Will try tonight after work and report. Cheers.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] srqrob:
So best practice on updates for the 2XL now is to (1) take the monthly security update, (2) boot the 3.3.0 TWRP img, then go to advanced>patch recovery ramdisk, chose 3.3.0 image, (3) exit TWRP to the bootloader and reboot TWRP, and finally (4) install Magisk (add a kernel if that's your preference) and finally reboot system?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] HueyT:
Anyone ever get stuck on TWRP 3.3.3.0 boot logo screen--I let it sat for 10 min and no luck. Hard-button power off reboots to same stuck TWRP logo screen. Hard-button bootloader mode works so try to change active slots and reboots. NO luck. Finally had to fastboot flash stock 4/2019 (preserving data by removing "-w" wording by editing "flash-all.bat"). Only then will it load stock 4/2019. Scary thing was that "dirty flashing" stock worked on 2/2019 Nitrogen-OS's data which was the custom rom I was on when this happened (was backing up Nitrogen-OS in TWRP and then rebooting back to Nitrogen when I got stuck).:confused:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MrBrady:
I've had that happen with certain kernel installed. Typically a couple hard resets fixes it though. Never have had to reinstall the system because of it.

If you get stuck, try reflashing just dtbo, boot, and twrp.

Example: fastboot flash dtbo [path to your dtbo file]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I'm in Q beta 2 and TWRP 3.3.0 won't let me enter my password. Keeps saying password is incorrect. If I want to use it, I have to first remove my pin. Is there something I should be doing?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ChrisDos:
Restoring an encrypted backup is not successful for me. Backups of both stock and Pixeldust result it not being able to restore. Unencrypted restores of backups work fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Piout:
I had the same issue. I got smart and changed my screen lock from a password to a pattern. Presto, everything worked. Not sure why it didn't work but now I can at least go in.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I'm going to try that.

---------- Post added at 10:28 PM ---------- Previous post was at 10:23 PM ----------

Didn't work for me. Said pattern was incorrect.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
im on Pie and had to do a factory wipe and start from scratch.

booting into twrp it keeps saying pattern wrong also.

i think may update broken twrp

any advice?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
Yes I had to go to scratch like you.

I thought it was me I had to go back to

twrp-pixel2-installer-taimen-3.2.3-1.zip
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
so on 3.2.3-1 you can decrypt data?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
No Version will allow me too.

I was doing more testing trying different versions.

You must remove all security pin etc in order for TWRP to to work
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
Seems like it's not affecting everyone.

Sultan on his thread says he on may update and twrp decrypts fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] loadie:
Because I forgot to remove it, I flashed the may security update without removing my pattern/fingerprint lock. Fastbooted 3.3.0 img, pushed img to ramdisk in twrp. Did not use the zip. Rebooted recovery, flashed magisk 19.1. booted to system, updated ex kernal to may in ex app.. decrypting works every time with Patten lock. Also, surprisingly I did not have to reapply fingerprint or pattern.

Probably just dumb luck..
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
3.3.0 Decrypts data great on Android 10.0 dp3, Q3. It does not mount System or Vendor on this developer preview. 3.3 works fine on p!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] RogerF81:
I think it's just a difference whether one clean flashes the May update or if one just does a dirty flash. I was dirty flashing the May update and TWRP could decrypt data just fine. Updgrated to Q DP3, TWRP could decrypt data, even with pattern unlock set, but wasn't able to mount system and vendor. Now I flashed back the May update, did a clean flash, and TWRP is not able to decrypt data.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
Yeah I think issue is only present if you clean flash it.

I doubt anyone will fix it.

Wonder if only choice is flash April image without wipe and then see if twrp decrypts.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] RogerF81:
I'm just doing a clean flash of April factory image, installing TWRP and updating to May afterwards. Hopefully this will do the trick.

Edit: Yes, this works!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
Thanks for confirming.

I will try non wipe flash to April image.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] RogerF81:
Ok nice! But you guys nearly all update by flashing the factory image, right? I sideloaded the OTA instead. I don't know if it makes any difference and I barely can imagine, but I still wanted to point this out.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
i never use ota or factory to update as I use custom ROMs so just flash vendor in fastboot.

something went wrong in my last flash which broke decryption in my ROM so had to start again
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] loadie:
I do.. remove -w .. but always full.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
I had to do something similar, after the first Q DP came out and then I chose to clean flash it. Presto, data decryption started failing.

I just went back and flashed the latest Pie (I believe it was still the March update at that time, but it might have already been the April update), then took the Q OTA again and data decryption worked.

I've since then not clean flashed anything, taking each successive push of Q DPs OTA - as I am about to do with Q DP3.

So, yeah, it seems that clean flashing the Q DPs (and now the May Pie Update as well) throws TWRP off its game.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
There must be an easier way. Restoring data each time is a pain!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GohanBurner:
Latest TWRP enables MTP file transfer for Pixel 3 XL and Pixel 3, will this be coming to the P2XL???
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] RogerF81:
Would be nice at least
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GohanBurner:
Anyone know why I can't boot TWRP on slot A? If I try to boot it it just sits at the splash screen forever and for some reason this particular phone is defaulting to slot b.

Also, TWRP is asking for a password when I am using a PIN and my pin AND password doesn't work to decrypt. This is on 3.3.0-0.

Lol, wtf is going on. I can't install TWRP. I flashed both April and May factory images, it keeps defaulting to slot B and asking for a password when I use a PIN and I cannot decrypt the data. WTF.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Have you tried using twrp 3.2.3-1 instead? Had a similar issue myself, as others have.

When you say "defaulting" to slot b, is that by using fastboot to install the factory image or using the OTA? Fastbooting the factory image doesn't change slots.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GohanBurner:
I flash the factory image, boot, transfer files, enable usb debugging, adb reboot bootloader, boot twrp, install rom & twrp installer, boot rom and setup (including pin and fingerprint), boot to twrp and it keeps asking for password when I didn't use one. Does this on the latest 3 builds of twrp. Never had this issue before.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Personally, I've never had that issue, then again I use a pin for twrp, or no screen lock security at all. This is the P2XL though, which means any strange, unexpected behavior, is to be expected. I couldn't fastboot twrp 3.3.0-0, or use magisk 19+ after the May update, so go figure :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
I'm having issues with 3.3.0 as well.

I was running May patch ABC by Ezio with no issues, then I decided to try Q Beta 3.

When I decided to go back to Pie I fastbooted a May factory image with -w removed to save my internal storage, and that's when sh!t hit the fan. I booted into recovery with the TWRP image, but it wouldn't accept my pin. I was forced to factory reset and wipe my device. I then managed to get into TWRP and flash ABC, booted up and set up my device. However, when I rebooted into recovery to flash Magisk TWRP wouldn't accept my PIN, so I had to boot up the system and remove my PIN, and only then was I able to get back into recovery to flash anything. I tried a pattern and a couple different PINs and TWRP won't accept any of them, I keep getting an "invalid password" message.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Strange, unexpected behavior? You aren't kidding. I briefly tried the Android Q beta, didn't like it, and clean flashed the May update. With the May update I've got the classic issue of TWRP - regardless of version - not being able to decrypt data even with a valid pin/password. I was up until 4am this morning trying to resolve this and failed. I guess I'll have to flash the April update and see what happens.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
I wonder if Q Beta is the culprit...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
I thought of that, but I clean flashed everything in going back onto Android 9. Shouldn't the clean flash resolve that?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
I would've thought that a fresh factory image and a factory reset would've done the trick, but I guess not. I really don't know why it would do this, I've never had this issue either on my old Marlin or Taimen.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Yeah...I think I skipped a step. I didn't factory reset prior to going back to Android 9, although the fastboot -w command should have resolved that. I'll reinstall Android 9 and factory reset from within Android.

EDIT: This should tell you just how often I muck about with my phone these days. I performed both the factory reset and installing the April update, and everything worked fine. So, chalk this one up to user error.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
I nuked my phone with the April factory image, then updated radio, bootloader and vendor up to May update individually. PIN still not working for me. Damn
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Over the life of this phone we have seen several updates that required TWRP and/or MAGISK need to do an update to function properly. May is starting to look like one of those updates... :(
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
I got everything working with pin

on the latest twrp-3.3.0-0-taimen, I installed the image not zip.

I did a full wipe and installed April using flash-all.sh

Booted up and skipped all the setup, and turn on adb.

And set up my pin.

Then I Installed May taimen-pq3a.190505.001

usinf flash-all.sh removing the (-W)

Fastbooted the twrp-3.3.0-0-taimen.img and I entered my pin and all decripted as expected.

Installed twrp-3.3.0-0-taimen.img and rebooted into recovery

All working as expected here.

I then rebooted and let the phone stay on fore a few moments.

To verify I adb reboot recovery and no issues.

I installed ElementalX-P2-2.16 and Magisk-v19.1

All functioning here.

Hope this helps
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
Yup for some season the May patch breaks TWRP decryption if you do a full wipe.

It will only work if you remove the -W when your on April vendor.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Actually, it's clean installing May *or* clean installing any Q DP - see my post here:

https://xdaforums.com/showpost.php?p=79490619&postcount=2749
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
Thanks for the info, went back to April patch and dirty flashed back into May, all working. Cheers!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Glad it worked - from another guy who made the move from Shamu to Taimen :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
That makes three of us. I still occasionally visit the land of the whale, simply because my Nexus 6 is still in use: my roommate uses it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DonQuixote77:
Still love my whale, I use it mainly for music and videos at home for my kids ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I regret trading it in when I purchased my Taimen from Google. Could have kept it as a backup.[emoji847]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
I know this thread is getting in the ditch but I couldn't resist... Lol

Clearly I have a problem!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Bwahahahahaha...you don't have a problem bruh! You have an OCD addiction!! Love it! :laugh::good::laugh::good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Lol nice. I pull mine out for nostalgia's sake - after all, I used the thing for damned near 3 years.

Once in a while I'll even flash something - usually when testing builds of SamuriHL's House of Google app.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Schroeder09:
I too wiped my phone and am not happy about it because I didn't get a good backup.

I'm not sure how you guys are getting your phones set right back up like nothing ever happened as is claimed in darkroom and in some threads here on XDA because the few times I have restored from a Google backup there is SOOOO much missing. This time I screwed up my titanium backup too, so I don't have a fall back and am SOL on some of the stuff I had on my phone. Any help would or tips would be appreciated. Which type of backup should I do in TB before doing a fresh install.

So I too have the TWRP issue since I clean flashed may. I have to delete all my PINs and fingerprints if I wanna get in TWRP. You're saying I have to wipe my phone again with a clean April flash, dirty flash may, then all will be good with TWRP? I see mention of a 3.3.0 TWRP (I think that was the version number.)? I'm using 3.2.3-1 and it seems to be working fine aside from the decryption issue which it sounds like is on the new TWRP too. BTW, I'm on a pixel 2 xl.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
Yeah, pretty much. I had the same problem after going back to pie from Q3. I did a clean flash of April then updated all of the partitions with fastboot to May. Now encryption works fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] EXV:
Would possibly reverting back to 3.2.3-1 TWRP work best for clean flashing new ROMs with no issues?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharkie405:
Deleted
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Hormesis:
Just to confirm, is it possible to use the May update without doing a complete wipe using the current version of TWRP? Just wondering if I should hold off.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] js042507:
Wow. Didn't know you actually wrote some of Magisk. Awesome man! Would you happen to know why I can't install modules from Magisk Manager? I've only trued Greenify and viper, but both give me a merge_mount failed installation error. If you have any ideas, I'd very much appreciate it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
No, did not write magisk lol. We changed some of the scripts. But looking into arise and why it's not working on enforcing kernel. But use the viper zip from arise Magnum opus. Be sure to have permissive kernel.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
[MENTION=2955144]bryantjopplin[/MENTION] I use these two mods (audio modification library, Viper4Android by ahrion) with an enforcing kernel I set to permissive with a Tasker action to setenforce to 0 on boot and, Viper4Android works perfectly

Edit update: couldn't post a picture in this forum, changed the language in my post

Sent from my Pixel 2 XL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
The magnum opus has Dolby digital and tons of others as well. That's why I used it.

---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------

I also just use scripts to change from 0 to 1 on command. Using widgets.