Database Info

Failed to erase partition...getting desperate here

Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.

Try using mfastboot:
https://www.androidfilehost.com/?fid=23578570567719065​
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?

lost101 said:
Try using mfastboot:
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?
Click to expand...
Click to collapse
Yes sir it was bought in Saudi (asia) and is dual sim. The box also states that it is xt1033.
I have tried what you have suggested but the error still remains.
C:\Users\...\Desktop\mfastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 14.955s
C:\Users\...\Desktop\mfastboot>mfastboot erase userdata[/U]
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.953s
If it is of any help, the screen says that it has 41.18 bootloader, I don't exactly know what this information is for.

Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

lost101 said:
Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Click to expand...
Click to collapse
I already tried sir along with the Brazilian firmware and both returned the same error. The same partition error,
I get stuck right at the first command "mfastboot flash partition gpt.bin", it says the the phone couldn't erase the partition. I'm starting to hate motorola right now
The money I saved just to buy this phone and I only got to use it for 1 month.
I understand that my partition is likely messed up or is corrupted even though I did nothing with my phone except upgrading it to lollilop (biggest mistake ever), what I don't understand is there aren't anyone else here in the forum who seem to have the same problem as mine, its like I am the only who has this kind of error so there are no threads at all discussing on how to solve this.

You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

lost101 said:
You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 5.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.424s

titan015 said:
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
Click to expand...
Click to collapse
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​

lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"

Try another recovery.img just in case that one was a bad download.

titan015 said:
Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.
Click to expand...
Click to collapse
I have the same problem, do you managed to fix it?

kesy85 said:
I have the same problem, do you managed to fix it?
Click to expand...
Click to collapse
no. i've tried just about everything, didn't managed to fix it

hi
i have the same problem too bro, im from the philippines too..
have u fixed it yet?

no fix?
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.

Same for me, BUMP
hand_solo said:
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.
Click to expand...
Click to collapse
Anyone managed to fix this?

The best I've found...
hand_solo said:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
Click to expand...
Click to collapse
...is this:
Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
Fastboot Error: preflash validation failed
Try your original (or last flashed) firmware.
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
P.s.: I have the same problem.

titan015 said:
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"
Click to expand...
Click to collapse
lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
For me the error is:
Code:
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
target reported max download size of 536870912 bytes
[COLOR="SeaGreen"]sending 'recovery' (9372 KB)...
OKAY [ 0.377s]
[/COLOR]writing 'recovery'...
[COLOR="Red"][B](bootloader) Permission denied
FAILED (remote failure)[/B][/COLOR]
finished. total time: 0.408s
Same thing when I try to boot instead of Flashing
Code:
fastboot boot twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
[COLOR="SeaGreen"]downloading 'boot.img'...
OKAY [ 0.347s][/COLOR]
booting...
[B][COLOR="Red"]FAILED (remote failure)
[/COLOR][/B]finished. total time: 0.354s

An unlocked Bootloader is required to flash (or boot) a custom recovery.

lost101 said:
An unlocked Bootloader is required to flash (or boot) a custom recovery.
Click to expand...
Click to collapse
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.

Der_K said:
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.
Click to expand...
Click to collapse
Please try to explain more clearly. Don't use the term ROM, if you are talking about a factory firmware image - in other words - sparsechunk files.
Can you flash the stock recovery img included in the factory firmware image?

XT1032 Softbrick?

Hey guys,
i got a XT1032 from a friend and i try to repair it. First, i don't now which android version was installed! The only thing i can do with that device is booting into the bootloader (it's 41.13). Flashing roms, recovery or upgrading the bootloader didn't work for me. I tried many tools but nothing had a positiv effect for me. Please help me find a way, I'm sure it's possible.

First of all I'd recommend using BUT by @Xyzko to upgrade your bootloader to 41.1A
Then you should flash TWRP by using "fastboot flash recovery 'recoveryname'.img
If TWRP boots you can try to wipe all the data and sideload a ROM of your choice. Otherwise boot into bootloader and download your Factory Firmware image and then flash it with @lost101 's Mfastboot with the following commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash boot boot.img

Ju43 said:
First of all I'd recommend using BUT by @Xyzko to upgrade your bootloader to 41.1A
Then you should flash TWRP by using "fastboot flash recovery 'recoveryname'.img
If TWRP boots you can try to wipe all the data and sideload a ROM of your choice. Otherwise boot into bootloader and download your Factory Firmware image and then flash it with @lost101 's Mfastboot with the following commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash boot boot.img
Click to expand...
Click to collapse
I tried the tool by @Xyzko but it won't work for me. If I select c for 41.1A the software simple doing nothing. If i try 41.19 or 41.18 it starts to write the motoboot but after my device reboot nothing has changed (i ran it as admin).

Is your bootloader unlocked?

Yes it is (Status Code:3)!

41.13 is a pre lollipop bootloader so I would advise u to reflash a custom ROM based on kitkat.

Andus1988 said:
41.13 is a pre lollipop bootloader so I would advise u to reflash a custom ROM based on kitkat.
Click to expand...
Click to collapse
well that is that problem. I can't flash anything.....

But u can access (custom) recovery?

no. i only can access the bootloader (Fastboot Flash mode)

Then tell me the commands u used for flashing a custom recovery! And which custom recovery did u choose?

flashing recovery with fastboot and mfastboot:
fastboot flash recovery "recover.img" (without quotes)
mfastboot flash recovery "recover.img" (without quotes)
i took the recovery image from Cyanogenmod and renamed it.
Output:
C:\platform-tools>mfastboot flash recovery recover.img
target max-sparse-size: 256MB
sending 'recovery' (8812 KB)...
OKAY [ 5.266s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.282s
Device Output:
Mismachted partition size (recovery)

iToaster said:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.282s
Device Output:
Mismachted partition size (recovery)
Click to expand...
Click to collapse
That's the reason. I guess @lost101 or @_that could help u!

umm... no idea. Try "fastboot boot recover.img" to see if you can at least start the recovery. If it does start, run "adb shell cat /proc/partitions" to see if your partitions are there.

_that said:
umm... no idea. Try "fastboot boot recover.img" to see if you can at least start the recovery. If it does start, run "adb shell cat /proc/partitions" to see if your partitions are there.
Click to expand...
Click to collapse
Output:
C:\platform-tools>mfastboot boot recover.img
downloading 'boot.img'...
OKAY [ 5.290s]
booting...
FAILED (remote failure)
finished. total time: 15.326s
On Device:
incomplete boot image for booting

Try a different, known working recovery image.

Use TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

Tried both version for your link, with the same result as with the img I used.....

iToaster said:
Tried both version for your link, with the same result as with the img I used.....
Click to expand...
Click to collapse
What command are you using? check the name of the .img file.

fastboot flash recovery twrp-2.8.7.0-falcon_STOCK.img as it is mentioned in the post

@iToaster - It's starting to look like a case of corrupt emmc. Partitions are read only. There is no solution.

Help can only access fastboot mode and locked bootloader and stuck

HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help

getvar:all FAILED (remote: Command not allowed) it says command not allowed even in that command. and its bootloader lock is on any workaround so i can install update.zip without cmd says not enought space? or some workaround or command in fastboot to bootloader unlock with fastboot or any other idees?

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36998 KB)...
OKAY [ 0.786s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.786s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ALWAYS GETTING FAILED (remote: Command not allowed)

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt

i think YOU ARE DOOMED??
only thing you can do is getting it back to the service center..gud luck buddy...

goran85 said:
HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help
Click to expand...
Click to collapse
same problem,, how to solve it??

writing 'recovery'...
FAILED (remote: Command not allowed)
sometime happenned to me and when installed the correct drivers in windows installed ok

Huawei Mate 9 stuck on critical data loss screen!!

The device is not oem unlocked, and it only boots to the screen mentioned, when connected to the PC it appears as a CD unit, with no options at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When trying to use ADB or FastBoot won't work, also tried to use the Huawei tool and it doesn´t work.
Any ideas on what to do, I really want to obtain all my photos and data back.
Do I have to open the device or is it completely dead?

Could it boot directly to Fastboot - switch off, connect to PC, press and keep pressing Vol- , boot?
And to eRecovery - switch off, connect to charger, press and keep pressing Vol+, boot?
Can you explain which firmware you had (like MHA-L29c432 9.1.0.255(C432E7R1P8) or so)?
Was the Bootloader unlocked - and then, did you have TWRP, Magisk, custom ROM?
What were you doing last (maybe flashing something and what) when it got bricked

zgfg said:
Could it boot directly to Fastboot - switch off, connect to PC, press and keep pressing Vol- , boot?
And to eRecovery - switch off, connect to charger, press and keep pressing Vol+, boot?
Can you explain which firmware you had (like MHA-L29c432 9.1.0.255(C432E7R1P8) or so)?
Was the Bootloader unlocked - and then, did you have TWRP, Magisk, custom ROM?
What were you doing last (maybe flashing something and what) when it got bricked
Click to expand...
Click to collapse
As said on the post the phone was never bootloader unlocked, neither was it changed since i got it. An update came by and when i pressed accept, after 5 min of waititng thats the screen that the phone turns on to.

D.FrostIce said:
As said on the post the phone was never bootloader unlocked, neither was it changed since i got it. An update came by and when i pressed accept, after 5 min of waititng thats the screen that the phone turns on to.
Click to expand...
Click to collapse
Ok, but still what was the firmware you had (and update coming) - since no BL code, you can try to fix it only by DLOAD, and for DLOAD it is important to know what was the firmware (to find and use the same, at least same cust and EMUI version 8, 9 or 9.1)

zgfg said:
Ok, but still what was the firmware you had (and update coming) - since no BL code, you can try to fix it only by DLOAD, and for DLOAD it is important to know what was the firmware (to find and use the same, at least same cust and EMUI version 8, 9 or 9.1)
Click to expand...
Click to collapse
But there is no option at all to recover the data on the device right?

D.FrostIce said:
But there is no option at all to recover the data on the device right?
Click to expand...
Click to collapse
Not, because Internal memory is encrypted and only system can access - you must boot to system.
Try going to Service shop, what they can do
Asked you to try booting to eRecovery, it has an option to (re)Install latest firmware (without Factory reset if you don't force)
TestPoints method should fix the brick, but it would erase everything

zgfg said:
Not, because Internal memory is encrypted and only system can access - you must boot to system.
Try going to Service shop, what they can do
Asked you to try booting to eRecovery, it has an option to (re)Install latest firmware (without Factory reset if you don't force)
TestPoints method should fix the brick, but it would erase everything
Click to expand...
Click to collapse
After several attempts I am now able to enter Fastboot&Recovery mode, what should i do from here?

D.FrostIce said:
After several attempts I am now able to enter Fastboot&Recovery mode, what should i do from here?
Click to expand...
Click to collapse
From eRecovery (this is not Recovery, instructions were above), take Install latest firmware and recovery
If ain't work, read from Fastboot:
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry

same boat here,
MHA-L29c432 9.1.0.255
no oem unlock, got up this morning, phone exactly as described above..
erecovery fails, "in chinese", cannot format data...
below fastboot:
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.008s]
finished. total time: 0.010s
C:\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) MHA-L29
OKAY [ 0.035s]
finished. total time: 0.038s
C:\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :MHA-L29 9.1.0.252(C432E7R1P8)
OKAY [ 0.041s]
finished. total time: 0.047s
C:\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29 9.0.1.158(C432E6R1P8)
OKAY [ 0.042s]
finished. total time: 0.046s
C:\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.035s

In order to try some recovery methods "multtitool for huawei" , tried to use my old, never used unlock code, in order to unlock bootloader, in hope of some progress..
C:\Minimal ADB and Fastboot>fastboot oem unlock QXRFBADKDT677FUE
...
FAILED (status malformed (1 bytes))
finished. total time: 7.644s
C:\Minimal ADB and Fastboot>
it actually shows "phone unlocked":
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.006s
..but on reboot to next fastboot it does not stick, and I cannot flash any of the system images, or recovery.
Example:
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
Finished. Total time: 2.686s
it behaves very strangely according to me.
other than throwing it in the bin, does anyone have any idea, in order to recover this brick?
or is it time to move on..?

gjergji1 said:
In order to try some recovery methods "multtitool for huawei" , tried to use my old, never used unlock code, in order to unlock bootloader, in hope of some progress..
C:\Minimal ADB and Fastboot>fastboot oem unlock QXRFBADKDT677FUE
...
FAILED (status malformed (1 bytes))
finished. total time: 7.644s
C:\Minimal ADB and Fastboot>
it actually shows "phone unlocked":
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.006s
..but on reboot to next fastboot it does not stick, and I cannot flash any of the system images, or recovery.
Example:
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
Finished. Total time: 2.686s
it behaves very strangely according to me.
other than throwing it in the bin, does anyone have any idea, in order to recover this brick?
or is it time to move on..?
Click to expand...
Click to collapse
When you successfully unlock (or relock), it notes you that it will reboot and perform Factory reset - it didn't?
Anyway, in Fastboot screen, at the bottom, do you read in RED Phone (=Bootloader) unlocked and FRP unlocked.
Only then it will allow you to flash
If FRP (=OEM) is locked (GREEN), it will not allow you to unlock Bootloader

Phone confirmed dead. Very dissapointed in Huawei.
Moving on..
Purchasing a oneplus 7t...

Need fast help! Unbrick

I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....

@Peterrrrr said:
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
Click to expand...
Click to collapse
I have never tried msmtool, but it sounds like a driver issue. Maybe take a closer look at their instructions
You can try these fastboot flashable stock roms.

You have few options to solve your issue. Now you are in slot B. You can change switch partition to A with fastboot. Try use: fastboot --set-active=a. It will switch to partition A and then try to boot/flash recovery. Also you have try to use fastboot roms with flashall.bat. There are few availaible in forum.
If you would like to use MSM you have to connect phone in proper mode to PC. Power off and hold Vol+ then connect. Also try to install latest Qualcomm drivers.

Msm tool
Download and use msm tool