TWRP 3.2.3-1 for Pixel 2 XL

Search This thread
Rally time to update the title of this thread! Lol.

Yes I presume dev @Dees_Troy might be still busy with family and/or in a holiday mood as of now😃
Starting a new thread only for TWRP 3.5 wouldn't make much sense because of the discussion history being in this thread is relatively important for future development.
So, guess we need to wait and watch if he updates the thread topic 👍🏻
Wish you all a prosperous and safe new year!🎉
 
  • Like
Reactions: Alxoom33

Alxoom33

Senior Member
May 18, 2011
5,088
1,815
New York
www.sack-ip.com
Yes I presume dev @Dees_Troy might be still busy with family and/or in a holiday mood as of now😃
Starting a new thread only for TWRP 3.5 wouldn't make much sense because of the discussion history being in this thread is relatively important for future development.
So, guess we need to wait and watch if he updates the thread topic 👍🏻
Wish you all a prosperous and safe new year!🎉
Thank you @Dees_Troy!
 

empathicqubit

New member
Mar 18, 2019
2
0
I'm not sure if this is the right place to post this. I was trying to recover a phone that received too much rain. I've been booting into TWRP with 'fastboot boot' with the latest 3.5 image since I cannot see the screen. I also tried to 'reboot recovery' into the 3.4 installed on the phone and that doesn't seem to work either. It looks like Keymaster won't start. I've tried a few things like reflashing keymaster extracted from a recent Lineage zip, and also replacing build.prop and default.prop with the default versions, since I had experimented with adding props to them to try to get ADB to work in the main OS and I thought I might have broken something. I'm afraid to mess with things too much because I'm worried I'll accidentally lose the encryption keys, if they're even still there. I wish I knew how to prove that I didn't already blow them up.

Trying to 'twrp decrypt' doesn't work because TWRP never starts, and the CLI just keeps waiting for it.

I tried running the keymaster service manually from the command line, but it only said "configuration failed" and quit.

Under /data/media/0 all the files seem to be there, I was able to guess which one was my music folder, but I can't decrypt them obviously. Attempts to access any file gives a message "Required key not available".

I have the dmesg if that helps. I was having some trouble attaching it as a file.

recovery.log:

Code:
Starting TWRP 3.5.0_9-0-8f58a29d on Thu Jan  1 00:02:30 1970
(pid 574)
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_INCLUDE_CRYPTO := true
I:Find_File: Error opening '/sys/class/backlight'
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 80
I:TW_EXCLUDE_MTP := true
I:LANG: en
I:AB_OTA_UPDATER := true
Starting the UI...
setting DRM_FORMAT_RGB565 and GGL_PIXEL_FORMAT_RGB_565
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =   0   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =  16   .length =   8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (1440 x 2880)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 80
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.333333x and height 1.500000x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
I:Setting active slot B
=> Processing /etc/twrp.fstab for SAR-detection
I:Reading /etc/twrp.fstab
I:Done processing fstab files
I:SAR-DETECT: SAR System detected
I:Overriding ro.build.version.security_patch with value: "2021-02-05" from system property ro.build.version.security_patch
I:Overriding ro.build.version.release with value: "10" from system property ro.build.version.release
=> Processing /etc/twrp.fstab
I:Reading /etc/twrp.fstab
I:Processing '/boot'
I:Processing '/system'
I:Processing '/system_image'
I:Processing '/vendor'
I:Processing '/vendor_image'
I:Processing '/data'
I:FBE contents 'ice', filenames 'aes-256-heh'
I:Processing '/misc'
I:Processing '/efs1'
I:Processing '/efs2'
I:Processing 'auto'
I:Created '/auto0' folder.
I:Done processing fstab files
libc: Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb
libc: Unable to set property "ro.crypto.type" to "file": error code: 0xb
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key

default.prop:

Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.actionable_compatible_property.enabled=false
ro.postinstall.fstab.prefix=/system
ro.secure=1
security.perf_harden=1
ro.allow.mock.location=0
ro.debuggable=1
ro.com.google.clientidbase=android-google
ro.adb.secure=1
ro.ota.allow_downgrade=true
ro.control_privapp_permissions=enforce
ro.storage_manager.enabled=true
persist.sys.dun.override=0
media.recorder.show_manufacturer_and_model=true
net.tethering.noprovisioning=true
debug.atrace.tags.enableflags=0
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.usejit=true
dalvik.vm.usejitprofiles=true
dalvik.vm.dexopt.secondary=true
dalvik.vm.appimageformat=lz4
ro.dalvik.vm.native.bridge=0
pm.dexopt.first-boot=quicken
pm.dexopt.boot=verify
pm.dexopt.install=speed-profile
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.ab-ota=speed-profile
pm.dexopt.inactive=verify
pm.dexopt.shared=speed
dalvik.vm.dex2oat-resolve-startup-strings=true
dalvik.vm.dex2oat-max-image-block-size=524288
dalvik.vm.minidebuginfo=true
dalvik.vm.dex2oat-minidebuginfo=true
ro.iorapd.enable=false
tombstoned.max_tombstone_count=50
esim.enable_esim_system_ui_by_default=false
persist.traced.enable=1
persist.sys.usb.config=none

build.prop:

Code:
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Thu Feb 18 05:10:10 UTC 2021
ro.system.build.date.utc=1613625010
ro.system.build.fingerprint=google/taimen/taimen:10/QQ3A.200805.001/6578210:user/release-keys
ro.system.build.id=QQ3A.200805.001
ro.system.build.tags=release-keys
ro.system.build.type=userdebug
ro.system.build.version.incremental=7a6302f0b3
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=google
ro.product.system.device=taimen
ro.product.system.manufacturer=Google
ro.product.system.model=Pixel 2 XL
ro.product.system.name=taimen
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ3A.200805.001
ro.build.display.id=lineage_taimen-userdebug 10 QQ3A.200805.001 7a6302f0b3
ro.build.version.incremental=7a6302f0b3
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2021-02-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Thu Feb 18 05:10:10 UTC 2021
ro.build.date.utc=1613625010
ro.build.type=userdebug
ro.build.user=buildkite-agent
ro.build.host=lineage-buildkite
ro.build.tags=release-keys
ro.build.flavor=lineage_taimen-userdebug
ro.build.system_root_image=true
ro.build.ab_update=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=taimen
# Do not try to parse description or thumbprint
ro.build.description=taimen-user 10 QQ3A.200805.001 6578210 release-keys
ro.lineage.device=taimen
# end build properties

#
# from device/google/wahoo/system.prop
#

persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1

# Set network mode to Global by default and no DSDS/DSDA
ro.telephony.default_network=10

debug.sf.hw=1
debug.gralloc.enable_fb_ubwc=1

# system props for the cne module
persist.cne.feature=1

# system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
mm.enable.smoothstreaming=true
#13631487 is decimal sum of supported codecs in AAL
#codecs:(PARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS FLV 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC AIFF APE DSD
mm.enable.qcom_parser=13631487
persist.mm.enable.prefetch=true

# Additional buffers shared between Camera and Video
vendor.vidc.enc.dcvs.extra-buff-count=2

# system props for time-services
persist.timed.enable=true

# System prop to turn on CdmaLTEPhone always
telephony.lteOnCdmaDevice=1

# Simulate sdcard on /data/media
persist.fuse_sdcard=true

# sensor properties are moved to device.mk
#

#system prop for RmNet Data
persist.rmnet.data.enable=true
persist.data.wda.enable=true
persist.data.df.dl_mode=5
persist.data.df.ul_mode=5
persist.data.df.agg.dl_pkt=10
persist.data.df.agg.dl_size=4096
persist.data.df.mux_count=8
persist.data.df.iwlan_mux=9
persist.data.df.dev_name=rmnet_usb0

#
## system props for the data modules
#
#ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
persist.data.mode=concurrent
# end of device/google/wahoo/system.prop

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
ro.build.fingerprint=google/taimen/taimen:10/QQ3A.200805.001/6578210:user/release-keys
ro.lineage.version=17.1-20210218-NIGHTLY-taimen
ro.lineage.releasetype=NIGHTLY
ro.lineage.build.version=17.1
ro.modversion=17.1-20210218-NIGHTLY-taimen
ro.lineagelegal.url=https://lineageos.org/legal
ro.lineage.display.version=17.1-20210218-NIGHTLY-taimen
ro.lineage.build.version.plat.sdk=9
ro.lineage.build.version.plat.rev=0
 
Last edited:

cognitivedissonance

Senior Member
Jan 11, 2012
651
203
Hi there, I've been having issues with my Pixel 2 XL somehow becoming corrupted while mid-use. I'm still on Android 9.0 where I can still make customary nandroid backups and restore them fully to bring me back exactly to a point in time without any additional setup required.

