OrangeFox 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"
}
Installation
* Download Latest OrangeFox
* Assuming you already have twrp installed, copy the downloaded zip to device. Then Install.
* After successful installation it auto-reboots to OrangeFox recovery. Enjoy
Working
ADB
Decryption of /data
Screen brightness settings
Correct screenshot color
MTP
Flashing (opengapps, roms, images and so on)
Backup/Restore
OZIP decryption
Vibration support
USB OTG
Bugs
Report with proper logs.
Credits:
@MrYacha & @DarthJabba9 for this amazing custom Recovery
And the most 4j17h for pushing me to make it...
And whole HyperTeam for all the help in the beginning of my android development...
XDA:DevDB Information
[Official][Stable]OrangeFox Recovery for realme X2 Pro [R11][RMX1931], ROM for the Realme X2 Pro
Contributors
Jerry08, 4j17h
Source Code: https://gitlab.com/OrangeFox/
ROM OS Version: Android 10
Version Information
Status: Stable
Created 2020-08-04
Last Updated 2020-09-03
How to use F2FS
- boot to OrangeFox,
- go to 'Manage partitions'
- format data,
- select 'data', change filesystem, f2fs,
- select 'cache', change filesystem, f2fs,
- reboot,
- enjoy...
Reserved
Android 10 compatible?
tidschi said:
Android 10 compatible?
Click to expand...
Click to collapse
Depends, I tried on rui and it was fine. But it seems to have issues with decryption on a10 gsi, but first I let users report it as I'm not sure.
Will you need a modified vbmeta like the one on twrp?
And will it work on my global version?
Sent from my Realme RMX1931 using XDA Labs
SebTech33 said:
Will you need a modified vbmeta like the one on twrp?
And will it work on my global version?
Click to expand...
Click to collapse
Yes you will need vbmeta and yes it will work on global.
Jerry08 said:
Yes you will need vbmeta and yes it will work on global.
Click to expand...
Click to collapse
Thank you for your answer. Can i use the one from the twrp thread?
Sent from my Realme RMX1931 using XDA Labs
SebTech33 said:
Thank you for your answer. Can i use the one from the twrp thread?
Click to expand...
Click to collapse
Yeah or the one from my guides thread. It's up to you.
Jerry08 said:
Depends, I tried on rui and it was fine. But it seems to have issues with decryption on a10 gsi, but first I let users report it as I'm not sure.
Click to expand...
Click to collapse
By any chance was fingerprint working after installing RUi using this recovery?
There are reports of FP broken when using twrp
P1f said:
By any chance was fingerprint working after installing RUi using this recovery?
There are reports of FP broken when using twrp
Click to expand...
Click to collapse
Nope fp wasn't working after flashing rui, tested by me. Probably need to wait for official rui release.
Jerry08 said:
Nope fp wasn't working after flashing rui, tested by me. Probably need to wait for official rui release.
Click to expand...
Click to collapse
So what needs to be done to have a working FP sensor? But it's broken even without root?
---------- Post added at 06:03 PM ---------- Previous post was at 05:55 PM ----------
asusgarb said:
So what needs to be done to have a working FP sensor? But it's broken even without root?
Click to expand...
Click to collapse
I know I could simply flash it from twrp and try but, except for OTG working, are there any particular reasons to use this instead of twrp?
I've read that OrangeFox is based on twrp, but offers a better support to Treble than twrp.
asusgarb said:
So what needs to be done to have a working FP sensor? But it's broken even without root?
---------- Post added at 06:03 PM ---------- Previous post was at 05:55 PM ----------
I know I could simply flash it from twrp and try but, except for OTG working, are there any particular reasons to use this instead of twrp?
I've read that OrangeFox is based on twrp, but offers a better support to Treble than twrp.
Click to expand...
Click to collapse
Having also magisk/app manager, flashlight(if anyone would ever use it in recovery), password change. Just try it and check yourself.
Hi!
Switch to this recovery today. I'm having some trouble, stucked in a bootlooad: realme white logo and reeboots to recovery. Can someone help me?
I've tried the normal procedure, with the latest rom from Realme support in UK, after wiping system and data. No good.
What should I do? Do I need to install other rom? What about vbmeta? What should I wipe different?
johnnyjoe said:
Hi!
Switch to this recovery today. I'm having some trouble, stucked in a bootlooad: realme white logo and reeboots to recovery. Can someone help me?
I've tried the normal procedure, with the latest rom from Realme support in UK, after wiping system and data. No good.
What should I do? Do I need to install other rom? What about vbmeta? What should I wipe different?
Click to expand...
Click to collapse
It's a issue with vbmeta. You have to flash vbmeta via fastboot with disable flags:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Jerry08 said:
It's a issue with vbmeta. You have to flash vbmeta via fastboot with disable flags:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hi @Jerry08! I've tried that, many times, but no luck. I get the "fastboot.exe: unknown option -- disable-verity" error.
I've tried to download all short of adb/fastboot versions, I've installed the latest android studio, minimal adb, etc., but I can't find a way to get a fastboot that works.
I'm sure that my phone is seen after typing fastboot devices. I'm open my powershell window on the folder that has the files.
Can you please help? I'm not sure what I'm doing wrong. Thanks! : )
---------- Post added at 12:39 PM ---------- Previous post was at 12:14 PM ----------
[/COLOR @Jerry08, I think I get it to work:
C:\vbmeta>fastboot devices
513a895e fastboot
C:\vbmeta>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (0 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
After that, It keeps rebooting to recovery.
How can I format and install everything from scratch?
Here's what happened.
Yesterday, I tried to reboot to TWRP but, for some reason I can think off, I couldn't. I thought to try oragefox. When I was installing oragefox, and since I got the fastboot error, I maybe installed vbmeta and then the recovery - or I installed it without vbmeta, can't be sure now. After that, it kept rebooting to recovery. After a while, since I could'n fix it, I eraser caches, system and data and tried to flash the rom from scratch. No luck, I can't pass the reboot to recovery. I switch back to twrp, oragefox sometime got a full black screen and only the flash worked by vol up and power, and it was difficult o restart the phone.
Thanks! : )
What can I do to get my phone back?
johnnyjoe said:
It's a issue with vbmeta. You have to flash vbmeta via fastboot with disable flags:
Hi @Jerry08! I've tried that, many times, but no luck. I get the "fastboot.exe: unknown option -- disable-verity" error.
I've tried to download all short of adb/fastboot versions, I've installed the latest android studio, minimal adb, etc., but I can't find a way to get a fastboot that works.
I'm sure that my phone is seen after typing fastboot devices. I'm open my powershell window on the folder that has the files.
Can you please help? I'm not sure what I'm doing wrong. Thanks! : )
---------- Post added at 12:39 PM ---------- Previous post was at 12:14 PM ----------
[/COLOR @Jerry08, I think I get it to work:
C:\vbmeta>fastboot devices
513a895e fastboot
C:\vbmeta>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (0 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
After that, It keeps rebooting to recovery.
How can I format and install everything from scratch?
Here's what happened.
Yesterday, I tried to reboot to TWRP but, for some reason I can think off, I couldn't. I thought to try oragefox. When I was installing oragefox, and since I got the fastboot error, I maybe installed vbmeta and then the recovery - or I installed it without vbmeta, can't be sure now. After that, it kept rebooting to recovery. After a while, since I could'n fix it, I eraser caches, system and data and tried to flash the rom from scratch. No luck, I can't pass the reboot to recovery. I switch back to twrp, oragefox sometime got a full black screen and only the flash worked by vol up and power, and it was difficult o restart the phone.
Thanks! : )
What can I do to get my phone back?
Click to expand...
Click to collapse
Did you wipe or format data(option where you type "yes")? The best you can do now is to format data(option where you type "yes") and try boot to os. And if it does not help, than follow Updating colorOS via Custom Recovery and as last step format data(option where you type "yes").
Now for the RUI users.
There's still a lot issues i face in rui. So BEWARE! Like today I updated Magisk Canary to latest and got bootloop, couldn't boot to recovery and data partition got ****ed up. I had to flash ofox via fastboot and format data to get it back working.
Jerry08 said:
Did you wipe or format data(option where you type "yes")? The best you can do now is to format data(option where you type "yes") and try boot to os. And if it does not help, than follow Updating colorOS via Custom Recovery and as last step format data(option where you type "yes").
Now for the RUI users.
There's still a lot issues i face in rui. So BEWARE! Like today I updated Magisk Canary to latest and got bootloop, couldn't boot to recovery and data partition got ****ed up. I had to flash ofox via fastboot and format data to get it back working.
Click to expand...
Click to collapse
@Jerry08, format data, after installing rom, did work! Thanks a lot. : )
I did format data to install rom. After installing the rom I would get the phone to bootloop. Formating data after the rom was installed did solve it.
Thank you, one more time. : )
P1f said:
By any chance was fingerprint working after installing RUi using this recovery?
There are reports of FP broken when using twrp
Click to expand...
Click to collapse
FP works fine for me using this recovery before i update to rui i turned of lock screen password and booted to orange fox than wiped dalvik cache , cache, system. vendor and internal storage kept un touched than flashed rui after that i try to reboot back to recovery to install magisk but internal storage is not decting so i reboot to system and phone booted to rui every thing works fine sofar now finding a way to root it
Jerry08 said:
Did you wipe or format data(option where you type "yes")? The best you can do now is to format data(option where you type "yes") and try boot to os. And if it does not help, than follow Updating colorOS via Custom Recovery and as last step format data(option where you type "yes").
Now for the RUI users.
There's still a lot issues i face in rui. So BEWARE! Like today I updated Magisk Canary to latest and got bootloop, couldn't boot to recovery and data partition got ****ed up. I had to flash ofox via fastboot and format data to get it back working.
Click to expand...
Click to collapse
Exact same thing happened to me, and i did the same format data to fix it, I thought it was my fault somehow.
I will stay unrooted for now in order to use fingerprint and since Safetynet check was failing for me anyway ever since the server side change from Google
Related
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
I'm not responsible for hard bricks, however if any steps I've entered are entirely wrong, please do let me know. I'm only trying to help the community out.
What you need:
Unlocked bootloader, sadly you will have to wait for the permission from them (I don't like this process either)
Decent knowledge of TWRP menu system
no care for completely wiping the SD Card contents - please make a backup of pictures or anything else you want
adb and fastboot both working and recognising the phone properly
Gemini (Xiaomi Mi 5) TWRP - https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api **Thanks to Nesquix for posting the link to this** it is in Chinese and the theme changing solution did not work for me - but this doesn't really matter if you know your way around TWRP
Latest SuperSU - https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Latest DEV Fastboot ROM - I cannot post the link however it can be found by searching for "mi 5 fastboot developer rom" on Google and selecting the link going to en.miui.com
STEPS to take:
Extract the contents of the fastboot ROM to a location of your choice. The only file you need is this one: \...\...\images\system.img (if someone can upload separately, I'll link in OP)
Place both the system.img from the fastboot ROM and twrp img file in the location of your fastboot folder
Enter fastboot mode (bootloader) on the Mi 5 via Power off --> volume down + power on --> let go once you see the MI logo
Check your device can be seen via the command, fastboot devices --> ENTER
Now input the following command, fastboot flash recovery twrp-mi5.img --> ENTER
Now enter in to recovery via volume up + power on - There appears to be a bug with TWRP whereby on some boots, touch isn't responsive, just keep booting back till it works (it will eventually)
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card
Power off again, and reboot back to fastboot mode (bootloader)
Once there, input this command, fastboot flash system system.img --> ENTER
Once the system is flashed, input this command, fastboot reboot
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system
PROFIT - you now have an unencrypted system with working superSU and apps like Adaway work flawlessly - HAVE FUN and don't forget to say thanks if I did actually help you
Interesting notes.....
I'm not sure about anyone else, but I found web browsing to be alarmingly slow with no good explanation, the above steps completely resolved this
Google is now a search option in the default browser (it wasn't before!!)
Call it placebo all you want, but the phone really does seem a lot faster now.
Last but not least, I'm fairly certain to update to newer versions, you only have to extract same system.img from future fastboot ROM zips, and flash this on it's own to update the system.
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
nesquix said:
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
Click to expand...
Click to collapse
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
{
"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"
}
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
kickassdave said:
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
.
Click to expand...
Click to collapse
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
tomhtg90 said:
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
Click to expand...
Click to collapse
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
kickassdave said:
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
Click to expand...
Click to collapse
English languages in TWRP will not go back to chinese if you tap on "Never show this screen during boot again", "swipe to allow modification" and "Swipe disable recovery flash". But, if that's the only method that work for you, good then. Cheers
No need to flash again system here too
What exactly do the rest of the contents of the ROM contain then since I literally flashed on a single img from the entire zip!
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
1myxomatosis1 said:
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
Click to expand...
Click to collapse
this is what i'm trying to do now. but i'm on another base... not the 6.3.17 but the 7.2.7.0, anyway this is the same procedure.
when you have unlocked your bootloader, there is no way to encrypt all data again if you don't select "flash_all_lock.bat" with MiFlash windows app...
so you can play all TWRP partitions...except the SDCARD (called "data/media", don't mingle/mix up/confound with the "data" partition.... )
So since fastboot is still open with your unlocked bootloader are always able to reflash a recovery and do whatever you want again, don't panic !
i tried updating my rom 7.2.7.0 to 6.3.24 by flashing the system.img BUT there are some force close.... security center FC... wifi not working... i think they forgot to say that we need to manually flash the boot.img too (kernel.... who contain a lot of drivers and system links...)
so i just flashed the system.img and boot.img of the 6.3.24 on my 7.2.7.0 rom, i will report my feedback in some hours max. EDIT : WORKING !
but don't wory, since you don't wipe your SDCARD in the recovery (or use the flash_all_lock.bat with MiFlash), you will not loose your decrypted data partition
if my method of "simple updating" is not working by just flashing system.img and boot.img over the rom........ i suggest to reflash all partition with adb (system.img and boot.img), after that you can reboot to the twrp recovery, flash supersu 2.68 (or the last one) to be root, and setup your phone again... (you can do a MiBackup in the settings, and restore it later, this is working fine for your app, settings and so on)
:silly:
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
UPDATE : WORKING.
Procedure to UPDATE since your phone have UNLOCKED BL, data decrypted and TWRP already flashed (or you can flash it before the procedure by adb) :
PROCEDURE
just flash the system.img AND the boot.img with adb in the CMD
(be sure your files are in the same folder of adb.exe and fastboot.exe)
"fastboot flash system system.img"
"fastboot flash boot boot.img"
then reboot to twrp recovery... flash supersu 2.68..
you don't need to wipe something.
just reboot and wait.
your phone is now updated, with root, twrp, decrypted data, and you don't loose your apps, settings and files. :good:
nesquix said:
[...]
PROCEDURE
[...]
Click to expand...
Click to collapse
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
1myxomatosis1 said:
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
Click to expand...
Click to collapse
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Ivyn87 said:
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
Click to expand...
Click to collapse
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
p1nky said:
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Click to expand...
Click to collapse
After wiping all the phone 2 times in the twrp recovery.
nesquix said:
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
After wiping all the phone 2 times in the twrp recovery.
Click to expand...
Click to collapse
Very thanks... now it work
Why can't TWRP write to encrypted partitions? I thought this is possible with TWRP 3.0. At least I have not heard from new Nexus owners that disabling encryption is necessary.
Hello,
I have Twrp already and a custom rom, i only want to decrypt . Am i right that i only< had to do this:
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card.
And later to get root:
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system.
Kind regards gandalf
Thank you very much. !!!!:laugh::laugh:
I saved this tutorial, I had left the phone in the login screen.
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
christ-al said:
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
Click to expand...
Click to collapse
Yes ... U keep system...get blank data... Restart the phone... copy the zip/ROM again...or use USB otg
Joyeuse: Phone stuck in "the system has been destroyed" after recovery flash
Hi,
I've messed up my global Redmi Note 9 Pro (Joyeuse).
I had various issues updating to Xiaomi.EU 110.0.5 because of the dynamic storage while using PBRP 2.9.1 and 3.0 unofficial builds which I found on XDA.
So I ended up using the TWRP referenced here: https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ The multi-language version.
This finally installed the ROM, But it never passed the boot animation.
I tried various things with deleting data/reset which can be found when googling for that state, but they did not help.
So I though maybe this TWRP build is the culprit and let's check what happens if I go back to PBRP.
Big Mistake.
After flashing PBRP I received a "the system has been destroyed" message when trying to reboot.
I used the fastboot install batch file for stock 11.0.4 to get back to a working system which of course has the system recovery.
But now every time I try to flash a custom recovery, no matter which one I try (and they all installed fine before) I get the system destroyed message at reboot (no matter if to system or recovery)
Any ideas how to fix this so I can get a decent recovery?
Smuggle a PBRP recovery into the stock flash process?
thx
afx
a.f.x. said:
Hi,
I've messed up my global Redmi Note 9 Pro (Joyeuse).
I had various issues updating to Xiaomi.EU 110.0.5 because of the dynamic storage while using PBRP 2.9.1 and 3.0 unofficial builds which I found on XDA.
So I ended up using the TWRP referenced here: https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ The multi-language version.
This finally installed the ROM, But it never passed the boot animation.
I tried various things with deleting data/reset which can be found when googling for that state, but they did not help.
So I though maybe this TWRP build is the culprit and let's check what happens if I go back to PBRP.
Big Mistake.
After flashing PBRP I received a "the system has been destroyed" message when trying to reboot.
I used the fastboot install batch file for stock 11.0.4 to get back to a working system which of course has the system recovery.
But now every time I try to flash a custom recovery, no matter which one I try (and they all installed fine before) I get the system destroyed message at reboot (no matter if to system or recovery)
Any ideas how to fix this so I can get a decent recovery?
Smuggle a PBRP recovery into the stock flash process?
thx
afx
Click to expand...
Click to collapse
You've posted in the wrong section.
I'd suggest flashing the vbmeta.img with fastboot before flashing recovery to disable verified boot.
lalibm said:
You've posted in the wrong section.
Click to expand...
Click to collapse
Which one would be the right one?
I'd suggest flashing the vbmeta.img with fastboot before flashing recovery to disable verified boot.
Click to expand...
Click to collapse
The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times.
fastboot.exe $* flash vbmeta `dirname $0`/images/vbmeta.img
if [ $? -ne 0 ] ; then echo "Flash vbmeta error"; exit 1; fi
fastboot.exe $* flash vbmetabak `dirname $0`/images/vbmeta.img
if [ $? -ne 0 ] ; then echo "Flash vbmetabak error"; exit 1; fi
fastboot.exe $* flash recovery `dirname $0`/images/recovery.img
Click to expand...
Click to collapse
cheers
afx
a.f.x. said:
Which one would be the right one?
The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times.
cheers
afx
Click to expand...
Click to collapse
Try other recovery with te recovery from rr Telegram group Will work
Los recovery also Will work
canteo said:
Try other recovery with te recovery from rr Telegram group Will work
Click to expand...
Click to collapse
I am unfortunately not on Telegram;-(
Someone sent me this, but the link s recursive ;-(
https://t.me/pbrp_testers/9182
cheers
afx
a.f.x. said:
I am unfortunately not on Telegram;-(
Someone sent me this, but the link s recursive ;-(
https://t.me/pbrp_testers/9182
cheers
afx
Click to expand...
Click to collapse
https://www.dropbox.com/s/6k9w18cwof5w7yx/recovery.img?dl=0
flash with fastboot and will work, it is pbrp miatoll
canteo said:
https://www.dropbox.com/s/6k9w18cwof5w7yx/recovery.img?dl=0
flash with fastboot and will work, it is pbrp miatoll
Click to expand...
Click to collapse
Thanks, that worked.
I did try integrating it into the stock update script, just in case, still had stock recovery after that. Strange.
Explicitly flashed it afterwards and got PBRP. Great!
Immediately flashed xiaomi.eu 11.0.5.
Tried to sideload Magisk, but that seems to be wonky in this recovery (when I switch PBRP to sideload adb no longer sees the device).
Now I can only get to PBRP, no system boot and PBRP while it worked on the first start now has problems decrypting the device ;-(
thx
afx
a.f.x. said:
Thanks, that worked.
I did try integrating it into the stock update script, just in case, still had stock recovery after that. Strange.
Explicitly flashed it afterwards and got PBRP. Great!
Immediately flashed xiaomi.eu 11.0.5.
Tried to sideload Magisk, but that seems to be wonky in this recovery (when I switch PBRP to sideload adb no longer sees the device).
Now I can only get to PBRP, no system boot and PBRP while it worked on the first start now has problems decrypting the device ;-(
thx
afx
Click to expand...
Click to collapse
remember to unmount system and vendor before flash a rom, also i use to flash magisk with the recovery without issues, iḿ with eu rom on joyeuse
flash magisk after boot the rom, will be better
a.f.x. said:
Which one would be the right one?
The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times.
cheers
afx
Click to expand...
Click to collapse
The correct section would have been the Q&A as you've posted in ROMs and Kernels.
What I meant was to flash the modified vbmeta to force disable avb (android verified boot) which could have been easily found on the telegram group, the purpose of which is to prevent the "system destroyed" scenario from happening as the stock vbmeta img has avb enabled. You flashing pbrp somehow kept triggering the flag which resulted in system destroyed repeatedly on each attempt.
Additionally, I have read about pbrp giving some joyuse users trouble with encryption. I'd highly suggest that you join the telegram group for help regarding this. I would have gladly helped you with each step but I own curtana. Hope you get the device up and running again soon. Cheers!
lalibm said:
The correct section would have been the Q&A as you've posted in ROMs and Kernels.
Click to expand...
Click to collapse
Ok, me thought this is a recovery issue and as there is currently only alpha software.
What I meant was to flash the modified vbmeta to force disable avb (android verified boot) which could have been easily found on the telegram group, the purpose of which is to prevent the "system destroyed" scenario from happening as the stock vbmeta img has avb enabled. You flashing pbrp somehow kept triggering the flag which resulted in system destroyed repeatedly on each attempt.
Click to expand...
Click to collapse
I do not think that this is the issue in this case. By now I can install the PBRP that was kindly provided via dropbox.
Me thinks something was weird in the TWRP I installed that triggered this.
Since I tried the PBRP provided here, I no longer see this message.
Additionally, I have read about pbrp giving some joyuse users trouble with encryption.
Click to expand...
Click to collapse
I can get into PBRP after flashing stock, before setting the encryption password in stock,
At that time this is all with some default or null key and PBRP seems to be ok with it.
I'd highly suggest that you join the telegram group for help regarding this.
Click to expand...
Click to collapse
Let's just put it that way, Telegram is thanks to some analysis I did in a previous job, definitely not something I am keen on.
thx
afx
If Bootloader is unlocked, flash fastboot rom
Otherwise EDL
https://github.com/Szaki/XiaomiADBFastbootTools try this
You guys are responding to posts made on 5th September! I think the OP moved on long ago (on 5th September, actually) ...
OFFICIAL LINEAGE OS 17.1 NIGHTLIES
LineageOS Downloads
download.lineageos.org
The most recent build was dated 25th Feb 2021. [Edit UPDATED to most recent build date].
The previous offerings were 2021-01-28; 2021-02-04 ; 2021-02-11; 2021-02-18.
{
"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"
}
CEDRIC WIKI
Info about cedric | LineageOS Wiki
wiki.lineageos.org
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
QRXpMUvS said:
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
Click to expand...
Click to collapse
Any oero firmware will do as your base
Flash via fastboot - if you don't know which to choose use the latest retail version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to flash rom
Go to twrp
Select wipe
Format data - option on the right (will format everything on phone including personal files so backup first!)
Restart to twrp
Wipe then advanced wipe
Wipe system data and cache
Select install from main menu
Install rom zip
Install gapps (you want arm64 android 10 nano)
Install magisk (optional for root access & to hide apps from detecting root/custom rom)
Wipe delvik cache
Restart
Encrypt phone again if required once booted from phone settings menu
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
QRXpMUvS said:
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
Click to expand...
Click to collapse
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Hi,
i updated my G5 to the official LOS. Although VoWifi and VoLTE are enabled in settings, none of them are working (They didn't work on the unofficial version either).
According to my network operator, these functions are activated.
Unter Phone Info (*#*#4636#*#* in dialer's app) it says "IMS Registration: Not Registered"
Is there anything I can do about this?
Thanks!
TheFixItMan said:
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Click to expand...
Click to collapse
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
QRXpMUvS said:
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
Click to expand...
Click to collapse
I have the same problem. I can't get Lineage or Mint to boot on my Cedric.
I've tried TWRP 3.4 , and 3.5 and neither made a difference. I have been through the instructions on the lineage site many times, and I'm sure I'm not missing a step
But every time the device sticks at lineage boot logo for a long time, before returning to fastboot mode.
If I re-flash 8.1 using fastboot, the phone works again, then go from the top with twrp and lineage, and we're back to logo and eventually fastboot again.
So, although I cannot help yet, you are not alone.
Edit:
My cedric is the 3GB RAM XT1676 model which I think might be somewhat rare version?
HarpingOn said:
So, although I cannot help yet, you are not alone.
Click to expand...
Click to collapse
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
QRXpMUvS said:
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
Click to expand...
Click to collapse
I have only tried mint and official 17.1. Get the same problem with both sadly.
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
For your info everyone: the OP is not the developer. I am neither. I just patch the official builds and that is Mint.
HarpingOn said:
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
Click to expand...
Click to collapse
If you could give me logs, I'll check.
nift4 said:
If you could give me logs, I'll check.
Click to expand...
Click to collapse
My problem was that I was starting from the GB release of Cedric stock 8.1 as I'm in the UK. If I flashed the GB version, then no Lineage ROM would boot. Not this, and not the Mint one.
If you check out the Mint thread, what I did was use Fastboot to flash an international version of stock 8.1, then I could add TWRP and flash this successfully.
I ended up testing Lineage With microG, but actually successfully flashed this, and Mint as well.
So I'd say to anyone struggling to get a working flash of this ROM, try a different CEDRIC set of fastboot files.
as im aware, you need to flash from stock 8.1 but sometimes if youre on pie you gotta flash nougat and then oreo to flash custom roms i tried flashing that rom before but got no succes with bootlop but i didnt knew this i have tried unnoficial los 17 but never though about trying again the one from los page, guess its Worth a try
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Lighto97 said:
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Click to expand...
Click to collapse
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
TheFixItMan said:
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
Click to expand...
Click to collapse
oh damm i always forgot i have to send the log for them to track the issue, i already uninstaled anyway.
i did followed the steps the right way (thank you), right now im flashing stock nougat to try out LOS 14.1 (which i love and seems to be reeealy stable)
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
tfbb said:
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
Click to expand...
Click to collapse
i know how to boot with that LOS recovery, instead of flash comand you use boot command so the device will bot into recovery suing the image.
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
dario-20 said:
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
Click to expand...
Click to collapse
Always wipe dalvic cache data storage and format data before you flash any rom
It
akoaypinoy said:
Always wipe dalvic cache data storage and format data before you flash any rom
Click to expand...
Click to collapse
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
dario-20 said:
It
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
Click to expand...
Click to collapse
How you flash havoc? Vanilla or Gapps version?
akoaypinoy said:
How you flash havoc? Vanilla or Gapps version?
Click to expand...
Click to collapse
Gapps
If you installed a new rom, clear the data and delvik cache at the end.
StaryMuz said:
If you installed a new rom, clear the data and delvik cache at the end.
Click to expand...
Click to collapse
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
dario-20 said:
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
Click to expand...
Click to collapse
That's weird, havoc is not kind of caf rom , hnnn
akoaypinoy said:
That's weird, havoc is not kind of caf rom , hnnn
Click to expand...
Click to collapse
After this installation I cannot boot into recovery! Probably I installed twrp in wrong way for the very first time. But still don't know how to make it right. It means when I install twrp in the wright way I cannot install Havoc... Maybe tommorow I will try to come back to twrp...
The correct way to install TWRP is to run it without installing it first and then install it to the ramdisk. If you do it any other way, you will delete the boot and replace it only with the recovery one. Then the phone can't go anywhere but recovery.
only boot from twrp. dont flash it
inn0ichi said:
only boot from twrp. dont flash it
Click to expand...
Click to collapse
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
dario-20 said:
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
Click to expand...
Click to collapse
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
akoaypinoy said:
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
Click to expand...
Click to collapse
Thanks but: Now I am on OrangeFox recovery (which I cannot boot - it was the last flashed recovery). Typing fastboot boot twrp.img gives back: not found
What do you suggest in this situation?
StaryMuz said:
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
Click to expand...
Click to collapse
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
StaryMuz said:
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
Click to expand...
Click to collapse
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
{
"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"
}
Reboot to recovery → I return to the same recovery as above.
dario-20 said:
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Click to expand...
Click to collapse
orangefox is that your recovery now. Orangefox and twrp are recovery both. The difference is that orangefox can no flash the kernel unlike twrp. Please be specific what you are doing,
Orangefox and twrp are recovery
HavocOS is a rom
Before you do make specific, or else you get messed.
dario-20 said:
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
View attachment 5449627View attachment 5449629
Reboot to recovery → I return to the same recovery as above.
Click to expand...
Click to collapse
Everytime you install a new make it read . Because other rom have own recovery. (Ex. Pixelplus) once you install that automatically you have a pe recovery once it reboot , so the proper way to maintain twrp is "flash current twrp" which you can find in advance in twrp recovery. Remember once you flash a new rom don't reboot and go to advance then flash the current twrp. After that reboot.
{
"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"
}
TWRP recovery 3.6.1 for lancelot(redmi 9 | lancelot/galahad)
Code:
I am not responsible for your brick devices.
The recovery is fully working and has been tested.
If you encounter a problem, write here, maybe they will help you.
Before you accuse me of doing something wrong, take a look at how you use your smartphone.
You don't need to blame me for turning your device into a brick with my recovery, it's not my fault.
Attention!The recovery is fully operational, it can make backups, install backups, it was tested only on custom Roms, but not on MIUI, but it should also work there.
Install:
To install, simply flash img to the recovery section and then reboot.
If you want to flash via fastboot, do the following:
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
After that, you will find yourself in a new recovery.
Be careful when flashing!
Version Information
Status: Stable
Changelog:
Spoiler
24.03.2022
- inital build
- mtp not worked (For full operation, flash the ROM again through a new recovery!)
downloads:
Mega | GDrive
Information:
TWRP recovery for lancelot/galahad | redmi 9
Contributors
Furry__wolf
Credits:
TheGame455
Randomas3000
zubairk22oct
GADGETNiK
ExpressLuke
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
https://github.com/Redmi-MT6768/omni_device_xiaomi_lancelot
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
popej said:
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
Click to expand...
Click to collapse
Use another recovery. So that it is not replaced by this archive
popej said:
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
Click to expand...
Click to collapse
You can backup the whole flash using the instructions provided in this thread.
The problem with restoring recovery is because you haven't rooted (via magisk) the device after flashing recovery. That's why the phone restores the recovery. IMEI (and other numbers like MACs) sits on a dedicated partition, so you can back the partition without having access to the data partition. Currently TWRP is unable to decrypt data when A12+ is used.
Thanks for your advice.
I'm on A11 MIUI. I didn't expect problems with encryption, but maybe it is MIUI problem.
I have made a backup to microSD with SHRP. SHRP can read partitions used for IMEI. For some reasons I couldn't make backup with TWRP.
I forgot about Magisk. With Magisk SHRP stay permanently. Probably tweak in SHRP or zip provided by OP can do the same, but I haven't tested.
My question is if I can format data and install custom A11 system without worrying about encryption?
When you format the data partition, the system will encrypt it again with the fist boot after flashing the ROM.
My Redmi 9 is on Pixel Experience Plus 12.1 with Pixel Experience recovery. Bad battery drain on idle so I want to try crDroid or PixelPlus.
Can I install this version of TWRP over Pixel Experience recovery? I want to install via Fastboot. I am already on Pixel Experience recovery so do I need to issue :
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
or can I just go:
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
dataworx said:
My Redmi 9 is on Pixel Experience Plus 12.1 with Pixel Experience recovery. Bad battery drain on idle so I want to try crDroid or PixelPlus.
Can I install this version of TWRP over Pixel Experience recovery? I want to install via Fastboot. I am already on Pixel Experience recovery so do I need to issue :
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
or can I just go:
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Use a better full installation using vbmeta
Furry__wolf said:
Use a better full installation using vbmeta
Click to expand...
Click to collapse
Thanks for the reply - so I can just copy the vbmeta.img file from my original MIUI rom, and use that? Or does it need to be modified first?
dataworx said:
Thanks for the reply - so I can just copy the vbmeta.img file from my original MIUI rom, and use that? Or does it need to be modified first?
Click to expand...
Click to collapse
Use this vbmeta. It is patched for use on custom ROMs
Furry__wolf said:
Use this vbmeta. It is patched for use on custom ROMs
Click to expand...
Click to collapse
Thank you for your time and advice. I'll be able to tackle this tomorrow morning.
dataworx said:
Thank you for your time and advice. I'll be able to tackle this tomorrow morning.
Click to expand...
Click to collapse
No problem
I don't know if this is been asked before but after I flashed twrp recovery I noticed that on twrp internal memory doesn't show as it normal, can't access anythin, is there a way to fix that? (Lancelot)
hi iam install lineage os 18.1 twrp version is 3.5.2 this rom is very good and smooth and best battery...but install anu A12 custom rom whit twrp 3.5.2 its very slow and bad ram performance
what is problem? twrp is down virsion for A12?
Hi Everyone, twrp will be gone after some time by the miui Recovery. Though I flashed the vbmeta from Post #10.
What am I doing wrong?
morfikov said:
When you format the data partition, the system will encrypt it again with the fist boot after flashing the ROM.
Click to expand...
Click to collapse
Hello and thanks for your work here friend .
any way to make TWRP or SHRP decrypt internal storage ? I know about formatting data to make internal storage available , but a way to decrypt after booting ? On Android 10 I had no problem but on Android 11 Decryption doesn't work .
hi, when I try flashing this on miui 13 and reboot to recovery, it just reboots and goes into system ui. I'm using redmi 9 prime
Can anyone help me installating twrp for my poco m2, i tried but either i fot stucked into boot loop or my old miui recovery somehow replaced the file , can anyone plz.... Help via deskshare or any other way,
Vedant2 said:
Can anyone help me installating twrp for my poco m2, i tried but either i fot stucked into boot loop or my old miui recovery somehow replaced the file , can anyone plz.... Help via deskshare or any other way,
Click to expand...
Click to collapse
I had the same problem that I would fastboot flash the recovery, but still MIUI recovery would come up instead. You need to enter fastboot mode using Power+VolDown buttons and no cable connected, not via "adb reboot fastboot".
What tricked me is that (at least on MIUI 13) there are two fastboot modes.
When doing "abd reboot fastboot", the screen shows "FASTBOOTD" in BLUE letters. In this fastboot mode, "fastboot flash" finishes with "OKAY", but will actually do nothing.
When phone is off and you start it by pressing POWER + VOL_DOWN buttons, you get "FASTBOOT" (no D) in ORANGE letters. Only this fastboot will actually flash a new recovery!
It also prints "USB downloading..." on screen.