Develop Bugs

boot loop after installing twrp 2.8.7.2

so after i unlocked my bootloader, installed twrp 2.8.7.2, rebooted boot loader and went into recovery, i was greeted by twrp but it asked me for a decryption password (which i never set up) and Heisnberg said I wouldn't have worry about here under section 3 of how to decrypt the data partition "This is no longer necessary as long as you use TWRP 2.8.7.1 or newer". So I tried making a nandroid backup as normal, but that failed because twrp couldn't get to the data partition, unlike what Heisnberg said. So i just restarted the phone, and now I'm in a boot loop (about to flash factory image now).
So what I want to know is what twrp ppl use, do you have to do the decrypt data partition step, and the practical differences between systemless and nonsystemless root? why would anyone want to do systemless root if it doesn't work with all root apps?
Thank you so much for anyone who replies :angel:

Flashing TWRP - decryption mandatory?

I come from a Nexus. So I am bit confused regarding the process of flashing TWRP on the Z2 play. On Nexus devices I could flash TWRP but did not have to decrypt anything. However in the TWRP post (dev forum) I could read:
"Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well"
Why does TWRP (have to) decrypt /data on the Z2 play?

TWRP supports encrypted phones. The early versions required you to leave the phone decrypted or you couldn't read anything in recovery. DM verity seems to go both ways too.

Thanks for your response! Yes, TWRP supports encrypted phones (I did that on my Nexus). However in the TWRP topic you can read:
twrp will successfully decrypt /data at first boot if all goes well
Click to expand...
Click to collapse
So I am wondering whether it is possible to disable decryption when you flash twrp on the z2p?
Normally I would have tried it already and re-flashed the stock image if something went wrong (but there is no stock-image yet ...)

Flashing TWRP - Will it clear the data and apps? - Bootloader is already unlocked

I unlocked the bootloader on my device previously. I hadn't rooted it yet, just haven't had the time. I'm ready to do so now, and i've read that you need to boot to this modified version of TWRP and use it to flash the TWRP image to the device, in doing so it flashes it to both the A/B partition of the device. I know you are always supposed to do good backups when you are doing these types of mods, BUT is it by functionality going to clear the device when it writes TWRP to both the A/B partition? When flashing TWRP to any other device that has never been the case. I just wondered if this works differently given the dual partition setup?
Afterwards I plan on using TWRP to flash magisk beta 14.3 to my pixel xl.
Thanks in advance.

Flashing TWRP will not wipe your dsevice.

Using the unofficial modified twrp is no longer necessary. Use twrp 3.1.1.1 img and 3.1.1.1 zip.

Stupid question - twrp and root 5.0.4

Random and stupid Question.
to unlock and root oreo is it the same as normal ie remove screenlock and flash 8.0 twrp, custom rom and no verfy

You can root Oreo even while encrypted. You just need an Oreo compatible version of TWRP that is able to properly decrypt /data like Codeworkx or Blu_Spark TWRP and then flash Magisk. I haven't had the need to decrypt the phone in order to flash and root any version of OOS yet as long as you're using the proper version of TWRP.

With the latest official TWRP you can decrypt Oreo. If it fails, remove the PIN or password but once you're in TWRP you can flash everything like it is unencrypted. No need to worry about that.

TWRP recovery with decrypt ability?

As far as I'm aware we (A3 2017 stock users) cannot use TWRP (3.2.3.0) with an encrypted device while still being able to make full use of the recovery. Does anyone know about a way or a patched version of TWRP that supports decrypting for stock roms?