[RECOVERY][Unofficial] TWRP 3.2.1-0 [Notch Friendly] P20 Lite Edition

[ConsoleHax]

[RECOVERY][Unofficial][TWRP 3.2.1-0][Notch Friendly] P20 Lite Edition​

Don't use WIPE the data partition

[/B]
 * Your warranty is now void.
 * I am not responsible for bricked devices.
 * ATTENTION: YOU are choosing to install this recovery at your own risk.
 * I do not take responsibility for any problems with your device.

Features:
- This recovery is based on the TWRP from Pretoriano80
- Notch-friendly; due to notch-design I re-positioned the clock, now it is visible all the time
- I added the possibility to do a full device backup, thanks to Sudeep Duhoon

Installation:

fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
fastboot reboot

*Note many devices will replace your custom recovery automatically during first boot.
To prevent this, after typing fastboot reboot, remove the USB cable and hold the Vol+ key and boot to TWRP.
Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP.
If you don't follow this step, you will have to repeat the install.

Note: No sources available due to minor changes on the Pretoriano80's TWRP

Special Thanks:
@Pretoriano80
@zxz0O0
@Sudeep Duhoon
@persona78
+TeamWin
+OpenKirin

Version Information:
Status: Under testing

Created: 2018-06-06
Last Updated:

Download link:
TWRP_3.2.1-0_ANE-LX1_Full_01.img

Thank you! Can you please provide an update for compatibility with android Pie?

 

[kilroystyx]

[RECOVERY][Unofficial][TWRP 3.2.1-0][Notch Friendly] P20 Lite Edition

Don't use WIPE the data partition

* Your warranty is now void. * I am not responsible for bricked devices. * ATTENTION: YOU are choosing to install this recovery at your own risk. * I do not take responsibility for any problems with your device.



Features:
- This recovery is based on the TWRP from Pretoriano80
- Notch-friendly; due to notch-design I re-positioned the clock, now it is visible all the time
- I added the possibility to do a full device backup, thanks to Sudeep Duhoon

Installation:


Thank you! Can you please provide an update for compatibility with android Pie?

I can't do it. My current phone is P20 Pro.

Btw in my case in EMUI 9.0 I don't use TWRP, to have root the Magisk patch stock recovery_ramdisk image. After boot into recovery Magisk does the magic an phone restart with root.

Not sure how it will be in EMUI 9.1 but should be something identical.

 

[ladislav.heller]

Not really the proper thread but anyway was able anynody successfully root the ANE-LX1 stock EMUI9 ?

For me the method below does NOT work
0. Unlocked bootloader - obviously.
1. Extract recovery_ramdisk from official EMUI9 image and copy it to device.
2. Install Magisk app and patch the copied image.
3. Download patched image from device to laptop.
4. Reboot device to bootloader and flash image using fastboot.
5. Reboot to patched recovery to activate root => this part doesn't work

Anybody has the same problem and/or solution?

 

[kilroystyx]

Not really the proper thread but anyway was able anynody successfully root the ANE-LX1 stock EMUI9 ?

For me the method below does NOT work
0. Unlocked bootloader - obviously.
1. Extract recovery_ramdisk from official EMUI9 image and copy it to device.
2. Install Magisk app and patch the copied image.
3. Download patched image from device to laptop.
4. Reboot device to bootloader and flash image using fastboot.
5. Reboot to patched recovery to activate root => this part doesn't work

Anybody has the same problem and/or solution?

All your steps are correct according EMUI9 maybe in the EMUI9.1 you need do something extra!!!

 

[Migueks]

Fix

Not really the proper thread but anyway was able anynody successfully root the ANE-LX1 stock EMUI9 ?

For me the method below does NOT work
0. Unlocked bootloader - obviously.
1. Extract recovery_ramdisk from official EMUI9 image and copy it to device.
2. Install Magisk app and patch the copied image.
3. Download patched image from device to laptop.
4. Reboot device to bootloader and flash image using fastboot.
5. Reboot to patched recovery to activate root => this part doesn't work

