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

Search This thread

Nebrassy

Senior Member
Sep 17, 2015
946
1,658
Lattakia
Xiaomi Poco X3 Pro
@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?)
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
 

neobuddy89

Recognized Developer / Recognized Contributor
Mar 13, 2011
5,350
23,672
Mumbai
There is no white noise in test build TWRP-3.5.1-lemonadep-1623916477.img
However, cannot pass through it in new build.
 

djsubterrain

Senior Member
Jan 4, 2012
3,997
3,720
Livingston
OnePlus 9 Pro
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

Would I be able to flash TWRP with LOS in that case?
 

Nebrassy

Senior Member
Sep 17, 2015
946
1,658
Lattakia
Xiaomi Poco X3 Pro

neobuddy89

Recognized Developer / Recognized Contributor
Mar 13, 2011
5,350
23,672
Mumbai
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
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

  • IMG_20210620_190737.jpg
    IMG_20210620_190737.jpg
    4.4 MB · Views: 130
  • Like
Reactions: djsubterrain

Nebrassy

Senior Member
Sep 17, 2015
946
1,658
Lattakia
Xiaomi Poco X3 Pro
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.
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
 

djsubterrain

Senior Member
Jan 4, 2012
3,997
3,720
Livingston
OnePlus 9 Pro
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.

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
 

djsubterrain

Senior Member
Jan 4, 2012
3,997
3,720
Livingston
OnePlus 9 Pro
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

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)
 
  • Like
Reactions: Smedslund

Nebrassy

Senior Member
Sep 17, 2015
946
1,658
Lattakia
Xiaomi Poco X3 Pro
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
 

Top Liked Posts

  • 1
    new build is up

    fixed decryption on newer roms
    further fixes for flashing
    data can be formatted directly after flashing a rom
    added an option to auto flash TWRP after flashing a rom
    fixed the problem where you needed to refresh sizes before being able to flash TWRP
    thanks for your great work @Nebrassy, with the command fastboot boot *.img my password is recognised correctly, in the menu extended "flash current TWRP" also works, only the status bar cannot be operated.
  • 13
    new build is up

    fixed decryption on newer roms
    further fixes for flashing
    data can be formatted directly after flashing a rom
    added an option to auto flash TWRP after flashing a rom
    fixed the problem where you needed to refresh sizes before being able to flash TWRP
    4
    in the case where Flash Current TWRP fails, which is only happening for some people and not others, try going to the backup menu, refresh sizes and then try Flash Current TWRP again, let me know if that works for people who couldn't flash before so I add that to the OP
    3
    I'll look into this when I have some time, if you're on that update and can test join my tg group
    2
    2
    Before I went that route I was hoping to extract the recovery image from the Payload.bin for the latest OOS ROM, but I can't find a recovery.img in the extract. boot.img is there, but not recovery. Anyone have an OnePlus 11Pro OOS recovery.img file? Am I just looking for the wrong filename?

    I figure I can flash OOS recovery from fastboot and then flash the full OOS image from OOS recovery.
    Recovery is in boot
  • 46



    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/nebrassy/device_oneplus_lemonadep-TWRP
    https://github.com/nebrassy/device_oneplus_sm8350-common-TWRP

    Telegram group: https://t.me/NSSFB

    Download: https://www.androidfilehost.com/?w=files&flid=326293
    13
    new build is up

    fixed decryption on newer roms
    further fixes for flashing
    data can be formatted directly after flashing a rom
    added an option to auto flash TWRP after flashing a rom
    fixed the problem where you needed to refresh sizes before being able to flash TWRP
    10
    While 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://forum.xda-developers.com/t/...-unified-stable.4101313/page-57#post-84204575

    For more instructions see my original OP7T Series zip post: https://forum.xda-developers.com/t/...-adb-in-recovery.4002843/page-3#post-82376013
    4
    released new build which solves the display issue on custom roms
    4
    in the case where Flash Current TWRP fails, which is only happening for some people and not others, try going to the backup menu, refresh sizes and then try Flash Current TWRP again, let me know if that works for people who couldn't flash before so I add that to the OP