Related
Hi all,
I bought a H60-L12, but the manufacturer had installed the H60-L02 rom (version H60-L02V100R001CHNC00B611).
How can I install the H60-L12 version?
I've already tried to install these 5 ROMS:
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B307
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B611
H60-L12-4-4-V100R001CHNC00B118-unicom-32g
H60-L12-4-4-V100R001CHNC00B119-High-unicom
H60-L12-V100R001CHNC00B121
But I always get the error "Software Install Failed!" with the volume + & - & power method.
Also tried with the *#*#2846579#*#* and didn't worked as well.
Tried to install different stock versions and nothing.
What should I do more?
Regards,
Luis
Check INDEX
"For L12 Users ONLY" Sections you might need to restore correct version stock local.prop and build.prop
I have the same problem but I am on version L04 at the moment and can not got back to L12. My phone is not rooted nor unlocked. I asked the support of Huawei via mail but till now no reaction from their side...
Julsen1985 said:
I have the same problem but I am on version L04 at the moment and can not got back to L12. My phone is not rooted nor unlocked. I asked the support of Huawei via mail but till now no reaction from their side...
Click to expand...
Click to collapse
hi have you succeded to install L12? i found that you may need to install the L12 recovery image first and then you can flsh back to your L12 firmware have you tried?
henr721 said:
hi have you succeded to install L12? i found that you may need to install the L12 recovery image first and then you can flsh back to your L12 firmware have you tried?
Click to expand...
Click to collapse
Hi, yes I did. I wrote the way here (in german)
http://www.iphone24.org/blog/howtos...ielle-firmware-zurueck-flashen-full-restore-1
An thermalboyz included it into his collection here: http://forum.xda-developers.com/honor-6/general/huawei-honor-6-index-t2963209
Scroll down to: 3 Button Restore not working (If you change between variant example L02>L12) Or Partition been changes and cannot restore back Stock version. Use this steps below : -
From huawei club forum, which posted by Chinese, they provided a "middle package" for H60-L02/L12, L01/L03/L11/L21:
Link for refer: http://club.huawei.com/thread-4744481-1-1.html
中转包地址如下：
荣耀6移动版（H60-L01/L03/L11/L21）
荣耀6联通版（H60-L02/L12）
We have to download it, then do upgrade it first before upgrade ROM version.
P/S: If you cannot extract it, may need rename it from chinese name to latin letter.
If need assist in Chinese word, let me know.
Hope this help.
lmpcruz said:
Hi all,
I bought a H60-L12, but the manufacturer had installed the H60-L02 rom (version H60-L02V100R001CHNC00B611).
How can I install the H60-L12 version?
I've already tried to install these 5 ROMS:
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B307
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B611
H60-L12-4-4-V100R001CHNC00B118-unicom-32g
H60-L12-4-4-V100R001CHNC00B119-High-unicom
H60-L12-V100R001CHNC00B121
But I always get the error "Software Install Failed!" with the volume + & - & power method.
Also tried with the *#*#2846579#*#* and didn't worked as well.
Tried to install different stock versions and nothing.
What should I do more?
Regards,
Luis
Click to expand...
Click to collapse
Julsen1985 said:
I have the same problem but I am on version L04 at the moment and can not got back to L12. My phone is not rooted nor unlocked. I asked the support of Huawei via mail but till now no reaction from their side...
Click to expand...
Click to collapse
Julsen1985 said:
Hi, yes I did. I wrote the way here (in german)
http://www.iphone24.org/blog/howtos...ielle-firmware-zurueck-flashen-full-restore-1
An thermalboyz included it into his collection here: http://forum.xda-developers.com/honor-6/general/huawei-honor-6-index-t2963209
Scroll down to: 3 Button Restore not working (If you change between variant example L02>L12) Or Partition been changes and cannot restore back Stock version. Use this steps below : -
Click to expand...
Click to collapse
Hi all, I'm new of the forum, and this seems to be exactly the same issue I'm having.
I had to buy a replacement for my H60-L12 and I decided to buy a new one, so I went to the same store and I ordered the same phone.
When it arrived, the label indicate H60-L12, bon on the box and on the back of the phone. But when I switched on, the model name and the serial number indicated the H60-L02.
What is really strange is that, according to what I have been seeing on technical specification on internet, the L02 should have 16GB di memory, while this one has 32GB.
Do you have any idea if it is possible to verify from the IMEI what is the real model of the phone and if it is possible that a L02 firmware version was installed on a L12? I have the B316, I have tried to dowload the B316 for the L12 and put it on the dload folder, then local update, but it fails (probabily because it is the same version?).
I have download the H60-L02/L12 file indicated in the previous post, but it is very small. Is it ok?
After I have installed it using the local update procedure, what should I do?
Thanks!
I will share my experience with this issue.
As it turned out, my L12 was flashed with the wrong firmware and seens as a L02.
No way to restore the correct version with any more or less standard procedure (not even copying the built and prop files from the L12, the upgrad was always failing).
So, for future reference, what I did was:
- use the unbrick function to load a EMUI2.3 version of the firmware (at this point the phone was almost unusable because everything was crashing)
- copied the L12 B316 on the SD in dload directory
- installed using the three button procedure
The upgrade was correctly executed and now everything is working fine.
In case someone was wondering why I didn't use the unbrick function to load the L12 B316, the answer is: I did it, but it was not working. As I said, it seems that the unbrick function leaves a lot of the previous installation behind, and despite the load of the B313 (yes, I tried the 313 to be able to update then to 316 with the complete update package and have a clean installation), the update package was downloaded but not installed, always giving error. Same with the three button procedure.
So, the only way I found has been to revert to 2.3 and then apply the update.
Now I would like to know who flashed the L02 on my L12 and made me loose four days
Latest update from huawei did the following to my phone which was a rooted mate 8. ( losing root access was a given i guess )
No bluetooth
No google account
No file manager
No virtual keyboard
No alarm clock
Google voice set to default with no other alternative....AND it doesn't work!
Themes don't work.
Factory reset stops at around 22% with an exclamation mark
Pretty nifty for a 5 minute "Official" update.
What am i supposed to do with this lump of hardware?
I have my bootloader code, i have srk tool. I was originally on b190 buildnumber, then went to b200...and now this. Can someone please suggest which build number i need so i can then find the right instructions for the downgrade or whatever it's called.
U need Rollback package
ubermorgan said:
Latest update from huawei did the following to my phone which was a rooted mate 8. ( losing root access was a given i guess )
Factory reset stops at around 22% with an exclamation mark
I have my bootloader code, i have srk tool. I was originally on b190 buildnumber, then went to b200...and now this. Can someone please suggest which build number i need so i can then find the right instructions for the downgrade or whatever it's called.
Click to expand...
Click to collapse
if you have Huawei Mate 8 L29 model & if you are on Android Nougat then you need rollback package
Here is the link
http://consumer.huawei.com/sg/mobile-phones/support/downloads/detail/mate-8-sg.htm?id=91647
This is straight from Huawei and it is really a life saver. Only this file will work in dload method for you at this moment especially when you have NRD test keys or want to downgrade form nougat to marshmallow.
Download the file
Extract the update.app
Make a folder in your external SDcard and name it as dload
Place the update.app in that dload folder.
You can dload method 2 ways.
method 1
switch off your phone
press and hold volume up, volume down and power button all together
Once you see EMUI on your screen release your fingers from the phone.
method 2
open your dialer
type *#*#2846579#*#*
select - software upgrade - > SD card upgrade
that's it.
Once you are done. You will be on C900BXX build number. Then you need to dload another firmware. And which firmware you need to flash is based on your phone region and model. Is your phone previous firmware L29C185BXX ? if yes then you have to flash L29C185B180 or B192 according to your model. This is really important. Please share your complete build number.
Once you succeed in these steps then we can discuss how to move forward and what to flash next.
Hope you find this information useful and hope you succeed.
Please don't forget to click on :good::good::good::good::good::good::good: on my posts.
Samavb said:
if you have Huawei Mate 8 L29 model & if you are on Android Nougat then you need rollback package
Here is the link
http://consumer.huawei.com/sg/mobile-phones/support/downloads/detail/mate-8-sg.htm?id=91647
This is straight from Huawei and it is really a life saver. Only this file will work in dload method for you at this moment especially when you have NRD test keys or want to downgrade form nougat to marshmallow.
Download the file
Extract the update.app
Make a folder in your external SDcard and name it as dload
Place the update.app in that dload folder.
You can dload method 2 ways.
method 1
switch off your phone
press and hold volume up, volume down and power button all together
Once you see EMUI on your screen release your fingers from the phone.
method 2
open your dialer
type *#*#2846579#*#*
select - software upgrade - > SD card upgrade
that's it.
Once you are done. You will be on C900BXX build number. Then you need to dload another firmware. And which firmware you need to flash is based on your phone region and model. Is your phone previous firmware L29C185BXX ? if yes then you have to flash L29C185B180 or B192 according to your model. This is really important. Please share your complete build number.
Once you succeed in these steps then we can discuss how to move forward and what to flash next.
Hope you find this information useful and hope you succeed.
Please don't forget to click on :good::good::good::good::good::good::good: on my posts.
Click to expand...
Click to collapse
The region is Australia
Build number before this superb update was nxtl29c18b200
Now build number is NRD90 test-keys
Not that im being picky or selfish perhaps but is there a stable firmware which has low power consumption, themes work, better operation performance?
By the way, both of the above mentioned methods don't work. I got an exlamation mark and a message saying update doesn't exist after only 5% of updating
NRD test keys to Stock
ubermorgan said:
The region is Australia
Build number before this superb update was nxtl29c18b200
Now build number is NRD90 test-keys
Not that im being picky or selfish perhaps but is there a stable firmware which has low power consumption, themes work, better operation performance?
Click to expand...
Click to collapse
So you have NXT-L29C185B200 is that correct? you can check this in settings - > about -> build number
you are not in nougat so please do NOT use the file in my previous post. (that should be used only if you are in nougat)
At the moment you are in marshmallow EMUI 4.0
If you have unlocked bootloader and TWRP installed then flash L29C185B180 (stock firmware)
Link to that firmware - > http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v51422/f1/full/update.zip
For unlocking, installing TWRP you can use SRK tools. I hope you have SRK tools, if not you can get it from this thread
https://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
and from this thread you can find how to use SRK tools to unlock and install TWRP.
https://forum.xda-developers.com/mate-8/general/vdo-guide-how-to-srk-tool-huawei-unlock-t3409707
There is a video tutorial on how to do this.
Link to the thread where you can find all Stock firmwares is here
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727
For flashing the firmware
1) Factory reset
2) Format DATA
3) Flash the zip file from the above link.
Android Nougat is Android 7.0 version. and the corresponding firmware's start with L29C185B5XX
First let us get rid of that NRD test keys then you can your phone can be updated to latest firmware easily. I will explain you in detail once you succeed in this step. Don't worry about errors.
Hope you succeed.
Don't forget to :good::good::good::good::good:
Samavb said:
So you have NXT-L29C185B200 is that correct? you can check this in settings - > about -> build number
you are not in nougat so please do NOT use the file in my previous post. (that should be used only if you are in nougat)
At the moment you are in marshmallow EMUI 4.0
If you have unlocked bootloader and TWRP installed then flash L29C185B180 (stock firmware)
Link to that firmware - > http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v51422/f1/full/update.zip
For unlocking, installing TWRP you can use SRK tools. I hope you have SRK tools, if not you can get it from this thread
https://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
and from this thread you can find how to use SRK tools to unlock and install TWRP.
https://forum.xda-developers.com/mate-8/general/vdo-guide-how-to-srk-tool-huawei-unlock-t3409707
There is a video tutorial on how to do this.
Link to the thread where you can find all Stock firmwares is here
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727
For flashing the firmware
1) Factory reset
2) Format DATA
3) Flash the zip file from the above link.
Android Nougat is Android 7.0 version. and the corresponding firmware's start with L29C185B5XX
First let us get rid of that NRD test keys then you can your phone can be updated to latest firmware easily. I will explain you in detail once you succeed in this step. Don't worry about errors.
Hope you succeed.
Don't forget to :good::good::good::good::good:
Click to expand...
Click to collapse
Emui is 5
Build number is NRD90M test keys
Android version is 7
Before NRD test keys
ubermorgan said:
Emui is 5
Build number is NRD90M test keys
Android version is 7
Click to expand...
Click to collapse
I am sorry I should have been more specific. I meant before NRD test keys, your build number was NXT-L29C185B200 ? (C185 is region specific) C432 is for Europe.
And now you have EMUI 5.0? then you can use the rollback package.
Here is the link
http://consumer.huawei.com/sg/mobile...g.htm?id=91647
I thought you were in marshmallow so I suggested you not to use it. But if you are in Android 7.0 (Nougat) then you can use the rollback package.
This rollback package will downgrade your phone back to Marshmallow and then build number might say C900BXX. It should get rid of that NRD test keys.
And after that you have to flash the stock firmware using dload method
Link to that firmware - > [url]http://update.hicloud.com:8180/TDS/d...ull/update.zip[/url]
Correct link - > http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52952/f1/full/update.zip
Then you can update to any latest firmware. There are many ways to do this.
Please don't forget to click on :good::good::good::good::good::good::good: on my posts. It takes time, patience & lot of hardwork to type these posts. Not only on my posts but even on posts by other people who is helping you and giving you information
Samavb said:
I am sorry I should have been more specific. I meant before NRD test keys, your build number was NXT-L29C185B200 ? (C185 is region specific) C432 is for Europe.
And now you have EMUI 5.0? then you can use the rollback package.
Here is the link
http://consumer.huawei.com/sg/mobile...g.htm?id=91647
I thought you were in marshmallow so I suggested you not to use it. But if you are in Android 7.0 (Nougat) then you can use the rollback package.
This rollback package will downgrade your phone back to Marshmallow and then build number might say C900BXX. It should get rid of that NRD test keys.
And after that you have to flash the stock firmware using dload method
Link to that firmware - > http://update.hicloud.com:8180/TDS/d...ull/update.zip
Then you can update to any latest firmware. There are many ways to do this.
Please don't forget to click on :good::good::good::good::good::good::good: on my posts. It takes time, patience & lot of hardwork to type these posts. Not only on my posts but even on posts by other people who is helping you and giving you information
Click to expand...
Click to collapse
i've tried the update.app. I get incompatability message and it also says to try the correct update package. I keep getting error 404 on your links.
Rollback package
ubermorgan said:
i've tried the update.app. I get incompatability message and it also says to try the correct update package. I keep getting error 404 on your links.
Click to expand...
Click to collapse
If your Mate 8 was L29C185BXX before, then you can try this.
Device: Huawei Mate 8
Model:*NXT-L29
Rollback Build: NXT-LXXC185B500
Android Transition: v7.0 Nougat →*v6.x Marshmallow
EMUI Transition: v5.0 → v4.0
Status: Official
Type: Rollback (transition) firmware
File Name:*HUAWEI_Mate_8_Rollback_Package_NXT-L29_From Android7.0 EMUI5.0 to Android6.0 EMUI4.0_C185B500.zip
http://download-c.huawei.com/download/downloadCenter?downloadId=91643&version=358294&siteCode=kwen
The link I gave you in my previous post was from this thread. You can check for firmware from this thread.
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52952/f1/full/update.zip
Please don't forget to click on :good::good::good::good::good::good::good::good::good::good::good: on my posts.
Samavb said:
If your Mate 8 was L29C185BXX before, then you can try this.
Device: Huawei Mate 8
Model:*NXT-L29
Rollback Build: NXT-LXXC185B500
Android Transition: v7.0 Nougat →*v6.x Marshmallow
EMUI Transition: v5.0 → v4.0
Status: Official
Type: Rollback (transition) firmware
File Name:*HUAWEI_Mate_8_Rollback_Package_NXT-L29_From Android7.0 EMUI5.0 to Android6.0 EMUI4.0_C185B500.zip
http://download-c.huawei.com/download/downloadCenter?downloadId=91643&version=358294&siteCode=kwen
The link I gave you in my previous post was from this thread. You can check for firmware from this thread.
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52952/f1/full/update.zip
Please don't forget to click on :good::good::good::good::good::good::good::good::good::good::good: on my posts.
Click to expand...
Click to collapse
All good. I had help from danywalkert too though. Thanks to both of you really. Back on b200, emui 4, android 6. Now i guess i need an insecure boot image for this build number so i can root the phone again. Obtaining boot loader code now.
ubermorgan said:
All good. I had help from danywalkert too though. Thanks to both of you really. Back on b200, emui 4, android 6. Now i guess i need an insecure boot image for this build number so i can root the phone again. Obtaining boot loader code now.
Click to expand...
Click to collapse
You can check for your self. I have spent lot of time, energy and given you lot of information in writing not one but many posts.
:good::good::good::good::good::good::good:
I have NXT-L09-AC346B150 firmware installed on mate 8 Australian model.
Android 6 EMUI 4.03.
How to get nougat update.
Please help me.
Thanks
ketulharini said:
I have NXT-L09-AC346B150 firmware installed on mate 8 Australian model.
Android 6 EMUI 4.03.
How to get nougat update.
Please help me.
Thanks
Click to expand...
Click to collapse
Bro, you can download the firmware using firmware finder..you can install it from play store..then choose your model and region. hope this will help you.
Edit: Sorry i just checked your latest firmware is what you're using right now..sorry bro..i think you can debranding the phone then flash new nougat firmware..you can choose either europe, asia or middle east for the region. there are tons of thread to do this..
i do a rollback but build number get c900 instead of c605 of my region. original insrtuction PDF speak about a file called SDupdate_Package.tar.gz someone know about this? Im using a nxt-l09c605
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes
SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated
It's EMUI 5.0.1 not 5.1, I think.
Dear community,
I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.
In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.
I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".
My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:
- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.
- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085.
- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
mrspeccy said:
Dear community,
- In Step 17, I said ./oeminfo COL-29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
.
Click to expand...
Click to collapse
Can you share me the link to OEM info binary tool ?
It's linked from the thread I used for the first attempt. Direct access: https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo
the problem its how to get the bootloader unlock code ?
sweetjuice said:
the problem its how to get the bootloader unlock code ?
Click to expand...
Click to collapse
Correct. I received the code from Huawei before they stopped handing out the unlock codes. At the moment, I do not know of any alternatives.
mrspeccy said:
Dear community,
(...)
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Click to expand...
Click to collapse
Hey, thanks a lot for this thread!
Soo I am about to maybe do the same as you did – would you suggest/think that just doing the second Part will do the trick for me?
Can't really tell if the first part contained something that's relevant for the second/final part to work.
Furthermore – did you encounter any issues yet, now that you've used the eu rom for a bit?
(And does your device show up as certified within the Play Store?)
Oh and of what I understood, you'll have to do OTA Updates manually?
Thanks again for the effort!
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
mrspeccy said:
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
Click to expand...
Click to collapse
Great. I can assure you that without magisk but stock recovery it passes safety net as well.
mrspeccy said:
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
Click to expand...
Click to collapse
I'm the same device and is annoying chinese stuff, but i have some fear to do that. I already have the unlock code, but did not unlocked yet.
Same procedure for AL 10 c675?
Hi mine has this L29 Sp6c200 any chance changing roms?
Boorifee said:
Hi mine has this L29 Sp6c200 any chance changing roms?
Click to expand...
Click to collapse
Yes follow same procedure
.
First of all have a root access to your L29
Great find sir!!
mrspeccy said:
Dear community,
I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.
In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.
I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".
My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:
- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.
- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085.
- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Click to expand...
Click to collapse
Hi OP,
Is it possible if you could post a step to step procedure how you rebranded your phone. I have tried what you said but it turned my phone into a "beta" firmware with model number of "FTY-L29". Very weird. I have have missed something along the way now that I can't undo. If you could please help me out. Thank you very much.
tinguyen said:
Hi OP,
Is it possible if you could post a step to step procedure how you rebranded your phone. I have tried what you said but it turned my phone into a "beta" firmware with model number of "FTY-L29". Very weird. I have have missed something along the way now that I can't undo. If you could please help me out. Thank you very much.
Click to expand...
Click to collapse
Becareful , what was your previous build number and the firmware build number you tried to flash.
Can you also share more details asked in this thread .
https://forum.xda-developers.com/honor-10/how-to/discussion-hard-brick-infos-t3824022
I hard bricked a device after flashing another firmware over this same build fty l09 after flashing one firmware.
miststudent2011 said:
Becareful , what was your previous build number and the firmware build number you tried to flash.
Can you also share more details asked in this thread .
https://forum.xda-developers.com/honor-10/how-to/discussion-hard-brick-infos-t3824022
I hard bricked a device after flashing another firmware over this same build fty l09 after flashing one firmware.
Click to expand...
Click to collapse
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
tinguyen said:
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
Click to expand...
Click to collapse
5.1??
tinguyen said:
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
Click to expand...
Click to collapse
Can you provide me build number before flash and build number you flashed they are important here to solve the case.
vampirian said:
Great. I can assure you that without magisk but stock recovery it passes safety net as well.
Click to expand...
Click to collapse
Soo I just managed to rebrand my col-al10 to col-l29 (will share my whole experience soon).
But now it says my device is uncertified in the Play store (said so before Magisk & TWRP were installed and still says so, now that I've installed both and Magisk says SafetyNet is passed).
Any suggestions?
vollkornbaguette said:
Soo I just managed to rebrand my col-al10 to col-l29 (will share my whole experience soon).
But now it says my device is uncertified in the Play store (said so before Magisk & TWRP were installed and still says so, now that I've installed both and Magisk says SafetyNet is passed).
Any suggestions?
Click to expand...
Click to collapse
Can you use Google Pay after rebanding to EU version?
Johnson Chen said:
Can you use Google Pay after rebanding to EU version?
Click to expand...
Click to collapse
Hey, no I can't - and I am pretty sure it's because of the uncertified status in Google Play.
I think so because when trying to add my mastercard for contactless payment as described in my Google Pay thread, it doesn't work either but this time it's a different error message.
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
YorkiEg said:
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
Click to expand...
Click to collapse
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
ScardracS said:
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
Click to expand...
Click to collapse
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
YorkiEg said:
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
Click to expand...
Click to collapse
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
ScardracS said:
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
Click to expand...
Click to collapse
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
YorkiEg said:
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
Click to expand...
Click to collapse
For b406 and/or b407 I think you have to expect a bit
ScardracS said:
For b406 and/or b407 I think you have to expect a bit
Click to expand...
Click to collapse
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
YorkiEg said:
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
Click to expand...
Click to collapse
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
pix106 said:
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
Click to expand...
Click to collapse
That’s what’s frustrating me, all the firmware files I’ve downloaded are approved for my device Or so does Firmware Finder app says! Yet they all fail to install at 5%!
Proxy method doesn’t work on B404, or at least not working for me So nothing is working now
I’ve had enough with this phone, just to avoid smashing it into a wall next time it drives me crazy, I’m looking to get another phone, Xiaomi Mi A2 might be the one. Still looking though
Successful update
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
It downloaded the ROM files then when download completed it said the package has changed and requested to download again! I downloaded that and it started installation! Everything went well during installation but at the end it said it has failed because it could not find the update package I thought it failed and restarted the device only to find it running Android 8 and EMUI 8! Full reset and all working flawlessly
HiSuite acknowledges the update and offers to rollback to B407 if you’re having problems! Please note that I was stuck on B394! So even rolling back would be an upgrade
I’ve tested different apps, NFC (I never use it for contactless payments though so can’t confirm that, but I can’t see why it wouldn’t work) Also GPS and everything’s working just fine! Only issue is/was battery draining but that’s due to the auto launch in battery settings! I changed some of the application settings into manual launch and all great now!
Thank you for all those who helped :good: And hopefully this might help some of the frustrated Honor 8 users like myself! And hopefully won’t be stuck on B521 now!
YorkiEg said:
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK)
Click to expand...
Click to collapse
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Himmagery said:
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Click to expand...
Click to collapse
No such thing as stupid question! We all need to start somewhere
Finding the rollback package is via the official Honor support website for (Preferably) the country where you purchased your handset from. Or if it was EU, any EU country.
Rollback process will be executed by downloading and unzipping 2 files, the Honor 8_Rollback Package_FRD-L09_from Android 7.0 EMUI 5.0 to Android 6.0 EMUI 4.1_C900B300 (Around 75 MB in size) and the Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_CXYZB131 (Around 1.75GB in size).
Next you should have a MicroSD Card installed, formatted, and create a folder on root called dload.
Then Unzip the files you downloaded, will get you 2 Update.app files, copy the first one (From C900B300) to the dload folder, switch phone off, press Volume-, Volume+ and the Power button and don’t let go till system starts updating, this one won’t take long.
When finished, format you MicroSD Card, create dload folder again, then copy the second Update.app file (From CXYZB131) into the folder, same button combination to update. This update will take longer.
When finished, try Firmware Finder app immediately if you can and use the in-app proxy method to let your phone do the update, if it didn't work, let the phone do OTA update but don’t let it update too many times because Firmware Finder doesn’t work with newer System Update apps.
Hope that helps. And good luck :good:
YorkiEg said:
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
Click to expand...
Click to collapse
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
darklighthim said:
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
Click to expand...
Click to collapse
Glad it worked for you :good:
The fingerprint scanner was a bit of a hit and miss for me when I first updated but it wasn't bad enough to mention, and it has settled now! Other than that, still running smoothly