Database Info

Unlock/Root/TWRP OTA updates?

I've only had two phones prior to this but I have always unlocked the boot loader / rooted the device / installed a custom recovery / installed custom ROMS.
I believe with my MOTO X 1st gen this disabled the OTA updates.
Is that the case with the Honor 8? I'm wondering if it is worth it to install TWRP at this point as there seems to be so little in the way of kernels and ROMS.
Would I still be able to use SU or Xposed modules without Root?
What is the best move with this phone?

I have unlocked my bootloader as well as rooted my Honor 8. The only way to get SU and Xposed is by doing both of these procedures(root involves getting TWRP).
As for any Xposed modules, I tried amplify+greenify but instead of getting better battery life, my standby time decreased significantly. I am not sure why, but for some reason my Cell standby was showing to be eating a ton of my battery. Another big problem was that the dialer app would not let me call anyone, it kept crashing whenever I tried to. Both problems were fixed after I managed to get amplify+greenify uninstalled. Currently I am just running YouTube AdAway and MinMinGuard which seem to work fine.
So at this point, is it worth unlocking bootleader, installing TWRP, and rooting your phone? Well if there are certain Xposed modules that you really want then sure, and if there are certain apps you like that require root, then yes go ahead and root your phone. Note that if you try any OTA updates, you will have to remove TWRP as having your phone automatically restart and try to install the update wont work.

Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.

pairustwo said:
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
Click to expand...
Click to collapse
It doesnt matter whether or not your phone is rooted. You will get updates the same way, through OTA. Of course you can find .zip files to flash(although personally I am struggling to get the latest update flashed through TWRP).
The real question is for how long will we be receiving updates? Nougat is pretty much guaranteed with the new EMUI update. Huawei/Honor has promised up to 2 years of updates from what I have heard, but who knows what that actually means. They have also have a "partnership" with XDA, and the phone is decently popular so I am sure there will be a few roms, just not as many as say a OP3.

Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?

pairustwo said:
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
Click to expand...
Click to collapse
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.

Rakeen70210 said:
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Click to expand...
Click to collapse
I see the full package but I cant click on this, nothing is happened when I click on this.

Nas42O said:
I see the full package but I cant click on this, nothing is happened when I click on this.
Click to expand...
Click to collapse
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.

Rakeen70210 said:
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Click to expand...
Click to collapse
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?

Nas42O said:
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Click to expand...
Click to collapse
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.

Rakeen70210 said:
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Click to expand...
Click to collapse
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130

Nas42O said:
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Click to expand...
Click to collapse
No I am in the US. I am not sure about the EU version, but yes if you can find a .zip update file just put it on your phone and go into TWRP to install it. Might wanna make a backup too and wipe cache too just in case.

So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?

Palindrom87 said:
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Click to expand...
Click to collapse
Updating or wiping your phone does not lock the Bootloader. The only way to lock the Bootloader again is by doing it manually yourself.
Yes after doing a full update you will need to reinstall TWRP as it will be replaced with the stock recovery and then re-root your phone again.

Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?

pairustwo said:
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
Click to expand...
Click to collapse
Seeing as how the full update package was ~1.65GB in size, I think its ok to assume that it replaces everything with the stock Honor 8 image. So yes it will replace the kernel too.
For downloading full updates, the only way I got mine was an OTA directly from the phone itself. Look at my previous comments to see how I got this update. If for some reason you cant update, check if your model is ready for an update. If it is and you cant update, try to flash back to a stock image. You should be able to find one on this site or anywhere else.

Flash stock recovery will lock boot loader ?

Nas42O said:
Flash stock recovery will lock boot loader ?
Click to expand...
Click to collapse
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.

Rakeen70210 said:
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Click to expand...
Click to collapse
I thought the same thing, but after taking the full OTA update my bootloader was locked again. If you want to update I would suggest first making a full backup to the external SD card in TWRP.

Then , its better to download à full update ( update.zip) ,copy to root of the phone , reboot in twrp and flash it ? Anyone already did it ?

How to flash via TWRP a stock ROM in my problematic phone

Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys​
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'​
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.

Diamantes said:
Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys​
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'​
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Click to expand...
Click to collapse
U should use dload method
Sent from my BLN-L22 using Tapatalk

