yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
OrangeFox R10.1_3 Stable released

I have released OrangeFox R10.1_3 Stable.

Downloads

:

OrangeFox download site: https://files.orangefox.tech/OrangeFox-Stable/lavender/

Sourceforge: https://sourceforge.net/projects/orangefox/files/lavender/

Changelog (General for R10.1)

: https://wiki.orangefox.tech/en/changelog#orangefox-r101

Device-specific changes

:

- New kernel

- Several optimisations and fixes

- Release date: 05 June 2020

FAQ and Guides

: https://wiki.orangefox.tech/en/guides
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] jackk9:
Great, thank you! On which ofox are you? Besides, are you using any Gapps package and do you have to reflash it after the ota?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] dedavlade:
Latest. I am using Gapps (pico), you don't need to reflash them after an update.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] iPAQ 6515a User:
Thanks DarthJabba9

A question, is this version for Android 10 and above only (or is it good to go with Pie, too)?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
I personally wouldn't recommend using it with a Pie ROM (although I must admit that, when I tried it with MIUI 11, everything seemed okay, and (to my great surprise) even the incremental OTA update worked fine).
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] ahadrox:
Hi, I think decrypting thing is broken in orange fox recovery. When I boot to ofox recovery it asks for pin code to decrypt data. But if I hit back button it goes directly to the internal storage and I can do whatever I want without even putting my pin for decryption. I think it's a security risk. Please look up to that. I am using the latest recovery with Pixel Experience ROM.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] iPAQ 6515a User:
Thx

I remember the prev had 0 problems, too. Just to keep it safe, I will wait for the official MIUI update to Android 10 (still, no official release for lavender)
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
For the avoidance of doubt, there is absolutely nothing wrong with OrangeFox, and absolutely nothing is broken in the recovery. If you have a borked encryption, please don't blame the recovery for this. You might want to format your data partition, and let the ROM encrypt properly.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Azoset:
I can confirm this from the latest LOS official Rom.

Back button works but nothing can be changed without pin.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Peter1212:
[MENTION=5850987]DarthJabba9[/MENTION] Any possible recommendations on taking nandroid backups? Every rom I try just keeps giving me the creattarfork() failed and that's about it. At least the current recent roms from March and up ahead. I had Havoc OS from feb and it works fine to backup and restore both. I can't update it because the newer builds have been implemented with fbe, and now all of the current roms are built with the same encryption. Not sure if it's due to this change or what, but the last 5 or 6 roms I just tried, all gave me the same error. Yes I formatted over and over again. I wiped all the partitions, then formatted, even repaired (if it even does anything much), rebooted to recovery and installed the rom. But to no effect. It's funny because the Havoc build from feb (maybe pre-feb) works fine as normal.

If there's not a way to do a nandroid backup, anything else you could recommend aside from Migrate/TB app backups. What about pulling the data partition, would pushing it back on a new install work (after wiping the old data partition, of course)

EDIT: I think I got the backup through your current recovery build. R10.1.0_R3 but it shows me some error about "Unable to locate "/system" partition for backup calculations". It shows that twice, at the beginning and before starting the backup, but it finishes normally. I can also restore it up and boot it normally. Woah. Need some clarification here if it was just my luck or your genius prowess working on some fix lol not sure if it would give any issues later or not or anything in the rom but -shrugs- needs more testing. I'll test it out more once I set up my rom tomorrow. Too tired right now. Yep, boots fine at least heh

This is what I did, not sure if I need to repeat some steps for sure or not, but I do them in series as I got it to work.

1) Wiped all partitions Cache to Data (system/vendor included)

2) Formatted data. Rebooted into recovery.

3) Installed the latest/current (at the moment of this post, R10.0.1_R3) version of OF recovery.

4) Rebooted into recovery once again.

5) Wiped all partitions once again.

6) Installed Rom (tried it on ShapeShiftOS_Magikarp-1.0.3_lavender-10.0-20200603-2318-UNOFFICIAL and Bliss-v12.8-lavender-OFFICIAL-20200608)

Booted into system without wiping cache\dalvik-cache

Booted back into recovery. Took a new backup of data partition (at that time it was only just 45 mb or something, varies in each rom)

Backup was successful with the error I posted above.

