yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Good point... Several folks have already figured out they needed to wipe the phone to do it manually also.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Why did you do that? You were already on Q. What purpose did wiping the device and flashing the full system image for Q supposed to serve?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ne0ns4l4m4nder:
Glad I could help :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
I have the P2XL, Q beta, and TWRP 3.2.3-1

I fastboot boot it and don't have it installed on my phone

It decrypts data without a problem
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Yeah, no, I'm not going to do that - I said that his steps would be *much* easier than doing all that.

Plus, there is the fact that I already did it - but without disenrolling from the ßeta, by merely wiping the device and then flashing the full system image of the latest Pie for Taimen.

As for what you're saying about disenrolling from the program - yeah, it wipes your device, as it always has since Google began the ßeta testing of DPs (well, at least all the way back to Nougat, which is when I first joined on of their ßetas. And that was on Shamu, which came with Lollipop installed but got Marshmallow almost immediately after I bought it.).

It even clearly states that disenrolling will wipe your device: https://www.google.com/android/beta#faq

I was helping to test an app being developed by SamuriHL that automates, as much as possible, the download and flashing of both Full System Images as well as OTAs, and that is working on both Nexus devices as well as Pixel phones. He added code to handle installing the Q ßetas to the app, so I tested it for him by flashing Q with wipe. But an ancillary reason was that it had issues here and there that would not work, and I had read that some people got some of their issues fixed with a clean full system flash. Whereas my clean flash only resulted in more issues (like the loss of TWRP data partition decryption) with no real fixes for hte few issues I had.

I was the same when I initially took Q OTA over Pie. 0 issues.

Only started when I flashed the full system image of Q after a wipe.

I've already gone back and wiped, flashed P, set it up, and verified that decryption is working. Now, I've taken the Q OTA again (Since I did not disenroll, I merely wiped and flashed Pie full system, so the ßeta program sent me the Q OTA again as soon as I set up Pie with my user account).

I'm hoping the issue has gone away (or, more aptly, is working like it did that first time I installed the Q OTA), but I haven't actually had a chance to test. Yet.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Hi John I recall seeing your name and I believe corresponding with you on your postings back in my Nexus 6 days. Or it may have been as far back as my Droid bionic days.

I I remember samurai HL fondly, he helped me out way back, when he had his House of Bionic and House of Nexus set ups.

We were also in a somewhat private form together regarding Motorola devices. Please send my regards.

In order for you to get your encryption back, I suggest reverting back to Android p and then taking the Q OTA.

Best regards,
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Hi, LTNS!

Seeing as I have both the BIONIC and the Shamu, yeah, it could be either of those, though I'm betting it was, in fact, the BIONIC. As for SamuriHL, If you used HoMotorola and HoN, then you'll understand - he's developed House of Google (HoG) which works for both Nexus and Pixel phones. I (reverentially, of course :p) call it HoG (which means if you're wiping your device and flashing stock, you're putting your device through the HoGwash - OK, ok, bad pun, but it wasn't me who came up with it....)

The forum where he does his primary posting is (still) DroidRZR - IIRC, it should be the same one from before, as the device lists there go as far back as the Bionic. I'll definitely pass on your regards, but feel free to stop by and say hello yourself :)

As for TWRP decryption, yeah, I already wiped, flashed Pie full system, set it up, then took the Q OTA. Just haven't gotten around to actually checking whether decryption is working correctly or not.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
OK, checked and verified - just like I suspected and like you said - decryption working after flashing stock Pie, setting device up and taking Q OTA.

Now to fix GPay :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SamuriHL:
I'm still alive. ;) How things are good!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Hi SamuriHL, nice to hear from you! I'm doing well, owning the p2xl has forced me to learn rudimentary fastboot and ADB. Been enjoying Android Q on the preview.

Miss your posts about Motorola, barbecuing in life. How is Sarge? Best wishes.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] srqrob:
I don't know how many are in the boat with me but I no longer remove encryption when doing monthly updates. It's been three or four months. My routine now is to do the monthly security update and then do a queued flash of the TWRP zip, my kernel and then Magisk. Knock on wood, been flawless so far.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Well, the issue I had was that, after clean installing Q (with an unlocked bootloader on my Taimen), TWRP for Taimen (latest build) could not decrypt my data partition, resulting in an error message as well as gobblygook for every file in /sdcard/ (among other locations). This is with me live booting TWRP via

fastboot boot

