• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

CZ Eddie

Senior Member
Sep 27, 2011
6,193
2,332
Austin, TX
Hmm, the install didn't work for me.
Code:
fastboot boot TWRP-3.5.1-lemonadep-Nebrassy-2.img

When I booted to the temporary img above and then did the "Advanced > Flash Current TWRP" it said "error opening file".

Then, I tried the "Advanced > Install Recovery Ramdisk" but it doesn't see any files.

Then, I noticed TWRP doesn't see any files anywhere in my filesystem, of any type.
What am I doing wrong?
 

Nebrassy

Recognized Developer
Sep 17, 2015
1,012
2,079
Lattakia
Xiaomi Poco X3 Pro
Hmm, the install didn't work for me.
Code:
fastboot boot TWRP-3.5.1-lemonadep-Nebrassy-2.img

When I booted to the temporary img above and then did the "Advanced > Flash Current TWRP" it said "error opening file".

Then, I tried the "Advanced > Install Recovery Ramdisk" but it doesn't see any files.

Then, I noticed TWRP doesn't see any files anywhere in my filesystem, of any type.
What am I doing wrong?
Use the latest one
 

Superguy

Senior Member
Nov 28, 2007
850
159
Baltimore
Does fastboot get weird for anyone with TWRP installed? Instead of the normal fastboot, I get one that kinda looks like TWRP and then won't run any boot images pushed to it.
 
Does fastboot get weird for anyone with TWRP installed? Instead of the normal fastboot, I get one that kinda looks like TWRP and then won't run any boot images pushed to it.
I had a similar issue before, but with no touch. You can't enter any "fastboot boot" or "reboot fastboot" commands from twrp or it'll load that weird environment. You have to either enter the bootloader from power off with the hardware keys, or run "reboot bootloader" from system.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    hello, tried to boot twrp from adb, but when booted, the touchscreen dosn't work and i can't press on any button. any solution?
    1
    I made a mistake I think while installing this. So my phone was rooted and I installed a custom kernel. I followed the installation instructions and my phone booted just fine. I then wanted root back so I did "fastboot flash boot <magisk.patched.img>". I didn't do 'fastboot boot' because I was under the assumption that this would work fine, however it doesn't. My phone now just keeps booting, it shows the oneplus logo with those spinning white dots around it. I'm on oxygenos 11.

    I've tried to reflash TWRP which gives the same result and when I try to flash my stock boot.img, it won't boot at all. Any clues what went wrong and how I could resolve this? My guess is that I need a boot.img which is modified for TWRP and I don't have that one on my computer?

    Thanks in advance, and merry christmas ;)
    which custom kernel did you flash. I'm guessing it was arter which means you need to flash dtbo.img, vendor boot.img, and stock boot.img for phone to boot. If you don't have these imgs, just flash your rom again.
    1
    @Nebrassy can you help with decrypt android 12, trying everything, but nothing help.
    Attach log from recovery. Thanks
    1
    Anyone else unable to move a file to twrp using adb push/pull? I have also tried using the sideload mode, but it doesn't work, adb just says no devices/emulators found.
    When adb says no devices or unauthorized, ckeck your adb key in a hidden /.adb folder in your User folder. Sometimes the authentication gets revoked and device is not recognised in adb.
    If that's your issue:
    Delete adb.key from <YourUsername>/.adb folder.
    Turn off Usb Debugging.
    Disconnect your phone
    Turn On Usb Debugging
    Connect your phone.
    You should now get a dialog asking for authorization again.
    You probably will have to do this again after disconnecting your phone for a long while.
    Also:
    TWRP has bug with mtp not functioning. The given solution was to disable/enable usb Debugging and enable/disable "mtp enabled" in Mount menu. That did not work for me.
    What i think worked was this:
    I plugged my phone in booted system ( or you can try fastboot) then after device is recognised by windows, go to
    device manager > your phone's driver update menu > choose driver and install the standard windows mtp driver. Reboot to recovery and see if it connects.
    I think that's worked for me when i tried installing this rom and found myself stuck with no way to sideload it. Spend all night on it before succeeding and tried lots of things so not sure it this works 100%. Hppe it helps.
    1
    When adb says no devices or unauthorized, ckeck your adb key in a hidden /.adb folder in your User folder. Sometimes the authentication gets revoked and device is not recognised in adb.
    If that's your issue:
    Delete adb.key from <YourUsername>/.adb folder.
    Turn off Usb Debugging.
    Disconnect your phone
    Turn On Usb Debugging
    Connect your phone.
    You should now get a dialog asking for authorization again.
    You probably will have to do this again after disconnecting your phone for a long while.
    Also:
    TWRP has bug with mtp not functioning. The given solution was to disable/enable usb Debugging and enable/disable "mtp enabled" in Mount menu. That did not work for me.
    What i think worked was this:
    I plugged my phone in booted system ( or you can try fastboot) then after device is recognised by windows, go to
    device manager > your phone's driver update menu > choose driver and install the standard windows mtp driver. Reboot to recovery and see if it connects.
    I think that's worked for me when i tried installing this rom and found myself stuck with no way to sideload it. Spend all night on it before succeeding and tried lots of things so not sure it this works 100%. Hppe it helps.
    Pretty sure I've found the issue,

    The rom I was using overwrote my twrp with an older version that did not function correctly, so I should be able to update it to make it work again (tested on fresh newest twrp, it worked in the latestver)
  • 58



    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
    19
    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
    17
    Official builds have started

    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
    6
    So far i have read onlyvup to page 8. But i noticed a lot of people having problems with fastboot (me included). I think fastboot flashes to inactive slot without saying so.
    With slot a active, doing fastboot flash boot <filename>.img works fine (it goes to slot b) but rebooting anything (system, recovery, bootloader) ends up rebooting to fastboot mode in slot a (because of corrupted partitions).
    I am now in twrp on slot b but can't sideload files to install ramdisk. Pc is not detecting device even with mtp enabled. Stuck at this point...
    Edit: I was able to load the system on slot b. Transferred twrp img and installed ramdisk. Rooted and rebooted to system. On slot b.
    Should i start again everything from the top to slot a (reboot slot a, fastboot twrp, install rom reroot)
    the instructions say fastboot boot twrp.img, NOT fastboot flash