Afterwards, I just rebooted back in system to see if everything was fine, it was. Then booted back and restored the backup, which it did. And restarting into system once again it worked like a charm. Also, encryption was working fine. Not sure if it's already fixed or not but if it was, then oops, late to the party but glad I got the backup working again. Pretty sure some of the steps can be skipped though.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
:eek: What a drama you have encountered! This is a most unusual experience (indeed, I have never seen anything quite like it before). The error about being "Unable to locate "/system" partition for backup calculations" is also one that I have never encountered, on any recovery, on any device. My conclusion is that something (possibly a ROM) has well and truly borked your partitions. If everything is fully recovered now, that is well and good. Otherwise, you might have to use "the nuclear option" ...
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] hyborian:
Do you get the same error if you use the official TWRP ?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Peter1212:
Lmao man, really unsure what happened and what did not, but it's something worth taking a look into or am I wrong? I wonder if others would try to backup using this way perhaps. About the Rom having borked anything at all, idk, because both times I formatted my device, and then did all those steps. I'll test some more out and see if I can do it in lesser steps or not today. Maybe it's just the recovery and somehow it makes it work. Anyways, I also tried mounting the system before taking the backup. Again it showed me the error and surprisingly when I went into the mount options, system was unmounted. I mean, for whatever worth it is, it could be the possible solution to overcome not being able to take backups before.

I'll test some more out in a little bit and post my results here.

EDIT: Hosh, taking backup of system/vendor or any other partition does not give that error. Only on data. It's like during backing up data it unmounts the system itself.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
As I said, something is borked, and formatting data doesn't seem to be curing it - perhaps you are trying to cure the wrong thing? Don't manually mount system. System does not need to be mounted randomly, and, if I were you, I would leave it well alone. Anything that needs to write to system will mount and unmount it when required.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Peter1212:
Uhm, not sure why you keep saying that it's borked? Or whatever? Are you implying that it shouldn't give that particular error or that it shouldn't backup at all, regardless of the error. Simply googling for "Unable to locate "/system" partition for backup calculations" results some issues where people had that same error, albeit for different partitions instead of the system. So, I do reckon that it's not supposed to be happening perhaps.

Before, I was on the R10.0_2 Stable for lavender, that's where I took the old backup for Havoc (while it was still in FDE, v3.1 or v3.2). Next month I switched to the R10.1_02 Stable for Lavender. I hadn't updated the recovery to the 01 version before, and the last time I updated the recovery was in December, hence I was still on the R10.0_02 version of it. This is also the time, most roms started to convert to FBE and I couldn't take backups at all for the data partitions. But that was a month ago. So if anything is borked by your means, it should be something that the previous version of recovery did. I presume that it's still using the TWRP 3.3.1-0 (maybe with the latest commits for it perhaps). Bottom line is, backup is back again, even though with the error. Backup restores fine. system partition and others backup normally without any errors, and restoring them works fine too. Phone reboots normally after all those restores too.

https://xdaforums.com/showpost.php?p=71533829&postcount=1601 Here you can see that the error (although on bacon) is for other partitions yet the user says that they finish successfully.

Just tried it out, no error with TWRP at all. Backup runs fine. No issues. And saw that it was updated back in december only. Makes me wonder if I were on that recovery back a month ago, I wouldn't have been so troubled.

EDIT: I'm going to try again with the old OF recoveries and give my results. If you want the logs I can provide them. If not, that's fine as well. I am just glad that the backup is working once again for now.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
Indeed!

Perhaps, perhaps not - anything is possible in theory - except that other people (literally tens of thousands on lavender) have been using all previous versions of the recovery. This is the first time that that anyone has reported this kind of error on OrangeFox (on any device). I take backups several times every week, as I test the recovery on all sorts of ROMs, and the recovery has yet to bork anything on my phone. So I can confidently say that the problem is not due to anything that OrangeFox has done. If is caused by OrangeFox, I think that I would be the first to experience it.

That is all good. But the error should not happen.

:good: Please test only R10.1_2 and R10.1_3.

Logs would be extremely useful, because at the moment, anything said is pure speculation.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
The official TWRP was only released less than 2 weeks ago. And if you look closely, you will see that the device tree is based on my OrangeFox tree.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Peter1212:
[MENTION=5850987]DarthJabba9[/MENTION] Okay. I tried the alpha version just being curious, and the error doesn't occur on it at all.

The R10.0_01 and the R10.1_01 both gave the error, but the R10.0_01 did finish it successfully, restoreable backup. In case of R10.1_01 I ended up having the createtarfork() failed once again. R10.1_02 surprisingly, for some reason now created backup successfully with the error still, while it wasn't doing so previously (when I had updated from R10.0_01 to R10.1_02, this time around it was R10.0_01 -> R10.1_01 -> R10.1_02) Also, note that instead of flash I am doing a fastboot install.

Curiosity got the better of me and I tried using the alpha version. It works the same as TWRP without giving me any errors.

I can give the logs, (recovery logs I guess, saved inside the FOX\logs folder or something else?) But I'd like to know on which version of it should I give you.

And if so, should I also replicate the period when it wasn't giving the /system error but only the error 255/createtarfork() failed error in R10.1_02?

