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.
Good morning all:
I am having a problem with my phone.
The history...
Bought a P9 EVA-L19 in Belgium and it came originally with version B127 (I think).
So, I decided to root it and so I used SRKTool to unlock bootloader, install TWRP and root.
Problems started when I tried to update to a newer ROM.
It lost the original look and some functionalities, like the random imagens in lock screen and some original apps (FM Radio?)
In the meantime I managed to update to B137. The look was ugly but I managed to solve it using Nova Launcher.
Then the phone started giving me the message there was an update to B342 but everything fails.
I tried to reblock bootloader with SRKTool but it fails, I tried to download and install with dload method and fails.
So, I'm stuck with B137.
I even tried to debrand using this method: https://youtu.be/JZVsIKtdgV4
But after the first step "changing oeminfo and custom.bin" I even lost the keyboard so I gave up following the next steps.
So now my phone has a ROM EVA-L19900B137 and I can't find a way of updating to android 7.0 and I can't go back to the original ROM with all the functions.
Tha only thing I haven't tried is an Update using TWRP.
Is there a final release of 7.0 that can be flashed using TWRP?
Or even the original ROM?
(no, I know I am stupid but didn't made a backup before root and updates :crying: )
Thank you so much in, in advance, for your time.
I am not expert in these stuff but when I completely removed my system I installed a rom with different cust after that I got c900 then again I removed system and just installed the old cust "c185" and version b161 and then it worked like a charm even updates are working
your original dload method should be working. Just flash an original firmware with your original cust. This will lock your bootloader and turn your phone to original. You will even get the OTA updates.
After that if there is still no nougat update for your phone, there is 2 option. 1st one is check if there is an update that has the same cust number with your phone and apply it.
If not so, you can do a debranding procedure. Here is the link for it: https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
I managed to fix it.
Just in case someone has the same problem, I used the solutions/methods described on these threads:
1st
https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
2nd
https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
thank you guys for your replies!
Who has successfully updated to B387 or B388?
Or do we still have to wait for the Full OTA MF-PV?
If you use the OTA DNS method from firmware finder team, its possible to install the OTA-MF version of this.
Note that the firmware is not marked for installation that i can only assume means it's not passed all the QA tests.
I have not yet installed either of these.
I tried to install with firmware finder and update came up succesful but when I check I am still on B386.
I then tried to install the full image it failed.
Can't install the updates via dload method either.
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.
Hello guys, here is my problem. Some days ago when I was on stock - firmware B504, I decide to try Open Kirin AOSP (Treble). Then I realised that I want to go back to stock.
Everything went OK but now I am stuck on B395. When I try to update via FF (Auto and manual DNS method) in Updater app it show me that "Custom" update was found. And it always fails to even download!
Of course I tried OTA and FullOTA versions but with no luck.
In best case scenario - Is there any way to update with LOCKED bootlader?
My version is EVA-L09c432b395
Thanks
Sorry for the thread, found solution myself, HWOTA script by Tecalote