yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] thekwijibo:
Hope someone can steer me in the right direction with this.

Recently unlocked my bootloader, flashed TWRP, and got my phone working with Magisk. It was working quite well for a day or so before I decided I wanted to make a backup before I screwed anything up. I booted into TWRP and made a backup. Now here's where I might have messed up.

I considered flashing another ROM in slot B, so I made slot B active. Then I realized, I should probably take baby-steps since I left my USB cable at home and wouldn't be able to dig myself out of any holes if I encountered problems. I then switched back to slot A, and rebooted my phone.

I'm now stuck in a bootloop. I can still access TWRP. I've tried to recover from my recovery, and I encounter the same results. Just for kicks, I tried activating slot B again and flashing LineageOS, but it said "failed to mount /system (permission denied). So I went back to slot A bootloop.

Any suggestions that I can try before I can get to a USB cable?

Thanks.

---------- Post added at 09:57 AM ---------- Previous post was at 09:13 AM ----------

Powered the phone off to conserve battery, and now I can't get into TWRP "Slot unbootable: Load Error".

Lesson learned not to futz with the phone w/o a USB cable handy.

I'm new to this whole slot A slot B thing and did a bit of reading up, but apparently I don't quite understand it yet.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] rekids:
Sounds almost like you were trying to flash to different slots like back in the old "Safestrap" Days when unlocked bootloader wasn't available.

I highly recommend once getting the phone to a state of being seen by the PC and able to boot into bootloader(if you can't get to the bootloader don't know what options are left).

I would download the full factory image of the phone and use something like Duce's recovery script to flash the phone back to 100% stock.

once back on pure stock firmware leave it alone until you got a clearer picture as to what you need to do and want to do.

But as far as how you got into this spot in the first place, like I said sounds ALMOST like you were trying to boot the phone like it was using safestrap. The slots are used for OTA updates and its own self recovery not for different booting options. I always leave slot A active and any time something weird happens(unplanned) or updates not by me and Slot B goes active I reflash the current stock, set A active, boot, flash magisk, then kernel and reboot. Its fun to play but not so fun when we make a mistake and can't undo it right then. I personally never flash anything unless in front of the PC and have lots of time to fix.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] thekwijibo:
Thanks for the input. Yeah, I recently got my Pixel2 and was admittedly playing around with it and got a little careless. I had been under the impression that the 2 slots allowed one to "dual-boot" if desired. I've been using my HTC M8 for the last several years, and I've grown careless with being able to monkey around and if I screwed up I could always just restore my last backup from TWRP.

As for the Pixel2, I ended up getting my USB cable, flashing the current stock, then TWRP, then Magisk. I tried messing around with substatum and somehow ended up soft-bricking again where even the touch-screen didn't respond. Did the re-flash process again, and things are working fine. It'll get some getting used to, and I definitely have some more reading up to do about how to utilize this little machine to its full potential.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
If anyone is still reading this thread, the 2 slots are so that you can keep using the phone on the currently active slot while the update is being flashed to the non-active slot. If that works, the update switches you to that slot, and flashes to the "what used to be active" slot.

No my question - if anyone is still reading this, and I hope that Dees_Troy is, I can't find any changelog on 3.3.0.0 - can we find out what the changes were? 3.2.3.1 is working fine (aside from MTP, but what's an "oops, I forgot to copy the file to the phone" even if you reboot, MTP it, then reboot to TWRP? (I've done that many times, and never bothered to use adb push for some reason. Then, again, if I told you how many times I';ve hard-bricked this P2 ... but it's still my daily driver, you.just.can.not.kill.this.thing.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] KittenSauce:
The changelog for TWRP 3.3.0-0 can be found here. Note that this doesn't include device-specific changes, of which can probably be found at the TWRP repo on Github for walleye/wahoo.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] b3nman:
can't boot into twrp

i'm on the april security update on 9.0 and i just get a blank screen after running the fastboot command with 3.3.0. i did get a twrp flash screen the first time but now nothing. any ideas?

edit**oops downloaded taimen by accident
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] joetheshmo:
Latest platform-tools?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] BS86:
Seems like decryption is broken again, at least on a clean flash.

TWRP 3.3 as well as 3.2.3-1 worked with the May security patch as well as the Q Beta 3 on my walleye. Yesterday I switched back to Pie and did a clean install (with wipe-flashing the factory image) and now neither 3.3 nor 3.2.3-1 will decrypt data, always says wrong password although I enter the exact lockscreen code like I did before.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] mikebeatrice:
For what it's worth, 3.3 works fine for me with the May image. Have not tried June yet
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] BS86:
Did you try on a fresh install with wipe everything?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] D3RP_:
Works great on June update! I'm on a Pixel 2, updated last week. No issues as of yet!

