Database Info

[Recovery][TWRP][OFFICIAL] for Mi A2 (jasmine_sprout)

Team's Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Cautious :-
Quote:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
What's new in 3.2.1-1:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
What's new in 3.2.0-0:
* Allow restoring adb backups in the TWRP GUI (bigbiff)
* Fix gzip backup error in adb backups (bigbiff)
* Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
* Better support for installing Android 8.0 based zips due to legacy props (nkk71)
* Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
* Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
* Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
* v2 fstab support (Dees_Troy)
* Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
* Various other minor bugfixes and tweaks
What's new in 3.3.0-0:
(Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Code:
/*
Whats Working?
All paritions are mounting.
Can change Slot A/Slot B on twrp.
Add system_image mount point to flash system images.
Fixed MTP and OTG issues.
Fixed JDI Pannels issue on pie
Added Pie Support.
Fixed Pie permanent twrp.
Added Pie decryption support. (thanks to @[URL="https://4pda.ru/forum/index.php?showuser=6362530"]d4e8ede8f1f2[/URL])
Added Splash img support.
*/
Code:
Flashing Commands:
fastboot boot recovery.img
Downloads :TeamWin
Status : OFFICIAL
Created 2018-11-02
Last Updated 2019-06-24

Another recovery ?
Hi Folk,
We got 4 available recovery as far as now but 100% get buggy for now.
I see many thanks : do someone have tested this Recovery for Mi A2 ? Do it can flash LOS on both slot A and B without failed ?
Thank for your enlightenment.

? Mumu said:
Hi Folk,
I see many thanks : do someone have tested this....
Click to expand...
Click to collapse
I have backed up and restored with this. It works well. Have not flashed any roms though.

I updated my phone to the November beta and could not boot into this twrp as it did not recognize the device was encrypted. The temporary twrp from TingyiChen did work however. Had to wipe and install the October version to get everything back to normal. Will wait for the official release to test some more. Just a heads up to be aware that the next os update might cause some complications.

@Manish4586
I can confirm the latest security update breaks encryption detection by this twrp version. I just updated to the official ota for November and twrp loads but does not ask for the decryption pattern and thus the drive is not decrypted.

And, it seems in a near future that TWRP will be official to Mi A2 - https://github.com/TeamWin/android_device_xiaomi_jasmine
If you take a look at this repo, it's forked from the one that is the unofficial and linked on this thread.

It works well but It has encryption issue. I have a fix for this issue:
-find /vendor/etc/fstab.qcom file and replace line 10:
"
Code:
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,resize,slotselect,verify
"
-reboot fastboot mode and run it:
"fastboot -w"

parduscix said:
It works well but It has encryption issue. I have a fix for this issue:
-find /vendor/etc/fstab.qcom file and replace line 10:
""
-reboot fastboot mode and run it:
"fastboot -w"
Click to expand...
Click to collapse
This format userdata and others partitions
Totally useless.
Same of format data using TWRP

How to flash twrp I'm going in miA2. I have tried but failed no command show

razahaider03 said:
How to flash twrp I'm going in miA2. I have tried but failed no command show
Click to expand...
Click to collapse
unlock bootloader, then boot to fastboot and boot the recovery

Ironmaniaco said:
And, it seems in a near future that TWRP will be official to Mi A2 - https://github.com/TeamWin/android_device_xiaomi_jasmine
If you take a look at this repo, it's forked from the one that is the unofficial and linked on this thread.
Click to expand...
Click to collapse
It's official now.

Manish4586 said:
Flashing Commands:
fastboot boot recovery.img
flash twrp-flasher-xxx.zip from twrp
Click to expand...
Click to collapse
Where do I download the twrp-flasher zip? I only found the .img in the website. Or is fastboot recommended?
Thanks.

Now we have TWRP fixed on smartphone?
Or we have to flash TWRP after flash every ROM?

Thx man. Its working.
I booted into twrp and then flashed the installer zip which is i took from your sourceforge account.
Now im able to boot into recovery without fastboot. ??

satti8893 said:
Thx man. Its working.
I booted into twrp and then flashed the installer zip which is i took from your sourceforge account.
Now im able to boot into recovery without fastboot. ??
Click to expand...
Click to collapse
Have a nice day

jaycedam said:
Where do I download the twrp-flasher zip? I only found the .img in the website. Or is fastboot recommended?
Thanks.
Click to expand...
Click to collapse
It will be available on twrp download soon.

tsulolxd said:
Now we have TWRP fixed on smartphone?
Or we have to flash TWRP after flash every ROM?
Click to expand...
Click to collapse
We have to flash twrp.zip

Manish4586 said:
We have to flash twrp.zip
Click to expand...
Click to collapse
Where do I find this zip? It's working on Android Pie?

Hi Manish4586, I'm in PBRP and Pixel Experience right now, how to change to TWRP OFFICIAL for Mi A2? I try from fastboot it didn't work, plase help.

I installed the zip via sideload, it's ok or do I have to flash the img?

[rom][treble][9.0][huawei p9]

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
Requiriments:
Stock EMUI 8.0
STOCK RECOVERY_RAMDISK
STOCK RAMDISK
THIS ROM WORKS WITH HI3650 DEVICES AND HI6250 DEVICES (WITH TREBLE)
Working:
*All* *Apart Camera*
FLASH LKT IN MAGISK FOR FIX UI MICRO-LAGS
Bugs:
Camera (Working on it)
When the rom boot shows a error but nothing important (For now no)
Installation:
Flash Stock EMUI 8.0
Don't setup anything
Flash stock ramdisk
Now flash this twrp: https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
Select English language
Go to Wipe-Advanced Wipe-And wipe only system
Now copy the rom to SD CARD OR Internal Storage
Flash the rom
NOW FLASH STOCK RECOVERY_RAMDISK (VERY IMPORTANT)
Reboot to Emui recovery
Wipe cache
Wipe data (if the recovery fails its normal)
Now reboot to system
Setup what do you want
----------------------------------------------------------------------GAPPS---------------------------------------------------------------------------------
FIXED:MAKE SURE THE ROM BOOTED
NOW DOWNLOAD THE NANO PACKAGE OF GAPPS
REBOOT TO MY TWRP : https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
FLASH GAPPS
IF TWRP SAYS UNABLE TO MOUNT SYSTEM ITS NORMAL JUST REBOOT
ENJOY GOOGLE APPS
Link: https://opengapps.org/
Select arm64 9.0 nano
---------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------LINKS-----------------------------------------------------------------------------------
Rom:
MEGA: https://mega.nz/#!MRthiAhJ!nxDU4O1rxEoLoYo1r_n0gaZodwKB4KAcV25mej7gh_g
GOOGLE DRIVE: https://drive.google.com/open?id=111OfwRDG09uAbG-RPDv8xijt9JxVdeB9
---------------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------Magisk-------------------------------------------------------------------------------------
DON'T FLASH NORMAL MAGISK BECAUSE CAUSES BOOTLOOP
FLASH IANMACD MAGISK
MEGA: https://mega.nz/#!oEdjHaRB!MdqyZvgk4lvkkfOOVk16vEeqAH5Uc7v_fjzVvSoXEk8
IF AFTER INSTALLATION YOU SEE UNABLE TO MOUNT SYSTEM OR SOMETHING LIKE THIS IS NORMAL
IF AFTER INSTALLATION AND REBOOTED TO SYSTEM YOU DON'T SEE MAGISK MANAGER IS NORMAL JUST REBOOT TO RECOVERY AND
FLASH IT AGAIN
---------------------------------------------------------------------------------------------------------------------------------------------------------------
I HAVE UPLOADED SCREENSHOTS
--------------------------------------------------------------------------Credits-------------------------------------------------------------------------------------------
@Tecalote 
 @korom42
 @ianmacd
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
LineageOS 16, ROM for the Huawei P9
Contributors
sasi2006166
ROM OS Version: 9.x Pie
Version Information
Status: Beta
Created 2019-01-20
Last Updated 2019-01-20

ScreenShots:
https://imgur.com/a/bhUJe1y

Deleted
Post #2 for screenshots

sasi2006166 said:
...
Requiriments:
Stock EMUI 8.0
...
THIS ROM WORKS WITH HI3650 DEVICES AND HI6250 DEVICES (WITH TREBLE)
...
Installation:
Flash Stock EMUI 8.0
...
Now flash this twrp: https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
...
Now copy the rom to SD CARD OR Internal Storage
Flash the rom
....
REBOOT TO MY TWRP : https://mega.nz/#!xUcBxKLZ!MJv5xk86GAJOEKl1KRS-tKr5wvkBFTOI0DgosaEUkXA
...
LineageOS 16, ROM for the Huawei P9
...
Click to expand...
Click to collapse
Is this TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img your port of TWRP, and is it based on TWRP 3.1.1 or newer?
When you say it is for P9 EVA with stock EMUI 8.0.0, does it mean that this TWRP works with EVA-AL10c00b535 as obtained by rebranding P9 L09/L19 with HWOTA7 method
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
By its name, Decryption Supported, does it really mean that this TWRP can access Internal memory and Data partition under P9 stock Oreo?
Btw, Huawei P9, EVA, comes with HiSilicon Kirin 955, but you refer above HI3650 and HI6250 - so is this TWRP really for Huawei P9 EVA with stock Oreo (EMUI 8.0.0)?

This TWRP from China does not have decryption support
@zgfg to answer some of your questions:
1) "MY TWRP" - which is mentioned in OP is not correct because it is a TWRP from China - that means it is not developed by @sasi2006166
2) You can not flash this TWRP because the name contains a space: TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img - if you want to test, you must first rename it.
3) This TWRP does not have decryption support. Decryption support means that it would be possible to access the encrypted internal storage without the need to format data. This is not the case, the internal memory has 0 MB and no content.
4) This TWRP has version 3.2.1.0 and it's not that bad - but it has bugs. I tested it a few months ago, in October 2018. I tested all features and found that partitions recovery is not working properly
→ For this reason, I have to say that the TWRP developed by @Pretoriano80 which we use, is much better. Everything works, except that it does also not have access to the encrypted internal storage: https://androidfilehost.com/?fid=1322778262903998750
→ But we would not say it has decryption support, when it is not the case.
5) Huawei P9 HiSilicon Hi3650 (Kirin 950/955/) is correct.

