What do you mean?
No, only flash twrp by fastboot booting twrp then advanced > Flash current twrp or install recovery ramdisk
Or same procedure if twrp is already flashed
Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
- Thread starter Nebrassy
- Start date
Or same procedure if twrp is already flashed
TWRP backups are unreliable currently, do not rely on them as your only backup
See attached pic. On flashing this recovery I get white noise like this.
However, this noise was not present on test build earlier. Test build still doesn't give this kind of noise.
Attachments
After seeing that screen, I will wait a few days before flashing and see if more have the same issue
Hm, pm me on tg I'll send a test build later
This might be due to the kernel I'm using, has anyone tested this build on a custom rom and it worked?, please let me know if it worked for you
Same as I'm getting.
Can you confirm more info :
Current rom :
Last flashed OOS version :
Current recovery :
Phone version with memory/storage :
Mine :
Current rom : crDroid 15th June Build
Last flashed OOS version : 11.2.6.6 (No 11.2.7.7 available for EU yet)
Current recovery : LOS 15th June Build
Phone version with memory/storage : LE2123 8/128GB
I, also, was not getting that on the earlier test builds but couldn't apply TWRP from the "Flash current version" option which I think you suspected was due to crDroid.
Are you using blu_spark then? (Not sure I can use it with crDroid as the kernel is meant to be used with OOS)
Yes I'm using blu_spark in hopes of eliminating the need for kernel module hacks, I'll send you a build in a bit
Also getting the white noise screen.
TMO OP9P, I have latest lineage installed with the 0608 recovery installed since 0615 recovery won't boot for me.
Firmware is only up to 11.2.6.6 due to EU not hitting .7.7 yet
TMO OP9P, I have latest lineage installed with the 0608 recovery installed since 0615 recovery won't boot for me.
Firmware is only up to 11.2.6.6 due to EU not hitting .7.7 yet
Yes I just tried booting twrp so I cld direct install from it... I am getting the same white noise screen.. On crdoid as well..
So if I flash a ROM and want to go back to OOS does the zip file you download through OTA updater work as a flash able zip to return to stock?
Not unless it's the full zip. There's a pinned collection of full zips here anyway
Just tested on new version of crDroid released today, same multi-coloured snow shown on booting via fastboot.
Their update post stated the kernel is new and built on LOS so I'm guessing we'd see similar behaviour on LineageOS
Their update post stated the kernel is new and built on LOS so I'm guessing we'd see similar behaviour on LineageOS
Last edited:
released new build which solves the display issue on custom roms
Boots correctly now without the snow image but still unable to apply using advanced>Flash Current TWRP
Attached logs
Just installed on my OnePlus 9 (non-pro). Everything worked as it should and I was able to re-install the kernel and Magisk without issue. The only minor thing I noticed is that it sits on the TeamWin Recovery loading/splash screen for a long time (probably a similar amount of time to how long a normal boot takes).
I'm using the pro and it shows the teamwin screen for like 3 seconds then asks for a pass here
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
66
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.html17Official builds have started
10While TWRP development's ongoing here, I figured I'd also upload an OP9x Series version of my stock recovery adb insecure patching AK3 zip, which can be handy if, for example, after an OTA TWRP doesn't work anymore due to some change in OOS. So if something then goes wrong at least we've got decrypted data and adb shell dmesg access for our various devices via stock recovery. Attached below. Simply flash via FKM or EXKM once you're already rooted, before you flash TWRP, and then you may dump that patched stock recovery boot.img for later use.
Supporting OnePlus9/lemonade, OnePlus9TMO/lemonadet, OnePlus9VZW/lemonadev, OnePlus9Pro/lemonadep and OnePlus9ProTMO/lemonadept.
For OnePlus9R/lemonades see my OP8x+9R Series zip (since 9R is closer to 8T than 9): https://xdaforums.com/t/twrp-3-4-0-...-unified-stable.4101313/page-57#post-84204575
For more instructions see my original OP7T Series zip post: https://xdaforums.com/t/magisk-twrp...-adb-in-recovery.4002843/page-3#post-823760139
I **might** be interested in helping out. I want to get TWRP running on A12 on my OnePlus 9 Pro, too. I am a software engineer, so I'm familiar with dealing with code, git, and whatnot. But I've never done anything with Android, so I would need some pointers in what exactly is involved with maintaining a device tree. What is the purpose of the code in the device tree? I'm assuming it has to do with configuring TWRP for a specific device? What is the process for figuring out what the configuration is? How do I get started?Hmm, or not: https://jenkins.twrp.me/view/TWRP Release Android-12.1/
We need a new maintainer to bring-up the device tree to android-12.1, since @Nebrassy has confirmed he is stepping down.
