Booted ;P

Dynamic partition succesfully retrofited for begonia !

PixelExperience BETA builds based on Android 12 will start around end of November / start of December for the Xiaomi Redmi 7A (pine)

A clean flash will be needed

ProtonAOSP 12.0.0 for begonia booted

As per new PixelExperience device requirements, the Xiaomi Redmi 7A (pine) will be dropped as it has a 2Gb/16Gb variant and the minimal requirement is 3Gb/32Gb

Just a little reminder, begonia will be probably deprecated soon by me

#TWRP #Recovery #Unofficial #Denniz
TWRP Recovery v3.6.0_11-0 | UNOFFICIAL.
Updated: 21/12/'21

▪️Download [128 MB]
▪️XDA
▪️Support

Changelog:
• Sync with TWRP 3.6.0 sources
• Update prebuilt kernel to A.14

Note:
• Read the XDA thead for flash steps

By @TheMalachite
Follow @OnePlusNord2Updates
Join @OnePlusNord2GlobalOfficial

Merry Christmas

Hey, Xiaomi Redmi Note 8 Pro support will be dropped from me officially at the 1st April of 2022 since I will switch to Realme 8

Also expect a first and last UnicornHorn build for a11 for Redmi Note 8 Pro at that date

Stable official POSP (enforcing and everything working except screen recorder obviously) rebased over LineageOS tree will be available soon for begonia

Happy new year's

Custom kernel booted for Realme 8

Anyway, posp for Realme 8 soon

Hello everybody, as a member of Teracube developers team, I have access to full MediaTek BSP used on Teracube devices.

I decided to push inside Teracube GitHub organization the MediaTek sepolicy publically used by Teracube with the approbation of Teracube developers team leader, which means third-party developers can use it without getting a possible DMCA from MediaTek and get official maintainership in some custom roms like LineageOS.

This MediaTek sepolicy repo is based over Android 10 sepolicy. However, MediaTek Android 11 sepolicy repo will soon be pushed.

https://github.com/Teracube-Inc/platform_device_mediatek_sepolicy

An update over this post:

MediaTek Android 11 sepolicy repo got pushed.

https://github.com/Teracube-Inc/platform_device_mediatek_sepolicy/tree/teracube-11

Realme 8 development is paused until Realme allow EEA region to unlock bootloader with indepth for Realme 8 or if mtkclient manage to avoid corrupting dm-verity and unlock fastboot access for that device.

Currently some devices only with ID, IN and RU region are able to unlock with indepth for Realme 8.

CBT for RMX3370