Develop Bugs

[Q] galaxy nexus stuck on boot loop screen animation.

I update, my ROM from cyanogenmod ROM 10.1 m1 to 10.1 m2 ROM and know my galaxy nexus is stuck on boot loop animation! I tried, tacking out the battery and then turning it back on no luck in also tried the ( volume button and power button method) and still no luck with that. Is,there a way I could fix it?

wipe data and reflash rom.

Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse

Never, mind i got it working know!

mrcoleminer said:
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse

Zepius said:
mrcoleminer said:
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse

Chamaeleon said:
Zepius said:
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse

Soulaysahmi said:
Chamaeleon said:
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
I was using the ClockworkMod (I don't remember exactly the version number but I updated recently and it was the touch screen one). I'll try to re-install also the recovery with the very last version (6.0.4.7). Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse

Chamaeleon said:
Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
have you tried adb sideload?

Soulaysahmi said:
have you tried adb sideload?
Click to expand...
Click to collapse
Just tried.
On the terminal after the command
adb sideload cm-11-20141115-SNAPSHOT-M12-maguro.zip
it tells me "error: closed"
I also tried to reinstall the Clockwork via bootloader but didn't change the situation (still not able to do a complete factory reset)

you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?

Soulaysahmi said:
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Click to expand...
Click to collapse
You are right, I didn't click "install zip from sideload" before. Now I tried in this way and, effectively, it worked: I managed to send and install the zip apparently without any problem but than after rebooting I'm still not able to turn on the phone completely. Again the same problem. I re-tried to do wipe data/factory reset both from the recovery and using adb but didn't managed to finish the process...
It seems I tried all the options since now.... but my nexus is still unusable...

did you try getting back to stock rom using any guide on this forum?

Soulaysahmi said:
did you try getting back to stock rom using any guide on this forum?
Click to expand...
Click to collapse
I tried but still with the same result. I'll try to follow the guide I found here

I mean through methods other than recovery, through fastboot mode or odin mode.

Soulaysahmi said:
I mean through methods other than recovery, through fastboot mode or odin mode.
Click to expand...
Click to collapse
I tried to Restore Galaxy Nexus to Stock (as described here) with the proper google image but in the last passage I get:
$ fastboot -w update image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMELC03
Baseband Version.....: xxx
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
FAILED
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'
I put all I need in one folder and I decided to update the bootloader at the PRIMEMD04 version but apparently I didn't managed because doing again the procedure I was getting the same error
ps: I'm using linux so I don't have odin

when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?

Soulaysahmi said:
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Click to expand...
Click to collapse
Yes I have BOOTLOADER VERSION - PRIMELC03
With fastboot I tried to install the PRIMELC04 bootloader
$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.969s]
finished. total time: 8.278s
$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But than, after the reboot, on the screen it's still written BOOTLOADER VERSION - PRIMELC03
I think this is the main problem now... if it's not updated the bootloader I can not reinstall the rom probably...

you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img

Soulaysahmi said:
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Tried as you suggested to install the PRIMELC04 bootloader flashing each image.
Apparently is not possible also in this way. After rebooting on the screen is still written BOOTLOADER VERSION - PRIMELC03.
So I tried to install a stable cyanogenmod 10.2.1 (which should work with the bootloader 03).
I used adb sideload and after the "installing updates" message, everything stopped with the message "fixing fs_size in crypto footer". After more than 30 min I rebooted and the situation was the same as before.

Can't install custom recovery (TWRP)

Hello,
I have a big problem with my H815.
My H815 bootloader is been unlocked.
II try to install TWRP, but without success:
Code:
C:\Users\~\Downloads\G4\platform-tools>adb reboot bootloader
C:\Users\~\Downloads\G4\platform-tools>fastboot flash recovery twrp-2.8.7.0-h
815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32064 KB)...
OKAY [ 1.197s]
writing 'recovery'...
OKAY [ 0.317s]
finished. total time: 1.520s
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
For me, it's ok, but after that, my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Any idea please?
Kind regrards,
~~
Sylar

I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.

nfsolutions said:
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
Click to expand...
Click to collapse
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287

hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
This does not work for me. :'(
After this command : fastboot boot twrp-2.8.7.0-h815.img
My G4 boot imediatly to the System... :s

hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
thanks, now it works. My mistake was that I installed directly a supersu (not this from twrp) and this messed up the boot.
After installing twrp permanently, I used this method to get root:
http://forum.xda-developers.com/g4/general/guide-root-lg-marshmallow-rom-repacked-t3265497
now I have root and twrp

Can someone help me please ?

I tried to flash the KDZ 2 times but still nothing I parobleme always the same.

hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
Thank you Sir!
Got the same problem, installed TWRP but got bugdroid dead once booting recovery. Idk why TWRP isn't written.

Nothing to do I'm trying every way I could imagine. The result is always the same.
I can't find solution on any forum. Please, I need help. :'(
Kind Regards

Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk

rjboy11223 said:
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
Click to expand...
Click to collapse
No i'm not rooted atm. That why i wanna install a custom recovery ^.^

Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)

bender_007 said:
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
Click to expand...
Click to collapse
Thank you, but after that... :
Code:
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
...my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."

Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:

bel57 said:
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
Click to expand...
Click to collapse
Thank you, but same problème i can't boot to TWRP after the comand "fastboot boot twrp-2.8.7.0-h815.img" my G4 reboot directly to the system.

Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?

bel57 said:
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
Click to expand...
Click to collapse
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.

Ur phone is weird lol

Sylar37 said:
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Click to expand...
Click to collapse
try first fastboot erase recovery, then fastboot flash recovery twrp....img
then fastboot reboot recovery

I downloaded the v20b kdz and flashed via LGUP.. I don't know what's wrong mate, sorry. :silly:

Twrp disappears after loading, recovery Red Triangle NO Command

Getting confused.
Loaded Nougat on my Nexus 5x... unlocked boot loader, loaded TWRP 3.0.2-2 rebooted, saw TWRP,
Moving files to the phone to restore using TB, but have not yet done SUPERSU.. reboot back into recovery, Android Flat on back Red Triangle, No command??
Can reboot into the phone it works, just can't get back to TWRP for reasons I can't figure out.
Feels like I missing a step, but can't figure out what. Looked at a lot of pages, but nothing really stands out.
Update: Used fastboot boot [twrp imagename].img
And it got me directly to TWRP. Able to load SuperSU then.
Update #2: What I didn't make clear in this original post was I did in fact flash the TWRP recovery, it just didn't stick.
Command used originally:
Code:
C:\SDK\platform-tools>fastboot flash recovery twrp-3.0.2-2-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.579s
My mistake was to then reboot where it was apparently overwritten hence the confusion.

krelvinaz said:
Getting confused.
Loaded Nougat on my Nexus 5x... unlocked boot loader, loaded TWRP 3.0.2-2 rebooted, saw TWRP,
Moving files to the phone to restore using TB, but have not yet done SUPERSU.. reboot back into recovery, Android Flat on back Red Triangle, No command??
Can reboot into the phone it works, just can't get back to TWRP for reasons I can't figure out.
Feels like I missing a step, but can't figure out what. Looked at a lot of pages, but nothing really stands out.
Update: Used fastboot boot [twrp imagename].img
And it got me directly to TWRP. Able to load SuperSU then.
Click to expand...
Click to collapse
The reason that happens is if u fastboot boot twrp.img u will only have a temporary twrp until u reboot..if u had typed fastboot flash recovery recovery twrp.img then when u reboot the recovery would be permanent...
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
The reason that happens is if u fastboot boot twrp.img u will only have a temporary twrp until u reboot..if u had typed fastboot flash recovery recovery twrp.img then when u reboot the recovery would be permanent...
Click to expand...
Click to collapse
Actually, I did use flash the recovery. It came up just fine. However, after a reboot, when I booted back to recovery I got the No Command.
I had to re-flash TWRP, and then reboot back to Recover from TWRP, then reboot, then it worked like it should.

The command you posted was to boot a recovery, not to flash one in the recovery partition.
Anyway, you can't just flash TWRP and boot, because the boot will replace stock recovery, you got to flash supersu/another kernel from the recovery after flashing for it to stick.