Tecalote said:
1) "MY TWRP" - which is mentioned in OP is not correct because it is a TWRP from China - that means it is not developed by @sasi2006166
2) You can not flash this TWRP because the name contains a space: TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img - if you want to test, you must first rename it.
3) This TWRP does not have decryption support. Decryption support means that it would be possible to access the encrypted internal storage without the need to format data. This is not the case, the internal memory has 0 MB and no content.
4) This TWRP has version 3.2.1.0 and it's not that bad - but it has bugs. I tested it a few months ago, in October 2018. I tested all features and found that partitions recovery is not working properly
→ For this reason, I have to say that the TWRP developed by @Pretoriano80 which we use, is much better. Everything works, except that it does also not have access to the encrypted internal storage: https://androidfilehost.com/?fid=1322778262903998750
→ But we would not say it has decryption support, when it is not the case.
5) Huawei P9 HiSilicon Hi3650 (Kirin 950/955/) is correct.
Click to expand...
Click to collapse
Thanks for testing and elaborating.
I tried also now this TWRP (it says developed by www.7to.cn) and indeed it cannot read Internal memory, neither Data partition (showing both as empty).
Hence the claim about installing LOS ROM from External SD or Internal memory (post #1 above) is wrong, this TWRP also can only read (and install something) from External SD, not from Internal memory
Btw, this TWRP is based on 3.2.1.0, just like TWRP from Pretoriano80, but this one has non-standard, more colourful UI
(Didn't test does it correctly support recovery ramdisk partition)
PS: OpenKirin ROMs should be flashed by Fastboot, not from TWRP (it doesn't work from TWRP, even when TWRP finds OK ROM img on External SD)
I'm also wondering is this really here a new Treble LOS ROM, or just the one from OpenKirin team (for which other users also reported some problems with camera upon rebooting or so)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/

Great work and thank you .hope the bugs will be fixed soon!

The TWRP is ONLY for Huawei p9
The rom is a fleshable zip
This ROM supports hi6250 and hi3650 devices
The twrp is modified by me for working decryption
For working decryption you have to follow the instructions for installing the rom

Tecalote said:
@zgfg to answer some of your questions:
1) "MY TWRP" - which is mentioned in OP is not correct because it is a TWRP from China - that means it is not developed by @sasi2006166
2) You can not flash this TWRP because the name contains a space: TWRP-8.0.0-EVA-DECRYPTION SUPPORT.img - if you want to test, you must first rename it.
3) This TWRP does not have decryption support. Decryption support means that it would be possible to access the encrypted internal storage without the need to format data. This is not the case, the internal memory has 0 MB and no content.
4) This TWRP has version 3.2.1.0 and it's not that bad - but it has bugs. I tested it a few months ago, in October 2018. I tested all features and found that partitions recovery is not working properly
→ For this reason, I have to say that the TWRP developed by @Pretoriano80 which we use, is much better. Everything works, except that it does also not have access to the encrypted internal storage: https://androidfilehost.com/?fid=1322778262903998750
→ But we would not say it has decryption support, when it is not the case.
5) Huawei P9 HiSilicon Hi3650 (Kirin 950/955/) is correct.
Click to expand...
Click to collapse
Don't use Pretoriano TWRP it causes bootloop
This twrp works very well
And the decryption works

