General [SHARED] [UNOFFICIAL][A12/A13] TWRP 3.7.0 for Redmi Note 11 (spes/spesn)

Search This thread
By:
Advanced…
Sheist!

Sheist!

Senior Member
Oct 7, 2009
556
139
Redmi Note 10 Pro
Redmi Note 11
SubwayChamp said:
Sorry for delay, I can only respond once at day. ADB sideload only works with zips, not with images, anyway, it fails, you always can use fastboot for flashing the recovery that actually works fine. If you are doubting how to get that recovery you actually have, take a backup from it, then transfer to the PC (for example), then change the extension to img, to the file, then you can use it through fastboot at any time.
Click to expand...
Click to collapse
I think you are confused. The spes has no recovery partition; custom recoveries cannot be flashed in fastboot. Certain ROM's have incorporated them, like crDroid, but the steps to change to TWRP on spes do not work. You can boot to TWRP, but the 3 methods within TWRP to make it permanent all fail me... I get booted back to fastboot instead of recovery or system.
 
SubwayChamp

SubwayChamp

Senior Member
Aug 6, 2016
4,944
5
1,820
Sheist! said:
I think you are confused. The spes has no recovery partition; custom recoveries cannot be flashed in fastboot. Certain ROM's have incorporated them, like crDroid, but the steps to change to TWRP on spes do not work. You can boot to TWRP, but the 3 methods within TWRP to make it permanent all fail me... I get booted back to fastboot instead of recovery or system.
Click to expand...
Click to collapse
Sorry, I know, it was a typo, I meant to boot to it using fastboot.

I also had Spes, months ago, and I never had the kind of issues you are facing. Although that said, there is some specific builds that don´t allow TWRP to be flashed, why? because they integrate the recovery into the ramdisk partition, if you replace that recovery (maybe CrDroid), device won´t boot.

Also you can try by booting to fastbootd, using adb reboot fastboot, or from fastboot (bootloader mode) with fastboot boot fastboot, in the userspace is possible to target directly to the ramdisk, not sure if it works with spes, using fastboot flash recovery_ramdisk twrp.img
 
Sheist!

Sheist!

Senior Member
Oct 7, 2009
556
139
Redmi Note 10 Pro
Redmi Note 11
SubwayChamp said:
Sorry, I know, it was a typo, I meant to boot to it using fastboot.

I also had Spes, months ago, and I never had the kind of issues you are facing. Although that said, there is some specific builds that don´t allow TWRP to be flashed, why? because they integrate the recovery into the ramdisk partition, if you replace that recovery (maybe CrDroid), device won´t boot.

Also you can try by booting to fastbootd, using adb reboot fastboot, or from fastboot (bootloader mode) with fastboot boot fastboot, in the userspace is possible to target directly to the ramdisk, not sure if it works with spes, using fastboot flash recovery_ramdisk twrp.img
Click to expand...
Click to collapse

Has anyone successfully installed TWRP via "fastboot flash recovery_ramdisk [TWRP name].img" with crDroid 9.3 from April 2023? Now, I have the boot, dtbo and vbmeta images ready to go, but if crDroid (which incorporates its own recovery) borks, I do not want to risk losing my data. (It fails trying to insert TWRP permanently from a booted TWRP recovery for me.)

I just messaged the OP/developer, jabieff.

EDIT: in crDroid 9.3, the TWRP 3.7.0_12-0.img successfully installed via "install recovery ramdisk." Stress relieved! (y)
 
Last edited:
  • Like
Reactions: mierdaseca
arkhoirys

arkhoirys

Member
Sep 25, 2022
9
4
Every time i try to make a backup i get the error ''create tar fork() process ended with error=255'', everything else is working supposedly just fine, can u help me with this?
 
s265925

s265925

Member
Aug 27, 2023
9
0
With MIUI 14 I can't boot with
fastboot boot twrp-3.7.0.img

It reboots back into system itself (MIUI) everytime
 
Sheist!

Sheist!

Senior Member
Oct 7, 2009
556
139
Redmi Note 10 Pro
Redmi Note 11
Let me see what I get.

EDIT: works fine.

...adb\platform-tools>fastboot boot twrp-3.7.0.img
Sending 'boot.img' (98304 KB) OKAY [ 2.272s]
Booting OKAY [ 0.288s]
Finished. Total time: 2.629s

Should boot easily on the spes regardless of the ROM.
 
Last edited:
You must log in or register to reply here.

Similar threads

jabieff
  • Locked