You Can try this adb command :
fastboot flash recovery twrp_3.0-2-2.img
fastboot boot twrp_3.0-2-2.img
And normaly it's ok you have twrp installed

Thanks for the other responses...
Just to confirm what I did originally (I just unrooted so that I could use Magisk and PPH Root)
Code:
C:\SDK\platform-tools>fastboot flash recovery twrp-3.0.2-2-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.579s
However, If after doing this I rebooted the phone etc... TWRP was no longer there again. I had to do the same, force a boot to twrp, and then install Magisk before rebooting for it to stick.
Just in case someone else runs into this confusion.
I am now on Android 7 Nougat on a Nexus 5X with Magisk using PPH Root and can now use Root, Android Pay and some other apps which won't run with root enabled. Happy Camper for now.

The step your missing is after you fastboot flash the recovery don't reboot the phone just yet. You have to reboot the bootloader by typing fastboot reboot bootloader. After doing that use the volume up button to access recovery. Once you do that then you can start the phone.
Sent from my Nexus 5X using Tapatalk

krelvinaz said:
However, If after doing this I rebooted the phone etc... TWRP was no longer there again. I had to do the same, force a boot to twrp, and then install Magisk before rebooting for it to stick.
Click to expand...
Click to collapse
If you boot with a stock boot.img the android boot process will replace your recovery partition with stock if the SHA256 for the recovery doesn't match what it expects. The way you can stop this is to modify your boot.img, which would happen if you install SuperSU prior to first android boot after a new flash.

HELP miui 11.25 can't boot or flash twrp anymore

Hellpppp!
I can't boot nor flash custom recovery anymore after updatting to last Global Miui 11.15,
using :
fastboot boot twrp.img
stuck at : downloading 'boot.img'...
using fastboot flash recovery twrp.img
nothing happens,.
is this something with xiaomi ARP ?

Why don't you flash for example global stable through fastboot and see how it goes you just need to extract the tar.gz file and run the flash_all.sh file on the terminal.

Use mi flash with TGZ firmware.
if you can open the back cover then use test point method
XBowman said:
Hellpppp!
I can't boot nor flash custom recovery anymore after updatting to last Global Miui 11.15,
using :
fastboot boot twrp.img
stuck at : downloading 'boot.img'...
using fastboot flash recovery twrp.img
nothing happens,.
is this something with xiaomi ARP ?
Click to expand...
Click to collapse

XBowman said:
Hellpppp!
I can't boot nor flash custom recovery anymore after updatting to last Global Miui 11.15,
using :
fastboot boot twrp.img
stuck at : downloading 'boot.img'...
using fastboot flash recovery twrp.img
nothing happens,.
is this something with xiaomi ARP ?
Click to expand...
Click to collapse
Same here
Should I just downgrade to MIUI 9 just to flash TWRP?
Update: I succeed flash twrp
Here's how i did it:
- Go to EDL mode using test point
- Flash MIUI 9 (I used version 7.9.7) using MiFlash
- Boot to fastboot and flash twrp
- Boot twrp using fastboot

My Huawei P20 lite (ANE-LX1, hw/eu) is bricked. Please help

I tried installing a custom ROM on my p20 lite, but ended up bricking my phone instead at some point, and now I can't figure out how to restore it to stock EMUI 9.1.
When I boot my phone, it always goes to the TWRP recovery but gets stuck on the TWRP logo. It still accepts adb commands though. Fastboot works too.
The bootloader is unlocked, and there's no FRP lock.
I've tried flashing the images extracted from Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.274(C782E5R1P7T8) Firmware EMUI9.1.0 05015ARN [androidhost.ru].zip UPDATE.APP as shown in this video but my phone is still stuck on the TWRP logo.
I think erecovery has been overwritten because I can't get to it and I get the error seen below in the images (no system error) when I try the power button + vol up + vol down and just vol up + vol down.
Code:
C:\platform tools adb>fastboot devices
9WV4C18706040848 fastboot
C:\platform tools adb>fastboot oem get-build-number
(bootloader) :ANE-LGRP2-OVS 9.1.0.274
OKAY [ 0.000s]
Finished. Total time: 0.016s
Is my phone ****ed or is there still hope?

