Can not update l29636B393 to B394 - Huawei P9 Plus Questions & Answers

Recently I saw on FF that there is an full update to b394. However when I try to download it using the proxy method it fails every time. Any ideas?

Related

B166 > B378-FULL How I did it.

Basically I've followed a few different methods and got it to work.
Using the firmware finder apk I downloaded the B182 (full) rom.
While this is downloading... Using es Explorer or similar create a folder called hwff in the root of your main storage.
When it has finished downloading...
Check the md5.
Unpack it.
Move to dload.
Then turn it off.
Turn back on using the 3 finger method.
This will then install B182.
Note: when it reboots it will stay on the Huawei red logo for a few minutes.
Let it finish and you will have B182 working.
***********
Now to update to B361.
I used the combination of Huawei updater 2.0 and HiSense to update.
It found it with no issues and I just left it to update.
**********
Update to B378-FULL
This was simply an OTA update through the normal Settings > Update menu.
Fairly painless, just time consuming really.
Sent from my EVA-L09 using Tapatalk
Man the update path on these huawei's is killing me. I've only just taken the plunge. Accidentally turned my c432 into a c900 by double flashing a b166 rom. Took me best part of a day to get it back to c432b166!
The amount of slow crappy downloads we have to make in order to make incremental upgrades. Is there not a way that we can just go straight into a later build without all these rollups?
You can just use the proxy install method within the Firmware Finder app, its very easy.
Just google "how to. using firmware finder youtube" as I cant post direct link, then 99% of the work is done for you
Hutchism: Sadly not, from what I've seen you can only jump to Nougat from B182 and nothing earlier - Don't ask me why... Makes NO sense!
Natchi: The proxy install method did not work for me. That's why I did it the way I did... All I know is that it worked and I'm running Nougat.
BigDaddyBlue said:
***********
Now to update to B361.
I used the combination of Huawei updater 2.0 and HiSense to update.
It found it with no issues and I just left it to update.
**********
Click to expand...
Click to collapse
Hi there, followed your first step with no issues - finally on B182! Struggling to find the B361 update using Hisuite (windows PC), HiCare (app) or the Update app.
Any advice on how to do this? What is Updater 2.0 please?
Thanks very much!
Sam
Hi Sam,
You can find the updater here;
https://forum.xda-developers.com/p9/development/huawei-p9-p9-plus-firmware-updater-t3435873
Thanks,
Jay.

Unable to install B382 (for VIE-L29C636)

Straight to the point, has anyone successfully updated to B382?
I've tried via FirmwareFinder, it downloads successfully, but during install it says Unauthorised, removes files, and remains the same.
Trying via the dload/sdcard method, and it gives an error @ 5%, and then prompts to reboot the phone.
Have tried going from B190/202/362/370 but no luck each time. Tried with bootloader unlocked & locked, have since done a factory reset once on 370, and still no progress.
Will remain on B370 for now, B382 appears to only be a security patch, but it would be nice to have the peace of mind being on the latest (for Huawei anyway) patch.
CAN YOU GIVE ME LINK FOR b370 ? I HAVED TO TRY WITH FIRMWARE FINDER BUT NOT WORKING, THANK YOU. and i have a same problem when update B382, i think it's a beta version .
midouban87 said:
CAN YOU GIVE ME LINK FOR b370 ? I HAVED TO TRY WITH FIRMWARE FINDER BUT NOT WORKING, THANK YOU. and i have a same problem when update B382, i think it's a beta version .
Click to expand...
Click to collapse
I actually used Firmware Finder to update to B370. Although initially I was having issues getting to that as well, from B362 both via dload & FF.
Ended up rolling back to B190 (via dload), then using FF went to 362 > 370.
Here's the LINK to the update.zip anyway.
djyoshii said:
I actually used Firmware Finder to update to B370. Although initially I was having issues getting to that as well, from B362 both via dload & FF.
Ended up rolling back to B190 (via dload), then using FF went to 362 > 370.
Here's the LINK to the update.zip anyway.
Click to expand...
Click to collapse
i'll try now, but if i use FF to update B370, i try 3 version B370, but i see only download file =5.78mb, then it downloading and fail to update , thank you !
midouban87 said:
CAN YOU GIVE ME LINK FOR b370 ? I HAVED TO TRY WITH FIRMWARE FINDER BUT NOT WORKING, THANK YOU. and i have a same problem when update B382, i think it's a beta version .
Click to expand...
Click to collapse
midouban87 said:
i'll try now, but if i use FF to update B370, i try 3 version B370, but i see only download file =5.78mb, then it downloading and fail to update , thank you !
Click to expand...
Click to collapse
Check one of the other threads in here on how to update via FF, step by step.
You need to go back out and check for updates again. Full size is def not 5mb.
In order to update to B382 NOW, you need to unlock your bootloader and use TWRP to update it UNLESS you wait till it official launch.
djyoshii said:
Check one of the other threads in here on how to update via FF, step by step.
You need to go back out and check for updates again. Full size is def not 5mb.
Click to expand...
Click to collapse
thanks for help, but i have to try manytime , it's alway show 5.78mb. and i know it fail. i try dload method but still fail to verify at 5%.
jhleo1 said:
In order to update to B382 NOW, you need to unlock your bootloader and use TWRP to update it UNLESS you wait till it official launch.
Click to expand...
Click to collapse
Bootloader unlocked.
update.zip for B382 downloaded.
Is it as simple as flashing that zip in TWRP?
Anything else required? Anything to be aware of?
As mentioned above, I've only updated via dload & FF previously, was not aware of any other method/s.
Thanks
I didn't not tried since bit troublesome for me to backup all data etc. I rather wait for final release. You may try to google this firmware and TWRP method was highlighted. Anyway do it at your own risk.
djyoshii said:
Bootloader unlocked.
update.zip for B382 downloaded.
Is it as simple as flashing that zip in TWRP?
Anything else required? Anything to be aware of?
As mentioned above, I've only updated via dload & FF previously, was not aware of any other method/s.
Thanks
Click to expand...
Click to collapse
b382 is still unofficial, if u insist on installing it try this method:
https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
The firmware already approved by Huawei. Just use FF to update will do.
wizix said:
b382 is still unofficial, if u insist on installing it try this method:
https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse

C432 p9 on EMUI 4.1.3, no OTA since then

I'm sorry if this has been answered before, but I'm amazed Huawei can't help me update.
I'm in UK, and still on MM. I updated by forcing it from 182 to 210 but I want to avoid breaching warranty by installing twrp.
It's working fine, I am happy with battery life, I just wanted to get the current stable version of Nougat.
Huawei suggest continuing to wait. Any other options for me within the warranty?
Well its simple... Manually ....
vampirian said:
Well its simple... Manually ....
Click to expand...
Click to collapse
You mean the hisuite download?
No i mean manually. Root debrand, download manually firmware and install.
Hi, I would recommend using firmware finder from the play store and installing using the in app proxy method. It's always worked perfectly for me on any of my Huawei phones.
Just make sure you use the download latest full package option in system update by selecting from the three dots
Exactly but sometimes its not working so he better change DNS
My phone is second hand, seems to be debranded, L09C432B210 forced by putting the update.app in dload. It doesn't work for B360.
I have unticked unlock OEM.
I have created apn for proxy setting, and once L09C432B360 Fullota-mf-pv is downloaded, I'll install it via in app proxy.
Thanks for the explanation. If I have misunderstood please let me know.
L09C432B360 2017.01.05 failed the imei check. I'll try another version 2016.12.23 which passed the check.
In app proxy hasn't been successful on my current settings.
The default apn for ee is greyed out so I made a fresh apn with localhost server, without the mms or security settings.
Update, dload folder, update.app method failed after 5%
I found a way to change dns without rooting, installed dns66 and applied ff change dns setting.
However though updater finds the right file, and I can connect, it doesn’t install. Either download fails partway, or install fails.
Is persistence the key, or should I try another file?
Patxperia said:
I found a way to change dns without rooting, installed dns66 and applied ff change dns setting.
However though updater finds the right file, and I can connect, it doesn’t install. Either download fails partway, or install fails.
Is persistence the key, or should I try another file?
Click to expand...
Click to collapse
You have to do all the procedure mate. and i mean ALL even de-branding again to C432 because seems your provider gave you a touched C432 firmware. Which means unlock, debrand relock , update.
Now follow one of these guides on how to upgrade your phone.
use search or use this https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
PS: Next time your posts on guides and not on general topics
I received OTA updates bringing me to b395 Nougat. No unlock or debranding necessary

Update with FirmwareFinder

