Develop Bugs

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

Stuck in bootloader - no recovery - no system

Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
fastboot boot twrp.img
creating boot image...
creating boot image - 13133824 bytes
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
FAILED (remote: image verification failed)
Click to expand...
Click to collapse
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?

Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Have you tried flashing stock?

Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."

xrad said:
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
Click to expand...
Click to collapse
No, meanwhile I returned it to google and got a new one. But thank you for help!

Phone is bootloader unlocked, but get a fastboot error trying to flash

So I managed to get the phone bootloader unlocked by following one of the guides, cross-flashed a ULM firmware, then followed the EDL method guide and this time it worked. It wouldn't work before cross-flashing the ULM firmware for some reason.
However, i cannot flash the rooted magisk boot image, i get this error in command prompt when i run the command "fastboot flash boot_a magisk_patched.img": fastboot: error: cannot get boot partition size. I also tried "fastboot flash boot magisk_patched.img", but i get the same error.
I'm stuck here, basically one step away from root. What is going wrong? How do i fix the error "cannot get boot partition size" to flash the pre-rooted image?

Load the boot patched via Qfil

Question Need help, Can't figure out how to change my ROM

Exactly a year ago I bought Poco F3, unlocked the bootloader and installed ArrowOS. Now I'm trying to figure out how to change my ROM and I can't really find any answers. I have the ArrowOS recovery and it's useless, I can't install another recovery with it. My fastboot also seems to be broken(?), it has a different logo and it's detected on my computer when I do (fastboot devices) but other than that it gives me a bunch of errors
I would like to at least know how to change the recovery. Is it possible that my bootloader got locked? One last thing, when I installed ArrowOS I used TWRP and updated it using OTA updates, now TWRP is gone.
Please help me

You need fastboot for TWRP.

It could not have gotten locked, no.

Arealhooman said:
It could not have gotten locked, no.
Click to expand...
Click to collapse
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?

Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.

Arealhooman said:
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Click to expand...
Click to collapse
I don't have any oem unlock option in ArrowOS and I never locked anything wtf, I just used it as a normal phone and only did OTA updates + sometimes FW updates when required
Is there anyway to fix it?

ADB & Fastboot Binaries: https://developer.android.com/studio/releases/platform-tools
OrangeFox Recovery (recommended): https://orangefox.download/device/alioth
Install the Recovery ZIP by either ADB Sideload in ArrowOS Recovery
or you can extract the "recovery.img" and fastboot boot it ("fastboot boot recovery.img") and select "Install current Recovery"
Then you simply flash the ROM.zip (select "Reflash Recovery after ROM Flash") -> Reboot Recovery -> Format Data
The OTA Update has replaced your TWRP with ArrowOS Recovery, because ROM Updates replace the boot-partition (along with other system related partitions). The boot-partition contains the recovery-environment.
Only install Custom Recoveries from inside the Recovery, because Fastboot can only replace partitions entirely (and boot-partitions contains both bootloader & recovery)
The bootloader of the Poco F3 cannot (or shouldn't) be locked on Custom Software.

gobertel said:
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Click to expand...
Click to collapse
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.

Also, what's the problem with ArrowOS anyway? We've ArrowOS MiPa, it's a good and reliable ROM.

cyanGalaxy said:
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Click to expand...
Click to collapse
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general

Thank you for helping me out by the way

gobertel said:
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Click to expand...
Click to collapse
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.

Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com

cyanGalaxy said:
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot boot recovery.img
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Another thing to add is I still I get the unlock symbol when booting up the phone, I dont know if that makes a difference

cyanGalaxy said:
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I'm using the exact one you gave me and I will try it

gobertel said:
Yes I'm using the exact one you gave me and I will try it
Click to expand...
Click to collapse
Yup try it.
Else, here I have the vendor_boot.img & boot.img from the latest ArrowOS MiPa (February). More up-to-date than the SourceForge links.
Either the 2 files from ArrowOS v12, or the latest v13 ones that I've uploaded here, should definitely work.
Also try rebooting Fastboot Mode.

XDA doesn't let me upload the boot.img ඞ

cyanGalaxy said:
XDA doesn't let me upload the boot.img ඞ
Click to expand...
Click to collapse
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything

gobertel said:
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
Click to expand...
Click to collapse
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.

cyanGalaxy said:
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
Click to expand...
Click to collapse
IT WORKED. Thank you so much, it was a driver issue but the exact version you gave me didn't work, I had to find another one

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.