XRealXX said:
I tried installing a custom ROM on my p20 lite, but ended up bricking my phone instead at some point, and now I can't figure out how to restore it to stock EMUI 9.1.
When I boot my phone, it always goes to the TWRP recovery but gets stuck on the TWRP logo. It still accepts adb commands though. Fastboot works too.
The bootloader is unlocked, and there's no FRP lock.
I've tried flashing the images extracted from Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.274(C782E5R1P7T8) Firmware EMUI9.1.0 05015ARN [androidhost.ru].zip UPDATE.APP as shown in this video but my phone is still stuck on the TWRP logo.
I think erecovery has been overwritten because I can't get to it and I get the error seen below in the images (no system error) when I try the power button + vol up + vol down and just vol up + vol down.
Code:
C:\platform tools adb>fastboot devices
9WV4C18706040848 fastboot
C:\platform tools adb>fastboot oem get-build-number
(bootloader) :ANE-LGRP2-OVS 9.1.0.274
OKAY [ 0.000s]
Finished. Total time: 0.016s
Is my phone ****ed or is there still hope?
Click to expand...
Click to collapse
I don't understand why you installed C782 firmware when you have C432??
XRealXX said:
UPDATE.APP
Click to expand...
Click to collapse
New know-how?
XRealXX said:
I think erecovery has been overwritten
Click to expand...
Click to collapse
I think both Recovery has been overwritten...
First flash stock recovery_ramdisk, then try to flash service ROM via dload, for region C432, of course. And please FOLLOW INSTRUCTIONS on how to install correctly full Stock (can be found in ReleaseDoc folder).
Or, flash TWRP again, enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc." .
Files:
Stock Recovery:
https://mega.nz/file/M0FHlYhb#4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
Stock eRecovery:
https://mega.nz/file/58tnXIKB#KiNi1LXdvZ6hFQAKknULA6fTaOW4-3dstDDdngzBdco
Service ROM for hw-eu

I don't understand why you installed C782 firmware when you have C432??
Click to expand...
Click to collapse
I don't get these version number names... fastboot oem get-build-number command says that the version number is: ANE-LGRP2-OVS 9.1.0.274. How is it C432 then? I don't understand it.
The zip file I downloaded has .274 in it "Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.274(C782E5R1P7T8) Firmware EMUI9.1.0 05015ARN [androidhost.ru].zip". So shouldn't it be the version I need? How do I know that this is actually C782? Sorry, I'm not very experienced with this stuff.
New know-how?
Click to expand...
Click to collapse
What I meant by this is that I extracted the UPDATE.APP file from update_sd.zip. I opened the UPDATE.APP file via the Huawei Update Extractor program and extracted the files shown in this video and flashed those files as shown in the video too: From the UPDATE.APP I extracted: RECOVERY_RAMDIS.img, RECOVERY_RAMDIS.img.header, SYSTEM.img, SYSTEM.img.header.
I then flashed RECOVERY_RAMDIS.img via fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
SYSTEM.img with fastboot flash system SYSTEM.img
Everything went fine, but when I tried to enter the erecovery, it still only went to twrp. When I tried to go to the forcible upgarde mode (power button + vol up + vol down), I got this error message:
Spoiler: Image
I think both Recovery has been overwritten...
First flash stock recovery_ramdisk, then try to flash service ROM via dload, for region C432, of course. And please FOLLOW INSTRUCTIONS on how to install correctly full Stock (can be found in ReleaseDoc folder).
Or, flash TWRP again, enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc." .
Files:
Stock Recovery:
https://mega.nz/file/M0FHlYhb#4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
Stock eRecovery:
https://mega.nz/file/58tnXIKB#KiNi1LXdvZ6hFQAKknULA6fTaOW4-3dstDDdngzBdco
Service ROM for hw-eu
Click to expand...
Click to collapse
Okay, so I tried flashing stock recovery_ramdisk that you linked in your comment this way:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
I copied the dload folder to the root of the SD Card, as instructed in the ReleaseDoc folder.
Held down power button + vol up + vol down, I still got this error screen:
Spoiler: That error screen I showed previously in this comment
I tried flashing the ERECOVERY_RAMDISK-ANE-9.1.img instead:
Code:
fastboot flash recovery_ramdisk ERECOVERY_RAMDISK-ANE-9.1.img
but that didn't help either, and I still got that error screen shown above.
I tried flashing a different TWRP recovery
Code:
fastboot flash recovery_ramdisk twrp.img
before I posted this thread on the forum but my phone still only booted to the twrp that was on it before that gets stuck on the TWRP logo (holding down power button + vol up or just vol up yields the same result).
Spoiler: The stuck TWRP
So, what now? Thank you for your patience.