My phone just corrupted again and is going to require a full wipe, so I'm wondering if I maybe should upgrade to Android 10 or Android 11. Of primary concern is that it's a hardware issue and maybe my device is starting to fail, so I want to make sure I actually am able to do a FULL backup that I can export to an external HD, then push back to my phone if necessary and flash to get me up and running again if it corrupts again.

So here's my question:
What can and cannot be backed up with TWRP after Android 9.0?

My goal is going to be running a daily nandroid backup in the evening and immediately pulling it to my HD so that I'm always only a day off. I can't keep taking a week to get everything back running normally, which is how long it took this past time, and probably will this time.
 

73sydney

Senior Member
Hi there, I've been having issues with my Pixel 2 XL somehow becoming corrupted while mid-use. I'm still on Android 9.0 where I can still make customary nandroid backups and restore them fully to bring me back exactly to a point in time without any additional setup required.

My phone just corrupted again and is going to require a full wipe, so I'm wondering if I maybe should upgrade to Android 10 or Android 11. Of primary concern is that it's a hardware issue and maybe my device is starting to fail, so I want to make sure I actually am able to do a FULL backup that I can export to an external HD, then push back to my phone if necessary and flash to get me up and running again if it corrupts again.

So here's my question:
What can and cannot be backed up with TWRP after Android 9.0?

My goal is going to be running a daily nandroid backup in the evening and immediately pulling it to my HD so that I'm always only a day off. I can't keep taking a week to get everything back running normally, which is how long it took this past time, and probably will this time.

Above where you are there is no full nandroid backup

All i do is backup apps and app data with Migrate

Im swapping and testing ROMs all the time, this is the best way to go above 9.0

As an aside, if you have no confidence in the device to the point where youre contemplating doing a daily backup because its that unstable, then youre better off looking for a replacement

Ill also point out that by doing a full backup and restore cycle with a nandroid backup, you may be restoring the issue as well

Migrate is a better option, youre not also restoring the base system, just the apps and app data. Its not as long a process as you think to do a basic ROM setup, then restore stiff with Migrate, i do it sometimes twice a week....
 

lg_g3_d855

Member
Feb 8, 2021
22
0
what is the most stable version? I had downloaded the 3.5.0 and it didn't start, then I downloaded the 3.3.0 and a strange thing happened to me, I copy and paste: I finally managed to flash lineage os 17.1 directly via twrp recovery and zip file, but during the installation process, the screen went completely off, I had to manually reboot the phone and then it booted, is this normal?
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,939
7,188
what is the most stable version? I had downloaded the 3.5.0 and it didn't start, then I downloaded the 3.3.0 and a strange thing happened to me, I copy and paste: I finally managed to flash lineage os 17.1 directly via twrp recovery and zip file, but during the installation process, the screen went completely off, I had to manually reboot the phone and then it booted, is this normal?
3.5 works well for me on taimen. Maybe you need to update firmware?
 
Jan 13, 2015
12
8
Prior to each test I used flash-all.bat with factory image taimen-rp1a.201005.004.a1-factory-2f5c4987.zip
Thus all firmware is up to date prior to my attempts.

twrp-installer-3.5.0_9-1-taimen.zip fails when booting with the command:
Code:
fastboot boot twrp-3.5.0_9-1-taimen.img
The screen flickers/flashes the twrp logo and fails to boot twrp.

twrp-installer-3.5.0_9-0-taimen.zip succeeds when booting with the command:
Code:
fastboot boot twrp-3.5.0_9-0-taimen.img

Temporarily booting twrp-3.5.0_9-0-taimen.img, I then attempted to install twrp-installer-3.5.0_9-1-taimen.zip.
This successfully installed but resulted in the same flickering/flashing of the twrp logo and a failure to boot into recovery.

Temporarily booting twrp-3.5.0_9-0-taimen.img, I then attempted to install twrp-installer-3.5.0_9-0-taimen.zip.
This successfully installed and allowed me access to twrp recovery.

Unless I am missing something twrp-installer-3.5.0_9-0-taimen.zip is the most stable version and was capable of decrypting the 4 digit pin encryption on my device.

There might be a bug or something that we are missing that is causing a problem for lg_g3_d855 and I as their post was recent enough to have used the very new twrp-3.5.0_9-1 for taimen.

This is the unlocked version of the Pixel 2XL on Verizon.

