yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
Where did you get Magnum Opus?

Sent from my Pixel 2 XL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
https://androidfilehost.com/?fid=889964283620765959

Then pull the arise_customize.prop from the zip in your_system folder and place on /sdcard and flash.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] js042507:
Oh ok. LOL. Still, you contribute more than most. However, I always used ARISE on an enforcing kernel. This was on my last phone though, have not tried it on the pixel.

Anyways, I just realized that TWRP is working! LOL. I'll just flash the modules that way instead of from the Magisk Manager

---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------

Here is the original ARISE forum. https://www.google.com/amp/s/xdafor...sound-systems-auditory-research-t3379709/amp/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
Something in the script for arise I believe is not working in pixel 2 and xl for enforcing.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] eqbirvin:
Yeah it is having issues installing as is right now. They will have to update or we will have to do a bit of tinkering on our side
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
Mine works but only in permissive. Open terminal and type su and hit enter. Then to setenforce 0 and enter. Changes to permissive. 1 changes back to enforcing. But you have to use the newest magisk I posted that has the avb-verity changes.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
How long do you have to have it in permissive mode?

Sent from my Pixel 2 XL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
When using it. You can turn it off when done lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
So, I can turn permissive mode off when not using a media program?

Sent from my Pixel 2 XL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
I have been. I use smanager and create script widgets to toggle on and off within seconds.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] js042507:
Just curious, has anybody tried flashing a full OTA zip with TWRP? I was going to try and flash it, but I am not sure if it's going to wipe my device because of that -w switch or whatever. Anybody?

EDIT: nevermind. The OTA definitely shouldn't wipe your device. However, attempting to install failed. Received a 'no digest file present' error.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jamiejames:
Is anyone getting, there is a internal problem with your device, on startup? 8.1, Magisk 14.4.2, Twrp beta 2. Everything appears to be working perfectly. Just curious.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alsip1023:
If you read the latest info on the official TWRP post, it specifically says SuperSU. This is a snippet from the instructions:

"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 with SuperSU, 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, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU."
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
This was copied and pasted from the last pixels instructions, hence the reference to 2015 supersu version
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] galaxys:
Looks like the op did a copy and paste from another TWRP (2015-11-15)? They maintain TWRP for a zillion device's...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alsip1023:
Derp... I saw the November date and was like yeah that's crazy recent. I guess it was too excited to notice that was so 2015.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Yep. I updated via fastboot with the -w removed. Then fastbooted twrp 3.2.3-1 then flashed the twrp installer zip, then magisk 18.1 and Ex kernel. Just FYI, the newest versions of twrp and magisk didn't work for me, but did for several others. Go figure :fingers-crossed:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] occtec:
Hi I'm having an issue with twrp recovery disappearing after flash magisk? Both are the latest stable version I'm currently on Havoc-OS- on my pixel 2xl. Please see attached recovery logs it seems it reverts back to stock recovery. Could someone shed some light on this please. Thanks in advance.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
After taking a look at your recovery log, I have some suggestions...

First, as a general rule, Magisk doesn't really like "playing with others", so it really is best to install it as the last flash.

Second, many experts here (most outspokenly [MENTION=4670411]Az Biker[/MENTION]) say to flash one at a time, and reboot

each and every time

after every flash.

Third, you should have mentioned that you were also installing a custom kernel -- it is a very important distinction -- and also important to have stated is that you were installing it along side of/in tandem with Magisk (using the "add more .zips" option). I personally do this method as well (on my Stock ROM though), but doing it this way has chances to cause such bugs and inconsistencies...

Fourth, I noted that the custom kernel you were flashing with Magisk is Caesium (good choice, btw), but, usually, installation of custom kernels wouldn't result in reverting the custom recovery. But, as the recovery now resides in the boot partition, and the custom kernel has to modify that and the dtbo, it may be inadvertently doing it -- I doubt it has to do with your custom ROM, but it might -- so it would be a good idea to make sure that you are using all the up-to-date, latest installation flash .zip of Caesium.

In the end, you should reconsider the order in which you flash your custom anythings (Magisk should always be last), only flash one .zip at a time with reboots to bootloader after each and every flash, and make sure everything is up-to-date...

Hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] occtec:
OK, Caesium Kernel retains root apparently so this should not be an issue flashing it after magisk as for rebooting back to recovery after every flash, i haven't heard of the need to do this nor have i had any issue not doing this in the past?? As for flashing a custom kernel, this kernel is baked into Havoc-OS but due to loosing recovery and baked in kernel after flashing twrp i had to re-flash the custom kernel and this was never done using (add more zips option).. Point taken on your Fourth annotation, i should not have a reason to flash the custom kernel if all goes well with the rest and ill definitely try rebooting between each flash, is that directly into bootloader, then recovery or recovery directly? Much appreciated & cheers
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] occtec:
Thanks for all the help guys but my issues are finally sorted thanks too [MENTION=4667597]Didgeridoohan[/MENTION] on the Magisk thread & [MENTION=1434592]sharkie405[/MENTION] on the Havoc-OS thread who both pointed out what I was actually doing wrong which was, flashing the twrp.zip recovery before flashing HavocOS which was replacing twrp recovery with stock recovery. Thanks again to all! Now I can finally rejoice and use my phone as intended. Cheers ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
By the way since you are using havoc, there is no need to install Caesium. It already comes with the havoc rom.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] occtec:
Yeah I know, just needed it as backup
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
I just wanted to mention you have made many of us smile today... Your post above noting what your actual root cause was as well as the way to reproduce it and the fix is spot on! I so wish folks would take this practice and run with it. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] occtec:
I think it's commonsense and the help on XDA has been great, it's nice to come back to a breath of fresh air after a one year break from tinkering with devices and yes you are right, it would be good practice for all. Thanks & have a great day :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dcrewchief:
I am running 3.3.0 twrp. Works well for me on pixel 2 xl
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
+1 here
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Can either of you say if you did a clean install of the may update with that version? Not updating??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pkgnex:
I did a clean update of Q dp3.

Worked fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Man this 2xl is just whacked. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharkie405:
I used to be able to flash from /data since TWRP can't encrypt these days, but lately, maybe every since the May update, I get errors when trying to flash from /data if I've got security set up in the phone (PIN). Is /data known to not work anymore?

I can't remember the specific TWRP error. I know, I should have paid more attention. It happens on 3.3.0.0 and the build before that. I haven't tried going further back.

Edit: Nevermind. /data/app works. Maybe that's what I always used to use, and I just had a brain fart and forgot. Who knows. In an event, /data/app will work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GoldElocks:
I have been disabling my password in rom before booting into TWRP to flash or backup anything otherwise I get the encryption failed error. Is there a workaround for this issue or is this standard protocol for using TWRP now with this phone? I thought I remembered not having this issue when I first unlocked the phone. Would flashing TWRP via fastboot make any difference?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] afilopou:
Clean flash with April image. Do all the upgrades and flash TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Many of us have been doing just that for like a year now. Unless you have an app that forces some crap to reconnect it's the safest way. Some Bank apps have been known to require cumbersome actions if you kill the security but I've never had the smallest issue. I switch from pattern and fingerprint to NONE for all my updates or fresh installs then put it back. No sweat...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dcrewchief:
Good to here this. I also found that out the hard way. Had to start over before i realized i could enable an unable security. I set up a swipe action and twrp likes that.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joeo10:
Deleted
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Piout:
+1
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] manhb01:
Do I need to unlock bootloader before installing?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Well said my brother... Well said. :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
You know me bro! :laugh:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] manhb01:
Should I choose normal unlock or critical unlock? I'm using pixel 2 xl.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
Normal is good unless your booloader is old.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] manhb01:
Hi, I've unlocked successfully and now trying to flash TWRP. However when TWRP ask for the password to decrypt data, I entered my PIN (including 5 digits) but it said decrypt failed. What should I do?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sticky Fin:
May update seems to break the TWRP decrypt data. Refer here to understand more. Otherwise, remove pin/pattern/password before booting into TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] manhb01:
Worked. Thanks a lot.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Darione90:
Hi, clean flash latest havoc, latest twrp, but pin not working, the steps are, fastboot boot twrp.img, flash rom, flash twrp.zip, reboot twrp flash magisk, reboot, i do something wrong?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
You did it right. Decryption isn't working on the pixel 2xl. You'll have to remove your pin everytime you go into TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arvylas:
Or you can sideload the zips you want
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Darione90:
but for use sideload you need to enter twrp no?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arvylas:
Yeah obviously but you don't need to decrypt your data so you don't need to remove your lock screen methods
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sacca25:
So the only option if I have clean flashed may, june or july factory image is still going back to april and then OTA updates to have working decryption?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Somewhat working decryption. I found back at the end of Dec or Jan that, though the phone was decrypting seemingly correctly when booting TWRP, a full TWRP Nandroid backup would not restore correctly (I cannot remember exactly which parts were breaking, but it was breaking on a full restore, for sure).

