Database Develop

[RMX206X][RECOVERY] Pitch Black Recovery Project

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: Realme 6 Pro(RMX2061/2063)
Authors build: @ishu88
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android_device_realme_RMX2061-pbrp
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
Disable DM Verity
Use AromaFM as default file manager
Various tools are included
Universal flash-able file for all variant of a device
Many bug fixes ,optimization & much more
Click to expand...
Click to collapse
Installation Instructions
WARNING
If you are flashing this recovery for the first time /or/ If you are flashing this after installing the stock ROM,
You will get a "Current Image Destroyed Error".
To fix it, Just flash the original vbmeta.img extracted from the ozip file of current realmeui ROM and flash it in fastboot mode by disabling Verity.
Fastboot code to flash vbmeta below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing from previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
initial build
Bugs
- Stock ROM Ozip flashing error (use twrp for now)
- Flashlight not working
- MTP only works for SD card
Downloads
Flashable zip
https://drive.google.com/file/d/14BgBiKlfMXnKRwBp5YZh2g0N85gm6sJY/view?usp=drivesdk
XDA:DevDB Information
Pitch Black Recovery Project, Tool/Utility for the Realme 6 Pro
Contributors
Kevin Saiza, ishu88
Version Information
Status: Testing
Created 2020-08-19
Last Updated 2020-08-19

Screenshots
Take a look what pbrp offers

Reserved 2

wow thank you friend & hope to fix all problems asap
all support to your work

do you need a patcheed vbmeta to installl this fresh to a bootloader unlocked 6 pro? Im very new sorry if this is a obvious answer.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Okay so i just straight up flashed the recovery image and yep theres something else you need to make it work. Probably refer to the TWRP guide in this same device forum to figure it out.
Thanks for your work, now i have a phone to fix lol not complaining tho! i might be able to get my android skills up!

SKELEKINETIC said:
Okay so i just straight up flashed the recovery image and yep theres something else you need to make it work. Probably refer to the TWRP guide in this same device forum to figure it out.
Thanks for your work, now i have a phone to fix lol not complaining tho! i might be able to get my android skills up!
Click to expand...
Click to collapse
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Kevin Saiza said:
Up-to-date kernel, built from sources
Click to expand...
Click to collapse
Can you share how you got the 6 pro kernel compiling, and most of all, running?

Kevin Saiza said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------

neoxcool said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
Click to expand...
Click to collapse
Try to use latest version of minimal adb and fastboot , and , platform tools

Do you have twrp 3.4 built for this device? Or does nullexceptiosn 3.3 work to flash stock ozips?

Kevin Saiza said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Click to expand...
Click to collapse
Thank you. Where can I learn more about "dm-verity" and vbmeta? They are anti tamper protection right? W

I know xda really isnt for noob but a step by step with prerequisites would be amazing. currently i cant get FBE to work.

Pitchblacl no longer decrypts internal storage!

neoxcool said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
Click to expand...
Click to collapse
I had the same issues with the commands, even after updating my Fastboot, and for some reason, they worked fine in Command Prompt, instead of Powershell, give it a try!!

Link doesnt work. google says the file is in the owners trash

SKELEKINETIC said:
Link doesnt work. google says the file is in the owners trash
Click to expand...
Click to collapse
It works

SKELEKINETIC said:
Do you have twrp 3.4 built for this device? Or does nullexceptiosn 3.3 work to flash stock ozips?
Click to expand...
Click to collapse
To flash stock ozip,use twrp only

I couldn't download this L.R. TWRP from russian site pda. Does anyone have this file (LR.TWRP-3.4.2b_RMX2061.img)?

It looks to be incompatible with the latest firmware, A.33. I'm going to downgrade and see if PBRP works with A.31. It did work before I upgraded to A.33.

I was able to make it work after I downgraded to A.17 but it broke the moment I flashed anything to do with the system partition.

[CLOSED][RECOVERY][dandelion][v3.0.0]Pitch Black Recovery[31/12/2020]

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: dandelion
Maintainer/Authors build: PBRP Team
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_dandelion-pbrp
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by
Code:
fastboot flash recovery recovery.img
Flash vbmeta (get from fastboot rom)
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Bugs
- fastbootd
- sideload
Device Tree:- https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_dandelion-pbrp
Downloads
Dropped Support
You Can Build Amd Fix Bugs As Device Tree I have shared

cant wait to try! thanks for your work mate!

touch screen not working plz help me...

dreadmachine said:
touch screen not working plz help me...
Click to expand...
Click to collapse
it is working for me
check if touch is working in this https://gofile.io/d/UWjWjR

Mrinalsaha said:
it is working for me
check if touch is working in this https://gofile.io/d/UWjWjR
Click to expand...
Click to collapse
sadly wont boot, i tried flashing it, but its not booting to it

dreadmachine said:
sadly wont boot, i tried flashing it, but its not booting to it
Click to expand...
Click to collapse
it boot but the screen stays black
press power button 2 times to see it when it is in black screen

i did and it worked, but.... when i install system.img of rom, it says no os on system.. sure you want to reboot?

everything functions correctly(mtp,brightness,touch,decryption) but couldn't root with magisk(both with recovery provided one and the official one) it flashes, but when i turn on device and open the magisk manager app, it shows no root. and tried flashing gsi (to super partition) messed up the partition table. didn't try backup. couldn't find a way to wipe system, there was no system entry. couldn't mount it either

Rediancool said:
everything functions correctly(mtp,brightness,touch,decryption) but couldn't root with magisk(both with recovery provided one and the official one) it flashes, but when i turn on device and open the magisk manager app, it shows no root. and tried flashing gsi (to super partition) messed up the partition table. didn't try backup. couldn't find a way to wipe system, there was no system entry. couldn't mount it either
Click to expand...
Click to collapse
flashing magisk to get root works but you'll have to use the latest 21.2 version
I have tried to flash all the magisk version but only 21.2 gave me root
download from here https://github.com/topjohnwu/Magisk/releases

Mrinalsaha said:
flashing magisk to get root works but you'll have to use the latest 21.2 version
I have tried to flash all the magisk version but only 21.2 gave me root
download from here https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
thanks man it worked. were you successful in flashing gsi?

Rediancool said:
thanks man it worked. were you successful in flashing gsi?
Click to expand...
Click to collapse
how are you suggesting that I would flash gsi ?

Mrinalsaha said:
how are you suggesting that I would flash gsi ?
Click to expand...
Click to collapse
i meant did you flash gsi with this

Is there any way to flash arm64 gsi in redmi 9a? because I want to run google camera which works in 64bit

Rediancool said:
i meant did you flash gsi with this
Click to expand...
Click to collapse
no it cannot be flashed

i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)

Rediancool said:
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Click to expand...
Click to collapse
You can't modify system in recovery because of dynamic partition

[/QUOTE]
Rediancool said:
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Click to expand...
Click to collapse
Try this way

Wooww!! It worked fine for me... But just to install recovery. I can't root with magisk. No with 21.2 or 21.4 versions, cause the phone goes into bootloop.
No way with supersu.
I'm in MIUI 12.0.10.0 QCDEUXM
Is there anybody who can help me, please?

t's sad, but it doesn't feel pressed . the touchscreen doesn't work(

wanlus said:
Wooww!! It worked fine for me... But just to install recovery. I can't root with magisk. No with 21.2 or 21.4 versions, cause the phone goes into bootloop.
No way with supersu.
I'm in MIUI 12.0.10.0 QCDEUXM
Is there anybody who can help me, please?
Click to expand...
Click to collapse
you have to flash vbmeta to avoid bootloop
fastboot flash vbmeta vbmeta.img
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io

[RECOVERY] [UNOFFICIAL] PBRP 3.1.0 For Galaxy A7 2018

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.5.1
PitchBlack version: 3.1.0
For device: a7y18lte
Authors build: itmr
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/itamar567/android_device_samsung_a7y18lte
Kernel: https://github.com/devkingsteam/android_kernel_samsung_universal7885/tree/android-8.1
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto download mode in your device
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
Boot into PBRP
Copy the zip to internal storage/sdcard
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.1.0
- Bump to 3.1.0
- Based on TWRP 3.5.1
- Redesigned homescreen
- Fixed minor glitches
- Added more languages support
Device Side Changelog
Code:
- Initial release
Bugs
- Decryption doesn't work
- Flashlight
- Some people are experiencing black lines, expect a fix soon
- You tell me!
Downloads
Flashable zip
https://www.androidfilehost.com/?fid=14943124697586335986

itmr said:
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.5.1
PitchBlack version: 3.1.0
For device: a7y18lte
Authors build: itmr
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/itamar567/android_device_samsung_a7y18lte
Kernel: https://github.com/devkingsteam/android_kernel_samsung_universal7885/tree/android-8.1
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto download mode in your device
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
Boot into PBRP
Copy the zip to internal storage/sdcard
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.1.0
- Bump to 3.1.0
- Based on TWRP 3.5.1
- Redesigned homescreen
- Fixed minor glitches
- Added more languages support
Device Side Changelog
Code:
- Initial release
Bugs
- Decryption doesn't work
- You tell me!
Downloads
Flashable zip
https://www.androidfilehost.com/?fid=14943124697586335986
Click to expand...
Click to collapse
This PBRP works fine on my TREBLE supported A7 2018 (sm-a750f/ds).

I tested this out. Only thing that doesn't seem to work is the flashlight but that's not a big deal
otherwise this recovery works flawlessly
For anyone wanting to flash this recovery!
You might want to downgrade to the stock November 2020 Security Patch while it's still allowed. As the newest Patch presents you with bootloops and black lines when flashing
edit:
device used A750FN

Dark8812 said:
I tested this out. Only thing that doesn't seem to work is the flashlight but that's not a big deal
otherwise this recovery works flawlessly
For anyone wanting to flash this recovery!
You might want to downgrade to the stock November 2020 Security Patch while it's still allowed. As the newest Patch presents you with bootloops and black lines when flashing
edit:
device used A750FN
Click to expand...
Click to collapse
Didn't know you can activate flashlight in PBRP, so I didn't notice the issue. I'll try to fix it
About the black lines, I had black lines with ashyx's TWRP and that's why I made this release.
I don't have black lines, but I think that I know how to solve this issue.
Expect an update today/tomorrow

Since this release is based on android 8, I thought that moving to android 10 would fix the black lines.
But I had problems with compiling PBRP on android 10. I will try it again later, but until then I made a release using latest kernel and android 8.
Can you tell me if this image boots for you on latest security patch?
kernel source: A750FNPUS5CTI1 kernel from Samsung opensource
download zip
NOTE: I noticed that adb shell doesn't work, but all other adb commands work (don't worry, normal terminal works). I will try to fix this and the flashlight in the next release.

itmr said:
Since this release is based on android 8, I thought that moving to android 10 would fix the black lines.
But I had problems with compiling PBRP on android 10. I will try it again later, but until then I made a release using latest kernel and android 8.
Can you tell me if this image boots for you on latest security patch?
kernel source: A750FNPUS5CTI1 kernel from Samsung opensource
download zip
NOTE: I noticed that adb shell doesn't work, but all other adb commands work (don't worry, normal terminal works). I will try to fix this and the flashlight in the next release.
Click to expand...
Click to collapse
I initially installed it on the latest DBT patch
A750FNXXS5CUC2 it booted fine however when flashing it rebooted into the recovery and it showed black lines in the meantime
Edit: I will try the updated version now I misread your request the first time

Dark8812 said:
Edit: I will try the updated version now I misread your request the first time
Click to expand...
Click to collapse
I can't seem to flash it using the newest firmware

If you are on Windows:
Flash this using Odin3.
If you are on Linux/Mac:
install heimdall
unzip the installer, open the terminal in the extracted folder and run:
Code:
heimdall flash --RECOVERY TWRP/recovery.img

itmr said:
If you are on Windows:
Flash this using Odin3.
If you are on Linux/Mac:
install heimdall
unzip the installer, open the terminal in the extracted folder and run:
Code:
heimdall flash --RECOVERY TWRP/recovery.img
Click to expand...
Click to collapse
It seems like there is a misunderstanding. I am able to flash the recovery and I had it for a few days now. However I need to first downgrade to bootloader version 5 of this phone (Security Patch 1st November 2020). For the recovery to work correctly. As the newest version shows black lines and restarts the phone when flashing a file in the recovery. Another thing is I can't flash the file you gave me for odin.
It gives this error:
Code:
ID0008 engine v(ID3.1401)
ID0008 File analysis..
ID0008 FAIL! LZ4 is invalid
OSM All threads completed. (succeed 0 failed 1)
Further if you flash it with an already existing recovery you get this error:
Code:
Could not do normal boot. Invalid KERNEL LENGHT!
I instead found a workaround and used the one found in the heimdall archive, I extracted the recovery.img file and added it to a new archive named recovery.tar. This is flashable trough odin and successfully installs the recovery

