yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
No if you use that flash zip of magisk you don't.

---------- Post added at 01:34 PM ---------- Previous post was at 01:32 PM ----------

Umm not really just fastboot flash boot and then fastboot boot twrp, then flash kernel zip and flash twrp in same flashing succession. then flash magisk by hitting home button in twrp and hitting install again

---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------

That's right his zip in the op doesn't have the corrected util_functions.sh in it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] js042507:
Yeah, see my last update to my last reply. All is working. I did try flashing stock boot.img via fastboot method before and didn't seem to help. Ultimately, I think it was the updated Magisk version that solves everything.

Thanks again man!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
Yep, I'll be making a newer magisk later as well. This fixes the viper audio if on permissive kernel. We are working on enforcing now.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirFronts:
Thank you I'll have to try this soon

I'm running the new havoc os and maybe this will fix the not getting notification ringtones seeing how it seems I'm the only one having the issue
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] rickysidhu_:
Make sure this is default
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] rickysidhu_:
Still don't get sound?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirFronts:
Ya still not all the time it seems like if my phone's been set down for over 10 minutes it will give me notification sounds but if they're back-to-back it doesn't
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirFronts:
I installed twrp again had to install updated rom seems that update fixed my issues with rom but haven't done a back up yet but the time is still showing wrong lol

Update made a fast backup and just tried to restore right after so far so good
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dhayat1919:
Bagi aplikasinya bos

Mod edit

Please only use English language on the forums. You're free to use other languages as long as you provide an English translation, as per the XDA rule 4:

---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirFronts:
Huh? I don't understand sorry
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
for what it's worth, a quick google translate search has it "Share the application boss" (Indonesian). I don't think he knows how forums and replys work and might just be accidentally quoting as well as he might be mixing up threads (the Magisk thread is always talking about custom modules and .apks and such...always those kinds of requests there...)...

but yea [MENTION=9605097]dhayat1919[/MENTION], this is a ENGLISH ONLY forum, use translate.google.com if need be...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] crunkbeast4life:
Im trying to flash TWRP 3.2.3.1 but it keeps giving me a "failed" message in fastboot. I downloaded the TWRP app and it's saying my recovery partition is missing.

I fastboot boot into TWRP 3.2.3.1 to see if I can just flash the img through there but there is no recovery slot available?

Does anyone have a solution??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
After you fastboot into twrp using the image file, once your in twrp, you need to flash the twrp.zip file to install it as you default recovery. Always remember...you fastboot images, and flash zips. They are different animals :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Don't use fastboot to flash TWRP. Instead fastboot boot the TWRP.img. Then flash the TWRP installer.zip and latest Magisk.zip in TWRP and then reboot system.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] crunkbeast4life:
That's the thing though, when I flashed TWRP.zip it default flashed it on my boot partition because for some reason my phone doesn't recognize my recovery partition.

What's even weirder is that if I direct boot to recovery from off position or in bootloader, it pulls up the stock recovery!

I'll try redownloading the zip again and see what happens
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
The P2XL doesn't have a separate recovery partition per say. The stock boot.img also includes the recovery. No matter, something isn't right. Are your sdk platform-tools up to date? You should be on version 28.0.1. Which can cause problems if your not.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] crunkbeast4life:
Yes, it's all up to date. Worst come to worst I'll just wipe everything and start from scratch. It's just annoying to adb boot into recovery everytime I want to use it
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shindiggity:
I'm getting a problem where I'll fastboot twrp, install the zip and boot. If I try and boot back into twrp the phone just boots to system. Running latest Havoc. Anyone having this issue with Magisk 18.0?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
Try fastboot flash boot Boot.img extracted from the factory image. Or just flash_all
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
The output it gives when you're installing the .zip from within TWRP would be helpful.

...You shouldn't have the stock partition once you install the .zip from within TWRP. I would double check and make sure you have the "taimen" TWRP installation zip version 3.2.1-2 . I mean, the TWRP .zip is built by the same people and made specifically to be installed by its own program, so I can't imagine how it would be having trouble installing itself.

Oh! One thought I just had right now, by you flashing the image (.img) manually, you may have "forked" up the boot image/partition that TWRP doesn't recognize or decipher the boot partition properly. You may want/try to flash the stock boot image from the Full Factory google image (fastboot flash boot boot.img) or run the flash-all (with "-w" removed) and then try installing the TWRP .zip again (again, from within the TWRP environment)...

