Related
I was using firmware finder to update my sister's new phone to Nougat. There were 2 downloads for the first nougat firmware and I think I got the wrong one because it rejected the next update. Can anyone confirm or explain?
Thanks
Some update packages simply don't work . It also happened to me when downgraded my BLL-L23 to MM, then upgraded to Nougat, but some OTAs got rejected. I would suggest you to try the next OTA package, or maybe to flash an "OTA/FULL" package with Nougat.
I already tried a couple of full packages... I'll just work through them in order then. Thanks.
fishnchips2 said:
I already tried a couple of full packages... I'll just work through them in order then. Thanks.
Click to expand...
Click to collapse
OTA remains the best method for official updates... It never misses a shot. Never used FF, but the results that come out from a research are just too many packages... Even wrong sometimes, as you could verify
RedSkull23 said:
OTA remains the best method for official updates... It never misses a shot. Never used FF, but the results that come out from a research are just too many packages... Even wrong sometimes, as you could verify
Click to expand...
Click to collapse
Yup but sadly they don't always show up
Hi, sorry to bump again. I've tried all the packages and had no luck, all of them failed to authenticate.
So how is your sister's state of mind ?
You should only install updates ending with PV. Put the update.app (unzipped) in a file called dload. The others should only work via Twrp recovery (did not test).
Nollie8969 said:
So how is your sister's state of mind ?
You should only install updates ending with PV. Put the update.app (unzipped) in a file called dload. The others should only work via Twrp recovery (did not test).
Click to expand...
Click to collapse
Don't understand that comment. I'm trying to do ota via proxy method not flash via dload or twrp.
Try with a rollback package
fishnchips2 said:
Don't understand that comment. I'm trying to do ota via proxy method not flash via dload or twrp.
Click to expand...
Click to collapse
Try with dload or twrp. That FF proxy method is not good always
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.
So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x
Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.
do i need the stock recovery flashed in order to do dload?
well i followed the first half of your guide and it successfully "updated" but my storage is encrypted
xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!
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
The HFF app seems to find a new firmware for M5 8.4, I downloaded it but haven't not installed it yet, waiting for the OTA maybe it will turn up soon with the Gpu turbo update, this firmware don't have that update
omaga said:
The HFF app seems to find a new firmware for M5 8.4, I downloaded it but haven't not installed it yet, waiting for the OTA maybe it will turn up soon with the Gpu turbo update, this firmware don't have that update
Click to expand...
Click to collapse
I've been running on version 163 since last Friday (SHT-AL09). No differences between versions 151 and 163 that I have noticed other than the security update. Battery life, screen response, etc. are all about the same. My tablet is running smooth with no issues other than the well documented issues known with Huawei phones/tablets (e.g. Bluetooth and WiFi)
@Butch1326: Did you get the firmware OTA? I downloaded this firmware again and made a try to update manyally but it give me a error, tried once and give it a rest, I read the change log and thought I don't bother to even try update manually because this firmware don't include the Gpu turbo update, so I try to be patient ?and wait for the OTA update.
Edit:By the way you wrote that you have SHA-AL09 device?? Do you meen SHT-AL09?
Sorry about the typo. I meant to type SHT-AL09 as the model name of my tablet.
To install the firmware upgrade as an update (no data wipe) I followed the Tutorial 2 procedure documented from the site below. It worked like a charm.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
I downloaded the Full version of the SHT-AL09C432B163 (8.0.0.163) firmware since it was the only variant available at the time from the Huawei firmware download site. If you decide to use the OTA version instead which is now available for download please note the public ZIP file name is different in the OTA ZIP file download than the ZIP file name found in the Full version of the update.
The only change I made was to update the filename for one of the firmware ZIP files from update_SHT-AL09_hw_eu.zip to update_full_hw.zip.
I downloaded and extracted the RAR file mentioned in the procedure and included the three (3) firmware update ZIP files in the oreoupdate folder as instructed, copied the oreoupdate folder and its contents to the tablet, renamed the update_SHT-AL09_hw_eu.zip to update_full_hw.zip, and let the TWRP install do the rest. This procedure will install the stock recovery. You will need to rerun the magisk root and TWRP procedures.
For Magisk I used this patched_ramdisk procedure found below:
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
and this procedure to install TWRP
https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
-----
Mine updated OTA this evening to 163.
Great news, hope to get mine very soon , if not I do it manually
I got my. 163 OTA this morning
Butch1326 said:
Sorry about the typo. I meant to type SHT-AL09 as the model name of my tablet.
To install the firmware upgrade as an update (no data wipe) I followed the Tutorial 2 procedure documented from the site below. It worked like a charm.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
I downloaded the Full version of the SHT-AL09C432B163 (8.0.0.163) firmware since it was the only variant available at the time from the Huawei firmware download site. If you decide to use the OTA version instead which is now available for download please note the public ZIP file name is different in the OTA ZIP file download than the ZIP file name found in the Full version of the update.
The only change I made was to update the filename for one of the firmware ZIP files from update_SHT-AL09_hw_eu.zip to update_full_hw.zip.
I downloaded and extracted the RAR file mentioned in the procedure and included the three (3) firmware update ZIP files in the oreoupdate folder as instructed, copied the oreoupdate folder and its contents to the tablet, renamed the update_SHT-AL09_hw_eu.zip to update_full_hw.zip, and let the TWRP install do the rest. This procedure will install the stock recovery. You will need to rerun the magisk root and TWRP procedures.
For Magisk I used this patched_ramdisk procedure found below:
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
and this procedure to install TWRP
https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
Click to expand...
Click to collapse
Thanks to this, i finally was able to install a official firmware (8.0.0.161) on my CMR-AL09C432.
I flashed a Chinese Firmware like a month ago (yes, me stupid...) and could recover from it by buying a Bootloader unlock and flashing 8.0.0.151.
It worked again but it felt buggy and clunky. Also i didnt got this OTA (161). Now i used you methode and got a full clean and fresh installed 161.
Thanks a lot!
New firmware 8.0.0.172 on HFF for SHT-AL09, no Gpu turbo yet, only Google security patch
I upgraded the firmware on my M5 SHT-AL09 from 163 to 172 using the same procedure as I previously outlined in post #4. I found out that this procedure only works with the full version of the firmware. I first tried running the OTA version. It failed at about 15% of the way through the install.
The only issue I am still investigating is the Magisk SafetyNet check. Granting apps root privilege is fine but the SafefyNet check is failing. I tried both versions 16.0 and 16.7. Other than that everything seems fine so far. I will post when I have any updates.