LOS update problem via TWRP

[Singulus]

TWRP 3.2.3 is released:
https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html

• Fix automatic installing of OTA zips on encrypted devices
• Remove SuperSU from TWRP
• Support both md5 and md5sum file extensions when doing MD5 checking for zip files

[bastoGrande]

I’m not sure if it belongs in this topic, but I have the problem that I can’t enter anymore the recovery mode.

Last week I did the upgrade to LOS 15.1 and wanted to update to this weeks update of LOS today, but couldn’t install anything because it seems like I can’t enter TWRP anymore? Afterwards the failed update, my FP2 simply rebooted instead of enter the recovery mode, so I tried to reboot into recovery without the LOS updater app, but even this didn’t work.

So I’m not sure what is wrong? Do I need to reflash TWRP or did I brick something?
In LOS everything seems to work, at least I didn’t imagine anything wrong.

before the update to 15.1 I installed the latest version of TWRP.

@Roboe, @z3ntu, @AnotherElk: any ideas?

[AnotherElk]

@bastoGrande

I tried to reboot into recovery without the LOS updater app, but even this didn’t work.

Please confirm … if you press Vol + all the way through rebooting (from the moment the screen goes blank to the moment TWRP appears) … this doesn’t work?

@bastoGrande

Do I need to reflash TWRP

If in doubt, you can do this anytime.

@bastoGrande

any ideas?

Well, there’s always booting TWRP without flashing it …

https://forum.fairphone.com/t/howto-use-twrp-without-flashing-it-e-g-for-backup/23747

[Amber]

Hi @AnotherElk

the guide to boot into recovery without flashing doesn’t work for me, because similar to @bastoGrande my phone after flashing last weeks’ LOS 15.1 can now only reboot into OS.

Any adb reboot recovery or adb reboot bootloader (or power + Vol+ or power + Vol-) always results into booting OS instead. Even when using the previously installed TWRP app I experience the same problem.

fastboot doesn’t recognize the phone when OS has booted and with adb I cannot flash anything…

[AnotherElk]

The guide doesn’t do anything with ADB.
Please follow the guide (resulting in … fastboot boot signed_recovery_image_of_choice).

[bastoGrande]

@AnotherElk

Please confirm … if you press Vol + all the way through rebooting (from the moment the screen goes blank to the moment TWRP appears) … this doesn’t work?

Juhuu, that worked already… afterwards I entered TWRP I installed the LOS-update right away, but what is the problem? Is it a known issue? Do I need to change something?

[Singulus]

It is a known issue, that with the new camera module installed, you can’t boot to recovery from within Android. Workaround is to press Vol + until it (hopefully soon) get’s fixed.

[brab]

@Singulus

It is a known issue, that with the new camera module installed, you can’t boot to recovery from within Android.

I don’t have the new camera module and I have the same issue.

[Amber]

For me, the hint of @Ingo has worked out to boot without camera. I could go to recovery in whatever way I liked. But in contrary to @brab using the old camera module it works as well.

[AnotherElk]

@brab

I don’t have the new camera module

Are you sure? If you got a brand new Fairphone 2 in October 2017 …

@brab

For the record, I just got a brand new FP2.

… you should have the new camera …

Will the new camera module be in the new FP2 batches?

yeah, sadly there is always going to be a line somewhere… FP2 Pre-sale orders promised to be delivered by Mid August will feature the old camera. Orders delivered by Mid September and later feature the new camera.

Did you install an old one afterwards?

The new module most notably has a white “separator” between the lens and the flash, the old module didn’t have that … here’s a picture of the two modules.

[brab]

You’re right, I do have a new module and I did not even know it (I thought it was upgrade only). Sorry for the confusion.

[BIOHAZARD]

Hi, FP-Community.

Sry if i do a re-post or asking a question already solved, but i have a problem with twrp 3.2.3.0 an LineageOS 15.1 (Build 20181022).

I have installed twrp 3.2.3.0 and LOS 15.1 today and encrypted my FP2 in LOS. I can reboot or shutdown/start my FP2 and enter my encryption key. Normal boot, normal function and login in LOS. So far so good.

But when i want to boot into twrp-recovery (manual or enhanced restart-menu in LOS) i can not enter the encryption key. This error appears:

---

Updating partition details…
…done
Unable to mount storage
Full SELinux support is present.
Failed to decrypt data.

Im sure, ive typed the correct code, the key works by starting into LOS.
Does anyone have a solution for this situation or more information…?

Greez BIOHAZARD

[z3ntu]

That’s an issue with TWRP, see https://github.com/omnirom/android_bootable_recovery/issues/224

[AnotherElk]

@BIOHAZARD

Does anyone have a solution for this situation or more information…?

If you want a fix now, install one of Fairphone’s OSes (Android 6 currently), set a lock screen pin/password/pattern, then encrypt the phone, then install TWRP 3.2.3-0 and wipe everything (only wipe, no format!), then install LineageOS 15.1 . That way TWRP can still access the encrypted data partition, and LineageOS 15.1 is fine with it, too.

I installed LineageOS 15.1 for microG on prior encryption myself, works like intended.

[BIOHAZARD]

Thanks AnotherElk, seems to be a little tricky for me…

I have tested de update to the lastest LOS-Build (20181029) with encrypted phone and all worked perfectly. So its only the access to the encrypted partition in twrp, that doesn`t work. And i will need this access only, if i have a problem with my phone/LOS, to wipe, format or something…

By the way, the same twrp works perfectly on my samsung s7 (also encripted). Seems to be only a problem of a few twrp-recoverys / phones, including the fairphone 2…

I will wait for a (hopefully fast) solution/update of twrp.

[Tuffi]

Hey.
Will this help us to decrypt our FP2 in TWRP?

Issue: Cannot decrypt device in LOS 15.1

[AnotherElk]

@Tuffi

Will this help us to decrypt our FP2 in TWRP?

Upgrading from *official* 14.1 to 15.1 (feedback/issues)

So what I know: The 3.2.3-1 version that is available for some devices is a rebuild of version 3.2.3 but with an updated device/kernel tree. I asked what was changed in the devices that got the -1 build but I only got vague answers from the TWRP maintainers. I’ve looked into the issue on the FP2 multiple hours trying different things that didn’t help at all unfortunately. Basically I don’t know what part is broken so i can’t fix it…

[Tuffi]

I tought the neccassary changes are discribet in the yesterdays post from github user kumajaya

But to be honest: I have no idea how to figure this out.
If i made an unusefull post: Sorry.

[AnotherElk]

@Tuffi

I tought the neccassary changes are discribet in the yesterdays post from github user kumajaya

But to be honest: I have no idea how to figure this out.

I’m no developer either … so, perhaps you really have found something here.

I only saw at first glance that the fix seemed to be for bacon (= OnePlus One), and since fixes for several devices exist already and didn’t translate over to the Fairphone 2 as per the statement of @z3ntu (the maintainer of Fairphone 2 TWRP) in the other topic, I thought I’d link to his statement here, too.