twrp-3.5.1_9-0-taimen.img no longer has the problems I experienced in twrp-3.5.0_9-1-taimen.zip.
 
Last edited:
  • Like
Reactions: schnuffdroid
Jan 13, 2015
12
8
Prior to each test I used flash-all.bat with factory image taimen-rp1a.201005.004.a1-factory-2f5c4987.zip
Thus all firmware is up to date prior to my attempts.

twrp-installer-3.5.0_9-1-taimen.zip fails when booting with the command:
Code:
fastboot boot twrp-3.5.0_9-1-taimen.img
The screen flickers/flashes the twrp logo and fails to boot twrp.

twrp-installer-3.5.0_9-0-taimen.zip succeeds when booting with the command:
Code:
fastboot boot twrp-3.5.0_9-0-taimen.img

Temporarily booting twrp-3.5.0_9-0-taimen.img, I then attempted to install twrp-installer-3.5.0_9-1-taimen.zip.
This successfully installed but resulted in the same flickering/flashing of the twrp logo and a failure to boot into recovery.

Temporarily booting twrp-3.5.0_9-0-taimen.img, I then attempted to install twrp-installer-3.5.0_9-0-taimen.zip.
This successfully installed and allowed me access to twrp recovery.

Unless I am missing something twrp-installer-3.5.0_9-0-taimen.zip is the most stable version and was capable of decrypting the 4 digit pin encryption on my device.

There might be a bug or something that we are missing that is causing a problem for lg_g3_d855 and I as their post was recent enough to have used the very new twrp-3.5.0_9-1 for taimen.

This is the unlocked version of the Pixel 2XL on Verizon.
Notably, the ProtonAOSP rom I am testing now has firmware build numbers that are greater then stock. I am not certain if it is common place to have a newer then stock firmware, but that might be why some folks are able to use the newest build. Everything is working for me now so I wont change it for a while. Thanks fellows.
 

Alxoom33

Senior Member
May 18, 2011
5,088
1,815
New York
www.sack-ip.com
Prior to each test I used flash-all.bat with factory image taimen-rp1a.201005.004.a1-factory-2f5c4987.zip
Thus all firmware is up to date prior to my attempts.

twrp-installer-3.5.0_9-1-taimen.zip fails when booting with the command:
Code:
fastboot boot twrp-3.5.0_9-1-taimen.img
The screen flickers/flashes the twrp logo and fails to boot twrp.

twrp-installer-3.5.0_9-0-taimen.zip succeeds when booting with the command:
Code:
fastboot boot twrp-3.5.0_9-0-taimen.img

Temporarily booting twrp-3.5.0_9-0-taimen.img, I then attempted to install twrp-installer-3.5.0_9-1-taimen.zip.
This successfully installed but resulted in the same flickering/flashing of the twrp logo and a failure to boot into recovery.

Temporarily booting twrp-3.5.0_9-0-taimen.img, I then attempted to install twrp-installer-3.5.0_9-0-taimen.zip.
This successfully installed and allowed me access to twrp recovery.

Unless I am missing something twrp-installer-3.5.0_9-0-taimen.zip is the most stable version and was capable of decrypting the 4 digit pin encryption on my device.

There might be a bug or something that we are missing that is causing a problem for lg_g3_d855 and I as their post was recent enough to have used the very new twrp-3.5.0_9-1 for taimen.

This is the unlocked version of the Pixel 2XL on Verizon.
I have a Taimen on VZ and have not had any problems booting and installing latest TWRP. You may have a bad dl or other issues with your phone.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 247
    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/
    22
    I don't think this did nothing to fix or improve this device. Touch without kernel still broke. Temp not working and I think the clock is still off. It's kinda sad this device is getting overlooked. I haven't tested anything else.

    Well, at least be thankful you have a recovery from which to flash mods and such. Last time I checked, Team Win isn't on any of our payrolls. Have a blessed day :laugh:
    21
    3.4 Test Image for Taimen

    Hi all. I have been working on getting Taimen re-worked the last few days based on Dees_Troy's original tree. I have a patch on gerrit and once merged I can make a official download image.

    In the meantime please test http://build.twrp.me/test/taimen/twrp-3.4.0-0-test1-taimen.img and let me know if everything is working.

    I have tested backup/restore, decryption under keymaster 3 on stock android-10 for taimen and repacking boot.img works into ramdisk.

    I am hoping someone can test the multi-user patch too. I will test it tomorrow.