Database Info

[Kernel] Diades Kernel for custom ROMs

Hello !
Currently i'm working in Le 2 kernel and device tree. My purpose is to make meaningful changes and additions so other ROMs can implement them.
Confirmed working with LOS, Carbon, LegendROM (latest releases)
This thread is all about the kernel. Currently the kernel features
sdcardfs support
cpu-input boost
power efficient work-queues
improvements to touchscreen driver, preparing support for dt2w
adj tree
low memory killer improvements
powersuspend driver
nvidia patches for energy efficiency
memory bus improvements
Adreno memory pools
and other small improvements in battery management and scheduler
Download: https://drive.google.com/open?id=0B4AOvCehd4v3OXBEX3dMSkdxQ3c
Source: https://github.com/mthomos/android_kernel_leeco_msm8976
To enable sdcardfs support just add this line in build.prop
Code:
ro.sys.sdcardfs=true
To be clear from the beginning: I will not answer to any feature requests and i respond to bug reports without logs. I hope to understand this
Cheers !
XDA:DevDB Information
Diades Kernel, Kernel for the LeEco Le 2
Contributors
marios199546
Kernel Special Features:
Version Information
Status: Testing
Created 2017-09-05
Last Updated 2017-09-07

What's the decryption key?

Good luck :good::good:

For which ROM?

Nice one.
Gonna try and report!

Its asking for decryption key!

OP updated with new link

Work on rom based in eui or only aosp rom ?
Sent from my Le X522 using XDA-Developers Legacy app

fmehdi said:
Work on rom based in eui or only aosp rom ?
Click to expand...
Click to collapse
Doesnt work on eui base
Only custom roms

What does sdcardfs mean?

bonsai.14 said:
What does sdcardfs mean?
Click to expand...
Click to collapse
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/

I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed

billybobjoe512 said:
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
Click to expand...
Click to collapse
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.

Njishi said:
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Click to expand...
Click to collapse
So where would I flash these .img files? Or do I have to do something else before flashing

billybobjoe512 said:
So where would I flash these .img files? Or do I have to do something else before flashing
Click to expand...
Click to collapse
What else you can do? Like going for a walk is recommended!?
You just have to boot into recovery. And then flash them like the way i said.
Or else you can use this app.
https://youtu.be/6IMvOCUy2Wc

You can also flash .img via fastboot with this command : fastboot flash boot <file_name.img>
Also if you have magisk installed you have to flash again the magisk install every time you install a new kernel.

I am a bit of a noob so I'm probably doing a ton of things wrong here
So how long does it take to start up the device after flashing the kernel? I flashed to boot partition and I waited for about 10 minutes and I got impatient so I restarted and tried to take a logcat but it just said waiting for device so I just restored a backup that I had made
Did I mess up somewhere or do I need to have a logcat for this

Phone don't boot bro I waite d 20 min

Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly

marios199546 said:
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
Click to expand...
Click to collapse
Phone not booting. Stuck at Spash screen. Cant take logs (waiting for device).

[GUIDE][PORT] How to install the Android Pie sGSI on your Xiaomi Mi A1

