Database Info

[ROM][CM] KitKang Rom CM11 Kangs (**Building Guide Now Included!!)

Welcome to KitKang ROM!​
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* 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.
Click to expand...
Click to collapse
Description:
KitKang ROM is a ROM built from the CyanogenMod 11 source, with some cherrypicks added for features and functionality.​
Bugs List:
Code:
-???
Current CherryPicks
Code:
#56346 LockScreen: allow long-press actions from hardware keys (1/2)
#56357 LockScreen: allow long-press actions from hardware keys (2/2)
#55209 Forward port Status Bar interface (1/2)
#55211 Forward port Status Bar settings (2/2)
How To Flash:​Coming From a Different ROM?​
1. Make sure you are unlocked and running the latest version of ClockworkMod Recovery (Either Touch or Non-Touch is fine). If you do not know how to unlock your bootloader or install recovery, follow these steps.
2. Make sure you are running the latest firmware version. If you do not know what firmware version you are running, you can check in Settings in the "About Phone" tab. Currently, the latest firmware is VRBMF1, and a recovery flashable of the firmware can be found here. To install, simply reboot to ClockworkMod and flash the zip file.
3. Backup everything you need. All of your files will be deleted! To backup your apps, I recommend using Helium. It is very easy and straightforward.
4. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
5. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
6. Wipe the data, system, cache, and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
7. Install the ROM and G-Apps files
8. Reboot and setup your phone!
Click to expand...
Click to collapse
Updating From A Previous KitKang Nightly?
1. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
2. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
3. Wipe the cache and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
4. Install the ROM and G-Apps files
5. Reboot!
Click to expand...
Click to collapse
Download Links​
ROM DOWNLOAD
(Note: This is a folder, and has all of my builds. Download the one you want. If you don't know what to download, use the latest.​
G-APPS DOWNLOAD​
KANGED G-APPS DOWNLOAD
Not supported or recommended because of stability issues. However, this does include the new dialer with Google Search support. Use with caution. If you do not know which G-Appps package to use, use the first link.​
Enjoy?​
If you enjoy the ROM, please consider sending me a donation​
​​
XDA:DevDB Information
KitKang Rom CM11 Kangs, a ROM for the Verizon Samsung Galaxy S III
Contributors
dmeadows013, XRaptor29, cammykool, tvall
ROM Kernel: Linux 3.4.x
ROM Firmware Required: VRBMF1
Based On: CyanogenMod
Version Information
Status: Testing
Created 2013-11-14
Last Updated 2014-01-01

Guide to Building
Guide for Building KitKang on Mac OSX
This is a guide demonstrating how to build KitKang for yourself on Mac. I am not responsible for anything you do to your computer or your phone as a result of following this guide. Before building, I would recommend that you have at least a little knowledge of Terminal, and a powerful computer. AOSP takes up a lot of resources, and even my i7 Ivy Bridge build with 16GB RAM and an SSD takes almost an hour to build. The AOSP code takes up a lot of space, so I recommend AT LEAST 150GB free space, just to be safe. This guide involves installing specific packages to build AOSP. To install these packages, we will use Homebrew. You will also need XCode to build. If you do not have these installed, refer to the beginning of the guide. If you already have these installed for some reason, skip the first section for installing XCode and Homebrew.
Click to expand...
Click to collapse
Installing XCode/Homebrew
Download and install XCode from the Mac App Store. You will need an Apple account to do this.
After downloading and installing XCode, you will need the Command Line Tools. These can be installed by opening a Terminal window and entering:
Code:
xcode-select --install
After entering this, hit return and a box should pop up asking you if you want to install Command Line Tools. Click yes, and wait for it to install.
Now, make sure you have the latest Java Runtime. You do this in Terminal by entering a command and going through an installation process. Enter the command
Code:
java
With the Command Line Tools and Java installed, we can now install Homebrew. To do so, open Terminal again and enter the following:
Code:
ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go/install)"
Make sure Homebrew is installed and works correctly by running
Code:
brew doctor
If you got errors in the previous command, try googling to see if there is something else you need. If you can run the command without errors, you are good to go!
We must now move the SDK so the build recognizes what to use. To do this, run the following commands in Terminal
Code:
sudo mkdir /Developer
Code:
sudo mkdir /Developer/SDKs
Code:
sudo cp -r /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk /Developer/SDKs/MacOSX.sdk
NOTE: You need superuser permissions to run the previous 3 commands.
Now, in Terminal, type
Code:
nano ~/.bash_profile
If you get a no file found error, then run
Code:
nano -w ~/.bash_profile
You should get a screen with some text. Scroll to the bottom using the arrow keys until there's just blank spaces, and paste the following code
Code:
export BUILD_MAC_SDK_EXPERIMENTAL=1
Save the file using ctrl-x and clicking yes and enter
Restart Terminal to make the changes take effect
With Homebrew now installed, we can continue to downloading required build packages!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installing Required Packages
Now we will install packages required to build the AOSP source. This can be done with the Terminal command
Code:
brew install git coreutils findutils gnu-sed gnupg pngcrush repo
With these packages installed, we need to make some symlinks so that OSX knows which files to use, and doesn't mess up the build. To do this, enter
Code:
ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed
With these packages installed, we are now ready to create a build environment and download the AOSP source.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Preparing the Build Environment and Downloading the Source
First, we need to create a dedicated workspace for our AOSP code. This can be done in Terminal by entering
Code:
hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 120g -volname "android" -attach ~/Desktop/Android
This will create the workspace image on our desktop. To move it, simply drag and drop in Finder to the location you want.
Now, locate the workspace in Finder and double click it to mount it
NOTE: If you moved your workspace to a different directory, you will have to use the path to that directory in the previous step.
Next, from within Terminal, locate the directory by typing
Code:
cd /Volumes/android
Now that we are in the working directory, it is time to download the Android Source. This is done by entering the following command
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0 && repo sync && say 'finished'
Wait for the download to finish. Depending on your connection, it can take a long time, so get comfortable.
When the download finishes and you can see all of the source folders in your directory, it is time to download the S3 specific files. To do this, we need to edit the roomservice.xml. However, this file is hidden. We can access it by entering the following in Terminal
Code:
open -a TextEdit .repo/local_manifests/roomservice.xml
You should get a blank file in TextEdit. Enter the following code as is here
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
Save and close the file, and again run
Code:
repo sync
With the S3 specific files downloaded, we need to download the CyanogenMod specific app files. This can be done by running
Code:
./vendor/cm/get-prebuilts
With this done, we need to download the cherrypicks specific to the S3. Eventually, these will not be needed, but as CyanogenMod 11 is still in beta, it is needed for now. Because the cherrypicks are often being merged, and new ones created, the kind folks at CyanogenMod have created a Google Document with a list of the latest commits. This is located here. NOTE: This document does not include any cherrypicks that I may include for features. By using these cherrypicks, you are installing everything needed to make the ROM as stable as possible. I may occasionally include other cherrypicks that I find enhance features. Inside the document, scroll down to the '# repopicks' section and continue scrolling past the commit messages. At the bottom, you will see a section titled 'Combined'. This will have a command such as
Code:
repopick -s s <List of commit hashes>
You could simply copy this command and paste it into a Terminal window, but that would put the cherrypicks on new branches of the source, which could cause problems with resyncing the source. I would recommend copying only the commit numbers.
In Terminal, run the command
Code:
. build/envsetup.sh
Run the repopick command, adding the commit numbers to the end. Here is an example
Code:
repopick 53075 53131 53302 53309 53356 53445 53528 53595 53603 53604 53637 53964 54197 54198 54219 53468 54251 54274 54277
If the commits do not all merge correctly, you will get what is called a merge conflict. This is because one or more of the commits does not play nice with the CyanogenMod code. Make sure you have the latest code by resyncing, and also make sure you have the latest cherrypicks. If the command still fails, wait a few hours because the document probably just hasn't been updated.
Once you get all of the commits merged correctly, it is time to build!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Building the Source
Before building, if you have extra space on your hard drive, you can optionally use CCache to speed up your build a bit. Enable this from inside the working directory by using
Code:
export USE_CCACHE=1 && prebuilt/darwin-x86/ccache/ccache -M 20G
You may also need to change the ulimit to support building. On OSX 10.9, I experienced errors stating that I had too many files open, and I had to change the ulimit amount. NOTE: If you have issues, you will need to do this every time you build! Change the ulimit amount by running
Code:
ulimit -Hn 8192
and
Code:
ulimit -Sn 8192
Make sure your working directory is clean by running
Code:
make clean
Next, initiate the build by running
Code:
brunch d2vzw
If all goes well you should have a flashable zip in the out/target/product/d2vzw/ folder. Enjoy!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updating the Source
Later on, you may decide to build another file to see with new changes to the CyanogenMod code. Think of this as a ROM update. To do this, you will need to follow some steps. All of these steps have been completed already in this guide, so I will just be outlining them, and will not be listing everything. If you forget how to do something, consult the guide.
Repo sync
Apply cherrypicks
Enable CCache (Optional)
Set the ulimits
Clean your working directory using
Code:
make clean
Build the code using
Code:
brunch d2vzw
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Reserved

