[RECOVERY][SM-N960F/DS/N] OrangeFox Recovery R11.0 [UNOFFICIAL]

[3arthur6]

Hi,
is there an update with the new official TWRP?

Thank you

Hey
Not sure to well understand what you mean.
Actually official twrp and orangefox use pretty much the same recovery source base (excluding orangefox overlay so).
So it is, and was, already up-to-date.
I even added some commits which are in review phase and could be merged with official twrp source in the future. This is an advantage of not being official, keep the freedom to include some mods.

 

[HorstiG]

Hey
Not sure to well understand what you mean.
Actually official twrp and orangefox use pretty much the same recovery source base (excluding orangefox overlay so).
So it is, and was, already up-to-date.
I even added some commits which are in review phase and could be merged with official twrp source in the future. This is an advantage of not being official, keep the freedom to include some mods.

Great, thank you.

Sent from my SM-N960F using XDA Labs

 

[HorstiG]

I'm just wondering, OF img has 31 MB, the official over 40.

Sent from my SM-N960F using XDA Labs

 

[3arthur6]

I'm just wondering, OF img has 31 MB, the official over 40.

Yep I disabled lot of unused kernel stuffs and use lzma compression to reduce final size

 

[kramer04]

@3arthur6 Hello

i would like to make a zip file but i need to test if Orange Fox or TWRP is installed
Is there a test command to put in .sh file to know this ?

 

[3arthur6]

@3arthur6 Hello

i would like to make a zip file but i need to test if Orange Fox or TWRP is installed
Is there a test command to put in .sh file to know this ?

Hey
You can use getprop
I don't remember the properties names but there are some orangefox specifics, launch a 'getprop|grep fox' from adb shell in recovery to find them

 

[3arthur6]

New release
Updated to OrangeFox R11.0

 

[[email protected]]

Not sure what happened but here is the summary:
1.flashed 2.0 recovery, all was ok booted fine,
2.later rebooted and got an error "can not boot normal mode: invalid kernel length" and I can only access download mode.
3.flashed via odin v1.92 of fox, all good, no errors, there never were errors before


Reflashed v2.0 again, boot and rebooted, I see same thing.
I'm on F2FS and don't think this might be the cause.


Anyone else having this problem?

Edit:
I flashed 2.0 via TWRP since its a flashable zip file, somehow this writes to my boot partition giving me the error of Invalid kernel length and I say this because after I flashed the recovery via download mode to fix the error it keeps booting to recovery unless I re-flash my kernel.

 

[3arthur6]

Not sure what happened but here is the summary:
1.flashed 2.0 recovery, all was ok booted fine,
2.later rebooted and got an error "can not boot normal mode: invalid kernel length" and I can only access download mode.
3.flashed via odin v1.92 of fox, all good, no errors, there never were errors before


Reflashed v2.0 again, boot and rebooted, I see same thing.
I'm on F2FS and don't think this might be the cause.


Anyone else having this problem?

Edit:
I flashed 2.0 via TWRP since its a flashable zip file, somehow this writes to my boot partition giving me the error of Invalid kernel length and I say this because after I flashed the recovery via download mode to fix the error it keeps booting to recovery unless I re-flash my kernel.

Thanks for the details!
Same problem happen on S9, I will take a look in coming hours

 

[3arthur6]

New release is up with fixed boot issue thanks to @[email protected] for finding the bad scenario

 

[Cedoresti]

i dont understand how this its only for exynos if you find only for note 9 qualcomm on website: https://orangefox.download/en/device/crownqltechn

 

[3arthur6]

i dont understand how this its only for exynos if you find only for note 9 qualcomm on website: https://orangefox.download/en/device/crownqltechn

Actually you will find official releases in OrangeFox website.
Exynos N/S9 aren't officially maintained so I just share my personnal/unofficial builds here

 

[SammyTRK]

@3arthur6 First, Thank you for this recovery it is nice. :good:

But, I am getting this message when copying setting permissions in the system partition.

WARNING: linker: Warning: couldn't read "/system/etc/ld.config.txt"

It seems it needs to be pointed to /system/etc/ld.config.29.txt (or maybe /system/system/etc/ld.config.29.txt) but I'm not sure how or if it's even necessary.

I unpacked the img and found this file init.recovery.ldconfig.rc

#Causes clashes if recovery and ROM are based on different android versions - so disable
#on fs
#    export LD_CONFIG_FILE /sbin/ld.config.txt

I am not sure if I should un-comment that and leave the path pointing where it is or maybe point it to /system/etc/ld.config.29.txt.

 

[Detonatte]

How flash? Because iz zip and Odin no see
3arthur6 backup and restore work perfect???

 

[Yillié]

Maintainership

Actually you will find official releases in OrangeFox website.
Exynos N/S9 aren't officially maintained so I just share my personnal/unofficial builds here

Why don't you apply for official maintainership?? You can contact Mr.Yacha on Telegram and apply for maintainership.

 

[3arthur6]

@3arthur6 First, Thank you for this recovery it is nice. :good:

But, I am getting this message when copying setting permissions in the system partition.

It seems it needs to be pointed to /system/etc/ld.config.29.txt (or maybe /system/system/etc/ld.config.29.txt) but I'm not sure how or if it's even necessary.

I unpacked the img and found this file init.recovery.ldconfig.rc


I am not sure if I should un-comment that and leave the path pointing where it is or maybe point it to /system/etc/ld.config.29.txt.

It is related to busybox but should not cause any problem.
Btw your screen shows no rom. Are you on Android 9 or 8? Or did you not have a rom installed at the time?

How flash? Because iz zip and Odin no see
3arthur6 backup and restore work perfect???

Flash twrp first when this zip on twrp.

Why don't you apply for official maintainership?? You can contact Mr.Yacha on Telegram and apply for maintainership.

I implemented few comsetic and samsung related changes which can't be applied with official release. It's more simple for me to share these builds.

 

[SammyTRK]

It is related to busybox but should not cause any problem.
Btw your screen shows no rom. Are you on Android 9 or 8? Or did you not have a rom installed at the time?

I am running SuperStable Rom android 10. It always says no rom.

 

[3arthur6]

I am running SuperStable Rom android 10. It always says no rom.

Interesting.. It should not!
You can try to reinstall the rom after checking the box in settings "reboot to recovery without SAR mount". It could also be related to the linker warning you faced.