{
"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.3.1
PitchBlack version: 2.9.0
For device: onclite
Maintainer/Authors build: Ashu Sharma
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android-device-xiaomi-onclite-pbrp
PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources (Pie is on the way)
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 Fastboot
Extract the Downoaded zip file
Grab the recovery.img from extracted folder
Reboot device in fastboot
Run "fastboot flash recovery recovery.img" from fastboot
Boot into recovery
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
PitchBlack-onclite-2.9.0-20190624-0606-OFFICIAL
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
To decrypt data:
1. Backup Boot.img
2. Wipe data and flash patched boot.img by magisk or Magisk zip file (You Can Patch boot.img through magisk app)
3. Reboot
Hit Thanks Button If I Helped You:good:
:laugh::laugh::laugh:
Nice thread, kindly explain the process of patching the the boot.IMG
And will I be able to use OTA from notification using this recovery even after I've flashed magisk?
Thanks for your anticipated response
Stephinnoye said:
Nice thread, kindly explain the process of patching the the boot.IMG
And will I be able to use OTA from notification using this recovery even after I've flashed magisk?
Thanks for your anticipated response
Click to expand...
Click to collapse
To patch boot.img
1. Open magisk
2. Click in install and select patch image
3. Find your boot.img
4. Done
5. Boot into recovery, wipe data and flash patched image
To apply OTA:
https://c.mi.com/thread-1782169-1-1.html
ashu7073 said:
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.3.1
PitchBlack version: 2.9.0
For device: onclite
Maintainer/Authors build:Ashu Sharma
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
......
..... . .
... . . .
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
To decrypt data:
1. Backup Boot.img
2. Wipe data and flash patched boot.img by magisk or Magisk zip file (You Can Patch boot.img through magisk app)
3. Reboot
Click to expand...
Click to collapse
After installing RECOVERY via fastboot, Is it necessary to backup boot image ?
There is no decrypt. Zip to flash after recovery coz i don't want to use magisk to decrypt data ?
[email protected] said:
After installing RECOVERY via fastboot, Is it necessary to backup boot image ?
There is no decrypt. Zip to flash after recovery coz i don't want to use magisk to decrypt data ?
Click to expand...
Click to collapse
Decrypt.zip is included in PitchBlack zip file. You've to flash again zip from any recovery or From Pitchblack to Get decrypt zip and other files which included in PitchBlack recovery zip file
Or you can use this : https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
It is Not Necessary to Backup boot.img after Flashing recovery But it is Recommended to Backup boot.img Before Flashing ForceDecrypt zip, patched boot image or Magisk.
In Case your Device got Stuck in Bootloop after flashing decrypt zip, You can Restore Boot.img.
ashu7073 said:
To patch boot.img
1. Open magisk
2. Click in install and select patch image
3. Find your boot.img
4. Done
5. Boot into recovery, wipe data and flash patched image
To apply OTA:
https://c.mi.com/thread-1782169-1-1.html
Click to expand...
Click to collapse
Thanks bro
But must u patch the boot.IMG? Wats the need for doing that?
All I want is root (using magisk) and a custom recovery
Thanks
---------- Post added at 15:38 ---------- Previous post was at 15:36 ----------
ashu7073 said:
Decrypt.zip is included in PitchBlack zip file. You've to flash again zip from any recovery or From Pitchblack to Get decrypt zip and other files which included in PitchBlack recovery zip file
Or you can use this : https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
It is Not Necessary to Backup boot.img after Flashing recovery But it is Recommended to Backup boot.img Before Flashing ForceDecrypt zip, patched boot image or Magisk.
In Case your Device got Stuck in Bootloop after flashing decrypt zip, You can Restore Boot.img.
Click to expand...
Click to collapse
What is d essence of this decrypt zip of a thing?
Stephinnoye said:
Thanks bro
But must u patch the boot.IMG? Wats the need for doing that?
All I want is root (using magisk) and a custom recovery
Thanks
Click to expand...
Click to collapse
It's optional and alternative to direct magisk zip
It's upto you. Flash magisk or patched image
ashu7073 said:
It's optional and alternative to direct magisk zip
It's upto you. Flash magisk or patched image
Click to expand...
Click to collapse
So once uve this pitch recovery, and I flashed magisk, I'm gud to go?
Thanks
Please help bro
I've pitchblack recovery now,but whenever I boot to recovery,it keep asking me to decrypt data .
I've tried to backup my boot.img but to no avail
Also, whenever I flashed anything,I get this response "unable to mount storage" and recovery can't read my internal storage
Kindly help pls
Thanks in anticipation
Stephinnoye said:
Please help bro
I've pitchblack recovery now,but whenever I boot to recovery,it keep asking me to decrypt data .
I've tried to backup my boot.img but to no avail
Also, whenever I flashed anything,I get this response "unable to mount storage" and recovery can't read my internal storage
Kindly help pls
Thanks in anticipation
Click to expand...
Click to collapse
This is problem in PitchBlack recovery. It can't decrypt data. I'm working on a fix. Untill then you can wipe data in pitchblack once to decrypt it.
Or go back to another recovery
ashu7073 said:
This is problem in PitchBlack recovery. It can't decrypt data. I'm working on a fix. Untill then you can wipe data in pitchblack once to decrypt it.
Or go back to another recovery
Click to expand...
Click to collapse
I've wiped data, but whenever I go-to recovery,it will still ask me to decrypt
And what abt the inability of the recovery to read my internal storage?
I opted in for pitchblack so that I can use OTA (tho I still don't get the procedures to enable me use OTA,but I'm sure u will still put me tru personally,that site seems complicated)
Stephinnoye said:
I've wiped data, but whenever I go-to recovery,it will still ask me to decrypt
And what abt the inability of the recovery to read my internal storage?
Click to expand...
Click to collapse
You've to flash magisk to disable force encryption
Or just flash your stock boot.img, pitchblack automatically disables force encryption
ashu7073 said:
You've to flash magisk to disable force encryption
Or just flash your stock boot.img, pitchblack automatically disables force encryption
Click to expand...
Click to collapse
I've flashed magisk, lemme see if the recovery can read my internal storage now
Modified: still can't read my internal storage
Stephinnoye said:
I've flashed magisk, lemme see if the recovery can read my internal storage now
Modified: still can't read my internal storage
Click to expand...
Click to collapse
Flashing magisk is not going to help with decrypting data. Either your recovery can decrypt, or it can't. If it can't, and you want to remain encrypted, then you will need another recovery which can decrypt. If you don't mind not being encrypted, then you can format your data ("format", not "wipe"). That will obliterate all the contents of your internal storage - so you had better backup all your photos, videos, etc, before formatting data.
For me works the recovery...but pc doesn't recognize device then...
Work in redmi 7 Global EEA
So whats up with this recovery is it usable or not? Can encryption be removed with formatting data? And also does miui ota survival work? I would like to use this recovery with xiaomi eu rom
Immortal0907 said:
So whats up with this recovery is it usable or not? Can encryption be removed with formatting data? And also does miui ota survival work? I would like to use this recovery with xiaomi eu rom
Click to expand...
Click to collapse
Yes, you can
Wipe data and flash any encryption disabler zip
Or patch boot.img with magisk and flash with PB recovery
Pb disables dm-verity so it may cause boot loop on miui. you've disable dm-verity disabler
ashu7073
How Disable Dm-verify method here, automatically or from where?!.
Don`t use this recovery if you are flashing xiaomi.eu rom fingerprint / Pin won`t work no matter what you do use LR Team TWRP.
Related
{
"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 (or isn't ? who am I to judge ?)
*
* 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.
*
*/
Team Win Recovery Project 3.4.1 for Realme 6 Pro
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.
Ported From Realme X50 5G
• by ctapchuk from 4pda
Most Bugless Recovery Right Now
Installation
1. Disable verified boot first
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img which is extracted from current stock rom ozip file
2. Flash downloaded twrp
Code:
fastboot flash recovery twrp.img
3. Reboot to recovery
Code:
fastboot reboot recovery
List of features :
• Decryption of storage works on latest Stock firmware (September security patch)
• Successful installation of any ROM's
• External sdcard & USB-OTG support
• Additional features such as close AVB2.0 (disabled-verify on vbmeta), disable replace TWRP
• Working mounting of dynamic partitions (r/o only)
• Additional backup/restore partitions list (except system, vendor and etc)
Download :
https://drive.google.com/file/d/1NWS74xHgyIKwpTd5sZ6af9ukroXF7VAp/view?usp=sharing
Version Information
Status : Stable
Current Stable Version : 3.4.1b_0507
Stable Release Date : September 30, 2020
Reserved
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Richardo87 said:
The same issue i was getting with the previous TWRP versions, cannot access MTP storage. Also while phone on, cannot copy anything on storage.
Click to expand...
Click to collapse
Please provide screenshots of your problem. I assume that you are trying to copy files to an encrypted internal storage. Decrypt /data or copy files to SD card
Is this compatible with build number RMX2061_11_A.35? Thank you!
Sent from my RMX2061 using XDA Labs
ByinAlbirt said:
Is this compatible with build number RMX2061_11_A.35?
Click to expand...
Click to collapse
Yes
Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
No need i guess. Try 'Disable Replace TWRP' and reboot ...
debdeep98 said:
Yes
Click to expand...
Click to collapse
Thank you so much! I have successfully installed TWRP Recovery in my realme 6 Pro build number RMX2061_11_A.35.
Sent from my RMX2061 using XDA Labs
Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
All you need is vbmeta.img from your stock ROM.
I used above instructions and everything work just fine, including decryption of internal storage.
@Kevin Saiza thank you for your good work.
Everything's working as expected.
Right now I'm using:
Firmware A.35
LR.TWRP 3.4.1B_30.09
Magisk 21.0 (pass safety net check)
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
neoxcool said:
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Click to expand...
Click to collapse
Coming Soon
Andres88z said:
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
Click to expand...
Click to collapse
Yes why not .
Kevin Saiza said:
Yes why not .
Click to expand...
Click to collapse
Some problem with RMX2063. You try whit RMX2061
Sorry Is 2063
thank's
LR.TWRP 3.4.2B_05.10 for RMX2061 Ported from Xiaomi Black Shark 3 by Ctapchuk & logotoy73
Change extention to .img
https://anonfiles.com/hfcehcd1p9/LR.TWRP_3.4.2B_05.10_for_RMX2061_img
Changelog:
• Port from Xiaomi Black Shark 3
• Upgrade to version 3.4.2
• Fixes in Russian language
• Changed the font for English language
• Fixed fastbootd
• A/B table selection Disabled
• Correct display of the status bar
If i only boot, i need flash vbmeta?
I need urgent help please the twrp does not recognize my otg it only recognizes the sd but the otg does not what should I do to make it recognize it please help
:good:
Can't delete file from phone with root explorer so i tried with TWRP as usualy and for the first time IT DOESNT WORK!! Never seen that before. Though system's not mounted as read only. What to do..?
Do nothing. vendor, product and system partitions are R/O, because they are part of new type partition named "super". It is dynamic partition that is not editable.
Take a look here for details
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
{
"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
{
"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 to expand...
Click to collapse
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 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.
*/
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.2
- PitchBlack version: 3.1.0
- Maintainer: Nazim @naz664
- For device: M21/M215f
- PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject/manifest_pb
- Device tree: https://github.com/PitchBlackRecoveryProject/android_device_samsung_m21-pbrp
- Kernel tree:
https://github.com/naz664/android_kernel_samsung_m21
- PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
- Fully native android like UI
- 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
- Many bug fixes & optimization & much more
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
- After installation reboot the recovery
- Enjoy
* If you are getting vbmeta error flash null vbmeta
From PC
- Download PitchBlack Recovery flashable zip from bellow
- Extract the PBRP zip
- Tar the recovery file and flash via odin in Ap block
- 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
- Added support to directly flash images in logical partition
- Added dtbo,vbmeta partition backup and restore support
- Disabled dm verity by default
- Fixed MTP
- Fixed flashlight
Credits:
- @Yilliee for the base tree
- @Chaitanya_Yeranagula and PBRP team for all your help
- And all the testers for their reports
Downloads
Samsung Galaxy M21 | m21 - PitchBlack Recovery Project
PBRP Version: 3.1.0 Maintainer: Nazim
pitchblackrecovery.com
Nice job!!
Awesome work dev!
Clutchmaster_OP said:
Nice job!!
Click to expand...
Click to collapse
Thankz bro
Daniel~007 said:
Awesome work dev!
Click to expand...
Click to collapse
Thankz
Tried to flash (both trough TWRP & Tar file flash) but booting into Download Mode only. Its for M21/M215F, is that why its not working on M215G?
Its showing some red error msg like Custom Binary Invalid & vbmeta, something like that.
OldNoobOne said:
Tried to flash (both trough TWRP & Tar file flash) but booting into Download Mode only. Its for M21/M215F, is that why its not working on M215G?
Its showing some red error msg like Custom Binary Invalid & vbmeta, something like that.
Click to expand...
Click to collapse
Try flashing null vbmeta via Ap block of odin
naz664 said:
Try flashing null vbmeta via Ap block of odin
Click to expand...
Click to collapse
Same error repeats :
ODIN MODDE (AVB Fail)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
I even tried flashing another vbmeta zip file (906kb) which had worked before during flashing GSI but even after that I got same error.
OldNoobOne said:
Same error repeats :
ODIN MODDE (AVB Fail)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
I even tried flashing another vbmeta zip file (906kb) which had worked before during flashing GSI but even after that I got same error.
Click to expand...
Click to collapse
Flashing gsi doesn't need null vbmeta.
* Extract the zip
* Flash recovery.img into recovery partition using any other recovery
* And check if ure getting vb meta error or not
If yes try flashing the vbmeta file i attached before
* If the problem still persist contact me on telegram @naz664
naz664 said:
Flashing gsi doesn't need null vbmeta.
* Extract the zip
* Flash recovery.img into recovery partition using any other recovery
* And check if ure getting vb meta error or not
If yes try flashing the vbmeta file i attached before
* If the problem still persist contact me on telegram @naz664
Click to expand...
Click to collapse
1) Actually null vbmeta was the issue I was facing on SM-M215G (while flashing GSI) and as per Dev GuruPrasadAH, he gave me null vbmeta file which solved the problem and after that GSI booted.
2) I already had done that, when i had flashed recovery img to recovery partition, same error was showing.
3) Now the phone only boots to download mode, so I think I should flash stock ROM again.
OldNoobOne said:
1) Actually null vbmeta was the issue I was facing on SM-M215G (while flashing GSI) and as per Dev GuruPrasadAH, he gave me null vbmeta file which solved the problem and after that GSI booted.
2) I already had done that, when i had flashed recovery img to recovery partition, same error was showing.
3) Now the phone only boots to download mode, so I think I should flash stock ROM again.
Click to expand...
Click to collapse
Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
Click to expand...
Click to collapse
GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Does that recovery working for you ?
naz664 said:
Does that recovery working for you ?
Click to expand...
Click to collapse
As stupid as this may sound, I dont have the phone anymore. Upgraded to redmi note 10 pro max. But, I do have some experience and can help out after honework and classwork.
I'm not a leech who spampings for eta lol
GuruPrasadAH said:
As stupid as this may sound, I dont have the phone anymore. Upgraded to redmi note 10 pro max. But, I do have some experience and can help out after honework and classwork.
I'm not a leech who spampings for eta lol
Click to expand...
Click to collapse
Ooh kk can anyone confirm that ?
naz664 said:
Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664
Click to expand...
Click to collapse
Thanks no problem naz664
GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Oh Dev GuruPrasadAH, nice to meet you again
My phone only booting to Download Mode , so after I restore from backup I will have ADB access again then i'll run the above command and paste it here.
OldNoobOne said:
Thanks no problem naz664
Click to expand...
Click to collapse
Unified orangefox recovery for exynoss9611 working for you ?
naz664 said:
Unified orangefox recovery for exynoss9611 working for you ?
Click to expand...
Click to collapse
OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad
OldNoobOne said:
OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad
Click to expand...
Click to collapse
Ok thankz for the report.
I used ofox tree as base if it didn't boot then no hope for this one too lol
{
"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"
}
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
Downloads:
twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5
twrp_3.7.0_12-2_X200XXS1CWA3.img
Change Log:
v3.7.0_12-2 (2023-02-28):
Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
v3.7.0_12-1 (2023-01-22):
Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.
Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.
Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.
Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?
As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.
I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?
Not unless you can recieve ota while rooted.
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?
Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com
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....