reserved

Recognized Developer - OP
OP hmmm OVER POWERED
Finally i can choose between sspencer10,tvall and cammykool and now you!
---------- Post added at 01:06 AM ---------- Previous post was at 12:41 AM ----------
Same Gapps? PA?

Is the 4.3 or the 4.4 camera included in this rom? If it is the 4.4 camera, is the quality of the photo better than the initial builds? Thank you.

-External SD Card May or May Not Work
It does work

markdapimp said:
-External SD Card May or May Not Work
It does work
Click to expand...
Click to collapse
The reason why he posted that is because one thing gets fixed another is broken. Every Device is different kinda thing.

XRaptor29 said:
The reason why he posted that is because one thing gets fixed another is broken. Every Device is different kinda thing.
Click to expand...
Click to collapse
I have 3 S3's my mom's dads and mines SD works perfectly on all 3

markdapimp said:
I have 3 S3's my mom's dads and mines SD works perfectly on all 3
Click to expand...
Click to collapse
Well thats a good thing lol :good:

Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!

mds96 said:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
Click to expand...
Click to collapse
Do a clean wipe in CWM and flash the FULL PA Gapps
---------- Post added at 02:22 AM ---------- Previous post was at 02:12 AM ----------
Some screenshots for OP

mds96 said:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
Click to expand...
Click to collapse
seems to be a bug to only paid apps. free ones work for me. weird.

XRaptor29 said:
seems to be a bug to only paid apps. free ones work for me. weird.
Click to expand...
Click to collapse
I see what you mean

Thanks Markdapimp! I kinda figured a clean wipe would solve the problem, but guess I wanted to be lazy, lol

markdapimp said:
I see what you mean
Click to expand...
Click to collapse
Pretty sure this is because of the SD card problem. Hopefully there is a fix soon

Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2

WeThePeople13 said:
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would just do a clean flash just to be sure

WeThePeople13 said:
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes dirty flash should be fine, but idk for sure. I've got homework to do but when I get time I'll make a new build and upload/put more stuff in the OP. Maybe tonight but probably not.
Screenshots in screenshots tab thanks @markdapimp

Yea that is what i was thinking. I just am lazy lol and I really hate doing that whole process of getting art enabled.
Sent from my SCH-I535 using Tapatalk 2

[UNOFFICIAL][wrappedkey] LineageOS 16 with CAF encryption support

Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet

Thanks ?

Thank you for the ROM!

There's a Typo in the ROM os version description.

cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.

jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.

jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?

Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.

jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first

Download link not working
Edit: UC browser was the culprit

dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue

gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer

rom keeps rebooting into twrp , i did every step

gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too

Device not charging above 86%. Anyone else facing this bug ?

PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!

lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build

PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.

lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint

Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.

[RECOVERY][grus] KudProject's Unofficial TWRP 3.5.2_9-1 [16-05-2021]

