Tap on Menu, and tap on the settings icon at the top right of the screen. You will see all the
Really, you should not ask this question at all. But if you insist on asking, the answer is that there are many possible reasons;
- We don't have the device (in which case, you are welcome to donate a device, or donate money, or build the recovery yourself);
- Nobody is interested in maintaining OrangeFox for the device (in which case, you are welcome to build for yourself, and, if successful, you can request to become an official maintainer, and we will consider the request in due course);
- A working build has proved impossible, for any number of reasons (in which case, nothing more can be done - but you are welcome to try to build it for yourself);
- The device was supported before, but the maintainer no longer wishes to maintain it (in which case, you are welcome to build it for yourself, and request to become a maintainer for it);
- Other reasons;
The "long and short of it" is that if it doesn't exist, there is a good reason why it doesn't exist.
- You have simply asked the previous question in a different way. The answer is exactly the same as the answers just given above.
- Go to Menu -> Manage Partitions -> Data -> Format Data and then type "yes".
- When you have finished formatting your data, reboot OrangeFox before doing anything else.
- Formatting data will also delete the contents of your internal storage - so you had better backup your personal files (eg, photos, music, etc) before formatting. If you do not take a backup of your files, there will be no way of restoring them after formatting.
- Look at the log screen in OrangeFox, and see what messages are there. Follow any recommendations that you see there.
- Get the logs via "adb" (see below) and look for things like "
Android Rescue Party trigger" or any other message that may explain why you have just been dumped back to OrangeFox, and follow the instructions given.
- Assuming that other people can boot OrangeFox properly (which will definitely be the case, if you are using an official release) and that you are trying to boot into OrangeFox the correct way, then the problem is
on your device - either your ROM, or your firmware version, or the specific version of your device. So you will need to supply
full details about your situation.
- Supply all the information prescribed in the Reporting problems page.
Tap on "Wipe", tick Dalvik/Art Cache, Cache, Data, and swipe to wipe.
- If you have an old Xiaomi device, running an old MIUI firmware (based on Android 6.x, 7.x or 8.x) then this might be possible.
- If your MIUI firmware is based on Android 9 or later, then it will not be possible. Why? Because newer Xiaomi firmware updates in newer MIUI ROMs (based on Pie or later) will replace your bootloader with one that cannot "hotboot" a recovery image.
- Your only option in such a case is to flash the recovery image, with "fastboot flash ..."
- This is not an OrangeFox issue, so please do not come to the OrangeFox groups to ask about it.
- Because the maintainer has decided that you should not try to wipe them manually.
- Hint: just leave this issue, and move on with life. There is no reason why you should have to manually wipe system or vendor.
- That's tough.
- The moral of story is - do not forget your password/pin. We will certainly not assist you in recovering the situation unless you can
prove beyond a shadow of doubt that the device is actually yours.
- Why? Because if we were simply to assist everyone who comes to our forums saying that they forgot their password/pin, then the OrangeFox security feature is essentially useless.
There are a variety of ways:
- Tap on "Menu -> More -> Copy Log to SD", and swipe. This will copy the logs to your internal storage
- Connect a PC to your device via adb, and run the command:
adb pull /tmp/recovery.log (the "recovery.log" file will be downloaded to the location from which you ran this command, and you can then attach the file to your post)
- Send the contents of the device's /sdcard/Fox/logs/ folder(put them all in a single zip archive) - as long as at least one of them contains a log showing the problem that you have encountered.
That is unfortunate - but there is nothing that can be done about it - unless and until somebody decides to update the Aroma project. This also applies to Aroma GAPPs.
- Provide the logs and screenshots
- Provide a full explanation of precisely what has happened, and precisely how you got to that point.
- If you do not provide both of these, then we will simply ignore any report of any problem. So, it is advisable to (a) learn how to take logs before trying anything, and (b) always take the logs before rebooting after using the recovery.
- Note: just posting a screenshot is totally unhelpful - and just saying that it "doesn't work" is totally unhelpful. You must post the recovery logs
¶ How can I know the maintainer for my device?
Tap on Menu -> (Settings icon) -> About