yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jasonstackhouse:
So my last reply to you would have been helpful had you actually had any of the issues I was responding on. I just now figured out that you are ahead of the curve so to speak on discovering compatibility issues with TWRP and the April image file. I started messing around in TWRP and replicated all the problems you were having.

From a fresh install of the April factory image via fastboot all appears to work fine, the problems with the 255 error will start to happen once you add any kind of pin/finger print protection. before, I think this was like 2 releases back on TWRP, if you had this issue you could just delete your finger prints/pin than boot into TWRP without issue. If you were to remove your finger prints/pin now than boot into TWRP, you will run into 1 of 2 scenarios.

Scenario 1, you are not required to enter a password or pin to use TWRP, however Twrp will still display all the files on the device as encrypted, just like if you were to skip entering your pin and enter TWRP. Scenario 2, is that all your file will look normal, however back ups fail once data is attempted to be backed up, the same will happen for most anything you attempt to flash, you will receive a 255 error code. Where this situations gets bad is when you decide too much has gone wrong, your device wont boot, it just loops you back into TWRP and you decide to do what you always do in these types of situations and restore your last back up.

Upon attempting to restore your last back up, TWRP will delete your entire device, system and all data. When TWRP does a restore it deletes every item on the device that it is restoring, so when you go to restore your previous backup, it will delete boot, system, vendor, data, than instantly fail the restore process with a 255 error, leaving your device a blank slate.

I decided to bump back down to the March security patch, If you are on the April security patch be warned you will most likely run into issues and lose all your data. Hopefully this issue can get some attention. Thank you for your post and again i apologize for my first reply, I had not yet needed to use TWRP for a restore or new rom with the new April security patch, once I did, I found out exactly what you were talking about.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CrashTestDroid:
Thanks for using the time to replicate my findings. When I couldnt get the most basic restore working of a fresh install I felt the need to warn people of potential problems, that's all. I hope I have helped others with my canary in the coal mine experience.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jasonstackhouse:
Good find man, I keep seeing posts pop up now with people thinking its rom related. It's for sure a compatibility issue with the April security patch, hopefully the issue is something small and the guys working on TWRP can figure out a new patch/update.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Hello guys and gals!

I have quite the issue. It seems that I cannot get into Slot B at all. I have flashed the latest FW package, on both slots, and let the system warm up. I went back into recovery (fastboot boot twrp) and then installed the zip. I wanted to see if both slots were working and no dice! Slot A is perfectly fine, and I can flash a ROM and such. But when I try switching to Slot B, it will hang on the TWRP splash screen. It also does this when I flashed Android P.

This HAS happened to me before, but I cannot get both slots to work. Am I not supposed to flash TWRP and then return back into the system?

I think I read something about needing to flash a kernel too?

I am an absolute noob with this A/B thing. Pixel 2 XL unlocked, by the way.

Thank you for helping!! I honestly appreciate it so much. I try reading a lot before I throw in the towel, to ask for help.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] rickysidhu_:
Why are you manually trying to switch to slot B anyway? Unless you have a very specific reason to do so, you don't need to.

If you want to flash a custom ROM,

Flash the rom zip

Flash twrp

Reboot to recovery and the slot should switch automatically

Flash gapps if the rom didn't include them

You should be good to go

I've never switched slots in TWRP so I can't be much help there. I do switch slots manually in fastboot mode though, and that's just to get the new factory images installed on both slots of the system.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
I guess that was my theory to switch slots, in order to flash gapps and kernel. I was just under the assumption that, since I couldn't manually switch, then TWRP would not automatically switch either.

I'll have to test this theory out. Hell, if I don't need to switch slots for anything, that'll make my life easier!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ZeroSkylineX:
Flashed the most recent 3.2.1-2 but the recovery is frozen upon entering. Can't swipe or tap any of the functions. I don't have a lock screen security or anything. Anyone know what seems to be the problem?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Try entering twrp again. If that fails, fastboot twrp again, then do whatever, and flash magisk again when you leave.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ZeroSkylineX:
Thank you badger, I was actually going to do this as my last resort until I read another post from December that someone else had the same issue. But as you mentioned earlier, TWRP works momentarily when I flash the img and that gives you a small window to do whatever.