arshilhonor6x said:
U should use dload method
Click to expand...
Click to collapse
I forgot to mention: dload not working. Always error.
That's why I think TWRP is the only solution

B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.

Dazed No More said:
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Click to expand...
Click to collapse
but you mean that I have to downgrade from Nougat to MM again?
And before doing it I have to flash the stock recovery?
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips.
With the files you provide I should "dload"?
I do not understand your post.
please explain better.
Thanks.

Diamantes said:
but you mean that I have to downgrade from Nougat to MM again? Yes
And before doing it I have to flash the stock recovery? No
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips. Like I said they did half of the rollback process which is why you are on B300 firmware that you cant find available for download
With the files you provide I should "dload"? Yes
I do not understand your post.
please explain better.
Thanks.
Click to expand...
Click to collapse
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.

Well, I will try this weekend. Now the risk to stay without phone during working days is too high
Ah, BTW, thanks for suggestion.

Dazed No More said:
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Click to expand...
Click to collapse
Well, I changed my mind and tried anyway now. I was just too curious.
result:
Software install failed.
Incompatibility with current version.
please download the correct update package.​
As usual. Huawei sucks. Full stop.

Diamantes said:
Well, I changed my mind and tried anyway now. I was just too curious.
Click to expand...
Click to collapse
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
As usual. Huawei sucks. Full stop.
Click to expand...
Click to collapse
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:

Dazed No More said:
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Click to expand...
Click to collapse
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.​
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers

Diamantes said:
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.​
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Click to expand...
Click to collapse
Have you tried the Team MT huawei multitool to flash the images from the firmware? Use the Huawei update extractor tool to get the boot,cust,recovery,system and userdata.img from the firmware you tried to flash and then put them in the unbrick folder in the multi tool. Put phone in fastboot and run the Multi tool and use the unbrick option. I know your phone is not bricked but this way it will flash all 5 images in order through fastboot. You could actually try and flash the most current firmware with this method and avoid having to system update from MM to Nougat.

yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic

Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.

Diamantes said:
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Click to expand...
Click to collapse
Thats me i guess :silly:
---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
I am still learning and everytime its different result . Someitmeit works and sometimes it doesn't

Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
When I go to multitool "unbrick", it asks for custom.img, but in no update.app of my firmware is present.
Moreover now I just can enter erecovery. It does not boot. I can enter fastboot only. Multitool is now not recognizing the phone. Do you know how to proceed?
I put in dload the firmware .app, but it says "software install failed"

Pheew...I managed to have again that fuc..ng C900B300.
I entered fastboot and repeated the unlock bootloader process. That way the phone got a hard reset and started over. Believe me when I say I tried all the methods I knew.
I think there is something locked somewhere in my partitions (I am not an expert of course) that prevent me to do deep modifications. Now I just can TWRP data but not the core. And again I have no update option. I think I am stuck forever at this stage with 1st march patches and nougat 7.0.
I do not think I will be ever able to have Oreo.
Amen. I am really tired to waste my time with this s**t. Next phone will be again a Samsung or One+. Full stop. Stop chinese brands.

Where are you located, Europe?

Yes

Ok bro I really hope this is it. Full firmware BLN-L21C432B151. I already downloaded it myself and checked with extractor tool it has all the images you need. Since you have fastboot back use the multi tool unbrick again and now that you have all the necessary images cross your fingers it will work.
And I agree with you about the phone. Made up my mind im giving this turd to my sister and getting the OP5T in a few weeks.

Thanks. I will do it this weekend. Today I spent 5 hours to get back my configuration after the hard reset with the apps I use for work. Cannot risk again tomorrow.
In another thread, sashank suggested to change OEM file because probably phone doesn't recognize the firmware I want to install.
It didn't work and lead me to start from scratch with the same strange build.
I will try your method but first I must study better the procedure because I don't want to mess up everything and risking to throw the phone in the garbage (where it belongs in the end...).
Thanks.

Need help fixing an Honor 8. Stuck on EMUI 4.0 after failing with custom ROMs