Since you're able to boot TWRP, you've already unlocked your bootloader. Temporarily removing the phone lock mechanism (pattern / PIN) is just as easy, but I haven't verified if a fully unlocked non PIN / pattern protected phone can restore a full backup or not (Something I should probably take the time to do, eh?). Even if you use FP unlocking, setting up the FPs again takes literally less than 2 minutes for 2 fingers, after re-enabling the lock pattern / PIN, which itself takes all of 15 seconds.

But if you're sideloading, no need to decrypt anything to begin with, as [MENTION=4544285]arvylas[/MENTION] said.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ZVNexus:
Can anyone running TWRP on the P2XL confirm that vibrate is working?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Are you talking about vibrate in general, or vibrating within TWRP functionality?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
It is not working for me in TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
confirmed here as well.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ZVNexus:
Alright thanks for confirming, working on TWRP for the 3A and was wondering if it was working on 2/XL because the haptics driver for the 3A was ported from 2/XL and I saw that haptics were not excluded for TWRP on the 2XL.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
That's interesting...but I've noticed for many months now that my vibrate hadnt worked in TWRP...but I figure that that could've just been me...

*because everytime I reinstall TWRP after a monthly flash/update, I go through all the settings to make sure everything is set correctly, and I always stop a "beat" when I get to the vibration settings and max it out, yet not feel anything...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
IIRC, yeah,. the problem also existed on 3231. And, remember, we're still on 3300, not 3310, too.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] last_nooby:
But I remember a version that worked well with encrypted partition.

So what happened? Why isn't possible?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
I'm guessing you wiped on Q?

If you go back to Pie's April version (? I might be mistaken, [MENTION=4831195]buffal0b1ll[/MENTION] will know more ~ he did it, I didn't) and update from there without wiping, TWRP will decrypt.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
I'm running havoc-os currently and wanted to start the settings fresh. If I wipe data will that keep my apps? Logins etc?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
No.

If you are backed up with Google, you will get most of your apps back (if they were downloaded from the Play Store), but will probably have to log into them again, except for the Google apps of course.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
^^^^ This - it was tested by a few folks, including me, and it worked perfectly.

However, Q over Pie caused *me* issues, so I went ahead and wiped at ßeta 2 build .19 anyway, and just started removing the PIN for the very, very few times that I wanted / needed to use TWRP for anything.

The reason I rarely every use TWRP is because Magisk has a built-in method for taking OTAs, even the Q builds, that allows you to do everything from within the app on the device with no external computer (nor TWRP) required, and it's worked on my device through all the ßetas (when there was a working Magisk to the coresponding new ßeta build, of course). For ßetas 5 & 6 Magisk has pretty much worked perfectly fine with no wait time for a new Magisk build. They outline their method at this page - and I've been using it flawlessly: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Of course, if you're cleanly installing anything newer than Android Pie April build, use the full system image via fastboot (and an external device), and don't set up any PW / PIN / Pattern / etc. Then you can boot into TWRP and do what you need to and won't have to boot back into the system, remove the PIN / Pattenr / PW, then reboot into TWRP again, wasting all that time. Finish what you got to do, then when you boot back into the system, finally add the PIN / PW / Pattern.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alershka:
With final 10 coming out in a few days, I am looking to go back and flash April then update. I wanted to make sure I am catching all of the nuances so please correct me if I'm wrong. I am on Q b6 currently. I fastboot boot TWRP. I have stock recovery with Magisk Canary and Sultan Kernel.

Backup everything via TiBu

Remove pin and backup data in TWRP.

Flash the April full update via the flash all with -w enabled.

Set up phone then take 10 ota

Install Magisk via fastboot'd twrp

Restore data from twrp backup taken beforehand

