[RECOVERY][lavender][UNOFFICIAL] TWRP touch recovery for Redmi Note 7

Search This thread

PYCON

Senior Member
Nov 1, 2006
1,470
300
I've seen on youtube some tutorial related to TWRP for our RN7 with a strange logo... LR TEAM or something like that. The version of that TWRP seems to be 3.3-0517.

Someone knows what's different in that release? Is newer than this one? And where to find it?


Thx
 

Tanay nag

Senior Member
May 22, 2018
106
4
When i am trying it on RN7s
I flash recovery from computer it flashed successfully
Then i boot into recovery then i flashed the recovery zip again and i boot in recovery.
Then i boot in system futon recovery.
Next time when i go to recovery it replaced with stock recovery.
 

artaeun

New member
Aug 26, 2018
3
3
If you flashed TWRP, but you can't get into the TWRP recovery screen, this is for you:
I was having the same issue, but this phone is tricky.
Just DON'T USE fastboot boot recovery.img

1. Boot into Fastboot screen
2. fastboot flash recovery recovery.img
3. Check if flashed ok in the cmd prompt and remove the usb cable while the fastboot screen is on
4. Keep pressed Volume UP + POWER until the phone reboots - after the first vibration, remove your finger from power button, but keep Volume UP.
5. You should boot into TWRP screen.

If you use "fastboot boot recovery.img" - the old recovery from gets back - DON'T USE IT

Well, at least that's how it worked for me on two Redmi Note 7 lavender (64gb rom/4gb ram).

well this saved my ass.. i wiped the Data and Cache like a dummy because i got stuck into the password screen for not wiping the data on the first boot, and got stuck on an endless boot.. now i finally managed to boot into TWRP and flash the damn dalvik and get back from the beginning. Thanks!
 
  • Like
Reactions: Andrio

Ptathavi

Member
Feb 7, 2016
25
3
23
Bhopal
Hello, I need help does the same recovery works with Redmi note 7s? It's exactly the same as redmi note 7(Lavander). Someone, please reply as I tried this with redmi note 7s and it kinda bricked my devices, i wasn't able to boot to fast boot and if luckily if i did; it stayed there just for a second or two and then rebooted back to system and then asked for the password to turn back on the devices. Any help would be appreciated, thank you. :)
 

Walden0

Retired Forum Moderator
Nov 24, 2018
2,019
1,165
Jabalpur
Hello, I need help does the same recovery works with Redmi note 7s? It's exactly the same as redmi note 7(Lavander). Someone, please reply as I tried this with redmi note 7s and it kinda bricked my devices, i wasn't able to boot to fast boot and if luckily if i did; it stayed there just for a second or two and then rebooted back to system and then asked for the password to turn back on the devices. Any help would be appreciated, thank you. :)
All the stuff is same for Note 7 and 7S.
Regarding yhe issue you faced , it didn't get brick. Fastboot mode doesn't stay there usually if you haven't connected the usb cable or the port is faulty. The password thing is called encryption , it happens when you switch from aosp to miui or vice versa , maybe sometimes with aosp to aosp rom. You need to format data from recovery in order to fix it.
 

Ptathavi

Member
Feb 7, 2016
25
3
23
Bhopal
All the stuff is same for Note 7 and 7S.
Regarding yhe issue you faced , it didn't get brick. Fastboot mode doesn't stay there usually if you haven't connected the usb cable or the port is faulty. The password thing is called encryption , it happens when you switch from aosp to miui or vice versa , maybe sometimes with aosp to aosp rom. You need to format data from recovery in order to fix it.

Ok Bro thanks a lot, it was really a great help!? Thanks again a million!!
 

ssaikia3

Senior Member
Jan 9, 2018
128
52
All the stuff is same for Note 7 and 7S.
Regarding yhe issue you faced , it didn't get brick. Fastboot mode doesn't stay there usually if you haven't connected the usb cable or the port is faulty. The password thing is called encryption , it happens when you switch from aosp to miui or vice versa , maybe sometimes with aosp to aosp rom. You need to format data from recovery in order to fix it.
"...You need to format data from recovery..." By "data" do you mean the internal storage or the data partition? I know it's silly but please confirm. Thanks.
 

Walden0

Retired Forum Moderator
Nov 24, 2018
2,019
1,165
Jabalpur
"...You need to format data from recovery..." By "data" do you mean the internal storage or the data partition? I know it's silly but please confirm. Thanks.
It means internal storage and data partition both. "formatting data" means wiping /data and internal storage , while "wiping data" simply means wiping /data.
 
  • Like
Reactions: ssaikia3

nagesh nani

Senior Member
Aug 16, 2018
137
4
well this saved my ass.. i wiped the Data and Cache like a dummy because i got stuck into the password screen for not wiping the data on the first boot, and got stuck on an endless boot.. now i finally managed to boot into TWRP and flash the damn dalvik and get back from the beginning. Thanks!
Anna recovery latest version update ple

---------- Post added at 11:56 PM ---------- Previous post was at 11:51 PM ----------

Any custom roms install problem Anna please mobile no.call back
 

SugnaB

Member
Jun 16, 2016
23
0
So i recently just flashed the unofficial 16.0 lineage OS on my Redmi Note 7 (lineage-16.0-20191006-UNOFFICIAL-lavender.zip).

Everything was going pretty well twrp installed successfully. Then i hit an error when side loading Lineage OS which was that there was a "ZIP treble compbatibility Error"