Alas, since you mentioned that it's a rare scenario and you haven't ever experienced it on lavender, maybe I should just drop it up. I am happy with the backups back again, which is what matters. It would be something else if someone was able to reproduce it first and if it occurred on more devices, I would have been glad to provide the logs more too, cause right now it's just me and depends/varies on situations I don't know.

EDIT: I see, thanks for that then. I didn't know about the lavender official twrp release date earlier.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
I have searched Google for this kind of "Unable to locate ... partition for backup calculations" error, and it is rare. But its occurrence also seems to be random, and no solution ever came out (other than to delete the configuration file and reboot TWRP to start with clean configuration)! There seems to me to be no rhyme or reason for when and where it occurs.

In any case, with respect to the logs, perhaps you might want to just zip the entire /sdcard/Fox/logs/ folder, and send it to me by PM (or give me a place from where I can download it). I will try to see if I can learn anything useful - but I can't guarantee that any clear solution would arise out it, especially since it shouldn't occur at all.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] hyborian:
Are you using Lavender phone, because the latest TWRP was released on May 31, 2020, version 3.3.1

Anyway, at least your OF now works ...
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Peter1212:
Yeah, DJ pointed me out on it too, I didn't know. Thought it was released back then only. Sorry for my mistake. Also just sent him a PM regarding it all, surprisingly, after being through and forth with the recoveries and all the formats, that error is gone. The dreaded createtarfork() failed occurred only on the R10.1_01 but the other two were fine. I'm gonna stick with the alpha for now, love the design changes in it heh.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
You logs of R10.1_1 backup show the specific directory problem that I referred to in my PM - "failed to lookup tar policy for '/data/per_boot' - '6f9404b3b6a02489'". My solution to that specific problem was in R10.1_2, and has also been merged by TWRP into their upstream code. There are other directories that can cause the createtarfork() problem during backup (mainly in dual apps or multiuser setups), and R10.1_3 tries to avoid those directories causing any problem. Of course all these latest developments are in the R11 Alpha too.

I am glad you are liking the R11 Alpha. Just remember that it is an Alpha, and treat it as such. And any discussion about Alpha releases should be in our TG beta group, not here.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] yodanutz01:
Hello my friends! I use previous OrangeFox release with Redmi Note 7 and Pixel Experience Plus ROM.

I have an issue: After I installed the ROM and booted, made all my set-ups, I wanted to boot to recovery to install Magisk. But the recovery sees my phone as encrypted no matter what, I can't install anything from recovery, not even ROM incremental updates. When I reboot to Orange Fox, the data is encrypted, all I see is scrambled characters names. The problem is that it doesn't prompt me for the password to decrypt data. I tried removing the PIN or passwords from my phone and go back to recovery. The same result, the data is encrypted!

What can I do in this case? Thank you!
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
https://wiki.orangefox.tech/en/guides/encryption
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] yodanutz01:
Ok, so i have to format DATA partition. After that I'll flash Pixel Experience Plus ROM again. After booting and setting up the ROM, I should't have any more problems with OrangeFox encryption when booting recovery, right?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
Just format the data partition and reboot the PE ROM. PE will encrypt again in its own way while booting up, and that should suffice (assuming you didn't tick "Disable forced-encryption" when flashing PE in the first instance).
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] vlouis:
Internal Storage recovery backup

I'm using latest Orange Fox version (10.1_3). Tried to backup data without encryption: I removed the pin/fingerprint, successfully make a "Data" and "Internal Storage" backup and restored later after reinstalling the new version of same rom (EvolutionX, changed encryption). More info here: https://xdaforums.com/showpost.php?p=82830165&postcount=447

The strange thing is, I tried to backup the "Internal Storage" after restoring the encryption, but missing from available elements.

My question is, if the data and Internal storage use same (FBE) encryption, why I can backup the data and can't backup the "Internal Storage", if the encryption is active?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
Who said you can't?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] vlouis:
Thank you for your answer. I think I found it.

The Internal storage need to be mounted manually (Menu-Mount...) then will appear in "New Backup" Partitions list.

My programming knowledge is very limited, but I think this list is populated at startup, before entering the pin/password. When the data partition not encrypted, the internal storage is "detected" at startup and added to "New Backup" partitions list. If encrypted, only after mounted it manually.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] anon1135:
I had a bug where torch would turn on once I enter recovery. Is that normal?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] anon1135:
Any ideas what could be the problem if it's user related?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
No idea.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] JR Bautista:
how to fix failed to map error?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
What is that?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] JR Bautista:
trying to install miui 12. but it fail. error says failed to map (path of file)

miui zip file comes from sdcard not in internal

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM ----------

"Failed to map file (Directory/Filename such and such) Error installing zip file (Directory/Filename such and such)
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
All this means nothing to me. You should post the logs.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Dog4:
I'm on R10_3.

Everythings works fine and the OTA Update from MIUI EU 12 Dev Rom works to.

Thanks for this great recovery!
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Finki:
Hi,

I am currently running TWRP 3.3.1 on my lavender with Xiaomi.eu-ROM 11.0.7.0 PFGCNXM. Now I want to update to the latest Xioami.eu-ROM 11.0.2.0 QFGCNXM (Android Q).

I read some hints that I have to use OF for updating instead of TWRP, so I would like to change to OF firstly. But there are threads about encryption-errors and solutions by formating data partition, so I am not sure if I could get some problems. And I don't want to format data and have to install all apps and settings again.

My phone is encrypted, so I have to enter the password after each reboot. In the past I always removed the encryption before I flashed a new Xioami.eu-ROM and encrypted it again after flashing.

So would this work to update to Android Q-ROM?

Remove encryption in Xiaomi.eu-ROM developer settings

Reboot to TWRP 3.3.1 recovery

Flash OrangeFox-R10.1_3-Stable-lavender.zip

Reboot to OrangeFox recovery

Flash Xioami.eu-ROM 11.0.2.0 QFGCNXM

Thanks.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Daenjel:
Hi, I've an issue today, I hope someone could help me;

I used OF recovery to update from MIUI 11(xiaomi.eu) to MIUI 12(xiaomi.eu), after a successful update the device rebooted and started asking for a password to initiate the OS over a black screen, I entered my screen pin but it didn't worked, rebooted to OF recovery and also asks for a password to decrypt, my screen password doesn't work in here too, I don't know what to do can someone help me?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
Long story: https://xdaforums.com/showpost.php?p=79771468&postcount=2

Short story: you have flashed a ROM using a different kind of encryption from the one you had before. You have to format your data partition - and you will lose all the contents of your internal storage. If you didn't make backups of your internal storage before embarking on this enterprise, then ....
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
Then you had better stay with your current ROM, because moving from Android 9 to Android 10 will almost certainly require formatting the data partition. Of course, you can try your luck, and you may end up being lucky - but don't say you weren't warned ...

For more details, see: https://xdaforums.com/showpost.php?p=79771468&postcount=2
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Dog4:
Finki and Daenjel

If you change from Android 9 to 10 or from MIUI11 to 12 Dev ROM you must Format your Data and install all Apps and Settings again. A little bit helpfull is to use Titanium Backup. After flashing a new ROM you can Install your Apps from Playstore and after that you can restore your AppData with Titanium Backup.

I'm on EU 10 latest Stable and Ofox R10.1_3, everything works fine.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Finki:
Thanks DarthJabba9 and Dog4.

So I really have to do the big thing again? Puh... Titanium is helpful, but there are many things which have to be done by hand afterwards.

What about a OF data-backup? Would that help to get around the new install of all apps after formatting data and flashing the ROM?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Dog4:
From Android 9 to 10 no.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Finki:
So a data-backup does not make any sense? Is it not a file-based backup in OF?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Dog4:
The OF backup is for you only. If something goes wrong you can restore the Phone with your Backup.

I can very good understand you but there is no other way if you wanna change to 10. You have to install all Apps again and you can try to restore your Data with Titanium Backup.

If you wanna try TB don't forget to copy the TB Folder after you have made all Backups from the internal storage to your sd card.

About Backup and Restore read this. https://wiki.orangefox.tech/en/guides/backups
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] SaBo_05:
I flashed OR recovery through fastboot but when I reboot to recovery i get miui recovery. I even tried flashing twrp even it does not work. I'm running in miui 10.3.5.anyone please help
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] PYCON:
After full backup, phone hangs up on Redmi logo :confused:

What's the purpose of an alternative recovery that cannot do major job of TWRP ?! :confused:
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] trantrungtu:
how to backup kernel MIUI with orangefox
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] dd721411:
[MENTION=4212059]trantrungtu[/MENTION] Sorry but what do you mean by "kernel MIUI"? Have you read the manual provided?

Xin lỗi nhưng bạn nói "kernel MIUI" là sao? Bạn đã đọc bài hướng dẫn chưa?

[MENTION=356616]PYCON[/MENTION] Could you please describe the steps you did and provide error logs so that developers can look into this issue?

Developers and testers must've spent thousands of times testing OFR so please don't disregard the time and effort they've been putting into this project! :(
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Bananabill0002:
Hello i want to ask something: if I try to install a rom with a rollback protection this recovery will advise me that the telephone may not boot properly or it does and the phone go in boot loop?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
You are perfectly welcome to return to TWRP.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
No, and No.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] DarthJabba9:
How did you "reboot to recovery"?