Anybody has the same problem and/or solution?

In order to boot with Magisk, you have to always reboot to recovery (press volume up while booting)
or using ADB
adb reboot recovery

 

[ladislav.heller]

In order to boot with Magisk, you have to always reboot to recovery (press volume up while booting)

or using ADB

adb reboot recovery

Hello

When I press volume up too long, it reboots to eRecovery, which is different than normal recovery.

I also tried "adb reboot recovery" where the device will stuck at booting and nothing happens.


Tapatalkkal küldve az én ANE-LX1 eszközömről

 

[kilroystyx]

Hello

When I press volume up too long, it reboots to eRecovery, which is different than normal recovery.

I also tried "adb reboot recovery" where the device will stuck at booting and nothing happens.


Tapatalkkal küldve az én ANE-LX1 eszközömről

Send me your stock recovery_ramdisk.img and I will patch it for you.

 

[Arnys]

Hello

When I press volume up too long, it reboots to eRecovery, which is different than normal recovery.

I also tried "adb reboot recovery" where the device will stuck at booting and nothing happens.


Tapatalkkal küldve az én ANE-LX1 eszközömről

bigest mistake are "USB still conected" , you never will be able to boot in recovery, if usb are conected, disconect it

 

[ladislav.heller]

Send me your stock recovery_ramdisk.img and I will patch it for you.

Uploaded here:
https://drive.google.com/file/d/12GiZfc8CWj02OBzrNH3yu0_Qjh8a6tJL/view?usp=drivesdk

Tapatalkkal küldve az én ANE-LX1 eszközömről

 

[kilroystyx]

Uploaded here:
https://drive.google.com/file/d/12GiZfc8CWj02OBzrNH3yu0_Qjh8a6tJL/view?usp=drivesdk

Tapatalkkal küldve az én ANE-LX1 eszközömről

https://mega.nz/#!4BJWhA4K!-kivmOkb8b0c1He26OtJb79LRd-jDy3urdF20kxl9QU

Name: magisk_patched.img
Size: 30494720 bytes (29 MiB)
CRC32: 521A8681
CRC64: 1889C6BD6403C1C9
SHA256: 69D3F46E13B659893FEA21FE3F0548706D31D73E6CB46606EA581D1133D1A3E8
SHA1: 84EC8338D41DF3DB64FCEA450D4B5F13FB9A176A
BLAKE2sp: 4FD76D5791F2A4346091AF8C208E93EBC09AA4AFA7B918AE67F81529A055AEFF

Test only if the one patched by you got a different checksum.

 

[ladislav.heller]

https://mega.nz/#!4BJWhA4K!-kivmOkb8b0c1He26OtJb79LRd-jDy3urdF20kxl9QU

Name: magisk_patched.img
Size: 30494720 bytes (29 MiB)
CRC32: 521A8681
CRC64: 1889C6BD6403C1C9
SHA256: 69D3F46E13B659893FEA21FE3F0548706D31D73E6CB46606EA581D1133D1A3E8
SHA1: 84EC8338D41DF3DB64FCEA450D4B5F13FB9A176A
BLAKE2sp: 4FD76D5791F2A4346091AF8C208E93EBC09AA4AFA7B918AE67F81529A055AEFF

Test only if the one patched by you got a different checksum.

I have the same checksum.

Another info: Using adb reboot recovery I am able to boot to recovery, even when the recovey itself does not appear, just the previous screen is showing with the message "Your device is booting now".
But I am able to enter into shell using adb shell and even the su command works.
So the recovery image is patched, but the root functionality is only accessible in recovery mode.

 

[pmatj]

Just a question: is this a 3.3.x based TWRP (so that it can be flahsed/installed in ramdisk_recovery) or are we talking here about magisk?

I formyself got magisk working on the current Firmware, however I'm more interested in a more slim GSI (but I'm currently stucked with MagiskHide - it always leads to a bootloop and I do not know why...)

Best regards,
Peter

 

[ladislav.heller]

I formyself got magisk working on the current Firmware

