[RECOVERY] OrangeFox Recovery for OP8 Unofficial [BETA2][2030203] - OnePlus 8 / 8 Pro & 8T Cross Device Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You now the procedures, else ask on the thread!
Download Links to Beta 2:
https://devuploads.com/n7fwy5sxm7ez -> OrangeFox-deepongi-op8-ext4-b2.img - 100.0 MB
https://devuploads.com/vxtjmn4yfkhk -> OrangeFox-deepongi-op8-ext4-b2.zip - 61.8 MB
https://devuploads.com/1rnsgyrbngox -> OrangeFox-deepongi-op8-erofs-b2.img - 100.0 MB
https://devuploads.com/rx8kzcmoajuq -> OrangeFox-deepongi-op8-erofs-b2.zip - 65.0 MB
(Please disable any adblockers downloading from my links)
​Instructions
Windows
Install oneplus usb driver, after disabling driver signature enforcement
Download and install platform tools, unzip and add the folder to Windows path,
"Settings > Advanced System Settings > Environment Variables > New"
Example -> http:///imgur.com/a/x8XOofQ
open command prompt, or powershell, and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
Linux
Download and add to path (.bashrc) platform-tools:
export PATH=$HOME"/platform-tools:$PATH"
dont forget udev rules if you're using ubuntu based distro:
https://github.com/M0Rf30/android-udev-rules
open a terminal and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
that's all.
Telegram Group:
Telegram: Contact @infected_unofficial_stuff_group
t.me
Feel free to join!
Source: https://github.com/the-deepongi/orangefox_instantnoodle-dev​

reserved

reserved again

hello are the zips flashable via twrp

Or magisk

lagaff4437 said:
hello are the zips flashable via twrp
Click to expand...
Click to collapse
Yes flash from TWRP should work.

Flash/ install instructions may be handy to have in the OP for the novice user.

Do it support the last OP8P firmware?

Marcyvee said:
Do it support the last OP8P firmware?
Click to expand...
Click to collapse
Working here on F.15

RodiNet7601 said:
Working here on F.15
Click to expand...
Click to collapse
I can boot it from fastboot, but it can't decrypt data. I'm using EvoX 7.6.1 and the erofs B2.
Do anyone can see data partition? do I have to format it?

Marcyvee said:
I can boot it from fastboot, but it can't decrypt data. I'm using EvoX 7.6.1 and the erofs B2.
Do anyone can see data partition? do I have to format it?
Click to expand...
Click to collapse
try an initial format

deepongi said:
try an initial format
Click to expand...
Click to collapse
No need for it: the last version can decrypt data without any wipe. It works flawlessly. Thanks!

Attempted to boot (not flash) OrangeFox-deepongi-op8-erofs-b2.img via fastboot - unable to decrypt data. Phone is IN2025 OP8 Plus running A13, F25.

Please After install orangefox B2 erofs IMG in my oneplus 8 i Cant see storage internele for flash magisk zip why ?

My phone is a OnePlus 8 Pro IN2023 running Android 13, build number IN2023_11_F.62 (official OOS13).
I have the same issue as @rmedure, even when flashing the image.
Can't give you a log since I can't mount /data
Also, for some reason MTP file transfer doesn't work "out of the box", the device isn't recognized in "Device Manager", it just shows as "MTP":
I have to manually select a driver by doing Update Driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer > Show All Devices > (Standard MTP Device) > MTP USB Device.
I have to do this every single time I connect my phone to my computer, and my phone incorrectly shows as a OnePlus 8T.
Still can't access Internal Storage ofc
Both /data decryption and MTP file transfer are working flawlessly with TWRP 3.7.0-13 Beta 3

