Database Info

Downgrade from lollipop b312 to kitkat b143

As the title, anyone know how? I tried the transitional b300 but failed. Tq in advanced

I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?

muzammil84 said:
I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?
Click to expand...
Click to collapse
Where can I find b300?
Sent from my HUAWEI MT7-TL10 using Tapatalk

muzammil84 said:
I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?
Click to expand...
Click to collapse
R u malaysia? Btw.. Can i hv the b300 link

It always stuck at 19%

Dekdek1 said:
R u malaysia? Btw.. Can i hv the b300 link
Click to expand...
Click to collapse
No man UK.
http://www.carbontesla.com/2015/07/how-to-downgrade-ascend-mate-7-to-kitkat-firmware/

why u all downgrading .. u love so much lolipop all sudden dont like it ?

because it's a performance step back, phone is almost non usable on lollipop.

if you have L09, from B300 you can flash B137Sp03, then you can flash any kitkat you want

I just want to go back to kitkat lollipop is boring , i stuck on 19% on rolling back of MT7-tl10

muzammil84 said:
because it's a performance step back, phone is almost non usable on lollipop.
Click to expand...
Click to collapse
Update to 317 it is really cool..

XDADEVX said:
Update to 317 it is really cool..
Click to expand...
Click to collapse
yeah, done it few days ago, big improvement over b308 and b312.

Anybody else here stuck on B300 transition? I can't seem to flash back to B137 or B145...keep getting stuck at 19% and menu says failed. I was at B327 5.1.1, flashed B300 and now I'm stuck.
Any ideas? Please help.

jfer671 said:
Anybody else here stuck on B300 transition? I can't seem to flash back to B137 or B145...keep getting stuck at 19% and menu says failed. I was at B327 5.1.1, flashed B300 and now I'm stuck.
Any ideas? Please help.
Click to expand...
Click to collapse
Have you tried flashing KitKat B119?
For the model TL10, here is the link: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Let me know if it works or not.

kingrk said:
Have you tried flashing KitKat B119?
For the model TL10, here is the link: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Let me know if it works or not.
Click to expand...
Click to collapse
I'm MT7-L09...tried the lowest firmware 127 up to 148, no luck.

jfer671 said:
I'm MT7-L09...tried the lowest firmware 127 up to 148, no luck.
Click to expand...
Click to collapse
Can you try this?
Upgrade to firmware B308 by downloading from here for L09 -> http://www.carbontesla.com/2015/06/download-ascend-mate-7-b308-lollipop-ota-zip-emui-3-1/
Then follow this guide:
http://www.carbontesla.com/2015/07/how-to-downgrade-ascend-mate-7-to-kitkat-firmware/
Best

Ok, problem solved. Before being stuck, I was on 145, then >148...wanted 145 back, and flashed 300. Somehow was able to then upgrade to 324 and >327. Camera is really slow on 5.1.1 and somehow doesn't take full pics (leaves gallery with multiple "no image") files.
Flashed 300 again and became stuck for the past two weeks. Re-flashing and factory resetting failed as well. Read somewhere on the forum to not factory reset on 5.1.1, after the fact, and thought I'd been soft-bricked.
**Update: finally was able to unlock boot-loader; and via adb/fastboot, re-flashed 300>324>327.
Thinking of going back 145 if I can't find solution for LP root.
Thanks for all the input tho, helped in organizing my thoughts on what went wrong.

How did you flash using fastboot. Can you write the procedure please. Did you use a custom recovery or directly flash using fastboot?
Sent from my HUAWEI MT7-TL10 using Tapatalk

