Database Develop

Problem with installing Nougat firmware and apps onto Huawei P9 EVA-L09. Please help!

Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.

Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.

chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.

I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...

I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &

tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!

If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....

chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.

Vns-l31c440 FullOTA-MF-PV b380 , b382, b383

Hello
In two files full ota mf pv. For c440 + (MM , bootloader, twrp MM flash update.zip + updatedatafull.zip, REBOOT)
2017.07.21 VNS-L31C440B383 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v91311/f2/full/update.zip
updatedatafull http://update.hicloud.com:8180/TDS/...-L11_ee_gb/update_data_full_VNS-L11_ee_gb.zip
2017.06.08 VNS-L31C440B382 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v87647/f2/full/update.zip
updatedatafull http://update.hicloud.com:8180/TDS/...-L11_ee_gb/update_data_full_VNS-L11_ee_gb.zip
Firmware for L31c440b380, on Firmware Finder FullOTA-MF-PV version.
2017.06.05 VNS-L31C440B380 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v87168/f2/full/update.zip
updatedatafull http://update.hicloud.com:8180/TDS/...-L11_ee_gb/update_data_full_VNS-L11_ee_gb.zip
VNS-L31C440B160
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v98030/f1/full/update.zip
If, you are looking to get,
* your bootloader code,
* to install TWRP for MM,
* to install or change your oeminfo.
this toolkit can help you.
https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873

Tried and failed through FF & proxy, Failed to authenticate installation package.

bananas33 said:
Tried and failed through FF & proxy, Failed to authenticate installation package.
Click to expand...
Click to collapse
Hello.
They are the two files to install with twrp since MM.
Or be in b370 and dload the first file (update.app).

Chisetdel31260 said:
They are the two files to install with twrp since MM.
Or be in b370 and dload the first file (update.app).
Click to expand...
Click to collapse
No TWRP here, all stock - I'm trying to install using Firmware Finder + proxy which worked well for the two parts needed for B160 to B370. It seems there's an additional check going on now giving the authentication error after a successful download and verification.

bananas33 said:
No TWRP here, all stock - I'm trying to install using Firmware Finder + proxy which worked well for the two parts needed for B160 to B370. It seems there's an additional check going on now giving the authentication error after a successful download and verification.
Click to expand...
Click to collapse
OK,
I never found firmware finder server.
I always use twrp.
I am currently, in c432, I will change oeminfo and test it.

Well, I installed it. Interesting, android security June 5 and kernel version June 5, 2017.
I was c432b380.
Downgrade MM (c432b160), I use the toolkit to change oeminfo to c440 and firmware c440b132.
Then, bootloader code, installs TWRP for MM, install update.zip and file datafull.zip, REBOOT.
everything is OK. works correctly.:good:

bananas33 said:
Tried and failed through FF & proxy, Failed to authenticate installation package.
Click to expand...
Click to collapse
Try to remove data of updater application and check again. This solution works for me

Tried clearing data for System Update, same problem Is that what you meant by updater application?
---------- Post added at 09:07 PM ---------- Previous post was at 08:31 PM ----------
If I put the phone into airplane mode the updater complains it has no internet access to authenticate, then fails as before; it really does look like there's another stage to this now.
I suppose I could try a factory reset and redo the FF+proxy approach but I don't think that'll work. Revert to B160 and try going straight to B380? Sounds like too much of a risk for me!
Without capturing the network traffic (or decompiling the updater app perhaps) to find out what it's up to it doesn't look like I'm going to get beyond B370 until someone somewhere else decides I can

Yes, this is that application what I mean. It's strange that system update download 4GB of data - I've got same problem and cleaning data and sending full package from Firmware Finder via proxy fixed problem, system update download just ~300mb.
Wysłane z mojego HUAWEI VNS-L31 przy użyciu Tapatalka

Did you go from B370 to B380? It seems that the updater in B370, for me at least, is phoning home for 'authentication' and being denied. If it's working for you from B370 then I wonder what it's using for the check... IMEI, IP address location lookup... hmm. I might try again via a VPN server in Poland.

Not exactly, I upgrade from B371 to B381.

C440? I've not seen odd numbers for the UK/EE firmware.

This is not important - on Your screenshot is a bug with a big update file and this is why You have error with authentication

Good point, it's double the size showing during a download

Still fails when the size is shown correctly and using a Polish VPN

bananas33 said:
Tried and failed through FF & proxy, Failed to authenticate installation package.
Click to expand...
Click to collapse
Same thing happens to me :/
I can't go from b370 to b380...
Anyone knows what is the difference between b370 and b380 and are there valuable reasons to keep trying to update our just stick with the b370?

If nothing else I believe it has a more recent Android security patch level. It looks like either the MM updater doesn't do the authentication check which is failing, or it does but b380 hasn't been cleared wherever that check looks. The only way I can see to check the first is to roll back to MM and try going straight to b380. Otherwise we're waiting on the authentication being given to b380.

bananas33 said:
If nothing else I believe it has a more recent Android security patch level. It looks like either the MM updater doesn't do the authentication check which is failing, or it does but b380 hasn't been cleared wherever that check looks. The only way I can see to check the first is to roll back to MM and try going straight to b380. Otherwise we're waiting on the authentication being given to b380.
Click to expand...
Click to collapse
Hello
I have tested b382
I see it looks very good.

Chisetdel31260 said:
Hello
I have tested b382
I see it looks very good.
Click to expand...
Click to collapse
I'm sure it's delicious, but will it install using FF+proxy or is a flash from custom recovery the only option? I'll give it a go later...