Hello! So I tried flashing a custom ROM to my friends Honor 8 after reading around a bit and such but it ultimately failed and now we're trying to get it back to the default ROM. We found a ROM download but it was for the version FRD-l09C900B120 which was running EMUI4.0 and Android 6.0. I also read that the "C" version he has doesn't receive any further updates, I'm failing to find anything on the correct "C" version anywhere. If anyone could guide me through the installation process for the correct and latest firmware it would be great!
On another note, the build in eRecovery doesn't seem to want to install the update package. It always fails pretty early on after connecting to WiFi, any fix for that would be great. Thanks!
Thanks for any help!

On which ROM was the custom ROM based? You should try to flash the rollback package with dload method and then flash B120 or another EMUI 4.X ROM with same method

Rayan19997 said:
On which ROM was the custom ROM based? You should try to flash the rollback package with dload method and then flash B120 or another EMUI 4.X ROM with same method
Click to expand...
Click to collapse
The custom ROM was Linageos 14.1, so it wasn't anything EMUI based.
I'm gonna try and manually flash the ROM from an update.app that we downloaded from the app Firmware Finder.

ZelafAry said:
Hello! So I tried flashing a custom ROM to my friends Honor 8 after reading around a bit and such but it ultimately failed and now we're trying to get it back to the default ROM. We found a ROM download but it was for the version FRD-l09C900B120 which was running EMUI4.0 and Android 6.0. I also read that the "C" version he has doesn't receive any further updates, I'm failing to find anything on the correct "C" version anywhere. If anyone could guide me through the installation process for the correct and latest firmware it would be great!
On another note, the build in eRecovery doesn't seem to want to install the update package. It always fails pretty early on after connecting to WiFi, any fix for that would be great. Thanks!
Thanks for any help!
Click to expand...
Click to collapse
You did not make any twrp backup??
You are on twrp recovery right now??
Which firmware number you were on before going to custom??

