New Update is Out!
Date: 03 February 2022
Type: OFFICIAL
Changelogs and Build notes:

Type: OFFICIAL


is there any way to remove these scripts?@Sushrut1101 I had a problem with my 9A, it doesn't complete booting, it gets stuck forever in bootanimation, I believe it has to do with adiutor/lspeed/macrodroid kernel boot scripts. how to proceed?
I'm not able to proceed with miflash using orangefox fastboot
Because Android 11 MIUI is not supported@Sushrut1101 I had a problem with my 9A, it doesn't complete booting, it gets stuck forever in bootanimation, I believe it has to do with adiutor/lspeed/macrodroid kernel boot scripts. how to proceed?
adb reboot bootloader
Hi, i'm interested to know, a way to make this recovery (or another) to work with MIUI 12.5 / Android 11, sadly i'm stuck without root in android 11, and dont wanna back to Android 10, buut need adaway worrking... if you could please point me in a direction to a recovery or at least root, would be great, many thanks, and greetings from Colombia!
Just patch your boot image with Magisk, then flash it through fastboot. It doesn't need custom recovery to work. You can find your boot image easily if you download your actual rom version, specifically the recovery rom.Hi, i'm interested to know, a way to make this recovery (or another) to work with MIUI 12.5 / Android 11, sadly i'm stuck without root in android 11, and dont wanna back to Android 10, buut need adaway worrking... if you could please point me in a direction to a recovery or at least root, would be great, many thanks, and greetings from Colombia!
Many thx for the Response buddy, btw, this its the first method that i try, sadly when i fastboot the magisk patch boot (taken from the fastboot Rom) and reboot, phone bootloops in the first "redmi" screen, reflashing the no touched boot.img make phone works again... this was tried with the last magisk version (25.1), canary and stable, again many thanks and any idea would be appreciated (i just need adaway working).Just patch your boot image with Magisk, then flash it through fastboot. It doesn't need custom recovery to work. You can find your boot image easily if you download your actual rom version, specifically the recovery rom.
While flashing boot image you must also flash empty vbmeta, and make totally sure that the fastboot rom you downloaded its the same version you have right now in your deviceMany thx for the Response buddy, btw, this its the first method that i try, sadly when i fastboot the magisk patch boot (taken from the fastboot Rom) and reboot, phone bootloops in the first "redmi" screen, reflashing the no touched boot.img make phone works again... this was tried with the last magisk version (25.1), canary and stable, again many thanks and any idea would be appreciated (i just need adaway working).
Many Thanks my friend, works like a charm, i put the vmeta in the same folder that the boot, and just searh the "disable"fastboot command in the web, everything works, included AdAway, you're very kind and helpfull, good day buddy!While flashing boot image you must also flash empty vbmeta, and make totally sure that the fastboot rom you downloaded its the same version you have right now in your device
Hello. Thank you for your great contribution, but I have something to ask for. Do not force the auto reboot because you are causing damage. I recently wanted to downgrade the firmware from v12.5.12 china to v12.0.10 global in order to be able to install other custom roms. I went to the custom recovery I had: PBRP (built with vndk30 for r-vendor); and flashed the firmware v12.0.10 global from there, my next step was to flash OFRP because I needed a recovery that works with firmware v12.0.10. What happened was that the installer of OFRP rebooted my device without my permission and now I have my device dead. It doesnt boot nor show the initial screen nor nothing and I am not able to enter into META mode in order to flash it from there. What I planned to do was to flash firmware, then recovery and last the new custom rom, and finnaly reboot, but, the installer of OFRP did what it never should do. If you know any trick, program or anything to get my device to life once again you can tell me.OrangeFox Recovery Project
Code:/* * 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 recovery * 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. * */
OrangeFox is FREE SOFTWARE
Information
Status: Official
Version: R11.1_1
Release Date: 28 June 2022
Maintainer: Sushrut1101
Sources
Source Code: https://gitlab.com/OrangeFox
Device Tree: https://gitlab.com/OrangeFox/device/garden.git
Kernel: Prebuilt (in the Device Tree).
XDA Template Generator: https://github.com/OrangeFoxRecovery/XDA.git
Downloads: Here
Supported Models:
- Redmi 9A (dandelion)
- Redmi 9C (angelica)
- POCO C3 (angelicain)
- Other garden device (Xiaomi MT6765 / MT6762 With Dynamic Partitions)
- [ Currently Supported Codenames: dandelion, angelica, angelican, angelicain, cattail ]
Installation:
https://wiki.orangefox.tech/en/guides/installing_orangefox
Documentation (FAQ):
https://wiki.orangefox.tech/en/guides
Donations:
https://t.me/Sushrut1101
Source changelog:
https://wiki.orangefox.tech/changelog
Telegram Channels:
News - https://t.me/OrangeFoxBetaTracker
Support Chat - https://t.me/OrangeFoxChat
OrangeFox App:
XDA : DevDB Information
OrangeFox Recovery Project, Tool/Utility for garden (Xiaomi Redmi 9A / 9C / POCO C3)
Contributors
Sushrut1101, Sushrut Gupta ,DarthJabba9, MrYacha
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
* @Sushrut1101 - For this XDA Template
* @mastersenpai05 - For Helping and some Fixes
* @Sushrut1101 - Maintainer, Device Trees
If you're talking about Dandelion and no other garden device, you will have to open the device and remove the battery, then plug it again and use sp flash tool (with a exploit to bypass auth) to flash full firmware. Another option is wait for the battery to die, but i haven't tried it yet.Hello. Thank you for your great contribution, but I have something to ask for. Do not force the auto reboot because you are causing damage. I recently wanted to downgrade the firmware from v12.5.12 china to v12.0.10 global in order to be able to install other custom roms. I went to the custom recovery I had: PBRP (built with vndk30 for r-vendor); and flashed the firmware v12.0.10 global from there, my next step was to flash OFRP because I needed a recovery that works with firmware v12.0.10. What happened was that the installer of OFRP rebooted my device without my permission and now I have my device dead. It doesnt boot nor show the initial screen nor nothing and I am not able to enter into META mode in order to flash it from there. What I planned to do was to flash firmware, then recovery and last the new custom rom, and finnaly reboot, but, the installer of OFRP did what it never should do. If you know any trick, program or anything to get my device to life once again you can tell me.
My device is dandelion, model m2006c3lc. where i can download that software who make the exploit? ModemMeta can not enter into META mode because en error #6004 that is related to Serial Link Authentication.If you're talking about Dandelion and no other garden device, you will have to open the device and remove the battery, then plug it again and use sp flash tool (with a exploit to bypass auth) to flash full firmware. Another option is wait for the battery to die, but i haven't tried it yet.
My device is dandelion, model m2006c3lc. where i can download that software who make the exploit? ModemMeta can not enter into META mode because en error #6004 that is related to Serial Link Authentication.
Hello. I was able to flash the stock ROM once again using the software MTKClient. It has modern techniques. Now I'm using crDroid with firmware 12.5.12 R-vendor. I believe that I must to flash the full stock ROM v12.0.10 if I want to avoid that bad experience once again, and then flash other custom ROMs. Thank you all for your tips.If you're talking about Dandelion and no other garden device, you will have to open the device and remove the battery, then plug it again and use sp flash tool (with a exploit to bypass auth) to flash full firmware. Another option is wait for the battery to die, but i haven't tried it yet.
/*
* 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 recovery
* 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.
*
*/
None works. I had to make a very simple port from a non-touch custom recovery to make some backups I really needed, but is also full of bugs and I had to Uninstall it. Better wait for developer to sort things out. If by any chance you are looking to root this device, you can easily do it flashing a patched boot image through fastboot.I cross my fingers, same thing happened with Pitch Black recovery. Any other custom recovery works on your side?
Nop