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

3arthur6

Senior Member
Sep 15, 2011
413
857
123
Thank you for this recovery project... I was following the official telegram thread and did not know this thread already existed here...
Great work. Love the options...
Couple of questions
1. I got pin not correct in lock screen. The fix in the recovery ( add-ons) did not help. I had to delete some files in data/system to clear the password.
Then I got into the issue of samsung password not working... Had to spend sometime cleaning up the storage of a bunch of smasung apps to sign in again.
Is there a better solution to this?

2. Is there a way to show the zip files as default instead of all files in the file section. Most common reason why I go into recovery is to flash a file. Having the above option will be very useful...

Once again appreciate your work
Yep. Because it's not a fix, it prevents this issue. Once you got this issue, it's not easy to get rid of it..

Or maybe you talk about the password deleter addon?
If so it would be nice if you remember which deleted files really removed the password to fix the addon.

If not sure check the box when flashing kernel, you will never again have this **** with it.
I will add the box option in img flash page with next release.

About showing only zip (as well as only img) there is an option by taping the first icon in top right.
 

3arthur6

Senior Member
Sep 15, 2011
413
857
123
@Arteush
What do you mean by dirty zip ?
Not dirty zips, "dirty" scripts.
Lot of zip scripts need a tool (busybox) which is not but has his egual (toybox, which I provide) include in aosp.
And there is some other ways to execute the same tasks they want no matter environment in which they are (more proper, hence this "dirty").
But I do my best to add a support for them as unfortunately it became a common way to write zip scripts.

Edit:righter explanation
 
Last edited:
  • Like
Reactions: kramer04

Techvir

Senior Member
Jul 13, 2007
3,515
886
253
@Arteush after flashing a kernel with this TWRP, I got the lockscreen issue. I was able to overcome by deleting the lock screen.db file from data/system in twrp.
However, since then I am unable to set a pin/password for the lock screen. When I enter it , it confirms it but the lockscreen still is in swype option.
When I try to add biometrics it asks for the password/pin and when I enter it, it says its wrong. When I reboot the phone, the pin gets reset.
I have tried a lot of things including odin flashing a full new rom. Now even on stock unrooted device I cannot set a lockscreen pin.
I restored the efs folder and still no respite.
Can you please suggest a way to overcome this issue ?
 

3arthur6

Senior Member
Sep 15, 2011
413
857
123
@Arteush after flashing a kernel with this TWRP, I got the lockscreen issue. I was able to overcome by deleting the lock screen.db file from data/system in twrp.
However, since then I am unable to set a pin/password for the lock screen. When I enter it , it confirms it but the lockscreen still is in swype option.
When I try to add biometrics it asks for the password/pin and when I enter it, it says its wrong. When I reboot the phone, the pin gets reset.
I have tried a lot of things including odin flashing a full new rom. Now even on stock unrooted device I cannot set a lockscreen pin.
I restored the efs folder and still no respite.
Can you please suggest a way to overcome this issue ?
Sorry for that.
Which kernel?
Flash the dedicated addon for this issue though orangefox, factory reset and it should work.
 

Techvir

Senior Member
Jul 13, 2007
3,515
886
253
Sorry for that.
Which kernel?
Flash the dedicated addon for this issue though orangefox, factory reset and it should work.
White wolf
I tried that too but issue still there...
As I said I did an odin flash including nand erase and still the issue.
Once again the issue is the inability to set a lockscreen password... I have never seen this... How is it possible that the issue is still present after a nand erase ?
 

Timtown

Senior Member
Feb 27, 2007
571
287
93
Wake Forest, NC
So far, very good.

I'm enjoying the product thus far. I do have some questions.

I performed a back-up (a.k.a. Nandroid) and was impressed with the back-up speed. However, when I looked at the file sizes as compared with my most recent TWRP back-up, there was a significant difference. OrangeFox was about 6 gigs, TWRP was about 15 gig. In all honesty I'm sure this is my error as I've become so familiar with TWRP but, it would be helpful if you could please provide some guidance as to what to include in a OFR back-up to enhance the odds that an OFR restore will actually restore the device.

I do not need code-line directions, just recommend which boxes to tick. ;)

Thanks in advance for any help you can provide.
 

bober10113

Senior Member
Mar 12, 2017
4,457
1,617
113
White wolf
I tried that too but issue still there...
As I said I did an odin flash including nand erase and still the issue.
Once again the issue is the inability to set a lockscreen password... I have never seen this... How is it possible that the issue is still present after a nand erase ?
maybe white white wolf uses dirty scripts?

:cowboy:

i was sure he was a clean guy.
 

3arthur6

Senior Member
Sep 15, 2011
413
857
123
White wolf
I tried that too but issue still there...
As I said I did an odin flash including nand erase and still the issue.
Once again the issue is the inability to set a lockscreen password... I have never seen this... How is it possible that the issue is still present after a nand erase ?
Humm
Even with stock kernel you can't set a password? Not sure to understand.
Make a clean odin flash, install a custom recovery and the kernel, maybe magisk and go.

Since some time we have a security stuff which check that system and kernel security versions match.
WW breaks the checking stuff in your system. So when you clean flash with Odin you reinstall this crap and you have to flash the kernel zip again.
 

3arthur6

Senior Member
Sep 15, 2011
413
857
123
I'm enjoying the product thus far. I do have some questions.

I performed a back-up (a.k.a. Nandroid) and was impressed with the back-up speed. However, when I looked at the file sizes as compared with my most recent TWRP back-up, there was a significant difference. OrangeFox was about 6 gigs, TWRP was about 15 gig. In all honesty I'm sure this is my error as I've become so familiar with TWRP but, it would be helpful if you could please provide some guidance as to what to include in a OFR back-up to enhance the odds that an OFR restore will actually restore the device.

I do not need code-line directions, just recommend which boxes to tick. ;)

Thanks in advance for any help you can provide.
Thanks!

Oh yep this should be approximately the same size!
You have to use this recovery in the same way as you used twrp.
The safer is to check all box when you do a backup.
Maybe no need for cache.

If you need more feel free to ask.
 
  • Like
Reactions: bober10113

3arthur6

Senior Member
Sep 15, 2011
413
857
123
maybe white white wolf uses dirty scripts?

:cowboy:

i was sure he was a clean guy.
Lmao didn't you see that you are the only one who claims he can't flash his stuff?

Take a look in WW script, it is the kind of which can be flashed anywhere. Who knows, you could be inspired.
 

bober10113

Senior Member
Mar 12, 2017
4,457
1,617
113
Where did you see that? Yes they are
just trying to figure out why the csc pack im flashing works on geiti94's twrp and not on both twrp you cooked. it worked 3 or more versions ago on your regular twrp but since the ODM issue was fixed, now the script issues are back. flashing custom csc fails just like before.