sasi2006166 said:
The TWRP is ONLY for Huawei p9
The rom is a fleshable zip
This ROM supports hi6250 and hi3650 devices
The twrp is modified by me for working decryption
For working decryption you have to follow the instructions for installing the rom
Click to expand...
Click to collapse
Maybe you uploaded the not modified TWRP?
Because it's absolutely the same TWRP which I tested in October 2018 for P9.
It has absolutely the same md5 checksum as the one you have uploaded.
If it would be modified, the md5 checksum would be different.
On EMUI Decryption is not working. I tested it yesterday and @zgfg too.
For this reason I can't imagine that decryption would work after flashing your Rom.
When you say "copy Rom to the internal storage" - we couldn't do this with this TWRP, because it is not accessible.
What's your understanding of "Decryption is working"?
If you mean in your Install Guide to format data (instead of wipe data) then data would be decrypted.
But this is not the sence of "working decryption" and can also be done with TWRP by Pretoriano.

Tecalote said:
Maybe you uploaded the not modified TWRP?
Because it's absolutely the same TWRP which I tested in October 2018 for P9.
It has absolutely the same md5 checksum as the one you have uploaded.
If it would be modified, the md5 checksum would be different.
On EMUI Decryption is not working. I tested it yesterday and @zgfg too.
For this reason I can't imagine that decryption would work after flashing your Rom.
When you say "copy Rom to the internal storage" - we couldn't do this with this TWRP, because it is not accessible.
What's your understanding of "Decryption is working"?
If you mean in your Install Guide to format data (instead of wipe data) then data would be decrypted.
But this is not the sence of "working decryption" and can also be done with TWRP by Pretoriano.
Click to expand...
Click to collapse
I'm my case the decryption works
You need to go to advanced fix decryption

