After doing a factory reset with TWRP (including /data), I flashed the custom ROM, as it got stucked in a bootloop, I tried to install stock firmware. I tried so using the dload method on external SD and internal storage as well. But both get to 5% and fail. I restored my backup but without /data because TWRP did not allowed me to back it up. Now it's running but without many apps. I would like to go back to stock. Any ideas?
My version is MHA-L29C636B158
For the mate 9 there actually are 2 Offline Firmwares available. a Chinese for the MHA-L00 and the other one is the international version, C636. Offline says they don't need the verification which for you fails at 5 percent. They will go through for sure using the dload method. Just ask Google for " Mate 9 offline firmware C636"
another solution for your problem is to download the specas data for your specific firmware using Firmware Finder ( Google play ) and flash it via TWRP.
Once done your phone should run regular.
You will get an error within TWRP but you may ignore it, the flash process will success, even it it shows something else.
Last step Wipe cache and dalvik cache, then reboot
WieserZ1C said:
For the mate 9 there actually are 2 Offline Firmwares available. a Chinese for the MHA-L00 and the other one is the international version, C636. Offline says they don't need the verification which for you fails at 5 percent. They will go through for sure using the dload method. Just ask Google for " Mate 9 offline firmware C636"
another solution for your problem is to download the specas data for your specific firmware using Firmware Finder ( Google play ) and flash it via TWRP.
Once done your phone should run regular.
You will get an error within TWRP but you may ignore it, the flash process will success, even it it shows something else.
Last step Wipe cache and dalvik cache, then reboot
Click to expand...
Click to collapse
Thanks! I tried downloading public/update_data_full_public.zip from Firmware Finder, i flashed it with TWRP but everything looks the same. So now I´m downloading this ffirmware https://drive.google.com/file/d/0B9GG_Oe0gQDyUWlCS3lTRm5IOUE/view , that i found on this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 thread, so i will try updating it with that. Should I flash hw_data for c636b136 (my actual version is c636b158),after flashing the previus step, as said on that thread?
for the international c636 you need the update_full_hw_spcseas.zip and the update_vendor.app
linorallo1 said:
Thanks! I tried downloading public/update_data_full_public.zip from Firmware Finder, i flashed it with TWRP but everything looks the same. So now I´m downloading this ffirmware https://drive.google.com/file/d/0B9GG_Oe0gQDyUWlCS3lTRm5IOUE/view , that i found on this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 thread, so i will try updating it with that. Should I flash hw_data for c636b136 (my actual version is c636b158),after flashing the previus step, as said on that thread?
Click to expand...
Click to collapse
Use this instead https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
It will let you update to the latest C636 build.
You'll have to unlock bootloader again after it's finished, and reflash twrp.
Though if you just want to use AurRom the one you downloaded will be enough.
And yes you will need too flash B136 hw and Public.
WieserZ1C said:
for the international c636 you need the update_full_hw_spcseas.zip and the update_vendor.app
Click to expand...
Click to collapse
Great, so i should download the update_full_hw_spcseas.zip for C636B158 from FF, and the update_vendor.app from the offlline C636 firmware. But i don´t quite understand the steps.
should i do like this?:
1- Flash offline C636, using dloader´s method .
2-Flashing TWRP
3-Flash update_full_hw_spcseas.zip from C636B158.
4-Done?
Sorry for so many questions but never had a Huawei before, and this is more complex than I expected.
Thanks all, the flashing via dloader´s method succeded, but now i have the b110 its not a problem.
you may update it through systemupdate if your system is untouched.
Any huawei apps now working?
WieserZ1C said:
you may update it through systemupdate if your system is untouched.
Any huawei apps now working?
Click to expand...
Click to collapse
I tried but, it doesn't detect any update. I think I will have to update manually, so far anything has worked
Related
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.
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
Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:
The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.
hackslash said:
The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.
Click to expand...
Click to collapse
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Sent from my FRD-L04 using Tapatalk
juanboja said:
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Click to expand...
Click to collapse
Unlock your bootloader and follow this guide:https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306/
Choose the B385 firmware or any newer firmware available for your region.
So I decided to finally reinstall the stock firmware in my Honor 8 FRD-L04 in B389, and this is where the nightmare began.
- I made a full backup with TWRP just in case and I decided I wanted to start from the earliest firmware possible available.
- I started unrooting my phone using the UnSU zip by Osmosis.
- Then I flash via bootloader the recovery and boot image of the firmware B360.
- I flashed the rollback package from the Huawei official site with the B122 firmware also available at the same place. I saved the rollback package in my root directory in the dload folder, and loaded it with the 3-button method. After this I wasn't able to boot my phone normally, I was stuck in a boot loop. I still continue with the next firmware, the B122, and it was successfully loaded (this also relocked my bootloader).
- It is important to say I clear many times the cache and wipe/erase data through stock recovery options, and also tried to erecover but I wans't able to connect to the WiFi. I guess something was missing (at this point I was already going crazy).
- I was still stucked at a boot loop after loading the B122, so I decided to unlock my bootloader and flash the twrp 3.1.1-1-frd.img
- From there I tried to wipe data and cache and system and everything, but I wasn't able because an error saying unable to mount always appeared.
- After rebooting, since I already had unlocked the bootloader, the initial message prompting: "press power to continue, press for 3 seconds for erecovery, etc..." appeared.
- I enter the erecovery options with the hope it will do something... and it did!!! I could connect this time through WiFi and the system asked to update the firmware and many other things it said at that moment. This was the first time I felt relieved through the night.
- The phone updated perfectly, it started at the firmware B122 and I kept updating it until I reached the B389.
- I unlocked the bootloader again and rooted the phone. And everything is running smooth as silk!
I know this is a very long story, but I just want to get it out there in case anyone is facing the same problem I just passed. Hope this helps someone and brings peace to them! =) Good luck!
I believe B385 is not functional with TWRP. Flash B360 and reboot to recovery. This should go to stock recovery, where you will have to do a factory reset. I got EMUI working, but it refuses to update to any newer version (it does show B380 but doesn't update). Also there should be updates after making that update. The updates did work for other people, so you may be able to have it working.
juanboja said:
Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:
Click to expand...
Click to collapse
Try flash B360 then OTA to 388 or 391 (If 391 singed).
blackbuffalo said:
Try flash B360 then OTA to 388 or 391 (If 391 singed).
Click to expand...
Click to collapse
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk
juanboja said:
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0
blackbuffalo said:
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0
Click to expand...
Click to collapse
Thank you very much for this info!
Sent from my FRD-L04 using Tapatalk
Hi
I have a rooted phone, and received the ota update, but when phone reboots, it goes boots to twrp .
Since ff is approved, could someone pls advise how to update via hwota8
kind regards
the-light said:
Hi
I have a rooted phone, and received the ota update, but when phone reboots, it goes boots to twrp .
Since ff is approved, could someone pls advise how to update via hwota8
kind regards
Click to expand...
Click to collapse
Flash stock recovery.
For HWOTA8, follow the thread. You need to download FullOTA.
Also with HWOTA8, you will not need to flash stock recovery manually. Basically you flash the zip from TWRP with the provided stock recovery and the three FullOTA update files from Huawei located in a HWOTA8 folder on your external SD card. Once the update is completed, you can then flash TWRP and root again. Same process for every update. Bootloader stays unlocked.
Here's the thread: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522/
the-light said:
Hi
I have a rooted phone, and received the ota update, but when phone reboots, it goes boots to twrp .
Since ff is approved, could someone pls advise how to update via hwota8
kind regards
Click to expand...
Click to collapse
mp187263 said:
Also with HWOTA8, you will not need to flash stock recovery manually. Basically you flash the zip from TWRP with the provided stock recovery and the three FullOTA update files from Huawei located in a HWOTA8 folder on your external SD card. Once the update is completed, you can then flash TWRP and root again. Same process for every update. Bootloader stays unlocked.
Here's the thread: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522/
Click to expand...
Click to collapse
Hi mp187263
Thank you for your reply, I also think updating via hwota8 is better solution, having said that, there are 4 file downloaded from ff 3 of them are with l29 and one is l09.
could u pls advise if i should dl and flash the 3 files all together with hwota8?
many thanks
You should only have 3 files, that are specific to your model. FF gives you the exact download links you need as long as the correct model is selected.
If you can get into the OS, it will be under Settings > System > About phone (example: MHA-L29 with the build number showing the region - ie. C636). Or a better way is to get the FF app and it will show you the model as well as the region. If you cannot get into the OS and your phone has not been rebranded, it will be on a label on the original box. My phone is from China so it came as a MHA-AL00, but was rebranded to MHA-L29C636 (International version). There are also other versions such as C567 for USA and so forth. The files you download have to match exactly what you have, do not flash it if unsure.
the-light said:
Hi mp187263
Thank you for your reply, I also think updating via hwota8 is better solution, having said that, there are 4 file downloaded from ff 3 of them are with l29 and one is l09.
could u pls advise if i should dl and flash the 3 files all together with hwota8?
many thanks
Click to expand...
Click to collapse
mp187263 said:
You should only have 3 files, that are specific to your model. FF gives you the exact download links you need as long as the correct model is selected.
If you can get into the OS, it will be under Settings > System > About phone (example: MHA-L29 with the build number showing the region - ie. C636). Or a better way is to get the FF app and it will show you the model as well as the region. If you cannot get into the OS and your phone has not been rebranded, it will be on a label on the original box. My phone is from China so it came as a MHA-AL00, but was rebranded to MHA-L29C636 (International version). There are also other versions such as C567 for USA and so forth. The files you download have to match exactly what you have, do not flash it if unsure.
Click to expand...
Click to collapse
Thx again for clarifying. im on c567, I didnt know if i should flash all 3 files, now I do..btw, there is a new patch coming in soon, .369, guess ill wait for it to be approved and then make the flash
ante0 said:
Flash stock recovery.
For HWOTA8, follow the thread. You need to download FullOTA.
Click to expand...
Click to collapse
I flashed the EMUI stock recovery but OTA update still fail. Any idea? Thanks.
drift08 said:
I flashed the EMUI stock recovery but OTA update still fail. Any idea? Thanks.
Click to expand...
Click to collapse
Any modified partitions? That would most likely be why, and you'd have to flash FullOTA if that's the case.
ante0 said:
Any modified partitions? That would most likely be why, and you'd have to flash FullOTA if that's the case.
Click to expand...
Click to collapse
I think I reflash EMUI to ram disk recovery via adb but still have root via magisk. When you say FullOTA, will it erase all my apps and accts? Thanks.
drift08 said:
I think I reflash EMUI to ram disk recovery via adb but still have root via magisk. When you say FullOTA, will it erase all my apps and accts? Thanks.
Click to expand...
Click to collapse
Difference between OTA and FULLOTA is that OTA patches existing partitions while full flashes full images. Your data will stay untouched
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