Code:
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this GSI and/or kernels. You do so at your own risk and take the responsibility upon yourself.
MOD EDIT: Remember to be prepared for an experimental or unstable ROM. If do you not know what you are doing or not experienced with flashing and recovering your data then it's not recommended.
REMEMBER TO BACKUP EVERYTHING AS THIS WILL REPARTITION YOUR USERDATA AND WILL WIPE YOUR INTERNAL STORAGE. ALSO, REMEMBER TO READ EVERYTHING AS ALL FIXES ARE POSTED BELOW. DON'T JUST FLASH THEN JOIN TELEGRAM TO ASK WHY THIS DOESN'T WORK FOR YOU.
READ THE IMPORTANT NOTES POSTED HERE​
TO REVERT TO NON-TREBLE/STOCK ROM, WATCH THIS VIDEO BY @GizmoFreak OR FOLLOW THIS POST
Here's everything I can provide to the normal user willing to try this out on their Mi A1.
PLEASE VISIT THIS NOTE TO SEE ALL THE REMAINING BUGS
OR JUST READ THEM HERE
SELinux is permissive
Hw key lights don't light up
Everything else works fine. Just need to update your Google Play services app and you can restore apps via Google Backup (if you didn't already do it with Titanium Backup). Yes, rooting with Magisk works and some modules work as well such as Blobmojis among others.
Here are the steps to install it in your Mi A1 if you're coming from stock ROM
Or watch a video made by @GizmoFreak
Enable Developer options in Settings app
Check Enable OEM Unlocking
Reboot to fastboot mode
Unlock your bootloader
Install TWRP-fastboot only through fastboot boot command (Extract the .img file from the zip)
Flash CosmicDan's TWRP Installer through your current TWRP. Credits to @CosmicDan for his TWRP and @mohancm for official TWRP sources.
Reboot to TWRP recovery
Go to WIPE then ADVANCED then click FORMAT data. This will remove Encryption on your device and allows you to set new passwords when installing the GSI. Note that this will format your internal storage.
Treblelize through TWRP Tissot Manager (Go to advanced, click Tissot Manager and choose the repartition userdata option. Select singleboot option then click repartition)
Flash latest Vendor.img as VENDOR IMAGE
Flash A/B system Pie PR2 img as SYSTEM IMAGE (Extract the .img file from the zip) (special thanks to @dgadelha for the sGSI)
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Flash a treble-compatible kernel (Moun, ProjectK,Velocity)(credits to @mountaser halak, @khusika, @kdragon)
Reboot to system.
Once booted, install the latest Play services linked above either via the Files app or via adb. This will fix the Pixel Setup and Google Backup issues as well as allows you access to the Play Store without problems.
You can now flash Magisk 17.3. This is the version that works properly with treble. Credits to @topjohnwu for Magisk.
Install the Data transfer tool APK update as well.
Special thanks to @erfanoabdi for porting the Pie A/B GSI.
Some features may seem to be broken but can actually be fixed with a few tweaks
USB MTP FIX
To enable USB MTP, enable Developer options in the About phone section of the Settings app by tapping the Build Number 4 times. Then look for the File Transfer option in the Dev options.
ENABLE NAV BAR GESTURES
To enable Nav Bar, I installed this nav bar enabler by @Hugwalk via Magisk.
After rebooting, go to Settings > System > Gesture and enable Swipe Up on Home Button to enable the Nav Bar Gestures.
SUBSTRATUM
Substratum is now much better for Pie.
Install the latest APK from this telegram channel and now all themes with Pie support can be installed.. Just reboot after building the themes and go into managers to enable the overlays you built.
Ethereal - https://play.google.com/store/apps/d...ethereal&hl=en
Outline - https://play.google.com/store/apps/d....outline&hl=en
Compound - https://play.google.com/store/apps/d...compound&hl=en
Sai's theme - https://t.me/tissotpsemigsi/33526
Click to expand...
Click to collapse
You should have the Android Pie booting on your Mi A1 now with less issues.
To update from PR1 to PR2, you can do so without wiping data
Wipe system ONLY
Flash PIE PR2 AB GSI
Reboot to system
Click to expand...
Click to collapse
To update your post post GSI zips, follow this
Wipe vendor ONLY
Flash vendor
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Reboot to system
Click to expand...
Click to collapse

Awesome work @joeyhuab bro ?

Edit:- Chrome sucks! Posted same thing twice.

Youtube not working for me(

Great job!!!i will wait to change to beta

Tornado95 said:
Youtube not working for me(
Click to expand...
Click to collapse
I also encounter YouTube issues. :/

Don't work the camera and black for me

ErickCartman17 said:
Don't work the camera and black for me
Click to expand...
Click to collapse
Try Footej Camera from Play Store please, it can be usefull if Footej or Open Camera works

waiting camera fix

cant mount system(invalid argument)
Failed to mount system after i try to flash GSI

I will wait for the stable...but is a good work... Thanks for try this.

andrexp31 said:
I will wait for the stable...but is a good work... Thanks for try this.
Click to expand...
Click to collapse
lol, then just wait for the official release. This is as close as we can get, for now since google hasn't uploaded the source code for P yet

I'm already looking into a fix for Camera. I'll post it once it's available.

What if I want to come back from Android Phone to another Custom ROM? Do I have to "un-treble" the device?

When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?

danilguy said:
When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?
Click to expand...
Click to collapse
Remove the spaces from the folder name and try... Works for me...

Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.

joeyhuab said:
Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.
Click to expand...
Click to collapse
U have don great work
Really well done
Waiting for camera, fingerprint and flash bugs fixed and i will surely test the rom

What about Bluetooth?

Chris_Cheekyz said:
What about Bluetooth?
Click to expand...
Click to collapse
Fixed as well together with Camera fix. Credits to Rupansh and @kdragon for using Whyred's blobs. Credits also to @ghpranav for BT fix.
Download

[ROM][UNOFFICIAL][Oreo 8.1] AOSP Extended for Mi Mix (lithium)

I was quite disappointed to find that my favourite ROM from my old phone was not available for the Mi Mix. So I took some time to research how to compile roms and built this for the community to enjoy.
Download AEX v5.8 here: https://www.androidfilehost.com/?w=files&flid=285169
EAS version with pepsy kernel: https://androidfilehost.com/?fid=1322778262904030327
Recommended TWRP here: http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
Sources:
https://github.com/AospExtended
https://github.com/PsyMan47/Pepsy-Kernel
https://github.com/PsyMan47/lithium
https://github.com/PsyMan47/msm8996-common
Requires global firmware 8.8.30. Nano Opengapps is recommended, but has Webview patches so you can install any version you like.
Everything works as it should, but unfortunately I'm no developer and won't be able to do feature requests or fix bugs. That being said, if and when the main AEX code base gets updated I will provide new builds. This was mainly a project for me to learn a bit more about Linux, Github and Android in general and I provide this with no guarantees of anything.
Big thanks to Psy_Man for his device tree that enabled me to build this.

Another great rom is revived!

New build with webview patches, you can now install whatever version of opengapps you like
https://www.androidfilehost.com/?fid=1322778262903988659

Inkypen said:
New build with webview patches, you can now install whatever version of opengapps you like
https://www.androidfilehost.com/?fid=1322778262903988659
Click to expand...
Click to collapse
Noice, thanks for your efforts.

Had anyone tried this?
Is everything working?
How is the battery life?

sexlord89 said:
Had anyone tried this?
Is everything working?
How is the battery life?
Click to expand...
Click to collapse
it's working good according to some users who've tried it.

New version up, last build had some random intermittent bugs. This new version uses the same kernel as the official SD821 aex roms, so everything works exactly like official version. This has on screen nav bar by default so no messing around with settings. Nano opengapps is recommended, but has webview patches you can install any version you like.
https://www.androidfilehost.com/?fid=1322778262903989778

Can anyone tell me DOES Magisk and SystemLess Xposed Work on this rom?

I use Magisk myself, works fine. I don't use Xposed so I have no idea

Wowwwwzer nice and smooth..so far so good !! Thanks ,!!!:??

TWRP Error code 7 happened...
Why it need MiUi to install?

00hobin said:
TWRP Error code 7 happened...
Why it need MiUi to install?
Click to expand...
Click to collapse
Hi there,
I don't understand your question "Why it need MiUi to install?".
But here's the suggestion, flash this twrp and try again : http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img

heindrix said:
Hi there,
I don't understand your question "Why it need MiUi to install?".
But here's the suggestion, flash this twrp and try again : http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
Click to expand...
Click to collapse
This time error code 6 happened. I attached log file

Error code 7 is assert error (device does not match) in installer script, usually down to incorrect TWRP version. Error 6 is some other error in installer script, unfortunately your attached recovery log is no longer available. Does your device have MIUI installed or you coming from a different ROM?

Inkypen said:
Error code 7 is assert error (device does not match) in installer script, usually down to incorrect TWRP version. Error 6 is some other error in installer script, unfortunately your attached recovery log is no longer available. Does your device have MIUI installed or you coming from a different ROM?
Click to expand...
Click to collapse
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI

00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
Coming from CrDroid Oreo and using latest twrp (the one by raupe and blunden which file name ends with updated or some such) you should have no trouble...

00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
It makes no sense, if you already have crdroid installed then all the messy parts of getting rid of MIUI has already been done. If you reinstall MIUI, then it automatically encrypts storage and you will have to format (not wipe) data to move to a different ROM.
Best thing I can suggest is to wipe (not format) everything apart from internal storage. Then reboot into recovery and then try to install the ROM. I suspect error 6 might have something to do with not being able to mount /vendor partition. Make sure you have the updated raupe+blunden TWRP, I believe the official version doesnt mount /vendor as well as having touch screen issues with some variants of mi mix.

00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash all files you want to flash -> Throw the phone as far as you can -> BOOM

Inkypen said:
It makes no sense, if you already have crdroid installed then all the messy parts of getting rid of MIUI has already been done. If you reinstall MIUI, then it automatically encrypts storage and you will have to format (not wipe) data to move to a different ROM.
Best thing I can suggest is to wipe (not format) everything apart from internal storage. Then reboot into recovery and then try to install the ROM. I suspect error 6 might have something to do with not being able to mount /vendor partition. Make sure you have the updated raupe+blunden TWRP, I believe the official version doesnt mount /vendor as well as having touch screen issues with some variants of mi mix.
Click to expand...
Click to collapse
Problem solved.

New version up with September security update: https://www.androidfilehost.com/?fid=1322778262903998959

[GUIDE] Havoc P and other P GSI with anykernel2 8.1 to P boot patch [temp]

First things first
1. Remove all pattern, fp, face data and BACKUP all Partition in TWRP ( I lost baseband trying GSI images, those backup saved me).
2. TWRP should be installed and also Force disabled Encryption should be flashed.
Now follow the steps
1. Go to TWRP, wipe dalvik/cache, cache, system, data
2. Go back and Flash HavocP system image as System or you can try other P GSIs..
HavocP-arm64_aonly_vanilla_nosu-0830.zip
( You can check the source here for updates).
Optionally you can flash arm64 Gapps 9.0 (nano or micro is recommended) opengapps.org
3. Next without exiting TWRP flash this zip, this one patches boot for Android P GSI image compatibility..
POST-sGSI_3_v0.5.zip
4. Now go to wipe menu and wipe Dalvik/cache, cache, data and reboot.
For audio distortion fix:
[Temp] How-To Fix Audio distorted on P GSIs
For Volte: not found any fix yet, but may be fixed by tweaking build.prop like some other devices.. Will add if found.
May this line be added in Vendor/bin/init.qcom.sh like One plus 3.
Code:
# Hack to get IMS up and running on GSI
if [ -f /data/system/users/0/settings_global.xml ]; then
sed -i 's/"multi_sim_data_call" value="1"/"multi_sim_data_call" value="-1"/g' /data/system/users/0/settings_global.xml
restorecon /data/system/users/0/settings_global.xml
fi
This thread is temporary.. Will close it if stable Havoc is released by the Devs
Credits- skulshady, zenixxx, erfanoabdi, EnesSastim, phhusson, SH1M4BD

Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!
EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized
Regards.

Please test multitouch issue, if it exists in this rom.

NexusPenguin said:
Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!
EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized
Regards.
Click to expand...
Click to collapse
1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.
In short, these GSIs are not stable.
shailendra1993 said:
Please test multitouch issue, if it exists in this rom.
Click to expand...
Click to collapse
Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..

palbadi said:
1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.
In short, these GSIs are not stable.
Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..
Click to expand...
Click to collapse
No, the multitouch bug, ghost touch is different.
Check this out: en.miui.com/forum.php?mod=viewthread&tid=3746297

palbadi said:
1.
In short, these GSIs are not stable.
Click to expand...
Click to collapse
Hi,
Same impression here : Treble needs a lot more work to deliver what Google is aiming at !
I now understand why some ROM devs do not want to release GSI ROM images
Regards.

If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.

Technical said:
If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.
Click to expand...
Click to collapse
It is due to mismatch of ro.vendor.build.fingerprint value in build.prop in System and Vendor..
FIX:
1. Connect data cable to PC and boot into twrp
2. Go to Advanced/file manager
3. Copy build.prop from both Vendor and System to Sdcard, so that you copy them to your PC and edit.
4. In PC, Copy those build.prop files from sdcard and change the value of ro.vendor.build.fingerprint from build.prop (system) to build.prop (vendor).
5. Now overwrite the edited build.prop (vendor) to Vendor in the same process and you may give permission 644 (rw-r--r--) that vendor/build.prop
6. Reboot and check

What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.
I don't see the point.

SmallTarzan said:
What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.
I don't see the point.
Click to expand...
Click to collapse
Havoc did not boot without that zip

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Introduction
This is an unofficial build of TWRP for Redmi Note 7 Pro (violet). Differences with the official one include:
- Supports CAF-based wrappedkey encryption (decryption) properly (tested with MIUI 10.3.5.0)
- Supports decrypting devices that have screen lock set up after Android 9 May update, which introduced a new key derivation function.
- Mounts the system partition at /system_root as per AOSP standards. This makes the auto-backup scripts (e.g. GApps / Magisk survival script) work properly during updates, and you no longer need any 'patch' to flash GApps / Magisk properly. However, this may break some existing ROMs. See below FAQ section for details.
- Appended DTBO to the recovery image so it doesn't depend on the dtbo partition. No standalone DTBO image required.
Flashing instructions
- Download and extract the img file
- Reboot to fastboot mode
- fastboot flash recovery whatever_img_file_you_extracted.img
- Reboot and press Volume + to enter recovery
- DO NOT try to run 'fastboot boot recovery.img', it won't work.
- DO NOT flash the fcrypt disabler if you use my recovery. There is no need to do so, and it is possible to mess stuff up if you don't know what you are doing.
- You have to format the data partition if and ONLY IF:
1) You were not encrypted, now going to an encrypted state, or vice-versa OR
2) You were on a ROM other than MIUI that does not support "wrappedkey" (ROMs would often state it supports wrappedkey if it does), now going to a ROM that supports it
Limitations
DO NOT boot this recovery with empty system and vendor partitions. It will fail to decrypt any data partition with empty /system and /vendor. DO NOT wipe system and vendor partitions without installing a new one before rebooting. I am working to remove this limitation.
Now works even with empty system and vendor partitions after 3.3.1-5. No need to worry about formatting system and vendor breaking TWRP any more.
The restore zip created by the Migrate app is NOT compatible with this recovery. It's a problem of the Migrate app, not this recovery. Please DO NOT try to flash the restore zip created by Migrate.
FAQ
- Q: Do I need any specific DTBO image to make this recovery working?
- A: Nope. It is appended to the recovery image so it will work with any DTBO.
- Q: What is wrappedkey?
- A: It's a different mode of FBE implemented in CAF, the Qualcomm branch of AOSP.
- Q: This cannot install ROM X, why?
- A: Because it mounts the system partition at /system_root, which is AOSP standard behavior for A-only system_as_root devices, but is broken in some custom ROMs currently (MIUI should work though). To make any ROM work again, they will need to include this commit from LineageOS Gerrit https://review.lineageos.org/c/LineageOS/android_build/+/247066
- Q: Decryption doesn't work with ROM X, why?
- A: Decryption should work for most ROMs based on the CAF branch (not AOSP). CAF ROMs (including official MIUI) use a different scheme for key storage, which is why TWRP hasn't supported it till now. I have ported the CAF encryption changes (wrappedkey) to TWRP, but unfortunately this will break ROMs that do not support the CAF wrappedkey mode of encryption. Here is a list of patches non-CAF ROMs need to support CAF-encrypted /data partitions https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged). If you confirm your ROM is CAF-based but the decryption still does not work, please open an issue on my GitHub repository which you could find below. (XDA threads are no good for issue tracking, sorry)
- Q: Why not contribute to the official TWRP?
- A: All the patches to the TWRP code base have been submitted to the official gerrit code review, though not merged yet, which you can see below.
Downloads
3.3.1-6: https://mega.nz/#!3QIRQYhK!Jq5QrGfJw5VCYZ8sq_BO1qNZecrFqlM9IB1IdSwogvI
changes: updated kernel to support pstore instead of /proc/last_kmsg. If you don't know what this is, it's probably not relevant to you.
Here you can find an unofficial LOS build with wrappedkey encryption and also proper system_as_root support for those survival scripts https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-lineageos-16-caf-encryption-t3933532. In addition, all official MIUI builds should flash just fine.
History versions:
3.3.1-5: https://mega.nz/#!nMowHKiL!zRvoTM0iIZKArmUDnZzaEFtXQv0_q7hIHUCmTHTOmOM
changes: 1) Now works even with empty /system and /vendor partition 2) Fixed brightness problem; 3) Enabled EDL Reboot
3.3.1-3: https://mega.nz/#!yAYXxAzZ!FNMYLzLphnSmJ-DbBx-OZUgxxYiftgn8e4Jn3kxiQik
Patches and sources
Patches for TWRP are available here:
https://gerrit.omnirom.org/#/c/34091/
https://gerrit.omnirom.org/#/c/34093/
https://gerrit.omnirom.org/#/c/34092/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34096/
Patches for ROMs to support wrapped key have been given in the above sections.
Source of the current device tree for TWRP: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp
Kernel source: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150, note that the device tree uses a prebuilt kernel image.
Contributors
PeterCxy, Dyneteve, merothh
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp

Now fixed and tested with MIUI.

PeterCxy said:
Now fixed and tested with MIUI.
Click to expand...
Click to collapse
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.

I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?

Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?

Can confirm this successfully decrypts storage, running xiaomi.eu on my phone. Thanks for your work.

Dwughjsd said:
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.
Click to expand...
Click to collapse
It did not decrypt MIUI 10.3.5.0 successfully due to magic (I missed some commits from qcom). It was fixed by pulling more commits in.

Jpwner said:
I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?
Click to expand...
Click to collapse
You won't need to erase userdata or flash fcrypt disabler anymore, if all the ROMs will update to support the wrappedkey encryption

Naveenthemi said:
Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?
Click to expand...
Click to collapse
just fastboot flash recovery whatever_you_downloaded_and_extracted.img

PeterCxy said:
just fastboot flash recovery whatever_you_downloaded_and_extracted.img
Click to expand...
Click to collapse
So it's possible for me to flash OTA Updates without encountering a bootloop and such?

Can someone please provide an alternate download link? The Mega link doesn't seem to work for me.
EDIT: Worked on a different device. Thanks.

Naveenthemi said:
So it's possible for me to flash OTA Updates without encountering a bootloop and such?
Click to expand...
Click to collapse
+1
Please answer

Good job! ?
I want you to know that your patch has been merged with the official one. I was away for a while so I hope you understand the little unfortunate delay.

In latest update can we flash any custom roms without any issue?

Yogendra Kher said:
In latest update can we flash any custom roms without any issue?
Click to expand...
Click to collapse
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in

PeterCxy said:
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in
Click to expand...
Click to collapse
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)

Naveenthemi said:
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)
Click to expand...
Click to collapse
Should work fine with MIUI. At least from what I have tested.

kushal.purkar said:
+1
Please answer
Click to expand...
Click to collapse
PeterCxy said it would as far as his testing had been done.

Gapps aroma not installing in this one as well. error 255

Can I flash Magisk and root my phone with this build.?
Do you have any Magisk zip file that will work.?
Thank you for your work