[RECOVERY][ANDROID 11] TWRP 3.7.0-11

[angpysha]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

#include <std_disclaimer.h>
/*
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

Features:​

- TWRP boots
- Decryption works
- Rom flashing should work
- Backups should work
- Flash partition should work
- Format/wipe data works
- Backup Restore
- Fastbootd
- System and vendor image flash should work
- Decryption works only in Android 11. Decrytprion for later versions of Android WIP

-USB-OTG - I cannot test, because I have not a USB-OTG cable. Please, send me a result to PM

Note: boot takes about one minute - it required by decryption​

Install guide:​

You can install it from fastboot using command

fastboot flash recovery_$(slot) path_to_recovery/recovery.img

Or you can directly boot it:

fastboot boot path_to_recovery/recovery.img

Download:​

Link

Sources:​

angpysha/android_device_OnePlus_Nord_N100 at android-11 (github.com)

Thanks:​

hellisabove - for initial device tree
infectedmushi - for device tree for OnePlus 8 with working encryption
TeamWin

 

[angpysha]

Reserved

 

[angpysha]

Reserved

 

[thomaskmaagaard]

I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.

 

[thomaskmaagaard]

I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.

Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.

 

[angpysha]

Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.

Oh, yes. I forgot to write that boot takes about one minute. Thanks

 

[tonydiepyyz]

Thanks for releasing this. Used it this weekend on OnePlus Nord N100 Model BE2013 Oxygen OS 11.0.10.BE83BA

# TWRP recovery-3.7.0-11-08012023 worked for multiple flashed

Was working fine flashing 4 or 5 ROMs to taste test them. CAOS rom worked like a charm. Nothing else worked. Somewhere along the line I deleted a logical partition to make room for Pixel Experience. It suffered flickering / dimming issues so reflashed CAOS.

TWRP was working so well I flashed it to my phone.

# TWRP recovery-3.7.0-11-08012023 stopped being able to mount volume

Then TWRP couldn't mount the partitions for writing anymore. Volume showed 0 bytes available. Fastboot could not recreate logical partitions. Weird thing was I could write a test file in /system but I couldn't flash /system. Fastboot error messages said it could not find partition or there was no room left. Somehow TWRP's ADB shell could get into the /system partition but its flashing could not ?!?

# TWRP recovery-3.7.0-11-08012023 did not see USB drive through OTG cable

Tried to access ROM through USB drive through OTG cable. TWRP could not mount it.

# Recovery

* Had to use MSM tool to cover phone to Stock today.
* After recovery, I flashed CAOS using Fastboot instead of TWRP because I'm not sure if I did something wrong or if TWRP wasn't working properly.

 

[tonydiepyyz]

# Can't boot after TWRP backup (no restore)!?!

I booted into TWRP through fastboot boot twrp.img so that it wouldn't write anything. Used TWRP to do a backup and saved backup to external sd card (not the /sdcard directory but the separate external sd card).

So I didn't flash recovery or anything else. I did a backup to an external sdcard. I did not flash or write anything to the phone's memory.

Now when booting it gets stuck on the logo!?!

How do you recover from that?

Looking at /tmp/recovery log shows that twrp wasn't able to mount /data /product

 

[bentalebnordine]

This recovery works well, it flashs every partition except the super partition you can flash it with the terminal of the recovery.
There is one obstacle, which is you need to replace stock product with gsi product to be able to flash lineage 19.1, and to be able to flash larger ROMs you need to delete the system_ext partition (I suppose ). I will attach it to my reply.
The second obstacle is the backup when restored it show some bugs. and the last one is that Android 13 is a little bugy in this slot unlike the other slot.

 

[bentalebnordine]

I flashed successfully the super image with this recovery, thank you guys.

 

[bentalebnordine]

Hi guys, I have good news for you, this recovery works in both slots ( with boot _A10 and boot_A11), so weird but true.
This recovery is fully working, I mean you can flash Zips and IMGs and you even use its built-in terminal to pull or push partitions.
There is one problem which is the resizing, you can do it with CMD command
fastboot resize-logical-partition system_a 4210000000
or
fastboot resize-logical-partition system_b 4210000000
And this can be done anly by flashing the product_a, product_b and the system_ext_b partitions with small size IMGs like product_gsi.img(you need to put this file in the adb-fastboot folder) . (you can flash it in product_a, product_b and system_ext_b. It does not serve anything, it just reduces the size of this useless partitions. You can find it with a working adb-fastboot tool.

 

[Bill345]

Well, this TWRP is flashing Magisk, and I can make a backup, but when I want to restore the backup, errors occur, including the bootloop. Has anyone encountered this problem?