Good luck and hope this helps....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
You might want to read up on installing TWRP. It's clear that you don't understand how the installation works. You are asking for trouble, although the P2 XL can make a very interesting coaster or ash tray ;)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigknowz:
Pattern not recognized

[MENTION=912474]Dees_Troy[/MENTION] last 2 times i flashed a new kernel, pattern isn't being recognized when going back into TWRP to update. I have to flash boot and then TWRP image again to TWRP back. Any thoughts? Don't want to delete pattern, then I would lose all my fingerprint sign ins. Issue yesterday was with Snoke 9. Thanks in advance.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
what version of TWRP are you using? When's the last time (if ever) you've flashed a Full Factory image (without "-w" intact)? Have you tried running a "flash-all" type "re-installation" of the system?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigknowz:
TWRP

running 3.2.3-1, just clean flashed everything earlier this month to clean up the phone. That's when the issue began, not the worst issue, just can't update kernel without a computer.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Hmmm...I see...I guess, for what it's worth, you can remove your screen lock anytime you wish to boot into TWRP...when I had the same issue, that's what I resorted to...

I actually did resort to your issue, but for different reasons. It had nothing to do with the kernel, but I had done a nandroid TWRP backup with the fingerprint and pattern, then restored the system and data and even vendor image to a system that had no security screen lock set. My pattern would work and decrypt on normal boot, but wouldn't when loading up TWRP. In the end, I resorted to running the flash-all with the "-w" intact, and made sure that I backed up the /data partition with no security screen lock as well as only restoring the data partition.

You may also want to discuss this with the kernel's developer and see if it can't be attended to on that end...

Sorry couldn't help much, but good luck and Happy Holidays!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] libracez:
guys quick question, sorry if it's repeated but if i have plain stock setup installed by deuces script to both slots how can i continue to be sure to install twrp and then magisk to both slots?

coz i gave a lot of tries and just now i get stock system
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Twrp will install to both slots. Magisk will just do it's thing on whatever your active slot is. Really no need to worry about it at all. At least I haven't for the past 14 months :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
It's as the great [MENTION=3730810]Badger50[/MENTION] states, if you use their (both TWRP's and Magisk's) installation .zip's, it will automatically install it on the slots for you properly. There's nothing you should be worried about because the developers take care of it all (no need to manually fastboot flash anything towards any slots) -- which is kind of the reason why I don't like suggesting patching and flashing the boot.img yourself and don't suggest anything other than using the installation .zips.

It's all good, go ahead in confidence...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Anyone have decryption issues with the January patch?

I had a pattern lock and TWRP did not decrypt.

Rebooted and switched security to pin and decryption worked. I have yet to try and duplicate the issue.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigv5150:
I had a pattern lock and it worked
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I reinstalled the pattern and rebooted to TWRP, now it is working. Strange!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
For what it's worth, I've been using pattern for the life of the phone and have not seen decryption issues for like over 6 months. Prolly more... Whenever the fix was a few versions ago.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Uh......okay?? :confused:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Well good for you :silly:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I recently did a clean flash of the February Stock image, due to issues with a mod that corrupted the System UI.

Everything works fine, but now I am getting the red "your system is corrupt and can't be trusted" warning, as well as the orange one that we usually get when rooted. In the past flashing a custom kernel and the most up to date Magisk.zip got rid of the red "corrupt" warning. But it hasn't, at least for me.

Has anyone experienced this issue recently? Anyone come up with a solution, besides clicking through the warning?

Thanks,
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] spaceman860:
Flash the vbmeta image with fastboot
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] yyz71:
Yes I encountered the same problem with my pIxel 3. Just reflash the all-bat in the platform tools no need to wipe anything and you should be good to go ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Thanks, that worked![emoji3]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Hi all,

Old crackflasher playing around on my Taimen. I was on the Feb release and rooted via Magisk. Booted TWRP 3.2.3-1 via BL, proceeded to make a backup, which got stored into /sdcard/TWRP/{Serial number}. Copied that {Serial number} folder to my HD for backup.

I then wiped everything and installed BlissROM 11.5 RC1. Played around a bit, and then decided to go back to stock. Wiped everything, then used adb push to push the {Serial number} folder back to its location - and TWRP refuses to recognize that it is a backup, until I use the file manager to move the folder underneath it (with a 1970-xx name) to the same level as {Serial number}.

Is this a known issue? Also, any other things I need to watch for when restoring this image (as in, OK to let it load every partition that was backed up)?

