[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [03-MAR-2024]

[Wishmasterflo]

New Orangefox Version for Android 13 and Android 14 custom ROMs.
It does not work on Stock OOS now (with Stock OOS Kernel!)

Changelog
R12.1 V28 02-Feb-2024
- Synced with latest Orangefox source changes
- Now Orangefox will reflash itself if a ROM is flashed from within a already flashed Orangefox V28 (or newer) Version on the phone.

 

[kjslabber]

Can I flash a fastboot oos 11 rom to downgrade from A14 Derpfest. No windows machine available to MSM. I only use Linux.

 

[Wishmasterflo]

Can I flash a fastboot oos 11 rom to downgrade from A14 Derpfest. No windows machine available to MSM. I only use Linux.

Via fastboot you can flash whatever you want. Juszt make sure you flashed the needed firmware for that first.

 

[Mr.Vince]

is there any build available for Oos 14? Im currently using oos 14 so is there any build for oos 14?

 

[Wishmasterflo]

is there any build available for Oos 14? Im currently using oos 14 so is there any build for oos 14?

Not yet, but soon.

 

[BillGoss]

New Orangefox Version for Android 13 and Android 14 custom ROMs.
It does not work on Stock OOS now (with Stock OOS Kernel!)

Changelog
R12.1 V28 02-Feb-2024
- Synced with latest Orangefox source changes
- Now Orangefox will reflash itself if a ROM is flashed from within a already flashed Orangefox V28 (or newer) Version on the phone.

I'm running official Los 21 (Android 14) on my 8T (with latest OOS 13.1 EU firmware). V28 behaved perfectly (unlocking with password, backing up data, rebooting).
But I couldn't find the Fox folder or the backup on my phone. So I rebooted into recovery, and the backup was there, where I expected it to be (/sdcard/Fox).
The one thing I noticed was that files/directories were owned by root:media_rw, unlike the other files in /sdcard which were owned by media_rw:media_rw.
I had seen something like this happening a long time ago and moving the files/directories would fix the ownership, but not this time. So I changed the owner to media_rw and rebooted, but that made no difference.

My Android file explorer (Solid Explorer) has root permission so I looked in /data/media/0 (aka sdcard) but no Fox directory there. Then I used su in Termux and ran 'ls -la' and then I could see the directory. But all the attributes where showing ??'s and I couldn't access the contents. I did get a message saying something like "file needs cleaning" which I've never come across before. I was not able to do anything with the directory, not even delete it.

I took screenshots of all of this, but in the process of trying some other things I managed to get Orange Fox to make the whole sdcard unavailable to the system. So I had to factory reset the phone and lost the screenshots.
This also makes me wonder what would happen if I tried to restore a backup - would that trash /data, not just /sdcard?

Any idea what's going on? I'm prepared to try things again using Orange Fox and get information for you because I would love to have a working backup of my phone.

 

[BillGoss]

I decided to play around a bit more. So I installed OF again, and then just looked thorough all its options, hoping that one of them would allow me to backup to an SD card. But no such luck.
Upon rebooting system, /sdcard is no longer visible, but /storage/emulated/0 is working, as is /data/media/0.
In fact programs that have data on /sdcard seem to be working fine

In Termux running 'ls' on /sdcard gives "ls: reading directory '.': Structure needs cleaning". But the same command on /data/media/0 gives

ls: cannot access 'Fox': Structure needs cleaning
'.$Trash$'     Movies          data
 .transforms   Music           driveinfo.calibre
 @install      Notifications   los-ota.txt
 Alarms        Obsidian        metadata.calibre
 Android       Pictures        nine
 Audiobooks    Podcasts        ninex
 Books         Recordings      openrecoveryscript
 DCIM          Ringtones       ors-prev.log
 Documents     SwiftBackup     ors.log
 Download      TWRP            pif
 Fox           Tools           rssd.log

And ls -l gives:

...
drwxrwsr-x   6 media_rw media_rw    3452 240229 10:55 Download
d?????????   ? ?        ?              ?            ? Fox
drwxrwsr-x   3 media_rw media_rw    3452 231207 08:48 Movies
...

I tried to run e2fsk and fsck.(erofs,f2fs) but neither worked.

Since not having /sdcard isn't a show stopper - it's a nuisance - I'm leaving things as they are in case you want more information.

 

[BillGoss]

I managed to get my phone back to normal by booting into recovery, entering my password to decrypt storage, then used adb shell from my PC and deleting /sdcard/Fox and rebooting (all from shell).

Update: I was correct in not rebooting from the Fox UI because that will create /sdcard/Fox if it doesn't exist so that it can write logs.
And I didn't need to use adb because you can run the reboot command from Terminal.

 

[Wishmasterflo]

I'm running official Los 21 (Android 14) on my 8T (with latest OOS 13.1 EU firmware). V28 behaved perfectly (unlocking with password, backing up data, rebooting).
But I couldn't find the Fox folder or the backup on my phone. So I rebooted into recovery, and the backup was there, where I expected it to be (/sdcard/Fox).
The one thing I noticed was that files/directories were owned by root:media_rw, unlike the other files in /sdcard which were owned by media_rw:media_rw.
I had seen something like this happening a long time ago and moving the files/directories would fix the ownership, but not this time. So I changed the owner to media_rw and rebooted, but that made no difference.

My Android file explorer (Solid Explorer) has root permission so I looked in /data/media/0 (aka sdcard) but no Fox directory there. Then I used su in Termux and ran 'ls -la' and then I could see the directory. But all the attributes where showing ??'s and I couldn't access the contents. I did get a message saying something like "file needs cleaning" which I've never come across before. I was not able to do anything with the directory, not even delete it.

I took screenshots of all of this, but in the process of trying some other things I managed to get Orange Fox to make the whole sdcard unavailable to the system. So I had to factory reset the phone and lost the screenshots.
This also makes me wonder what would happen if I tried to restore a backup - would that trash /data, not just /sdcard?

Any idea what's going on? I'm prepared to try things again using Orange Fox and get information for you because I would love to have a working backup of my phone.

Yes, got it. I am just building a new Orangefox Version. The Kernel things and adjustments I used in my Orangefox V28 (when trying to get it to work on Stock OOS13/OOS14 have messed up things now.
So reverting back to the Kernel settings I used before in V27 .

 

[Wishmasterflo]

New Orangefox Version V29 for Android 13 and Android 14 custom ROMs.
It does not work on Stock OOS for now!

Changelog
R12.1 V29 03-Mar-2024
- Synced with latest Orangefox source changes
- Orangefox will reflash itself if a ROM is flashed from within a already flashed Orangefox V28 or later Version on the phone!
- Reverted back Kernel settings which caused issues on Orangefox V28
- Updated Magisk addon to Magisk v27.0

 

[BillGoss]

New Orangefox Version V29 for Android 13 and Android 14 custom ROMs.
It does not work on Stock OOS for now!

Changelog
R12.1 V29 03-Mar-2024
- Synced with latest Orangefox source changes
- Orangefox will reflash itself if a ROM is flashed from within a already flashed Orangefox V28 or later Version on the phone!
- Reverted back Kernel settings which caused issues on Orangefox V28
- Updated Magisk addon to Magisk v27.0

Thanks for the update. The new version doesn't have the problem.
BUT...
When I booted v29 I got errors about inaccessible directories that needed cleaning.
I discovered that v28 had not only affected /sdcard/Fox but a number of other locations in /data (see file ll in the attached zip and look for "??").
I rebooted v28 and went through deleting all of the relevant directories, rebooted v29 and it still has errors (/data/reserve)! And backing up /data failed (see the logs in Fox/BACKUPS/...)
Rebooted v28 again and deleted /data/reserve (rm -fr reserve) but it didn't get deleted even though there were no errors executing the command.
So I'm now stuck with a system that can't be backed up and v28 won't delete the offending directory.
Any suggestions?

 

[Wishmasterflo]

Thanks for the update. The new version doesn't have the problem.
BUT...
When I booted v29 I got errors about inaccessible directories that needed cleaning.
I discovered that v28 had not only affected /sdcard/Fox but a number of other locations in /data (see file ll in the attached zip and look for "??").
I rebooted v28 and went through deleting all of the relevant directories, rebooted v29 and it still has errors (/data/reserve)! And backing up /data failed (see the logs in Fox/BACKUPS/...)
Rebooted v28 again and deleted /data/reserve (rm -fr reserve) but it didn't get deleted even though there were no errors executing the command.
So I'm now stuck with a system that can't be backed up and v28 won't delete the offending directory.
Any suggestions?

Yes I guess that has something to do with different Kernels I use in v28 and v29.
I heard from others that they had to do a format data in order to get that working corretly.

 

[BillGoss]

Yes I guess that has something to do with different Kernels I use in v28 and v29.
I heard from others that they had to do a format data in order to get that working correctly.

I tried to avoid doing a format, but ended up having to do it.
One of the things I tried was restoring a v29 backup from a different phone (but same OS). But that resulted in my phone ending up with the other phone's MAC address for the WiFi connection! I have no idea why that happened as the backup was only of /data. It's weird.

I'm in the process of setting up my phone again. But I can confirm that v29 can backup and restore /data.
And ORS works nicely on v29.

Thanks very much for this. It's great to have a backup that works on Android 14.

 

[AmericanRebel]

I remember awhile back one of your recovery zip files could be flashed in magisk. Is it possible to flash the latest fox recovery in magisk? I ask because there's a glitch in A14. Fastboot seems to be missing. I found a workaround, so I was able to flash the patched boot.img but it won't let me boot your recovery. I could probably flash the orangefox recovery, but I don't really want to tread in unknown waters too much and end up bricking my phone and starting from scratch.
UPDATE: I went ahead and flashed OrangeFox. Everything seems to be working fine. So I flashed the EU firmware flasher (just to enable dual SIM) but it didn't enable, and I'm still getting the Bootloader unlock warning. So I flashed the firmware flasher for 13.1, but as I figured, the phone wouldn't boot, so I reflashed the firmware flasher for OOS 14

 

[Rootk1t]

I remember awhile back one of your recovery zip files could be flashed in magisk. Is it possible to flash the latest fox recovery in magisk? I ask because there's a glitch in A14. Fastboot seems to be missing. I found a workaround, so I was able to flash the patched boot.img but it won't let me boot your recovery. I could probably flash the orangefox recovery, but I don't really want to tread in unknown waters too much and end up bricking my phone and starting from scratch.
UPDATE: I went ahead and flashed OrangeFox. Everything seems to be working fine. So I flashed the EU firmware flasher (just to enable dual SIM) but it didn't enable, and I'm still getting the Bootloader unlock warning. So I flashed the firmware flasher for 13.1, but as I figured, the phone wouldn't boot, so I reflashed the firmware flasher for OOS 14

Did you try to flash OOS14 beta bootloader (abl.img) to enable dual SIM?

 

[Wishmasterflo]

Did you try to flash OOS14 beta bootloader (abl.img) to enable dual SIM?

That does not work with OOS14 !!

 

[ghatothkach]

hi

I updated firmware to OOS14, and the current version of recovery won't work. Does anyone know of an OOS14.x based recovery?

I am able to boot to the OOS14 recovery image but all the custom recoveries I have tried so far have not worked, all of them seem to be 13.x based.

I need to get into fastbootd mode somehow to complete the partially finished flashing process, OR somehow rollback to 13.1 firmware so this recovery would work. No idea how to do that.

G

 

[BillGoss]

hi

I updated firmware to OOS14, and the current version of recovery won't work. Does anyone know of an OOS14.x based recovery?

I am able to boot to the OOS14 recovery image but all the custom recoveries I have tried so far have not worked, all of them seem to be 13.x based.

I need to get into fastbootd mode somehow to complete the partially finished flashing process, OR somehow rollback to 13.1 firmware so this recovery would work. No idea how to do that.

G

I've been able to use TWRP on stock OOS 13.1 and 14 (https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/).
But on Los 21 (Android 14 on OOS 13.1 firmware) I have to use Orange Fox V29.

So it seems to me that the recovery depends more on the ROM installed than the firmware.

 

[ghatothkach]

Update:

Don't know what exact sequence of steps I did, but I was able to flash the boot and dtbo and some other images from the vanilla 13.1 firmware and apparently some part of the firmware rolled back to 13.1, then I was able to get Orange Fox v29 to boot, and then used the firmware update patch, followed by LOS21-μG and it all worked out well

I now have LOS21-μG on both a and b

Would love to see a version based on the firmware of KB2005_14.0.0.301-EX01_20240305 or later..

G

 

[amine tenes]

Hello friend I want the language file so that I can translate it into Arabic