Edit: Decryption is broken.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] rekids:
3.3.0-0 Working for me on June including decryption

However I didn't do a wipe before hand.

May be off, but perhaps it only works cause of no wipe, meaning the data is not encrypted with a new a logarithm.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] thekwijibo:
I had 3.3.0-0 encryption working with June's update. However, I just recently did a full wipe, and now encryption is broken.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] hunfatal:
Same here, decryption is broken, TWRP says wrong password.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] NafNuf:
Same for me - after flashing June images password doesn't work for /Data volume decryption in TWRP 3.3.0.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] blastagator:
Seems they changed encryption at some point and if you were already encrypted you kept the legacy encryption scheme. I was on May update with working decryption, wiped and still on May and now it doesn't decrypt in TWRP. However, as a workaround, if you set your screen lock to none (temporarily, of course!) you can boot TWRP and decrypt. Just set your screen lock back after you're done playing in TWRP.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] hunfatal:
I know and it's working, but then it wipes every fingerprint which takes some time to set. But I can live with that. :) At least I hope, this will be fixed some day. :)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Erkki123:
Worked nice, i I appreciate you.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] blastagator:
Looks like they merged the fix, hopefully someone rebuilds soon:

https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34092/

Maybe I will but I'm not feeling super motivated at the moment, since I haven't built TWRP for the Pixel 2 before.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] hunfatal:
Thanks for the info, waiting for the update. :)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] jaggillararla:
Man they've had so much time. And they're releasing several twrps for other devices. Idk how to build a recovery but I bet it's not that hard. These days I'm too afraid to download a magisk module or a new kernel just cuz I have to boot into twrp if something messes up. Feels like I'm on stock without root.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Meowdib:
If it's not too hard for you, please build
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] jaggillararla:
Man I don't even know how to ?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] hunfatal:
Maybe I will try that if i will have some time.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] jaggillararla:
How'd it go ?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bluh5d:
Your welcome

(Hunter)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] gururoop:
It did work! I tried on 8.1 DP with stock boot.img, TWRP and Magisk 14.4 and now I have root!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] nuumuun:
SafetyNet still works with stock boot image.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bryantjopplin:
Weekend with r9se. That I've selinux enforcing. Just r9 is selinux permissive. Also r9 has some new eas changes from aosp.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] gururoop:
I'm using Pixel 2, but I wasn't able to grab factory image for 8.1 till it was online. You have to enroll yourself for getting 8.1 DP via OTA at https://g.co/androidbeta

You will get update notification within few hours of enrolling.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bennyasf:
Can anyone confirm if twrp boots for them on Nov update??
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] gururoop:
Even I was rooted prior to updating from 8.0 to 8. 1. I simply booted the alpha TWRP and flashed the official uninstaller zip from Magisk thread and then successfully updated to 8.1. However, a kind user has posted a mirror of 8.1 in the 8.1 announcement thread and you can try updating using that. Just be sure you have the latest version of platform tools and remove the -w option from flash-based.bat to prevent loss of user data.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ajrty33:
Boots fine for me.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bryantjopplin:
OTAs usually only fail when it detects /system changes. OTA sideload worked for me
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] GohanBurner:
I got this to work and got root to stick but I can't get Viper4Android to work. Any ideas on how to get it working?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] giant22000:
It boots on November update for me.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bryantjopplin:
I sideloaded, unlocked and rooted, and successfully updated. IDK.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] multi_rom_user:
Yeah good luck getting any magisk modules to flash right now.. TWRP is unable to read data on our system due to its alpha state.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kinfam:
You need to use Selinux Switcher
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] dethknite:
You can install the Snoke kernel (permissive one that doesn't end in "se" for selinux enforcing). Then just install the Viper4Android from the magisk modules downloads... if you encounter issues with playback via bluetooth or in other apps, also flash the deep buffer remover from the module downloads.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kinfam:
Flashed Snoke-R11-P2 IMG, booted new Beta TWRP, flashed TWRP ZIP, Flashed Magisk 14.4 ZIP, and flashed Framework V4A (In that order!).

All working fine :)

Thanks!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] DJarkIV:
So we can use Magisk as an alternative to SuperSU if I decide to actually install TWRP Beta? Has that been confirmed working for sure?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Chronzy:
Thank you [MENTION=912474]Dees_Troy[/MENTION]

