[RECOVERY] Unofficial TWRP 3.3.1-0 recovery for Xiaomi Redmi (olive)

  • Thread starter Deleted member 10372799
  • Start date
Search This thread

JaSomTy

Senior Member
Dec 20, 2017
57
12
Kežmarok
hey man i fixed up novatek touchscreens on a repack version of your twrp i will include here
Download also i did a PR on your github with the needed changes so your next version will have this fix

I tried it and it bricked my device, fixed by flashing stock recovery. I don't have any details about the brick, I just know that after flashing I can't access anything but fastboot.

Edit: To clarify, it boots straight into fastboot, no matter what buttons I press or what command I send from PC.
 

ahmedsheme

Senior Member
May 1, 2013
62
18
Cairo
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.

How to Disable Ads (Most of Them) From Your Xiaomi Phone Running MIUI 9/ MIUI 10
https://c.mi.com/thread-1864821-1-0.html

How to Remove Ads From Xiaomi Phone: Step by Step Instructions to Disable Ads in MIUI 10
https://gadgets.ndtv.com/how-to/fea...disable-ads-step-by-step-instructions-2016469

MIUI 11 offers one-click to disable Ads of Xiaomi phones: Here is how to do it
https://www.gearbest.com/blog/how-t...ds-of-xiaomi-phones-here-is-how-to-do-it-8966
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    D
    Deleted member 10372799
    There is now an official version available (xda post). Go use that.
    2
    @seprode, Reading your post and seen your work, I decided and today I ordered a Redmi 8 (olive) for my self , too.
    I am very thankful that there are people like you, pioneers, who open the path, for all of us to follow.
    Thank you again for what you are doing for us.
    I hope, soon enough, some developer will pay attention to our new phone and , maybe , we will be also able to see new Android (Q ?) roms for it.
    I am active involving so far in Samsung NOTE 2(exynos) and Note 4 (snapdragon) and also Xiaomi Redmi 5 plus community
    I will do my best and see, if any of these groups will be able , in the future, to do something for our little brother here.
    But the path you have open, is the very important first step to it.
    KUDOS

    :good::):good:
    2
    D
    Deleted member 10372799
    @pulka103 You want to try again? I made some changes and got MTP working.
    1
    I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
    I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
    I used it successfully to flash the xiaomi.eu rom and magisk.

    You can find the device tree on my GitHub: here
    And the image in the release section: here

    Installation:
    • Unlock Bootloader if not already done (Official Tool)
    • Boot in to fastboot (Powerbutton + volume down)
    • Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
    • Boot in to recovery (Powerbutton + volume up)

    If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
    You can download the fastboot rom here.

    I have a problem and maybe some of you can help me. I flashed last recovery.img. After flashing phone reboot itself and boot to system. Next, perform reboot to recovery and it boot to mi-recovery, not twrp. Then I cant boot to system. I have to flash again and then it boot to system.

    ===EDIT====
    Ok, I managed this. After "fastboot flash recovery recovery.img" you have to type "fastboot reboot"
    1
    @pulka103 You want to try again? I made some changes and got MTP working.

    hey man i fixed up novatek touchscreens on a repack version of your twrp i will include here
    Download also i did a PR on your github with the needed changes so your next version will have this fix