command.

By wiping the device and installing Pie cleanly, I was able to get TWRP to decrypt the data partition successfully again, using the same live boot method. Then, installing Q by taking the offered OTA (as I never disenrolled from the βeta program when starting this journey), my live boot TWRP is still successfully decrypting the data partition, unlike with some other people reporting that Q broke decryption.

FWIW, I have avoided actually installing TWRP for as long as I have owned my Taimen because I am leery about not being able to take OTAs (with Magisk, the process is relatively easy, and it works perfectly fine - but I've seen too many issues with TWRP installed and trying to update the device - frequently I am not in a position to sit down at a computer and flash the full system image without the data wipe argument enabled). It works for me as it is, because I so rarely ever need to go into recovery in the first place, and I'm able to (relatively easily) take OTAs as well, without any manual intervention / manual loading of recovery.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
John, with Android P, I have been able to flash the full factory OTA's in TWRP with no issues. No computer needed!

The Q beta program OTA bypassed TWRP and seemed to install itself. Again, no computer or complicated Magisk Manager manuverings needed.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
Good to know.

On a (semi) side note, I've also got GPay working with root on Q without Magisk Props config use - strictly through Magisk Hide. The procedure outlined, though, gave an indication that an installed TWRP may lead to failure, although the poster couldn't say for sure since he also does not install TWRP.

Since I have everything working as I want it, I'll stick to not having it installed, for now.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
Hi .... I need help :/

I just made a full TWRP backup (saved on internal storage) and after that I restored an old backup excluding the data partition.

Now the phone shows "your device is corrupt" and TWRP doesn't ask for the decryption password when launched.

Therefor I'm stuck in TWRP without a chance to restore my backup

Any idea :(
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Fastboot the factory image to both slots without the -w. Then you should be able to fastboot into twrp and resume what you were doing.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
How did you get Gpay to work?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I'm betting you restored more than just the /data partition.... I've/We've all made that mistake. I'm sure, somehow, there is a way to get it to work, but I personally have never gotten restoring anything other than the /data partition to successfully restore and been able to boot into the OS (even after having broken and/or corrupted partitions)...

I don't know if you're coming from a custom or stock ROM, but if you were running a stock ROM, simply do as [MENTION=3730810]Badger50[/MENTION] had suggested -- running/flashing the Full Factory image without the "-w" attribute, and then load up TWRP afterwards -- and then Restore only the /data; in that way, you will have a stock fully stable ROM, but with your apps & custom settings/personalizations (/data) and your internal data (hopefully; it's what removing "-w" is supposed to do...)...

Good luck and hope this helps!

Do you mean just the app? ...or get it to work while rooted?

I am merely asking because I'd like to be informed if Google Pay hasn't been working on the P beta...

If you do mean get it "...to work" while rooted, he stated his surprise at just using the MagiskHide option was enough and not necessarily needing to modify any config files...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
THX, that did the trick.

Sadly my initial problem is still present:

Quick settings can't be pulled down and mobile data can't be activated

Developer options are also gone and can't be activated again

F**k
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Is that on stock or custom rom?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
Stock

And also notifications are missing in the status bar
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Then it's likely that your data got corrupted on the restore you did. Personally, I'd backup your important data on your pc, which for me, is just backing up my app data with TiBu, then clean fastboot the factory image leaving the -w intact, so as to wipe your device. Then start all over again. I know it stinks, but sometimes there are no other options. Been there, done that as well my friend :eek:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
Thanks for your help.

I think something is going on with USER MANAGEMENT.

It seems that I'm stuck as GUEST
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Yeah, clean flashing is your only option then, because I'm relatively sure you can't switch it off of guest I bet.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Just a note if anyone has the same issues as I do... For some reason my TiBu folder can't be copied to windows due to directory structure length. I just use root browser to zip it up then copy the single file. It's also easy to keep a backup on the phone like that if you ever need to use adb pull in a pinch for disaster recovery. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
I was able to restore an old backup and apply factory image w/o -w afterwards

Now everything is up again
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] malybru:
Mod Edit

Thread cleaned.

If you have nothing good to share or contribute , it is best if you say nothing at all.

Thank you.

malybru

Senior Moderator
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
GPay working on Android Q DP1 with Magisk Canary build f5f7fd91 - I used the metohd that [MENTION=2177334]mmf01[/MENTION] posted here:

Good idea, thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] provolinoo:
I have a small question:

If I'm on latest stock android with twrp+magisk and I get a notification about ota update, can I go on with automatic update or it will fail because it can't find stock recovery on boot?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Response to the (essentially) identical question in the Magisk forum: https://xdaforums.com/showpost.php?p=79246946&postcount=32451
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] provolinoo:
thanks a lot, I didn't know the best section for it :)

Live long and prosper
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Boskoel03:
One question,i am on DP2 and flashing twrp goes ok,magisk also,but when reboot loose twrp magisk also,new to this device so am i missing something maybe?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
I don't do beta builds, so twrp may/may not be quite ready yet for prime time. However, after you fastbooted into twrp, did you swipe to allow modifications, and did you flash the twrp installer zip? :confused:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Boskoel03:
Did not flashed twrp installer zip ( did not know i should do that? ),and yes allowed modifications.... :confused:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
And that's why twrp is gone after a reboot. Fastboot into twrp again, then flash the twrp installer zip, then magisk again. However, magisk is a little suspect at this time with Q beta. You may have to use one of the canary builds to get it to work :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Boskoel03:
Thank u for all ur help :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] override182:
Anyone achieved root on Beta 2 yet?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Yep!

TJW will probably update beta and Canary builds soon
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Ibramj12:
this post by Xunholyx

This Magisk version works with Q DP2 :

https://www.dropbox.com/s/ffvr43ro5bo1u64/Magisk-v18.2-e476c18c.zip?dl=0

It worked for me with pixel 2 xl
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
The new Magisk canary version that was released last night works as well. You can update now if you want to ;)

EDIT: As does the new Magisk canary build that was just released now. :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Confirmed.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] n@vier:
Hi guys there are any chances to get a TWRP that supports rom's OTA updates ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
It is not TWRP that prevents taking an OTA it is Google ROM signature.

What prevents taking an OTA is the fact that you have altered the pure vanilla stock ROM signature by ANY modifications
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] n@vier:
I meant that if you receive an OTA update on a custom rom it will replace TWRP with the stock recovery so I asked if there's the possibility to have a TWRP that survives to OTA updates... without replacing it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
That won't happen. The OTAs contain the stock recovery.img, and TWRP will get overwritten.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
This looks interesting...

https://www.xda-developers.com/twrp-3-3-0-release/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ReVo_007:
I was just wondering if anyone got the abd backup to work with twrp. I was not able to make it work if someone was able to then let me know, I hate keeping backups on my phone cause in any cause I have to connect it to boot twrp.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
Have you tried it?

https://dl.twrp.me/taimen/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
A bit difficult to try it when it hasn't yet been uploaded. Give it time. :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
That link I posted has the link to the img, here is another. :)

https://dl.twrp.me/taimen/twrp-3.3.0-0-taimen.img.html
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] johnlgalt:
I've DLd it to my computer since I only live boot TWRP and don't actually install it - but I might give it a go this time to see how it works. Just for giggles. And *especially* if it works like Magisk, with a native "restore stock boot image" option.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
I've got night shift the next few days. Lol I'll wait until I'm off to blow up my phone or my wife will kill!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigv5150:
I downloaded it works fine
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
did you use the image or the installer zip?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharkie405:
I use the installer zip. It flashed just fine. I haven't really had occasion to use it yet, so I can't speak to whether or not there's any problems with it other than to say that it installs fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigv5150:
I had ElementalX kernel installed and magisk installed all I did was go in and install the zip file it loaded into TWRP but wouldn't go into the OS. So I flashed the OS again didn't delete user data booted the image then flashed it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Open question to anyone??

I might be wrong but I thought if you flash twrp, you need to flash the kernel and Magisk again after as it is overwriting the boot partition?? . Am I having a brain cloud on that??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
When I looked at the page, prior to making that post, I didn't see the link. I must have missed it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
That's why [MENTION=3462404]bigv5150[/MENTION] had issues and "...wouldn't go into the OS" i imagine...he didn't flash it in the correct order you listed (so, no need to worry about such "brain cloud", you are in the right)...If anything, even though he's gotten back into the OS, he may not have root and/or the kernel or even TWRP(after re-reading, he "booted the image then flashed it" must mean he booted the twrp .img and then installed the twrp .zip...) installed any longer...unless he redid everything in the correct order and just didn't mention it...

in any case, yes, the correct order is TWRP, kernel, then Magisk (always last), even though the installing script in TWRP may mention a modified dtbo (via Magisk) and installing it considering it and that it won't mess with it, it always seems to wreck the booting process when installed after Magisk; so it's just best to install Magisk at the end "overwriting the [TWRP modified] boot partition..." as it (Magisk) seems to be better at preserving the TWRP modified boot than the other way around -- TWRP modifying the Magisk-modified boot...

Sorry for the rather big, over-explained response, but hope it helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigv5150:
You are correct I thought this new version was going to allow us to just update. I guess I misunderstood any way I am back to ElementalX and root this version works the same. I even did a TWRP backup without incident.

---------- Post added at 02:35 AM ---------- Previous post was at 02:34 AM ----------

You are correct I thought this new version was going to allow us to just update. I guess I misunderstood any way I am back to ElementalX and root this version works the same. I even did a TWRP backup without incident.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pkgnex:
So, I'm on the road and can't try myself, but does this basically just mean that we don't have to download (or push via adb) the .zip file to our device anymore?

I'm gathering we now download only the .img to the PC, fastboot boot that image from the bootloader, select the new "self-install recovery" option or whatever it is called from within the fast-booted twrp (instead of flashing the separate.zip from within the fast-booted twrp), and then proceed as before (flash kernel, flash Magisk)?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
You know....I'd like to ask the community about a thought...

Thanks to [MENTION=388504]captaint[/MENTION]hrowback, based off of the line from the release, "Use ANDROID_ROOT variable instead of hard coding to /system", do you guys (@CyberpodS2, [MENTION=3730810]Badger50[/MENTION]) think it will be safe to finally install TWRP unto the phone via the prompt it sometimes asks when first installing TWRP? Specifically, by installing it inside of TWRP via the prompt, do you guys think it will/might cause the same issues and instabilities even though it's now not "hard [coded] to /system" like it has before this point? I'm curious about this "ANDROID_ROOT variable" and its differences from /system (partition); it sounds like (at least) the permissions seems to be higher/elevated from ANDROID_ROOT than working out-of/from the /system -- I mean, why else go through the trouble. I guess it might be akin to the Windows account user "Local System" versus merely being an "Administrator" or being within the "Administrator" usergroup; apologies for the Microsoft OS speak -- and the "capslock" is a good indicator that it is a type of an account or account-group because most of the built-in users in Windows is displayed in all-caps...

If true (that it is superior and it's not needed to worry about installing from the prompt), at the very least it might cause less confusion and issues from novices and might even make things easier and more "streamlined" doing all of it straight from the TWRP recovery environment. I mean, I'm rather excited that it seems we won't have to essentially load TWRP twice to install it (once via fastboot temporarily, and another after it is installed and on to continue whatever you intended to do using TWRP...) and/or manually running the .zip installation file or making sure it's on the phone's memory to make things easier... All in all, it's all a good thing and they (the various developers) should (continue to) be commended for their efforts...

But, I'm curious, what thoughts are there on this?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
From now on you install new versions of TWRP using its image install capability, just as if you didn't have an A/B device. The only difference is a new option, "install to recovery ramdisk".

For 3.3.0-0 itself, you need a copy on the PC as well as the device, because you need to start the new TWRP using fastboot since 3.2.3-1 doesn't have the recovery ramdisk option, and then install the TWRP image to the ramdisk. Then you need to install Magisk to avoid a TWRP bootloop.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
If I'm dirty flashing my rom for an update can I just use the 3.3.0 zip after flashing the rom then reboot to recovery and flash the 3.3.0 img to get both slots updated?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
If there is a 3.3.0-0 zip, but I haven't seen one even though there was supposed to be one. Future updates to TWRP will NOT have a zip file available in any event, so at some point you'll have no choice in the matter.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
See https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.3.0-0.zip.html
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
3.3.0-0 has been on the TWRP website for a couple of days now.

https://dl.twrp.me/taimen/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] g0at1:
Please just help me understand. Based on the parts you mentioned above, should I use magisk 18.1 or 19?

I ask that because I had understood Magisk as it is now should only be used by "A" partition devices.

Thx in advance!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
It wasn't when I last looked. See my comments to [MENTION=4403217]Pkt_Lnt[/MENTION].

I loaded the image using fastboot and updated TWRP with the copy I had on my P2XL. Problem solved.

You should always use the latest (currently 19.0), but who said Magisk should only be used by devices that don't have seamless updates (i.e. "A partition devices")?