Development [CLOSED] [ROM][DISCONTINUED][12.1-13.0] crDroidAndroid 8.x - 9.x [SPES|SPESN]
Replies
279
Views
63K
Sheist!
Sheist!
chrisw444
Development [ROM][13][REDMI NOTE 11/11 NFC - SPES/SPESN] PixelExperience [AOSP]
Replies
221
Views
44K
B
blackthorn1337
hecaex
Development [ROM][DISCONTINUED][13] LineageOS 20.0 for Redmi Note 11 [SPES|SPESN]
Replies
72
Views
25K
H
helloyello
etylix
Development [ROM][13.0_r74]Evolution X for the Redmi Note 11/NFC
Replies
96
Views
35K
rizqi putra firmansyah
rizqi putra firmansyah
etylix
Development [ROM][DISCONTINUED][12.1] Evolution X for Redmi Note 11 [spes/spesn]
Replies
76
Views
23K
P
pumpi851

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    NeoSDAP
    NeoSDAP
    Well, I found this in a Telegram group (which I know I can't share the link) and when performing all possible tests, it works perfectly with my 4/128 spes.

    And as we would all say, I am not responsible for any damage and loss of data caused to your device. I only share the information "as is" and the tests performed by myself on my personal device. Everything is at your own risk.

    So, let's start with the post:

    New Developer on this version:
    @jabieff

    Previous Developer
    @dblenk9 - Telegram


    2022/11/06 Update Changelog:
    • Synced latest TWRP 12.1 source
    • Fixed Android 13 ROM flashing issue (source side)

    Changelog in the previous version by @dblenk9
    • Sync with latest TWRP
    • Update kernel to MIUI V13.0.4.0.SGCMIXM
    • Update blobs to MIUI V13.0.4.0.SGCMIXM
    • MTP fixed
    • Decrypt works

    Features I tried and didn't have any problems
    • Flashing and decrypt data from A13 ROMs
    • Flashing and decrypt data from A12.1(A12L) ROMs
    • Flashing and decrypt data from MIUI-based ROMs (custom and Stock) with A12
    • Flashing Magisk
    • MTP fully functional
    • ADB sideload
    • Install recovery ramdisk and "Flash current TWRP" from Advanced menu

      DO NOT USE WITH ANDROID 11 ROMS!!!

    Bugs I've found so far
    • If you perform a format data, the internal memory will not be recognized in MTP mode of TWRP, which will not be displayed in Windows file explorer
      SOLUTION:       Boot into the OS at least once so that the internal memory is rebuilt and made available again in MTP mode

    • Sometimes, when checking the option "Automatically reflash TWRP after installing the ROM", it does nothing when it finishes installing the ROM
      SOLUTION:       The option seems to be somewhat bugged, so before restarting always reinstall TWRP with the methods that I will explain below

    • When flashing some ROMs, "Failed to mount *partition*" errors come out when you finish installing
      SOLUTION:       In some ROMs you may get errors when mounting some partitions, commonly "system_ext", "product" and "vendor".

      If the installation process ended without any problem and without showing any error code, that's fine, you can restart without problems, This bug has been in all unofficial TWRP for this device

    Steps to install

    Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
    Tutorial for Windows only because zero knowledge for Mac and Linux

    From PC:
    1. Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder

    2. Download the TWRP image file from here, or from the post attachments
      SHA256: 8F25AC88628E6D7BC5E29D8572CF4ACA3499B7D626685654B3C4548323B8D591

    3. Restart your device to fastboot mode
      Method 1:
      Using this adb command if you have USB debugging active on your device
      Code: 
      adb reboot bootloader

      Method 2:
      -       Turn off your device
      - After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out

      Method 3:
      - Turn off yout device
      - Press and hold Vol - button
      - Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out

    4. Connect your device to the PC

    5. Open a cmd window in the folder where you extracted the binaries from the zip from step 1
      Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location

    6. Verify that your device is recognized by fastboot using this command
      Code: 
      fastboot devices
      If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.

      - Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.

    7. Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end
      Code: 
      fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:

fastboot boot

    8. Now, drag the image file (twrp-3.7.0.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.

      - The result should be this:

    9. Code: 
      fastboot boot "C:\location\to\your\file\twrp-3.7.0.img"

Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.

    10. Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.

      DONE! You've started perfectly in TWRP

    From the device
    NOTE: Only use these steps if you want to have TWRP installed semi-permanently
    I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.

    If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.

    Method 1
    1. While in the TWRP menu, tap the Advanced button

    2. Now tap on the option "Flash current TWRP"

    3. "Swipe to confirm" and the TWRP installation process will begin
    Method 2
    1. While in the TWRP menu, tap the Advanced button

    2. Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
      You can use a USB OTG too

    3. Now tap on the option "Install recovery ramdisk"

    4. Now locate the file and tap on it.
      You can use the "Select storage" button to switch between different storages

    5. "Swipe to confirm" and the TWRP installation process will begin
    Method 3
    1. While in the TWRP menu, tap the Install button

    2. Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
      You can use a USB OTG too

    3. Tap on the option "Install image"

    4. Now locate the file and tap on it.
      You can use the "Select storage" button to switch between different storage

    5. In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
    Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP if you already had it previously installed.


    Conclusion
    I did everything I could but I couldn't find the source code for this TWRP, so I'm sorry for that.
    View
    2
    NeoSDAP
    NeoSDAP
    05/05/2023
    POST
    - Link to GDrive fixed

    11/11/2022
    POST:
    - Reverted to previous version as @jabieff TWRP is unable to flash MIUI ROMs due to dynamic partitioning error.

    07/11/2022
    POST
    - Added info about Android 11
    - Updated to latest TWRP and new developer

    19-10-2022
    POST:
    - Fixed typo and A11 ROMs info added
    View
    2
    NeoSDAP
    NeoSDAP
    essor-13 said:
    Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
    It returns :
    Code: 
    Failed to decrypt user 0
    Is there a way to solve yhis issue ?

    Rom version : MUI global 13013 Stable RGKEUXM
    Android version: 11 RKQ1.211001.001

    Thanks !
    Click to expand...
    Click to collapse
    This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
    View
    1
    J
    jtrakx
    essor-13 said:
    Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
    It returns :
    Code: 
    Failed to decrypt user 0
    Is there a way to solve yhis issue ?

    Rom version : MUI global 13013 Stable RGKEUXM
    Android version: 11 RKQ1.211001.001

    Thanks !
    Click to expand...
    Click to collapse
    I think this version of TWRP works only with MIUI13 A12. You're on A11 version of MIUI13.
    View
    1
    NeoSDAP
    NeoSDAP
    essor-13 said:
    Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.

    I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).

    I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.

    Thanks !
    Click to expand...
    Click to collapse
    Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.

    If you want to keep everything in order:
    - Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
    - If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
    View

New posts