I'm starting with a fresh, clean install of the Feb release on both slots just to be safe that nothing is left over from Bliss, a 2 attempts at restoring the TWRP backup with Bliss still installed (even though I wiped - thrice!) hasn't worked at all. So, I manually ran flash-all from the Feb factory image, let it reboot, booted it back to BL, changed slot, and ran flash-all again.

I'm slowly working through the thread, but it's long AF.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Yea...TWRP seems to be really fickle about the naming/folder placement conventions in order to successfully detect a backup.... I'm not sure if it's a "known issue"...but I sure know about it...

Also, after running the "flash-all.bat", you only need to restore /DATA or the data partition (this holds your apps and your settings) -- which is basically all you should be concerned with -- because, if you think about it, going through all that with the flash-all pretty much inputs a clean copy of the other partitions (/vendor, /system, /boot, etc.) so you shouldn't/wouldn't need to replace all that with your TWRP backup. Honestly, I've personally never been able to successfully restore anything other than the /data backup anyways. But, hopefully, you made other arrangements for your internal data (/internalsd) because TWRP (*normally) doesn't back that up (*there actually is a way, but there's added steps and can get rather convoluted)....

Also, just an added note; with the "flash-all.bat", you don't really need to select/choose a slot -- I've never ever needed to. The only instance I see that relevant is in Deuce's script and it's pretty much set up to flash manually on both (one, and then the other). So, if you really are concerned about that, it might just be easier to run Deuce's script than to run the "flash-all.bat" twice; once after manually choosing/forcing to be on a certain slot...

hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Roger that. It makes sense now, in retrospect, that I could have tried to load just /data and been done with it. I thought that perhaps installing BlissROM was messing with TWRP in some way so that when I tried to flash stock it was either not taking or else coming back as Bliss anyway, so that's why I did the whole Flash-all, change slot and flash-all again.

I did make arrangements for the internal storage - in fact, I had first made a Titanium Backup of all apps, before I started anything, and then made the TWRP backup, and finally not only copied both backup sets to my computer but also everything else in internal storage as well.

I was just curious if there was something I was missing - turns out, not a lot really.

Thanks for the suggestions. Now I better know what to do.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] boomerams4l:
I have tried searching around a little, but I am just plain horrible at finding an answer on this...

I see from the TWRP website that some more recent phones have newer versions available (ie pixel 3xl with 3.2.3-5). Do these iterations include anything that would benefit or apply to us Pixel 2xl owners?

I am one of those "gotta have the latest to be the greatest" kind of people and just wondering if we are missing out on anything. Thanks in advance for any help on the matter.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Ugh.

Manually flashed Q DP1. Now TWRP says it cannot decrypt my data.

Welcome me to the world of issues with TWRP lol.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
I used to be one of the "gotta have the latest and greatest" guys until I got tired of having to reset my devices, flash a newer version to correct the unknown issues in the latest and greatest version, etc...

Now I'm one of the "content on letting the (gotta have the latest and greatest guys) deal with all the bugs and resets and lost data" guys :p

It's money in the bank just waiting a few days or a week after the "latest and greatest" comes out and most of the bugs are found and fixed.

Usually, if TWRP or a kernel can be used across multiple devices, it will be spelled out in the title ***TWRP 3.2.3-1 (taimen/crosshatch)*** or mentioned in the OP. If it isn't mentioned, I would NOT assume a pixel is a pixel is a pixel, so TWRP for one should work for all :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Does it work if you remove screen lock? :confused:

---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------

Amen to all of that my brother! Shoot, I still like my flip phone! :laugh:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ne0ns4l4m4nder:
Guys pixel 2 xl can use regular twrp to flash even if it asks for password!!! Just skip the password and push the magisk.zip to /mnt and install from there and it will work, I did it myself. /Mnt is never encrypted for some reason
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
I'll give that a shot.

---------- Post added at 07:34 PM ---------- Previous post was at 07:14 PM ----------

Bingo! That worked! Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
FYI, I believe this is also true for the /data partition as well...possibly other partitions, I imagine...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] drewski_1:
on the TWRP website they outlined their versioning scheme.

haven't looked recently so not sure if it's in a FAQ or what, but the number after the '-' (i.e. the 5, in your 3XL example) is for device specific updates which means the 3xl is on 3.2.3-* the same version as the 2XL

it just means they had a few more iterations before getting to a stable version than we did.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
edit - Thanks to [MENTION=3730810]Badger50[/MENTION] I did a rethink on this. If data is intentionally decrypted, then yes this is correct. I was thinking about the stock encrypted data, even when rooted and using TWRP. (damn honeybadger :angel: Made me do some research since my one cuppa was not enough - two espresso shots and some great googly-moogly later and my head is on straight now) :D