Transaction ID

38D67283BY098445Y
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] SuperSmashedBro:
look one post before you lol
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] DJarkIV:
I sure did, that's what got me asking ? Just wanted to make sure others have the same results and that's it's not dependant on the kernel you're using.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] hunfatal:
Sorry, didn't have time. Maybe I will give it a shot on next week, but that's a huge maybe.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Diaz1999:
aw man, huge thanks! :svetius:

just bought this walleye this afternoon, bl was locked in latest August 2019 Pie.

did an ubl, set a PIN lockscreen, stuck in temporary twrp without successful decryption.

did what u said there and now it's installed! :o
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] NFSP G35:
Can someone please rebuild this? I would really like to have TWRP decryption working
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Hadookie:
Anyone? ?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] UncertainSpin:
Please help us [MENTION=912474]Dees_Troy[/MENTION], you're our only hope.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Hadookie:
Pretty please, anyone.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] buffal0b1ll:
You do know that you can have working data encryption on current walleye (Android Q/10 included) in TWRP 3.3.0-0 by following these steps?

Flash an April pie factory image clean (let it wipe data)

Boot once and set your PIN/PATTERN/PW

Update to current factory image (don't wipe data)

Never remove or reset you PIN/PATTERN/PW
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] NFSP G35:
Yes, very much aware.

I have the latest version (Q) and am currently in the state where I can still decrypt with twrp because I already did the exact steps you mentioned.

The real problem is the that last caveat: "Never remove or reset you PIN/PATTERN/PW"

That's pretty untenable from several standpoints, not the least of which is the need to change a compromised (or 'loaned') PIN/Pattern/Password
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] _U03C6_:
hi, when i try to install some stuff (rom or twrp itself) i get this error:

impossible mount '/system' (invalid arguments)
impossible mount '/vendor' (invalid arguments)

how can i fix this? may affect the installation of lineageos?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] RedNXL:
I have same issue. Latest stock, magisk, TWRP. Anyone?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Diaz1999:
same story here, i was on the latest 10.0.0 (QP1A.191005.007.A1, Oct 2019) with magisk

when suddenly it went bootlooping after restarting

since i had no backup whatsoever i decided to retain the data in internal storage

by flashing the entire factory image without wiping userdata

then it went bootlooping once again, so i decided to wipe data but excluding internal storage

by booting to and wiping data through twrp

but that error message appeared and i could do nothing about it

other than reluctantly wiping userdata through fastboot and starting it all over again

:crying:

EDIT

in other words, we are desperately in need for an update in TWRP

specifically to address that decryption issue and, the recent one too

should they have worked around the issue that seems to be about compatibility with Android 10.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] RedNXL:
Indeed. Later I found this thread: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1473#issuecomment-532810787

All that remains is to hope and wait...
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] shaqthegr8:
I think you can flash 9.0 or 8.1 factory images and use TWRP after that
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] thekwijibo:
Went to flash the November image, and started with a TWRP backup and I got:

impossible mount '/system' (invalid arguments)
impossible mount '/vendor' (invalid arguments)

Now I'm worried that with TWRP not functioning properly, if I attempt to flash the November factory image, I won't be able to install Magisk or suffer bootloops like some other users on this thread. Has anyone figured out a stable workaround with TWRP other than going back to Android9?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] rekids:
If you can't read user data with TWRP after updating to 10, then youust wait for a new TWRP that does work OR start over with full wipe (user data, sys, ect.) back to April 9.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] BS86:
or you can simply use an USB stick on the USB port (connector is included in the delivery package of the Pixel 2's)

@thekwijibo the message also appears on my phone, but flashing magisk from USB stick succeeds anyway. (TWRP is temporarily booted via fastboot boot, you can disconnect the phone after TWRP is fully loaded and connect the USB stick)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] tkacer:
patience.......

least we forget...…..from the man himself

https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] thekwijibo:
Possibly a silly question, but why do you suggest the April 9 image? May - Aug are also 9.0
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] pa.pn2:
Because with April build decryption work's.