Maybe a dumb question: I'm currently on B360 (VTR-L09 8.0.0.360) and I see that in Firmware Finder the B365 is available and approved for my IMEI.
Is there any risk on installing theis trough FF instead of waiting for the OTA? (like risk on bootloop etc)
Will I still be able to have OTA updates in the future when updating trough FF or will I always have to maual update with FF afterwards?
Hello. It won't be a problem but if you want my advice go back to the previous stable build of nougat (B185 I believe), to start clean, through HiSuite using your PC, and the you'll receive automatically the latest B365 through ota. And always choose the option "download latest full package"
johnxarma said:
Hello. It won't be a problem but if you want my advice go back to the previous stable build of nougat (B185 I believe), to start clean, through HiSuite using your PC, and the you'll receive automatically the latest B365 through ota. And always choose the option "download latest full package"
Click to expand...
Click to collapse
How can you go back to B185 when the phone is already in OREO?
Invicta said:
How can you go back to B185 when the phone is already in OREO?
Click to expand...
Click to collapse
Connect your phone to your PC and download HiSuite. From there you can choose the option to rollback to a previous firmware. In this case nougat
it doesnt work mate, this option is no longer available
johnxarma said:
Hello. It won't be a problem but if you want my advice go back to the previous stable build of nougat (B185 I believe), to start clean, through HiSuite using your PC, and the you'll receive automatically the latest B365 through ota. And always choose the option "download latest full package"
Click to expand...
Click to collapse
Why would you do that? I've updated from B360 to B365 with FF without any problems. So what's the advantage of going back to Nougat?
djg269 said:
Why would you do that? I've updated from B360 to B365 with FF without any problems. So what's the advantage of going back to Nougat?
Click to expand...
Click to collapse
I read somewhere that FF breaks the ota and acting weird sometimes. So I rolled back to nougat, waited 2 3 days and Oreo update appeared normally.
johnxarma said:
I read somewhere that FF breaks the ota and acting weird sometimes. So I rolled back to nougat, waited 2 3 days and Oreo update appeared normally.
Click to expand...
Click to collapse
FF doesn't break anything as it's just an intermediate between your phone and OTA server.
If you do everything according to instructions you will not have any troubles and normal OTA updates will be still available. I always update via FF using DNS method and it works like a charm.

Rebranded EVA-AL10 to EVA-L19C432....

Rebranded EVA-AL10 to EVA-L19C432....
Anybody find a way to flash update higher then 386?I am unable to update to 398(or any higher then 386)...
So, I tired:
1. flashed EVA-L19 partition table (DCUNLOCKER Phenix ), EVA-L19C432B360, got OTA to 378 then then to 386
futher updates possible but only manually. However, there a big problem - long delay placing calls and miss some incoming calls
2. flashed EVA-AL10 partition table(same tool), EVA-L19C432B360, got OTA to 383, then to 386
no futher updates possible - ota, sd or FF DNS, or FF Proxy.
3. Keep EVA-AL10 partition table, dowgraded to MM EVA-L19C432B182, then got OTA 383, then OTA 386..
no futher updates possible - ota, sd or FF DNS, or FF Proxy.
Seems to be problem with partition table. Does anybody overcome this issue. Does anybody have partition table for EVA-L29C636?(dgtks file)
gkirko said:
Rebranded EVA-AL10 to EVA-L19C432....
Anybody find a way to flash update higher then 386?I am unable to update to 398(or any higher then 386)...
So, I tired:
1. flashed EVA-L19 partition table (DCUNLOCKER Phenix ), EVA-L19C432B360, got OTA to 378 then then to 386
futher updates possible but only manually. However, there a big problem - long delay placing calls and miss some incoming calls
2. flashed EVA-AL10 partition table(same tool), EVA-L19C432B360, got OTA to 383, then to 386
no futher updates possible - ota, sd or FF DNS, or FF Proxy.
3. Keep EVA-AL10 partition table, dowgraded to MM EVA-L19C432B182, then got OTA 383, then OTA 386..
no futher updates possible - ota, sd or FF DNS, or FF Proxy.
Seems to be problem with partition table. Does anybody overcome this issue. Does anybody have partition table for EVA-L29C636?(dgtks file)
Click to expand...
Click to collapse
Ifnproperly rebranded and not affected by your later flashing, HWOTA will work
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
zgfg said:
Ifnproperly rebranded and not affected by your later flashing, HWOTA will work
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Click to expand...
Click to collapse
Can you please elabiorate.... You suggesting that i have I have issue with recovery? and to re-flash recovery partition from L19 will work?
JUst one question - if there are issue with my recovery then why i have no problem to install firmware up to v 386?
and if i uninstall updates for SYstem Updater, I can download new update and verify it but when phone reboots I got to 5% and then it said install failed(without any explanation).
gkirko said:
Can you please elabiorate.... You suggesting that i have I have issue with recovery? and to re-flash recovery partition from L19 will work?
JUst one question - if there are issue with my recovery then why i have no problem to install firmware up to v 386?
and if i uninstall updates for SYstem Updater, I can download new update and verify it but when phone reboots I got to 5% and then it said install failed(without any explanation).
Click to expand...
Click to collapse
Not sure what is the latest OTA update for L19, but definitely lower number than L09.
And saying that HWOTA method is proven for upgrading to approved or even unapproved builds (O've used it several times myself too)
And one more - you can flash by the 'old' DLOAD method only FulOTA-MF-PV releases, but for the last 6-7 months there were no more PV builds, hence DLOAD method doesn't work for new releases
PS: New thread on (new) HWOTA7 for rebranding, upgrading, rolling back to stock, etc
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849

Categories

Resources