Daturachan said:
My phone is a OnePlus 8 Pro IN2023 running Android 13, build number IN2023_11_F.62 (official OOS13).
I have the same issue as @rmedure, even when flashing the image.
Can't give you a log since I can't mount /data
Also, for some reason MTP file transfer doesn't work "out of the box", the device isn't recognized in "Device Manager", it just shows as "MTP":
View attachment 5859033
I have to manually select a driver by doing Update Driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer > Show All Devices > (Standard MTP Device) > MTP USB Device.
I have to do this every single time I connect my phone to my computer, and my phone incorrectly shows as a OnePlus 8T.
Still can't access Internal Storage ofc
Both /data decryption and MTP file transfer are working flawlessly with TWRP 3.7.0-13 Beta 3
Click to expand...
Click to collapse
MTP file transfer is a Kernel thing. For my Orangefox for OP8t/9r build I had to update the file drivers/usb/gadget/function/f_mtp.c from the used OOS13 based Kernel to get that working in Orangefox.
These things is something Oneplus is messed up with OOS13 I guess.

Related

Need help flasing Paranoid Android - All TWRP'd up

Hi all! This is my first attempt to flash a custom rom and I'm stumbling. Summary below:
DEVICE AND SYSTEM:
Xiaomi Mi 6X
Running MIUI 11.0.6.0(PDCCNXM) (based on Android 9)
Device bought in China in 2018, not used until now, only updated through Xiaomi OTA.
Mi Unlock status - Unlocked
Developer options unlocked
USB debugging - activated
Phone not rooted.
Phone has no lock screen password set.
FILES TO FLASH:
1. dm-verity anti-rollback flash:
no-verity-opt-encrypt-6.0.zip
2. Paranoid Android custom ROM:
pa-quartz-5-wayne-20200924.zip
METHOD
I'm using Google pltaform-tools (https://developer.android.com/studio/releases/platform-tools) + TWRP files (https://twrp.me/xiaomi/xiaomimi6x.html) and command prompts in adb and fastboot.
WHAT HAS WORKED SO FAR
adb devices OK - cmd shows hexa key
adb reboot bootloader OK - phone enters fastboot
fastboot flash recovery twrp.img OK - cmd shows Finished. Total time: 1.504s
fastboot reboot (holding recovery key combo to avoid entering automatic MIUI recovery) OK - TWRP loads
Then the problems start. TWRP shows:
Mount
Decrypt Data
Enter Password
and no password in the realms of man or heaven works. by clicking cancel as a workaround several mounting problems appear:
THE ISSUE
Since TWRP can't decrypt internal storage, I can't find the zip files I copied to the phone's memory.
Googling around I found the OTG option and tried it. But as it turns out it's also impossible to mount OTG (on Mount, the option for OTG appears but clicking it does nothing)
Googling more I found out about abd sideload, but TWRP fails to start the feature (on Advanced -> ADB sideload -> select Wipe Dalvik Cache + Wipe Cache)
Also googling intensely I found that by wiping the memory (on Wipe - Format Data - write "yes") then reentering recovery it was possible for TWRP to enter a decrypted mode. after doing this no password is required but both OTG and ADB show the same problems as before (and of course the internal memory files are no longer there).
As a summary of my woes, this is what I've tested so far and the results:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Assorted tests with older versions of TWRP have exactly the same results.
After every wipe I have to set up MIUI11 again, open developer optios, allow USB debugging etc. My fingers hurt. Morale is low. My soul is leaking. Any ideas on where to go next? Is this some unfixable incompatibility between TWRP and MI? I think I've exhausted the paths I can find by just googling around like a progressively more hairless maniac noob.
TWRP sucks for mi 6X. Download this one (OrangeFox Recovery) and everything works fine.To install it extract the zip and flash the recovery.img that is there. After that reboot to recovery and if it still asks for password just ignore, go to menu, manage partitions, clik on data, click on the button that will show, then format data and type yes. This will clean every partitions (It's the only way i found to fix encryption since our device doesn't support sd cards)Then download the Rom you want to your pc and then copy to your phone storage and install it. Good Luck.

Question Flashing Factory Images