Restore pin and any data missing from TiBU backup

Moving forward, I was not going to flash Sultan, instead keep everything stock so I can take the OTAs and not need TWRP. However I wanted to do this so that if I did need TWRP in the future, the pin deletion wouldn't be needed.

I am also doing this because I did wipe during the beta and now my Android Auto is not working correctly so I am hoping going back to a previous Pie install will fix the low audio volume issue I have with Android Auto.

Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
One thing I see is -- and anyone correct me if I'm wrong, things might've changed in the last few months -- because you have an unlocked bootloader, you most likely won't be able to "take 10 ota" literally over-the-air to upgrade. Also, do

NOT

lock your bootloader just to do this! Way too many stories of people irreparably bricking their phones attempting so. What you can always do is download the OTA and install it using the stock recovery. I personally would just download and flash the Full Factory directly; but to each their own.

Hopefully this is helpful...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hawknest:
[MENTION=912474]Dees_Troy[/MENTION] , I Sent you a PM in regard to recovery for the Verizon Pixel 2 xl..
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
You can upload full factory OTA images from the Android Developer's website and flash them in TWRP. Or, if you want to be old-school, sideload the OTA.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
uh, no, sorry, you're wrong.

BL unlock has not interfered with any of the Q ßetas, and I'm actually currently taknig the 10 final right now - with my BL still unlocked.

I'm also rooted via Magisk, but am using this method to install - it's worked flawlessly for me every time I've used it except for once, which was user error.

https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Ifthe OTA fails these are always backup options. But as long as root is not active, you can take the OTA even with an unlocked BL.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Chance Ill:
Is there any particular way it should be done? Every time I tried, I ended up with errors and wound up flashing manually
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] paulCIA:
I think Google's magic differential A/B OTA patcher is just ****ty because a lot of people complain about being unable to install OTAs on Pixel phones even if they never touched the bootloader or system anything. OTAs used to work fine for me even with an unlocked bootloader as long as I'd restored the boot partition, but lately almost every one has been failing for no apparent reason unless i had just factory reset the phone and I end up having to sideload the full OTA. And that is indeed Google's official response to these non developer type people who have the problem, factory reset and try again.

I'll bet if the patcher used the full OTA this problem wouldn't exist. I can't remember when they started doing the differential OTA thing but I'll bet it has something to do with that and/or the A/B patching because they are not easy to implement and the quality of Google engineering is not what it used to be (typically what happens when the bean counters take over a company).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
I've had very few problems with it. And every problem I've had can be traced back to something either that *I* did or something that I *didn't* do (like update drivers on my computer when using flash-all.bat, or forgetting to disable selective USB suspend (yes, it makes a difference on my computer, because when in the BL, and flashing a single item and rebooting back to the BL, sometimes my computer detects the USB device disconnecting aka rebooting and shuts off that USB port, and I have to manually reboot to BL again by the device for the system to reactivate the USB port)).

With the BL unlocked, I do have an advantage, because if I hose things up (I've twice gotten my Taimen to a state where at startup it tells me that my system is corrupt) I can then manually flash either (or both) of the slots with stock and get back up and running again.

TBH, I realize that not everyone is computer savvy, but the security offered by having a locked BL is offset strongly by not being able to do jack to fix it if something goes awry.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joeo10:
Keep in mind that TiBU doesn't back up some apps properly due to split APKs so should use Swift Backup instead for that purpose.

I use both since TiBU still is good for system backups.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alershka:
Thanks! I have been using TiBU so long and have had issues with restores but never knew why. I will have to check out Swift Backup for app backup moving forward.

I wound up doing both to the TiBu backup and the TWRP backup of Data. Used the March 2019 system image via Flash-All.bat (keeping the -w) then flashing B6 image (removing the -w) and then restored data via Twrp. This didn't allow twrp to decrypt after the restore so I am assuming I needed to take the otas instead of flashing the image for it to work. It wasn't important enough to me to redo so back to removing the pin.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Correct on the above - OTAs don't break the decryption in TWRP, but full system flashing does.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clever_man:
Yesterday I flashed latest Android 10 (clean install). After that I booted into twrp 3.3.0 (latest for that moment) and tried backup my firmware but get error

Failed to mount '/system'

Is any solution for making backup Android 10?