I searched up how to fix this and someone said delete compatibility.zip, did that and it booted fine into Lineage OS with no issues. After that i tried flashing gapps (open_gapps-arm64-9.0-nano-20191009) which took me to a boot loop where it would try boot into lineage, then after about 3mins would reboot in to recovery. I read up on people saying you needed to flash them together. So i factory reset AND Formatted my data. Then i side loaded lineage (without compatibility.zip) and then i side loaded Gapps. Which then did the exact same thing and keeps taking me back to recovery. I also tried pico Gapps and that didn't work either!

I am also on twrp 3.3.0-0 if that helps

I am lost as to what to try and what to do now. Any help would be great! Thanks
 

Walden0

Retired Forum Moderator
Nov 24, 2018
2,019
1,165
Jabalpur
So i recently just flashed the unofficial 16.0 lineage OS on my Redmi Note 7 (lineage-16.0-20191006-UNOFFICIAL-lavender.zip).

Everything was going pretty well twrp installed successfully. Then i hit an error when side loading Lineage OS which was that there was a "ZIP treble compbatibility Error"

I searched up how to fix this and someone said delete compatibility.zip, did that and it booted fine into Lineage OS with no issues. After that i tried flashing gapps (open_gapps-arm64-9.0-nano-20191009) which took me to a boot loop where it would try boot into lineage, then after about 3mins would reboot in to recovery. I read up on people saying you needed to flash them together. So i factory reset AND Formatted my data. Then i side loaded lineage (without compatibility.zip) and then i side loaded Gapps. Which then did the exact same thing and keeps taking me back to recovery. I also tried pico Gapps and that didn't work either!

I am also on twrp 3.3.0-0 if that helps

I am lost as to what to try and what to do now. Any help would be great! Thanks
Flash orangefox twrp , wipe data, system, cache and dalvik along with formatting data. Then flash rom and gapps.
Report if that worked.
 

SugnaB

Member
Jun 16, 2016
23
0
Flash orangefox twrp , wipe data, system, cache and dalvik along with formatting data. Then flash rom and gapps.
Report if that worked.

Thanks for the insight on orangefox, much nicer than twrp! But yeah, turned out the issue was gapps 2019.10.10 and 2019.10.09. They both do not work on the unofficial lineage OS 16. 2019.10.06 worked well for me. Hope this helps other people
 

MHDhsn

Member
Sep 16, 2015
6
0
The recovery is not bootig instead the official miui recovery is booting after installing this one.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 92
    https%3A%2F%2Fimg.xda-cdn.com%2FpSvihPyfhapF9LoHqaNVoQ9y7kw%3D%2Fhttp%253A%252F%252Flh3.googleusercontent.com%252F2HtVAF5zfNMlmKhF0QYqCSr1rsstB1btNfdKl7WvGTcZkOSKCYNxdXwsSizx9VhiPg%253Dw300

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. 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.

    Code:
    #include <std_disclaimer.h>
    
    /*
     * Your warranty is now void.
     *
     * 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.
     *
     */

    Features:
    • All function in a normal TWRP
    • Multi-language support
    • Supports MTP
    • Support decrypt /data!

    Install guide:
    1. Install fastboot tools from google's sdk on your PC
    2. Enter fastboot mode
    3. Unlock your bootloader
    4. Run "fastboot flash recovery recovery.img" in command line
    5. Reboot and enjoy it

    Download:
    https://drive.google.com/uc?id=1rp_cgVuk6fsRybN0wDoOTbt_Pc-vOiHx&export=download

    Source code:
    https://github.com/omnirom/android_bootable_recovery
    https://github.com/thelazyindian/android_device_xiaomi_lavender-twrp

    Note:
    • Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
    • When you flash twrp for the first time in MIUI you need to goto Wipe > Format Data otherwise you won't be able to boot to system as it will ask for password.
    • GAPPS FIX: In TWRP, goto Mount > system_root and try reflashing.

    FAQ:
    How is it different from other TWRPs available for lavender ?
    This build uses standalone decryption which is better than the recoveries using vold decrypt as vold decrypt will fail if system ROM is corrupt or wiped

    Credits:
    Huge thanks to @abhishek987 and @vasishath for helping
    @tufadorin @faraz shafi (For testing)
    9
    Changelog:

    Build 03/05/19:
    • Add offset for notch
    • Updated prebuilt kernel built from source
    • Option to mount system as system_root to fix GAPPS flash error
    • Enable /vendor wipe option

    Links updated in OP
    6
    If you flashed TWRP, but you can't get into the TWRP recovery screen, this is for you:
    I was having the same issue, but this phone is tricky.
    Just DON'T USE fastboot boot recovery.img

    1. Boot into Fastboot screen
    2. fastboot flash recovery recovery.img
    3. Check if flashed ok in the cmd prompt and remove the usb cable while the fastboot screen is on
    4. Keep pressed Volume UP + POWER until the phone reboots - after the first vibration, remove your finger from power button, but keep Volume UP.
    5. You should boot into TWRP screen.

    If you use "fastboot boot recovery.img" - the old recovery from gets back - DON'T USE IT

    Well, at least that's how it worked for me on two Redmi Note 7 lavender (64gb rom/4gb ram).
    4
    Can you install official miui ota zip after installing twrp and magisk?
    Would it brick the device?

    It won't brick the device, but no you can't install them.
    The update will just fail and reboot you back into MIUI. Everything working as usual.

    If you want TWRP/Magisk installed and get updates then you'll have to manually download the 'Recovery ROM' to the update you want to update to. Then flash it in TWRP like you would a custom ROM.
    You'll want to reinstall Magisk after you flash the Recovery ROM to get root back.

    TWRP remains intact