This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's 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.
Disclaimer​
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* I am 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 RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements​
Xiaomi Mi 9 SE (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing Instructions​I assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Optional: Flash stock vbmeta with the following command (attached if needed):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-grus.img
Where x and y are version of TWRP you're going to flash.
IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
Swipe the option to allow modifications. This will prevent stock ROM from replacing recovery, however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues​
/dev/null
Special Thanks​
Dees_Troy and everyone behind TWRP
Everyone on Mi 9 SE community
Device Sources​
TWRP repository fork
Device tree
Kernel source

Changelogs​twrp-3.5.2_9-1-KudProject-grus
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated kernel to MoeSyndrome kernel based on Android 10
Mount firmware partition as read-only
Added support for formatting Cust partition in GUI
twrp-3.4.0-0-KudProject-grus
Merged TWRP source changes up to 22 June 2020 (UTC+8)
Supports decryption of userdata on Android 10-based MIUI and custom ROMs using Android 10 crypto blobs (might not be backwards compatible)
Restored system and vendor (non-image) backup support
Added support for backing up persist (and the image)
Build some blobs from source
Updated remaining blobs from V11.0.2.0.QFBEUXM
Updated prebuilt kernel to latest Pie
twrp-3.3.1-3-grus-20190802
Switched to source-built kernel
Updated blobs from MIUI China developer 9.7.4
Added support for F2FS in kernel (tell me if decryption breaks on this file system though)
Added persist into fstab
Added vendor-side touch firmware
Get CPU temperature from proper thermal zone
Disabled vbmeta checks
Only allow image backups for system and vendor
Symlinked /system to /system_root/system for backward compatibility
Misc stuffs
TWRP and f2fs-tools upstream changes
twrp-3.3.1-2-grus-20190609
Fixed wrong USB-OTG mount point
twrp-3.3.1-1-grus-20190603
Updated prebuilt kernel and DTBO from MIUI China developer 9.5.30
Corrected vendor image flashing
Support for wiping /vendor
Support for flashing and backup up (as part of boot) DTBO
Defined TW_SCREEN_BLANK_ON_BOOT
(Properly) excluded TWRP app
Included private recovery configuration
twrp-3.3.1-0-grus-20190531
Initial build.

Notes​
Don't use fastboot boot to boot the recovery; it'll proceed to boot system instead using recovery's kernel. If this happens with your current kernel's boot image security patch being older than recovery one, you're basically busted as FBE keys are upgraded the time newer combination of system + vendor + boot image security patches are detected.
If you're out of luck in this situation, the only way to resolve is to format data (just backup your data to somewhere safe before doing so).
If you flash disabled vbmeta, you can't flash stock MIUI zips until the original vbmeta is restored.

Wrapped key support is added into recovery just for anticipation, although not defined by default in fstab.
I can't test it since EEA device so far is on March ASB as of V10.2.5.0 stable.
Otherwise, basic functionalities including decryption should work.
Edit: grus doesn't have anti rollback enabled at this moment, but Xiaomi may enable it in the future...

it is save changed from wzsx150 twrp ? or must on fastboot ?

bonbibonkers said:
it is save changed from wzsx150 twrp ? or must on fastboot ?
Click to expand...
Click to collapse
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.

ok, gonna test it out , many thanks great work ??

Thanks! working so far so good

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
Working fine when flashing from wzsx150 twrp version.

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol

rzki03 said:
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
Click to expand...
Click to collapse
Just ignore it. That same CPU temperature glitch also happens on sirius.

Wow, finally an *actual* twrp
Sent from my Mi 9 SE using Tapatalk

krasCGQ said:
Just ignore it. That same CPU temperature glitch also happens on sirius.
Click to expand...
Click to collapse
okay then. thank you!

@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks

denzel09 said:
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
Click to expand...
Click to collapse
So this release doesn't have Backup/Restore working?

luisbelmont said:
So this release doesn't have Backup/Restore working?
Click to expand...
Click to collapse
Yes, it has. My request was a bit different.

denzel09 said:
Yes, it has. My request was a bit different.
Click to expand...
Click to collapse
Oh, perfect! Thank you. What advantages does your request have?

luisbelmont said:
Oh, perfect! Thank you. What advantages does your request have?
Click to expand...
Click to collapse
To backup and recover dtbo image before and after flashed this custom kernel: https://forum.xda-developers.com/mi...nel-okitakernel-v1-0-mi-9-se-27-2019-t3934029

Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).

puppetminds said:
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
Click to expand...
Click to collapse
Kinda off-topic, but well rebasing over CAF is a tough job...
Sent from my Mi 9 SE using XDA Labs

[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s

DESCRIPTION
Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download.
FEATURE
The following items may not be available for all versions, please use the latest build!
Click to expand...
Click to collapse
Build with user variant instead of userdebug (to reduce image size and improve performance).
CPU/GPU is overclocked with optimized voltage/bus-cci and 300 Hz/Jiffies kernel clock frequency. [16.0 +]
EAS (sched cpufreq governor from linux-3.18) CPU scheduler implemented. [16.0 +]
Full-weight NotoSansCJK fonts included (to display East Asian characters with more font weights).
High screen refresh-rate (75 Hz) support for Mi-4c with "Sharp-rsp61322 LCD" screen. [16.0 +]
Implement ZRAM with ZSTD crypto algorithm (KSM is used after 20210116) to improve I/O performance on devices with 2GB RAM. [16.0 +]
Linux kernel is built by clang-12 toolchains, with Polly + LTO + -Ofast optimization to get better performance. [17.1 +]
Pre-dex2oat with everything filter globally (sacrificing space and first-install time to improve efficiency).
Remove or disable unnecessary kernel configs and modules, also includes some other optimizations. [16.0 +]
Remove unnecessary apps/binaries/libraries/services from system. [16.0 +]
Signature spoofing support (ready for MicroG, including Chinese translations).
User-friendly controller for special features in Settings app (like CPU overclock, Edge gesture and Screen refresh rate). [17.1 +]
...
STATUS
Go to GitHub Issues for more details and give me feedback.
Click to expand...
Click to collapse
Working
Basic hardware
Baseband/SMS
Bluetooth
Camera/Flashlight
IR remote
Speaker/Microphone
Wi-Fi
Extras
Camera API2 (with patch) [17.1 +]
Edge gesture (in Settings > System > Buttons) [16.0 +]
Overclock control (in Settings > Battery > Battery saver and performance) [17.1 +]
Screen refresh rate (in Settings > Display) [17.1 +]
Not working
SELinux permissive [16.0 +]
VOLTE (won't fix because of no compatible IMS stacks) [16.0 +]
DOWNLOAD
GitHub Releases: https://github.com/BYZYB/android_device_xiaomi_libra/releases
Kernel/ROM: https://www.androidfilehost.com/?w=files&flid=287533
TWRP: https://www.androidfilehost.com/?fid=8889791610682882451
SOURCE
Device: BYZYB/android_device_xiaomi_libra
Forked from (16.0 +): android_device_xiaomi_libra + android_device_xiaomi_msm8994-common
Kernel: BYZYB/android_kernel_xiaomi_libra
Forked from: android_kernel_xiaomi_leo
Vendor: BYZYB/android_vendor_xiaomi_libra
Forked from (16.0 +): android_vendor_xiaomi_libra + android_vendor_xiaomi_msm8994-common
Custom changes: repo_17.diff + repo_18.diff
Thanks to all developers and users (Gah0 | Mortezadadgar | Xiaomi classic dev | ...) who contributed to Mi-4c/Mi-4s (including other devices shipped with MSM8992/8994 SOC) or gave me help!
Click to expand...
Click to collapse

TIPS
Here are some tips which may improve your experience or resolve some problems.
Basic quality assurance: I only have one smart phone (3+32GB Mi-4c ×1), so the ROMs here should at least satisfy my daily usage.
This project will be kept maintained even after I bought my new mobile phone (8+128GB Mi-Mix-2 ×1) in 2021. My Mi-4c is one of the most meaningful items of my own, it's not easy to leave it behind in the drawer and say goodbye. The new battery and rear cover (thanks to yipinghuang1991) will refresh this old device and make it usable again.
Even though the signal icon in status bar shows "No signal" at the first minute after boot, the device is still able to receive SMS and phone calls (so the device does have signal, but the system doesn't admit it at all).
If the free space in /system is not enough to install GAPPs, try to delete /system/fonts/NotoSansCJK.ttc to get about 100MB free space (If Chinese/Japanese/Korean is not your main language). Removing the prebuilt Webview packages (about 120MB) after installed another one is also a solution.
If you found random reboot on your device with overclock enabled (or just updated to lineage-17.1-20201216 and left overclock option unchanged), please disable this feature to see if this issue is resolved. Go to Settings > System > Battery > Battery saver and performance, enable then disable "High performance mode", and reboot your device. If you are using lineage-17.1-20210209 or newer, it's no need to do such steps after a clean install (as both persist.sys.cpu_overclock and persist.vendor.edge_touch_mode are default to false by default).
It's highly recommended to disable system logs to reduce resource consumption (for better performance and privacy), unless you're going to collect system logs. Go to Settings > System > Developer options, and set the value of "Logger buffer sizes" to off.
It's not recommended to use SELinux enforcing mode even if it's supported in some builds. Also, please consider the negative effect of I/O performance before enabling disk encryption, unless you really want to.
BUILD
As all source codes and custom changes in my LineageOS ROMs are open-source, you are permitted to build your own ROM or kernel (not only for LineageOS) with my sources for non-commercial purpose.
There are many documents about how to build custom Android ROMs in Linux/OSX, so I will not post these basic steps here to reduce redundancy. However, there are still some important things which may not be included in other documents. Here are some basic steps about what you should do (using lineage-18.1 as example), you can also take a reference to other tutorials.
Install necessary packages
There are a number of "necessary" packages listed in most tutorials, but not all of them are needed. Here are the packages you need to install manually on Ubuntu or Debian.
sudo apt install bc bison git gnupg make repo rsync unzip zip
Sync Android sources
You need to download and update your local repo with upstream sources regularly, in order to get new changes as soon as possible (just like other open-source projects).
Init repo to current directory: repo init -u https://github.com/LineageOS/android.git -b lineage-18.1 --depth=1
Sync all repos and prune unused branches: repo sync --prune
If nothing wrong happened, the LineageOS sources have been downloaded to your computer (about 100GB). Here are some commands which might be useful in the future.
Show all local changes of your repos: repo status or repo diff
Perform any operations to all repos: repo forall -c "xxx"
Setup local manifest
To sync your Android sources with upstream repos easily, it's recommended to create a local manifest in ./repo/local_manifests/. The local manifest should be a XML file like the following one, any filename is accepted (file: libra.xml).
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="BYZYB/android_device_xiaomi_libra" path="device/xiaomi/libra" remote="github" revision="lineage-18.1" />
<project name="BYZYB/android_kernel_xiaomi_libra" path="kernel/xiaomi/libra" remote="github" revision="master" />
<project name="BYZYB/android_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_xiaomi" path="hardware/xiaomi" remote="github" revision="lineage-18.1" />
</manifest>
Resolve build errors
Due to some hacks in my device configurations which are conflict with Android build rules, there might be some build errors if using all my repos directly. To resolve this issue, you need to modify project build/make/manually on your disk. After that, you should be able to prepare the necessary environment for Android build without errors.
Setup build namespace only: . build/envsetup.sh
Prepare build environment for Mi-4c with a specified build variant (xxx = eng/userdebug/user): . build/envsetup.sh && lunch lineage_libra-xxx
If you want to build the ROM in "user" build variant instead of the default "userdebug", more changes are needed to avoid build errors or potential bootloop. The following commands are some ways to build a full ROM.
Build full ROM in "user" variant: brunch lineage_libra-user
Build full ROM in "userdebug" variant: brunch lineage_libra-userdebug
Build full ROM with a specified number of threads (x ≤ physical CPU cores): lunch lineage_libra-xxx && make -jx
If you have lunch before, here is the simplest way: m
As git patch files are similar to git diff, you can always do these changes manually without using git am xxx.patch && git reset HEAD^ or other shell commands.
Kernel build toolchains
The kernel supports to be built with gcc-9+ or clang-10+. As Link-Time-Optimization (LTO) for Clang is enabled by default (config: CONFIG_LTO_CLANG), building the kernel with GCC directly will result in build errors. In conclusion, it's recommended to choose Clang as your toolchains for both faster build speed and better performance.
As VDSO compat is enabled (config: CONFIG_COMPAT_VDSO), both arm and arm64 toolchains are needed to build the kernel. Clang could handle different cross compile targets easily (thanks to LLVM), but GCC could not. Also, though the kernel sources are compiled by clang, they will be linked by LD (included in GCC toolchains -> Binutils) with LLVM plugins. In conclusion, if the ROM you are building provides legacy gcc-4.9 toolchains (like LineageOS based projects), it should be safe to go ahead without installing GCC toolchains or Binutils. Otherwise, you need to install both Binutils and Clang packages in your computer to avoid build problems.
If you are using Ubuntu or Debian on your computer, please install the following packages (choose one way).
Using prebuilt toolchains in Android repo (recommend): sudo apt install libc6-dev libgcc-12-dev
Using toolchaings in your distribution: sudo apt install clang llvm-dev
For ROMs without legacy gcc-4.9 toolchains: sudo apt install binutils-aarch64-linux-gnu binutils-arm-linux-gnueabihf
Then you should be able to build the kernel without modifying build configs.
Build kernel image only: make bootimage
Build recovery image only: make recoveryimage
Apply custom changes (optional)

This is great. Is signature spoofing enabled? If not, could it be? MicroG users would like it. Ty.
Edit: signature spoofing is enabled, but It seems LineageOS 17 locked my bootloader.
Edit2: LineageOS 17 do not support custom partition tables. After flashing, my 2.3gb "system" goes to 1.8gb and there's no space left for NanoDroid and other mods.

Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?

rostopira said:
Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?
Click to expand...
Click to collapse
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.

WJXXBSH said:
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.
Click to expand...
Click to collapse
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)

rostopira said:
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)
Click to expand...
Click to collapse
It seems you're using lineage-17.0 roms, which needs more free space than 16.0 (eg. the APEX image).
Deleting the fonts that you never used is surely a way to get more space. If you have installed "Android System Webview" (com.google.android.webview) from play store or other origins, removing the prebuilt one from "/system/product/app/webview" should be another possible solution (get another 100MB). However, make sure to choose the new webview package in "Developer settings" and prevent factory reset unless flashing the rom again, or it might result in problems.

Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks

elna.nitz said:
Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks
Click to expand...
Click to collapse
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.

WJXXBSH said:
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.
Click to expand...
Click to collapse
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here (twrp from lollipop - nougat bootloader) I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.

elna.nitz said:
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.
Click to expand...
Click to collapse
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!

WJXXBSH said:
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!
Click to expand...
Click to collapse
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?

elna.nitz said:
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?
Click to expand...
Click to collapse
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".

WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?

elna.nitz said:
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?
Click to expand...
Click to collapse
Yes, if you want to unlock your device. A Mi account is needed to do this, on the latest MIUI version (if stable version "10.1.1.0" doesn't work, the develop version of MIUI is needed).

WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?

elna.nitz said:
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?
Click to expand...
Click to collapse
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).

WJXXBSH said:
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).
Click to expand...
Click to collapse
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?