hassanjavaid8181 said:
You did not make any twrp backup??
You are on twrp recovery right now??
Which firmware number you were on before going to custom??
Click to expand...
Click to collapse
We did not make a twrp backup (In hindsight we should've....)
We don't have twrp on it right not but can be fixed if needed.
We were on the latest update available to the phone which should be latest today as well. (OTA)

Flashing it manually made the phone enter a bootloop. It didn't even start the firmware. Any suggestions?
EDIT: We got into Fastboot. What are our options?

Right now your best option in my opinion is to flash Boot.img, recovery.img,cust.img and system.img that you will extract from the UPDATE.APP of your CURRENT Rom. Then just try the dload method again and again, it may not accept the firmware you try to flash but in this case just try another, but not a lower one because you need the rollback package to do that

Rayan19997 said:
Right now your best option is to pray for USB debugging to be enabled and then unlock the bootloader if you didn't do it earlier. After that you should try to flash TWRP
Click to expand...
Click to collapse
What should we do after we've flashed TWRP? When I tried flashing LineageOS 14 it decided to fail the installation somehow and be at an endless boot animation. So I'd like to get the phone restored to EMUI5.0.

Sorry, what I said was garbage, I just edited my comment, you're so quick lol

Rayan19997 said:
Sorry, what I said was garbage, I just edited my comment, you're so quick lol
Click to expand...
Click to collapse
Well currently there's a broken firmware on it of FRD-L09C432B943... Or something like that.
I think at this point he's looking at getting a new phone all together.

No matter if the firmware inside isn't working properly, with fastboot you can manually flash each partition that is needed as long as USB debugging is enabled and bootloader unlocked. After flashing these cleans parts you can properly use the dload method , and if you get an error using dload method can you tell me which one is it? At least the device behavior.
I have to sleep, I'll be right back on the morning hope you'll make it this night , if don't , please be more specific and accurate when you describe the errors you faced, that way we will be more efficient when answering
Sorry for language mistakes, English isn't my native language :silly:

Rayan19997 said:
No matter if the firmware inside isn't working properly, with fastboot you can manually flash each partition that is needed as long as USB debugging is enabled and bootloader unlocked. After flashing these cleans parts you can properly use the dload method , and if you get an error using dload method can you tell me which one is it? At least the device behavior.
I have to sleep, I'll be right back on the morning hope you'll make it this night , if don't , please be more specific and accurate when you describe the errors you faced, that way we will be more efficient when answering
Sorry for language mistakes, English isn't my native language :silly:
Click to expand...
Click to collapse
Currently there's no working OS on it so I'm gonna see if I can find a firmware that I can flash. Do you have any idea where I can get one?

Yeah on honor official site: Hihonor
Or with firmware finder

ZelafAry said:
Currently there's no working OS on it so I'm gonna see if I can find a firmware that I can flash. Do you have any idea where I can get one?
Click to expand...
Click to collapse
If you need a full firmware then you should visit official honor site..

If you flash LineageOS on a phone without OS it won't work just because LineageOS patch the current installed System, if there is no system there is no way it will boot

hassanjavaid8181 said:
If you need a full firmware then you should visit official honor site..
Click to expand...
Click to collapse
I can't find any Honor 8 FRD-L09 downloads anywhere on the Huawei sites or Honor sites. They must've removed the downloads just like they did with the Honor 7..
Rayan19997 said:
If you flash LineageOS on a phone without OS it won't work just because LineageOS patch the current installed System, if there is no system there is no way it will boot
Click to expand...
Click to collapse
I get that now and I know how to proceed in the future.
On another note, I got a good UPDATE.APP available but it refuses to install using the dload method because the versions are different. Does anyone know which partition the USERDATA.img file goes to?

You don't have to flash each single partition but dude in my opinion it's better to flash the whole UPDATE.APP, just use the rollback package and flash a lower EMUI.
Another thing: I'm currently on honor official site and I can download firmwares, you're searching in the wrong place.
www.hihonor.com/fr/support/search-result/index.html?keywords=honor 8

Rayan19997 said:
You don't have to flash each single partition but dude in my opinion it's better to flash the whole UPDATE.APP, just use the rollback package and flash a lower EMUI.
Another thing: I'm currently on honor official site and I can download firmwares, you're searching in the wrong place.
www.hihonor.com/fr/support/search-result/index.html?keywords=honor 8
Click to expand...
Click to collapse
Thank you for that link, I downloaded it and flashed it, I couldn't find it on any other hihonor site but this French one had it.
Again, thank you, it worked flawlessly installing and it updated instantly. You saved me from a lot of worrying and anxiety about breaking my friends phone lol.

I'm really glad to read that dude

thanks for the firmware been looking for it for very long!
btw you just saved another honor 8

Problem with Magisk ver 15.O and new flashing B369

Hi !
I had a problem for a few days.
I rooted my phone ( BLN L 21 C432B360) with Magisk, and when i update Magisk to version 15, i had no "Audio Engine "anymore.
With luck, i flashed my phone and updat this to B369, and rooted with Magisk Version 14.0.
Audio engine work fine yet, but I am unable to enter in developper option and in sécurity option to allow unknow source..
Any idea what happening?
I made a factory reset, flash boot.img, made a factory reset via TWRP but nothing work..

check u'r model number- it would be most probably generic
come back to stock by dload method or restore working twrp backup if u have with u'r model number and recheck u'r model number - if it's back to stock
after cleaning everything
follow this procedure
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
or
this
https://forum.xda-developers.com/honor-6x/help/calling-testers-stock-rom-t3725430
don't forget to report back

It's the same error that i encountered, only that i was on B368 before updating other than B360. At the beginning i thought that i made something wrong, but as suggested by @sreekantt, Magisk versions above V14.5 breaks up the vendor.img of our phone. I flashed through TWRP Magisk V14.6 and that's where all this is started. This means that now if you go on phone info, your model should be changed to "generic_a15" instead of BLN-L21. At the moment i solved this restoring a previous backup took on B368 just before updating to B369, but i had to fix some errors still present in the file that i exposed in this guide https://forum.xda-developers.com/honor-6x/how-to/guide-how-to-correct-wrong-shown-build-t3724439 to make my build name correct again, because even restoring a previously took backup, my build number remained B369 (and i was on a B368 build with October security patch, not the November one), so i've solved incompatibilities with some apps of my original build that was keeping crashing, like camera. I'll download the update again, update and root but this time staying on Magisk V14.5, until a fix will be ready.

RedSkull23 said:
It's the same error that i encountered, only that i was on B368 before updating other than B360. At the beginning i thought that i made something wrong, but as suggested by @sreekantt, Magisk versions above V14.5 breaks up the vendor.img of our phone. I flashed through TWRP Magisk V14.6 and that's where all this is started. This means that now if you go on phone info, your model should be changed to "generic_a15" instead of BLN-L21. At the moment i solved this restoring a previous backup took on B368 just before updating to B369, but i had to fix some errors still present in the file that i exposed in this guide https://forum.xda-developers.com/honor-6x/how-to/guide-how-to-correct-wrong-shown-build-t3724439 to make my build name correct again, because even restoring a previously took backup, my build number remained B369 (and i was on a B368 build with October security patch, not the November one), so i've solved incompatibilities with some apps of my original build that was keeping crashing, like camera. I'll download the update again, update and root but this time staying on Magisk V14.5, until a fix will be ready.
Click to expand...
Click to collapse
Thnaks you for your help.
I use Root Explorer but I am unable tu enter in root/version/special cust/BLN-L21/hw/eu/prop/local.prop because my phone , even if i installed Magisk Version 14 , is not rooted because I am unable to allow unknow source and developper option....
My build nummer is BLN-L21 but yesterday I saw in my Build.pro "Generic-a15...."
How can I downgrade or fresh install B369 or B365???
Or haow cann acces to the folder root/version/special cust/BLN-L21/hw/eu/prop/local.prop?
Thanks in advance.

ben75011 said:
Thnaks you for your help.
I use Root Explorer but I am unable tu enter in root/version/special cust/BLN-L21/hw/eu/prop/local.prop because my phone , even if i installed Magisk Version 14 , is not rooted because I am unable to allow unknow source and developper option....
My build nummer is BLN-L21 but yesterday I saw in my Build.pro "Generic-a15...."
How can I downgrade or fresh install B369 or B365???
Or haow cann acces to the folder root/version/special cust/BLN-L21/hw/eu/prop/local.prop?
Thanks in advance.
Click to expand...
Click to collapse
Try to get full firmware package and use dload method to flash the latest update. Go only with a number matching or superior your build number to make dload work fine (if you're on B369, actually you can dload only with B369 for example)

RedSkull23 said:
Try to get full firmware package and use dload method to flash the latest update. Go only with a number matching or superior your build number to make dload work fine (if you're on B369, actually you can dload only with B369 for example)
Click to expand...
Click to collapse
Hi,
I download the latest B69 firmware and try to install with DLOAD but updating work to 5% and said Update Failed.
I find a solution to endter in my system prop, My Buil nummer is BLN-L21C432B369 but in my build prop, it is notified generixc_a15....
And the problem is, i can not enter in the menu "Security" and not enter in the developper option, even if it is notified...
How to erase everithing and flash the B369 i have downloaded?
Sorry for my bad english

ben75011 said:
Hi,
I download the latest B69 firmware and try to install with DLOAD but updating work to 5% and said Update Failed.
I find a solution to endter in my system prop, My Buil nummer is BLN-L21C432B369 but in my build prop, it is notified generixc_a15....
And the problem is, i can not enter in the menu "Security" and not enter in the developper option, even if it is notified...
How to erase everithing and flash the B369 i have downloaded?
Sorry for my bad english
Click to expand...
Click to collapse
Never had luck using dload method so i can't help much, but try like this, it should work;
1 - in the local.prop file, modify every voice that ends with B369 with B368, save, reboot and check by phone info if the build number is still B369 or it is become B368. Because in this way, you'll be able to receive the OTA of B369 again.
2 - Remove root by Magisk Manager with the completely uninstall function (you're already without, but do it anyway). Reboot.
3 - Flash by fastboot the stock boot.img and recovery.img for BLN-L21C432B368 (i provided those two in the repository thread here on XDA, check this post of mine to get them https://forum.xda-developers.com/ho...ory-honor-6x-file-depot-t3534800/post74645608). After that you've flashed both of them, reboot.
4 - Go on system update. It will detect the partial OTA for B369, that weights 247MB or something like that. Don't do it, but instead click on the 3 dots in the upper right corner and tap on "download latest update". Then it'll detect the BLN-L21C432B369-FULL package. Once it'll be available for download, download it and when UI prompts if updating immediately or during night, let the update start.
If everything will works, you'll be on B369, with BLN-L21 as model number and with everything in its right place. Good luck

RedSkull23 said:
Never had luck using dload method so i can't help much, but try like this, it should work;
1 - in the local.prop file, modify every voice that ends with B369 with B368, save, reboot and check by phone info if the build number is still B369 or it is become B368. Because in this way, you'll be able to receive the OTA of B369 again.
2 - Remove root by Magisk Manager with the completely uninstall function (you're already without, but do it anyway). Reboot.
3 - Flash by fastboot the stock boot.img and recovery.img for BLN-L21C432B368 (i provided those two in the repository thread here on XDA, check this post of mine to get them https://forum.xda-developers.com/ho...ory-honor-6x-file-depot-t3534800/post74645608). After that you've flashed both of them, reboot.
4 - Go on system update. It will detect the partial OTA for B369, that weights 247MB or something like that. Don't do it, but instead click on the 3 dots in the upper right corner and tap on "download latest update". Then it'll detect the BLN-L21C432B369-FULL package. Once it'll be available for download, download it and when UI prompts if updating immediately or during night, let the update start.
If everything will works, you'll be on B369, with BLN-L21 as model number and with everything in its right place. Good luck
Click to expand...
Click to collapse
Thanks you for your help. I will try it and see feedback soon !!!
I hope it work yet

RedSkull23 said:
Never had luck using dload method so i can't help much, but try like this, it should work;
1 - in the local.prop file, modify every voice that ends with B369 with B368, save, reboot and check by phone info if the build number is still B369 or it is become B368. Because in this way, you'll be able to receive the OTA of B369 again.
2 - Remove root by Magisk Manager with the completely uninstall function (you're already without, but do it anyway). Reboot.
3 - Flash by fastboot the stock boot.img and recovery.img for BLN-L21C432B368 (i provided those two in the repository thread here on XDA, check this post of mine to get them https://forum.xda-developers.com/ho...ory-honor-6x-file-depot-t3534800/post74645608). After that you've flashed both of them, reboot.
4 - Go on system update. It will detect the partial OTA for B369, that weights 247MB or something like that. Don't do it, but instead click on the 3 dots in the upper right corner and tap on "download latest update". Then it'll detect the BLN-L21C432B369-FULL package. Once it'll be available for download, download it and when UI prompts if updating immediately or during night, let the update start.
If everything will works, you'll be on B369, with BLN-L21 as model number and with everything in its right place. Good luck
Click to expand...
Click to collapse
Also.
I made everything possible.
Flash B368, unroot...
But yet my build number is B368 and i cant received any notification of update.
And i am not allowed to enter in the Security option and in the developper option...
I dont know what I can do yet...

Thanks for the heads up. Didn't even realize the magisk update had completely borked my system.

Bro I Had The Same Problem Just Go To Recovery And Uninstall Magisk v15 And Flash Magisk V14.Everything Will Be Back To Normal.

I like how I found this thread AFTER I went through heck and back to fix my audio issue after flashing Magisk v15. Ultimately ended up flashing magiskuninstaller.zip then flashing with supersu.zip as I figured Magisk was the cause. Sure enough now Youtube and stock music app now works. I will be attempt reflashing magisk v14 and see if that makes a difference. Glad I wasn't the only one having this issue!!

I've been looking everywhere for a solution for the same problem. No sound and can not play any kinda video. I'm useing a BLN_-L24 567360. And I tried a twrp back up and now it say my phone is generic_a15. I was just rooted with magisk and twrp recovery.

McRoberts said:
I've been looking everywhere for a solution for the same problem. No sound and can not play any kinda video. I'm useing a BLN_-L24 567360. And I tried a twrp back up and now it say my phone is generic_a15. I was just rooted with magisk and twrp recovery.
Click to expand...
Click to collapse
I try since yesterday all possible. And I think the only solution is to revert to stock but I am im moment unable to revert to stock....

jyothis.shajiv said:
Bro I Had The Same Problem Just Go To Recovery And Uninstall Magisk v15 And Flash Magisk V14.Everything Will Be Back To Normal.
Click to expand...
Click to collapse
ieatgravity said:
I like how I found this thread AFTER I went through heck and back to fix my audio issue after flashing Magisk v15. Ultimately ended up flashing magiskuninstaller.zip then flashing with supersu.zip as I figured Magisk was the cause. Sure enough now Youtube and stock music app now works. I will be attempt reflashing magisk v14 and see if that makes a difference. Glad I wasn't the only one having this issue!!
Click to expand...
Click to collapse
McRoberts said:
I've been looking everywhere for a solution for the same problem. No sound and can not play any kinda video. I'm useing a BLN_-L24 567360. And I tried a twrp back up and now it say my phone is generic_a15. I was just rooted with magisk and twrp recovery.
Click to expand...
Click to collapse
ben75011 said:
I try since yesterday all possible. And I think the only solution is to revert to stock but I am im moment unable to revert to stock....
Click to expand...
Click to collapse
To use Magisk 15
Follow this
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
Perfectly working

sreekantt said:
To use Magisk 15
Follow this
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
Perfectly working
Click to expand...
Click to collapse
Thanks you, but my problem is for the moment to be able to revert to complete stock.....

ben75011 said:
I try since yesterday all possible. And I think the only solution is to revert to stock but I am im moment unable to revert to stock....
Click to expand...
Click to collapse
Do you still have a restore on twrp,? All I did to fix was went inti twrp and uninstalled magisk via magisk uninstaller then rebooted to recovery then flashed magisk v14 and now I think it's all sorted out for the min. I just got it done but I got sound and video again. The XDA labs app is picking my phone up anain as honor x6 non generic a_15.

McRoberts said:
Do you still have a restore on twrp,? All I did to fix was went inti twrp and uninstalled magisk via magisk uninstaller then rebooted to recovery then flashed magisk v14 and now I think it's all sorted out for the min. I just got it done but I got sound and video again. The XDA labs app is picking my phone up anain as honor x6 non generic a_15.
Click to expand...
Click to collapse
I found the solution with this amazing topic https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I flashed my phone with latest firmware B369 and yet all is fine !!!!!
thanks you for your help.

[NEED HELP] Unbrick Honor 6x

I've somehow bricked my 6X.
I have an EU version successfully debranded to India variant BLN-L22 and upgraded to EMUI 8.0, unencrypted and rooted with Magisk.
Something went wrong during the flash of AEX for hi6250 devices (which is reported to be 6X compatible ): I was mainly stuck in a bootloop except for two times when the phone booted, but internal storage wasn't recognized properly (in settings I was able to see the correct percentage of available space but in default file manager I wasn't able to access it and also downloading files to internal storage was impossible, as if my it was full - which isn't true since I was able to move file there through TWRP file manager).
At that point I was pretty pissed, I've forced fastboot and used update.bat to flash stock Oreo again and here things screwed up.
I took a full TWRP backup before experimenting with AEX and copied it to my pc; I'm able to push it to internal storage through adb, but then TWRP isn't able to restore it, dunno why.
My phone is in these condition now:
fastboot is available, commands from pc are working here
bootloader is unlocked
FRP is unlocked
I have a working TWRP recovery (askuccio 3.2.3) which I can access and use; I'm able to replace it with Elemental 3.2.1, with the one provided in the "update.bat" thread (which is another 3.2.1 version) or with stock recovery
if I replace TWRP with stock recovery and boot into it, it shows the update screen and it freeze at 5%, then reboot; no factory reset option there
when I'm into TWRP I can push files from pc to internal memory through adb
pretty sure my phone is still decrypted, dunno if it's still rooted tho
eRecovery is gone
I have no idea how eRecovery gone missing since I never touched that partition; trying to flash ERECOVERY_RAMDISK.img through fastboot using "fastboot flash erecovery_ramdisk erecovery_ramdisk.img" which fails (remote: command not allowed) and "fastboot flash recovery2 erecovery_ramdisk.img" which fails (remote: partition length get error) as well as through Multi Tool (the size or path does not match the file system markup); if I try to boot into eRecovery I get error mode screen: Func NO : 11 (recovery image) Error No : 2 (load failed) and I have no idea how to try to restore it in another way (pretty sure all I need is to factory reset through it and then reflash the firmware for unbrick my phone).
Atm I've tried only Multi Tool: I can successfully flash everything in the unbrick section but it doesn't solve my problem (guess it's due to my missing eRecovery).
I still need to try Image Download method (which I would like to keep it as last resource since it requires to disassemble my device and since I have a working fastboot and TWRP), HuRu and dload (I don't have a micro SD big enough atm, only 2GB - dunno if it can can work from internal storage the same).
Thank you for any help.
@player615 @shashank1320 @vovan1982 @RedSkull23

I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.

shashank1320 said:
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
Click to expand...
Click to collapse
How do I do that?
I mean, flash OEMINFO and Custom Bin and then dload method as per debranding guide or HWOTA7, since I'm on Oreo/Emui8 now?

You already debrnaded to Indian version and then updated to Oreo right?

shashank1320 said:
You already debrnaded to Indian version and then updated to Oreo right?
Click to expand...
Click to collapse
Exactly. I was on BLN-L21 Nougat (EU), debranded to BLN-L22 (Indian) through fast method (flash oem and cust bin, dload, update through system update) and then upgraded to Oreo through HWOTA8_BLN - script method.
Multi Tool list my device as BLN-L22 8.0.0.510(C675).

Just dload b340 indian variant. You should be fine

I restored my device countless times with HuRUpdater, the best tool I used on Huawei devices. It always go fine, but a microSD of at least 3GB is required (files to flash are usually 2,70GB). Probably the device won't boot with stock recovery because as you pointed out, it needs to format first before booting since that you was decrypted. HuRUpdater needs to be executed from microSD because it flashes files from there to internal storage, so flashing from there isn't allowed due obvious reasons.
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)

shashank1320 said:
Just dload b340 indian variant. You should be fine
Click to expand...
Click to collapse
RedSkull23 said:
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
Click to expand...
Click to collapse
dload doesn't work, I guess it's because I miss eRecovery.
If I hold vol+ vol- and power my phone boot into TWRP; I've tried replacing it with stock recovery but it freeze at 5%.
Any way to flash eRecovery from fastboot or as a zip from TWRP?
Gonna get a SD and for HuRu if I won't be able to solve it differently.
Edit: managed to boot into dload screen, but it states "software install failed".

AleNonsense said:
Edit: managed to boot into dload screen, but it states "software install failed".
Click to expand...
Click to collapse
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)

RedSkull23 said:
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
Click to expand...
Click to collapse
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!

AleNonsense said:
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
Click to expand...
Click to collapse
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!

Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.

player615 said:
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
Click to expand...
Click to collapse
Wait: wiping /data with TWRP makes it visible through custom recoveries since that it removes encryption, but when you flash whole EMUI 8 on system stock recovery_ramdisk is reflashed on the recovery partition too, and it forces to reformat /data before booting because if not it'll say that OS is seriously corrupted bla bla bla... EMUI 8 doesn't have to run encrypted?
By the way HuRU is faster, easier and leaves bootloader unlocked.

RedSkull23 said:
If you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Click to expand...
Click to collapse
Nope: don't get me wrong, but I'm here since 2012 and I'm pretty used to this kind of stuff.
I can assure you I haven't picked wrong packages nor any other noobish error: in fact I wouldn't even had to post here if I had encountered just some standard problem lol... my device wasn't fixable through usual ways, or else I would have been able to
RedSkull23 said:
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse
Just heard back from assistance and they are waiting for a new motherboard since there was nothing to do, good to me I was still covered by warranty.
Now it would be nice to know what screwed up my device so bad, since I hadn't any problem till the flash of AEX for hi6250 devices (so 6X compatible) and even in the case it wasn't flashing a wrong rom has never fked up a motherboard in my experience, but whatever.
My only trouble is I'm pretty sure I won't be able to unlock bootloader when my phone will be back, now
Also, thank you to everyone who tried to help!

try this
i had issues also until i found this step by step, i named everything just as he has pictured and made sure to just add the .zips all 3 needed, got correct FW from FW finder and also be sure to put the actual HuRuUpdater.zip in the same folder with the FW files and name the parent folder just like the pic on post shows...poof working stock FW and did not relock my BL....Honor 8 FRD-L04 reverted from no OS to stock 7.0 on EMUI 5 https://www.getdroidtips.com/hurupdater-tool/#comment-109621
RedSkull23 said:
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse