TWRP 3.2.3-1 for Pixel 2

Search This thread

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,563
KC MO
www.teamw.in
Note: Do not use if you have multiple users (including a guest user)

Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu

I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.

Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.

MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.

Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.

The zip install method installs TWRP to both slots.

Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.

If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:

fastboot boot path/to/twrp.img

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, 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, you will need to reflash root.

If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/

Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/
 
Last edited:

Spire42

New member
Oct 19, 2016
1
0
Thank you! You're a hero.

I'm dying to root my Pixel 2. Does anyone know whether this alpha release of TWRP can be used to install SuperSU (and suhide)? I'm afraid to try.
 

marc.ientilucci

Senior Member
Dec 8, 2007
867
244
Rochester, NY
www.starvingmarc.com
Thank you! You're a hero.

I'm dying to root my Pixel 2. Does anyone know whether this alpha release of TWRP can be used to install SuperSU (and suhide)? I'm afraid to try.

i tried flashing SuperSU v2.82 SR5 and phone would not boot into system. It just kept booting into bootloader.

To get my phone working again, I needed to flash the boot.img from the Pixel 2 Factory image via
Code:
fastboot flsah boot boot.img

i've gathers recovery / kernel logs - however since TWRP boots i will post them in the SuperSU forum.
 
Last edited:
  • Like
Reactions: rshift

deepdvd

Member
Mar 1, 2016
26
7
Code:
fastboot boot twrp-3.1.1-alpha1-walleye.img
I've tried to boot to this alpha on my Pixel 2, and it just sits there and does nothing. I've tried two different cables. If I unplug, it fails, obviously.
Code:
fastboot devices
shows my device and I'm definitely on the bootloader screen.

Any ideas? I re-downloaded the sdk platform tools as well as the latest usb driver to see if that was the problem, but it wasn't the problem.
 
Last edited:

Natakranta

Senior Member
Mar 19, 2013
3,227
6,159
Dublin
Code:
fastboot boot twrp-3.1.1-alpha1-walleye.img
I've tried to boot to this alpha on my Pixel 2, and it just sits there and does nothing. I've tried two different cables. If I unplug, it fails, obviously.
Code:
fastboot devices
shows my device and I'm definitely on the bootloader screen.

Any ideas? I re-downloaded the sdk platform tools as well as the latest usb driver to see if that was the problem, but it wasn't the problem.

Connected to PC vie USB 3 port?
Try with USB 2 if you have it. I've read people having success with it.
 

maxrhys

New member
Oct 26, 2017
3
1
i tried flashing SuperSU v2.82 SR5 and phone would not boot into system. It just kept booting into bootloader.

To get my phone working again, I needed to flash the boot.img from the Pixel 2 Factory image via
Code:
fastboot flsah boot boot.img

i've gathers recovery / kernel logs - however since TWRP boots i will post them in the SuperSU forum.

Same issue here, tried with Snoke kernal and get the same problem
 

bryantjopplin

Senior Member
Sep 15, 2010
1,635
724
Anyone out here that can basically decrypt in twrp? Who can see all the folders and backup like me? I can flash a zip from install? Anyone else?

Sent from my Nexus 6 using Tapatalk

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

Note, this is BROKEN. Decrypt does not work yet and because it does not work, a lot of other things like backup and restore don't work. You can't transfer files with MTP. I have no idea what will happen if you try to factory reset. Basically, a lot of stuff won't work so if you're scared or can't afford to lose data or be unable to use your device, DON'T use this. I strongly recommend that you have the factory images already downloaded and know how to reflash them if needed.

I am not providing a way to permanently flash TWRP at this time. You should use:
fastboot boot /path/to/twrp.img

This will one-time temp boot TWRP so you can do whatever like maybe adb sideload a zip or something.

I am working on decrypt. The Pixel 2 uses a new embedded secure element chip from NXP. Most of the crypto implementation is done in Java and not in native C/C++ so it's going to take a while to convert all of this code and its many layers into something that TWRP can run. Be patient. I'll get it eventually (probably).

Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/

Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/
@despairfactor can see all the files in twrp and flash from install tab as well as me from my 2 XL?

Sent from my Nexus 6 using Tapatalk
 

bryantjopplin

Senior Member
Sep 15, 2010
1,635
724
Anyone out here that can basically decrypt in twrp? Who can see all the folders and backup like me? I can flash a zip from install? Anyone else?

Sent from my Nexus 6 using Tapatalk

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

@despairfactor can see all the files in twrp and flash from install tab as well as me from my 2 XL?

Sent from my Nexus 6 using Tapatalk
FYI screenshot-01.jpegscreenshot(1)-01.jpegscreenshot(2)-01.jpeg

Sent from my Nexus 6 using Tapatalk
 

bryantjopplin

Senior Member
Sep 15, 2010
1,635
724
Anyone willing to reflash magisk via twrp and pull recovery.log immediately after from twrp and upload?????

Sent from my Nexus 6 using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 83
    Note: Do not use if you have multiple users (including a guest user)

    Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu

    I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.

    Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.

    MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.

    Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.

    The zip install method installs TWRP to both slots.

    Installation:
    If you already have TWRP installed: Download the latest zip and install the zip using TWRP.

    If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:

    fastboot boot path/to/twrp.img

    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, 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, you will need to reflash root.

    If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

    3.2.1-1 has working decrypt with the February security patch!
    3.2.1-2 fixes some zip install errors
    3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

    Pixel 2:
    https://twrp.me/google/googlepixel2.html
    https://dl.twrp.me/walleye/

    Pixel 2 XL:
    https://twrp.me/google/googlepixel2xl.html
    https://dl.twrp.me/taimen/
    7
    You sound like you've got some experience so let me ask a dumb question...I have a 64 GB P2. So how does slot a/b work exactly...does each slot take up like 2 GB of the drive like they're partitions? Or are the slots a/b separate from the 64 GB capacity similar to a BIOS? I'm trying to relate to something I can understand :(

    on all Android phones, all partitions are part of the internal storage - so /system is part of the 64GB.

    On walleye (and all other phones that have an a/b partition scheme), the /system - partition is present twice: /system_a and /system_b and yes, that is also "taking" space away from the 64GB.

    How the seamless update basically works is:
    In the beginning partition a and b are in an identical state. The booted slot always is slot a.
    The OTA now installs the update into slot b. When it is done, it displays the message that you should reboot your phone. When you reboot it, the updated slot b becomes slot a and the old slot a becomes slot b, basically switching the partitions. When the boot succeeds, the now labelled slot b partition gets synchronized with the new slot a so that they are identical again.
    When the boot does not succeed after some tries, the slots are switched back and the phone boots the old, not updated system.
    4
    Completely stock Pixel 2 with google accounts already set up and device in use since October 21st.

    I have successfully aquired root with the following steps:
    Code:
    > fastboot boot twrp-3.1.1-alpha1-walleye.img
    downloading 'boot.img'...
    OKAY [  0.700s]
    booting...
    OKAY [  0.068s]
    finished. total time: 0.768s
    
    TWRP > Advanced > ADB Sideload
    
    > adb sideload "Magisk-v14.3(1437).zip"
    opening 'Magisk-v14.3(1437).zip'...
    connecting...
    * daemon not running. starting it now at tcp:5037 *
    * daemon started successfully *
    Total xfer: 1.44x

    Pulled recovery.log immediately after.
    See attached file.