Dark8812 said:
Another thing is I can't flash the file you gave me for odin.
It gives this error:
Code:
ID0008 engine v(ID3.1401)
ID0008 File analysis..
ID0008 FAIL! LZ4 is invalid
OSM All threads completed. (succeed 0 failed 1)
Further if you flash it with an already existing recovery you get this error:
Code:
Could not do normal boot. Invalid KERNEL LENGHT!
Click to expand...
Click to collapse
Sorry about that, I didn't pack the recovery correctly for odin.
Dark8812 said:
I instead found a workaround and used the one found in the heimdall archive, I extracted the recovery.img file and added it to a new archive named recovery.tar. This is flashable trough odin and successfully installs the recovery
Click to expand...
Click to collapse
Glad you got it to work! Again, sorry!
If you upgrade the firmware to the latest security patch, can you boot this version of PBRP successfully without black lines?

itmr said:
Sorry about that, I didn't pack the recovery correctly for odin.
Glad you got it to work! Again, sorry!
If you upgrade the firmware to the latest security patch, can you boot this version of PBRP successfully without black lines?
Click to expand...
Click to collapse
On the latest security patch the recovery doesn't work that great. As I said before it restarts the phone into the recovery when flashing and also with certain compatible files it shows black lines when flashing them.

I can't flash it using TWRP. just stuck. Is it okay to flash it using TWRP image install? I'll just extract the zip and get the recovery.img

Hello, sorry I didn't answer for some time.
Dark8812 said:
On the latest security patch the recovery doesn't work that great. As I said before it restarts the phone into the recovery when flashing and also with certain compatible files it shows black lines when flashing them.
Click to expand...
Click to collapse
I made a new build with an extracted kernel from latest security patch (A750FNXXU5CUD3). Can you tell if it works?
kernel source should be in samsung opensource
download
xxfDeadStar88x said:
I can't flash it using TWRP. just stuck. Is it okay to flash it using TWRP image install? I'll just extract the zip and get the recovery.img
Click to expand...
Click to collapse
It seems that also other devices have the same issue. Yes, flashing using TWRP image install will work. I also suggest you to copy the zip files from PBRP/tools to /sdcard/PBRP/tools.

itmr said:
Hello, sorry I didn't answer for some time.
I made a new build with an extracted kernel from latest security patch (A750FNXXU5CUD3). Can you tell if it works?
kernel source should be in samsung opensource
download
It seems that also other devices have the same issue. Yes, flashing using TWRP image install will work. I also suggest you to copy the zip files from PBRP/tools to /sdcard/PBRP/tools.
Click to expand...
Click to collapse
Thanks bro! It works absolutely fine on my SM-A750GN/DS device. Thanks for this wonderful recovery!

Hello guys, i am a new XDA member and i have troubles rooting my samsung galaxy a7 2018 with april 2021 security patch, i find this new recovery but i didn't understand this point
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
what i have to do after extract my PBRB ZIP?