kingrk said:
How did you flash using fastboot. Can you write the procedure please. Did you use a custom recovery or directly flash using fastboot?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
You need to be on correct firmware version (KK or LP) to flash correctly.
-Extract correct firmware using Huawei Update Extractor (127-137SP03), and highlight boot, recovery img
-Power down device and do Volume - and Power with usb plugged (to enter rescue mode)
-Shift + right click inside adb/fastboot folder (to open command prompt)
-Type: adb devices (to make sure it recognizes, you should see your device number)
-Type: fastboot flash boot boot.img (wait a few seconds, success)
-Type: fastboot flash recovery recovery.img (wait few seconds again, success)
-Type: fastboot reboot (your device should reboot and flashed to the firmware you chose.
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
jfer671 said:
You need to be on correct firmware version (KK or LP) to flash correctly.
-Extract correct firmware using Huawei Update Extractor (127-137SP03), and highlight boot, recovery img
-Power down device and do Volume - and Power with usb plugged (to enter rescue mode)
-Shift + right click inside adb/fastboot folder (to open command prompt)
-Type: adb devices (to make sure it recognizes, you should see your device number)
-Type: fastboot flash boot boot.img (wait a few seconds, success)
-Type: fastboot flash recovery recovery.img (wait few seconds again, success)
-Type: fastboot reboot (your device should reboot and flashed to the firmware you chose.
Click to expand...
Click to collapse
Sorry, make sure to put extracted boot/recovery img files into adb/fastboot folder, and then proceed with Shift + right click

Manually debrand from C900 to Cxxx

So the easiest way to do this as I understand it is to use @somboons srk tool unfortunately I'm having trouble with adb.
Running the srk tool the process gets stuck on the command waiting for device
I have tried different adb/fastboot installers and when I run the adb devices command I always get returned "device number Offline"
http://cloud.tapatalk.com/s/58a18bc141157/IMG_20170213_113246.jpg
But funny enough running fastboot devices with phone in fastboot mode return correct respond and I can flash file via fastboot so I don't think it's the USB drives.
So I'm now trying to find a manual way to do it, searching for the past few days have lead me to the following, but I would like someone to confirm that this is the way to go:
1. Take oeminfo from srk tool folders and place it at
/dev/blocl/platform/hi_mci.0/by-name/oeminfo
2. Take custom.bin from srk tool folder and place it at
/data
3. Change build.prop file at /System
And changing the line
ro.build.display.id=NextL00C432B011 for C432
Additional questions I have is that currently am on C636B320 and if I restart my phone will it boot up if I change above thing?
Since I need to change the build.prop file I need to use a file browser/Explorer on the phone... Or is it possible to do the changes above from TWRP?
My ultimate goal is to go to C432B560.
System info:
Unlocked bootloader
Rooted
L29C900B320 (belive it was C636 update.img)
Phone was originally AL10
Computer info:
Windows 10
Skickat från min NEXT via Tapatalk

No one? Anyone? [emoji20]
Skickat från min NEXT via Tapatalk

dexz said:
Okay. I will try to guide you. Let's do it one by one. Bare with me. So are you in C432B320 right now? Are you able to load into the system?
Sent from my HUAWEI NXT-L29 using XDA Labs
Click to expand...
Click to collapse
I'll reply to you in this thread since my initially problem is connected to the question I have in this thread.
To answer your question my phone shows C900B320 same as @EGOiST1991 did. My issue is that I can't use adb commands which means I can't use the srk tool to rebrand. I belive that is why I cannot follow the guide stated in the other thread about updating to nougat. If you read op on this thread you see the issue I have, like you said one step at a time. My goal is to upgrade to nougat... I'm wondering if wouldn't be easier to go stock and update via official update and then root once on C432B560. But if I can get it to work with TWRP which always had been easier until now I would rather do that, then I don't need to redo as many steps.
PS. I appreciate if you point me in the correct direction.

Leo_83 said:
I'll reply to you in this thread since my initially problem is connected to the question I have in this thread.
To answer your question my phone shows C900B320 same as @EGOiST1991 did. My issue is that I can't use adb commands which means I can't use the srk tool to rebrand. I belive that is why I cannot follow the guide stated in the other thread about updating to nougat. If you read op on this thread you see the issue I have, like you said one step at a time. My goal is to upgrade to nougat... I'm wondering if wouldn't be easier to go stock and update via official update and then root once on C432B560. But if I can get it to work with TWRP which always had been easier until now I would rather do that, then I don't need to redo as many steps.
PS. I appreciate if you point me in the correct direction.
Click to expand...
Click to collapse
Ok. Let's settle your adb first because it's much easier having adb working for now and in the future.
1. Which adb version are you using? SRK tools adb should be fine. Make sure run SRK Tools as administrator.
2. Did you installed latest HiSuite (for latest debug driver)?
3. Did you tried different usb port/usb cable?
Sorry you have to do the checklist. Just bare with me on this.
Edit:
One more thing you can try. Plug in your phone to your computer. Make sure the usb debugging icon showing. In Developer Options, select "Revoke USB debugging authorisation" then press OK. Unplug the usb cable then replug it again. You should get message "Allow USB debugging". Tick Always allow and press OK. After that try the "adb devices" again. Hope this will solve your adb issue.

dexz said:
Ok. Let's settle your adb first because it's much easier having adb working for now and in the future.
1. Which adb version are you using? SRK tools adb should be fine. Make sure run SRK Tools as administrator.
2. Did you installed latest HiSuite (for latest debug driver)?
3. Did you tried different usb port/usb cable?
Sorry you have to do the checklist. Just bare with me on this.
Edit:
One more thing you can try. Plug in your phone to your computer. Make sure the usb debugging icon showing. In Developer Options, select "Revoke USB debugging authorisation" then press OK. Unplug the usb cable then replug it again. You should get message "Allow USB debugging". Tick Always allow and press OK. After that try the "adb devices" again. Hope this will solve your adb issue.
Click to expand...
Click to collapse
1. I have used minimal_adb_fastboot_v1.4 and also tried from the srk commadn folder, in both I have run adb kill-server and adb start-server and then adb devices but I always get respond "Device number Offline".
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."
2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled
I dont have that option in Developer Option
The only Revoke option there is when I search is the following

Leo_83 said:
1. I have used minimal_adb_fastboot_v1.4 and also tried from the srk commadn folder, in both I have run adb kill-server and adb start-server and then adb devices but I always get respond "Device number Offline". 
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."

2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled 
I dont have that option in Developer Option 
The only Revoke option there is when I search is the following
2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled
I dont have that option in Developer Option
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."

2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled 
I dont have that option in Developer Option 
The only Revoke option there is when I search is the following

Click to expand...
Click to collapse
Ok. I think that's the reason why your adb detect offline because of usb debugging authorisation issue. Maybe you can extract boot.img & recovery.img from update.app B320 and then flash it via fastboot. After that do factory reset. Backup if needed. After enter to the system. Enable developer option again then check if revoke usb debugging showing.

dexz said:
Ok. I think that's the reason why your adb detect offline because of usb debugging authorisation issue. Maybe you can extract boot.img & recovery.img from update.app B320 and then flash it via fastboot. After that do factory reset. Backup if needed. After enter to the system. Enable developer option again then check if revoke usb debugging showing.
Click to expand...
Click to collapse
That did the trick!!! Cheers!!!
Now shall we go back to the other thread?
Edit: So I felt adventures (I know I know ) and started trying to debrand, initially didn't get it to work but now I'm half way there...
I managed to flash oeminfo and custom.bin for C432 via srk tool when I look in About Phone the following is stated:
Model Number: NXT-L29
Build Number: NXT-C900B320 I believe it is because I haven't changed the build prop
Now to the "issue" when changing the oeminfo and custom.bin with the srk tool the phone did a factory reset and I now I see that in fastboot it states:
Phone Locked
FRP Locked
So this was what I was trying to avoid initially but since it happened I wonder which is the best way forward. Unlocking bootloader once again, installing TWRP and rooting or with the bootloader locked try to go completely stock and down to C432B192....?

Leo_83 said:
That did the trick!!! Cheers!!!
Now shall we go back to the other thread?
Edit: So I felt adventures (I know I know ) and started trying to debrand, initially didn't get it to work but now I'm half way there...
I managed to flash oeminfo and custom.bin for C432 via srk tool when I look in About Phone the following is stated:
Model Number: NXT-L29
Build Number: NXT-C900B320 I believe it is because I haven't changed the build prop
Now to the "issue" when changing the oeminfo and custom.bin with the srk tool the phone did a factory reset and I now I see that in fastboot it states:
Phone Locked
FRP Locked
So this was what I was trying to avoid initially but since it happened I wonder which is the best way forward. Unlocking bootloader once again, installing TWRP and rooting or with the bootloader locked try to go completely stock and down to C432B192....?
Click to expand...
Click to collapse
Glad you managed to get adb back.
Before you do anything please make sure FRP is unlock first (This step is very important before you go Nougat). In developer option under Enable Oem Unlocked is turn on and once you flashed oeminfo it will lock your phone again. Just unlock your Bootloader using SRK Tools. I assumed you have BL code right? Once you have Unlocked BL, Unlocked FRP, TWRP, Root & Debrand. Now you are ready to go Nougat. Report me back.
Good luck

dexz said:
Glad you managed to get adb back.
Before you do anything please make sure FRP is unlock first (This step is very important before you go Nougat). In developer option under Enable Oem Unlocked is turn on and once you flashed oeminfo it will lock your phone again. Just unlock your Bootloader using SRK Tools. I assumed you have BL code right? Once you have Unlocked BL, Unlocked FRP, TWRP, Root & Debrand. Now you are ready to go Nougat. Report me back.
Good luck
Click to expand...
Click to collapse
Before I do complete rebrand... Shouldn't I go to a C432 rom first otherwise I will get bootloop, because of incompatible rom and "model", right?
Sent from my NX507J using Tapatalk

Leo_83 said:
Before I do complete rebrand... Shouldn't I go to a C432 rom first otherwise I will get bootloop, because of incompatible rom and "model", right?
Click to expand...
Click to collapse
Yes. You should debrand first. I mean debrand should be done before going to Nougat.

dexz said:
Yes. You should debrand first.
Click to expand...
Click to collapse
Sorry I think I need step by step instructions now...
I have unlocked bootloader, TWRP for EMUI 4.1 is installed and I think I'm running C636B320 but it is shown as C900B320.
If I change build.prop to C432 I won't be able to boot up on my current C636B320 update.zip so I will download C432B320. And install it from TWRP 4.1 after changing build.prop or maybe do first hmmm...
An other option could be to change build.prop, get bootloop, go to fastboot flash TWRP 4.0 and then flash C432B192.
Which do you think is the better option going forward and keeping in mind I want to go to L29C432B560?
Sent from my NX507J using Tapatalk

Leo_83 said:
Sorry I think I need step by step instructions now...
I have unlocked bootloader, TWRP for EMUI 4.1 is installed and I think I'm running C636B320 but it is shown as C900B320.
If I change build.prop to C432 I won't be able to boot up on my current C636B320 update.zip so I will download C432B320. And install it from TWRP 4.1 after changing build.prop or maybe do first hmmm...
An other option could be to change build.prop, get bootloop, go to fastboot flash TWRP 4.0 and then flash C432B192.
Which do you think is the better option going forward and keeping in mind I want to go to L29C432B560?
Click to expand...
Click to collapse
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys

dexz said:
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
Click to expand...
Click to collapse
Check! Here goes nothing... [emoji38] wish me luck [emoji12]
Sent from my NX507J using Tapatalk

Leo_83 said:
Check! Here goes nothing... [emoji38] wish me luck [emoji12]
Click to expand...
Click to collapse
Good luck :laugh:

dexz said:
Good luck [emoji23]
Click to expand...
Click to collapse
Haha to late... The phone won't boot into recovery after flashing TWRP 4.0 which is needed if I'm going to flash C432B180 or C432B192
Sent from my NX507J using Tapatalk

Leo_83 said:
Haha to late... The phone won't boot into recovery after flashing TWRP 4.0 which is needed if I'm going to flash C432B180 or C432B190
Click to expand...
Click to collapse
You can't used TWRP 4.0 because you are still in EMUI 4.1 . Try flashing TWRP 4.1 then install C432B180/B192

dexz said:
You can't used TWRP 4.0 because you are still in EMUI 4.1 . Try flashing TWRP 4.1 then install C432B180/B192
Click to expand...
Click to collapse
It's either C432B180 or C432B192?
Or both in sequence i.e first B180 and then B192?
Sent from my NX507J using Tapatalk

Leo_83 said:
It's either C432B180 or C432B192?
Or both in sequence i.e first B180 and then B192?
Click to expand...
Click to collapse
It's either one. If you can flash B192 then B192 it is.

dexz said:
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
Click to expand...
Click to collapse
Success!!!
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/
I goes it will be harder to get rooted if I first go to B560 instead of following sillanwali guide

Leo_83 said:
Success!!! 
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/

I goes it will be harder to get rooted if I first go to B560 instead of following sillanwali guide
Click to expand...
Click to collapse
Thats great. :good:
It's depend what method you want to try. you can try to follow some of the thread here
Good luck

stock recovery corrupted

apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed

Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
same here. did you managed to work it out?

Solved
eelc said:
same here. did you managed to work it out?
Click to expand...
Click to collapse
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.

Mass1veDynam1c said:
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.
Click to expand...
Click to collapse
can u make the total tutorial video of this whole process ???

I would ask if you could post a link to the update you used and a list of the commands you used..im in the US ..so it is honor 6x for the US

bricked honor 6x
You need three softwares
1. huawei multi tool by mt,,,,, in english version bro
2. Huawei update extractor
3. Firmware file update .zip
First extract the zip file , there you will get update.app file . Extract BOOT.IMG RECOVERY.IMG SYSTEM.IMG USER DATA.IMG using Huawei extractor software .
NOW open huawei multitool app (internet connection required)
Put all these files you extracted in unbrick folder of huawei multi tool
Follow steps to unbrick your device
Thank you..

can you send the links please....thank you!

Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
Try to flash twrp first , later flash stock recovery from twrp by clicking on flash image . Be sure u are installing a working recovery but not a corrupted one

eRecovery stops at 5% - Bricked?

Hi guys,
so i just had my Honor 8 on Android 7 (EMUI 5.0?) rooted and unlocked but wanted to unroot and relock. I used a tutorial for that but i think i made a mistake.
Now I stuck on the honor 8 bootscreen. I can enter fastmode and the recovery but my battery is always low.
I used the rollback package but it didnt install. Also a factory reset from the stock recovery doesnt work.
I also tried a method from here where you flash the cust.img boot.img recovery.img and the system.img from the stock an then flash the Update.app via eRecovery but this also didnt work. It stucks at 5% and does nothing. I am also not able to get to the eRecovery without pluging in the usb into the pc.
Is there any possibility to save my honor? Data's all saved.
I tried it with the rollback package, the B101 and B131 i think.
Thanks,
Musti

Hello, what is your Honor 8 model number? (L04/L09/L19/etc.)

Sorry, FRD-L09

Musti222 said:
Sorry, FRD-L09
Click to expand...
Click to collapse
What you can do is to try to flash firmware via TWRP.
Follow this guide (use "FRD-L09" link ofc...): https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
And after TWRP flash, you should flash this firmware (L09 link instead of L19 link of the guide) via dload folder method: FRD-L09C432B131
If you need help to find TWRP version, see my post : here

Do the method where you flash cust.img system.img etc but this time you boot into recovery and factory reset, then just boot, i do this everytime

Bootloop and eRecovery fails, dload fails - no way to recover

Hi people,
I need some help here and I hope anybody got an idea to get my FRD-L09 (C432 - on B521 base with OpenKirin's RROS Oreo) to work again somehow.
Situation is: After a failed attempt to upgrade the firmware base to B562 my device is now bootlooping, and goes into eRecovery, after one or two tries to boot, which is then offering to "Download and recovery". That fails at getting package info ("Getting package info failed").
Next I tried to install full OTA-PV package (extracted UPDATE.APP) via dload folder on my SD - that fails at 5 % ("Software install failed!"). For this I took the service ROM from this thread (see post #24 for Oreo version) and version B521 for FRD-L09C432 from firmware finder.
I also tried to get into TWRP 3.2.0 from Huawei Multi-Tool by TeamMT but this suddenly reboots after a few seconds everytime - so this is also useless (I tried several TWRP versions I found - maybe 'bootcomplete=false'?). I hoped to flash the extracted .img files with it.
Flashing the extracted .img files (specially the vendor image, because I think I destroyed it somehow) via fastboot also fails with error "command not allowed". Replacing the eRecovery with TWRP is also not possible (not allowed).
Flashing to system, recovery_ramdisk, kernel etc. via fastboot is possible without any problems - which shows that bootloader and frp are both unlocked.
Info btw: in this few seconds in TWRP I could see that vendor partition cannot be mounted - which shows that it's likely an error on this partition.
Is there any way to flash any "other" (vendor) partition via fastboot? Or do you guys have any ideas to this what I can try - except for bringing this thing to service center for repair :silly:? And please ask, if something is not clear or I forgot to give any info.
Any help is very appreciated.

cypher187 said:
Any help is very appreciated.
Click to expand...
Click to collapse
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.

cypher187 said:
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
Click to expand...
Click to collapse
In my case eRecovery save my a*s 2 times

ScardracS said:
In my case eRecovery save my a*s 2 times
Click to expand...
Click to collapse
Usually dload did the job well for me. I don't know why it didn't in that case.
But I'm still looking for an easy way to upgrade the firmware base for future use (in case we get some) :laugh:

Next time just use HiSuite windows version with Firmware Finder's DNS trick to flash any stock ROM version what you need, only works with version 5.0.2.300. I've got the same issue and recoered by this method ease.
You can download it here.