OrangeFox Recovery
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.
*
*
INSTALLATION:
1. Back up your important data
2. Boot image with "fastboot boot path/to/image"
3. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
4. Install flashable zip
5. Enjoy!
Credits
* TeamWin - for TWRP Recovery
* The OrangeFox Team - for your hard work
* To all testers for their time and patience
* @TheRealDarkness for build OrangeFox
* @ThE_MarD for TWRP sources
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Password, torch, led
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* And many more!
Screenshots: https://telegra.ph/OrangeFox-Recovery-Project--Moto-g30caprip-12-22
Source Code: https://gitlab.com/OrangeFox
Download recovery: https://sourceforge.net/projects/caprip/files/OFOX/
REPORTING BUGS!
* You tell me
* You have to wait 10-20 seconds for the touch to work, (recovery was tested on caprip with ilitek and Novatek touchscreen)
could you enable data decryption for android 12, or it impossible?
even once I disabled screen lock entirely, I can't "decrypt /data" for some reason, which severely limits the entire point of custom recoveries
(running via fastboot boot, not permanent install, but shouldn't make a difference)
otherwise it looks pretty cool!
jan6 said:
could you enable data decryption for android 12, or it impossible?
even once I disabled screen lock entirely, I can't "decrypt /data" for some reason, which severely limits the entire point of custom recoveries
(running via fastboot boot, not permanent install, but shouldn't make a difference)
otherwise it looks pretty cool!
Click to expand...
Click to collapse
did you boot recovery?
I can make a guide on how to decrypt data on this device, it's really easy to do it, in the Moto G³⁰ group in BR we have two methods to do it.
Although since the recovery is based on TWRP 3.7.0-12-0 it should decrypt itself )))
why else would I write here if I didn't boot into this orangefox, lol
I did
Code:
adb reboot bootloader
fastboot boot OrangeFox-R11.1_0-Unofficial-caprip.img
it's the same as with twrp, more or less, /data is locked, and mounting of /data is required for like half the functionality, and nandroid backups are most of the point of a custom recovery
from what I've heard twrp SHOULD be able to decrypt android 11 and 12, idk why it doesn't work for me with neither twrp nor orangefox (which even has a nicer pin entry box for decryption), even if I remove screen lock entirely, it can't do it... (I'm running android 12)
jan6 said:
why else would I write here if I didn't boot into this orangefox, lol
I did
Code:
adb reboot bootloader
fastboot boot OrangeFox-R11.1_0-Unofficial-caprip.img
it's the same as with twrp, more or less, /data is locked, and mounting of /data is required for like half the functionality, and nandroid backups are most of the point of a custom recovery
from what I've heard twrp SHOULD be able to decrypt android 11 and 12, idk why it doesn't work for me with neither twrp nor orangefox (which even has a nicer pin entry box for decryption), even if I remove screen lock entirely, it can't do it... (I'm running android 12)
Click to expand...
Click to collapse
With the attached file you can easily decrypt, just follow these steps:
1° Format data
2° Flash zip attached
3° Format data and reboot
After that the storage should be free of encryption.
Or you can use another method, if you use my rom you will know that all the partitions are in read-write, being able to modify anything, including the vendor. Another exp would be:
With the other attachment "fstab.zip"
You can do the download, then unzip "fstab.zip", it will leave a file called "fstab.qcom", with it you go to the vendor and mount it as RW, then follow the path "/vendor/etc" and copy fstab.qcom, then you do a reboot and the storage would be decrypted.
Related
OrangeFox Recovery For XZ Premium
Adapt By SJll
禁止任何内置推广APP以及收费ROM使用或参考本项目
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
Download:
Link
INSTALLATION:
1. Download th zip file to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. Enjoy!
ChangeLog
Pie-V3.3.1-V1:
Update blob to android Pie.
V3.3.1-V2:
Fix mountpoint of persist partition.
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* Cryptomilk for init tweaking.
FEATURES:
* Increased compatibility with TWRP
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM [only for some devices]
* Password
* 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!
Contributor
@Sjll
Source code
Github
Update date
2019.08.01
Screenshots
- see below
Nice
我用twrp3.2.1刷入这个zip后重启还是twrp，解出img来用trwp app刷进recovery分区也一样。系统用的是马大官改，没有刷你的pt。
I flashed this zip file via twrp 3.2.1 , but reboot to recovery still gets twrp 3.2.1 working on it. the same thing happened using twrp app to flash unpacked img file. I haven't flashed your project treble yet.
leiersai said:
我用twrp3.2.1刷入这个zip后重启还是twrp，解出img来用trwp app刷进recovery分区也一样。系统用的是马大官改，没有刷你的pt。
I flashed this zip file via twrp 3.2.1 , but reboot to recovery still gets twrp 3.2.1 working on it. the same thing happened using twrp app to flash unpacked img file. I haven't flashed your project treble yet.
Click to expand...
Click to collapse
检查你的刷入分区，如果还是不行，获取root后用工具箱类的app试试。
Check the partition you flashing in, if still error, try to flash via some app tool after getting root permission.
I finally made it work by flashing via computer through fastboot. but now I'm facing another problem, it shows my data patition is encrypted, but I don't know the password. I'm using gesture lockscreen and fingerprint in Android. my device has been rooted via magisk.
----------------------------------------
now i knew what is going wrong... temporarily give up.
leiersai said:
I finally made it work by flashing via computer through fastboot. but now I'm facing another problem, it shows my data patition is encrypted, but I don't know the password. I'm using gesture lockscreen and fingerprint in Android. my device has been rooted via magisk.
----------------------------------------
now i knew what is going wrong... temporarily give up.
Click to expand...
Click to collapse
If you forget your password, you need to format userdata partition.
I'm install through newest twrp as img and working great. Awesome job on original twrp some kernels won't let me get into twrp. On Orangefox is OK.
Sjll said:
If you forget your password, you need to format userdata partition.
Click to expand...
Click to collapse
I know my passwords, but not that secret key I even have no idea about when my phone encrypted /data by itself...
Benio9436 said:
I'm install through newest twrp as img and working great. Awesome job on original twrp some kernels won't let me get into twrp. On Orangefox is OK.
Click to expand...
Click to collapse
Enjoy it!
leiersai said:
I know my passwords, but not that secret key I even have no idea about when my phone encrypted /data by itself...
Click to expand...
Click to collapse
I didn't support dm-verify in OrangeFox, so you could only format it.
On the Pie-V3.3.1-V1 variant of OrangeFox I'm noticing some strange issues.
Some scripts cannot properly mount or unmount /system, with all kinds of excuses such as "device or resource busy", or just outright "no such file or directory"... It can also happen after a nandroid backup. While mostly harmless, sometimes it can cause addon.d to break (such as OpenGApps and Magisk) and I need to manually flash back things that addon.d should have guaranteed their survival at that time.
For now it can be worked around by flashing only one zip at a time and reboot to recovery to flash my next one.
By the way, it seems backing up/restoring the entire system image is safer than only the contents of the system partition, as back then with stock ROM (eXistenZ) I noticed that if I back up only the contents of system partition with TWRP then restoring it later, the system would bootloop at Sony logo, whereas restoring a backup of entire system image would boot fine.
LSS4181 said:
On the Pie-V3.3.1-V1 variant of OrangeFox I'm noticing some strange issues.
Some scripts cannot properly mount or unmount /system, with all kinds of excuses such as "device or resource busy", or just outright "no such file or directory"... It can also happen after a nandroid backup. While mostly harmless, sometimes it can cause addon.d to break (such as OpenGApps and Magisk) and I need to manually flash back things that addon.d should have guaranteed their survival at that time.
For now it can be worked around by flashing only one zip at a time and reboot to recovery to flash my next one.
By the way, it seems backing up/restoring the entire system image is safer than only the contents of the system partition, as back then with stock ROM (eXistenZ) I noticed that if I back up only the contents of system partition with TWRP then restoring it later, the system would bootloop at Sony logo, whereas restoring a backup of entire system image would boot fine.
Click to expand...
Click to collapse
Have you disabled the MIUI OTA?
Sjll said:
Have you disabled the MIUI OTA?
Click to expand...
Click to collapse
What is MIUI OTA? I did see it mentioned something about XiaoMi or MIUI but I remember it said "DISABLED".
After all, I'm not flashing anything XiaoMi or MIUI related (I'm flashing just LOS, OpenGApps, Magisk and modules).
LSS4181 said:
What is MIUI OTA? I did see it mentioned something about XiaoMi or MIUI but I remember it said "DISABLED".
After all, I'm not flashing anything XiaoMi or MIUI related (I'm flashing just LOS, OpenGApps, Magisk and modules).
Click to expand...
Click to collapse
It's in settings and "MIUI OTA" is enabled by default.
I confirmed this issue, but I had no idea to solve it now. And the core function of OrangeFox is fine. You can compare my device tree with OrangeFox official devices'. We may lack of some blob or have some wrong settings
Sjll said:
It's in settings and "MIUI OTA" is enabled by default.
I confirmed this issue, but I had no idea to solve it now. And the core function of OrangeFox is fine. You can compare my device tree with OrangeFox official devices'. We may lack of some blob or have some wrong settings
Click to expand...
Click to collapse
I can confirm the MIUI OTA was enabled. However, disabling it has no effect regarding the failures in handling the /system partition. Also, it seems the recovery can determine whether the package is a MIUI OTA, as I recall it says MIUI OTA support DISABLED when flashing ROM zips such as LOS.
When mount/unmount operations on /system fails, the error usually reads "device or resource busy". Guess something is locking the system partition for too long.
While the issue doesn't impact much when flashing zips, it can potentially prevent addon.d scripts from succeeding causing loss of certain OTA survival capable components such as OpenGApps and Magisk.
EDIT: Also, when the "device or resource busy" error occurs, I also can't mount/unmount system partition from the Mount screen.
EDIT 2: It seems the Orangefox tree uses a prebuilt kernel... is that kernel image also overclocked? It appears the phone would overheat while in recovery, and the overheated state would carry over and cause freezes/reboots due to the SoC hit certain power/thermal thresholds, as the logcat is simply cut off without anything implying kernel panics or fatal errors.
可以汉化不
Amazing post
Any stable version
any chance of updating this for andriod 11?
i am trying to build it myself but i am a total beginner.
there is an aosp a11 rom for maple now and i really need the magisk manager recovery that orangefox provides!
ok i cant get this to work,
ive used your device tree to build with three different kernels and it compiles every time. i can flash it and it boots ok, but touchscreen doesnt work so i cant get into recovery.
is there something i need to do to get touchscreen working before i build?
Code:
Code:
#include <std_disclaimer.h>
/*
*
* We 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 project
* 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.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
# Method 1 (Fastboot Installation)
1. Boot into fastboot mode by adb reboot bootloader or key combo, doesn't matter.
2. Download the twrp image following the link in the download section and transfer it to the adb folder (or add adb to PATH for universal access).
3. Open the cmd/terminal and change directory into the adb folder (or where you downloaded twrp image).
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug, linux users may need to change connection type to transfer files from charging only.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery <pbrp-recovery.img>
BooM ! PBRP flashed successfully.
# Method 2 (Zip Flashing)
1. If you haveany custom recovery(TWRP, Orange Fox etc.) installed in your device, then this is just a piece of cake.
2. Download & flash the zip from custom recovery install menu.
3. It will reboot to recovery automatically after that.
BooM ! PBRP flashed successfully.
Note: Flashable zip contains decryption patch, so you don't need to worry about encryption, you can check log right after flasing PBRP, there should be a string in green color confirming device encryption status.
Downloads
Both Image & Zip=> Here
XDA:DevDB Information
PBRP For Realme X, Kernel for the Realme X
Contributors
chankruze
Source Code: https://github.com/N00bTree/android_device_realme_RMX1901
Kernel Special Features:
Version Information
Status: Testing
Created 2019-09-20
Last Updated 2019-09-23
I cannot believe my eyes ! Thanks so much
No boot my phone..
How to flash...
Add Video..
Help me bro..
Team Win Recovery Project 3.x, or twrp3 for short, 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>
/*
*
* We 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 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.
*
*/
Installation
Download version .tar when you haven't a TWRP installed and you are coming from stock ROM and flash it via Odin in download mode. NOTE: Un-check Auto-reboot option in Odin, install tar file (it has to be placed in AP section) and after reboot manually in recovery mode with vol+, home and power buttons. This because otherwise you'll come back to stock recovery.
Download version .img when you have a TWRP installed. Simply, from home, go in install -> install image -> select your .img file -> press recovery as partition where you want to install it -> swipe to flash -> reboot system.
Download version .zip if you have an old TWRP. (you can install a .img or .zip file, as you want)
Bugs/Issues
Encryption with password isn't supported, so don't set the secure boot or put a password at the boot of the device
Download
kmini3g (SM-G800H): https://www.androidfilehost.com/?w=files&flid=319793 - mirror: https://t.me/tab4los
Source code
kmini3g: https://github.com/matteo0026/android_device_samsung_kmini3g
Kernel: https://github.com/matteo0026/android_kernel_samsung_msm8226
Contributors
matteo0026, isbon
Works great, thanks!
New build (-2) is out.
Changelog:
- Minor TWRP source changes (either recovery and device tree)
- Slightly reduced size of the package
New TWRP 3.5.0_9-0 is out.
Changelog:
- All TWRP 3.5.0_9 changes and improvements
- Some changes done in device tree to make it ordered and with less junk
- Persist and firmware (modem) partitions aren't backupable anymore. Firmware partition backup/restore/wipe with vfat partition makes network issues, and with emmc backups are useless since can't be restored successfully, and this "filesystem" isn't wipeable. Persist partition doesn't need any backups/wipes/restores, and if someone has some particular issues, it's always better to go to latest stock firmware, better with pit file too. I don't want to support anymore something that is half working.
- Try to fix time even in backups
Hi guys, new TWRP 3.5.0_9-1 is out!
Changelog:
- Get back persist partition backup, since it can be important to backed up, sometimes.
- Reintroduce su
New TWRP 3.5.1_9-0 is out!
Changelog:
- Changes coming from 3.5.1 version
New TWRP 3.5.2_9-0 is out!
Changelog:
- Changes coming from 3.5.2 version
Hi guys, new builds of TWRP are up. You can find the changelog of the TWRP 3.6.0 here: https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
TWRP 3.6.2_9-0 for kmini3g is out!
Changelog:
- https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
- https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
matteo0026 said:
TWRP 3.6.2_9-0 for kmini3g is out!
Click to expand...
Click to collapse
Where is it?
i5510 said:
Where is it?
Click to expand...
Click to collapse
Sorry, I forgot to put the mirror site. Now you can find it in the downloads section
matteo0026 said:
Sorry, I forgot to put the mirror site. Now you can find it in the downloads section
Click to expand...
Click to collapse
Thanks!
Some people don't use Telegram. Is there a particular reason why you don't upload it to https://www.androidfilehost.com/?w=files&flid=319793 ?
i5510 said:
Thanks!
Some people don't use Telegram. Is there a particular reason why you don't upload it to https://www.androidfilehost.com/?w=files&flid=319793 ?
Click to expand...
Click to collapse
Yesterday I've added on rush the link in the first post, and then I just forgot to upload them in AFH. Now they are uploaded on AFH too, hoping that it works fine.
Thank you.
Hi,
How do i know if my device has Encryption with password enabled ? I have a 800F here and would like to flash TWP.
Thanks in advance.
Team Win Recovery Project 3.x, or twrp3 for short, 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>
/*
*
* We 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 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.
*
*/
Installation
Download version .tar when you haven't a TWRP installed and you are coming from stock ROM and flash it via Odin in download mode. NOTE: Un-check Auto-reboot option in Odin, install tar file (it has to be placed in AP section) and after reboot manually in recovery mode with vol+, home and power buttons. This because otherwise you'll come back to stock recovery.
Download version .img when you have a TWRP installed. Simply, from home, go in install -> install image -> select your .img file -> press recovery as partition where you want to install it -> swipe to flash -> reboot system.
Download version .zip if you have an old TWRP. (you can install a .img or .zip file, as you want)
Bugs/Issues
Encryption with password isn’t supported, so don’t set the secure boot or put a password at the boot of the device
Download
gtelwifiue (SM-T560NU): https://www.androidfilehost.com/?w=files&flid=328969
gtesqltespr (SM-T377P): https://www.androidfilehost.com/?w=files&flid=328968
Source code
gtelwifiue: https://github.com/TWRPSG-8916/android_device_samsung_gtelwifiue
gtesqltespr: https://github.com/TWRPSG-8916/android_device_samsung_gtesqltespr
Kernel: https://github.com/LOSSG-8916/android_kernel_samsung_msm8916
DJABHipHop said:
Team Win Recovery Project 3.x, or twrp3 for short, 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>
/*
*
* We 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 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.
*
*/
Installation
Download version .tar when you haven't a TWRP installed and you are coming from stock ROM and flash it via Odin in download mode. NOTE: Un-check Auto-reboot option in Odin, install tar file (it has to be placed in AP section) and after reboot manually in recovery mode with vol+, home and power buttons. This because otherwise you'll come back to stock recovery.
Download version .img when you have a TWRP installed. Simply, from home, go in install -> install image -> select your .img file -> press recovery as partition where you want to install it -> swipe to flash -> reboot system.
Download version .zip if you have an old TWRP. (you can install a .img or .zip file, as you want)
Bugs/Issues
Encryption with password isn’t supported, so don’t set the secure boot or put a password at the boot of the device
Download
gtelwifiue (SM-T560NU): https://www.androidfilehost.com/?w=files&flid=328969
gtesqltespr (SM-T377P): https://www.androidfilehost.com/?w=files&flid=328968
Source code
gtelwifiue: https://github.com/TWRPSG-8916/android_device_samsung_gtelwifiue
gtesqltespr: https://github.com/TWRPSG-8916/android_device_samsung_gtesqltespr
Kernel: https://github.com/LOSSG-8916/android_kernel_samsung_msm8916
Click to expand...
Click to collapse
thank you for all your great and dedicated hard work
blaze2051 said:
thank you for all your great and dedicated hard work
Click to expand...
Click to collapse
NP
New TWRP 10 update for Samsung Galaxy Tab E 9.6 & Samsung Galaxy Tab E 8.0 MSM8916 Model
Change Log:
- Backup Now Works.
- Plus All Partitions can now be backup.
Hi there!!
I'm having some troubles installing TWRP on a gtelwifiue (Samsung SM-T561). Could the 3.5.2_10 version work also on this device?
I apparently uploaded with success TWRP through heimdall, but when I restart the device with (volumeUp+home+power) the recovery doesn't show up; instead, I get the logo splashpage with a small red exclamation mark on the top left :-|
fillotassi said:
Hi there!!
I'm having some troubles installing TWRP on a gtelwifiue (Samsung SM-T561). Could the 3.5.2_10 version work also on this device?
I apparently uploaded with success TWRP through heimdall, but when I restart the device with (volumeUp+home+power) the recovery doesn't show up; instead, I get the logo splashpage with a small red exclamation mark on the top left :-|
Click to expand...
Click to collapse
Nope, This version of TWRP is for SM-T560NU & the SM-T337P.
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
Download:
*.ZIP LINK
*.TAR LINK
Bugs
Decryption will only work if no password/PIN/pattern is set in Android.
You tell me.
How to install
Spoiler: If you dont have a custom recovery installed
[*]Make sure your bootloader is already unlocked and OEM unlock is enabled, otherwise the installation will fail.
[*]Download and install Samsung Drivers
[*]Download the latest *.tar for your phone
[*]Download Odin, from example from https://downloads.corsicanu.ro/samsung/
[*]If not done before, flash disabled VBMeta with Odin in AP slot
[*]Turn off your phone, connect it to PC and reboot to download mode by holding down Volume up, Volume down and power button at the same time.
[*]Open Odin and check if your device is detected, then untick "Autoreboot" in its settings.
[*]Put the tar file you downloaded into the AP tab
[*]Click start and wait for the installation to finish, Odin will show PASS
[*]Now hold down Power button and Volume down for about 10 seconds to force reboot the device
[*]Immediately after the screen goes black release the keys and hold down Volume up and Power button at the same time until you enter OrangeFox (You may need to release the keys after about 20-30secs due to the "unlocked bootloader" warning)
[*]If you properly followed all the steps you should now see the OrangeFox menu.
[*]I HIGHLY recommend to flash services disabler right after you enter OrangeFox to disable forced encryption and stock recovery restoration.
[*]IF YOU ALREADY HAVE TWRP OR OLDER ORANGEFOX BUILDS INSTALLED, JUST DOWNLOAD AND FLASH THE ZIP FILE IN RECOVERY
Spoiler: If you do have a custom recovery installed
[*]Download the *.zip file
[*]Flash it in recovery.
[*]Once its done flashing, phone will reboot on its own to recovery
[*]If you properly followed all the steps you should now see the OrangeFox menu.
Sources: https://github.com/RisenID/android_device_samsung_a52sxq
Credits:
Orangefox team
@BlackMesa123 for the TWRP trees and general help and support.
@corsicanu for updating multidisabler for A12 and providing download links for Odin, USB drivers, etc.
Thanks to all my testers, you know who you are <3
Hey guys, after a lot of thpught, I have decided to drop official support, and provide unofficial builds, so that I can give you guys the best possible builds that I can, so there will be no more official ofox builds from me, but there will be unofficial ones. Thanks for understanding, hope you like these builds.
Changelogs
R11.1
- Fix /vendor backup restoring
- Updated kernel to DVK5
- Support Android 13 decrypt with no password
- Fix /efs, /sec_efs backup
- Fix fastbootd
- Disable stock recovery patching in /vendor
-Bundle Magisk Delta instead of Magisk
Reserved