Hello xda,
i'm going straight to the problem, i used to have my Huawei GR3 rooted but i decided that i wanted to receive official updates so i could try a specific app that starts with P and ends in GO, thing is, after i flashed my phone with the stock rom from the huawei official website my phone doesn't say it can't receive updates because the phone was modified anymore but won't receive them either, i'm stuck on TAG-L21C328B126, tried using the huawei firmware search app to download the most recent version of the TAG-L21C328 but when i try to update my phone with the most recent updates, the phone always gets a error saying that the package can't find the fingerprints and asks for L21C328B127 or L21C328B128.
Is there a way i can fix this ?
Error mentioned above:
"Package expects build fingerprint of huawei/tag-l21/hwtag-l6753:5.1/huaweitag1/c328b127:user/release-keys or huawei/tag-l21/hwtag-l6753:5.1/huaweitag-l21/c328b128:user/release-keys; this device has huawei/tag-l21/hwtag-l6753:5.1/huaweitag-l21/c328b126:"
PS: Is there a way to update the stock rom update.zip with the small ota updates manually on your computer ? i contacted huawei help center on my country, all they told me was that TAG-L21C440B139 is the last ota for my phone, and since i can't update via android, i was thinking if i could grab the stock rom and just update it with all the otas till it reach TAG-L21C440B139 on my computer.
Best Regards
RD
Just trying to somehow get nougat without rooting or anything. Firmware finder shows an OTA available for L09C636B593 but I can't get it to go into updater.
This is a good question because I'm in the same boat
same to you
brian85 said:
Just trying to somehow get nougat without rooting or anything. Firmware finder shows an OTA available for L09C636B593 but I can't get it to go into updater.
Click to expand...
Click to collapse
About the only way I've seen so far, is to load twrp, screw around with other files, load a custom rom.
Until the rom shows up via the stock updater, or, the firmware finder app shows something that says
FULL and not OTA or FullOTA, you and the rest of us are stuck until Huawei officially releases it.
It's not that bad of a deal though, 6 for me anyway is VERY stable.
I agree it's stable but one of the reasons I bought a huawei phone was they are supposed to be the first to update to new versions and here I am still waiting. I thought Samsung was bad but guess what the s7 is already on android 7 and I'm not.
I think I'll be going back to Samsung soon as the note 8 comes out.
brian85 said:
Just trying to somehow get nougat without rooting or anything. Firmware finder shows an OTA available for L09C636B593 but I can't get it to go into updater.
Click to expand...
Click to collapse
from L09C636b210 you can update via Firmware Finder to L09C636b521. Then go to System Update and you will see L09C636b563 update available. I recommend DOWNLOAD LATEST FULL PACKAGE from the pull down menu.
The update came for me, but not through firmware finder. Mine came through the built in update program
in the phone.
Mine was L29C185B180, then I got 321 through firmware finder, but it never would update. When I saw someone
post that 560 came through, I tried firmware finder, never had anything, but when I checked the Huawei update
app and it showed up.
I uninstalled the firmware finder app. Nice idea, but didn't work for me.
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.
My p9 lite is VNS-L22C706B120. I never upgraded it since I bought it in New Zealand, though I have received notification of updating to B130 for a long while.
Recently I tried updating to B130 in order to get Android 7 finally, but got problem that the successful update takes no effect at all. I still remain at B120 and keep receiving update notification to B130. I described my steps recently as below:
Try Updater
First of all, I tried using Updater downloading the package and install, it says update failed because the package it not found. I found the reason is the update package is stored in internal storage other than SD card. Then I created dload folder and moved update package to SD card, but Updater cannot detect it and keep telling me to download B130. Therefore, I tried pressing Volume Up, Down and Power button together. Then the package is detected and installing started. It is very fast and I was told install success. However, after rebooting I still have B120 and am told to update to B130 by Updater.
Unlock bootloader and root
Yesterday, I decided to try custom ROM, so I managed to unlock the bootloader, install TWRY and root the phone, though I still cannot make B130 update take effect. I searched for a few custom Rom with Android 7, but I found they still required a higher firmware version than B120, like this ROM, which requires EMUI 5.X.
The help I need
I wonder if I can flash the ROMS that require a higher firmware version when I only got B120 firmware. If I cannot, how can I get my firmware updated, through Updater or any other way (like TWRY possibly) ?
I hope I have stated my problem properly so that you guys can understand. I appreciate any suggestions!
Jlw_ said:
My p9 lite is VNS-L22C706B120. I never upgraded it since I bought it in New Zealand, though I have received notification of updating to B130 for a long while...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3461043
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hey guys,
I had my Honor 8 in L19C636B380 update for a long time now.
Yesterday I tried to update with official app, I selected an option "full update", or something like that, since the app said there was no update available.
However, with that option in the menu, It found the B390 update and began the update, but the phone bricked in eRecovery mode.
I've tried the 390 update through dload method without luck. Tried full-MV of 380 without luck (recovery will stop at 5% and won't install the firmwares).
Now I'm trying the 360 full-MV-PV update (a downgrade), which seems to go past the 5% in recovery... It worked.
Considering that the european version is way ahead of the asian pacific, I'd like to know if you guys can point me to a way to rebrand to the european version, since this C636 version is stuck in 2017 (or at least my phone won't pick any OTA updated here in Brazil). I've seem some directions in the forum, but some have broken links and stuff, so I fear I may get stuck in the middle of a process...
valp88 said:
Hey guys,
I had my Honor 8 in L19C636B380 update for a long time now.
Yesterday I tried to update with official app, I selected an option "full update", or something like that, since the app said there was no update available.
However, with that option in the menu, It found the B390 update and began the update, but the phone bricked in eRecovery mode.
I've tried the 390 update through dload method without luck. Tried full-MV of 380 without luck (recovery will stop at 5% and won't install the firmwares).
Now I'm trying the 360 full-MV-PV update (a downgrade), which seems to go past the 5% in recovery... It worked.
Considering that the european version is way ahead of the asian pacific, I'd like to know if you guys can point me to a way to rebrand to the european version, since this C636 version is stuck in 2017 (or at least my phone won't pick any OTA updated here in Brazil). I've seem some directions in the forum, but some have broken links and stuff, so I fear I may get stuck in the middle of a process...
Click to expand...
Click to collapse
You Could Try Updating With The Firmware Finder App Using DNS. Maks Sure Get The One That Is The Size Of GBs
The Firmware Finder App Is In The Play Store