p20 lite bootloop

Search This thread

SignoreTNT

Member
Feb 6, 2021
20
0
C:\Users\Davide\Desktop\Userdata ecc>fastboot flash userdata USERDATA.img
Sending sparse 'userdata' 1/2 (458754 KB) OKAY [ 16.907s]
Writing 'userdata' FAILED (remote: 'failed to erase partition when sparse img flash')
fastboot: error: Command failed

C:\Users\Davide\Desktop\Userdata ecc>fastboot flash userdata USERDATA.img
Sending 'userdata' (32768 KB) OKAY [ 1.201s]
Writing 'userdata' FAILED (remote: 'failed to erase partition when sparse img flash')
fastboot: error: Command failed

C:\Users\Davide\Desktop\Userdata ecc>fastboot flash kernel KERNEL.img
Sending 'kernel' (24576 KB) OKAY [ 0.905s]
Writing 'kernel' FAILED (remote: 'flash write prim vrl failure')
fastboot: error: Command failed

C:\Users\Davide\Desktop\Userdata ecc>fastboot flash cust CUST.img
Sending 'cust' (131218 KB) OKAY [ 4.785s]
Writing 'cust'


(i extracted those files using huawei update extractor)
 

-Alf-

Senior Member
C:\Users\Davide\Desktop\Userdata ecc>fastboot flash userdata USERDATA.img
Sending sparse 'userdata' 1/2 (458754 KB) OKAY [ 16.907s]
Writing 'userdata' FAILED (remote: 'failed to erase partition when sparse img flash')
fastboot: error: Command failed

C:\Users\Davide\Desktop\Userdata ecc>fastboot flash userdata USERDATA.img
Sending 'userdata' (32768 KB) OKAY [ 1.201s]
Writing 'userdata' FAILED (remote: 'failed to erase partition when sparse img flash')
fastboot: error: Command failed

C:\Users\Davide\Desktop\Userdata ecc>fastboot flash kernel KERNEL.img
Sending 'kernel' (24576 KB) OKAY [ 0.905s]
Writing 'kernel' FAILED (remote: 'flash write prim vrl failure')
fastboot: error: Command failed

C:\Users\Davide\Desktop\Userdata ecc>fastboot flash cust CUST.img
Sending 'cust' (131218 KB) OKAY [ 4.785s]
Writing 'cust'


(i extracted those files using huawei update extractor)
Can you flash system.img?
 

SignoreTNT

Member
Feb 6, 2021
20
0
I want to apologize for asking such a stupid question, but I can't read your mind. Have a nice day.
I think there's been a misunderstanding, sorry for that.
I was trying to say that it's stuck at "Writing system". I cannot send the cmd log because im not at home right now, for now i just left it running.
 

-Alf-

Senior Member
I think there's been a misunderstanding, sorry for that.
I was trying to say that it's stuck at "Writing system". I cannot send the cmd log because im not at home right now, for now i just left it running.
Run
fastboot -w
fastboot erase system
and flash only the following partitions:
fastboot flash cust CUST.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash system SYSTEM.img
fastboot flash vbmeta VBMETA.img
(thanks Mr. @Pi0312 )
- fastboot reboot
 

SignoreTNT

Member
Feb 6, 2021
20
0
Run
fastboot -w
fastboot erase system
and flash only the following partitions:
fastboot flash cust CUST.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash system SYSTEM.img
fastboot flash vbmeta VBMETA.img
(thanks Mr. @Pi0312 )
- fastboot reboot
>fastboot -w
Finished. Total time: 0.031s

C:\Users\Davide>fastboot erase system
Erasing 'system' FAILED (remote: 'failed to erase partition')
fastboot: error: Command failed

it always fails to erase system (same goes for userdata and cache)

p.s. could this be due to the FRP lock instead of an hw failure?
 

SignoreTNT

Member
Feb 6, 2021
20
0
No bro :

So in the end it's my fault :p. Okay, good luck!
Im not trying to put at fault in any way, you have been super helpful about this whole thing and i thank you for that. Im not an expert user so i thought that unlocking the bootloader would have allowed me to load a working firmware, or at least allow me to remove the FRP lock. Anyways im really sorry if i wasted your time :(
 

-Alf-

Senior Member
Im not trying to put at fault in any way, you have been super helpful about this whole thing and i thank you for that. Im not an expert user so i thought that unlocking the bootloader would have allowed me to load a working firmware, or at least allow me to remove the FRP lock. Anyways im really sorry if i wasted your time :(
No problem. I was thinking about frp, but I didn't mean to offend you by asking if you have frp unlock...:)
 

wax_77

Member
Nov 21, 2011
16
3
Run
fastboot -w
fastboot erase system
and flash only the following partitions:
fastboot flash cust CUST.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash system SYSTEM.img
fastboot flash vbmeta VBMETA.img
(thanks Mr. @Pi0312 )
- fastboot reboot

hello,
following all step i can't unbrick my device

my infos:

fastboot oem get-build-number
(bootloader) :ANE-LGRP2-OVS 9.1.0.132
fastboot oem get-product-model
(bootloader) ANE-LX1
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: Read oeminfo failed!)
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 8.0.0.112(C432)

i have also try to flash userdata.img but no way

in erecovery i have twrp but stuck on logo (so i cannot use)

could you help me?
 

-Alf-

Senior Member
hello,
following all step i can't unbrick my device

my infos:

fastboot oem get-build-number
(bootloader) :ANE-LGRP2-OVS 9.1.0.132
fastboot oem get-product-model
(bootloader) ANE-LX1
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: Read oeminfo failed!)
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 8.0.0.112(C432)

i have also try to flash userdata.img but no way

in erecovery i have twrp but stuck on logo (so i cannot use)

could you help me?
https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538623

Or, flash TWRP, install stock eRecovery and try to update the phone via eRecovery & wi-fi.
 

Top Liked Posts