I just double checked my lockscreen settings it was "swipe" to unlock. It didn't require a pattern or anything, just a simple swipe up to unlock. I unchecked that to ensure I didn't have any kind of unlocking methods and then bam, TWRP was unfrozen. What a strange glitch huh?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Yes indeed. I usually set mine to swipe and haven't had any issues with it. Just another story for the twrp record book ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] semakawa:
'

If you are on stock rom with TWRP allready installed and you rebbot the phone on TWRP and touch is not working ,is because of stock kernel. From fastboot flash a custom kernel (Flash kernel, or other) and problems are gone.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
this is true and a well known issue, and might've been true for ZeroSkylineX, but what made his issue most peculiar is that he didn't have a security code set and it seemed to be frozen at the TWRP load screen, not simply tapping the selections and it not registering.

But, for the record, I have the same experience as Badger50 where, when I was on 8.1 Feb patch and on TWRP 3.1 beta (lockscreen issue version), mine being on plain 'ol swipe seemed to be enough to allow TWRP to run "bugless", so I would have imagined it working for you ZeroSkylineX. TWRP has sure been running peculiar so far in '18...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ZeroSkylineX:
I will keep this option open in the future if this happens again. Thank you. Luckily for my situation, I didn't have to do that as it was a lock screen issue. I didn't think the "swipe" to unlock would cause TWRP to freeze. I did know that any other kind of passwords would encrypt TWRP though.

Thank for all the support, you guys are great. It's difficult for me to catch up on all the latest bugs since I really only flash once or twice a year. Once I find something stable and free of bugs, I stick with it for a while. I know there's some hardcore people here that flash the latest vendors and ROMS every month lol. But yeah, there's always something new...I'm also aware that TWRP doesn't have MTP functionality yet either for the 2 XL :eek:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mackentosh:
For some reason, when I try restore my phone goes in to bootloop. Am I missing a step?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
What partitions are you trying to restore? Boot, system, and data are usually all you need to restore.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mackentosh:
Ok I'll try that and report back, thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
And do a twrp wipe with the swipe bar before you restore.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mackentosh:
Thanks guys it worked
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sjpritch25:
Okay, I'm a little confused on what backup I should perform. Do I backup everything but boot? Or what are some suggestions
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Boot, system, and data is all you need :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sirxdroid:
What about just data? boot and system you can easily restore by flashing ROM + kernel.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Do it the way you like my friend. That's just what I do. Works for me :cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
....also keep in mind that (with at least TWRP Backups), "internal sd data" does

NOT

backup technically*. But that's probably the only data that doesn't necessitate root in copying/backing up...

*although technically, I employ a method to include even that data with the other data; i.e. both /data and /sdcard data. I found it easily enough (Google, on XDA), but hit me up pm if you would like more direct info on the matter...

good luck!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cognitivedissonance:
So, I'm sure lots of you have experienced this, but when I run a backup, the folder auto-generates a name based on the current time and date. For some reason, TWRP thinks I'm living in 1970, and the time is super off as well. Anyone know how to fix the TWRP date and time?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pkgnex:
Why are you hating on the '70's, man?

It was a great decade... or at least so I'm told ;)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Google search: Unix Epoch
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
You can choose not to Auto generate the date and time. When your in the backup mode, just tap the top line, then make up whatever you want. Ie..."Stock 8.1 FlashK 5-3-18" This is how I do mine :good:

Damn right it was! I'm living proof.....I think ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dadenet:
Dear Frieds ,

I have installed the last twrp twrp-3.2.1-2-taimen.img ,

When I go to recovery mode , the screen is not able to reconize my finger , If I push my finger , nothing happend on the screen , and I 'm not able to access to the recovery twrp , why ?

The display stay freeze ,:mad:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Either fastboot into twrp, or disable screen lock security. Either way, flashing a custom kernel should rectify the problem :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dadenet:
Yes , tried ................now It works .........perfect ! Great work !
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Ariac Konrel:
I just tested TWRP on the May update and it can decrypt it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Were you able to decrypt on the April patch, or is this new?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Ariac Konrel:
I was, but the May patch just dropped today.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
I just tried. 3.2.1-2 is NOT able to decrypt if you have security enabled.

Reflashed TWRP and now it's working. Not really clear why is wasn't working before though.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
I updated to May google image; I flashed twrp image from fastboot; then zip from twrp and rebooted system. When I came back to twrp to flash kernel and magisk, twrp had no touch responsiveness. I had to fastboot twrp image again, flash twrp zip from twrp, then kernel and magisk and all is well again.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bd177:
After sideloading the may update ota, I went directly to fastboot. Then fastboot boot twrp-3.2.1-2-taimen.img. When twrp booted up I was able to put in my pattern. It then decrypted and I was able to flash magisk. Rebooted to system and all seems fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
Well that sucks. Mine keeps saying wrong password :(
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Just remove code before booting into twrp until it gets updated.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
Does back up work yet? Last month when I got this device I tried to do a simple back up, wipe and flash a ROM. Didn't like it so I tried to do a restore and errored out. Is there a fix or certain procedure I need to follow to sucessfully do a back up and restore?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Personally, I've never had a backup/restore problem. I always remove screen lock security, and substratum themes, then just backup boot, system, and data and call it good. When I restore, I twrp factory reset, then restore those 3 partitions and I'm back in bidness :good::cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] :
I've run into a similar problem before and I think it has to do with multiple users. I took two backups, one before rooting and one after rooting and installing a single user mod. The one from before errored out when I restored resulting in a "your device is corrupted" screen. I had to reflash the boot image from the factory image zip and then flash twrp and magisk again but once I did the data and settings were exactly how I left them at the time of the backup. The other backup had no problems being restored.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
chopt51 & darkfire404, I remember a 'lil while back when jasonstackhouse and CrashTestDroid were having issues restoring from TWRP, especially when involving different ROMs and such...

I'm not sure if it precisely is the same as your issues (as actual error codes were not divulged), but it seems that there are some similarities (consequent restores from different backups at different stages result in different/varying outcomes) it may show some insight and/or some sort of explanation towards the issue...

if you are interested, please check out THIS and THIS with ending conclusions HERE & HERE. They seem to have come up with some interesting conclusions....

Again, I can't tell exactly if their issue compares with yours, but I hope it maybe helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CrashTestDroid:
My error was 255. The workaround was to remove security before backing up.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
So I have an interesting issue, and maybe you guys and gals can explain.

I am on the Android P beta. I was about to boot into TWRP but it seems one slot is encrypted for me (Slot A).

I'm about to do things on Slot B, like backing up and restoring. Probably a known issue, based on the new firmware?

Thanks!! :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CrashTestDroid:
User data and system slots are separate. Only user data is encrypted, the slots aren't. What do you mean by that?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Do forgive me, as I STILL don't understand the slots. I don't know what Slot A is or what Slot B is. All I know is, Slot A was encrypted on the beta. BUT when I'm on Oreo, I can see everything on both slots.

Mind you, I do not have any passcode or anything. My apologies if I sound, well, like a noob. I was about to flash Magisk and Flash Kernel though :)

I'll have to read more about these slots LOL.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
...Just to confirm, you are using the latest TWRP beta...? Because, if you don't know, TWRP was having a whole issue with decryption after Feb update (8.1) on v3.2.1 -- hence the "-2" at the end of the current beta version number. If anything, it may be related to that (in terms of using TWRP on P; I wouldn't know, I'm on 8.1). Maybe, I'm guessing, on P beta, you have security set to Swipe or something (which isn't really a lock, but technically calls for a lockscreen) and as such is calling for decryption...? (*though I admit this doesn't make much sense as decryption protocols are only triggered by pattern or pin...) Or P beta straight up just encrypts everything regardless....

cling clang

the rattling of my 2 cents...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
It seems that I hit one of those fluke incidents! I just fastboot booted twrp to both slots (not installed), and everything was fine. I honestly do not know what happened the first time, and I REALLY apologize for my slip up. I assumed, and we all know what happens when you assume things......

*bows head in shame*

Disregard MY mistake! Thank you for your help, however!!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Wr3ckd90:
is there anywhere else i can download the correct files for twrp... it looks like there server is down right now and i could use twrp image and zip file to fix a mess up....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
It's up for me...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Wr3ckd90:
I've been trying for 3 hours I've tried 3 different computers and 3 different connecting my wifi my hotspot for 2 different phone nothing loads the page to the downloads.... I guess I'll keep looking for something posted elsewhere
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dmarden:
It's just the Americas location that is down, use Europe: https://twrp.me/google/googlepixel2xl.html
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hanschke:
I have got a problem now. Slot B was flashed and android boot fine. I have done the mistake and change the slot a inside the twrp and now the phone dont boot. Fastboot work fine but recovery stuck and I cannot flash. How to change the slot now?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
fastboot --set-active=a OR fastboot --set-active=b
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hanschke:
thank you but I got following message if I try to set b:

error: Device does not support slots

and if I want slot a

Setting current slot to 'a'...

FAILED (remote: unknown command)

finished. total time: 0.003s
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] qwer777:
Could you please share a link to the single user mod you used?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
It's in the list of modules inside Magisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheUndertaker21:
Not working on P beta.

Just rebooted to twrp after flashing.

Good thing I had a back up lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
I'm just wondering, what route are you using for backups?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheUndertaker21:
Lol should have said that it's not gonna stick.

If you flash twrp zip, it will reboot right back to twrp.

You can use it if you fastboot then flash whatever you need

You'd have to do that Everytime you need recovery
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Why are you "flash[ing] twrp .zip"??? It's supposed to go you fastboot(ing) boot twrp.img and inside TWRP you install using that twrp.zip....

...if this is what's happening, it's probably why & where things are going wrong...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheUndertaker21:
Lol

You don't think that's what I did.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Try flashing twrp.zip and then magisk 16.4.zip sequentially, both in twrp, then reboot to system.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Before reading my post/reply, I realize (looking back through your posts) that I might be misunderstanding things...

From your post #2045, because it's not precisely and fully written out, I had assumed (maybe incorrectly) that you were having a problem with TWRP and in your subsequent posts (#2046 & 2047), you speak more about issues but it may or may not be directed towards #2046's inquiries; which in no direct and obvious way do you answer his/her inquiries and just spiel your (or a hypothetical person's) issues with TWRP...

If this isn't the case, and I assumed and understood things correctly, my reply below stands. If I'm misunderstanding the situation, then you can please disregard my reply below -- After reading back and looking at your experience, I figure I am misunderstanding and you are/were talking hypothetically and I am just re-iterating things you are aware of...

mmmm...I'm not sure... That's why I quoted you...

"If you flash

twrp zip

, it will reboot right back to twrp."

This is exactly what you said. That is the only reason why I have to believe "...that's what [you] did".

And going off of this, this would be the incorrect way about going at things and could be the root of the issue -- you

don't

flash twrp.zip.

If you made a typo or something, I can understand. But until specified otherwise, I can only assume that you

did

attempt flashing an installation file (.zip) incorrectly and not the correct image file (.img).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hanschke:
I need the solution that the twrp stuck on twrp logo.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Well, I imagine, that if you try to set it to slot B and it couldn't, then trying to set it to slot A would return a "FAILED" because you are already on that slot...maybe....

In any case, since you said in a previous post that you have the ability to fastboot, try to boot into TWRP using the twrp image file (.img) and using the fastboot command to boot into TWRP that way; i.e. fastboot boot twrp-image-file.img . At the very least this should get you to a stable TWRP recovery environment so you can try selecting slots back to the one originally (

I would not recommend this as this action was exactly what triggered all your issues

) or to re-install TWRP (from .zip installation file) to try and correct things (boot partition and slot selection) that way.

Worse comes to worse, you're going to have to obtain the unaltered stock boot.img for your version of Oreo (or P if you are on that; and version of Oreo meaning a month's patch; i.e. April patch, May patch, etc.) and flash it over your corrupted boot partition to set things right and back to stock. After, you'd have to temp boot into TWRP and install TWRP again and

NEVER

touch selecting/switching slots

ever again

! /s :p
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
ok so, need help. I booted into twrp and the screen wont respond to touch. I cant get it to do anything. Its stuck on the first twrp screen and now says swipe to unlock, but nothing is working. Am I screwed?? Ive looked it up, but found nothing that is working.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
You need a custom kernel.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
or you fastboot the twrp image...

those are really the only 2 options you have if you have unresponsive touch...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
so Ive lost everything. It somehow wiped my system. Notihng in the folders, nothing to flash. Just keeps booting into twrp. Any ideas??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I remember helping you a couple days ago....

So, it depends...It might/could be that TWRP isn't decrypting properly and that's why it's not seeing folders or you are directed/active in the wrong slot... as I said, it depends; what were you doing before all this?