[RECOVERY][SHARED][SURYA/KARNA][R11-0_5] Orange Fox Recovery Project by ManoloRey [UNOFFICIAL] - Xiaomi Poco X3 NFC Guides, News, & Discussion

{
"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"
}
Orange Fox Recovery Project is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Devs are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at them for messing up your device, they will laugh at you.
*
*/
Features:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included customization
Inbuilt patches, like Magisk and password reset patch
Password protection
Fully open-source
and more
Bugs:
- files sorting is not remembered between reboots (it seems this depends on the MIUI base used, I just found out that on 12.0.7 this works, but not on 12.0.8)
Screenshots:
Click to expand...
Click to collapse
Changelog - current version:
-----------------------------------
OFOX R11-0_5
md5: 28094aef3c3c8b4ed99810991aecadc6
-----------------------------------
• Sync with latest OrangeFox source
• Added zip encryption-disabler-v1 on modules ofox (Menu/Fox Addons/Other)
• Fixed version number Ofox
• Fixes minor bugs that appear in the previous release
DOWNLOAD - HERE
(also for older versions): BOX
or see attached files
Changelog - older versions:
Spoiler
-----------------------------------
OrangeFox-R11-Unofficial-Beta-surya-10-01
md5: 6e35f2aedc8a11621bd490dec12dc6db
-----------------------------------
• Fix Vibration
• Rework Fastbootd and Adb Sideload code
• Use USB configs from MIUI
• Remove predefined services
-----------------------------------
OrangeFox-R11.0_0_B004-Beta
md5: cb6ffb8710e2a31e68bf8345d1c5d6a9
-----------------------------------
• Fix ADB sideload
• Fix Fastbootd (It's in the reboot menu - "fastboot")
• Decryption works 100% now (Even with PIN or password and Android 11)
How to flash the OFOX:
- via fastboot
Code:
fastboot flash recovery recovery.img
Next reboot in OFOX manually or using a fastboot command.
Code:
fastboot boot recovery.img
REMEMBER: it is important that from fastboot you directly reboot into OFOX recovery or the OFOX will be overwritten.
- via custom recovery:
Code:
flash zip file (see attached file) in recovery
Credits:
- Thanks to TeamWin devs
- Thanks to Orange Fox Recovery Project devs
- Thanks to @MrYacha and @DarthJabba9 - Source Development
- Thanks to @ManoloRey - DONATE

---

Thanks for the work!
What is the difference with the rest orangefox recoveries?

---

ManoloRey builds are noticeably faster at startup than Brigudavs, also naming of internal storage is different, also name of backup folder differ. Other needs to be tested, now you can choose between two excellent devs/products and if you feel for it, you can compare which one suits you better...

---

Thx @jeryll for your help !!! Trying this evening...

---

Thanks @jeryll for presenting this new variant of OrangeFox.
Is it safe to switch between the different OrangeFox variants?

---

If you don't use backup restore function, then it is safe to switch between them, otherwise you need move your backups to a proper location so that specific recovery can see them:
ManoloReys OFOX use
/Fox/BACKUPS/insert_your_number_here/folders_with_your_backup(s)
Brigudavs OFOX use
/Fox/BACKUPS/POCO_X3/folders_with_your_backup(s)

---

Thank you for the swift response! I'm only using TitaniumBackup so I should be safe

---

Can decrypt after install if coming from a twrp mauronofrio version?
Thanks

---

jorgeepelos said:
Can decrypt after install if coming from a twrp mauronofrio version?
Thanks
Click to expand...
Click to collapse
probably yes, but I never used mauronofrios TWRP, so IDK

---

jeryll said:
If you don't use backup restore function, then it is safe to switch between them, [....]
Click to expand...
Click to collapse
I.e. the problem of dynamic position handling is solved and a full system backup/restore is now supported?
Do you know if there are plans to make OFox for surya an official version?

---

just Nob said:
I.e. the problem of dynamic position handling is solved and a full system backup/restore is now supported?
Click to expand...
Click to collapse
- AFAIK the problem of dynamic position handling is not solved (yet)
- full system backup/restore is now supported (if certain conditions are met) more about it - HERE
just Nob said:
Do you know if there are plans to make OFox for surya an official version?
Click to expand...
Click to collapse
AFAIK only two people can answer that ManoloRey or brigudav, they are kindly providing OFOX builds for POCO X3

---

Damned, totally overlooked that you started a new thread @jeryll
So OrangeFox-R11.0_5-Unofficial-surya is indeed a newer version than @brigudav's OrangeFox-R11.0_1.0-A10-Beta-surya?
With ArrowOS 11 just having moved to OSS vendor, people are reporting problems with decryption in recovery.
Can the current OFOX deal with device decryption on a real A11 base + OSS vendor or does it require an update to OFOX?

---

Master One said:
Damned, totally overlooked that you started a new thread @jeryll
So OrangeFox-R11.0_5-Unofficial-surya is indeed a newer version than @brigudav's OrangeFox-R11.0_1.0-A10-Beta-surya?
With ArrowOS 11 just having moved to OSS vendor, people are reporting problems with decryption in recovery.
Can the current OFOX deal with device decryption on a real A11 base + OSS vendor or does it require an update to OFOX?
Click to expand...
Click to collapse
OFox is indeed older & It won't probably work with A11 OSS encryption, but you can find & try newer TWRP version by brigudav which dates from 3.5.2021. It's on 4pda. I would share download link, but brigudav doesn't allow it.

---

SkaboXD said:
OFox is indeed older & It won't probably work with A11 OSS encryption, but you can find & try newer TWRP version by brigudav which dates from 3.5.2021. It's on 4pda. I would share download link, but brigudav doesn't allow it.
Click to expand...
Click to collapse
I thought @brigudav is maintaining both OrangeFox and TWRP?
So no new version of OrangeFox that supports A11 OSS decryption yet?
I've just downloaded twrp-3.5.2_10-1-surya.img dated with 20210503, but I already got used to OrangeFox, which just looks nicer, has the proper keyboard for PIN entry and the simplified view for OTA updates.
Can you or someone else confirm that twrp-3.5.2_10-1-surya.img is indeed the correct and newest version supporting A11 OSS decryption?

---

No it doesn't work. There is no recovery available right now that supports OSS vendor rom decryption. Go back to MIUI vendor roms if you need it.

---

syl0n said:
No it doesn't work. There is no recovery available right now that supports OSS vendor rom decryption. Go back to MIUI vendor roms if you need it.
Click to expand...
Click to collapse
Even if with MIUI Vendor there's no way to access to internal storage if it's related to an Android 11 rom. Neither with the latest TWRP release by Brigudav. I see only weird folders / files names.
EDIT : there's a new version by Brigudav... maybe ?!

---

PYCON said:
Even if with MIUI Vendor there's no way to access to internal storage if it's related to an Android 11 rom. Neither with the latest TWRP release by Brigudav. I see only weird folders / files names.
Click to expand...
Click to collapse
I, too, saw "weird" folders / filenames,
but eventually I was able to access the internal storage, via TWRP
(ie. read the files unencrypted).
This is not recommended, because it weaken's the phone security,
but you can read some steps --> here

---

metaxda said:
I, too, saw "weird" folders / filenames,
but eventually I was able to access the internal storage, via TWRP
(ie. read the files unencrypted).
This is not recommended, because it weaken's the phone security,
but you can read some steps --> here
Click to expand...
Click to collapse
I don't understand what some users mean with "no security at all"...
Running Android 10 for example, even if your device is encrypted, if u have a TXT in the internal storage with your bank user / password, it's sufficient to reboot into recovery ( or turn on the device into the recovery pressing VOL + ) and... et voilà. The TXT is here. Encryption of course but perfectly readable.
So the difference? From that situation to a device with Android 11 and a decrypted internal memory... I can see no differences...
My 2 cents

---

PYCON said:
So the difference? From that situation to a device with Android 11 and a decrypted internal memory... I can see no differences...
My 2 cents
Click to expand...
Click to collapse
If phone has Android 11 with OSS Vendor ROMs (or MiUI ROM),
then the TWRP does not show files from internal storage,
ie. all files show like this
Even if encryption is turned off (or no lockscreen/PIN/pattern),
the files/folders cannot be decrypted by TWRP.

---

metaxda said:
If phone has Android 11 with OSS Vendor ROMs (or MiUI ROM),
then the TWRP does not show files from internal storage,
ie. all files show like this
Even if encryption is turned off (or no lockscreen/PIN/pattern),
the files/folders cannot be decrypted by TWRP.
Click to expand...
Click to collapse
So basically, it seems that Android 11 is more "secure" than Android 10, speaking only about recovery accessing memory... right ?