{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 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!
DOWNLOAD:
https://www.androidfilehost.com/?fid=1322778262903997138
Alternative link
https://drive.google.com/open?id=10-Mham_-4CFllgVWPS-QGTG5jcf9lwgH
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Code:
Fastboot Flashing Code
Code:
Fastboot boot Twrp.img
Flash the recovery img again inside twrp and reboot to recovery again and it will stay.
If u are new to twrp, format data in twrp and reboot to recovery again and flash this file https://androidfilehost.com/?fid=3700668719832238534 after that u can flash the rom.
If u have already twrp installed, just flash the img in twrp
BUGS:
Nothing, if u find anything contact me
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce
Source Code: https://github.com/omnirom/android_bootable_recovery/
Thanks to geoleonsh for the device tree.
Version Information:
Status: Stable
Created 3-9-2018
Last Updated 3-9-2018
Update 3-9-2018
Fixed vibration
Set standard language to English
bassbounce said:
Reserved
Click to expand...
Click to collapse
custom rom is coming. . .
Wait for unlock bootloader and test
Installed, it works ok, but atm i've not flashed anything....
Starts in chinese language.... not in english.
Maybe is better to enable english as default language, chinese is very difficult to parse and to find a way to set another language.
This build is different from [LR.Team] (wzsx150) TWRP-3.2.3-0806 Version, because this build use official MI 8 Kernel?
I give thanks as a future Mi 8 user
gulp79 said:
Installed, it works ok, but atm i've not flashed anything....
Starts in chinese language.... not in english.
Maybe is better to enable english as default language, chinese is very difficult to parse and to find a way to set another language.
This build is different from [LR.Team] (wzsx150) TWRP-3.2.3-0806 Version, because this build use official MI 8 Kernel?
Click to expand...
Click to collapse
Thanks, I will look in that!
It was English by default when testing but I used also some files from a Chinese tree.
Edit:
Problem found i will re-upload a new img with English language set on default.
Thanks,
Is it different in any way compared to the latest L.R Team version?
drms12 said:
Thanks,
Is it different in any way compared to the latest L.R Team version?
Click to expand...
Click to collapse
No, this is just the stock twrp with the normal additional language's.
Thank you very much.
Thanks for your efforts.
Awaiting the developers to enjoy new custom roms
Thanks man
ultrarain said:
custom rom is coming. . .
Click to expand...
Click to collapse
what you mean?
you do not say anything in which you have improved it, it works with the global beta miu10 and it is not overwritten returned original recovery? Does magisk work without bootlops?
destroymen said:
you do not say anything in which you have improved it, it works with the global beta miu10 and it is not overwritten returned original recovery? Does magisk work without bootlops?
Click to expand...
Click to collapse
It works great with magisk 17.0 and with miui 10, always flash the img of Twrp after u flash global rom or Chinese rom just to be sure.
There is nothing to improve when it already works great.
If u like some mods in the recovery u can try to compile Redwolf recovery.
Keep bootlooping for me after installing Magisk 17.1
Its working great with the latest xiaomi.eu rom and magisk 17
No bootloop for me either.
I use the latest magisk 17.1.
Treble gsi is also working with magisk 17.1 without a. Bootloop.
If u bootloop follow the guides and informations on this forum.
It isn't related to this recovery.
bassbounce said:
No bootloop for me either.
I use the latest magisk 17.1.
Treble gsi is also working with magisk 17.1 without a. Bootloop.
If u bootloop follow the guides and informations on this forum.
It isn't related to this recovery.
Click to expand...
Click to collapse
Can you give me any tutorial to flasg magisk on global stable or global beta rom?
I flashed the twrp, booted into it, rebooted into twrp again, then system, and the stock recovery still as default and can't boot into twrp, what should I do?
Related
TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEATURES
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16
Nice work!
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!
aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.
modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...
works perferct! thank you :good:
I got an XZ1. Any chance to get TWRP for it (for testing)?
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it
modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...
it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.
Question just to be clear: do we have to update twrp for evry new securitypatch?
To decrypt the /data partion on a stock ROM, yes you do.
Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham
UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp
Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!
@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?
You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.
Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?
mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks
Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!
Thank you
Sent from my Redmi Note 9 Pro using Tapatalk
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222
Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
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. You can also view the Changelog for a full list of changes & features.
We have progressed to LineageOS 18.1
Flash instructions :
Use latest pbr recovery for miatol, supports decryption - beta available here, https://pitchblackrecovery.com/joyeuse/.
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
There is a way to fix this without the fastboot factory clean, flash and lock with the official Xiaomi tool, which was forcing you to clean and lock... now available here: https://github.com/Szaki/XiaomiADBFastbootTools
If you hose the phone, use this tool - you need to install JRE though, as the tool is Java base. Put your phone is fastboot, use the tool to download the latest global rom (or whichever). Then go to where its downloaded, extract the .xy/tar file, then go back into the tool and under "image" select the folder INSIDE the folder you just extracted, then select "clean install" and install it. This will flash the majority of imgs but will error out at the end and be unable to create the "user data" partition.
That's okay, because all of the partitions will be setup again, and you can flash any rom you want again. So when its done, and still in fastboot, fastboot flash recovery recovery.img (recovery.img being the latest joyeuse pbr recovery, you renamed to recovery.img and were in that folder in the command prompt, so it will flash that recovery) or use the tool to select that recovery and it will flash it for you and reboot into for you if you like.
(Do this step last, after Magisk, if you want to unencrypt, no worries if you don't unencrypt - PBR recovery will decrypt your data ON THE SECOND TRY OF ENTERING YOUR SCREENLOCK PIN NUMBER...), the new PBR Miatol Beta 10/14/20, fixes this issue, it is now decrypted on the first entry of the phone's lockscreen PIN. Then flash disable_dm-verity_forceencrypt.zip available here for those who want decrypted data partition: https://zackptg5.com/android.php#disverfe and other places as well.
If you are encrypted and decide to unencrypt later, you will need to flash the disable_dm-verity_forceencrypt.zip in miatol recovery, then format data. Store roms, gapps, recoveries (just in case), disable_dm-verity, magisk install and uninstall and all that stuff on the SD card, so you can use them in PBR after you format DATA (the first step after installing PBR miatol recovery), just FYI. Then do the following:
Flash ROM
Flash OpenGAPPS for android 11 nano
Boot into android, make sure its working and install Magisk Manager 8.0.7, then reboot into recovery and install Magisk 21.4 (in recovery, I did not need to extract the boot.img and patch in Magisk Manager, and reboot into recovery to flash the patched boot.img, but your results may be different): https://github.com/topjohnwu/Magisk/releases. If you want to unencrypt (no guarantees its permanent though) you need to format data, THEN FLASH MAGISK, then flash disable_dm-verity (always the last step)- I usually wipe dalvik and cache too.
USE LATEST MIATOL PBR RECOVERY, PLEASE.
SD card issues resolved with the implementation of the EXFat android driver.
Source Code: https://github.com/LineageOS
Kernel Source: https://github.com/Redmi-SM6250 or Stock kernel from Miui
Apologies for the lack of updates, was diagnosed with stage 4 metastatic cancer and this project was not on my priority list anymore...
Update 28/1/21:
Release notes:
LineageOS
Device: Unified (Miatoll)
Developers: ScaryMen1325 & Loptr4
ROM Version: 18.1
Android Version: Android 11
Build date: 22/01/2021
Status: UNOFFICIAL
Changelog:
• Fixed power related issues
• Added useful apps (thanks to Dev: Emulond for that)
• Other fixes and performance improvements
Notes:
• It's 2nd test version, if you found bugs, give log.
• Using loki kernel by default, haven't tested custom kernel.
Download here:
https://drive.google.com/file/d/1M5-cRBfrRdBdNYGzy5G9bOa1Ncf5JkE4/view?usp=sharing
Please note this is a unified release, you should do a clean install unless you're coming from a unified ROM alreadyl.
Will keep you more regularly updated now that I'm out of the hospital....
Perfect will try tonight
Belpek said:
Perfect will try tonight
Click to expand...
Click to collapse
Have you tried it?
How is it? Good for daily?
There are so many Joyeuse LineageOS ROMs I don't even know where to start.
i don't see you mentioned mobile network in bugs section; does it work? i'll try this rom in a couple hours
Tell me please. If phone will be locked with black screen and i say "ok google". Will it work? Or it will work only if screen is unlocked?
sorry if its not much, since i can't do much on this rom. flashed nikogapps, google sign-in succeded but it seems that i cant install anything from play store.
(dumb me forgot to screenshot, it only says "something went wrong" when i try to install an app from play store)
about ok google from lockscreen/screen off, i tried it, also not working. can't confirm about volte since volte still relatively new here and hasn't developed that much.
Why nikgapps? Open gapps nano is recommended.
Sent from my Redmi Note 9 Pro using Tapatalk
Flash it and using it by now, so far so good, sometimes it gets a little freeze but nothing serious, miracast reboots phone so dunno if this is a bug or not, proximity sensor is another one cuz while I was in speaking with my pal screen was on all the time and my ear activated bluetooth and DND
Have nothing to talk about VoLTE cuz in my country is not available.
ANX modules left my phone in bootloop so instead I went for GCam. Flash unofficial opengapps nano and make sure to use Wi-Fi to complete the first run.
Magisk canary works so it can be rooted.
Keep the hard work!
*Sorry if I made some writing mistakes, english is not my native language. Cheers!!
Tried flashing the latest build (02.10.20) using the latest TWRP from the thread you linked but I get the "can't install package over new build" error. Is it required to come from stock miui?
gigahurts said:
...
Newer Build:
https://mega.nz/file/PlkgiSzS#C_tIspgbtGDrweztQ83lADHyEQf4dTkIUiSAqgjVAFk
NOTE: You should be on 11.0.7.0 QJZMIXM (EU) Global firmware for this build. Also, I have a newer build, but its not ready for primetime and has issues with SMS and Call Log enabling permissions.
Oh, and BTW, if you hose your ROM/Phone, just flash vbmeta.img in fastboot to avoid using the factory fastboot img flash, otherwise you many need to wait another 7 days to unlock the bootloader.
...
The dev for this build is: @wight554, all thanks and credit go to him, he is awesome, and I, for one, seriously appreciate this ROM as it works very well for me. It is so snappy and smooth, with a super fast boot time, no reboots and generally pretty frickin AWESOME!
...
Click to expand...
Click to collapse
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Swiftor said:
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Click to expand...
Click to collapse
hey Swiftor,
We will continue to work on this rom. LineageOS has been around a long time, development has spread across so many devices, however, the hardware of many devices is very similar, so support will continue. The last Redmi Note 8 pro, had a mediatek SOC, and made development difficult until MIUI decided to release its source. The snapdragon platform is very mature and is more easily and readily available to develop roms for. Redmi Note 10 pro has been released in India, and has a slightly better processor 765g vs 730g, but the kernel and hardware are very similar, so I development for this phone and the Note 10 pro should parallel and continue. We are working on submitting an official 18.0 release, but have to have all hardware (and software) fully functional and as close to zero bugs as possible. I predict development to continue as long as Xiaomi continues to release new MIUI roms for this device (and they continue to release roms for phones much, much older than this).
I have updated the first post with a newer release. Let me know if you have any issues and I will try to help.
Thanks for the props too
does magisk 21 work on the latest build? really excited for android 11
So this will not be compatible with curtana devices?
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.??
everything is working perfectly and its showing charging rapidly , it was on 88% and showing 10 minutes until full
everything is completely smooth gonna keep it for my daily use
Bantryred said:
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.
Click to expand...
Click to collapse
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
there're few thing that you need to fix @gigahurts
1) you putting wrong kernel source. its should be this link
2) why would you mirror it when you can get it in his sourceforge
Why is today's build 590MB while all others are 1.1GB?
pwnaz said:
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
Click to expand...
Click to collapse
Sorry for the delay, Im on Curtana so dont know if it makes a difference, but I used no. 16 - mi 10 Global(11)
I also had to hide Magisk Manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OrangeFox Recovery
Code:
* 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.
Information
Status: Unofficial
Version: R11.1_0
Release Date: 2021-12-14
Source Code: https://gitlab.com/OrangeFox
Device Tree: https://github.com/Pranav-Talmale/android_device_xiaomi_alioth-ofox
Kernel Source: https://github.com/Pranav-Talmale/android_kernel_xiaomi_alioth
Download:
AFH Link
Installation:
Flashing guide:
Method 1: Already having a custom recovery
1.Just flash the OFox zip in your existing recovery
Method 2: using Fastboot
1. Extract the recovery.img inside the ofox zip
2. open adb and use the following command :
3. Fastboot boot recovery.img
4.After booting in the recovery, Flash the OFox zip again to make it permanent
Note:
1.You will need to reflash recovery every time you flash a ROM.
2. Magisk Root is lost so flash Magisk if you need root after flashing Recovery.
3. HentaiOS is currently unsupported and won't be supported in the future.
Bugs:
Android 12 decryption unsupported.
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Password
* 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!
Source changelog:
https://wiki.orangefox.tech/changelog
Telegram channels:
- Support Group
Noice finally orangefox is here ! Thanks dev
im waiting for this so long its my favorite recovery
Is compatibile with xiaomi.eu based on android 12?
domthewizard said:
Is compatibile with xiaomi.eu based on android 12?
Click to expand...
Click to collapse
No.
Is this based on any of the two existing TWRP modifications for Poco F3 or is it a new approach? Reasons for asking is that they both come with their own type of bugs.
TheBrutalLicker said:
Is this based on any of the two existing TWRP modifications for Poco F3 or is it a new approach? Reasons for asking is that they both come with their own type of bugs.
Click to expand...
Click to collapse
I have tried to take the good parts of all the existing TWRPs and add my own modifications to make the recovery more stable. There will be regular updates almost every week, so make sure to check the download link almost every other day. For changelogs of the latest build, You can check the pinned message of the support group
Woahh... Nice... my fave recovery since Redmi note 5 Whyred.
Hope next build also has feature to automatic reflash ofox after flashing a rom.
Thanks.... will try this after i get home.
Vuska said:
Woahh... Nice... my fave recovery since Redmi note 5 Whyred.
Hope next build also has feature to automatic reflash ofox after flashing a rom.
Thanks.... will try this after i get home.
Click to expand...
Click to collapse
The auto reflash ofox feature won't be implemented until the ofox source developers add it. Till that time, you can just select ofox zip in the "add to queue" option so that it will reflash after the ROM flashes
Works great so far, xiaomi.eu stable 12.5.19 (android 11)
In fact, it works better than twrp, to do a backup with twrp I had to run the rm data/extm - Rf before I could backup, but with orange fox, it works normally, no commands needed
Thankyou for your work on this sir
It really works. Xiaomi.eu stable 12.5.19. Backup also works, only restoration does not work ERROR: 255
Many Thanks
varadinum said:
It really works. Xiaomi.eu stable 12.5.19. Backup also works, only restoration does not work ERROR: 255
Many Thanks
Click to expand...
Click to collapse
Backups
wiki.orangefox.tech
Cant use fastbootd on my Redmi K40(Android 11)
But other function work well
eee625 said:
Cant use fastbootd on my Redmi K40(Android 11)View attachment 5528595
Click to expand...
Click to collapse
I have noted down the issue. It seems I had not added fastbootd functionality. I am working on a fix and will release a new build soon
Ok,thank you for fixing this
Pranav Talmale said:
I have noted down the issue. It seems I had not added fastbootd functionality. I am working on a fix and will release a new build soon
Click to expand...
Click to collapse
Any chance of A12 decryption like the twrp skkk where if you don't have a lock screen, it can decrypt?
regedit12345 said:
Any chance of A12 decryption like the twrp skkk where if you don't have a lock screen, it can decrypt?
Click to expand...
Click to collapse
I don't know what black magic that guy has done to achieve that, since his trees are private (they are not on github) and I've tried contacting him 2-3 times. All I got was no response. And I myself have tried to figure it out on my own more than 5-10 times, still no luck. So I don't think I'll be able to implement a12 decryption until TWRP officially supports it.
Pranav Talmale said:
I don't know what black magic that guy has done to achieve that, since his trees are private (they are not on github) and I've tried contacting him 2-3 times. All I got was no response. And I myself have tried to figure it out on my own more than 5-10 times, still no luck. So I don't think I'll be able to implement a12 decryption until TWRP officially supports it.
Click to expand...
Click to collapse
You're doing a good job either way. Keep it up.
The only reason I switched back to twrp from orangefox was it woudnt virabte on touch so I couldn't figure out if the recovery is fully functional and I can start using it or its still booting.
regedit12345 said:
You're doing a good job either way. Keep it up.
The only reason I switched back to twrp from orangefox was it woudnt virabte on touch so I couldn't figure out if the recovery is fully functional and I can start using it or its still booting.
Click to expand...
Click to collapse
Are you using the latest build ? Vibration has been fixed a long time ago. Please use the latest build. Latest build I pushed was on 1st February
TWRP Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads TWRPInstallation (for all MIUI roms )
Code:
fastboot boot boot_lisa.img
We boot into the recovery and flash the zip through it.
In the Fox folder you will find magisk + RW mount. (installation optional).
We clean the dalvik and reboot into the system
Works:
ADB
Decryption of /data
MTP
Flashing (opengapps, roms, images and so on)
Backup/Restore
USB OTG
CPU temperature
Vibration
A/B partition functions
ADB SIDELOAD
SD-CARD
PS: For AOSP - Please wait
You can donate on the link below:
Donate
Spoiler: SCREENSHOT
OrangeFox Recovery | Build in Cloud
Device Tree TWRP
My Telegram
NEW 23/04/2023: OrangeFox BetaTest / a13 - vendorboot recovery AOSP/MIUI
Version Information
Status: Unofficial
Current Release Version: 3.7_012
Release Date: 27-Feb-2023
This is very good news, it was about time that Lisa had a recovery for Android 13.
Thanks for sharing.
What a wonderful new! Previous version for Android 12 where absolutely perfect, I am sure that this update is, or soon will be also an excellent version.
Thank you very very much!
@Dkpost3 :
I would like to send a little contribution, have you a PayPal account?
Edit: I just installed it on my Lisa running Xiaomi.eu miui 13 weekly version (Android 12): It works perfectly on Android 12, the only limit (it's a beta version) is that it can't read the ext storage. I immediately installed the update to Xiaomi.eu update to miui 14 (14.05) stable without formatting. I don't notice any problem till now.
After update the stock recovery came back so I flashed again this new one through fastboot, first I booted boot_lisa.img then I flashed it definitely from inside recovery using the zip file.
At the end I flashed successfully magisk 25.2. I am really impressed with the wonderful work of Dkpost3!
A moment ago
Add bookmark
#125
Excellent recovery. Fully functional. Very good data decryption and OTG. Only the temperature sensor is not working but that's not a big deal. Surely there will be an evolution and it will be fixed. I use MI 11 lite 5g NE (lisa), MIUI 14 global (eea) android 13.
miki1966 said:
A moment ago
Add bookmark
#125
Excellent recovery. Fully functional. Very good data decryption and OTG. Only the temperature sensor is not working but that's not a big deal. Surely there will be an evolution and it will be fixed. I use MI 11 lite 5g NE (lisa), MIUI 14 global (eea) android 13.
Click to expand...
Click to collapse
How do you install it???
quasyl said:
What a wonderful new! Previous version for Android 12 where absolutely perfect, I am sure that this update is, or soon will be also an excellent version.
Thank you very very much!
@Dkpost3 :
I would like to send a little contribution, have you a PayPal account?
Edit: I just installed it on my Lisa running Xiaomi.eu miui 13 weekly version (Android 12): It works perfectly on Android 12, the only limit (it's a beta version) is that it can't read the ext storage. I immediately installed the update to Xiaomi.eu update to miui 14 (14.05) stable without formatting. I don't notice any problem till now.
After update the stock recovery came back so I flashed again this new one through fastboot, first I booted boot_lisa.img then I flashed it definitely from inside recovery using the zip file.
At the end I flashed successfully magisk 25.2. I am really impressed with the wonderful work of Dkpost3!
Click to expand...
Click to collapse
thnks
mohamadreza40 said:
How do you install it???
Click to expand...
Click to collapse
are you having problems?
anyone tried this on MIUI 14 China ROM?
I was almost installing for aosp rom.
Greetings,....thank you very much the twrp sir...working nicely for my phone....i use miui 14 eu and android 13
PaperKing13 said:
anyone tried this on MIUI 14 China ROM?
Click to expand...
Click to collapse
Yes. It works perfectly. I flashed xiaomi.eu rom (based on cn version ) and magisk. I also did a full backup.
I've not been able to download it, but MANY THANKS for your recovery!!
Is there any other place to download it?
yandex complains about the limit of downloads
thanks!
mohamadreza40 said:
How do you install it???
Click to expand...
Click to collapse
First I booted boot_lisa.img then I flashed it definitely from inside recovery using the zip file.
Thank you very much, you did an excellent job I also directly flashed the xiaomi.eu 14.06 zip and the system booted.
miki1966 said:
First I booted boot_lisa.img then I flashed it definitely from inside recovery using the zip file.
Click to expand...
Click to collapse
I don't know how do it ... Can you help me ??
mohamadreza40 said:
I don't know how do it ... Can you help me ??
Click to expand...
Click to collapse
Unlock your bootloader (if it's not already unlocked)
Onstall adb, fastboot and related USB drivers on your PC
Restart your phone in bootloader mode
Open a command line window/terminal emulator on your PC
Change to the adb directory on your PC
Boot TWRP 3.7_012 by running: fastboot boot boot_lisa.img
After TWRP 3.7_012 has booted, check that everything is working, such as that the data partition is mounted correctly and that the touchscreen is working.
Find and select the TWRP 3.7_012 zip on your phone, tap and swipe to install it.
After installation, your phone will automatically reboot into TWRP 3.7_012
Enjoy!
miki1966 said:
Unlock your bootloader (if it's not already unlocked)
Onstall adb, fastboot and related USB drivers on your PC
Restart your phone in bootloader mode
Open a command line window/terminal emulator on your PC
Change to the adb directory on your PC
Boot TWRP 3.7_012 by running: fastboot boot boot_lisa.img
After TWRP 3.7_012 has booted, check that everything is working, such as that the data partition is mounted correctly and that the touchscreen is working.
Find and select the TWRP 3.7_012 zip on your phone, tap and swipe to install it.
After installation, your phone will automatically reboot into TWRP 3.7_012
Enjoy!
Click to expand...
Click to collapse
Thanks my friend
Dkpost3 said:
are you having problems?
Click to expand...
Click to collapse
No just i try it
xabier-bo said:
I've not been able to download it, but MANY THANKS for your recovery!!
Is there any other place to download it?
yandex complains about the limit of downloads
thanks!
Click to expand...
Click to collapse
pls check
CPU temperature * Test Build
Vibration * Test Build
SD-CARD ** Test Build