sasi2006166 said:
I'm my case the decryption works
You need to go to advanced fix decryption
Click to expand...
Click to collapse
That Advanced Fix for decryption works only for Lineage or also for stock Oreo?

zgfg said:
That Advanced Fix for decryption works only for Lineage or also for stock Oreo?
Click to expand...
Click to collapse
In lineage works
I haven't tried on oreo
Whatever I need help for fixing camera
On hi6250 the camera works
Oy on hi3650 series doesnt work

For Working decryption on LineageOS 16
Flash the Chinese TWRP in fastboot
Reboot to recovery
Go to wipe advanced wipe and wipe ONLY system
Now go to wipe and select FORMAT DATA and type YES
Now flash ONLY the rom (no google apps or anything)
When the rom is flashed reboot to fastboot
Flash stock emui recovery
Reboot to emui recovery
DO first wipe cache, then wipe data
Now boot the rom
Setup what do you want
Now reboot to fastboot
Flash the Chinese TWRP
Now flash gapps (see the decryption in working)
Flash magisk (read OP #1)
Reboot to system
Enjoy

@zgfg Fix decryption alone does not work on EMUI (because I have tested too in October 2018) - EMUI doesn't work properly if data is formatted and @sasi2006166 it works on Lineage only because of FORMAT data - don't know if combination with Fix decryption is necessary.

Tecalote said:
If you mean in your Install Guide to format data (instead of wipe data) then data would be decrypted.
Click to expand...
Click to collapse
sasi2006166 said:
Flash the Chinese TWRP in fastboot
Reboot to recovery
Go to wipe advanced wipe and wipe ONLY system
Now go to wipe and select FORMAT DATA and type YES
Now flash ONLY the rom (no google apps or anything)
When the rom is flashed reboot to fastboot
Flash stock emui recovery
Reboot to emui recovery
DO first wipe cache, then wipe data
Now boot the rom
Setup what do you want
Now reboot to fastboot
Flash the Chinese TWRP
Now flash gapps (see the decryption in working)
Flash magisk (read OP #1)
Reboot to system
Enjoy
Click to expand...
Click to collapse
In this guide you never use Advanced Decryption fix option from TWRP?
Also, once you do Format Data then Encryption is gone, isn't it - as @Tecalote previously commented
For camera - did you try / look into OpenKirin LOS, RR or Omni Pie, they have integrated GApps and camera, but they don't provide source code for their Treble ROMs

I have tried with emui 8 stock camera
And also with openkirin omnipie camera but nothing

sasi2006166 said:
I have tried with emui 8 stock camera
And also with openkirin omnipie camera but nothing
Click to expand...
Click to collapse
You can try this, User tested it also on P9 and told it would work.
https://forum.xda-developers.com/p10/themes/google-camera-kirin-t3771927

could someone test this? https://forum.xda-developers.com/pr...opment/kirin-huawei-camera-android-p-t3840110
and does 4g lte work?

kristiansja said:
could someone test this? https://forum.xda-developers.com/pr...opment/kirin-huawei-camera-android-p-t3840110
and does 4g lte work?
Click to expand...
Click to collapse
So far I understand @sasi2006166 has already tried this camera and it does not work.
LTE I don't know, because I haven't currently not tested the Rom

[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

[A/B][TREBLE][9.0][A530F/A530W/A730F]SaR patch and kernel for Pie Vendor

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 patch
* 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.
*/
INFO:
This is a patch and SaR kernel made for @prashantp01's Vendor Dumpster V1.1.
SaR (System as Root) means the system partition is mounted as the root filesystem.
This allows our phone to boot System-as-Root (also labelled as A/B) GSIs which are the only type of GSIs still supported officially by Google.
There are two types of boot images I'm providing:
Android 9 style ramdiskless SaR
Android 10 style 2-stage init SaR
In general, you should use the Android 9 version for Android 9 based GSIs, and use whichever you want for Android 10 or newer.
The kernel is a modified version of @prashantp01's Quantum Kernel v4.0.
Source code for it is available here: github.com/VDavid003/universal7885_SaR
If you are used to using PHH-Magisk, now you don't have to: you can use normal Magisk on A/B GSIs, but
NOTE:Magisk currently doesn't work on Android R! (20.4, newer ones may work in the future)
NOTE:The patch and kernel are currently not tested on A530W and A730F. Please tell me if it works or not!
BUGS:
-Basically every bug that is present in the original Vendor Dumpster V1.1
-Secure lock screen can't be set (no pattern/pin/password unlock)
-Seems like Android 11 Developer Preview 2 and later does not currently work. DP1 works fine tho, you can download it here.
INSTALL INSTRUCTIONS:
Follow the instructions to install Vendor Dumpster V1.1.
Flash the SaR Patcher zip from TWRP(this will still let you boot non-SaR GSIs, but it will make the vendor compatible with SaR GSI)
Install a SaR boot.img (P or Q) for your model. (TWRP -> Install -> Install Image -> Select your boot.img -> Select Boot from the list -> Swipe to flash)
Flash an A/B or SaR GSI as you would do normally.
DOWNLOADS:
The root folder contains the vendor patcher zip, and the boot.img folder contains boot.imgs
Naming scheme for them: boot_[MODEL]_[P/Q].img
DOWNLOAD HERE
SPECIAL THANKS:
@prashantp01 for his vendor and kernel. Go support him!
Everyone involved in his vendor/kernel.

CHANGELOG
1.0:
-Initial release with some stuff accidentally left out
1.1:
-Fixed RIL (temporary fix currently), and enabled the media codec fix I forgot to enable in 1.0

I'm assuming it's for A/B only and won't work for A-only devices?

lanadelreywhore said:
I'm assuming it's for A/B only and won't work for A-only devices?
Click to expand...
Click to collapse
Since A530F is a A-only device i assume it works for both, OP correct me if i'm mistaken
Looking forward to test this after the Lock bug is fixed, that's kinda a daily must for me

lanadelreywhore said:
I'm assuming it's for A/B only and won't work for A-only devices?
Click to expand...
Click to collapse
OverLineMusic said:
Since A530F is a A-only device i assume it works for both, OP correct me if i'm mistaken
Looking forward to test this after the Lock bug is fixed, that's kinda a daily must for me
Click to expand...
Click to collapse
The patch shouldn't break aonly GSIs but it should allow an A/B(that's actually the wrong name but it's called that because of historic purposes) GSI to boot IF you install a SaR boot.img thus converting your phone to SaR. After installing a SaR boot.img you can't boot Aonly GSIs until you flash an Aonly boot.img again (by installing the regular quantum kernel for example)

VDavid003 said:
The patch shouldn't break aonly GSIs but it should allow an A/B(that's actually the wrong name but it's called that because of historic purposes) GSI to boot IF you install a SaR boot.img thus converting your phone to SaR. After installing a SaR boot.img you can't boot Aonly GSIs until you flash an Aonly boot.img again (by installing the regular quantum kernel for example)
Click to expand...
Click to collapse
Yeah I finally understood that a few days ago but I guess cause of my a8 being a530W model it's not working cause I do all the steps as instructed and when I try to boot it bootloops on splash screen. Will reboot every 3-4 seconds or straight to download mode. Tried a handful of different a/b gsi and no luck. Only a preview of Android 11 booted actually

lanadelreywhore said:
Yeah I finally understood that a few days ago but I guess cause of my a8 being a530W model it's not working cause I do all the steps as instructed and when I try to boot it bootloops on splash screen. Will reboot every 3-4 seconds or straight to download mode. Tried a handful of different a/b gsi and no luck. Only a preview of Android 11 booted actually
Click to expand...
Click to collapse
Huh, weird.
Have you tried the pie boot.img?
If that doesn't work, can you provide logs? (from /proc/last_kmsg)
I'd be interested in what might be the problem, since I can actually boot my a530f with the a530w kernel and it works.

My A530F is now up and running the descendatx a/b GSI. Great Work thanks

Hllo,
I want to ask about GSI FiX Boot.zip comes from prashantp01
Do I need to flash it ? Or just go straightforward as described instruction from OP ?
Sent from my SM-A530F using Tapatalk

hi.. i don't understand why there is boot_a530f_P_and_Q.img . do i have to install boot_a530f_Q.img when i install GSI android Q? can i install GSI android Q or above just by installing boot_a530f_P.img.. basically my device is android P..

suh4rji said:
hi.. i don't understand why there is boot_a530f_P_and_Q.img . do i have to install boot_a530f_Q.img when i install GSI android Q? can i install GSI android Q or above just by installing boot_a530f_P.img.. basically my device is android P..
Click to expand...
Click to collapse
Yeah very curious to know Aswell