twrp-3.3.0-1 unable to decrypt if Android 9.0 May update was factory flashed from image creating new userdata

TeamWin / Team-Win-Recovery-Project

Core recovery files for the Team Win Recovery Project (T.W.R.P) - this is not up to date, please see https://github.com/TeamWin/android_bootable_recovery/

http://twrp.me

1.96k stars 741 forks source link

twrp-3.3.0-1 unable to decrypt if Android 9.0 May update was factory flashed from image creating new userdata #1454

Open Sada-Mio opened 5 years ago

Sada-Mio commented 5 years ago

Device codename: crosshatch TWRP version: 3.3.0-1

WHAT STEPS WILL REPRODUCE THE PROBLEM?

factory flash android 9.0 May update from script (example flash-all.bat)
setup device with password/fingerprint
fastboot boot twrp-3.3.0-1-crosshatch.img
unable to decrypt with password

ADDITIONAL INFORMATION

If May update was done via OTA or factory dirty flash with -w flag to not wipe userdata on top of previous version then twrp 3.3.0-1 is able to decrypt perfectly fine.
May update changed something in how it setup or format new userdata.

prom3t3o commented 5 years ago

I have same issue with my device: sagit

srothkin commented 5 years ago

I have same issue with brand new Pixel 3 I just bought for my wife. I unlocked it and then immediately flashed the May update (blueline-pq3a.190505.002) with -w, fastbooted twrp-3.3.0-0-blueline.img (the latest for Pixel 3), rooted with Magisk and installed Magisk-v19.1.zip and twrp-pixel3-installer-blueline-3.3.0-0.zip.

I then setup the device including PIN and fingerprints.

Then after rebooting to recovery, TWRP doesn't accept the PIN - it keeps saying it is invalid. The only way to get access the SD card from TWRP to make a backup is to first remove the PIN code within Android (which also removes the fingerprints).

My own Pixel 3 (still on the April Android image) is able to unlock just fine in the same version of TWRP. I'm scared now that if I update my Pixel 3 to the May update that it will end up having this same problem.

Bohne commented 5 years ago

same issue with first Pixel (sailfish) and twrp-3.3.0-0-sailfish

srothkin commented 4 years ago

Any projection on when this issue will be fixed?

Sada-Mio commented 4 years ago

Been half a year with the issue. Have a feeling it isn't going to be fixed anytime soon.

They probably busy trying to get it Android 10 compatible since lots of rework needs to be done.

imknown commented 4 years ago

This is maybe a device-tree-side issue.

srothkin commented 4 years ago

The problem happens only if the phone is updated to the May OS update BEFORE installing TWRP. Upgrading a phone that already had TWRP installed doesn't trigger the problem.

Sada-Mio commented 4 years ago

Don't think it is if TWRP was installed prior or not. But, if the OS retained the old partition scheme.

Believe Google changed something in the May update with partitions in prep for android10. Only fresh clean installs used it as it requires a complete format. People with the older partition scheme didn't get affected upgrading the OS. Might also have to do some with the A/B partitioning.

Either this issue will need to be fixed for android10 support or maybe won't be fixed because the new TWRP coding uses an entirely different approach as android10 changed a lot of it's pipework