Database Info

Huawei Honor 6 H60-L12 bricked

Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos

janos666 said:
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
Click to expand...
Click to collapse
Instead of using the honor multi tool, why don't you use the Android SDK platform tools and connect to your phone through adb. You can solve any problem using that. You have to do everything manually but it works and never disappoints as long as you can enter fastboot mode.
Download android SDK and install it. Run the program and only choose platform tools to download. You don't need anything else
Download the latest firmware for your phone and unzip it to get dload folder which will have an update.app in it.
Download Huawei update extractor and open update.app in it.
Extract recovery, boot, Cust and system images from update.app and save them to the platform tools folder.
Flash them using adb and then do a forced update.
Will work wonders. If you need any help or need more info, please let me know.

Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos

janos666 said:
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
Click to expand...
Click to collapse
My expertise are quite limited but may be, just may be (wishful thinking), you can to flash the twrp recovery specific for your phone. Boot into that and flash a custom ROM from there.
It may not work as I guess, boot.img is needed before entering recovery but give it a try. It never hurts.

Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
Click to expand...
Click to collapse
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos

janos666 said:
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
Click to expand...
Click to collapse
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.

Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04

janos666 said:
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
Click to expand...
Click to collapse
Well, I have mentioned DigiGoon in the previous reply. May be he can help a bit.

@janos666
You can always put your desired boot.img in a flashable zip, and flash it via TWRP recovery.

Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery

janos666 said:
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
Click to expand...
Click to collapse
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.

muradulislam said:
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Click to expand...
Click to collapse
zinko_pt said:
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
Click to expand...
Click to collapse
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
Sure. I would go from there as I sometimes mixed boot.img from LP or MM and always got bootloop. I would stick to IMG files from last installed ROM.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Hi DigiGoon !
Sorry, which one is the flash transition package?
Which parts to flash from it?
Which is notification LED? I can see only one red LED blinking sometimes, but only when battery is low.

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Isn't there an option to flash all img files from fastboot?
P.S. I just got new info from the guy who flashed it first time. He says he tried to write version:
H60-L02-L12_emui3.1_android5.1_c00B535

Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me

janos666 said:
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
Click to expand...
Click to collapse
Some threads mention of locking and unlocking your device again. Give that a try. May help...

muradulislam said:
Some threads mention of locking and unlocking your device again. Give that a try. May help...
Click to expand...
Click to collapse
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.

janos666 said:
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
Click to expand...
Click to collapse
The info you are missing is device id, another user got his device id using Huawei hacker toolkit v 1.4, his model was h60-L02. May be you can give it a try.
You have to lock it before trying to unlock again.
Fastboot OEM lock xxxxxxxxxxxxxxxx...

Help!!! Is my Honor 8 bricked??

I'm in a really bad position right now. I flashed TWRP on my phone to flash stock recovery on my phone. I attempted to wipe everything before I flashed something, but it gave me errors that it failed to mount Cust, Product, Vendor, and Device. I was able to get rid of the Cust error, but the other three remained. Now my phone does not boot into anything. I tried flashing stock and it did nothing.
I just tried following this: https://forum.xda-developers.com/showpost.php?p=70158202&postcount=5
I was able to extract everything, but when I tried to unbrick the phone I got some errors.
RNV0216811011914 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15490 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.378s]
finished. total time: 0.720s
target reported max download size of 471859200 bytes
sending 'cust' (258509 KB)...
OKAY [ 5.576s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.597s
target reported max download size of 471859200 bytes
sending 'recovery' (37044 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 0.878s]
finished. total time: 1.685s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (433185 KB)...
OKAY [ 10.174s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.575s
As you can see, it failed to both write to cust and system. Due to this I still cannot boot into anything other than TWRP and Fastboot mode. Not the operating system (EMUI), not Huawei eRecovery.
Please help me...is my phone bricked for good, or can I fix this?

Quick update: I am able to reach Huawei eRecovery. However, if I try to download the latest version and recovery, it ultimately ends up at "Getting package info failed". Maybe I can do something with eRecovery?
Just to recap: I can access fastboot mode, TWRP, and eRecovery. I can not access the OS.

cosmopath said:
Quick update: I am able to reach Huawei eRecovery. However, if I try to download the latest version and recovery, it ultimately ends up at "Getting package info failed". Maybe I can do something with eRecovery?
Just to recap: I can access fastboot mode, TWRP, and eRecovery. I can not access the OS.
Click to expand...
Click to collapse
In twrp, select storage, how much is it?,internal not sdcard?

faizalotai said:
In twrp, select storage, how much is it?,internal not sdcard?
Click to expand...
Click to collapse
It shows 24104MB. I have the 32GB model.

cosmopath said:
It shows 24104MB. I have the 32GB model.
Click to expand...
Click to collapse
What about data partition, what type does it show..f2fs or ext

faizalotai said:
What about data partition, what type does it show..f2fs or ext
Click to expand...
Click to collapse
I'll just share all of the stats about it:
Mount Point: /data
File system: ext4 (I believe this is what you're looking for)
Present: Yes
Size: 24148MB
Free: 24104MB
Removable: No
Used: 0MB
Backup Size: 0MB

cosmopath said:
I'll just share all of the stats about it:
Mount Point: /data
File system: ext4 (I believe this is what you're looking for)
Present: Yes
Size: 24148MB
Free: 24104MB
Removable: No
Used: 0MB
Backup Size: 0MB
Click to expand...
Click to collapse
So far nothing wrong with your storage,
What software ver are you on with before this happened

faizalotai said:
So far nothing wrong with your storage,
What software ver are you on with before this happened
Click to expand...
Click to collapse
I was on the official beta build of EMUI 5.0, but I flashed it. I was trying to go back to stock so I could get the official update now that it rolled out in my region.

cosmopath said:
I was on the official beta build of EMUI 5.0, but I flashed it. I was trying to go back to stock so I could get the official update now that it rolled out in my region.
Click to expand...
Click to collapse
In beta, you use what ver of twrp?

faizalotai said:
In beta, you use what ver of twrp?
Click to expand...
Click to collapse
I'm using 3.0.2-0, the build from this post in particular: https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
I tried a couple other builds which didn't work.

cosmopath said:
I'm using 3.0.2-0, the build from this post in particular: https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
I tried a couple other builds which didn't work.
Click to expand...
Click to collapse
So youre using nougat, and you flash MM images??
Try this, find your rollback package, donload and put updated.app in dload folder(create new one in sdcard)
Let it updates with 3 button pushed.
Find your full firmware package, download it than you need to replace the updates.app in dload folder with full firmware one.
Let it updates with 3 buttons pushed also.
You'll loose twrp and bootloader locked again

I am also faced same problem. Just follow my steps
1.grab stock recovery.img form stock firmware by extracting update.app in Huawei update extrator .
2.flash it in fast boot.
3.switch off ur device.
4. Copy stock update.app to SD/dload.
5.then force update by all three buttons
Boom it works for me :good:

faizalotai said:
So youre using nougat, and you flash MM images??
Try this, find your rollback package, donload and put updated.app in dload folder(create new one in sdcard)
Let it updates with 3 button pushed.
Find your full firmware package, download it than you need to replace the updates.app in dload folder with full firmware one.
Let it updates with 3 buttons pushed also.
You'll loose twrp and bootloader locked again
Click to expand...
Click to collapse
VenuGopalu said:
I am also faced same problem. Just follow my steps
1.grab stock recovery.img form stock firmware by extracting update.app in Huawei update extrator .
2.flash it in fast boot.
3.switch off ur device.
4. Copy stock update.app to SD/dload.
5.then force update by all three buttons
Boom it works for me :good:
Click to expand...
Click to collapse
It worked!!! To be specific, I followed faizalotai's guide because I thought that updating the rollback package would fix it, but VenuGopalu's guide was very similar. I'm now running EMUI 4.1 without any problems. Apparently I don't have the update to EMUI 5 yet, but I'm sure I'll be getting that soon. Thank you so much, guys!

cosmopath said:
It worked!!! To be specific, I followed faizalotai's guide because I thought that updating the rollback package would fix it, but VenuGopalu's guide was very similar. I'm now running EMUI 4.1 without any problems. Apparently I don't have the update to EMUI 5 yet, but I'm sure I'll be getting that soon. Thank you so much, guys!
Click to expand...
Click to collapse

When I am tried install twrp by adb in fastboot mode isee infromation" target reported max download size of 471859200 bytes" and failed

Mysia said:
When I am tried install twrp by adb in fastboot mode isee infromation" target reported max download size of 471859200 bytes" and failed
Click to expand...
Click to collapse
Make sure your device is unlocked bootloader

i (think I) killed my Honor 8

I rooted my Honor 8 yesterday and it was working fine, I went to install BusyBox, and accidentally installed SuperSU, and now I couldn't pass the SafetyNet checks, even with Magisk installed. I used TWRP to wipe my device, and went to install the backup. Wouldn't you know, the backup I made was no good.
I'm able to get into TWRP and eRecovery, but since I unlocked the bootloader (and no longer have access to the code), i can't use eRecovery.
anyone want to earn a nice hug for helping me figure this out?

I've been trying to flash the BOOT, CUST, RECOVERY and SYSTEM IMG files I extracted from Update.APP. The first 3 flashed fine, but System is too large.
Microsoft Windows [Version 10.0.16257.1]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 10.731s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.778s

aNGERY said:
I've been trying to flash the BOOT, CUST, RECOVERY and SYSTEM IMG files I extracted from Update.APP. The first 3 flashed fine, but System is too large.
Microsoft Windows [Version 10.0.16257.1]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 10.731s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.778s
Click to expand...
Click to collapse
i too got this error.
flash the images by unbrick option in huawei multi tool it works

venugopalu007 said:
i too got this error.
flash the images by unbrick option in huawei multi tool it works
Click to expand...
Click to collapse
i struggle with russian. any idea where i can find the english build?

aNGERY said:
i struggle with russian. any idea where i can find the english build?
Click to expand...
Click to collapse
can you provide the information of build number and which build you want?

i found an english build, here's what it's doing:

what would be sick, is if someone could share a TWRP backup of their device.

aNGERY said:
what would be sick, is if someone could share a TWRP backup of their device.
Click to expand...
Click to collapse
Bro in which emui are you on, if emui 5 just do a roll back using rollback packages.

venugopalu007 said:
Bro in which emui are you on, if emui 5 just do a roll back using rollback packages.
Click to expand...
Click to collapse
I am pretty positive I no long have an OS installed on this device, TWRP is saying I have 0mb in the system partition.
However, the phone WAS on EMUI 5.

venugopalu007 said:
Bro in which emui are you on, if emui 5 just do a roll back using rollback packages.
Click to expand...
Click to collapse
https://club.hihonor.com/in/eyestow...-marshmallow-this-is-what-you-should-do.11907
that's the guide i found.
Now I'm getting:
"Software install failed! Incompatibility with current version. Please download the correct update package"

aNGERY said:
https://club.hihonor.com/in/eyestow...-marshmallow-this-is-what-you-should-do.11907
that's the guide i found.
Now I'm getting:
"Software install failed! Incompatibility with current version. Please download the correct update package"
Click to expand...
Click to collapse
Bro you cannot install another build roll back...
Tell me your build number ...frd-L09or frdl19or...??

FRD-L04

venugopalu007 said:
Bro you cannot install another build roll back...
Tell me your build number ...frd-L09or frdl19or...??
Click to expand...
Click to collapse
FRD-L04

aNGERY said:
FRD-L04
Click to expand...
Click to collapse
Download this http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098 extract and copy update.app to dload folder of sd card now make sure your device is off, now press and all 3 buttons after vibration release the power ,it will update successful.
And now download this ad again copy to sd card dload folder (replace it ) http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
Do the same power and hold buttons......
And after successful you device will works.
If it stucks at blue screen just do a factory reset once in recovery mode.

venugopalu007 said:
Bro you cannot install another build roll back...
Tell me your build number ...frd-L09or frdl19or...??
Click to expand...
Click to collapse
venugopalu007 said:
Download this http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098 extract and copy update.app to dload folder of sd card now make sure your device is off, now press and all 3 buttons after vibration release the power ,it will update successful.
And now download this ad again copy to sd card dload folder (replace it ) http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
Do the same power and hold buttons......
And after successful you device will works.
If it stucks at blue screen just do a factory reset once in recovery mode.
Click to expand...
Click to collapse
i love you <3
will i be able to update to Nougat pretty easily?

aNGERY said:
i love you <3
Click to expand...
Click to collapse
Report me after it works.

venugopalu007 said:
Report me after it works.
Click to expand...
Click to collapse
it seems to be hung up at 5 percent for a few minutes now, is that pretty common? how long does it take.

aNGERY said:
it seems to be hung up at 5 percent for a few minutes now, is that pretty common? how long does it take.
Click to expand...
Click to collapse
In which zip ? First or second?

venugopalu007 said:
In which zip ? First or second?
Click to expand...
Click to collapse
i actually reset it in the middle and it worked fine! thanks. updating to Nougat now

aNGERY said:
i actually reset it in the middle and it worked fine! thanks. updating to Nougat now
Click to expand...
Click to collapse
Just check if a system app is missing (like NFC or keyboard) as it did happen to many users

Huawei Mate 9 command not allowed but the bootloader is unlock

Hey guys i got a new problem with my phone. I did a factory reset and later i unlocked the bootlader again but when i tried to do something with adb said ''Command not allowed'' later when i tried to install twrp said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (8728 KB)...
OKAY [ 0.252s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.266s

Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo

ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I'm loving you so much right now

ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo

CommunalH said:
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo
Click to expand...
Click to collapse
Could you send me the recovery you're flashing?

ante0 said:
Could you send me the recovery you're flashing?
Click to expand...
Click to collapse
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3

CommunalH said:
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3
Click to expand...
Click to collapse
Good, that's the correct one
Can you boot to system?

ante0 said:
Good, that's the correct one
Can you boot to system?
Click to expand...
Click to collapse
I don't hace OS right now, options neither

CommunalH said:
I don't hace OS right now, options neither
Click to expand...
Click to collapse
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.

ante0 said:
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.
Click to expand...
Click to collapse
I don't know here to find my build number without OS, i know it's MHA-L09B

huawei mate 8 bricked rooting

hi guys hi tried to root my mate 8 but something went wrong and it goes in bootloop. now , there are no roms , i tried to flash stock rom unsuccessfully (dload metod it fail, from twrp error 7, hi suite not working, erecovery i can enter but not reset)
i tired to flas boot,system,cust and recovery img but these are the problems
QHC0216219001678 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (29094 KB)...
OKAY [ 0.623s]
writing 'boot'...
OKAY [ 0.589s]
finished. total time: 1.214s
target reported max download size of 471859200 bytes
sending 'cust' (230521 KB)...
OKAY [ 4.904s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 4.914s
target reported max download size of 471859200 bytes
sending 'recovery' (43930 KB)...
OKAY [ 0.938s]
writing 'recovery'...
OKAY [ 0.911s]
finished. total time: 1.851s
target reported max download size of 471859200 bytes
sending sparse 'system' (436384 KB)...
OKAY [ 9.752s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 9.797s
Premere un tasto per continuare . . .
what i can do now? thanks

Which official version you were on last? What else did you do?
It shows partition error which means you must have cross flashed something wrong.

apat26 said:
Which official version you were on last? What else did you do?
It shows partition error which means you must have cross flashed something wrong.
Click to expand...
Click to collapse
i was on the last b582 with emui 5 and android 7. i tried to do the root but it entered in a bootloop and i don`t know how , now there isn`t any rom.

Post your full version. L29C185 or L29C432 ....or.......

apat26 said:
Post your full version. L29C185 or L29C432 ....or.......
Click to expand...
Click to collapse
how i can know this? it was the europe version, i think the L29C185

rikyca said:
my version complete of what? sorry
Click to expand...
Click to collapse
You said B582.
Whats your full build no?
L29C185B582 or L29C432B582 or L29C636B582? or something else?
You are not on chinese AL or DL ...etc, right?

apat26 said:
You said B582.
Whats your full build no?
L29C185B582 or L29C432B582 or L29C636B582? or something else?
You are not on chinese AL or DL ...etc, right?
Click to expand...
Click to collapse
my version was the europe L29C185B582

rikyca said:
how i can know this? it was the europe version, i think the L29C185
Click to expand...
Click to collapse
That is Africa and Middle east. Europe is C432 and Asia is C636
---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------
Ok...try dloading rollback package and you should be through. On SD Card, not internal memory.
Worked???

apat26 said:
That is Africa and Middle east. Europe is C432 and Asia is C636
---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------
Ok...try dloading rollback package and you should be through. On SD Card, not internal memory.
Worked???
Click to expand...
Click to collapse
no, i can`t enter in dload mode and in twrp i cant clear cache!! the error is failed to mount `/data`(invalid argument)
failed to wipe dalvik ecc...

rikyca said:
no, i can`t enter in dload mode and in twrp i cant clear cache!! the error is failed to mount `/data`(invalid argument)
failed to wipe dalvik ecc...
Click to expand...
Click to collapse
You said you were able to dload. May be you flashed TWRP after that. Flash Stock recovery and try dload rollback package.

apat26 said:
You said you were able to dload. May be you flashed TWRP after that. Flash Stock recovery and try dload rollback package.
Click to expand...
Click to collapse
in TWRP there is (internal storage 0MB) i thin there is a bad problem. p.s dload continue to not work

rikyca said:
in TWRP there is (internal storage 0MB) i thin there is a bad problem. p.s dload continue to not work
Click to expand...
Click to collapse
Ok...Through TWRP, use Hurupdater and flash all three files you were on last. It will work.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the instructions exactly and change the file names exactly.

apat26 said:
Ok...Through TWRP, use Hurupdater and flash all three files you were on last. It will work.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the instructions exactly and change the file names exactly.
Click to expand...
Click to collapse
Ok thanks I will try it tonight

apat26 said:
Ok...Through TWRP, use Hurupdater and flash all three files you were on last. It will work.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the instructions exactly and change the file names exactly.
Click to expand...
Click to collapse
ok, I`ve installed the official rom but there isn't the keyboard, the updater etc. where I can find the complete version? thanks!!!!! P.s if i press power button + volume down it say: ''your device failed verification and may not work properly....'' the phone still start but sometimes it freeze for 3-4 seconds when i open an app, ex settings. i think something isn't installed. i don't know if the bootloader is just unlock.

rikyca said:
ok, I`ve installed the official rom but there isn't the keyboard, the updater etc. where I can find the complete version? thanks!!!!! P.s if i press power button + volume down it say: ''your device failed verification and may not work properly....'' the phone still start but sometimes it freeze for 3-4 seconds when i open an app, ex settings. i think something isn't installed. i don't know if the bootloader is just unlock.
Click to expand...
Click to collapse
Go to system updater and press look for update. you should get official one again.

apat26 said:
Go to system updater and press look for update. you should get official one again.
Click to expand...
Click to collapse
i've typed that tere isn't the updater

apat26 said:
Go to system updater and press look for update. you should get official one again.
Click to expand...
Click to collapse
If i'm not able to use the emui (because with this limitation isn't a smartphone but a phone?) i can flash a custom rom that not required the root? Thanks

Now you can use dload roll back package. Go back to MM and again upgrade to Nougat.

hi, I've unlock the bootloader on my Huawei mate 8 nxtl29c432. After the reboot the only screen on my phone is
Error mode please update system again
Error!
Func NO 11 recovery image
Error no 2 load failed!
What I can do?! I can't enter in fastboot mode only this screen!!

Looks like you are just playing around. You said all working but few app. Now you landed in error mode.
Well. let the battery dry down totally and switch off.
Then connect your phone to usb pressing vol- button n you will enter fastboot. Rest i leave it upto you to flash.