I am trying to flash 11.0.0 (RD2A.211001.002, Oct 2021) factory image in windows using the flash-all bat file. I updated my fastboot drivers in windows update and downloaded the latest platforms tools from google's website. I get this error while running the bat file.
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 3.254s
Press any key to exit...
Any idea as to why?
Do you have your platform-tools folder in your PATH Variables?
kingofnice said:
Do you have your platform-tools folder in your PATH Variables?
Click to expand...
Click to collapse
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
On Windows 10, type in the search bar "system environment variables" and open that settings menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click on Environment Variables...
Edit
Add the location to your folder. Press Ok and Apply if you need.
Now try your adb and fastboot commands from a new command prompt window. They should be working from any directory you are using command prompt in.
I think that is why your flash failed, though I don't know. It sounds like it couldn't connect because it couldn't utilize fastboot to find a device/partition.
Test "fastboot devices" and if you see your device try flashing again. Also, "fastboot -w update image-xxx-xxx.zip" is in the flash-all bat. remove "-w" to stop it from wiping data. That's your call as you might need a fresh install.
Klimon5 said:
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
Click to expand...
Click to collapse
Did that help at all?
kingofnice said:
Did that help at all?
Click to expand...
Click to collapse
I ended up using Windows 10 to adb sideload the most recent android 11 OTA zip from google. I performed a factory data reset in recovery after I booted into the update first. I then was able to unlock the bootloader, re-enable the oem unlocking setting in dev options, & install the official lineage os recovery and rom for barbet. I will try your steps and see if I can flash a factory image. When I had my nexus 6p, I removed the -w prefix and immediately rebooted into recovery to factory data reset. It then booted just fine. For me I think that my platforms tools for Ubuntu are out of date.
I ran this command on my ubuntu machine.
$ adb version
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5ubuntu2
The lineage os installation instructions warns about issues with out of date platform tools.
Install LineageOS on barbet | LineageOS Wiki
wiki.lineageos.org
"Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
I want to try this on linux manjaro on my laptop. The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Klimon5 said:
For me I think that my platforms tools for Ubuntu are out of date.
The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Click to expand...
Click to collapse
This is the problem. Using outdated Platform Tools causes problems. Latest release is 31.0.3, Aug '21. Many other users have run into similar problems because they were using outdated Platform Tools.

[GUIDE]Xiaomi.EU ROMs Flashing Guide All Devices [Windows-Only]

If you are going from MIUI 12 (or later) Weekly ROM to MIUI 12 Stable ROM, you are doing a downgrade, so format data is mandatory!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements:
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers, android bootloader interface and click install.
MIUI 12 (Weekly And Stable)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of c: drive and connect your device to fastboot mode and double click on flash_all.bat
A cmd window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Flash twrp using fastboot.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of c: drive.
Go into folder.
Run fastboot installation script in folder according your PC operating system:
If updating from older rom.
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
Done.
If installing first time.
--- For Windows OS - windows__first_install_with_data_format_.bat
--- For Linux - linux__first_install_with_data_format_.sh
--- For MacOS - macos_fastboot_first_install_with_data_format_.sh
NOTE(For Stable And Recovery ROMs):
CHECK THE XIAOMI.EU THREAD FOR KNOWING IF YOUR ROM IS FASTBOOT OR RECOVERY.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Install magisk after first boot and reboot after installing magisk to get rid of system lags.

[GUIDE]Xiaomi.EU ROMs Flashing Guide All Devices [Linux-Only]

Requirements:
Your device's bootloader must be unlocked.
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Click to expand...
Click to collapse
MIUI 12 (Weekly And Stable)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of home directory and connect your device to fastboot mode and open a terminal in the rom folder and run the command:
./flash_all.sh
A terminal window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Flash twrp using fastboot.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of home directory.
Go into folder.
Run fastboot installation script in folder
Open terminal window in the folder
If updating from older rom.
Run command in terminal:
./linux_fastboot_update_rom.sh
Done.
If installing first time.
Run command in terminal:
./linux__first_install_with_data_format_.sh
NOTE(For Stable And Recovery ROMs):
CHECK THE XIAOMI.EU THREAD FOR KNOWING IF YOUR ROM IS FASTBOOT OR RECOVERY.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Install magisk after first boot and reboot after installing magisk to get rid of system lags.

