OrangeFox Features
* Unique design in Android Pie style
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* White Flashlight
* Password, torch, led
* Support for Miui and Custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Click to expand...
Click to collapse
About this build
Clean OrangeFox R10, without any tweaks and modifications.
Click to expand...
Click to collapse
Information
OrangeFox Version: R10
Build Date: 03-07-2019
Host: OrangeFox manifest
Click to expand...
Click to collapse
Issues
- Data decryption isn't working, use decryption patch.
Click to expand...
Click to collapse
Downloads
Stable builds: https://files.orangefox.website/OrangeFox-Stable/cereus
Beta builds: https://files.orangefox.website/OrangeFox-Beta/cereus
Click to expand...
Click to collapse
Source
Device Tree: https://github.com/MyCats/recovery_device_xiaomi_cereus
Click to expand...
Click to collapse
Cannot installed, it say the recovery.img size is bigger than size of recovery partition. But i think, the recovery.img size is still smallest than recovery partition size. because the size of recovery partition is 26MB. :silly:
M. Hisyam Kamil said:
Cannot installed, it say the recovery.img size is bigger than size of recovery partition. But i think, the recovery.img size is still smallest than recovery partition size. because the size of recovery partition is 26MB. :silly:
Click to expand...
Click to collapse
Hi, matter is in your recovery. I have uploaded image, install it via fastboot
MyCats said:
Hi, matter is in your recovery. I have uploaded image, install it via fastboot
Click to expand...
Click to collapse
Yeah, i have tryed it, and worked. Can enter orangefox as well.
Bug:
- Cannot decyrpt /data partition :crying:
- The Splash Screen of OrangeFox is nothing, just black screen
- Some lag after enter menu(cannot touch any button), just few second, and its normal again. Not big problem
- Mtp, maybe.(Not tested yet)
M. Hisyam Kamil said:
Yeah, i have tryed it, and worked. Can enter orangefox as well.
Bug:
- Cannot decyrpt /data partition :crying:
- The Splash Screen of OrangeFox is nothing, just black screen
- Some lag after enter menu(cannot touch any button), just few second, and its normal again. Not big problem
- Mtp, maybe.(Not tested yet)
Click to expand...
Click to collapse
Can you take some screenshots? Thanks in advance!
MyCats said:
Can you take some screenshots? Thanks in advance!
Click to expand...
Click to collapse
im has take some screenshot, but i think it cannot save to Internal Memory, because the /data partition still encyrpted. Wait, i will take some screenshot again, and save it to MicroSD
I will fix data decryption in tomorrow build. Thanks for report!
New build is up! (010719c)
- Changed devtree base
- Fixed data decryption
MyCats said:
Can you take some screenshots? Thanks in advance!
Click to expand...
Click to collapse
this is the screenshot of error decyrpting
MyCats said:
OrangeFox Features
About this build
Information
Downloads
Source
Click to expand...
Click to collapse
This is some screenshot of OrangeFox Recovery for Redmi 6 cereus device. :good::laugh:
MyCats said:
I will fix data decryption in tomorrow build. Thanks for report!
Click to expand...
Click to collapse
wow, okay. You are welcome :victory:
---------- Post added at 03:30 PM ---------- Previous post was at 03:28 PM ----------
MyCats said:
New build is up! (010719c)
- Changed devtree base
- Fixed data decryption
Click to expand...
Click to collapse
And yeah, now it fixed . Thanks bro :victory::victory::victory:
MyCats said:
New build is up! (010719c)
- Changed devtree base
- Fixed data decryption
Click to expand...
Click to collapse
Has been tested your build now, and still cannot decyrpt /data partition :crying:. Btw, thanks making a beautiful custom recovery for cereus device :fingers-crossed::victory:
M. Hisyam Kamil said:
still cannot decyrpt /data partition
Click to expand...
Click to collapse
I will include hardware decryption in next build, should fix it
Ooh! Thank you so much for this! Maybe we will have more success with custom ROMs? I've previously tested like 5 ROMs but I deleted them all. Now I have to download them again... Grrrr
MyCats said:
I will include hardware decryption in next build, should fix it
Click to expand...
Click to collapse
Ooh, okay2. I hope it can fixed
New build is up!
- Using system vold to fix decryption
- Added screen resolution override
- Synced with OrangeFox sources
Maybe it's time for going official. Can somebody make some recovery tests?
- OTA updating on MIUI
- FBE/FDE decryption
- Basic features (install, backup and others)
MyCats said:
Maybe it's time for going official. Can somebody make some recovery tests?
- OTA updating on MIUI
- FBE/FDE decryption
- Basic features (install, backup and others)
Click to expand...
Click to collapse
I thought it would be great if you joined our telegram group. All dev is in that group.
---------- Post added at 10:44 AM ---------- Previous post was at 10:44 AM ----------
MyCats said:
New build is up!
- Using system vold to fix decryption
- Added screen resolution override
- Synced with OrangeFox sources
Click to expand...
Click to collapse
wow :victory:, will test it again
MyCats said:
New build is up!
- Using system vold to fix decryption
- Added screen resolution override
- Synced with OrangeFox sources
Click to expand...
Click to collapse
Screen Splash is appears now, nothing black screen again. But still cannot decyrpt /data partition . Maybe, we can take some file from this twrp to fix decyrpt error https://forum.xda-developers.com/re...e-3-3-0-twrp-redmi-6-custom-recovery-t3926225 . Because this twrp, can decrypt /data partition. :silly:
M. Hisyam Kamil said:
Screen Splash is appears now, nothing black screen again. But still cannot decyrpt /data partition . Maybe, we can take some file from this twrp to fix decyrpt error https://forum.xda-developers.com/re...e-3-3-0-twrp-redmi-6-custom-recovery-t3926225 . Because this twrp, can decrypt /data partition. :silly:
Click to expand...
Click to collapse
Are you using MIUI Pie? Recovery kernel supports only Oreo FW.
Related
https://dl.twrp.me/s2/
allrockedout said:
https://dl.twrp.me/s2/twrp-3.2.0-0-s2.img.html
Click to expand...
Click to collapse
What are the changes, oh wait, can read here https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html :
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
Click to expand...
Click to collapse
Anyone tried yet?
Just try it after see this thread and notice that does not boot into recovery, stay in the screen with LeEco logo before it.
EDIT: Downloaded and flashed 3.1.1.1 and still does not boot into recovery... HELP!
EDIT2: Turn out the download from twrp app went bad and the files were corrupted, download it from PC and now its ok...
mdio said:
Just try it after see this thread and notice that does not boot into recovery, stay in the screen with LeEco logo before it.
EDIT: Downloaded and flashed 3.1.1.1 and still does not boot into recovery... HELP!
EDIT2: Turn out the download from twrp app went bad and the files were corrupted, download it from PC and now its ok...
Click to expand...
Click to collapse
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
jithin6g said:
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
Click to expand...
Click to collapse
I'm on le s3 working fine
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* 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)
Andy_04 said:
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* 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)
Click to expand...
Click to collapse
is only for snapdragon or mediatek also?
jithin6g said:
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
Click to expand...
Click to collapse
Did not try 3.2.1.0 yet, but 3.2.0.0 is running ok.
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Andy_04 said:
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* 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)
Click to expand...
Click to collapse
That is nice... but is there any Android 8 rom for S2 already???
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
EDIT: 3.2.1.0 Ok and running.
dziubson said:
is only for snapdragon or mediatek also?
Click to expand...
Click to collapse
This ist only for Snapdradon (the X52x Models)
---------- Post added at 06:16 AM ---------- Previous post was at 06:13 AM ----------
I installed it via TWRP app (RR-OS 5.8.5) on my X527 and it works very good
Does twrp 3.2.1 word on leeco le 2 x620 on eui 5.9.028s?
Andy_04 said:
This ist only for Snapdradon (the X52x Models)
Click to expand...
Click to collapse
Sukkel21 said:
Does twrp 3.2.1 word on leeco le 2 x620 on eui 5.9.028s?
Click to expand...
Click to collapse
If you can write, I assume you can read, can't you?
It doesn’t work on eui 5.9.028s I tried flashing no Luck, I tried booting without flashing didn’t work either. And when I try to boot into it it changes my oem unlocking from true to false so I don’t know how to install it.
Leeco le 2 pro
will this work on leeco le 2 pro X625?
JamBax said:
If you can write, I assume you can read, can't you?
Click to expand...
Click to collapse
VJkhaled18 said:
will this work on leeco le 2 pro X625?
Click to expand...
Click to collapse
Yes if it had a snapdragon cpu, but it has not, so no.
Too lazy to read some posts, shame on you.
i use latest twrp-3.2.1-0-s2 bit i can't encrypt my phone. i tested LOTS OF ROMS..... same bug, i press encrypt, the interface reboots but not enters into recovery or encrypting .... it simply does NOTHING.
Hello
I would like to get an accurate TUTO to be able to install the TWRP 3210 on my brand new S2, just arrived from CHINA.
I absolutely did not do anything on it, just charged the battery.
He is therefore naked of any manipulation.
Where can I find a very accurate TUTORIAL to avoid cassermon "LeEco Le2 X526"?
Thank you
PS after this manipulation, I guess I could install any ROM, LINEAGEOS or MOKEE ???
https://wiki.lineageos.org/devices/s2/install
Does anyone have problems with making a nandroid backup? I am on TWRP 3.2.1.0 witch is the newest one. It does the back up but is missing partitions. It shows boot,system,data only 64 mb. I know that's not true. I get the same outcome using a Miui ROM and a aosp 9.0 ROM. Any help would be appreciated thank you.
mbl1979 said:
Does anyone have problems with making a nandroid backup? I am on TWRP 3.2.1.0 witch is the newest one. It does the back up but is missing partitions. It shows boot,system,data only 64 mb. I know that's not true. I get the same outcome using a Miui ROM and a aosp 9.0 ROM. Any help would be appreciated thank you.
Click to expand...
Click to collapse
Use latest unofficial twrp by rk585 at AFH
MP_Singh said:
Use latest unofficial twrp by rk585 at AFH
Click to expand...
Click to collapse
Can I find his link here on xda?
New TWRP available for download. Still appears not to have MTP. From 3.2.1-0 you must flash the new installer.zip. Reboot TWRP and flash Magisk again
Installation instructions here:
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
@joemossjr has an unofficial TWRP that has MTP working available here: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
I can't find the changelog on twrp.me, do you know what they changed?
axmirza2 said:
I can't find the changelog on twrp.me, do you know what they changed?
Click to expand...
Click to collapse
Nope your guess is as good as mine other than the general 3.2.2-0:
Quoted from TWRP.me site: "TWRP 3.2.2-0 is out now for most currently supported devices.
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links."
lollyjay said:
New TWRP available for download. Still appears not to have MTP. I think you need to first boot the new image, and then from it you must flash the new installer.zip.
Click to expand...
Click to collapse
Thanks dude. Have you tested the MTP because the previous version I am not able to transfer anything from PC to the device.
Thanks.
Mulham82 said:
Thanks dude. Have you tested the MTP because the previous version I am not able to transfer anything from PC to the device.
Thanks.
Click to expand...
Click to collapse
As I stated in the OP, MTP appears not to be included.
lollyjay said:
As I stated in the OP, MTP appears not to be included.
Click to expand...
Click to collapse
I see. By the way, I have saw some guys are taking about GSI MIUI 10, so do you think that will be possible?!
Thanks.
lollyjay said:
Nope your guess is as good as mine other than the general 3.2.2-0:
Quoted from TWRP.me site: "TWRP 3.2.0-0 is out now for most currently supported devices.
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"
Click to expand...
Click to collapse
can you elaborate on the fstab support?
virtyx said:
can you elaborate on the fstab support?
Click to expand...
Click to collapse
Hi I am only quoting from the twrp.me site.
virtyx said:
can you elaborate on the fstab support?
Click to expand...
Click to collapse
That's the changelog from 3.2.0.0 as far a single can tell he only made a visiual change everything else is the same functionally ty wise
Mulham82 said:
Thanks dude. Have you tested the MTP because the previous version I am not able to transfer anything from PC to the device.
Thanks.
Click to expand...
Click to collapse
lollyjay said:
As I stated in the OP, MTP appears not to be included.
Click to expand...
Click to collapse
MTP still does not work.
iElvis said:
MTP still does not work.
Click to expand...
Click to collapse
That is what I wrote
lollyjay said:
That is what I wrote
Click to expand...
Click to collapse
Sorry, was replying to the other guy.
joemossjr said:
That's the changelog from 3.2.0.0 as far a single can tell he only made a visiual change everything else is the same functionally ty wise
Click to expand...
Click to collapse
I got excited for a second
not being able to edit the fstab because /vendor cant be edited is why we can't remove encrypt
virtyx said:
I got excited for a second
not being able to edit the fstab because /vendor cant be edited is why we can't remove encrypt
Click to expand...
Click to collapse
Not really. It's more of a verity issue once you make the change in will be reverted due to verity
They removed MTP because sometimes you would get a kernel panic when entering twrp (putting in your password would freeze twrp) but even without MTP TWRP gives me a kernel panic every now and then. I think MTP support should be added back in especially since we don't have a MicroSD slot.
ajsmsg78 said:
They removed MTP because sometimes you would get a kernel panic when entering twrp (putting in your password would freeze twrp) but even without MTP TWRP gives me a kernel panic every now and then. I think MTP support should be added back in especially since we don't have a MicroSD slot.
Click to expand...
Click to collapse
im not gonna deny that mtp is important but you also have the ability to to do adb push rom.zip /sdcard and it will transfer that way.
joemossjr said:
im not gonna deny that mtp is important but you also have the ability to to do adb push rom.zip /sdcard and it will transfer that way.
Click to expand...
Click to collapse
Sometimes when the phone doesn't boot and have to factory reset, MTP comes in handy to backup the internal storage.
so sad mtp still not there. (((
also, by installing "TWRP 3.2.2-0" in twrp I got constant reboot into twrp and was have to flash "[OFFICIAL]OxygenOS.OTA" and root, xposed, custom recovery
oneplus6 is still highly unstable,
thanks to Oneplus and Google for poor work.
because of it nexus6 is still my primary phone and oneplus6 just as a second toy ((
joemossjr said:
im not gonna deny that mtp is important but you also have the ability to to do adb push rom.zip /sdcard and it will transfer that way.
Click to expand...
Click to collapse
I hear you but it's good for those times where you flash something then reboot then you end up in a bootloop and forgot to back up a few files before you rebooted. Having MTP in TWRP saves you in that case and it's a nice feature to have.
Does aroma work now?
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.
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 InstructionsI 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
Changelogstwrp-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
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
Hello, this is a test build for coral users (will work on crosshatch/blueline later).
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
- allow repacking of TWRP from boot.img
- magisk not working currently on repacked image
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
- fix repacking magisk with TWRP
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_twrp_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
Glad to see this!
Finally TWRPified! Thanks for bringing this to us!
bigbiff said:
[RECOVERY] TWRP 3.4.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me
Click to expand...
Click to collapse
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Daisymae said:
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Click to expand...
Click to collapse
Same here ?
I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:
I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001
Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw
If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Surge1223 said:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Click to expand...
Click to collapse
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
bigbiff said:
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
Click to expand...
Click to collapse
Sure, no problem. logs attached
Surge1223 said:
Sure, no problem. logs attached
Click to expand...
Click to collapse
Thanks, did you try test2?
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
Boggling my mind that it works on my coral with out linking issues.
Can you post the results of getprop please?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
bigbiff said:
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
Click to expand...
Click to collapse
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
Click to expand...
Click to collapse
Wait did you want getprop while in recovery or booted?
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Wait did you want getprop while in recovery or booted?
Click to expand...
Click to collapse
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
bigbiff said:
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
Click to expand...
Click to collapse
heres getprop
https://hastebin.com/eluqagolub.md
heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl
Got some $$ coming your way Monday OP.
Thank you for this. It could not have been easy
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
dhacke said:
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
Click to expand...
Click to collapse
No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.