If your firmware is EMUI9.1, then can u pls describe the exact steps how did you make Magisk working on it?

 

[pmatj]

If your firmware is EMUI9.1, then can u pls describe the exact steps how did you make Magisk working on it?

At first, follow the steps from Magisk Install:
1) Download a current FullOTA Firmware
2) deflate UPDATE.APP
3) Extract RECOVERY_RAMDIS.img (Using Huawei Image Extractor)
4a) Install Magsik-App
adb install MagiskManager-v7.3.2.apk
4b) Push Recovery to device
adb push RECOVERY_RAMDIS.img /sdcard/Download
4c) Let Magisk patch Recovery (Start MagisManager on device Install → Install → Select and Patch a File)
4d) Pull patched recovery from device
adb pull /sdcard/Download/magisk_patched.img
5) Restart device with VOL- and Power, Install this image to RECOVERY_RAMDISK
fastboot flash recovery_ramdisk recovery_ramdisk_patched.img
6) Now you can either do fastboot reboot, pull out the cord and push volup+power or do it slowly:
fastboot reboot
adb reboot recovery
7) Start Magsik, push install to set up some necesarry stuff reboot

Take care: you'll always have to reboot using recovery
From Magsik-Doc in GitHub:
In summary, after installing Magisk:

(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)


Some thinks I've noticed:
First of all, I was not able to enter the recovery (but this may be concerned as I almost always have connect the usb for now)
Taht's the reason, I was not able to reset/wipe the device (as eRecovery uses the normal recovery to wipe the device).
Don't panic: just reflash the original RECOVERY_RAMDIS.img and do everyhting nesessary.

Good luck,
Peter

 

[ladislav.heller]

Some thinks I've noticed:
First of all, I was not able to enter the recovery (but this may be concerned as I almost always have connect the usb for now)
Taht's the reason, I was not able to reset/wipe the device (as eRecovery uses the normal recovery to wipe the device).
Don't panic: just reflash the original RECOVERY_RAMDIS.img and do everyhting nesessary.

Good luck,
Peter

Exactly the same I noticed. Plus when I do the following:
1. fastboot reboot
2. quickly unplug usb cable
3. Vol+ and Power combo
the Magsik activation doesn't work and system does not boot into recovery.

When I release Vol+ and Power keys at splash/boot screen, the system starts normally, i. e. without Magisk. When I hold Vol+, system boots into eRecovery.
In other words I am not able to start system with Magisk. Maybe I am doing something wrong but it simply does not work.

I think I'll give up and go back to EMUI8 where Magisk/root works without problems.

 

[nofx161]

Exactly the same I noticed. Plus when I do the following:
1. fastboot reboot
2. quickly unplug usb cable
3. Vol+ and Power combo
the Magsik activation doesn't work and system does not boot into recovery.

When I release Vol+ and Power keys at splash/boot screen, the system starts normally, i. e. without Magisk. When I hold Vol+, system boots into eRecovery.
In other words I am not able to start system with Magisk. Maybe I am doing something wrong but it simply does not work.

I think I'll give up and go back to EMUI8 where Magisk/root works without problems.

i had the same and was at the same breaking point ,.. with the guide above just do that :
5) Restart device with VOL- and Power, Install this image to RECOVERY_RAMDISK
fastboot flash recovery_ramdisk recovery_ramdisk_patched.img
6) do fastboot reboot, dont pull out the cable start the phone, then adb reboot recovery, wait for the start dont do anything
7) Start Magsik

 

[alvaro_lopez_r]

Yes, it should work.
If not, let me know and, flash back your stock recovery.

Help man I update emui 8 to 9 but I want to go back to stock rom, emui 8, how do I do it?

 

[SkyMasterARC]

When I copy and paste the command it shows me this error message: "cannot load (insert file name)" why is this?

 

[Zep0th]

Do I need an unlocked bootloader
Also I have ANE-LX3C521

 

[nofx161]

Do I need an unlocked bootloader
Also I have ANE-LX3C521

yes