Flash april image.twrp.setup your phone and flash 10 or latest pie on top
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] N5X_ita:
I hope we get a full support of Android10 by TWRP soon
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Second that hope. I hate updating without backing up first. (December worked. The January update causes TWRP to fail.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] mikebeatrice:
Fails in what way? I'm on January and twrp decrypts my partition just fine.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Backup fails partway through. (Now I'm forced to use Titanium Backup until Dees Troy gets a new version of TWRP up. (I just wish I could help, but I've been out of the game far too long to be of much use.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Murmel2k:
Also suffering from the decrypting issue. Looks like in terms of recovery basically Google supported the pixel 2 longer than the community :(
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Google doesn't have to help its wife take care of 4 children. (And I don't think we'll see any further TWRP updates for the 2.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Severus_:
I built twrp 3.5 successfully, but it only successes at first time then stucks at twrp logo.

The build's here
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Pixel 2, Android 11. It boots the first time (not installed, just booted in fastboot), but fails the second time it's booted. (And the first boot failed to mount a few things, it just looped around the same errors.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Severus_:
Any deal for debugging, I didnot see twrp.log anywhere
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kurokuroninja:
deleted
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kurokuroninja:
hello, i'm using walleye and i can give test for you.

What log do you need and how to get it?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] crazykas:
Hello! I have been out of the game few years so forgive me I do not know up to date TWRP Info about the device. So my question is which version of TWRP is compatible with android 11? I want to flash android 11 ROM in order to do that I need to boot up TWRP no. So the latest version given in the official TWRP site is twrp-pixel2-installer-walleye-3.3.0-0. Is that compatible with android 11?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kurokuroninja:
it's partially compatible..

you can't install this twrp on android 11. Just boot the image in fastboot mode using "fastboot boot (yourboot.img)"
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] crazykas:
Thank you very much sir! Only issue is when I tried to do a factory reset via TWRP before installing a new ROM, I populate following error

Failed to mount /system

Failed to mount /vendor

However Ignored that and flash the ROM anyway, just don't whether whether it could mess up my new ROM
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] luis saucedo:
Does version 3.3.0.0 work on android 11?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Wheemer:
Yes
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] V0latyle:
Just to confirm, we are still unable to patch the boot image with TWRP on Android 11?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Severus_:
I built 3.6.0 successfully, but the decryption is broken. Here is my build
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] :
Thank you for this. Everything works well as the latest official build?

(Only decryption is the problem?)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Severus_:
yes, and if you format data partition with twrp, it can decrypt on next boot twrp.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Severus_:
I updated to new build (change from userdebug to -eng variant)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] :
This doesn't boot for me. I tried the first build and it boot fine!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Severus_:
sorry, I post wrong file,
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] g000n:
New TWRP version available for pixel 2 xl?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] SGH-i200:
"I built 3.6.0 successfully, but the decryption is broken: if you format data partition with twrp, it can decrypt on next boot twrp." - Thanks for building and upload this TRWP version! Can you build a newer one? I will donate to the person, who does! :-)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kinfam:
TWRP Beta + Magisk works fine using stock kernel, however, if you plan on using modules like Viper4Android you need to flash a SElinux permissive kernel, or use a Kernel Switcher Apk.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] DJarkIV:
Really, is that limited to certain modules? b/c I could have sworn I had a working busybox and adblock module using stock kernel although I didn't try V4A. Oandbackup worked for me so that's why I'm assuming the busybox module worked. But these were installed through Magisk download tab. I am currently running Flash Kernel as of recent and all seems working as well.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] kinfam:
Not all modules have this issue, correct.

In regards to V4A, I tried the framework Magisk variant and the 14+ Magisk variant, using both Alpha and Beta TWRP, flashed via Magisk and via TWRP direct on patched 14.4 stock kernel. Driver reports abnormal until SELinux is set to Permissive.

Sorry for OT!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bryantjopplin:
Try my newest magisk. It fixes avb-verity
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bryantjopplin:
Use this magisk for working viper with se kernel. It fixes avb-verity. https://www.mediafire.com/download/5poo50s3zt89995
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Archangel:
I guess now is the time to ask again what is the best selection for backups? I remember it was suggested on Pixel 1 devices,,for a good bit-for-bit back up, to select boot, system_image, vendor_image, and data? Is this still the same for Pixel 2 devices? Just did one using these sections and it went great!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] DJarkIV:
Where did this version come from? I can't find an official thread for it.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] bryantjopplin:
I compiled it from source last night. Newest changes that he had pushed 3 hrs before.

---------- Post added at 07:34 AM ---------- Previous post was at 07:32 AM ----------

Btw I did have to go to terminal emulator in Android and do setenforce 0 to changes to permissive to get viper working correctly. There is still a bug that isn't allowing it to work with enforcing. But to change back to enforcing just do setenforce 1