XRealXX said:
How is it C432 then?
Click to expand...
Click to collapse
It's your info:
"My Huawei P20 lite (ANE-LX1, hw/eu)"
hw/eu = C432 region.
C782 is an unlocked UK version, not a hw/eu. Keep in mind, the only trusted source for downloading service ROMs is the website in my link above.
XRealXX said:
I tried flashing the ERECOVERY_RAMDISK-ANE-9.1.img instead:
Code:
fastboot flash recovery_ramdisk ERECOVERY_RAMDISK-ANE-9.1.img
but that didn't help either, and I still got that error screen shown above.
Click to expand...
Click to collapse
Read carefully:
-Alf- said:
enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc." .
Click to expand...
Click to collapse
As for TWRP, try to install 3.2.1 pretoriano80 or 3.4.0-0-emui9_eR
https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/post-84056933

Do factory reset via fastboot:
fastboot erase userdata

As for TWRP, try to install 3.2.1 pretoriano80 or 3.4.0-0-emui9_eR
https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/post-84056933
Click to expand...
Click to collapse
I tried flashing the two TWRP recoveries you mentioned (3.2.1 pretoriano80 and 3.4.0-0-emui9_eR) via fastboot flash recovery_ramdisk twrp_image_name_here.img but my phone still keeps booting into GAGUGA Edition TWRP.

-Alf- said:
Do factory reset via fastboot:
fastboot erase userdata
Click to expand...
Click to collapse
Okay. I'll try that.

-Alf- said:
Do factory reset via fastboot:
fastboot erase userdata
Click to expand...
Click to collapse
So I tried that and it failed:
Code:
C:\platform tools adb>fastboot erase userdata
< waiting for any device >
Erasing 'userdata' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
C:\platform tools adb>fastboot erase userdata
(bootloader) success to erase cryypt info in oeminfo
Erasing 'userdata' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
C:\platform tools adb>fastboot devices
9WV4C18706040848 fastboot
But now the GAGUGA Edition TWRP works! Thank you!

Now that the GAGUGA TWRP recovery works, what should I do? I don't wanna mess it up again.

XRealXX said:
Now that the GAGUGA TWRP recovery works, what should I do? I don't wanna mess it up again.
Click to expand...
Click to collapse
-Alf- said:
enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc."
Click to expand...
Click to collapse
Btw, the firmware you have downloaded and flashed, is for Single SIM devices.

-Alf- said:
Btw, the firmware you have downloaded and flashed, is for Single SIM devices.
Click to expand...
Click to collapse
Oh... My phone is dual sim.

-Alf- said:
Btw, the firmware you have downloaded and flashed, is for Single SIM devices.
Click to expand...
Click to collapse
Okay, I'll try flashing the erecovery file. Ty

Thanks to you -Alf-, my phone is no longer e-waste! After flashing the eRecovery image in TWRP to eRecovery and rebooting my phone, it automatically started to install the software in my dload folder on my sd card. And it worked. Thank you again!
To recap everything for people in the future who might need this and find it via google or some other search engine, the fix was to run this command in fastboot (it does a factory reset):
Code:
fastboot erase userdata
Then the phone will automatically install the firmware that's in the dload folder in the root of your sd card (the firmware I used is the Service ROM -Alf- linked Alternatively, you can try installing the latest firmware via WiFi in eRecovery.

Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled.