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
Related
I had been searching for a way to update my EVA-L09C636 (Asia-Pacific) model to EMUI 5.0. During the previous month I tried to install EVA-L09C636B361 firmware via either dload and Huawei Updater, but such means of direct installation never worked out.
Now the problem is solved, and the solution is quite simple, though a little bit unexpected: using Huawei Updater to install EVA-L19C636B190 before installing EVA-L09's own B361 firmware. I mean, it is interesting that we have to "borrow" the B190 firmware from the Dual SIM L19 model in order to update to EMUI 5.
(I'm not the first person to find the solution. I just found out that in a Taiwanese forum a tutorial is already posted. )
So there are two steps to install B361:
1.
Install EVA-L19C636B190 via Huawei Updater
Use Custom ROM URL
Copy and paste the link to EVA-L19C636B190:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v64578/f1/
Use the HiSuite on PC to finish the installation of B190 (Set its proxy to 127.0.0.1 and the port to 41279)
2.
Repeat the previous process, but this time, replace the link with the one to EVA-L09C636B361:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1256/g104/v73928/f1/
Again, use the HiSuite to finish the installation of B361
Note that the C636B190 version firmware for L19 model does run on L09 without the support of the L09-exclusive NFC. I think there should be a thread discussing this. Anyways, before official update comes out, the two steps above seem to be the only way to install EMUI 5 on the Asia-Pacific EVA-L09C636 version without losing data.
That is interesting, I dont have a C636 but I would assume just doing step 2 without the need to flash a L19B636 would do the trick.
whyhowie said:
I had been searching for a way to update my EVA-L09C636 (Asia-Pacific) model to EMUI 5.0. During the previous month I tried to install EVA-L09C636B361 firmware via either dload and Huawei Updater, but such means of direct installation never worked out.
Now the problem is solved, and the solution is quite simple, though a little bit unexpected: using Huawei Updater to install EVA-L19C636B190 before installing EVA-L09's own B361 firmware. I mean, it is interesting that we have to "borrow" the B190 firmware from the Dual SIM L19 model in order to update to EMUI 5.
(I'm not the first person to find the solution. I just found out that in a Taiwanese forum a tutorial is already posted. )
So there are two steps to install B361:
1.
Install EVA-L19C636B190 via Huawei Updater
Use Custom ROM URL
Copy and paste the link to EVA-L19C636B190:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v64578/f1/
Use the HiSuite on PC to finish the installation of B190 (Set its proxy to 127.0.0.1 and the port to 41279)
2.
Repeat the previous process, but this time, replace the link with the one to EVA-L09C636B361:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1256/g104/v73928/f1/
Again, use the HiSuite to finish the installation of B361
Note that the C636B190 version firmware for L19 model does run on L09 without the support of the L09-exclusive NFC. I think there should be a thread discussing this. Anyways, before official update comes out, the two steps above seem to be the only way to install EMUI 5 on the Asia-Pacific EVA-L09C636 version without losing data.
Click to expand...
Click to collapse
I was searching for this for months. I bought my p9 EVA-L09C636 in the US (I'm european) and I never had the chance to update, even at 4.1.1. I went crazy because I tried several times to unlock the bootloader first, installing twrp and flashing updates but with no success. It's unbelievable that I need to fake the version with huawei updater to obtain the updates for my phone. Now I've Nougat, without factory reset, with everything working, from nfc to all stock apps and services. Thank you very much
Z-Blade said:
That is interesting, I dont have a C636 but I would assume just doing step 2 without the need to flash a L19B636 would do the trick.
Click to expand...
Click to collapse
Well, in that case it keeps failing at 1%. I saw some previous posts talking about this as well.
Need Help
My model is Huawei P9 EVA-L09C636
I tried to update like this, it's started updating and got an error while updating then phone rebooted with new update,
but there's lot of errors,
Built Number displays as - NRD90M test-keys
Updater missing in settings
Camera missing
Flash Light not working
Clock missing
File Manger missing
and few more default huawei apps missing.
How do I fix it or downgrade to previous version back?
Thanks finally I was able to update my P9 to Nougat using this steps. The only difference is that there is a EVA-L09C636B190 available now so i didnt have to use the version for any other cell, I was afraid to do it. So following this steps i was able to upgrade from 168 to 190 and finally to 361 version.
My Phone is Huawei P9 EVA-L09C636
Even though my phone is L09 I've flashed L19 by following the steps on this thread -
(https://forum.xda-developers.com/mate-8/general/nxt-l09c636b521-official-firmware-guide-t3544729/)
2016.12.29 - EVA-L19C636 - EVA-L19C636B361
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1583/g104/v74666/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...ll/hw/spcseas/update_data_full_hw_spcseas.zip
it's still NRD90M test-keys. but i'm cool with it.
Works on AL00 as well?
I was wondering if I can get the most current european rom on my AL00 with that method as well?
Holy cow thank you for this tutorial.
I spent six hours following every tutorial I could find on the web and my P9 staunchly refused to install ANY update from the very next one after the one it came with all the way up to the latest!
After hours and hours of trying this method is the one that worked.
Edit: This firmware is a developer build.
There have been several updates installed since it was released.
After you this firmware it you should immediately install Huawei Firmware Finder from the Play Store and install the latest full OTA.
The developer build changes the device ID of your phone so you have to manually add the model of your phone in Firmware Finder as:
EVA-L19C636
Otherwise Firmware Finder would tell you there are no firmwares available for your model.
If you can't install the latest OTA immediately after installing this firmware, first install the next one available (38 if I recall correctly) then install the latest OTA -- 38 will say it failed to install but it actually installs just fine, then install the latest full OTA.
That will give you all the bug fixes and the security patches from Google.
Also note that this firmware works on both the dual sim and single sim models (it's built for the single sim but my device is dual sim and the sim configuration in settings works).
snjflame said:
My model is Huawei P9 EVA-L09C636
I tried to update like this, it's started updating and got an error while updating then phone rebooted with new update,
but there's lot of errors,
Built Number displays as - NRD90M test-keys
Updater missing in settings
Camera missing
Flash Light not working
Clock missing
File Manger missing
and few more default huawei apps missing.
How do I fix it or downgrade to previous version back?
Click to expand...
Click to collapse
The build number is normal.
As for the disappearing apps, it sounds like you have faulty flash storage.
That will cause files and apps to randomly disappear.
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.
Hi guys! Would just like to seek some assistance regarding my girlfriend's phone. I know that the Oreo update is out for quite some time now, but her phone doesn't seem to be receiving the OTA update.
I've read some other guides instructing to use Firmware Finder(?). But I haven't tried it yet since I haven't seen her phone's build number from my searches.
Please see below:
Model: MHA-L29
Build Number: MHA-L29C185B110
We can find a lot of available firmware in the Firmware Finder app but I'm being extra cautious as I do not have any experience regarding this issue.
Any input or instructions will be greatly appreciated.
I wasnt seeing it either, called huawei support, pretty much useless. tried to do a forced Oreo update via huawei file finder and hisuite, but that bricked my phone. let the battery die down, then i got control of volume keys on boot, that got me to the erecovery, downloaded 7 again, oh well, at least it was going to work, but immediately upon reboot, it said i had an update to Oreo ready! so I did it and it worked. I think if you are rooted in 7, it wont find 8. just some food for thought.
The unit came from Dubai and we haven't done any rooting to it since we do not know how.
Is there any easier workaround for it?
Hadowken said:
The unit came from Dubai and we haven't done any rooting to it since we do not know how.
Is there any easier workaround for it?
Click to expand...
Click to collapse
FF is easiest.
But you need to choose right ROM version.
Check other threads and notice what versions of region C185 were distributed by OTA.
In FF you must choose ROM with FullOTA-MF tag.
There are 186, 187, 188, 189 builds, but I don't know which is actual, cause I have C636 region.
Builds from B321 and higher are on Android 8 (Oreo). Otherwise, I recommend upgrade to last build on Android 7, then start experimenting with Oreo
There is one build B187 with FullOTA-MF-PV tag.
According changelog it created by Huawei to downgrade onto Android 7 from Oreo. But it is still FullOTA, so it is independent one. Thoughts, that it can be used to upgrade from your old build B110 to actual.
P.s. don't forget to turn proxy off before finishing download. It will avoid traffic waste.
P.p.s. Backup your important data first.
FullOTA doesn't clear user data usually, but FullOTA-MF-PV can do it.
Mha-l29c185b187 FullOTA-MF-PV
I saw a youtube video where he clicked the in-app proxy then he went to the WiFi settings to check to proxy. It was set to localhost and 8080.
After backing up important files, should I just go straight to the FF app and download the build? So sorry for the noob questions.
Hadowken said:
I saw a youtube video where he clicked the in-app proxy then he went to the WiFi settings to check to proxy. It was set to localhost and 8080.
After backing up important files, should I just go straight to the FF app and download the build? So sorry for the noob questions.
Click to expand...
Click to collapse
No need to download manually.
FF forces ROM to install via system update. It looks like phone will get notification about new ROM and you simply decide to install. Phone will download ROM and install it.
Okay, so all I have to do is choose the one you specified earlier them I'm all good? Will try it later and revert for any developments. Thank you!
So I tried downloading the build you suggested but after downloading, it failed to install and said the software was not authorized or something.
Are builds only compatible to its corresponding region? I'm from the Philippines, by the way. But the phone originated in the Middle East.
Hadowken said:
So I tried downloading the build you suggested but after downloading, it failed to install and said the software was not authorized or something.
Are builds only compatible to its corresponding region? I'm from the Philippines, by the way. But the phone originated in the Middle East.
Click to expand...
Click to collapse
Ok. Check availability by imei in FF of every FullOTA ROM version 186+
Full OTA MF only? Not Full OTA MF PV?
Got the update finally! I've been checking every day almost
Hello, sorry it took so long. I successfully updated the phone to a new build no. Mha-L29c185B188. But we still couldn't see the oreo update in the updater settings. Please advise next step for an oreo update.
Hadowken said:
Hello, sorry it took so long. I successfully updated the phone to a new build no. Mha-L29c185B188. But we still couldn't see the oreo update in the updater settings. Please advise next step for an oreo update.
Click to expand...
Click to collapse
Hi i live in Lebanon and i have the Middle east variant C185 and i am still on MHA-L29C185B188 since 2 months.
No Oreo update till today. maybe we have to just wait a little more. Normally release of OTA updates is by IMEI and not by region.
michel090428 said:
Hi i live in Lebanon and i have the Middle east variant C185 and i am still on MHA-L29C185B188 since 2 months.
No Oreo update till today. maybe we have to just wait a little more. Normally release of OTA updates is by IMEI and not by region.
Click to expand...
Click to collapse
I have a ME variant C185 as well. So I have been eagerly awaiting Oreo update since long too.
I have recently moved to Australia, as you rightly noted, the phone wouldnt update here too, since Huawei is probably checking region or IMEI or both to allow firmware updates.
Last night, I downloaded FF to check and finally managed to find Oreo update being available. Its currently downloading the 2.67 GB OTA update. But I didnt install it yet.
The version number of the download is 8.0.0.370 (C185).
You can try your luck thru FF, and I hope it works for you as well. Good luck!
I have a seemingly stupid but still annoying problem. As many of you know Android 8 + EMUI 8 came out this summer and I have updated my Honor8. Everything works well, even better (especially with regard to the battery) apart from a problem, quite annoying. I have seen that everyone around complains about the same problem, so it is clear that both a build bug and not a local problem.
Basically ... the bluetooth link with the multimedia system of my car doesn't work as it should, while it worked well with the 7.0.
Tracknames, music infos disappears, sometimes it connects regularly, starting the music, sometimes nothing happens, sometimes the music passes from the car speakers to smartphone (!!)... in short, manage the music in the car It has become a big problem!
I tried all possible options; reset pairing, reset bluetooth, clear cache, activate the developer options to control some low-level aspects of bluetooth, and finally installed Bluetooth Auto Connect which also has several advanced options. Nothing works. In the meantime an update of 8.0 has been released (mine is the buiold 521). The update came out in September ... maybe (MAYBE) this update fixes all bluetooth issues (but i don't have any detailed info about). Until today I have not received any updates and normally I check new version regularly every day. At this point I decided to return to Nougat!
And here the adventure begins!
I CANNOT IN ANY WAY do the downgrade.
What I tried:
- through HiSuite. The "back to previous version" option appears random (rarely); normally the program tells me "the system is up to date". Once appeared I tried to run the procedure, but after the decompression it gives me an error "error updating".
- by standard Rollback procedure. Using a microSD and putting the full version of Nougate in the dload folder. The installation starts but stops almost immediately with the same "update cannot be applied" error.
At this point I am desperate. I cannot update Oreo, I can't go back to Nougat and meanwhile the bluetooth still doesn't work with my car. Remember that before Oreo, everything worked very well!
What can I do? Can you help me?
Thank you
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
m2relax said:
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
Click to expand...
Click to collapse
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Thelothian said:
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Click to expand...
Click to collapse
dont worry/ do u change region of your phone past?
m2relax said:
dont worry/ do u change region of your phone past?
Click to expand...
Click to collapse
Never. And never jailbroken or rooted...
Thelothian said:
Never. And never jailbroken or rooted...
Click to expand...
Click to collapse
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
m2relax said:
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
Click to expand...
Click to collapse
I Heard TWRP doesn't work well on Oreo...
CurlyApple said:
I Heard TWRP doesn't work well on Oreo...
Click to expand...
Click to collapse
no if you use multi tools 8 for install twrp its work perfectly on oero
m2relax said:
no if you use multi tools 8 for install twrp its work perfectly on oero
Click to expand...
Click to collapse
The more you know...
Finally I've decide to try updating to 8.0.0.562. After a month of tries, fails (damn Huawei and his stupid update system), errors and a lot of other stupid things, I was finally able to update my Honor hoping the latest version will fix all the problems. It was a enormous waste of time (searching around internet)... but in the end I found a method described here: https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085#4And if you go ahead you should find the correct firmware link (on a Russian site). Although, IMHO, failing with the classic method was due to the impossibility or some bugs in the update system, to unpack the update files on sdcard. So the solution seems to be to leave both the zip and the unpacked folder.The problems with bluetooth remain, but I hope that now there is not to be crazy applying next updates. ATTENTION: the method above is NOT valid for rollback! If you try, you'll brick your Honor.
And finally I've taken an important decision... for me this is the last Huawei/honor device. Next time I'll go to another brand, with a serious update system.
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
scseke said:
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
Click to expand...
Click to collapse
flash this file with twrp and install stock recovery and do reset factor / finally use hisuite to rollback
Guys! Hello again... I'm still blocked with android 8.1 on elm29 sp5c900. I understand that c900 is global, Huawei still tells me that an update will come soon, but nothing. Erecovery doesn't find nothing on server and hisuite doesn't help me at all. Now the question... Is there a problem if I download an update file from firmware finder and install it with forced update (power plus volume buttons)? Can I brick the device, since I don't have a backup file or original software
shtresatu said:
Guys! Hello again... I'm still blocked with android 8.1 on elm29 sp5c900. I understand that c900 is global, Huawei still tells me that an update will come soon, but nothing. Erecovery doesn't find nothing on server and hisuite doesn't help me at all. Now the question... Is there a problem if I download an update file from firmware finder and install it with forced update (power plus volume buttons)? Can I brick the device, since I don't have a backup file or original software
Click to expand...
Click to collapse
Firmware downloaded through Firmware finder won't install via forced update, you can use service ROM (download though androidhost dot ru) and place it on usb OTG and force it. Or you can use patched Hisuite method to update https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page132
Yes it can brick, anything can happen but very unlikely, just backup your device through Hisuite before trying that if you want to keep your personal data(won't back up firmware, only apps, contacts etc.)
C900 hw/normal does not get any update.
Just force some updated base via dload package or via forced hisuite with dns spoofed.
Thanks for your answers! So... The steps will be... 1. Download "update full base. app"
2. Place it on root folder in dload folder
3. Update it via forced update (power button plus both volume buttons)
I've found on firmware finder update.app file. This works via dload method?
madoxx77 said:
Firmware downloaded through Firmware finder won't install via forced update, you can use service ROM (download though androidhost dot ru) and place it on usb OTG and force it. Or you can use patched Hisuite method to update https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page132
Yes it can brick, anything can happen but very unlikely, just backup your device through Hisuite before trying that if you want to keep your personal data(won't back up firmware, only apps, contacts etc.)
Click to expand...
Click to collapse
Thanks for the link... I will try this too
shtresatu said:
Thanks for your answers! So... The steps will be... 1. Download "update full base. app"
2. Place it on root folder in dload folder
3. Update it via forced update (power button plus both volume buttons)
I've found on firmware finder update.app file. This works via dload method?
Click to expand...
Click to collapse
For dload, you ll have to use an USBOTG, exfat formatted.
On 8.1, Use a 9.0 dload's update.app .
Once on 9.0, use a 9.1 dload's update_sd.zip
Alternative is to use forced hisuite.-If so uodzte first to 9.0 then 9.1.
oslo83 said:
For dload, you ll have to use an USBOTG, exfat formatted.
On 8.1, Use a 9.0 dload's update.app .
Once on 9.0, use a 9.1 dload's update_sd.zip
Alternative is to use forced hisuite.-If so uodzte first to 9.0 then 9.1.
Click to expand...
Click to collapse
Thanks a ton. I will try with dload. Is more simple
Forced hisuite doesn't work! Gives me only update to android 8.0. Firmware finder on pc doesn't give me my version sp5c900, so I can't download any firmware. Now I don't trust FF on phone neither. What if this gives wrong firmware, since my emui version is not suported. ****
oslo83 said:
C900 hw/normal does not get any update.
Click to expand...
Click to collapse
Meaning there is no update on hicloud server available for C900.
True. Damn huawei ****ty version.
Thx a lot #oslo for advices
I've spoked (finally) with someone from Huawei on chat, and after verifying my serial number she told me that my phone is a demo version. F%$&. So, no Android 9 for me. Still, my phone works flawlessly. Since I'm stuck on 8.1 I want to root it and play a little more. Can you give me an idea how to root it? Thanks
shtresatu said:
I've spoked (finally) with someone from Huawei on chat, and after verifying my serial number she told me that my phone is a demo version. F%$&. So, no Android 9 for me. Still, my phone works flawlessly. Since I'm stuck on 8.1 I want to root it and play a little more. Can you give me an idea how to root it? Thanks
Click to expand...
Click to collapse
First, is this device is with an unlocked bootloader ? (and/or do you have the unlock code ?)
To check bootloader/phone status, boot to fastboot/bootloader mode :
Plug device to PC with Hisuite, reboot P20 and Hold volumeDown on P20 until it boot on white screen ;
What is your Phone status ?
Sorry for late response. Bootloader is locked.
"phone locked.
FRP UNLOCKED"
And I don't have bootloader code.
So you won't mind that dload packages are locking back bootloader as it is already locked...
oslo83 said:
So you won't mind that dload packages are locking back bootloader as it is already locked...
Click to expand...
Click to collapse
Nope... I just want to root it so I can use Xposed