Database Develop

[RECOVERY][OFFICIAL][SAGIT][V3.2.1-028-Beta] Red Wolf 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 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.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.1
For devices: Sagit, Mido, Land, Kenzo & Kate
Authors build: dadi11
Kernel: https://github.com/RedWolfRecovery/rw_device
Developers: ATG Droid, dadi11 & Devil7DK
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), dadi11 (for his awesome kernel & mido builds) etc.
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
*[B] Changes for security reasons [/B]*
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- fixed backup/restore of Firmware
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
[B][U]RedWolf-V3.2_027[/U][/B]
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
[B][U]RedWolf-V3.2_026[/U][/B]
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
[B][U]RedWolf-V3.2_025[/U][/B]
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
[B][U]RedWolf-V3.2_024[/U][/B]
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
[B][U]RedWolf-V3.2_023[/U][/B]
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
[B][U]RedWolf-V3.1_022[/U][/B]
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
[B][U]RedWolf-V3.1_021[/U][/B]
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
[B][U]RedWolf-V3.1_020[/U][/B]
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
[B][U]RedWolf-V3.1_019[/U][/B]
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
[B][U]RedWolf-V3.1_018[/U][/B]
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
[B][U]RedWolf-V3.1_017[/U][/B]
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
[B][U]RedWolf-V3.1_016[/U][/B]
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
[B][U]RedWolf-V3.1_015[/U][/B]
- Updated with the latest TWRP changes
- Added flashlight switch on mido
[B][U]RedWolf-V3.1_014[/U][/B]
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
[B][U]RedWolf-V3.1_013[/U][/B]
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
[B][U]RedWolf-V3.1_012[/U][/B]
- added F2FS support for mido
- added Night Mode (kcal) support for mido
[B][U]RedWolf-V3.1_011[/U][/B]
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Downloads:
Latest build for Xiaomi Mi 6 (sagit)
RedWolf-027-sagit.img
Screenshots:
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
Red Wolf Recovery Project for Xiaomi Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
dadi11, ATG Droid, Devil7DK
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-04-07
Last Updated 2018-04-07

Reserved
bugs: flashlight doesn't work, yet
https://t.me/joinchat/FZlpFECo9qt3MT5oRn-Bcg

Thanks Great Work

if you face issues with mounting Modem, redownload and flash the v27 image again

i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?

I flash the newest version, V3.2.1-027. After I enter system, I find the recovery is overwrite by system.
Steps:
1. flash recovery, Red Wolf V3.2.1-027.
2. Enter Recovery
3. Reboot to system
4. Reboot to recovery, the recovery is restored to original.
OS version: MIUI V9.2.3.0.OCAMIEK
P.S. I have renamed the file, /system/bin/install-recovery.sh, to /system/bin/install-recovery.sh.bak.
Does the under function work? or How to let it work? Thx.
"Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM"

@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?

zilan said:
i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?
Click to expand...
Click to collapse
yes it works fine
planetera said:
Does it support Oreo decryption and vendor support?
Can we flash treble images with it?
Click to expand...
Click to collapse
no you can't
dewa5227 said:
@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?
Click to expand...
Click to collapse
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data

finally,it get stable,what a good thing

It does not decrypt the files.

ibrahimyuksel said:
It does not decrypt the files.
Click to expand...
Click to collapse
why would it? that's what the encryption is for. format /data to disable encryption and have a full access..

dadi11 said:
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data
Click to expand...
Click to collapse
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.

slitaz said:
finally,it get stable,what a good thing
Click to expand...
Click to collapse
flashlight is still not running,and i can't change some settings

dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
same problem always goes back to stock recovery and when I try flash it with no-verity-opt-encrypt-5.1 my phone softbrick at miui logo after reboot

dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
I solved it, first u need flash twrp then flash magisk or supersu > reboot system > instal apk like root explorer/mixplorer > open root files > find system/bin/install-recovery.sh then rename > system/bin/install-recovery.sh.bak (i used mixplorer) turn off ur phone > press volume up + power button > say goodbye for mi recovery

I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.

spiderpl said:
I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.
Click to expand...
Click to collapse
it's not a rom. search for the guide and you will find it for sure

planetera said:
Can you please update this twrp to 3.2.1.1 base? Because it does not support Oreo encryption :/
Click to expand...
Click to collapse
it does. and if it's not then wait for next build

This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery

spiderpl said:
This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery
Click to expand...
Click to collapse
do not use fastboot boot command

[ROM][OFFICIAL][enchilada][10.0]crDroid Android[v6.27]

{
"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"
}
​
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring many of the best features in existence today.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Syslog (free, open source, available on Play store and F-droid) is your friend.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0

Notes:
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)

Thanks dev. This is a great ROM
When you say latest fw, you are talking about OOS Pie or H2OS Q?

firebird11 said:
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
To be defined
First time installing crDroid to your Op6, or coming from another ROM:
- Be on the latest firmware
- Make sure you're running latest TWRP
- Copy GApps and crDroid zip to your internal storage
- Disable your screenlocks
- Boot into Recovery
- Wipe cache,data
- Flash crDroid zip
- Flash TWRP zip
- Reboot to recovery
- Flash GApps zip
- Flash Magisk zip
- Reboot system
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such as Xposed!
- have modified system files
DONATE
crDroid Website
Telegram Oneplus6/6t group
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 6
Contributors
firebird11, neobuddy89, gwolfu
Source Code:https://github.com/crdroidandroid
Source Code Kernel:https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LOS
Version Information
Status: Testing
Created 2019-10-16
Last Updated 2019-10-16
Click to expand...
Click to collapse
Any bugs or something not working?
Will try this weekend.

Thank you dev

Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.

veronesi.n said:
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
Click to expand...
Click to collapse
Same here, I think new magisk 20 breaks it , because with 19.4 working fine

savinjo22 said:
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
Click to expand...
Click to collapse
Sorry I said not rooted ?... I wanted to say that magisk wasn't installed.

i tryed this rom on my htc m8 and i love it and i will try it again on oneplus 6

Is this also implemented already in android 10? TIA

tiga016 said:
View attachment 4847745
Is this also implemented already in android 10? TIA
Click to expand...
Click to collapse
Yes there's some customization settings.

dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?

backtrack292 said:
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
Click to expand...
Click to collapse
I assume you used the 'Green Box' link in Sourceforge? That always trips people up. That link is the latest ROM across all crDroid devices. (Currently the OP5 'Cheeseburger') Or next time actually read the file name before flashing.
Ignore that Green Box. Just pretend it doesn't exist. Use the links underneath to get the Enchilada downloads.

a new v6 build is up !
october security and statusbar padding are new

firebird11 said:
a new v6 build is up !
october security and statusbar padding are new
Click to expand...
Click to collapse
does it supports signature spoofing?

just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!

What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041

meistr91 said:
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
Click to expand...
Click to collapse
thank you for the suggestion... gone well beyond the link's status by the time i read this (on oos from local update), so may just wait it out for a working twrp solution - been too long since last used OOS anyway!

new v6 builds are up !

firebird11 said:
new v6 builds are up !
Click to expand...
Click to collapse
Can be flashe with oos 10 base ?

[RECOVERY][FBE]TWRP 3.4.0-0[Onclite][UNOFFICIAL]

{
"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.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Introduction:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices.It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images.It is, therefore, often installed when flashing, installing, or rooting Android devices,although it isn't dependent on a device being rooted prior to installation. [Wiki]
Click to expand...
Click to collapse
Changelogs:
What's new in 3.3.1-0:
Code:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Build - 02/04/2020
Code:
* Initial Build
What's new in 3.4.0-0:
Code:
* System As Root (SAR)
- Fix backup and restore using SAR - dianlujitao
- System mount point - Chaosmaster
- ORS - Chaosmaster
- Zip install - Chaosmaster
- system_root bind mount to /system - Chaosmaster
- Autodetection of SAR - Chaosmaster
* Digest
- fix creation of digests for sub-partitions (was bugfix applied to many devices since last year) - Bigbiff
* Encryption
- ext4Crypt Wrapped Key Update - Peter Cai
- Fix upgrading encryption key if export fails - Peter Cai
- Fix wrapped key support for devices without metadata partition - mauronofrio
- Don't skip decryption when using block map file in order to write to /data in ORS - CaptainThrowback
- FDE - Decrypt master key first - AndroidableDroid
- vold_decrypt - set Android version and patch level automatically - CaptainThrowback
- Set wrapped decrypt support by twrp flag - Peter Cai
- Don't try wrapped support unless needed - mauronofrio
- restore ext4 policy on /data/cache - Bigbiff
- multiuser decryption - Noah Jacobson
- FDE retry - AndroidableDroid
* TWRP App
- unmount system after checking for app - Bigbiff
* Prebuilt updates -
- android.hardware.confi[email protected] - cryptomilk
* Compilation Fixes:
- TW_EXFAT_FUSE compilation fixes - Bigbiff
- libuuid - cryptomilk
- 'system/etc/ld.config.txt' not found error - Martin Dünkelmann
* Language Updates:
- Portugal - Vasco Machado
- Dutch - Ian Macdonald
- Turkish - Fatih Fırıncı
- Localisation of Backup_Tar: Ian Macdonald
* ld.config.txt
- updates for 8.x trees - CaptainThrowback
- fix search path for /sbin - CaptainThrowback
- /sbin should come first in search path - Ian Macdonald
* General Bugs
- Fix persistent log storage - SyberHexen
- Compress Persistent Logs - Bigbiff
- FB2PNG compilation errors - Bigbiff
- exclude per_boot from backups - Darth9
- Unmount all directories that point to same block device - AndroidableDroid
- Blank screen fixes - Sean hoyt
- Toolbox is default on android-9+ - mauronofrio
* Cleanup -
- Typo fix in comment - VDavid003
- newlines in ext4crypt - CaptainThrowback
- TW_OEM_BUILD compilation issue - Patrick Zacharias
- Fix Dependency requirements - Dees_Troy
- Fix Symbolic links for BB and Toolbox - Dees_Troy
* Bootloader Message
- cleanup - Alessandro Astone
- add configurable offsets
* Error Cleanup
- uevent errors and decryption error - mauronofrio
- using copy_file to copy files from /etc - CaptainThrowback
- ueventd access to /acct - early directory creation in init - cryptomilk
* Haptics
- TSP Driver - LameMonster82
- QTI Input - AndroidableDroid
* update_engine
- read all asserts - Hernán Castañón
* Resetprop
- Add Resetprop from Magisk - CaptainThrowback & mauronofrio
- compile from source - Chaosmaster
- fix for android-7 and earlier - Chaosmaster
- cleanup for spaces in properties - AndroidableDroid
* Properties
- Add Property override - Chaosmaster
* Backuptool
- mount system and vendor for A/B installs for backuptool - Chaosmaster
* twrpTar
- fix backup freezes when pigz and openaes are used - Fabrice Bellet
* Zip Installs
- Info for A/B zip installing to inactive slot - Chaosmaster
- Reboot to system button now allows to be rebooted to different partitions after zip install
- progressbar rework - Chaosmaster
* Magisk updates
- update binaries from source - AndroidableDroid
* A/B Updater Zip Template
- rewrite A/B installer zip from scratch using a new generic template and latest magiskboot - osm0sis
- installer zip support for recovery_a/recovery_b partition ramdisks on newer 2SI SAR A/B devices - osm0sis
- generate installer zips for all prod A/B devices - bigbiff
- improve installer zip dump/write speed and add more error catching - arter97 & osm0sis
* OZIP Encryption Support
- add OZIP encryption - mauronofrio
* File Selector
- Support for more extensions in File Selector - mauronofrio
Build - 20/08/2020
Code:
* TWRP-3.4.0-0 release
* Fixed CPU temperature
Click to expand...
Click to collapse
Important Notes:
* This recovery supports only File-based Encryption.
* Use this recovery only for Custom Roms with File-Based Encryption support.Ask your ROM maintainer for more info
* As our MIUI stock rom uses Full-Disk Encryption,this recovery don't support that
Click to expand...
Click to collapse
Bugs:
* You tell me if you find anything
Click to expand...
Click to collapse
Download Link:
TWRP-3.3.1-0 : Gdrive[zip]
TWRP-3.4.0-0 : Gdrive[zip]
Installation:
* Download and extract the zip file provided above
* Rename the extracted img file to recovery.img
* Method 1: Flash through fastboot mode
Code:
fastboot flash recovery recovery.img
* Method 2: Use any other custom recovery to flash the recovery img
Click to expand...
Click to collapse
Sources:
* TWRP source
* Device Source
Click to expand...
Click to collapse
Support:
* If you like my work, don't forget to hit thanks button.:good:
*Buy me a packet of biscuit, PayPal
Click to expand...
Click to collapse
XDA:DevDB Information
TWRP with FBE for Redmi 7, Tool/Utility for the Xiaomi Redmi 7
Contributors
Dhina_17
Version Information
Status: Stable
Stable Release Date: 2020-04-02
Created 2020-04-02
Last Updated 2020-08-19

Reserved

pro

Wahoo! Keep up the great work, bro!

Fantastic! Thanks..
Question: It will be added supported rom list later? Thank you very much
Odesláno z mého Redmi 7 pomocí Tapatalk

Its great to see this development but the older unofficial version works batter. After installing latest aosp fbe rom with this latest recovery when i tap reboot to system it reboots to recovery. Installed fbe rom that said install with this version of recovery but after trying again and again it boots back to recovery. Used latest orangfox recovery based on this build but it got stucked in recovery logo. Flashed this recovery again from fastboot and now this recovery to stucked at logo. Tried to install older unofficial twrp from fastboot and it workes. Installed fbe rom that said install with latest but installed with older twrp and its working. Everytime Whenever i download an updated recovery from this official post it works worst then the unofficial build. The unofficial build is more stable no problem at all. Now using the TWRP-3.3.2B-0317-REDMI7-CN-wzsx150.img.

Mes shahadat said:
Its great to see this development but the older unofficial version works batter. After installing latest aosp fbe rom with this latest recovery when i tap reboot to system it reboots to recovery. Installed fbe rom that said install with this version of recovery but after trying again and again it boots back to recovery. Used latest orangfox recovery based on this build but it got stucked in recovery logo. Flashed this recovery again from fastboot and now this recovery to stucked at logo. Tried to install older unofficial twrp from fastboot and it workes. Installed fbe rom that said install with latest but installed with older twrp and its working. Everytime Whenever i download an updated recovery from this official post it works worst then the unofficial build. The unofficial build is more stable no problem at all. Now using the TWRP-3.3.2B-0317-REDMI7-CN-wzsx150.img.
Click to expand...
Click to collapse
I think you are in wrong thread.. its not official twrp thread.. go to that. Thanks

TWRP-3.4.0-0 is up

Works better than official build of TWRP.

@Dhina_17
Just reporting a minor bug:
The status bar position is too low (there is a noticeable gap/padding between the notch and the top border of the status bar).

I have a problem, please help me. After installed the 3.4.0.0. image, the phone always forget my pin/pattern/password. If I reboot in recovery mode and delete all of the *.key and lockprint.* files the phone works without any pin/pattern/password until I set a new one. But when I set a new pin/pattern/password and turn off the screen, after I try unlock my screen, it always said the pin/pattern/password is wrong, and can't unlock my screen. Only if I reboot it again in recovery mode and delet the files. But in this case I don't have any screen lock security. The other problem is the fingerprint sensor is not working after installed twrp 3.4.0.0. What can I do?

sbalika0ó1983 said:
I have a problem, please help me. After installed the 3.4.0.0. image, the phone always forget my pin/pattern/password. If I reboot in recovery mode and delete all of the *.key and lockprint.* files the phone works without any pin/pattern/password until I set a new one. But when I set a new pin/pattern/password and turn off the screen, after I try unlock my screen, it always said the pin/pattern/password is wrong, and can't unlock my screen. Only if I reboot it again in recovery mode and delet the files. But in this case I don't have any screen lock security. The other problem is the fingerprint sensor is not working after installed twrp 3.4.0.0. What can I do?
Click to expand...
Click to collapse
I've only experienced that in the official version of TWRP that's why I stopped using that.

@Dhina_17 Works great! Any plans to add /data decryption support?

[RECOVERY][Realme 6 Pro] TWRP Recovery [Stable]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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

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