Recommended and tested TWRP Recovery

[-Alf-]

I got it wrong, it's a PRA-LX3.

do you mean that PRA-LX3 got an upgrade to EMUI 9.1?

There was a bit of a miscommunication, im talking about Magisk root, on EMUI 8 you don't need patched recovery_ramdisk, (because ramdisk is not included in recovery_ramdisk). Simply flash Magisk.zip in TWRP and install Magisk manager apk.
And recovery partition will be not occupied by Magisk

 

[hopeless_bricker]

do you mean that PRA-LX3 got an upgrade to EMUI 9.1?

There was a bit of a miscommunication, im talking about Magisk root, on EMUI 8 you don't need patched recovery_ramdisk, (because ramdisk is not included in recovery_ramdisk). Simply flash Magisk.zip in TWRP and install Magisk manager apk.
And recovery partition will be not occupied by Magisk

I made a mistake, I meant ANE. It's a P20 Lite. Sorry, I got the models turned around. It's on 9.1 C432.

 

[TureX]

Hi!
Is anyone that are using official lineageos 16 and has keeping any of this twrp installed? If yes, which one?

Cheers

 

[Frax3r]

I reuploaded these twrps to my mega.nz repo. I hope you don't mind. @-Alf-

 

[Alex46165]

Hi, I'm having some problems with this recovery. I flashed the TWRP 3.2.1-0 GAGUGA Edition on my Honor 9 Lite with stock ROM.
Basically if I do this:

1. Boot into the TWRP recovery by pressing Vol Up + power button​

2. In the menu, Reboot->Recovery​

3. Wait for the recovery to boot up and go in the Reboot menu​

​

Now no matter what I choose to boot into(fastboot or system), the phone will always boot in the recovery and the only way to fix that is to go in eRecovery mode by turning off the phone, keeping the volume up button pressed and plugging the phone in my computer.
Is this normal behaviour or is it a bug?

 

[Frax3r]

Hi, I'm having some problems with this recovery. I flashed the TWRP 3.2.1-0 GAGUGA Edition on my Honor 9 Lite with stock ROM.
Basically if I do this:

1. Boot into the TWRP recovery by pressing Vol Up + power button​

2. In the menu, Reboot->Recovery​

3. Wait for the recovery to boot up and go in the Reboot menu​

​

Now no matter what I choose to boot into(fastboot or system), the phone will always boot in the recovery and the only way to fix that is to go in eRecovery mode by turning off the phone, keeping the volume up button pressed and plugging the phone in my computer.
Is this normal behaviour or is it a bug?

It is a feature turned into a bug with emui 9. I can only speculate but it is probably related to us having boot bundled with recovery in stock partitioning scheme. There's a twrp that actually utilizes this bug/feature. It's for honor 9 lite but it's based on official p20 lite twrp so it works on p20 lite too. Check here if you want to test it yourself. Boot it and go to reboot menu, there'll be a boot override selection. I haven't seen any twrp that offers this other than tishserg's.

edit : I've had the same thing happened to me multiple times and fixed it with the twrp in question. Irc another way to trigger this is to factory reset from gsi while twrp is installed. You'll keep booting to twrp until you fix it the way you did or with the twrp I linked.

 

[-Alf-]

Hi, I'm having some problems with this recovery. I flashed the TWRP 3.2.1-0 GAGUGA Edition on my Honor 9 Lite with stock ROM.
Basically if I do this:

1. Boot into the TWRP recovery by pressing Vol Up + power button​

2. In the menu, Reboot->Recovery​

3. Wait for the recovery to boot up and go in the Reboot menu​

​

Now no matter what I choose to boot into(fastboot or system), the phone will always boot in the recovery and the only way to fix that is to go in eRecovery mode by turning off the phone, keeping the volume up button pressed and plugging the phone in my computer.
Is this normal behaviour or is it a bug?

This TWRP doesn't have the bug at all. (If you know what you're doing . )

 

[avenger.forsyth]

It is a feature turned into a bug with emui 9. I can only speculate but it is probably related to us having boot bundled with recovery in stock partitioning scheme

You again?
Last time i saw the boot partition on android 7...

I can only speculate

Exactly! YOU can only speculate bro.

 

[Frax3r]

You again?
Last time i saw the boot partition on android 7...

Exactly! YOU can only speculate bro.

I'd argue with you but I see no point in doing so. Instead I am going to elaborate my point for future replies. Boot image is a combination of partitions. Normally a boot image includes kernel, ramdisk and few headers along with AVB. But this device is not normal. Huawei with their ultimate wisdom decided to approach this partitioning with a radical view and split these partitions into their own image. Then they merged them with different images in emui 9. Magisk is a perfect example for this because it uses ramdisk. It patches boot image because ramdisk is inside the boot image for most devices. But you patch dedicated ramdisk.img in emui 8 and recovery_ramdisk.img in emui 9 because that's where ramdisk resides for us. You could learn this much just by looking at magisk log while patching image from manager. So yeah, "boot" is bundled with recovery in our devices. As for the speculation part, it is what it is. I am no genius but I certainly am not a idiot either. I can't pinpoint why a bug happens with just the explanation of it.

normal devices : boot.img = AVB + kernel + ramdisk
emui 8 devices : ramdisk.img = ramdisk
emui 9 devices : recovery_ramdisk.img = recovery + ramdisk

 

[-Alf-]

Let's please remember to keep conversations and comments in this thread about "Recommended and tested TWRP Recovery".
Thank you.

 

[Alex46165]

This TWRP doesn't have the bug at all. (If you know what you're doing . )

Well I haven't done much so I think I know what I'm doing...
I've even reflashed the stock recovery, re-downloaded the TWRP, flashed it in recovery_ramdisk as usual and the bug is still there. Also looking in the thread on 4pda, it seems like I'm not the only one who has encountered this problem 1

 

[-Alf-]

it seems like I'm not the only one who has encountered this problem 1

it was a little different case - TWRP flashed over eRecovery + magisk-patched-recovery installed instead stock Recovery.

I have never faced problem like this on stock 9.1...
Try to install 3.2.1-0 by Pretoriano80, and let me know.

Well I haven't done much so I think I know what I'm doing..

Okay, sorry.

 

[-Alf-]

If you have installed another TWRP (e.g. 3.4.0 and above) before you have installed 3.2.1 (gaguga), then it may happen that the loading task stuck somewhere.
So if you have the same problem with TWRP Pretoriano, flash stock recovery, perform Wipe cache partition, and flash TWRP 3.2.1 by Gaguga again. GL!

 

[Alex46165]

I have installed the TWRP by pretoriano80 and it doesn't have that problem Thanks
(I had only installed the twrp by gaguga)

 

[-Alf-]

(I had only installed the twrp by gaguga)

Probably this modified TWRP is not fully compatible with LLD. So far I only knew about the bug on FIGO devices.
It should be noted that this TWRP has been modified for Honor 9, not for hi6250. Luckily it works on ANE without any problems...
Also you can try non-modified 3.2.1 , download .
Or search in Honor 9 lite section.

 

[[email protected]]

Hello to all, any idea where to find twrp compatible with the Huawei y9s 2019?
I tried some they boot but no response to touch, any device similar with twrp you know off?

 

[-Alf-]

compatible with the Huawei y9s

Hi,
TWRP compatibility depends on Android/EMUI version and intended usage (custom ROMs), not phone model.

 

[[email protected]]

Hi,
TWRP compatibility depends on Android/EMUI version and intended usage (custom ROMs), not phone model.

Am running emui 9.1 on stock ROM.

The 2 twrps I found here 1 boots(3.4 version) but reboots straight to bootloader, the other 3.2.x version didn't load twrp menu, only black screen and reboot and if no button Touched straight to emergency backup

 

[-Alf-]

Just to be sure - run commands :

fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION

and post the results.
Some might fail, so don't worry about it.

 

[[email protected]]

~ $ su
astboot oem get-build-number <
(bootloader) :STK-L22DV 9.1.0.359(C185E1R1P1)
OKAY [ 0.002s]
Finished. Total time: 0.002s
astboot oem get-product-model <
(bootloader) STK-L22
OKAY [ 0.002s]
Finished. Total time: 0.002s
astboot getvar vendorcountry <
vendorcountry: hw/meafnaf
Finished. Total time: 0.002s
astboot oem oeminforead-CUSTOM_VERSION <
(bootloader) :STK-L22DV-CUST 9.1.0.1(C185)
OKAY [ 0.003s]
Finished. Total time: 0.003s
astboot oem oeminforead-SYSTEM_VERSION <
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
1|:/data/data/com.termux/files/home #