Chris7897 said:
Hello guys, i am a new XDA member and i have troubles rooting my samsung galaxy a7 2018 with april 2021 security patch, i find this new recovery but i didn't understand this point
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
what i have to do after extract my PBRB ZIP?
Click to expand...
Click to collapse
If you use GNU+Linux/Mac, install heimdall (https://glassechidna.com.au/heimdall/) and run heimdall flash --RECOVERY recovery.img
If you use Windows, compress recovery.img to a tar archive and flash the tar archive in odin AP slot

itmr said:
If you use GNU+Linux/Mac, install heimdall (https://glassechidna.com.au/heimdall/) and run heimdall flash --RECOVERY recovery.img
If you use Windows, compress recovery.img to a tar archive and flash the tar archive in odin AP slot
Click to expand...
Click to collapse
With 7zip? I tried as you said but when i boot into Pbrp, screen goes black and my phone was blocked

For those who flash through Odin3, I'll leave a link to the .tar file with recovery. It would be nice if the author added a link to this file and a manual to odin3.
Download recovery.tar
(Sorry if my English is bad, unfortunately I don't know him well)

itmr said:
Hello, sorry I didn't answer for some time.
I made a new build with an extracted kernel from latest security patch (A750FNXXU5CUD3). Can you tell if it works?
kernel source should be in samsung opensource
download
Click to expand...
Click to collapse
Blank screen (like switched off phone) on my SM-A750F/DS after flashing, running on A750FXXU5CUD3.
Found hard time to access download mode to recover.
Even Orangefox SAR behaved same with this ROM update.
But, previous PBRP worked at least. However, setting lockscreen with password or fingerprint kept rebooting in a loop until flashed rmpass.zip.

drbsin said:
Blank screen (like switched off phone) on my SM-A750F/DS after flashing, running on A750FXXU5CUD3.
Found hard time to access download mode to recover.
Even Orangefox SAR behaved same with this ROM update.
But, previous PBRP worked at least. However, setting lockscreen with password or fingerprint kept rebooting in a loop until flashed rmpass.zip.
Click to expand...
Click to collapse
have you tried format data? data partition will be corrupted after you flash the custom recovery. format data first before doing anything else.

[UNOFFICIAL][RECOVERY][PitchBlackRecoveryProject] PBRP For Lenovo Tab 4 8 ( TB-8504X/F )

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.5.2
PitchBlack version: 3.1.0
For Device: Lenovo Tab 4 8 TB-8504X/F
Build by: @Electron.48
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device Trees: Device Trees
Fully native android like UI
Full dark theme with changeable accents
Reorganized menus
Use AromaFM as default file manager
Various tools are include
System debloater available
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions:
Fastboot Method:
Download PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
Open Terminal where u have downloaded the pbrp img file
Go into Bootloader
Apache config:
adb reboot bootloader
Flash the recovery image
Code:
fastboot flash recovery PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
Reboot to Recovery and congrats you have successfully installed PBRP.
Flashing ZIP:
You should have a custom recovery already for this method
Flash the PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.zip in your custom recovery
Press volume down button to reboot to PBRP.
Congrats. You have successfully installed PBRP
What works:
Everything ( May find bugs its in testing phase )
Bugs:
You tell me
Downloads:
PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.zip
Credits:
TeamWin for TWRP
PitchBlack Team for PBRP
@highwaystar_ru for Device Trees
Status:
Testing
Release Date:
28-05-2022

reserved

Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP

ZONTAC said:
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
Click to expand...
Click to collapse
Ig it should be possible. Try to copy the backups in PBRP folder then restore. Tell if it works or not

ZONTAC said:
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
Click to expand...
Click to collapse
Btw can u share some screenshots...?

Electron.48 said:
Ig it should be possible. Try to copy the backups in PBRP folder then restore. Tell if it works or not
Click to expand...
Click to collapse
Working

it doesnt work it just goes to the normal android recovery after i try to use it after flashing

stinkysockboi said:
it doesnt work it just goes to the normal android recovery after i try to use it after flashing
Click to expand...
Click to collapse
Tell in detail or provide log so that dev can work on it

Electron.48 said:
Bugs:
You tell me
Click to expand...
Click to collapse
So TB-8504F has a touchscreen issue where you need to sleep and wakeup recovery after it boots for touch to work. Like what @ZONTAC mentioned earlier. I was able to fix it on TWRP 3.6.2 that I built for testing. I would imagine it would work for PBRP as well. It does not affect TB-8504X which is why its not commonly seen. The F variant is not as popular. I have not tested it on 8504X mind you but I don't think that flag will be needed by it.
TB-8504F: Remove blank on boot · deadman96385/[email protected]
This flag kills the Himax touch until you lock and unlock on TB-8504F but strangely does not affect TB-8504X
github.com

deadman96385 said:
So TB-8504F has a touchscreen issue where you need to sleep and wakeup recovery after it boots for touch to work. Like what @ZONTAC mentioned earlier. I was able to fix it on TWRP 3.6.2 that I built for testing. I would imagine it would work for PBRP as well. It does not affect TB-8504X which is why its not commonly seen. The F variant is not as popular. I have not tested it on 8504X mind you but I don't think that flag will be needed by it.
TB-8504F: Remove blank on boot · deadman96385/[email protected]
This flag kills the Himax touch until you lock and unlock on TB-8504F but strangely does not affect TB-8504X
github.com
Click to expand...
Click to collapse
But i have 8504X variant

ZONTAC said:
But i have 8504X variant
Click to expand...
Click to collapse
Your recovery advertises that it supports both variants. That patch will fix the issue on TB-8504F, it should not change anything on TB-8504X but I don't have that version to confirm.

deadman96385 said:
Your recovery advertises that it supports both variants. That patch will fix the issue on TB-8504F, it should not change anything on TB-8504X but I don't have that version to confirm.
Click to expand...
Click to collapse
If you have build so i can test it on my tab(8504x)

Do You have any idea?
Freshly flashed stock, there everything works, but I cannot flash any ROM - tried both crDroid, RR and Ubuntu. Always same error.
Strange is it mounts system at first... And after formatting it can be mounted again, but than I got error, cos no image is there to be patched, I believe?

ch3mn3y said:
Do You have any idea?
Freshly flashed stock, there everything works, but I cannot flash any ROM - tried both crDroid, RR and Ubuntu. Always same error.
Strange is it mounts system at first... And after formatting it can be mounted again, but than I got error, cos no image is there to be patched, I believe?
Click to expand...
Click to collapse
Follow proper processor
In your case :- if you are coming from stock , 1. mount system in stock recovery
2.flash pbrp/twrp
3. do factory wipe(or reset)
4. do advance wipe in which wipe system, cache, delvick ,data
5.after that flash system
6. Still having problem try d/f twrp or contact rom dev

Did a test boot without flashing. System starts but hangs on many tasks, even restarting to other modes hangs the system. My device reports as tb_8504x. I had problem with flashing through TWRP so I wanted to try PBRB.

Hello, I got PBRP to boot into recovery, I have OEM bootloader unlocked and USB debugging enabled. I'm trying to completely format the tablet to install LineageOS 18. When I wipe the process gets stuck on "Formatting system using mke2fs". It's been on it for about an hour now. Is that normal? The device is responsive. I can hold the power button down and get reboot options. I can force a reboot and get back into the recovery and try again but each time it gets halted at the format stage. What should I do?

[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8 / 8t / 8 Pro / 9r] [05-Jun-2023]

OrangeFox Recovery Project
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
OrangeFox Recovery for the Oneplus 8 / 8t / 8 Pro / 9r
Download (for Android 13 ROMs) (OOS13 Based)
Download (for Android 12.x, 13 ROMs) (OOS12 Based)
Download FBEv1 Version Oneplus 8 (OOS13 Based)
Download FBEv1 Version Oneplus 8Pro (OOS12 Based)
Download FBEv1 Version Oneplus 8Pro (OOS13 Based)
Boot it with: fastboot boot OrangeFox-R12.1-OPKONA-V19.img
or flash it with: fastboot flash recovery OrangeFox-R12.1-OPKONA-V19.img​
Orangefox R12.1 can only be flashed to the recovery partition if you have OOS12 Firmware, but you can still boot it with fastboot boot if you are on OOS11 Firmware and need to decrypt data on Android 12 or Android 13 ROMs.
Some things like USB OTG etc are not working when using fox_12.1 on OOS11 Firmware!
If the touchscreen is not working for you after booting/flashing Orangefox please Update your OOS/Firmware to a newer Version!
Take a look at this Post from TWRP in regards of Backup and Restore or
here from the Orangefox wiki.
Spoiler: Flashing Instructions and switching OOS Firmware Base
Keep in mind! Never flash a recovery file if you are not on the same OOS Firmware as the recovery is for, otherwise you will end up in Qualcomm Crashdump mode or just a black screen.
Always just do a fastboot boot recovery.img until you are on the same OOS Firmware on your phone as the recovery is for, only then you can flash it with fastboot flash recovery as well!
From OOS11 Firmware to OOS12 Firmware ROM
------------------------------------------------------
Check DDR RAM type (from Windows cmd)
adb shell getprop ro.boot.ddr_type
0 - represents your device is LPDDR4X (use DDR0 Firmware file)
1 - represents your device is LPDDR5 (use DDR1 Firmware file)
or from Terminal on your phone
getprop ro.boot.ddr_type
0 - represents your device is LPDDR4X (use DDR0 Firmware file)
1 - represents your device is LPDDR5 (use DDR1 Firmware file)
When you are on OOS12 use this from the Orangefox Terminal:
cat /proc/devinfo/ddr_type
Download latest Orangefox 12.1 img file from here
Download OOS12 flashable Firmware for your phone from here or, Oneplus 8t, Oneplus 9r
adb reboot bootloader
fastboot boot OrangeFox_R12.1-xx.img
adb sideload fw_Oneplus8T_EU_c21_DDR0.zip
adb rebooot bootloader
fastboot flash recovery OrangeFox_R12.1-xx.img
fastboot reboot recovery
Apply Update - apply via ADB
adb sideload ROM.zip
Factory reset/Format Data
Reboot System
From OOS12 Firmware to OOS11 Firmware ROM
------------------------------------------------------
Please only use this right now when you have DDR4 RAM in your phone!
Check DDR RAM type (from Windows cmd)
adb shell getprop ro.boot.ddr_type
0 - represents your device is LPDDR4X (use DDR0 Firmware file)
1 - represents your device is LPDDR5 (use DDR1 Firmware file)
or from Terminal on your phone
getprop ro.boot.ddr_type
0 - represents your device is LPDDR4X (use DDR0 Firmware file)
1 - represents your device is LPDDR5 (use DDR1 Firmware file)
When you are on OOS12 use this from the Orangefox Terminal:
cat /proc/devinfo/ddr_type
Download latest Orangefox 12.1 img file from here
Download OOS11 flashable Firmware for your phone from here or, Oneplus 8t, Oneplus 9r
Download Recovery_OOS11_FW_Android12_decryption.img from here
adb reboot bootloader
fastboot boot Orangefox R12.1 recovery
flash OOS11.0.13.13 Firmware
flash ROM.zip
reboot to bootloader
fastboot boot Recovery_OOS11_FW_Android12_decryption.img
Factory reset/Format Data
Reboot System
ROM Flashing instructions:
(take a look at the Spoiler above if you need to switch OOS Firmware Base for your ROM)
From OOS to custom ROM
- Boot to Orangefox
- Format data
- Switch slot
- Reboot to recovery
- sideload/flash ROM
- sideload/flash Orangefox.zip
- reboot to recovery
- Flash Magisk (Magisk can be installed through Fox addons - Install Magisk as well)
- Reboot to system
From custom to custom ROM
- Boot to Orangefox
- Format Data
- sideload/flash ROM
- sideload/flash Orangefox.zip
- Reboot to recovery
- Flash Magisk (Magisk can be installed through Fox addons - Install Magisk as well)
- Reboot to system
For Updating a custom ROM
- Boot to Orangefox
- sideload/flash ROM
- sideload/flash Orangefox.zip
- Reboot to recovery
- Flash Magisk (Magisk can be installed through Fox addons - Install Magisk as well)
- Reboot to system
The Messages failed to mount system, vendor after flashing a ROM can be ignored.
That is due to mounting those for both ext4 and EROFS and of course you can have only one of them.
If you get a Bootloop after flashing a ROM and having done a Format Data do the below:
Boot to bootloader and:
- fastboot devices
- fastboot -w
- fastboot reboot
Source Code: https://gitlab.com/OrangeFox
Device Tree (A12/A13): https://github.com/Wishmasterflo/device_oneplus_opkona/releases
Device Tree OP8/8Pro FBEv1: https://github.com/SENSEIIIII/twrp_device_OnePlus_instantnoodlep
Wiki/FAQ: https://wiki.orangefox.tech/en/guides
OrangeFox Version: R12.1
Version: V19
Last Updated: 05-Jun-2023
​Changelog
R12.1 V19 05-Jun-2023
- Updated with latest Orangefox source changes
old Changelogs
Credits
* ApexLegend007 for Android 12.1 device Tree
* The-Incognito for Recovery Trees of Oneplus 8T
* YumeMichi For Implementing Erofs and Other Misc
* bigbiff for decryption
* Pranav Talmale for decryption
* Systemad for original tree
* CaptainThrowback for original tree
* mauronofrio for original tree
* BillGoss for Backup and Restore
* Qnorsten for OOS fix
* TWRP team
* OrangeFox team

thanks so much for hookin up the op8 users with a recovery that has some substance
Am I correct in assuming that I'm not seeing anything in my data partition (for backup purposes) because of this?
Data decryption on OP8 and OP8 Pro is only working when using a OP8 series unified ROM which uses FBEv2 encryption.
FBEv1 encryption which the OP8 and OP8 Pro normally uses is not added to Orangefox (yet).
Click to expand...
Click to collapse
Just wanting to make sure I wasn't missing something!

mmoritz said:
thanks so much for hookin up the op8 users with a recovery that has some substance
Am I correct in assuming that I'm not seeing anything in my data partition (for backup purposes) because of this?
Just wanting to make sure I wasn't missing something!
Click to expand...
Click to collapse
Yes correct.

Thank you

Oneplus 8 Pro Android 12 based custom ROMs not working, crash dump

tnchng said:
Oneplus 8 Pro Android 12 based custom ROMs not working, crash dump
Click to expand...
Click to collapse
On which OOS12 Version are you? And do you have that on both slots?
Have you flashed Orangefox or just booted it?
Make sure you have OOS12 c35 or what you are on on both slots before trying to flash anything.
Then just try to fastboot boot Orangefox first and not flash it directly and see if you can install a ROM and boot to it.

I've tried C.36 with crDroidAndroid-12.1-20220721-instantnoodlep-v8.7, lineage-19.1-20221106-nightly-instantnoodlep-signed, it crash dump
and swithed to 11.0.11.11-20220218 crDroidAndroid-12.1-20220721-instantnoodlep-v8.7, lineage-19.1-20221106-nightly-instantnoodlep-signed, it also crash dump

You mean must c.35

tnchng said:
You mean must c.35
Click to expand...
Click to collapse
No c36 should work as well. And have you flashed Orangefox or just booted it? So the crashdump comes after flashing a ROM and trying to boot to system?

just booted, I want to check OrangeFox-R12.1-Unofficial-OPKONA-V13 work first, but crash dump, not flash the zip now. But for the 11.0.11.11, OrangeFox-R12.1 should work

tnchng said:
just booted, I want to check OrangeFox-R12.1-Unofficial-OPKONA-V13 work first, but crash dump, not flash the zip now. But for the 11.0.11.11, OrangeFox-R12.1 should work
Click to expand...
Click to collapse
Hmm strange as it works for someone else on Oneplus 8Pro. So I dont know why it does not work for you. Sounds strange that it just gives a crash dump when booting into it. Normallly that happens if you flash Orangefox to your phone and have not the same OOS Firmweare on both slots!

Every test I made OOS on both slots. No hurry, recovery for 12 need time. I can wait, thanks your hardworking.

tnchng said:
Every test I made OOS on both slots. No hurry, recovery for 12 need time. I can wait, thanks your hardworking.
Click to expand...
Click to collapse
Also I know that there is someone else who build Orangefox recovery a few days ago using FBEv1 for Oneplus 8 and 8 Pro.
As my unified Orangefox now is using FBEv2 since that is what is used on Oneplus 8t and 9r so te Unified Version is using that.
So you will only be able to decrypt data with my unified Orangefox Version when you use some unified ROM which is using FBEv2.
I will check with the one who build Orangefox with FBEv1 for Oneplus 8/8 Pro if he has published that already somewhere.

Maybe the FBEv1, thank you very much. I'll test asap when you share it.

tnchng said:
Maybe the FBEv1, thank you very much. I'll test asap when you share it.
Click to expand...
Click to collapse
OK that Version is not fully ready yet therfor it is not published anywhere yet.

EDIT:
Whoops... just saw the top post... "Orangefox R12.1 can only be flashed to the recovery partition"... Will this affect Stock OOS12 to update in the future? or can I easily restore stock recovery?
****************
Hi! Does this work with OP8 OOS12 unlocked + rooted? can I do "fastboot boot recovery.img"? Not really worry about decrypt data, just want to get in to flash Magisk. OP has been very bad at releasing full ROM, can't extract boot.img for that purpose.
Like many (I think), I try official TWRP to "fastboot boot recovery.img" and the device got stuck... Anyway... I left the phone for few days..., it booted back in fine.

woofwoof75 said:
EDIT:
Whoops... just saw the top post... "Orangefox R12.1 can only be flashed to the recovery partition"... Will this affect Stock OOS12 to update in the future? or can I easily restore stock recovery?
****************
Hi! Does this work with OP8 OOS12 unlocked + rooted? can I do "fastboot boot recovery.img"? Not really worry about decrypt data, just want to get in to flash Magisk. OP has been very bad at releasing full ROM, can't extract boot.img for that purpose.
Like many (I think), I try official TWRP to "fastboot boot recovery.img" and the device got stuck... Anyway... I left the phone for few days..., it booted back in fine.
Click to expand...
Click to collapse
No it will not affect stock OOS to Update.

I'm using EvolutionX 7.3 (Android13) on a Oneplus8Pro. Do you know which version of the recovery do I have to download?
And also, which encryption does the rom use?

Marcyvee said:
I'm using EvolutionX 7.3 (Android13) on a Oneplus8Pro. Do you know which version of the recovery do I have to download?
And also, which encryption does the rom use?
Click to expand...
Click to collapse
No. I dont know. Check with your ROM Support group or just try to fastboot boot the orangefog.img file and see which Version works.

I can boot all three version of the recovery, but it seems none of them can decrypt data. The Data partition dimension is 0mb.
Anyway, is the first time I use orange fox, and i don't know it very well....