elna.nitz said:
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?
Click to expand...
Click to collapse
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "◻".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download

WJXXBSH said:
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download
Click to expand...
Click to collapse
Finally I installed Weeb Gapps magisk Moudle, and The majority are fine.
There are 2 problems:
1. The device feels very lag in the opening of the apps and in the transition between them.
2. After restart takes the device nearly 2 minutes to find a cellular network

[RECOVERY] TWRP for Blackview A80Pro [UNOFFICIAL] [Android 10]

TWRP Recovery Project for the Blackview A80Pro Android 10
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Blackview A80Pro.​
I am not responsible for any bricked imei, when flashing TWRP backup the NVRAM partition to be safe, do not root until having an actually good working backup, if you signal goes restore your backup.
Click to expand...
Click to collapse
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_blackview_a80pro_eea/releases​Known Issues / Report Issues -https://github.com/DevZillion/android_device_blackview_a80pro_eea/issues​​
How to install​
[Magisk patched boot.img required to properly boot recovery.]
Bash:
fastboot flash recovery recovery.img
After booting into TWRP flash this zip and format data to remove internal storage encryption.
Click to expand...
Click to collapse
Sources​
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_blackview_a80pro_eea
Kernel Sources - The manufacturer refused to give them.
Click to expand...
Click to collapse
Special thanks to:​
TeamWin for the Recovery Project.
Blackview for their stock kernel with toggable SELinux wich does not follow GPL Licenses.
Zillion for doing the device tree.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.