Development [RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support

[Steve0007]

Strange, i have never ever in my life used multiuser

Creating a clone app like whatapp creates a second user. There is an ADB command to look at profiles / users
adb shell pm list users if iam right

 

[jamescable]

Update

Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.

Download:

29.11.22 - Google Drive

drive.google.com

How should we flash this if we already have twrp?

 

[osm0sis]

Does the A/B flashable zip with the TWRP ramdisk in it work to install it? Might be able to skip the vendor_boot steps that way.

GitHub - osm0sis/twrp_abtemplate: TWRP A/B Installer Zip Template

TWRP A/B Installer Zip Template. Contribute to osm0sis/twrp_abtemplate development by creating an account on GitHub.

github.com

 

[der_akinator]

Does the A/B flashable zip with the TWRP ramdisk in it work to install it? Might be able to skip the vendor_boot steps that way.

GitHub - osm0sis/twrp_abtemplate: TWRP A/B Installer Zip Template

TWRP A/B Installer Zip Template. Contribute to osm0sis/twrp_abtemplate development by creating an account on GitHub.

github.com

I will try it. Thanks for your tip.

 

[der_akinator]

How should we flash this if we already have twrp?

The only tested method for updating is the default installation procedure. But if you want you cant test the update method used for the official builds.

 

[Evon88]

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.

As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.

For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:

[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...

forum.xda-developers.com

Download:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

Installation:

1. Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
2. Reboot to bootloader.
3. Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
4. Run "fastboot boot boot.img" with the TWRP boot image.
5. Go to Advanced > Flash Current TWRP.
6. After that is done, if you were using a custom kernel, reflash it now.
7. If you were using magisk, reflash it now.
8. Reboot to bootloader.
9. Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.

In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.


Source Code:

• TWRP: https://github.com/TeamWin/android_bootable_recovery
• Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
• Device Tree:
  • https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
  • https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
  • https://github.com/LineageOS/android_hardware_oplus

Bugs:

Please let me know.


Thanks to:

• Nebrassy
• TWRP team
• LineageOS

broooooooo, now you are helping all op9p users
much love and respect

 

[osm0sis]

Update

Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.

Download:

29.11.22 - Google Drive

drive.google.com

Does the A/B flashable zip with the TWRP ramdisk in it work to install it? Might be able to skip the vendor_boot steps that way.

GitHub - osm0sis/twrp_abtemplate: TWRP A/B Installer Zip Template

TWRP A/B Installer Zip Template. Contribute to osm0sis/twrp_abtemplate development by creating an account on GitHub.

github.com

I will try it. Thanks for your tip.

I tried it out over latest Lineage and it does seem to work! I even then re-rooted with Magisk and re-flashed blu_spark from within TWRP.

Only issue (but it's pretty big) is that vibration is broken and it seems to hang the UI hard any time it tries to vibe, so my workaround is to hit Cancel at the Decrypt page, go to Settings and turn all the vibration down to 0, then go back to Mount and Decrypt Data from there. (You can also just be verrrrrry patient when doing pattern.)

Not sure if this is because I installed the whole ramdisk directly like that or because it's over Lineage. I'm guessing the latter, with some kind of modules mismatch?

Any ideas how to resolve that? Disabling vibration entirely might be needed, since I recall @Nebrassy never got it working across all ROMs.

Either way, being able to use the TWRP zips will save a lot of headaches for rooted users.

P.S. Also great that vendor_boot is only need for fastboot tempboot, since that means my twrp_ab addon.d-v2 script should work for us already!

P.P.S. We need to get you in the TWRP Development Zulip if you're not lurking there already: https://rebrand.ly/teamwin-recovery-zulip-community

Edit: twrp-installer-3-7-0_12-0-20221129-lemonadep-zip attachment removed since a newer build exists.

 

[TheSayaMan]

Upon first boot, twrp was freezing and wouldn't let me enter screen lock but after another reboot, its working perfectly.

 

[der_akinator]

I tried it out over latest Lineage and it does seem to work! I even then re-rooted with Magisk and re-flashed blu_spark from within TWRP.

Only issue (but it's pretty big) is that vibration is broken and it seems to hang the UI hard any time it tries to vibe, so my workaround is to hit Cancel at the Decrypt page, go to Settings and turn all the vibration down to 0, then go back to Mount and Decrypt Data from there. (You can also just be verrrrrry patient when doing pattern.)

Not sure if this is because I installed the whole ramdisk directly like that or because it's over Lineage. I'm guessing the latter, with some kind of modules mismatch?

Any ideas how to resolve that? Disabling vibration entirely might be needed, since I recall @Nebrassy never got it working across all ROMs.

Either way, being able to use the TWRP zips will save a lot of headaches for rooted users.

P.S. Also great that vendor_boot is only need for fastboot tempboot, since that means my twrp_ab addon.d-v2 script should work for us already!

P.P.S. We need to get you in the TWRP Development Zulip if you're not lurking there already: https://rebrand.ly/teamwin-recovery-zulip-community

Yes, your twrp install script works for me too. Tanks for that.

I disabled vibration in a fresh build. Maybe I will find a way to get it working but it isn't important.

I think it's is reasonable for non root users to take the extra two steps in comparison to the official version because it's a one time thing. Updates are possible by using the zip installer.

 

[der_akinator]

Update

Sorry for the short update cycles but there are some problems with vibration that results in heavy input delays.
But the new update also includes a zip installer by @osm0sis which you can just flash to update your currently installed version.

Download:

30.11.22 - Google Drive

drive.google.com

 

[erad1]

So first off ...thanks for the awesomeness! But ... I'm having an issue with roms not flashing because of a "timestamp" issue? Is there a workaround?

 

[GeminiRx]

Quick question.
The following is not clear to me.
In step 1 it says to download your own vendor_boot.
In step 3 it says to flash it but which one? My own one or the TWRP one. (I'm currently on CrDroid13)

 

[TheSayaMan]

Quick question.
The following is not clear to me.
In step 1 it says to download your own vendor_boot.
In step 3 it says to flash it but which one? My own one or the TWRP one. (I'm currently on CrDroid13)

You flash the twrp one in order to boot twrp, then after permanent install, you flash yours or it won't boot to os

 

[GeminiRx]

You flash the twrp one in order to boot twrp, then after permanent install, you flash yours or it won't boot to os

Thx for the quick answer. That worked

 

[osm0sis]

You flash the twrp one in order to boot twrp, then after permanent install, you flash yours or it won't boot to os

Now that there's a TWRP zip you could skip vendor_boot shenanigans altogether by, a) flash from Magisk app, or even b) flash from custom ROM recovery like Lineage Recovery.

 

[TheSayaMan]

Thx for the quick answer. That worked

Your welcome, anytime

 

[IamTheBRAVE]

Now that there's a TWRP zip you could skip vendor_boot shenanigans altogether by, a) flash from Magisk app, or even b) flash from custom ROM recovery like Lineage Recovery.

When flashing from magisk, do we flash to inactive slot?

 

[TheSayaMan]

Now that there's a TWRP zip you could skip vendor_boot shenanigans altogether by, a) flash from Magisk app, or even b) flash from custom ROM recovery like Lineage Recovery.

Actually no, when you boot this twrp, it will not boot to twrp without the twrp vendor_boot. Likewise, the os won't boot unless you replace it with the original vendor_boot from stock, rom, etc.

 

[TheSayaMan]

When flashing from magisk, do we flash to inactive slot?

No it will automatically install to active slot. You can change slots but no reason to.

 

[der_akinator]

So first off ...thanks for the awesomeness! But ... I'm having an issue with roms not flashing because of a "timestamp" issue? Is there a workaround?

Can you please send me a logcat and recovery log. I have seen an initscript related to timestamps in Nebrassy's op7 device tree. Maybe this would solve the problem.