bananas33 said:
I'm sure it's delicious, but will it install using FF+proxy or is a flash from custom recovery the only option? I'll give it a go later...
Click to expand...
Click to collapse
Yes just MM, bootloader, Chinese twrp.
Sorry, I do not know how to do otherwise.
Firmware finder server I never succeeded.

No Service after OTA update to B386 on C432

Hi,
I got the B386 OTA update today and after installing my P9 EVA-L09C432 flashes "no service" in the status bar and a sim card symbol with exclamation mark is shown.
I tried removing and putting sim card back without success. Interesting is that when I restart the phone, after singing in for some seconds I can see the correct network operator in the status bar, before it changes to no service.
Under about phone the field IMEI shows Unknown, and Status does not open. So it looks like it doesn't read my sim card...
Any ideas what to try?
Thanks

Many reports on this! Rollback to MM, only way to solve it. Next time hit the 3 dots on the update page and Download the full package!

thanks, will give it a try

I had the exact same issue, a factory reset + dalvic cache wipe fixed it for me.

Didn't work for me. Had to rollback to B182. Going back to B360 didn't help.
How do I download the full package? Option is not available.

Downgrade to b300 and then flash b136 do it wipe data/system and cache in stock recovery

same trouble here, how can i fix it? wipe everything does not work for me

Rollback to B300, then install B182. You should get B383 offered as OTA. Install. After that it worked for me going to B386 with OTA update. No problems since.

theFloe said:
Rollback to B300, then install B182. You should get B383 offered as OTA. Install. After that it worked for me going to B386 with OTA update. No problems since.
Click to expand...
Click to collapse
And how can I rollback to b300?
Can I install from b386 the b383 or I must go to b300 ?

MartinDimchev said:
Many reports on this! Rollback to MM, only way to solve it. Next time hit the 3 dots on the update page and Download the full package!
Click to expand...
Click to collapse
No bugs with Full Update, 386 working for me

theFloe said:
Rollback to B300, then install B182. You should get B383 offered as OTA. Install. After that it worked for me going to B386 with OTA update. No problems since.
Click to expand...
Click to collapse
Any updates after that? I have re-branded EVA-AL10 to EVA-L19C432 and latest I have is 386. There are no more updates. Have you find the way how to update higher then 386? No of existing methods works...
Always get authentication error or update failed.

gkirko said:
Any updates after that? I have re-branded EVA-AL10 to EVA-L19C432 and latest I have is 386. There are no more updates. Have you find the way how to update higher then 386? No of existing methods works...
Always get authentication error or update failed.
Click to expand...
Click to collapse
HWOTA method must work if you have properly rebranded to L19c432
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3

[HELP NEEDED] PRA-LX1C432B170 currently, no update found after debranding

Hi all,
I have a PRA-LX1 that had a Vodafone customization. The suddendly it just factory resetted itself (I SWEAR, I had it in my pocket) only to find it with a NRD90M firmware. Sick of this customization, I unlocked the bootloader and flashed a C432 oeminfo. I then tried to flash PRA-LX1C432B212 downloaded via FirmwareFinder, but went in bootloop. Well, no panic: fired up eRecovery, it installs PRA-LX1C432B170. I installed it and after the factory reset I now have a working phone. My only question is: is B170 really the latest available version I can get via OTA? I'd like not to lose the OTA feature so I don't have to rely on Firmware Finder to get updates every time... is there anything I can do?
A slightly related question: one thing I tried is to download B212 with FirmwareFinder. I managed to use the in-app proxy and actually found an update, but once it downloaded it didn't apply because of some failed verification (I don't have the phone with me now, but it was something AFTER the integrity check, so it's not something related to the download. I also verified the availability of B212 in FF by clicking the "Check Firmware Access" button and it's actually not available, like any other version I tried. Does this mean I won't get any OTA in the future?

Here is a discussion, probably related to your problem. Are you using TWRP Recovery when installing the OTA update or the stock recovery?
I read somewhere that Huawei OTA updates won't install on custom recoveries.

[Guide] Nougat from scratch

I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE, USE AT YOUR OWN RISK​
I struggled to find all pieces of information needed so i am making this guide if anybody in future needs to fix bricks or just get back to stock rom, you can also debrand your phone if you use different oeminfo
Firmware for VNS-L21C432
B160 B370 DS OEMInfo
B161 B371 SS OEMInfo
Click to expand...
Click to collapse
Flash correct oeminfo using TWRP
Download B160 or B161 using FF (PC)
Put UPDATE.APP from update.zip in folder 'dload' in root of the sdcard
Turn the phone on while holding both volume keys, hold until huawei logo dissapears
Wait for installation to finish
Install B370 or B371 using FF proxy
Enjoy
NOTES​
Odd numbered updates are for single-sim, even numbered ones are for dual sim
FullOTA-MF-PV updates must be used when upgrading to nougat from marshmellow, otherwise half apps will be missing
FF (Android) can be installed without play store by using Yalp store
Upgrading from B160/161 to B370/371 and further using dload method did not seem to work for me
B160/161 firmware can be downloaded using FF (Android) application too in case computer isn't available
Click to expand...
Click to collapse

Using this method gave me bootloops. If anyone else gets them, what I did was:
1)Wait for installation to finish
2)Turn the phone off completely
3)Hold VolUp+Power and release on Huawei logo
4)Factory reset in the menu that appears
5)Reboot
And no more bootloops!