Hi all,
I have the AL10 dual sim version and have managed to rebrand it to L09. I've tried a few times to get custom roms working but they all seem to have the same issue which is that the sim card cannot be detected (I'm using a 4g Australian sim). I'm now back on stock EMUI 5 version b300 but have found there is no smart key feature, so I'm trying to update to a more recent version of EMUI. I've tried the method of using the dload folder then holding power and volume up and down and it tries to update but always fails and says to go to Huawei's website.. If I check for updates in settings or in hiSuite it says there are none. Does anyone know how I can get it to work?
Thanks,
Josh
Try using the Update Through DNS thing is Firmware Finder. Otherwise rollback to Marshmallow and update again, which should work.
I had the same problem. So i made the roll back to Marashmallow, then update to the latest Nougat Firmware trough OTA. That worked for me. For everything you can use the related guide here on XDA
Days Tech said:
Try using the Update Through DNS thing is Firmware Finder. Otherwise rollback to Marshmallow and update again, which should work.
Click to expand...
Click to collapse
That link doesn't seem to work..
Giuskiller said:
I had the same problem. So i made the roll back to Marashmallow, then update to the latest Nougat Firmware trough OTA. That worked for me. For everything you can use the related guide here on XDA
Click to expand...
Click to collapse
Thanks, I've tried the rollback to android 6.0 and EMUI 4.1 but it doesn't work. Do you have a link to the thread you followed?
JoshSnitz said:
Thanks, I've tried the rollback to android 6.0 and EMUI 4.1 but it doesn't work. Do you have a link to the thread you followed?
Click to expand...
Click to collapse
Hi, i followed this guide : https://forum.xda-developers.com/honor-8/how-to/restoring-relocking-bricked-frd-l04-t3666360
Obviously select the right model, i used FRD L09
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 am Currently on HONOR_8_Firmware_FRD-L02_C675B160CUSTC675D001_India.
I have tried to update to HONOR_8_Firmware_FRD-L02_C675B310CUSTC675D001_India, but I keep getting the error "Software Install Failed, Incompatibility with the current version."
What could be the reason for this? The phone was earlier on B130. There was OTA update to B140 and later to B160.
I am not rooted. The phone is Re-locked. I am on Stock recovery.
Any help would be appreciated.
P.s. FF method does not work for me.
Upgrade via firmware finder app
VenuGopalu said:
Upgrade via firmware finder app
Click to expand...
Click to collapse
I have mentioned in my post. I have not been able to get FF app working.
ganeshbiyer said:
I have mentioned in my post. I have not been able to get FF app working.
Click to expand...
Click to collapse
i didn't noticed that ..sry...
but yesterday honor 8 nougat india start rolling see the link here
you will got the update soon
Hi all. Today I purchased an Honor 6x. I am in the UK. The phone has been on all day and I have been tapping the update button like crazy. It seems that I am stuck on EMUI 4.1.3 and Android Marshmallow. Should there be a Nougat update in the UK for this phone? Thanks in advance
muppet2008 said:
Hi all. Today I purchased an Honor 6x. I am in the UK. The phone has been on all day and I have been tapping the update button like crazy. It seems that I am stuck on EMUI 4.1.3 and Android Marshmallow. Should there be a Nougat update in the UK for this phone? Thanks in advance
Click to expand...
Click to collapse
What's your build model?
Sent from my Honor 8 Pro using XDA Labs
Hi Adrian, I. Think this is it.
BLN-L21C432B151
muppet2008 said:
Hi Adrian, I. Think this is it.
BLN-L21C432B151
Click to expand...
Click to collapse
Have a look HERE, latest firmware is B366.
Sent from my Honor 8 Pro using XDA Labs
Ah thanks both. I've just had a look at that site and firmware finder. As there doesn't seem to be an OTA update heading my way I might give firmware finder a bash. Many thanks.
ahsan.mehar1 said:
U should try to upgrade via firmware finder app on play store its work 100% i also upgrade my 6x with this app
Click to expand...
Click to collapse
No, it doesn't work at 100%, often users detect problems of various types after using FF here on XDA, this because it can download even packages that not always match your phone variant...
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
muppet2008 said:
Ah thanks both. I've just had a look at that site and firmware finder. As there doesn't seem to be an OTA update heading my way I might give firmware finder a bash. Many thanks.
Click to expand...
Click to collapse
Updates should be already came out if I'm not wrong, try to force the update by clicking on system uodaye -> 3 dots on the upper right corner -> down latest update. If nothing is found, try to write to Huawei and ask about the most recent update for your build
I have sent Huawei an email requesting information with regards to an update. Obviously I'll get no reply being the weekend so I have been sat here looking at firmware finder. So close to using it. From what I understand it won't void the warranty of the phone if I update using firmware finder. What if the update doesn't work can I revert back to the original version. What if the update bricks the phone? Is that easy to fix?
TIA
ahsan.mehar1 said:
Bro its work 100% via FF application by proxy not manually. With FF application its detect ur build number and show u a valid roms
Click to expand...
Click to collapse
I saw too much times users having problem after that, i can't trust it yet man! (this is only MY opinion, to be clear)
muppet2008 said:
I have sent Huawei an email requesting information with regards to an update. Obviously I'll get no reply being the weekend so I have been sat here looking at firmware finder. So close to using it. From what I understand it won't void the warranty of the phone if I update using firmware finder. What if the update doesn't work can I revert back to the original version. What if the update bricks the phone? Is that easy to fix?
TIA
Click to expand...
Click to collapse
The rollback packages are available only for a limited amount of models at the moment (and i think forever, if Huawei wouldn't upload other packages as they've decided to do) so it could be a pain without a proper TWRP backup. For unbricking, there are some methods for doing that and it could be easy like it couldn't be, it just depends by the problem that could occur.
Ah thanks RedSkull. I might try and kerb my eagerness and see if I get a response from Huawei. This week's a bit busy so probably not the time to try anything risky.
i m not able to install stock recovery i m on twrp AND THERE IS NO OS IN MY PHONE
vendor and product partitions are completely empty
not able to boot at all not installing any rom zip as saying not able to mount vendor
how to flash vendor and product i tried with fastboot but it says remote command not allowed and tried installing stock recoery by fastboot and it installs successfully but when i boot recovery there is only twrp everytime
without stock i cant use dload method and stock is not installing and custom roms are also not installing
Hey guys.
after a download with firmware finder,I found this problem: ????
failed to authenticate installation passage.This package is unauthorized and will be deleted.Please download and install an authorized installation package.
Help me.my build number is b361 and I want to update to b380
So I'm finally ready to say goodbye to my H8 but after relocking the bootloader ,rolling back and dloading B360 for the L09 i am unable to get OTAs.
I thought i could simply flash another version from FF but all that did is allow me to update through HiSuite.
Plus it (HiSuite) always says I'm on a developer version.
Could anyone guide me to a proper L09 stock version that i can dload or anything else that would help?
I think I've had the problem before but I can't remember what I did to fix it other than maybe downgrading to MM.
But dloading the same file after that seems kind of pointless.
SharxX8 said:
So I'm finally ready to say goodbye to my H8 but after relocking the bootloader ,rolling back and dloading B360 for the L09 i am unable to get OTAs.
I thought i could simply flash another version from FF but all that did is allow me to update through HiSuite.
Plus it (HiSuite) always says I'm on a developer version.
Could anyone guide me to a proper L09 stock version that i can dload or anything else that would help?
I think I've had the problem before but I can't remember what I did to fix it other than maybe downgrading to MM.
But dloading the same file after that seems kind of pointless.
Click to expand...
Click to collapse
I Had That Problem When I Rebranded.
All You Have To Do Is Use " Get An Update Through DNS" In Firmware Finder And Now I Had The Latest Version.
And Then While I Did That I Suddenly Started To Get Updates Without Firmware Finder
Oh And Also How To Get To Stock:
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
RealFireBlaze20 said:
I Had That Problem When I Rebranded.
All You Have To Do Is Use " Get An Update Through DNS" In Firmware Finder And Now I Had The Latest Version.
And Then While I Did That I Suddenly Started To Get Updates Without Firmware Finder
Oh And Also How To Get To Stock:
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
Click to expand...
Click to collapse
Well the issue is i did both of those and neither allowed me to get official OTAs.
I want to sell the device as long as its worth something so this is rather important for that
But the rollback files i used are quite old so maybe its a wrong version or something.
But I did update through the FF proxy, same thing.no luck
Edit: i did the proxy update so maybe thats the culprit, but isnt it just downloading the same version as the dns one?
SharxX8 said:
Well the issue is i did both of those and neither allowed me to get official OTAs.
I want to sell the device as long as its worth something so this is rather important for that
But the rollback files i used are quite old so maybe its a wrong version or something.
But I did update through the FF proxy, same thing.no luck
Edit: i did the proxy update so maybe thats the culprit, but isnt it just downloading the same version as the dns one?
Click to expand...
Click to collapse
Yeah
Rommco05 said:
Which fw you were trying to install. I do not understand how you can not install eg B380 because it is point version and approved install over dload. What about unlock bootloader and flash fw over twrp?
Click to expand...
Click to collapse
I can install it but not over official OTA.
Also i saw i asked the same question on your other thread and apparently downgrading to MM fixed it last time.
So sorry,i forget things easy
I will try that
Tried it again with the official Rollback package and MM firmware.
Got the OTA to B360 and now, no OTA again...
Anyone have any suggestions?
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.