[RECOVERY][OFFICIAL] TWRP 3.7.0 for Galaxy S5 Mini Qualcomm

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This Recovery is for the Qualcomm 3G variant of the Galaxy S5 Mini (SM-G800H).
Flashing it on the Exynos variants (SM-G800F/M/Y) will result in a soft-brick!
The US Qualcomm variant (SM-G800R4) isn't supported.
Flashing custom binaries like TWRP will trip your Knox Warranty Bit permanently!​
Disclaimer​
Code:
Neither me nor Team Win will take responsibility for any damage that may occur from installing or using TWRP.
Features​
Everything you expecting from TWRP (backups, restore, installation, etc.)
Encryption of backups (/data/data)
Decryption of encrypted data (AOSP only)
ADB/MTP
F2FS filesystem
USB OTG supported
Built with android-8.1 branch
Installation methods​1. From existing TWRP​
Spoiler
Download the twrp-3.X.X_9-0-kmini3g.img file and push it to your internal storage
Boot into TWRP (volume up + power button)
Locate to Install > Install image > Select the previously downloaded .img file > Select "Recovery" partition > Swipe to confirm Flash
Reboot into Recovery to check if the installation was successful
2. Odin (Windows)​
Spoiler
Download Odin from here (or from any other trustworthy source)
Download the twrp-3.X.X_9-0-kmini3g.img.tar file to your PC
Open Odin (as administator if needed)
Power off your S5 Mini
Boot into Download Mode (volume down + power button)
Connect your device with an USB cable to your PC
If your PC did detect your device you should see a blue box with a centered text (e.g. 0:[COM10]) showing up in Odin and "Added!!" in Log
In Odin tap on AP (or PDA) > find and select the previously downloaded .img.tar file
Click on "Start"
If the installation was successful, you should see a green box showing PASS!
3. Heimdall​
Spoiler
The installation of Heimdall may differs from Distro to Distro so research first how to install in on your machine
Download the twrp-3.X.X_9-0-kmini3g.img file to your PC
Power off your S5 Mini
Boot into Download Mode (volume down + power button)
Connect your device with an USB cable to your PC
Open your terminal and cd to the downloaded .img file
Type the following command in your terminal:
Bash:
heimdall detect
If your PC did detect your device you should see the following output:
Bash:
Device detected
Flash the recovery using the following command (replace the "X" with the version numbers of the the previously downloaded img file):
Bash:
heimdall flash --RECOVERY twrp-3.X.X_9-0-kmini3g.img
Boot into recovery using volume up + power button combination to check if the installation was successful
4. Root​
Spoiler
Download the twrp-3.X.X_9-0-kmini3g.img file and push it to your internal storage
Open your local terminal app
Type the following commands to flash the image (replace the "X" with the version numbers of the the previously downloaded img file):
Bash:
su
dd if=/sdcard/twrp-3.X.X_9-0-kmini3g.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download​https://twrp.me/samsung/samsunggalaxys5miniqcom.html
Credits​
Team Win for their awesome recovery!
@bigbiff for his great assistance to bring up official TWRP support!
@Simon1511 for some help with general TWRP stuff and device tree
@haggertk and @Alastor89 for their uncountable kernel patches for msm8974/msm8x26
Sources​Device Tree: https://github.com/TeamWin/android_device_samsung_kmini3g
Kernel: https://github.com/prototype74/android_kernel_samsung_msm8226/tree/twrp-7.1
TWRP: https://github.com/TeamWin/android_bootable_recovery
TWRP is now official available for our SM-G800H!
Notes
Nano, Bash and Python are not included to allow the images to fit in our S5 Mini's recovery partition
Official TWRP images are built with android-8.1 (unofficial builds with android-7.1)
Happy flashing!

Categories

Resources