Database Develop

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.

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.

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

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.

Offical OTA problem update - repeat same notification - patch

Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?

lorreca said:
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
Click to expand...
Click to collapse
sounds like a bad update.. you could restore via erecovery

lorreca said:
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
Click to expand...
Click to collapse
Have you Factory Reset it?

.156 had 3 patch updates to it, so I would suggest to install until they go away. Not sure how many times you have seen this?

fregor said:
.156 had 3 patch updates to it, so I would suggest to install until they go away. Not sure how many times you have seen this?
Click to expand...
Click to collapse
I already updated several times...

oxfordmark said:
Have you Factory Reset it?
Click to expand...
Click to collapse
I would like to avoid to do a factory reset and set all the phone again. If when stable 9.0 Pie arrived I won't be able to update because of this, so I will do a factory reset.

fuzziion said:
sounds like a bad update.. you could restore via erecovery
Click to expand...
Click to collapse
Have you got a link for the guide?

lorreca said:
I already updated several times...
Click to expand...
Click to collapse
Wich patch are you on then? .157 is out as well, so you could just wait until you get that one.

fregor said:
Wich patch Are you om then? .157 is out as well, so you could just wait until you get that one.
Click to expand...
Click to collapse
I should already have received the september Google patch, but nothing at the moment...

fregor said:
Wich patch are you on then? .157 is out as well, so you could just wait until you get that one.
Click to expand...
Click to collapse
157? Country?
I'm on 156 (patch3) in Croatia and there is no update when I check...

install magisk with both checkboxes activated

lorreca said:
Have you got a link for the guide?
Click to expand...
Click to collapse
Turn off your phone hold volume up + power until your phone boot to erecovery after that it's pretty simple just click on restore and follow the instructions

i had the exact same issue. i don't recall exactly, since i tried multiple different things, but i either did a factory reset or reflashed the entire .156 from firmware finder to get the update to stick.
i did rebrand to C432 and had twrp installed if you're in the same boat.

Danchibald said:
157? Country?
I'm on 156 (patch3) in Croatia and there is no update when I check...
Click to expand...
Click to collapse
Norway, C432
Looks like .159 is just around the corner as well.

I'm also on C432 but latest i recieved is 156 (patch3)... nothing further

IceFoxX said:
install magisk with both checkboxes activated
Click to expand...
Click to collapse
With Magisk I will lost OTA update...

fuzziion said:
Turn off your phone hold volume up + power until your phone boot to erecovery after that it's pretty simple just click on restore and follow the instructions
Click to expand...
Click to collapse
Ah ok, is like to do a factory reset right?
Im going to wait for 10 november (pie release) and of doesnt receive the OTA i will do that

bravo261 said:
i had the exact same issue. i don't recall exactly, since i tried multiple different things, but i either did a factory reset or reflashed the entire .156 from firmware finder to get the update to stick.
i did rebrand to C432 and had twrp installed if you're in the same boat.
Click to expand...
Click to collapse
I'm already on C432 (rebrended from demo/retail) but I would prefer to keep stock with OTA until root for Pie coming. Then i will root again.

lorreca said:
With Magisk I will lost OTA update...
Click to expand...
Click to collapse
Yeah got the same issue..uninstall magisk.. install magisk manager activate both checkboxes ( keep force encryption + keep dm verity (without keep dm verity you will lose the patches)) download the zip and flash magisk with twrp and you will still have patch03
Sadly i dont know the source anymore

lorreca said:
I'm already on C432 (rebrended from demo/retail) but I would prefer to keep stock with OTA until root for Pie coming. Then i will root again.
Click to expand...
Click to collapse
i'm not talking about root. i'm suggesting you perform a factory reset with the stock recovery, and if that doesn't work, then install twrp and use hurupdater with the firmware files to really go back to the freshest install. using hurupdater will install the stock recovery as well. that got my updates to finally stick