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

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

Search This thread

Peterpaulmarie

Senior Member
Aug 21, 2011
405
134
Munich
Hi, I have a little problem.. I have installed twrp and I want to flash last EU weekly but I search where is located the zip but there is nothing in storage, or elsewhere.. I can't see internal storage.. What I are missing??
Thanks
Download to download folder should also work. Search in TWRP for sdcard/download
Did you switched off PIN unlook? Use pattern security
 
Last edited:

rayman95

Senior Member
Jan 14, 2009
6,331
3,836
63
monaco
Google Nexus 4
Samsung Galaxy Note 3
I installed via USB-OTG. But download to download folder should also work. Search in TWRP for sdcard/download
Did you switched off PIN unlook? Use pattern security
all my folders are empty so can't find the weekly zip...
the pin said wrong password, don't set passwoed for recovery..
....and I tried to install with adb sideload without success...cannot read xiaomi.zip
 

Peterpaulmarie

Senior Member
Aug 21, 2011
405
134
Munich
Hmm, can't realy help here. Everything works well for me. Can see all my folders.
Pls check: Do not use pin or fingerprint.
Use only pattern. After start of TWRP it ask for pattern and after decrypted folder...
Update: yes, confirm. External memory and USB-OTG empty
 
Last edited:
  • Like
Reactions: Vag-Zag

Rainman67

Member
Jan 21, 2013
36
17
The founder said: "Backup & Restore not working". Plus, SD & OTG doesn't recognized.
Thats not hundred percent true! He said:
"backup/restore is unreliable"
That's not the same and this was the reason for my question: did somebody try it (with or without success)?

And until sdcard is working you can make the backup to the internal storage, copy it to an external medium and in case you need the backup to restore, you can copy it back to the device.
 
  • Like
Reactions: tom65824

maxipaxi13

Member
Aug 12, 2015
7
0
Hi
I tried do install the twrp over fastboot with command: fastboot flash recovery twrp-3.5.2-renoir.img. This recovery is in adb folder, like I did before with many devices. But it is not working on this way. I comming from original Miui eea Rom. It says: sending recovery ok, writing recovery FAILED (remote: (recovery_a) No such partition) finished.
What are I am doing wrong? Do I have to copy to internal memory of the phone and then start with the command fastboot boot twrp.img?
Thanks for Help in advanced.

Now I tried this way and it worked. Dident know, that is possible.
 
Last edited:

daddiemus

New member
Jun 8, 2014
3
0
Hi
I tried do install the twrp over fastboot with command: fastboot flash recovery twrp-3.5.2-renoir.img. This recovery is in adb folder, like I did before with many devices. But it is not working on this way. I comming from original Miui eea Rom. It says: sending recovery ok, writing recovery FAILED (remote: (recovery_a) No such partition) finished.
What are I am doing wrong? Do I have to copy to internal memory of the phone and then start with the command fastboot boot twrp.img?
Thanks for Help in advanced.

Now I tried this way and it worked. Dident know, that is possible.
Hai,i have the same problem! How do you fix? Thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Official builds have started

    4
    Then i tried the TWRP-Backup again and all was working fine!
    ....and for those, who are worry about restoring a TWRP-Backup: I tried this too, and restoring of the TWRP-Backup worked fine too! (y)
    3
    I confirm that a bakcup works by copying it to the PC via the internal memory.

    But I still don't understand why you can't mount an SD card via TWRP. The most frustrating thing is that there is no communication about the lack of support for SD cards and other USB sticks, so this bug is still not fixed.

    Is it due to the new snapdragon 780G processor still not well mastered?

    A lack of time for volunteer developers, despite the fact that it is now more than 4 months?

    In short, staying in the dark for lack of communication is more than frustrating...

    Translated with DeepL
    3
    I confirm that a bakcup works by copying it to the PC via the internal memory.

    But I still don't understand why you can't mount an SD card via TWRP. The most frustrating thing is that there is no communication about the lack of support for SD cards and other USB sticks, so this bug is still not fixed.

    Is it due to the new snapdragon 780G processor still not well mastered?

    A lack of time for volunteer developers, despite the fact that it is now more than 4 months?

    In short, staying in the dark for lack of communication is more than frustrating...

    Translated with DeepL
    Lack of time, lack of testers, many other more important stuff to work on, and I don't have the device

    Otg does not work on any GKI devices in twrp, though I wasn't aware that sdcard had issues, join my tg group and tag me if you can test
    2
    Now that TWRP is official, I've sucessfully booted and flashed Nebrassy's TWRP 3.6.0, following the instructions on the 1st post here. But unfortunately, there is no way to retain TWRP if I root using Magisk. It reverts to stock Xiaomi recovery.
    I have started with a rooted xiaomi.eu_multi_MI11Lite5G_V12.5.8.0.RKICNXM_v12-11-fastboot rom (stable branch) on the phone, then installed TWRP, and lost root. Repeated the process to root with Magisk 23 again, only to lose TWRP, and upon repetition of booting to and flashing TWRP (using flash current TWRP in advanced menu on the phone) again, loosing root.
    I then repeated the rooting process from scratch, re-sending the boot.img from the rom files to the phone, using Magisk to patch it, copying the fresh patched boot.img to the computer and using fastboot... and TWRP was gone again.

    This did not happen with the previous 3.5.x version, from the same Nebrassy. So now I'm forced to choose between having TWRP or having Root with Magisk, since it seems they can't co-exist. Has anybody faced this problem? Is there a solution?

    Aditionally, on the download page (https://dl.twrp.me/renoir/) there is a twrp-installer-3.6.0_11-0-renoir.zip whose functionality I can not find any information about, or any instructions on how to use it, anywhere. Would this be the file to use in order to retain root and twrp alltogether? If that is so, please, can anybody explain how to use it?
  • 14



    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 Mi 11 lite 5G

    bugs:
    backup/restore is unreliable
    adb sideload and fastbootd

    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

    Contributors:
    @VladV1V , @TheMalachite

    Tree:

    Kernel:
    https://github.com/VladV1V/kernel_xiaomi_renoir

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

    Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
    7
    Official builds have started

    5
    @Nebrassy
    Thank you for bringing TWRP to this excellent device.
    Unfortunately this is the buggiest TWRP I have ever used and it also has a lot of limitations.
    Is there any active development to fix all the issues?
    4
    Then i tried the TWRP-Backup again and all was working fine!
    ....and for those, who are worry about restoring a TWRP-Backup: I tried this too, and restoring of the TWRP-Backup worked fine too! (y)
    3
    I confirm that a bakcup works by copying it to the PC via the internal memory.

    But I still don't understand why you can't mount an SD card via TWRP. The most frustrating thing is that there is no communication about the lack of support for SD cards and other USB sticks, so this bug is still not fixed.

    Is it due to the new snapdragon 780G processor still not well mastered?

    A lack of time for volunteer developers, despite the fact that it is now more than 4 months?

    In short, staying in the dark for lack of communication is more than frustrating...

    Translated with DeepL