Develop Bugs

[RECOVERY] [UNOFFICIAL] LR.Team TWRP 3.3.1-1119 for onclite by wzsx150

Disclaimer:
HTML:
/* Your warranty is now void! I'm not responsible for bricked devices, dead SD cards or anything else that may occur to you and / or your device.
* Do it at your own risk!
This recovery was not made by me, i'm just sharing it in easier ways to download. The guy behind this is wzsx150, thank him for it.
After a lot of pain researching and trying to download from Baidu servers i finally managed to get this custom TWRP to get rid of force encryption on stock MIUI because this recovery can successfully decrypt with no need to do a format data.
Just installed magisk v20.2 on stock MIUI global 11.0.4 and it works. :good:
Info
- Based on TWRP 3.3.1
- Build date: 2019.11.19
- Model: Redmi 7, Red Rice 7
- Developer: wzsx150 (profile)
Install Instructions
Warning: unlocked bootloader needed!
Fastboot
1. Download IMG file below
2. Rename file to recovery.img and put it into your adb path (if you don't have adb check this link)
3. Reboot your device into fastboot mode by holding down vol - and power button while device is off and connect to PC
4. Open cmd in your adb path and run the following command: fastboot flash recovery recovery.img
5. Run fastboot reboot, and hold down vol + key until device enters into twrp
Custom Recovery
1. Download ZIP file below to internal storage
2. Reboot to recovery
3. Install zip
4. Reboot to recovery
Downloads
IMG: https://drive.google.com/uc?id=16zXoYeviDUeV9zsSeDjyi_P8NnQkJhLr&export=download
ZIP: https://drive.google.com/uc?id=1ZF4C5-B9rlHKJVO0GbtS_ZjT5VlX1taH&export=download
Special Thanks
- TeamWin for building TWRP for a lot of devices, including this one
- wzsx150 and LR.Team for making this mod
- Firmwarex.net for providing a free Baidu account to download from their servers
Source: https://www.weibo.com/6033736159/IgY1Ex98h?from=page_1005056033736159_profile&wvr=6&mod=weibotime

Works backups AND restore opción?

mcf7 said:
Disclaimer:
/* Your warranty is now void! I'm not responsible for bricked devices, dead SD cards or anything else that may occur to you and / or your device.* Do it at your own risk!
This recovery was not made by me, i'm just sharing it in easier ways to download. The guy behind this is wzsx150, thank him for it.
After a lot of pain researching and trying to download from Baidu servers i finally managed to get this custom TWRP to get rid of force encryption on stock MIUI because this recovery can successfully decrypt with no need to do a format data.
Just installed magisk v20.2 on stock MIUI global 11.0.4 and it works. :good:
Info
- Based on TWRP 3.3.1
- Build date: 2019.11.19
- Model: Redmi 7, Red Rice 7
- Developer: wzsx150 (profile)
Install Instructions
Warning: unlocked bootloader needed!
Fastboot
1. Download IMG file below
2. Rename file to recovery.img and put it into your adb path (if you don't have adb check this link)
3. Reboot your device into fastboot mode by holding down vol - and power button while device is off and connect to PC
4. Open cmd in your adb path and run the following command: fastboot flash recovery recovery.img
5. Run fastboot reboot, and hold down vol + key until device enters into twrp
Custom Recovery
1. Download ZIP file below to internal storage
2. Reboot to recovery
3. Install zip
4. Reboot to recovery
Downloads
IMG: https://drive.google.com/uc?id=16zXoYeviDUeV9zsSeDjyi_P8NnQkJhLr&export=download
ZIP: https://drive.google.com/uc?id=1ZF4C5-B9rlHKJVO0GbtS_ZjT5VlX1taH&export=download
Special Thanks
- TeamWin for building TWRP for a lot of devices, including this one
- wzsx150 and LR.Team for making this mod
- Firmwarex.net for providing a free Baidu account to download from their servers
Source: https://www.weibo.com/6033736159/IgY1Ex98h?from=page_1005056033736159_profile&wvr=6&mod=weibotime
Click to expand...
Click to collapse
Thanks a lot ? so this should work to install any custom rom? Like the pixel experience one?
Sent from my Xiaomi Redmi 7 using XDA Labs

Jojethegamerpro said:
Works backups AND restore opción?
Click to expand...
Click to collapse
I haven't tested but it should work

SammyInTheCity said:
Thanks a lot ? so this should work to install any custom rom? Like the pixel experience one?
Click to expand...
Click to collapse
If you're planning to install a custom rom, any custom recovery should work, including this one.
The main advantage of using this recovery is that you can bypass the stock rom (maybe stock based roms too) force encryption to access your partitions on recovery.

mcf7 said:
If you're planning to install a custom rom, any custom recovery should work, including this one.
The main advantage of using this recovery is that you can bypass the stock rom (maybe stock based roms too) force encryption to access your partitions on recovery.
Click to expand...
Click to collapse
Okay thanks, I have my bootloader locked at the moment, but when I finally am able to unlock it I'll definitely use this
Sent from my Xiaomi Redmi 7 using XDA Labs

Thank you for sharing

Ask password for decryption
But my phone isn't encrypted
Tried my lock screen password it didn't work
Tried to remove all passwords but still asks for password

hamedhd said:
Ask password for decryption
But my phone isn't encrypted
Tried my lock screen password it didn't work
Tried to remove all passwords but still asks for password
Click to expand...
Click to collapse
Which recovery did you used before this? And what's your rom?
For the first time i used LR.Team's recovery i installed recovery, did a format data(due to the password issue as you), installed miui global and magisk and the system booted properly and after that recovery didn't asked for password anymore and i've been able to mount partitions and do other stuff.

I can't flash gapps using this twrp, fix it please

Me_Only said:
I can't flash gapps using this twrp, fix it please
Click to expand...
Click to collapse
I'm not the dev behind this project, i'm just sharing wzsx150's work in an easier way to download. You can contact him on the source link at the bottom of OP.
I only tested this twrp with stock rom which doesn't need gapps and encountered no issues.

mcf7 said:
I'm not the dev behind this project, i'm just sharing wzsx150's work in an easier way to download. You can contact him on the source link at the bottom of OP.
I only tested this twrp with stock rom which doesn't need gapps and encountered no issues.
Click to expand...
Click to collapse
same here but the custom roms that doesn't include gapps sucks, that's the problem with this twrp it cant flash gapps, thanks for the response bro.

[RECOVERY] [OFFICIAL] OrangeFox Recovery for OnePlus 5

OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Changelog:
- Initial Official build.
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
Treble & Non-Treble Support
No compatibility.zip error while flashing OxygenOS
A lot of customisations
Extremely beautiful UI ready to please your eyes.
Dev team is always ready to fix your problems
F2FS support
Screenshots
Screenshots at
https://imgur.com/a/Ai8KWX9
and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://orangefox.download/
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!

Hi !
I was kinda excited about this new recovery but official support for oneplus 5 is kinda... Dead, right ?

wund3rdelys said:
Hi !
I was kinda excited about this new recovery but official support for oneplus 5 is kinda... Dead, right ?
Click to expand...
Click to collapse
Yes

official dev did another update

SirRGB said:
official dev did another update an telegram
Click to expand...
Click to collapse
The link is broken

Phantom Thief said:
The link is broken
Click to expand...
Click to collapse
Telegram: Contact @orangefoxop5t
t.me

Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Poco F3/Mi 11X/Redmi K40
touch and adb work
flashing works
USB OTG works
Decryption is working
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
3. select the new image
4. after that is done, if you were using a custom kernel, reflash it now
5. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_alioth
https://github.com/TeamWin/android_device_xiaomi_sm8250-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocof3.html
Unofficial android 12 builds: https://www.pling.com/p/1836619/
mirror: https://store.kde.org/p/1836619/

Thanks for your hard work
All function has usable especially decryption.

Thank you mate!! That's is very important for all the community .What version of magisk i have to install??But you mean flash the zip of magisk??Thanks.

Awesome, mate!

I've been waiting for this, thank you sir for your contribution!

@Nebrassy Nice work - tested on my crDroid working-build and all ok

I only can say thank you a lot!! I'll buy a beer

"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw

reas0n said:
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
Click to expand...
Click to collapse
I believe that rom has customized encryption, so it's not supported

Nebrassy said:
I believe that rom has customized encryption, so it's not supported
Click to expand...
Click to collapse
Damn.. I will wait for any officially supported custom ROM then so I could just get OTAs, I dont want to do another wipe and setup lol. thx anyway

raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
your what?

raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
Not shared as yet?

arifqur said:
Not shared as yet?
Click to expand...
Click to collapse
Not yet. Won't take long though when first release will be posted in development.

this works "out of the box" for poco f3 with miui 12.x?

Thank you

Henkl said:
this works "out of the box" for poco f3 with miui 12.x?
Click to expand...
Click to collapse
answering my own question: you have to unlock the phone first with MIUI unlock tool.
AND unlocking involves wiating on part of xiaomi site afer registering ...can be even 7 days..

Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !

lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp

lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
The password is ur security PIN for unlocking ur phone.
No idea about backuping the boot.img in TWRP (I am not using it )

Nebrassy said:
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
Click to expand...
Click to collapse
I have entered a password but it failed. Is it a free password ?
EDIT : It's ok, sorry. the security PIN, of course !!!
EDIT 2 : And Thank you very much for your work and your help

Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 9/Pro
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
huge thanks to @osm0sis for help in making and testing this recovery
Trees:
https://github.com/TeamWin/android_device_oneplus_lemonadep
https://github.com/TeamWin/android_device_oneplus_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus9pro.html

Great, will test later on EU.

Thanks for your work, much appreciated

avid_droid said:
So I'm assuming flashing kernel and magisk is done through advanced and flash .img also?
Click to expand...
Click to collapse
No, the normal way

Thank you very much.... Finally

When in recovery, I plugged my phone in and my computer doesn't see it. My computer recognizes my phone, but it doesn't show up in my File Explorer. Also, can we flash system image files?

avid_droid said:
Sorry. Meant for magisk. I don't see a flash able zip for that. The kernel is obvious
Click to expand...
Click to collapse
The magisk apk itself is a flashable zip

Red Prez16 said:
When in recovery, I plugged my phone in and my computer doesn't see it. My computer recognizes my phone, but it doesn't show up in my File Explorer.
Click to expand...
Click to collapse
Did you enter your password to decrypt when recovery booted?, if you did, check mount > enable mtp

Nebrassy said:
Did you enter your password to decrypt when recovery booted?, if you did, check mount > enable mtp
Click to expand...
Click to collapse
Ah, okay. Thank you. Also, how do I flash a system image file? Let's say HavocOS for example.

avid_droid said:
Just got the zip from here
Click to expand...
Click to collapse
Do not download from unofficial sites, they could be malicious, only download from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com

Red Prez16 said:
Ah, okay. Thank you. Also, how do I flash a system image file? Let's say HavocOS for example.
Click to expand...
Click to collapse
Wait for them to release a zip

Nebrassy said:
Wait for them to release a zip
Click to expand...
Click to collapse
Ah, okay.

Red Prez16 said:
When in recovery, I plugged my phone in and my computer doesn't see it. My computer recognizes my phone, but it doesn't show up in my File Explorer. Also, can we flash system image files?
Click to expand...
Click to collapse
Pretty sure you need to mount storage for that in the mount menu

@Nebrassy I'm getting a multi-coloured white noise image when booting from fastboot (Step 1 in installation)
Currently I have LOS recovery due to installing current version of crDroid, should it be a different process for us? I was also on OOS 11.2.6.6 beforehand as 11.2.7.7 isn't out for EU (LE2123) yet.
i.e. fastboot flash boot TWRP-3.5.1-lemonadep-Nebrassy.img
(Kind of wary of doing so due to the white noise image but that's how LOS recovery was applied for crDroid instructions)
(Also was it you getting N7 BADA to search testers?)

djsubterrain said:
Pretty sure you need to mount storage for that in the mount menu
Click to expand...
Click to collapse
I did and nothing still.

djsubterrain said:
@Nebrassy I'm getting a multi-coloured white noise image when booting from fastboot (Step 1 in installation)
Currently I have LOS recovery due to installing current version of crDroid, should it be a different process for us? I was also on OOS 11.2.6.6 beforehand as 11.2.7.7 isn't out for EU (LE2123) yet.
i.e. fastboot flash boot TWRP-3.5.1-lemonadep-Nebrassy.img
(Kind of wary of doing so due to the white noise image but that's how LOS recovery was applied for crDroid instructions)
(Also was it you getting N7 BADA to search testers?)
Click to expand...
Click to collapse
The noise thing happens only on some devices, only Oneplus devices and I still have no idea what the cause could be, it seems to go away when twrp is flashed
And no, never flash twrp to boot that way, only fastboot boot and let twrp install itself with the options given
And yes, that was me

avid_droid said:
Well ill be damned... Magisk is a flashable apk. everything went through perfectly. Thank you. TWRP now installed with root and everything working so far. Appreciate you.
Click to expand...
Click to collapse
hi, are you on latest oos 11.77?

avid_droid said:
No I'm on BA 11.2.6.6
Click to expand...
Click to collapse
oh I see, gotta try later. thanks

There is no white noise in test build TWRP-3.5.1-lemonadep-1623916477.img
However, cannot pass through it in new build.

Nebrassy said:
The noise thing happens only on some devices, only Oneplus devices and I still have no idea what the cause could be, it seems to go away when twrp is flashed
And no, never flash twrp to boot that way, only fastboot boot and let twrp install itself with the options given
And yes, that was me
Click to expand...
Click to collapse
Would I be able to flash TWRP with LOS in that case?

Development [RECOVERY][3.7.0_12-8][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too.
As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
Download the twrp-installer zip
Flash it with Magisk manager or some other kernel flash utility
Reflash your custom kernel and Magisk.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
Don't reboot
Rename downloaded Magisk.apk to Magisk.zip
Open Magisk app
Select Modules tab
Click "Install from storage"
Select Magisk.zip
2. Option for users with other custom recoveries but without root:
Download the twrp-installer zip
Reboot to recovery
Flash it with "adb sideload twrp-installer*.zip"
Reboot to recovery
Reflash your custom kernel and Magisk.apk if previously installed
3. Option is universal:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Go to Advanced > Flash Current TWRP
Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps.
Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
Reboot to bootloader
Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.
TWRP Updates:
Download and flash the twrp-installer zip
After that reflash your custom kernel and Magisk if previously installed
ROM Updates:
Please follow the official update instructions for your ROM!
If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.
In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!
Instructions that work for me (on LOS based ROMs):
Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
Reboot to system
If Gapps packages keep crashing:
Reboot to TWRP
Flash Gapps again
Reboot to system
For OOS updates should work out of the box, but if you have issues you can follow these steps (I haven't tested them):
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
About backups/restore:
Restore data only WITHOUT pin/pattern set.
If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.
Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to system.
In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
How to use MTP, adb and fastbootD:
Windows:
Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.
To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.
Steps for choosing a specific driver (no the exact wording):
Connect phone in specific mode
Open device manager
Right click on phone either under "Android device" or "USB device", depending on mode
Select "update driver"
Select 2. option "browse my computer"
Select "pick from available drivers"
Pick driver according to above description
Linux:
Intall the fastboot and adb packages for your distribution
Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/nilz3000/android_hardware_oplus
Bugs:
Permanent installation alongside TMO stock isn't possible
Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
In case you notice anything else please let me know.
If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.
Thanks to:
@Nebrassy for the original device tree
@osm0sis for the zip installer
TWRP team
LineageOS

Thank you for this! Will try tomorrow.

Ah man this is dope. Thank you bud!!!

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.

Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...

vipinpvarghese said:
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
Click to expand...
Click to collapse
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.

der_akinator said:
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
Click to expand...
Click to collapse
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?

vipinpvarghese said:
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
Click to expand...
Click to collapse
Yes, but it was the same ROM I reinstalled after wipe.

der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse

der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
Sorry i forgot about recovery log

EugenStanis said:
Sorry i forgot about recovery log
Click to expand...
Click to collapse
recovery.log
Zippyshare.com - Free File Hosting
www1.zippyshare.com

Anyone tested it with stock OOS13?

der_akinator said:
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
Run "fastboot boot boot.img" with the TWRP boot image.
Go to Advanced > Flash Current TWRP.
After that is done, if you were using a custom kernel, reflash it now.
If you were using magisk, reflash it now.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/LineageOS/android_hardware_oplus
Bugs:
Please let me know. I have not encountered anything major yet.
Thanks to:
Nebrassy
TWRP team
LineageOS
Click to expand...
Click to collapse

For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.

Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Here is a link to the github issue, maybe it helps you solving the problem.
createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project
Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...
github.com

tnchng said:
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Click to expand...
Click to collapse
I use C.63 and have not tested with other firmware versions.

der_akinator said:
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Click to expand...
Click to collapse
Strange, i have never ever in my life used multiuser