Hi all,
I'm running a Huawei P9 with a build number of L19C900B190. I am not rooted, bootloader locked. Having an insane time trying to find a way to upgrade from Marshmallow to Nougat. I can't find any other C900 firmwares, so is it impossible for me to upgrade? In my desperation I have finally resorted to opening a new thread. Which regions received the C900 firmware? I am based in Singapore.
I understand another method i can go is to unlock my bootloader, root my phone, flash another oem firmware like C636 or whatever and then upgrade to Nougat. However I am trying to find a method that can keep my warranty intact as my device is just a few weeks old. If anyone can point out a firmware i can flash Nougat for my phone type via the dload method, I would be really grateful.
Hi,
Just sharing my experiences with you.. I had the same problem as you. Tried to flash C636B190 firmware from stock firmware (which is customised by Starhub I guess Cause build number is L19 C20B150 and I can't find any info for C20 build) and end up having C900B190 installed. Regardless of how many times I reflash, build number stay with C900B190 instead of C636B190. Although I had the B190 build, but fail to install Nougat update via Hisuit.
You can try to use Hisuit and PC to update to Nougat, see either it will fall at 1% or not. No harm will occur on your phone.. I tried many times. After giving up, I just send the phone back to service center and revert back to their original firmware.. And to wait for OTA.
Good luck...
I ended up sticking with the C900B190 FW as it's a pretty stable firmware for marshmallow. I've read around and with some help, found out that only way to go to nougat is to debrand to a C636 FW and then upgrade manually.
Hello!
I have a P9 Plus that I wish to update from Marshmallow (L29C636B170) to Nougat (L29C636B362), but I am unable to because I keep on getting this message when I try to update...
http://i.imgur.com/2m7sV4I.jpg
"Software Install Failed!
Failed to check the update package.
Please download the package again".
I have tried using different firmware versions like B320 but the same error appears.
This phone used to have a custom TWRP recovery, but was returned to stock, and I fully unrooted my phone. I then use the Huawei Updater to send the package to HiSuite and find the firmware using Firmware Finder. I still have an unlocked bootloader however. Am I missing anything?
Cheers,
mechasnyper
Try relock the bootloader.
How do I relock the bootloader? I tried using fastboot oem lock to relock but it says that the command isnt allowed.
just simply force update dload of update.app if you are in B170 then use update.app of B170 and force dload by push 3 button same time
Okay, it seems I have solved this question with the help of Mostar088 and itongx. Special thanks to them!
The first problem was that the firmware I had was to old to update to Nougat. I had to install L29C636B202 using HiSuite. This updates the firmware to B202. Updating to B202 makes it capable of upgrading to Nougat. So, I then install L29C636B370 to my phone using HiSuite and Huawei Updater. So far, I'm loving the update and none of my files were deleted, however, this doesn't mean you shouldn't back up.
Cheers.
mechasnyper
Hi, i have a P8 lite 2017. It's a single sim phone with hardware of a dual sim. I want to flush the software and install the dual sim P8Lite 2017 software. How do I do this, please help..
So I did a hard reset after relocking my bootloader in order to install my new update (EVA-L09C150B375). I successfully relocked it, then resetted it. However, after I turned it on to install the update and restore it from HiSuite, I was welcomed with the EMUI starting screen (language selection, T&C, wifi, google account) and I'm stuck there. The thing is, all my keyboards are lost and whenever I want to type in something, only the google voice button shows which I can't possibly use to enter passwords or pin. If I skip everything and 'set up as new phone', it brings me to the 'add fingerprint' scene which if I skip, I'm brought all the way back to the beginning of the WHOLE proccess (back to the EMUI logo), and I can't add a fingerprint because you have to give either a PIN or a password in order to be able to use it. I have Wi-fi connection but nothing else. I can't bring up any menus. When I do a hard reset, it bring me to this page again after rebooting. Is there a workaround? I'm completely lost.
horesz1994 said:
So I did a hard reset after relocking my bootloader in order to install my new update (EVA-L09C150B375). I successfully relocked it, then resetted it. However, after I turned it on to install the update and restore it from HiSuite, I was welcomed with the EMUI starting screen (language selection, T&C, wifi, google account) and I'm stuck there. The thing is, all my keyboards are lost and whenever I want to type in something, only the google voice button shows which I can't possibly use to enter passwords or pin. If I skip everything and 'set up as new phone', it brings me to the 'add fingerprint' scene which if I skip, I'm brought all the way back to the beginning of the WHOLE proccess (back to the EMUI logo), and I can't add a fingerprint because you have to give either a PIN or a password in order to be able to use it. I have Wi-fi connection but nothing else. I can't bring up any menus. When I do a hard reset, it bring me to this page again after rebooting. Is there a workaround? I'm completely lost.
Click to expand...
Click to collapse
First of all, unlocked bootloader does not prevent OTA - for OTA you must have stock recovery and stock boot partition (no root) but you can have bootloader unlocked.
Only thing - successful OTA may lock your bootloader back (depending if such a flag is present in stock update.zip or not) but again, you can safely start OTA with the unlocked bootloader.
Don't know why so many people go to relock bootloader before accepting OTA, which triggers hard reset and potentially troubles.
Did you at least leave OEM unlocked (OEM/FRP unlock also does not prevent OTA), that you can unlock bootloder again, install TWRP and revive your system by eg HWOTA method?
About missing keyboard - when you had your previous rooted system, have you disabled/removed Huawei default keyboards: SwiftKey and Swipe for Huawei - after hard reset it looks only for them, without them you have no keyboard...
Also, before hard resetting, have you removed fingerprint protection you have had?
Generally, if you removed fingerprint before hard reset, you should be able to skip setting the fingerprint.
I had a similar situation (no keyboard upun hard reset), and I was able to skip fingerprint, set-up a new system and then to install GBoard from apk on SD card and to continue.
zgfg said:
First of all, unlocked bootloader does not prevent OTA - for OTA you must have stock recovery and stock boot partition (no root) but you can have bootloader unlocked.
Only thing - successful OTA may lock your bootloader back (depending if such a flag is present in stock update.zip or not) but again, you can safely start OTA with the unlocked bootloader.
Don't know why so many people go to relock bootloader before accepting OTA, which triggers hard reset and potentially troubles.
Did you at least leave OEM unlocked (OEM/FRP unlock also does not prevent OTA), that you can unlock bootloder again, install TWRP and revive your system by eg HWOTA method?
About missing keyboard - when you had your previous rooted system, have you disabled/removed Huawei default keyboards: SwiftKey and Swipe for Huawei - after hard reset it looks only for them, without them you have no keyboard...
Also, before hard resetting, have you removed fingerprint protection you have had?
Generally, if you removed fingerprint before hard reset, you should be able to skip setting the fingerprint.
I had a similar situation (no keyboard upun hard reset), and I was able to skip fingerprint, set-up a new system and then to install GBoard from apk on SD card and to continue.
Click to expand...
Click to collapse
I couldn't install the new update when I was unlocked, because it went into a boot loop. That's why I decided to start over with a clean page. I haven't disabled any keyboards and I haven't removed my fingerprint.
horesz1994 said:
I couldn't install the new update when I was unlocked, because it went into a boot loop. That's why I decided to start over with a clean page. I haven't disabled any keyboards and I haven't removed my fingerprint.
Click to expand...
Click to collapse
You couldn't install OTA not because of unlocked bootloader per se, but because of TWRP or root.
You better had to remove fingerprint before forcing to relock bootloader.
Did you leave OEM (FRP) unlocked (it doesn't affect OTA anyhow) - then boot to Fastboot, unlock bootloader, install TWRP and use HWOTA to flash complete firmware
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Otherwise, if you could get over fingerprint, boot to the system and install GBoard (download the apk on the PC or another phone and put it to the SD card)
Last option, rollback to MM and then upgrade by OTAs to the latest Nougat.
zgfg said:
You couldn't install OTA not because of unlocked bootloader per se, but because of TWRP or root.
You better had to remove fingerprint before forcing to relock bootloader.
Did you leave OEM (FRP) unlocked (it doesn't affect OTA anyhow) - then boot to Fastboot, unlock bootloader, install TWRP and use HWOTA to flash complete firmware
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Otherwise, if you could get over fingerprint, boot to the system and install GBoard (download the apk on the PC or another phone and put it to the SD card)
Last option, rollback to MM and then upgrade by OTAs to the latest Nougat.
Click to expand...
Click to collapse
The problem is, I have no way of accessing the file system.
Take out SD card, put on DLOAD for rollback to MM.
zgfg said:
Take out SD card, put on DLOAD for rollback to MM.
Click to expand...
Click to collapse
I will try this, thank you! where can I find the correct rom for my phone model?
horesz1994 said:
I will try this, thank you! where can I find the correct rom for my phone model?
Click to expand...
Click to collapse
Firmware Finder
zgfg said:
Firmware Finder
Click to expand...
Click to collapse
Okay, so I've tried b136 and b167 (the two most common in these solutions in this forum), and both of them went to 5% and then came an error message:
“Incompatibility with current version. Please download the correct update package”
I'm truly lost now. Any ideas? Should I try every single package for the L09?
horesz1994 said:
Okay, so I've tried b136 and b167 (the two most common in these solutions in this forum), and both of them went to 5% and then came an error message:
“Incompatibility with current version. Please download the correct update package”
I'm truly lost now. Any ideas? Should I try every single package for the L09?
Click to expand...
Click to collapse
Here is a proven rollback guide
https://forum.xda-developers.com/showpost.php?p=73448165&postcount=371
Skip steps 7-8.
In step 9 you should get OTA updates till b504 for L09 (b399 for L19).
Steps 11-13 are about rooting by SuperSU, not part of rollback.
PS: This guide is for L09/L19 c432 - if your phone was diff cust, you should rebrand or use b182 for your cust (not b182 for c432 as in the guide - you should look for the appropriate FullOTA-MF-PV build in Firmware Finder - MUST be FullOTA-MF-PV MM for your cust)
zgfg said:
Here is a proven rollback guide
https://forum.xda-developers.com/showpost.php?p=73448165&postcount=371
Skip steps 7-8.
In step 9 you should get OTA updates till b504 for L09 (b399 for L19).
Steps 11-13 are about rooting by SuperSU, not part of rollback.
PS: This guide is for L09/L19 c432 - if your phone was diff cust, you should rebrand or use b182 for your cust (not b182 for c432 as in the guide - you should look for the appropriate FullOTA-MF-PV build in Firmware Finder - MUST be FullOTA-MF-PV MM for your cust)
Click to expand...
Click to collapse
Will do, but I have one more question; how do I find out my model number(cust)? the box only shows the IMEI and that it's EVA-L09 and nothing else. I can't access phone details in the phone itself because of the original problem.
I see for my L09c432 in this file:
/cust/hw/eu/prop/local.prop
at the end:
ro.comp.cust_version=Cust-432000 5.0.0.1(0001)
You can probably (never did myself) copy it by ADB commands to PC and read.
Maybe you need to unlock bootloader to get access.
In that case you can also install TWRP and copy the file to SD card, and then open it on the PC
PS: I usually save screenshots to the cloud with Build info (About), IMEI, etc...
zgfg said:
I see for my L09c432 in this file:
/cust/hw/eu/prop/local.prop
at the end:
ro.comp.cust_version=Cust-432000 5.0.0.1(0001)
You can probably (never did myself) copy it by ADB commands to PC and read.
Maybe you need to unlock bootloader to get access.
In that case you can also install TWRP and copy the file to SD card, and then open it on the PC
PS: I usually save screenshots to the cloud with Build info (About), IMEI, etc...
Click to expand...
Click to collapse
The guide you posted earlier worked! currently at b182, but haven't received any OTA yet (strange...). I'm now waiting for google play to update and install all the necessary apps though. Thank you, Thank you and THANK YOU!
So, is it normal that I'm now stuck on EVA-L09C900B182 ? Firmware finder is not working (not downloading, always getting error), and the stock huawei updater can't find any updates, so I'm now at emui 4.1.1. Will I receive those updates and should I wait, or should I flash from sd card the dload method?
Oh, and HiSuite also tells me that I use the newest update.
horesz1994 said:
So, is it normal that I'm now stuck on EVA-L09C900B182 ? Firmware finder is not working (not downloading, always getting error), and the stock huawei updater can't find any updates, so I'm now at emui 4.1.1. Will I receive those updates and should I wait, or should I flash from sd card the dload method?
Oh, and HiSuite also tells me that I use the newest update.
Click to expand...
Click to collapse
For OTA you must have SIM and must not be in Airplane mode.
It may take few hours or up to a day - it depends on your mobile operator.
Beginning of this year, last time I did rollback, I got b203 (if recalling correctly), then b383 or b387, then up to b398 (at that time).
Give it a try. Otherwise use DLOAD (use FF only for download), you must use FullOTA-MF-PV builds, only those work for DLOAD
zgfg said:
For OTA you must have SIM and must not be in Airplane mode.
It may take few hours or up to a day - it depends on your mobile operator.
Beginning of this year, last time I did rollback, I got b203 (if recalling correctly), then b383 or b387, then up to b398 (at that time).
Give it a try. Otherwise use DLOAD (use FF only for download), you must use FullOTA-MF-PV builds, only those work for DLOAD
Click to expand...
Click to collapse
okay, I'll wait til tomorrow. But the shady part is that even HiSuite can't find an update, what does my operator have to do with this?
I don't know how it depends on Huawei, ypur IMEI, SIM card... but once I was similarly waiting and both HiSuite and System Update told me I had the latest, and then same day later I got OTA push
Oops, sorry, I have overlooked that you say you are now on c900, not c432.
There are no OTA updates for c900
I assuned you have followed the rollback guide as above, didn't you - the guide included c432 b182 (not c900 b182), in which case you should have been getting c432 OTA updates
zgfg said:
Oops, sorry, I have overlooked that you say you are now on c900, not c432.
There are no OTA updates for c900
I assuned you have followed the rollback guide as above, didn't you - the guide included c432 b182 (not c900 b182), in which case you should have been getting c432 OTA updates
Click to expand...
Click to collapse
Yes, I followed that guide, and I don't understand why I'm on c900. Can you help getting me out of this situation? Private message convo is fine by me too.
horesz1994 said:
Yes, I followed that guide, and I don't understand why I'm on c900. Can you help getting me out of this situation? Private message convo is fine by me too.
Click to expand...
Click to collapse
Follow the guide
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Hi, unfortunately my p10 drop on the floor from an high of 8 cm... Yes almost 4 in an the camera now has a strange yellow border. Of course this issue happens only on the color camera. The b/w camera works well.
The problem is that I have unlocked the bootloader. Can I do something to prepare the phone for rma?
I've the original oem info and of course the unlock code.
Thank you in advance
Maybe downgrade to nougat and then ota update to oreo will help. When I made debrand had unlocked bootloader and frp. Then did ota update to oreo and now have bootloader and frp properly locked.
lukastob said:
Maybe downgrade to nougat and then ota update to oreo will help. When I made debrand had unlocked bootloader and frp. Then did ota update to oreo and now have bootloader and frp properly locked.
Click to expand...
Click to collapse
What guide should I follow for this?
For debrand I used this guide:
https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
but I was doing it on nougat and I am not sure how it works with downgrading from oreo to nougat.
If you are already on oreo (and C432 region) you could try to use this guide :
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
tutorial 2 to flash the first full-ota oreo 8.0.0.360 from: http://pro-teammt.ru/firmware-database
but here is question to @Jannomag if it's certain that the script will work from newer to older oreo version. If so then try to use HiSuite to downgrade to nougat (for .360 it should be possible when hit firmware update -> switch to other version) and finally do the ota update to oreo. Be aware that I am not absolutely sure it will work, just suppose it should.
lukastob said:
For debrand I used this guide:
https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
but I was doing it on nougat and I am not sure how it works with downgrading from oreo to nougat.
If you are already on oreo (and C432 region) you could try to use this guide :
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
tutorial 2 to flash the first full-ota oreo 8.0.0.360 from: http://pro-teammt.ru/firmware-database
but here is question to @Jannomag if it's certain that the script will work from newer to older oreo version. If so then try to use HiSuite to downgrade to nougat (for .360 it should be possible when hit firmware update -> switch to other version) and finally do the ota update to oreo. Be aware that I am not absolutely sure it will work, just suppose it should.
Click to expand...
Click to collapse
Downgrading to a lower version as Dec2018 security patches can be indeed a problem but this shouldn't cause a brick. The updated should fail flashing /kernel and /ramdisk from update files.
Jannomag said:
Downgrading to a lower version as Dec2018 security patches can be indeed a problem but this shouldn't cause a brick. The updated should fail flashing /kernel and /ramdisk from update files.
Click to expand...
Click to collapse
I tried to flash B365 oreo over B384 with tutorial 2, update started as usual then reached 100% and phone switched off totaly. Now looks like bricked, can't switch on, charging doesn't work, when connected to pc system shows unrecognized USB SER device. Is there any hope to unbrick it?
I have the same. Send to warranty and they fix this by replace the Motherboard. Now i can't unlock bootloader because no offical codes and DC unlocker not support newest security patch from Huawei. Otherwise Phone works fine and i have extra warranty to 2022 .