[RECOVERY][STABLE]Unoffical TWRP for Xiaomi Mi A3[laurel_sprout]

Search This thread

rootadvisor

Member
May 15, 2019
31
7
Hello, I had the V12.0.8.RFQMIXM and i follow the method as the op said
Now the phone does not boot with twrp-3.5.2_9-0-laurel_sprout.img the
Need help what should I do ?


fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.006s

fastboot set_active b
Setting current slot to 'b' OKAY [ 0.045s]
Finished. Total time: 0.056s

fastboot erase boot
Erasing 'boot_b' OKAY [ 0.011s]
Finished. Total time: 0.021s

fastboot flash boot twrp-3.5.2_9-0-laurel_sprout.img
Sending 'boot_b' (65536 KB) OKAY [ 1.472s]
Writing 'boot_b' OKAY [ 0.315s]
Finished. Total time: 1.826s

fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s

No answer.
 
Last edited:

KaTze87

New member
Apr 16, 2020
3
0
Hello. Do you know if they are study so that the TWRP can be permanently installed in MI A3 with android 11? Thank you for your work.
 
Feb 20, 2017
4
0
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.

Code:
#include <std_disclaimer.h>
/*
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.

HOW TO UPDATE a ROM and Keep TWRP and ROOT:
Before all Disable all magisk modules for boths methods

- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk(recommend to use Magisk v19.4);
- Reboot.

Download:
TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
TWRP 3.3.1-2 Unofficial by Nikesh Kataria

Donations:



Credits:

Thanks to @mauronofrio for a great help to make a stable recovery
Thanks to @Typhus_ for hardcore testing
Thanks to @prakash78 for testing

Contributors
Nik001
Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp

Version Information
Status:
Stable

Created 2019-10-21
Bro is it working on stock android 11?
 

Chends888

New member
Apr 8, 2014
2
0
Oh, and I forgot... if you're still on Android 10 the TWRP I recommend, where everything works as it should, is the one built by @mauronofrio.

You can get it HERE.

This TWRP can be booted on inactive slot while on Android 11 as well, it just can't be permanently installed...don't know why...


Cheers!
This was the only TWRP I was able to install (twrp-3.3.1-17-laurel_sprout-Q-mauronofrio.img), I tried all from TWRP official website (https://dl.twrp.me/laurel_sprout/) and none worked, when I flash them and tried to reboot, using fastboot reboot (holding volume up), or fastboot reboot recovery, it just went straight to fastboot again.

Thanks!
 

Zergrinch

Member
Sep 17, 2016
21
1
I tried temp booting into TWRP but it failed. Any ideas? I'm not sure why boot is considered an unknown command.

C:\Android\Mi A3>fastboot boot twrp-3.6.2_9-0-laurel_sprout.img
Sending 'boot.img' (41456 KB) OKAY [ 1.084s]
Booting FAILED (remote: 'unknown command')
 

garylawwd

Forum Moderator
Staff member
I tried temp booting into TWRP but it failed. Any ideas? I'm not sure why boot is considered an unknown command.

C:\Android\Mi A3>fastboot boot twrp-3.6.2_9-0-laurel_sprout.img
Sending 'boot.img' (41456 KB) OKAY [ 1.084s]
Booting FAILED (remote: 'unknown command')
Because it is an unknown command. You have to install TWRP to the boot partition not boot the twrp.img

Code:
fastboot flash boot twrp.img

Only then can you boot into twrp by rebooting and holding vol up
 

Zergrinch

Member
Sep 17, 2016
21
1
Fastboot flash boot xxx.img has the potential to brick the phone in my experience. Besides, Fastboot boot xxx.img is the recommended procedure on the TWRP.me website: https://twrp.me/xiaomi/xiaomimia3.html

I have temp booted into other versions of TWRP on other phones before (Poco X3, Xiaomi Mi A1, Xiaomi Redmi S2) and see no reason for this to fail on an Android One phone.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 45
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.

    Code:
    #include <std_disclaimer.h>
    /*
     *
     * We are not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at us for messing up your device, we will laugh at you.
     *
     */

    Whats Working?
    Everything is working
    Can change Slot A/Slot B on twrp
    SDcard and OTG working
    Decryption of Data working
    Flashing of roms work pie and even Q roms work.

    HOW TO UPDATE a ROM and Keep TWRP and ROOT:
    Before all Disable all magisk modules for boths methods

    - Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
    - Flash Rom;
    - Flash TWRP Installer;
    - Flash magisk(recommend to use Magisk v19.4);
    - Reboot.

    Download:
    TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
    TWRP 3.3.1-2 Unofficial by Nikesh Kataria

    Donations:



    Credits:

    Thanks to @mauronofrio for a great help to make a stable recovery
    Thanks to @Typhus_ for hardcore testing
    Thanks to @prakash78 for testing

    Contributors
    Nik001
    Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp

    Version Information
    Status: Stable

    Created 2019-10-21
    31
    Proper install method explained

    Hello!

    Please, @Nik001, update the OP with the install method that I'm going to describe next, ok?

    It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for "not that experienced users".

    1. Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
    2. Download TWRP zip file and copy it to your device (internal or external storage)
    3. Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
    4. Open a cmd line and execute these commands (being on that folder, of course):
      adb devices (to make sure your device is detected)
      adb reboot bootloader (to reboot into fastboot mode)
      fastboot getvar current-slot (to check what's your current active slot)
      fastboot set_active b (if your active slot was a, if it was b then change it to a)
      fastboot erase boot
      fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
      fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
    5. When TWRP recovery boots, if you have a stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
    6. Install the TWRP zip (always install the latest build available)
    7. Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
    8. Reboot to System

    Why do I suggest this?


    By doing this method (which seems more complicated but, trust me, it's how it should be done) we will flash TWRP img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When TWRP boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the TWRP img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition.

    On the other hand, if we have a stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching TWRP img and boot.img).


    Cheers!
    6
    This man -> @Nik001 deserves a beer!!!

    Thank you for delivering us a fully working TWRP for laurel_sprout!

    Cheers!