Not correct, data IS encrypted. That is the whole point of is to encrypt user data so that private information related to the phone user is protected from bad actors. That data encryption is enabled whether via wireless hacking intrusion or the bad actor having direct access to the phone via theft.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
I don't know about that one ole friend. Not really disagreeing with you, I just know that when twrp was in it's infancy in 2017 for our device, I flashed a few things from the data partition via twrp when it wasn't decrypting the data when my pin was entered. Of course, the solution then was to remove screen lock, then it worked fine. Haven't had to do that for a while, and maybe since 9.0 hit things have changed, but I definitely remember bypassing the twrp security log in to flash things back then. Heck, I still keep a copy of my substratum rescue zips in the data folder in case twrp decides to take a dump on me without warning :cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Simple enough to test. I can, right now, load TWRP, cancel the decrypt routine (which is not working anyway) and then try to pass a file to /data and see if TWRP gives it a gobbledygook name like all the other files there or if it is readable - and installable.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
Ok, corrected my post above. :o
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
And verified too.

Microsoft Windows [Version 10.0.18855.1000]
(c) 2018 Microsoft Corporation. All rights reserved.

D:\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
710KPMZ0254299 device

D:\platform-tools>adb reboot bootloader

D:\platform-tools>fastboot devices
710KPMZ0254299 fastboot

D:\platform-tools>fastboot boot twrp-3.2.3-1-taimen.img
Downloading 'boot.img' OKAY [ 0.291s]
booting OKAY [ 0.006s]
Finished. Total time: 0.432s

D:\platform-tools>

After I declined to attempt to decrypt, pushing the file was successful.

D:\platform-tools>adb devices
List of devices attached
710KPMZ0254299 recovery

D:\platform-tools>adb push "F:\Android related\Devices\Taimen\Root 4 Q\magisk-release_945f8810.zip" /data
F:\Android related\Devices\Taimen\Root 4 Q\magisk-release_...10.zip: 1 file pushed. 79.5 MB/s (4968154 bytes in 0.060s)

D:\platform-tools>

Even though pressing Install in TWRP showed the normal encrypted filenames, pressing up one level, then navigating to /data showed me readable folder names - including the Magisk canary .ZIP at the bottom.

So, I'd say it was successful - because of a misnomer. Here is what I think (please correct if I am wrong):

The data partition is what is encrypted. /data is a folder under root that is not mapped to that data partition, so is accessible to TWRP even without decrypting.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Yeah...I think it's easy to get /data folder and "user data" mixed up...because, essentially, /data folder merely holds the apps, personal settings, and customizations (home screen)...right? I don't see too much need to encrypt all that -- or at least not as much as personal files like pictures, documents, and videos...but thanks for "keeping me on my toes!" and checking my work...

Just wanted to say thanks for the backup, further explanation, and support (sort of)...! But you did bring something up to my mind that I hadn't considered, which is that things could have changed on Pie; I'm speaking from experience on Oreo...

Thanks for going out and doing the the work of confirming! That is weird...the actual partition is encrypted but /data doesn't contain the WHOLE data partition as I previously thought...! I dunno...maybe the data that has the encrypted folder and filenames is in a /internalsd partition and is simply rerouted when navigating through any file explorer...

But I appreciate you doing all that and checking...!

If anything, I put it out there just in case /mnt doesn't work or is inaccessible (for whatever reason) and it'd be a good idea to try another folder/partition...

Learning is fun!:silly:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Lol yes, learning is fun - and who knows, one day it might save somebody's bacon, too, so there is that.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Don't know why you have decrypting issues. No issues with twrp on Q. P2xl
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
I had no issues on Q either when I took it as an OTA from Pie.

As soon as I wiped my device and manually flashed the full system image for Q, it stopped decrypting my data partition - and I didn't change the PIN or anything.

I'm currently in the process of fully installing Pie again, setting everything up (including Fi) and then will take the waiting OTA back to Q - and see if it has any issues.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I'm sure you're aware of this...but it's still worth warning just in case...

Be careful about downgrading, especially through OTA's...I'm just recalling back when Pie was in beta... Whenever anyone wanted to downgrade back to Oreo, even if it was OTA, they would have to remove themselves from the "beta enrollment", which would then trigger an OTA to downgrade,

BUT

(most importantly) it would also wipe the device before installing Oreo back on...

So, just make sure to back up everything and be aware that, based off of past experiences, doing so via OTA might force your device to be wiped...