Database Develop

[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

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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 me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S21 Ultra G998B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21 Ultra: p3s.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
21.08.2021 - Add Symlinked dynamic partitions to fstab
09.08.2021 - Fix haptic feedback
- Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
01.03.2021 - Initial Release.

Boss!

Boss

Thanks boss..

Boss!

Omg.... Boss and Heroes

Any custom rims for this device yet? Maybe a Pixel Experience ROM?

Any news on rom development by chance?, Just curious thanks.

It will take a big while before custom ROMs, don't expect them too soon

Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.

siriow said:
Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.
Click to expand...
Click to collapse
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.

FreeRunner2017 said:
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.
Click to expand...
Click to collapse
Ok, Thank you

siriow said:
Ok, Thank you
Click to expand...
Click to collapse
Your welcome, any issues feel free to PM me

I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.

Burt Squirtz said:
I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.
Click to expand...
Click to collapse
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.

dr.ketan said:
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.
Click to expand...
Click to collapse
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?

JazonX said:
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?
Click to expand...
Click to collapse
You asked for dirty flash trick right? If erasing data and acc then it's not dirty flash.
I don't have any issue on March secure patch

What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.

JazonX said:
What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.
Click to expand...
Click to collapse
Run multidisabler script in twrp terminal

[RECOVERY][3.5.1][UNOFFICIAL] TWRP Xiaomi Mi 10 [umi]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
/*
*
* We are 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.
*
*/
Features:
- Decryption work
- Otg work
-Vibrator
- Zip Flash
- Mtp/adb
- F2FS support
- Fastbootd
- Adb sideload
- Backup restore and images flash
Not working:
-Tell me
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP.
5-A. You are using Xiaomi.eu Miui or custom Rom?
You can enjoy with a functional Data Decrypt
5-B You are using Miui EEA - Global -Cn or any custom rom that doesn't ship custom vbmeta.
6. Download this zip, copy by pc or using otg and flash this zip that will prevent twrp replacing.​​7. Download VbMeta and flash by fastboot​​
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
​7. Reboot into twrp (Take longer Time) ​​
Code:
fastboot boot "name_of_recovery.img"
​8. Format Data and Reboot​
NOTES:
By Command fastboot boot, recovery will decrypt everytimes you need, also with Global Rom and without patched vbmeta.
Download:
VbMeta
TWRP
(Version tag will follow vendor, a lower version tag than your vendor does not mean that recovery will not work)
Kernel Source: HERE
Donation:
PayPal: paypal.me/manuelbiancodev
Telegram Group: @MBsRoom

Nice! All nice worked for umi 12.2.9 xiaomi.eu. Big thanks man!

Mi 10 Global 12.2.4 RJBEUXM boots TWRP, but the touch screen does not work in TWRP, I can't decrypt. Is there any trick to make it work?

Koppis said:
Mi 10 Global 12.2.4 RJBEUXM boots TWRP, but the touch screen does not work in TWRP, I can't decrypt. Is there any trick to make it work?
Click to expand...
Click to collapse
had you flash umi version ? because if u flashed lmi version touch kernel drivers are differents

Thanks a lot, I had put the wrong TWRP, now it works, Thanks for the help!

Does it work when you install it via OTG?

pascha46 said:
Does it work when you install it via OTG?
Click to expand...
Click to collapse
Yep

Can someone confirm me that we can flash permanently this TWRP ? And not just boot in it by fastboot command ?

Aralas said:
Can someone confirm me that we can flash permanently this TWRP ? And not just boot in it by fastboot command ?
Click to expand...
Click to collapse
Yes, i'm confirm, can flash permanently this TWRP. fasboot boot command not need more. Big thanks to manuelbianco

New instructions for eea and global miui user, post updated

Troj80 said:
Nice! All nice worked for umi 12.2.9 xiaomi.eu. Big thanks man!
Click to expand...
Click to collapse
Hi, I'm also on Miui 12.2.9 and I want to go to 12.5, which tells me that it is running smoothly and good comments about it, but when trying to perform the fasboot boot command I was throwing an error ... so my question is With this TWRP can you proceed to flash and it will work?

@manuelbianco THX Working on PC with the latest weekly 21.2.23 from mi10 umi... thx men .. or install latest weekly 21.3.3 it has implented

Amazing work. Really big thanks. I was getting tired with the fastboot boot every time. Now I only wish we had a custom kernel as well.

冲冲冲

And when excactly do we have to flash this Vbmeta thing? Everytime flashing a new rom or not? I dont get what this vbmeta thing is

miui_UMI_21.2.24 Dev cn
fastboot boot twrp.img. 1)Twrp Welcome Screen wait for a few minutes, then into Decrypt Data. It can decrypt user 0, but failed to decrypt user 999.
2)When next time reboot to recovery, it directly into twrp home, didn't need key to decrypt data, in the end failed to Decrypt Data.

Where is twrp link

dtosun said:
Where is twrp link
Click to expand...
Click to collapse
{
"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"
}

Good afternoon, I currently have the version installed: umi_eea_global_images_V12.2.4.0.RJBEUXM
I can install and start TWRP, but when I do wipe factory reset, or format data, the phone throws the error not possible mount system-root and it only starts in fastboot mode. After this I have to install 12.2.4 again by miflash. They think that the vbmeta will fix what happens to me? I have already tried many times and I am left without a phone for 2 hours and I have to reinstall everything from scratch every time I test ...

Hola,muchas gracias por esta tan esperada actualización,solo encuentro un problema a la hora de realizar copia de seguridad,aborta el proceso,
Mod edit: English translation added
Hello, thank you very much for this long-awaited update, I only found a problem when making backup, abort the process

[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....