Recommended and tested TWRP Recovery

Search This thread

-Alf-

Senior Member
Sep 28, 2017
2,285
804
Huawei P9 Lite
Huawei P10 Lite
EMUI 8 Stock ROMs:

3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw

EMUI 8 Custom ROMs:

3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA

3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k

Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI

EMUI 9.1 Stock ROM & Custom ROMs:

3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8

EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU

On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
 
Last edited:

wax_77

Member
Nov 21, 2011
11
3
hi all,
addonsu.zip works?

my output trying to flash via twrp

...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...

twrp seems work fine, i can flash los and gapps without problem...

thank you
 

TureX

Senior Member
Mar 9, 2011
644
211
Huawei P20 Lite
hi all,
addonsu.zip works?

my output trying to flash via twrp

...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...

twrp seems work fine, i can flash los and gapps without problem...

thank you
HI!
Which vendor are you using? And which twrp shared are you using? Does lineageos 16 official boot keeping twrp installed?
Thanks in advance
 

-Alf-

Senior Member
Sep 28, 2017
2,285
804
Huawei P9 Lite
Huawei P10 Lite
hi all,
addonsu.zip works?

my output trying to flash via twrp

...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...

twrp seems work fine, i can flash los and gapps without problem...

thank you
Hello,
I successfully installed the addonsu-16.0-arm64 using
TWRP
You have to enable root in Developer options. Works fine...
 
Last edited:

fragtion

Senior Member
Sep 1, 2013
200
62
Johannesburg
Hi all. I am trying to recover content from a MediaTab T5 with a Damaged screen (no picture). I've managed to install these recoveries and reboot into them. However none of them provide an adb interface for shell access, only a virtual usb cd rom drive appears. How can I obtain recovery adb access? I need to enable USB debugging and push adbkey...

Anyone have any clues how I can work around this please. Is patched boot img the only way forward?


OK good news I Successfully booted into recovery and have adb access. I think the key was to power on with vol+, but WITHOUT the USB cable attached. If USB cable is attached then it tries to boot to system regardless
 
Last edited:

-Alf-

Senior Member
Sep 28, 2017
2,285
804
Huawei P9 Lite
Huawei P10 Lite
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!

Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
 
  • Like
Reactions: Mahad Habib
Jan 19, 2016
31
19
Hey Alf,

Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.

PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.

Thank you for your posts, they've been useful.
 

-Alf-

Senior Member
Sep 28, 2017
2,285
804
Huawei P9 Lite
Huawei P10 Lite
Hey Alf,

Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.

PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.

Thank you for your posts, they've been useful.
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.

P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
Since the recovery partition is occupied by Magisk
 
Last edited:
Jan 19, 2016
31
19
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.

P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
I got it wrong, it's a ANE-LX3! Mixed up with my other phone, sorry. In principle that method works, thank you. I didn't get to actually test it because it seems the Magisk recovery overrides the boot procedure so it always boots to recovery automatically.

Handy but I can't boot into the erecovery with the button combo now.

P.S.: I'm having issues with audio device switching. If I get a phone call with headphones inserted it routes to the speaker and I can't change it. If I remove the headphones then the mic doesn't work. I also have a bit inconsistent connection over bluetooth, sometimes it is connected but still plays over the speakers. I have the Huawei switch method enabled in the phh options. Did you experience this?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    EMUI 8 Stock ROMs:

    3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
    https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw

    EMUI 8 Custom ROMs:

    3.2.1.0 by Catuva21:
    https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA

    3.2.3-0 by Askuccio
    https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k

    Chinese ROMs (inc. KangVip):
    3.2.1-0
    https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI

    EMUI 9.1 Stock ROM & Custom ROMs:

    3.2.1-0 GAGUGA Edition
    https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8

    EMUI 9.1 Custom ROMs:
    3.4.0-0-emui9_eR by @S_mak
    https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU

    On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
    1
    yes that's my question.
    the one I have is
    "Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
    I know this works because I used it to downgrade.
    Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!

    Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
    update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
    1
    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.
    1
    You again? :giggle:
    Last time i saw the boot partition on android 7... :cool:

    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
    1
    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