Database Users

Final Marshmmallow is out now ! B522

Official marshmallow ( not beta) is finally out. Check out this link
B522
http://www.huaweiblog.de/android/marshmallow/huawei-mate-7-marshmallow-update-b550-offiziell-final/

Thanks, already installed. I received notification this morning !

jarbi said:
Thanks, already installed. I received notification this morning !
Click to expand...
Click to collapse
I also live in Belguim, I am on B331 but I have not received the update? Anything special you did to get this update?

tnx man
any news for mt-tl10?

Hello!
I'm new on this forum, but I realy like your work! My questions is: I'm now on B511 version of android 6.0; is it possible to update to this version (B522)? Or what would be the proper way to do it? I'm from Slovenia, Europe and my phone is MT7-L09.
Thanks guys!

Are we sure we will not hear this is the beta in a few days?

Sure it's not a beta? If so, what version I have to be to receive the Ota?

Can any one explain if you need to reinstall the device ? will all data be deleted ?
Can also some one explain on what version you need to be on to be able to update ?
I am on B331 currently (L09)

What about tl10?

I don't understand a single word from this german site.Do we need b513 to update with b522? Or it just can be updated from b331? Is this final ota official? Or just another beta build? For sure its for L09\2GB version thats only clear thing in text. Can anyone explain is it better than b513 and is there anything new? Is update menu in settings back?
Sent from my HUAWEI MT7-L09 using Tapatalk

Hynic90 said:
I don't understand a single word from this german site.Do we need b513 to update with b522? Or it just can be updated from b331? Is this final ota official? Or just another beta build? For sure its for L09\2GB version thats only clear thing in text. Can anyone explain is it better than b513 and is there anything new? Is update menu in settings back?
Sent from my HUAWEI MT7-L09 using Tapatalk
Click to expand...
Click to collapse
I agree there is some questions to be answered...
Also more confirmation if this is official and final...
Why I ask this is cause Huawei support around the glob is crap, I would only trust chinese support.
For instance I asked 2 months ago Huawei support in sweden when he thought Marshmallow would be released
he said that it has already been released in some markets... if the confirmation comes from china I trust it but not otherwise
since Huawei only have "fake support " in most countries where they will tell you to please restart your mobile phone and re install the phone etc besides that they do not know a ****
---------- Post added at 01:32 AM ---------- Previous post was at 01:15 AM ----------
The next final marshmallow update is coming up. This time is the extremely popular Mate 7 with Android 6.0 and 4.0 EMUI. It bears the name:
MT7-L09C432B522
On demand, Huawei has informed us that it is the final version for MM Mate. 7
The series join because both the P8 lite, the Mate S, the P8 and also the honor 7 have been supplied ? from the Far East with the coveted sweetness named Marshmallow (which is incidentally also excellent reintun for the hot cocoa. Huawei adopt because already a lot trouble, even though there are times comes in this context to the prophets of doom. this we hear but studiously and look forward rather than a working device.
The now presented and distributed via OTA update is of course again rolled out in waves. Your can watch the way with your wireless display introduced in about, first very little and in the end, more and more. The duration, the amount of time so that a rollout takes total to complete, until all are supplied is given always different. You should there but so get in the next two weeks. Of course it may be that Huawei first the BETA User supplied and brings the update shaft for rolling only after. Can not say or verify, as we currently know precisely only by a BETA users who we so firmware received update for its mate. 7 Thanks to the context of wool!
You will definitely be the next time the marshmallow update on your Mate 7 (in the branded devices such as Vodafone or Deutsche Telekom can take a little longer). It may of course be that the full version then has more MB than that which is currently provided to the BETA testers via OTA. Our version was approved by the MT7-L09C432B513 installed Coming. This should therefore be a prerequisite. If you can no longer wait or want, then flash your device manually, are but you aware of the dangers. It could be that your device after running bad, or not at all. Never change a running system. ? But as we now already know you, our warnings are you can not stop and you will not be able to leave. but Ok, then start please with here:
data backup
Before you charge ahead secures to any case your data, just what one should always do before an update. If you need to simple instructions, just look at our: Huawei backup - full backup
Furthermore, it should have your Micro SD card at least 8GB memory.
download
The firmware version MT7-L09C432B522 you can look in my mirror MEGA download / download.
installation
Normal method
The downloaded file "update.zip" copy in the to be created / or pre-created "dload" folder and this in turn to the root directory (which is the top level) of your Micro SD card (IMPORTANT! THE UPDATE.ZIP NOT UNZIP! !!)
Tippe following in the phone set string: * # * # 2846579 # * # * and then Switch to "ProjectMenu" -> "Software Upgrade" -> "SDCard Upgrade" and confirm with "OK"
It starts the update process and thereafter start your Mate 7 new
Force update method
The downloaded file "update.zip" copy in the to be created / or pre-created "dload" folder and this in turn to the root directory (which is the top level) of your Micro SD card (IMPORTANT! THE UPDATE.ZIP NOT UNZIP! !!)
Make sure your Mate 7 is turned off and the micro SD card with the "dload" folder is inserted. Now hold the VOLUME UP, VOLUME DOWN button and the POWER button is pressed, until a menu appears. Change the connection to the "Software Upgrade Mode".
The update process will start and your Mate 7 then starts automatically again.
After the successful update of your Mate 7 a manual Factory Reset is recommended.
they also write on the blog " The download, installation and use of the firmware is at your own risk.
We assume no liability for the functionality and compatibility of the software.
Damages on your hardware, we assume no liability.
Also for the correctness of the contents is no liability. The firmware version has not been tested by us. "

not a beta (for the ones wondering) it just shows up in my update app

when i try to install it by 3 bottoms that number doesn't work with zip update just with update.app
so it reach 5% in like 3 sec and then fail
so what should i do to work ??
i am on B513 mt7-l09

[email protected] said:
when i try to install it by 3 bottoms that number doesn't work with zip update just with update.app
so it reach 5% in like 3 sec and then fail
so what should i do to work ??
i am on B513 mt7-l09
Click to expand...
Click to collapse
maybe this update is not compatible with the Marshmallow beta version ?
This is a update version and not full version so some one really need to clarify which versions that are compatible with this update!

Any chance some one who has it could do a clean twrp backup and maybe put on mega, it would be muchly appreciated.
TIA
Sent from my JAZZ using Tapatalk

Hi everyone, My phone is Mate 7 TL-09 and firmware was B513 till yesterday I've got B522 notification and installed it. I installed Huawei ID and Huawei Cloud app, so I think, maybe, I got OTA update because of that. These two allow you to backup contacts, notes, ... to your Huawei cloud.
Huawei Cloud+ app: https://mega.nz/#!KVNzzaDL!AOVdRCttM27utV7N937zM__GSZxpyNvRjCtu0itQR1wL
Huawei ID app: https://mega.nz/#!3EdS0L4K!U8cBJw1kB-qlvQF838W-id78vFDMKQeKOyJ2_F1bJ_U
Also my B513 firmware was rooted and my phone recovery was twrp 2.8.7 mobopx tool.
In Notification of B522 update it said it's Full version, first it showed me a 1.22 GB File and I got a backup and return and it was 486 MB.
B522 download link: https://mega.nz/#!GRlzxJZS!x_dSYDOIofOQD-NeoIZ8sT2V6SvtgnPfNkMDKtBCt2g
The changes are: some minor bug fixes, "Backup" and "health"app added, still missing local update and a little phone smoother.
For installing of B522, it says your phone should not be rooted so I unroot and installed stock recovery of android 6 using mpbopx tool. Then downloaded and using automatic install and it reset two times and installed without any error. I installed twrp again and "supersu 1.64 pro.zip" helped me to root again. I've created a nandroid backup, upload in progress.

Sassan_Payehdar said:
Hi everyone, My phone is Mate 7 TL-09 and firmware was B513 till yesterday I've got B522 notification and installed it. I installed Huawei ID and Huawei Cloud app, so I think, maybe, I got OTA update because of that. These two allow you to backup contacts, notes, ... to your Huawei cloud.
Huawei Cloud+ app: https://mega.nz/#!KVNzzaDL
Huawei ID app: https://mega.nz/#!3EdS0L4K
Also my B513 firmware was rooted and my phone recovery was twrp 2.8.7 mobopx tool.
In Notification of B522 update it said it's Full version, first it showed me a 1.22 GB File and I got a backup and return and it was 486 MB.
B522 download link: https://mega.nz/#!GRlzxJZS
The changes are: some minor bug fixes, "Backup" and "health"app added, still missing local update and a little phone smoother.
For installing of B522, it says your phone should not be rooted so I unroot and installed stock recovery of android 6 using mpbopx tool. Then downloaded and using automatic install and it reset two times and installed without any error. I installed twrp again and "supersu 1.64 pro.zip" helped me to root again. I've created a nandroid backup, upload in progress.
Click to expand...
Click to collapse
decryption key ?

somboons said:
decryption key ?
Click to expand...
Click to collapse
check the links again.

battery drains very fast on b552...100% to 91 % to 5h scree off

Well it would be nice if we could get better information for us normal people and non-hackers and rooters too ?
In fact all people who have waited for final marshmallow version do not care about any of that staff that is why we did not install the beta.
So leet keep all this "root" talk in another thread. The final version seem to be here so lets instead discuss what versions that are compatible with this official update.
I have never got any updates pushed on OTA so I most install this manually

Huawei P8Lite Notification/Double Tap problem

Hi there, I'm experiencing some issues with my new bought phone Huawei P8 Lite(ALE-L21 Single-Sim locked in Vodafone Romania).
The first issue and that's kinda important is the notification one; I won't receive for example Facebook's Messenger messages, when phone it's locked or often on home screen. I've given priority on that damn task killer, I did anything recommended on all forums and sites, even from WhatsApp's thread about receiving delayed notifications, I also installed that Push notifications app;
When I said I often receive notifications on my home screen it's beacuse they are delayed I think. I want to fix this so bad so I made a thread about this. Everything has priority, even networking apps, the lock screen has the default theme, I really don't know what to do anymore.
And the second one is about the common double tap execution when writing or tapping or anything else. I'm experiencing some troubles there too, especially when I'm writing, the phone is executing the second tap without my action and I don't know how to fix that.
I'll let some informations about my phone..
I've purchased this phone on 31th of May, 2016
The model number is ALE-L21/Single Sim
The build number is ALE-L21C02 B140
Android 5.0.1 with EMUI 3.1
Phone isn't rooted or modified, and I want to fix these without rooting if it's possible.

well .. you have 2 options:
1. Check notifications manager from notifications panel
2. Upgrade to marshmallow: upgrade to b170 then upgrade to b564 and hope this will fix your problem xD
About the double tap: that is an often problem on this huawei and you can fix that by upgrading to last version of marshmallow.

Can't find an notification manager, may you show me where it is?
And about the versions I found only b170 but it's from spain and I told you that I'm a little bit scared beacuse it's locked in Vodafone Romania

It doesn't matter from where it is, it's official from huawei. It doesn't matter if it's locked in vodafone romania, mine was also locked in vodafone romania, and i have b565 now
You won't brick your phone.
Here it's notification manager:
If you can't find notification, it means that this option is not available on 5.0

May you give me some links to the updates, please? I really don't want to f**k up the phone

Update via local update: make a folder named dload on your internal memory or sdcard an put the update.app inside of this zip
Then, update with the same procedure to 6.0 by installing update.app from this zip

ALE-L21C02 B140
It looks that Your phone is branded and I don't know if You will have balong bug after upgrading the system to B170 and upper. I recommend you to make a debrand process but it needs an unlocked bootloader. When You decide to do it remember to have done a backup of Your data!

Azaradel said:
ALE-L21C02 B140
It looks that Your phone is branded and I don't know if You will have balong bug after upgrading the system to B170 and upper. I recommend you to make a debrand process but it needs an unlocked bootloader. When You decide to do it remember to have done a backup of Your data!
Click to expand...
Click to collapse
Oups, didn't read c02 xD
But i don't think it's a big problem, even if he has balong, he can install vendor or change it.

Could you explain me what's "balong" and "vendor"; I'm sorry but I'm completely parallel with these kind of "deep" stuff in phones..

Balong is a bug that appears when you are installing a firmware that is not for your country and it's a problem with the version not showing properly. The vendor file will fix it.
Sent from my ALE-L21 using XDA-Developers mobile app

And where can I find the vendor file, to avoid the balong bug?
And also is it a problem if I update my One-Sim Phone with an Dual-Sim FW?

That's strange, why are you having b140 on single sim?
And why you want to update with a dual sim version on single sim?
Just install b171 first then install b551, at last install b565 via ota.
Vendor file is inside firmware archives.

Hi,
I bought this phone Huawei P8Lite (ALE-L21) without being connected to any network carrier.
Before I start to unlock bootloader, install TWRP and Root the phone, I checked the system version and EMUI and the rest of the information needed before update to Marshmallow 6.0.
Before I had the following info:
OS: Lollipop 5.0.1
EMUI: 3.0
(ALE-L21C432B200)
At this point I had no update via OTA - (to the Android 6.0 Marshmallow), and made only unlock bootloader
After several hours of searching, I found that I could do a local update (B560 Marshmallow Firmware [Europe] - Dual SIM) available by Huawei.
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
I checked Huawei PDF on how to do the update but does not mention Required Version and proceeded to local update.
So far so good, the phone did the update without any problem.
I checked OTA for new update and the phone made update for B564 - Also mentioned by Carbontesla.com
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
Phone did the update (B564) without any problem, then I proceed installing TWRP and then I root the phone.
All work beautifully, but I noticed that whatever the application I use both SMS, Facebook, Whatsapp, GMail, takes too long to receive notifications.
I do not know if he was already with this bug when the phone was with Lollipop 5.0.1 with (ALE-L21C432B200) and EMUI 3.0
I have not had time yet to reset the phone to factory settings and verify that fixed the bug, I will do this weekend week :fingers-crossed:
Can someone help me?

pedra3000 said:
Hi,
I bought this phone Huawei P8Lite (ALE-L21) without being connected to any network carrier.
Before I start to unlock bootloader, install TWRP and Root the phone, I checked the system version and EMUI and the rest of the information needed before update to Marshmallow 6.0.
Before I had the following info:
OS: Lollipop 5.0.1
EMUI: 3.0
(ALE-L21C432B200)
At this point I had no update via OTA - (to the Android 6.0 Marshmallow), and made only unlock bootloader
After several hours of searching, I found that I could do a local update (B560 Marshmallow Firmware [Europe] - Dual SIM) available by Huawei.
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
I checked Huawei PDF on how to do the update but does not mention Required Version and proceeded to local update.
So far so good, the phone did the update without any problem.
I checked OTA for new update and the phone made update for B564 - Also mentioned by Carbontesla.com
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
Phone did the update (B564) without any problem, then I proceed installing TWRP and then I root the phone.
All work beautifully, but I noticed that whatever the application I use both SMS, Facebook, Whatsapp, GMail, takes too long to receive notifications.
I do not know if he was already with this bug when the phone was with Lollipop 5.0.1 with (ALE-L21C432B200) and EMUI 3.0
I have not had time yet to reset the phone to factory settings and verify that fixed the bug, I will do this weekend week :fingers-crossed:
Can someone help me?
Click to expand...
Click to collapse
Check battery management and give access to work in the background for apps You need. Eventually check notification centre too.

Azaradel said:
Check battery management and give access to work in the background for apps You need. Eventually check notification centre too.
Click to expand...
Click to collapse
Yes, I've been checking battery management if everything with access to work in the background for apps, and it seems to be ok and notification center too.
It continues with the same delay / bug
I hope this weekend to reset the phone to factory settings and verify if it keeps the same problem.

Check Wi-Fi sleep, and set it to off from Power Saving tab
Sent from my ALE-L21 using XDA-Developers mobile app

Krokodillo said:
Check Wi-Fi sleep, and set it to off from Power Saving tab
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I checked and is always on, no sleep.
Today is the day, I'm going to reset the phone to factory settings and then check if all is ok.
I'll be back once I have the result:fingers-crossed:

Before starting to reset the phone to factory settings, I made backup all my personal files and a recovery with TWRP if something wrong happened.
It seems to be all right after the whole process
I receive all notifications like any other phone in normal operation, no delay :good:
But before I celebrate, I will be alert to phone with daily use to make sure that everything continued well.
Thanks for all the help :good:

Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions

Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a reliable solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware (no root, locked bootloader, after factory reset) and then upgraded to Nougat C432B370 using FirmwareFinder (FullOTA-MF-PV). Installation worked fine, everything running as expected except for the camera - as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting after upgrading doesn't solve the issue. After upgrading to B370, I also updated to C432B388 - but to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Could this hint at some issue? Also, checking the device info with
Code:
*#*#2846579#*#*
shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop mentioned by @danielegta : https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Edit: I tried the fix on B370 but it has no effect.
Use the fix in #3, but reflash system.img if the fix doesn't help: https://forum.xda-developers.com/showpost.php?p=70069246&postcount=26
Unfortunately this also didn't work for me
Use TWRP-flashable .zip files as given in this thread here: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
I tried this today, but unfortunately it ends up in the same state as I was when upgrading B160 -> B370 using Firmware Finder. Everything except for the camera works.
Edit: I notice that in TWRP there are always errors about not being able to mount /data and /cust. Is this normal or does it hint at some error/malfunction when updating via flashable zip?
Use TWRP-flashable .zip as in #5 but instead of flashing the two .zip without restarting the device, first flash update.zip, then restart phone, flash Nougat TWRP, flash update_data_full_VNS_Lxx_xx_xx.zip as described in this post: https://forum.xda-developers.com/showpost.php?p=70704697&postcount=7
Tried this in the following way: stock MM -> unlock bootloader and flash TWRP -> flash update.zip -> flash Nougat TWRP -> flash update_data_. Doesn't help. Also I cannot confirm what I read somewhere here on xda (some user mentioned that his camera was working when he only flashed the update.zip - this is not true for me).
Other things I tried for uprading the OS that are not necessarily meant to fix the camera issue, but might:
Use B336 as intermediate step: B160 => B336 => B370 (=> B388) as suggested by @vozilo here: https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
Unfortunately this does not solve the issue. The camera doesn't work in any of the versions flashed after B160.
Go from B160 direcly to B388: didn't help
Does anyone know of something else that might help or could someone maybe comment on the "known" fixes, especially if there might be some changes that could be done to commands/build.prop or even local.prop that eventually help?
Thank you very much,
theluk

_theluk_ said:
Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware and then upgraded to Nougat C432B370 using FirmwareFinder. Installation worked fine, everything running as expected except for the camera as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting doesn't solve the issue. Afterwards, I also updated to C432B388 to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Also, checking the device info with shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop: https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Does anyone know of something that might help or could someone maybe comment on the "known" fixes?
Thank you very much,
theluk
Click to expand...
Click to collapse
I had the same problem, and i fixed it by (un)rooting and (un)rooting again

Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly

_theluk_ said:
Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly
Click to expand...
Click to collapse
Ok so usually u should upgrade like 160>b336>b370... The problem might be that you missed a step, not sure though. Try to factory reset first, then go back to b160 and to b336 and then to b370

Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess

_theluk_ said:
Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess
Click to expand...
Click to collapse
try updating through the stock updater

mjz2cool said:
try updating through the stock updater
Click to expand...
Click to collapse
Unfortunately the stock updater doesn't show any updates. So I have to enforce this by using the proxy method provided in Firmware Finder. As I understood this is the "fully" official way of updating, since it does use the "system update" feature provided inside settings of the phone. I will try it again later today to see what could've gone wrong. Maybe I'll just try one of the other B336 firmwares that are listed as FullOTA in FF.

Major update to OP - including new stuff and new information about what I tried. Any other suggestions? I am out of ideas for now and will probably have to live with MM until Huawei has solved this issue

After a suggestion to try VNS-L21 firmware I did, after flashing the corresponding oeminfo. And indeed this worked nicely. Upgrading to Nougat B370 worked and camera is working as well.

_theluk_ said:
after flashing the corresponding oeminfo
Click to expand...
Click to collapse
Hello,
Sorry but I'm a noob, can you explain to me what do you mean by "flashing the corresponding oeminfo" ? Does it mean you had to somehow "trick" your phone so it believes it's L21 instead of L31 or something ?
I have the same problem on the phone of my girlfriend (although I don't recall it's a dual sim one), I'd really like to solve this.
Thank you

_theluk_ said:
...
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
...
Click to expand...
Click to collapse
Ah, one of number of my statements taken out of context. When I worked on CM13, initially only the P9 Lite was supported. After a NEMO user tested this, which was proof of concept that the nemo camera could work on my p9 lite ROM, I added support for NEMO in my AOSP ROMs. So, the reason this helped was that it restarted the camera to work with NEMO and not VENUS, for which it was originally started.
As for your problem, Developer Options -> Take Bug Report ->FULL and post?

How to make my VNS-L21 C432 B503 EMUI 5.0.3 Single-Sim to a Dual-SIM?

Hello everyone,
i would need help - if its possible anyway - to get the Dual-Sim working on my SS P9 lite.
Until now i was able to unlock BL, install TWRP Elite and SuperSU 2.82.
What do i have to do next?
Thank you in advance...
(PS: flashed some oeminfo - did not work, so i flashed back my original bached up oeminfo -
strange thing is that *#*#2846... is not working anymore - i recognized that because i wanted to
reinstall from HWOTA mode...? Should i orry about that?)

crouso said:
Hello everyone,
i would need help - if its possible anyway - to get the Dual-Sim working on my SS P9 lite.
Until now i was able to unlock BL, install TWRP Elite and SuperSU 2.82.
What do i have to do next?
Thank you in advance...
(PS: flashed some oeminfo - did not work, so i flashed back my original bached up oeminfo -
strange thing is that *#*#2846... is not working anymore - i recognized that because i wanted to
reinstall from HWOTA mode...? Should i orry about that?)
Click to expand...
Click to collapse
Hello,
had you already took a look at @k1ll3r8e's thread ?
He made a toolkit that can do what you need.
Best regards
Edit:
Dude you can do that also without the toolkit.
You only need the right oeminfo dual sim
and the correct rom.
Feel free to ask...

hello dadditz,
thank you for your reply! Of course i read a lot here and other sites, and also found the P9 toolkit! But my problem was/is, that i cant "upgrade" to VNS-L21C432B160 because i already was on VNS-L21C432B503 ... so i tried different things, but it did not work. Always the menue "Dual sim configuration" was not in the settings menue... and the image felt little bit "laggy"...
BUT
i was giving it another try - i downgraded from Nougat to MM with this ... tutorial and repeated the steps listed in the P9 lite toolkit... and now i have the Dual-Sim menue in the settings dialogue... and it is working
Because its not "enough" i wanted to return to Nougat - until now with no success... so am i now stuck on VNS-L21C432B160 ?
I tried some images from 380/370/336 but the huawei recovery always stops on 5% and denies the update - how can i upgrade again?
kind regards

crouso said:
hello dadditz,
thank you for your reply! Of course i read a lot here and other sites, and also found the P9 toolkit! But my problem was/is, that i cant "upgrade" to VNS-L21C432B160 because i already was on VNS-L21C432B503 ... so i tried different things, but it did not work. Always the menue "Dual sim configuration" was not in the settings menue... and the image felt little bit "laggy"...
BUT
i was giving it another try - i downgraded from Nougat to MM with this ... tutorial and repeated the steps listed in the P9 lite toolkit... and now i have the Dual-Sim menue in the settings dialogue... and it is working
Because its not "enough" i wanted to return to Nougat - until now with no success... so am i now stuck on VNS-L21C432B160 ?
I tried some images from 380/370/336 but the huawei recovery always stops on 5% and denies the update - how can i upgrade again?
kind regards
Click to expand...
Click to collapse
Hey,
I think you could save yourself from going back
at MM, but, the omelette is made now ...
Have you already done a factory reset + wipe cache in stock recovery ?
Tell me a little bit when you reboot the device
does any warning text come out ? if yes, what color ?

Dadditz said:
Hey,
I think you could save yourself from going back
at MM, but, the omelette is made now ...
Have you already done a factory reset + wipe cache in stock recovery ?
Tell me a little bit when you reboot the device
does any warning text come out ? if yes, what color ?
Click to expand...
Click to collapse
Well, when i was on Nougat, i was not able to see the "Dual Sim Settings" in the settings menue - i tried 20 times
i think... when i went "back" to MM the menue was immediately there...
I did the factory reset and wiped cache in stock recovery menue.
Booting up my device seems all fine - bootloader is relocked, no warnings or anything...
HiSuite told me that my device "has the latest developer version" and no upgrade would be available...
I tried to flash the firmware with TWRP - without success...; when i try dload the phone stuck on 5%... i also
tried the "-PV" versions - without any luck...
So i really have no idea left how to upgrade from this version?!

crouso said:
Well, when i was on Nougat, i was not able to see the "Dual Sim Settings" in the settings menue - i tried 20 times
i think... when i went "back" to MM the menue was immediately there...
I did the factory reset and wiped cache in stock recovery menue.
Booting up my device seems all fine - bootloader is relocked, no warnings or anything...
HiSuite told me that my device "has the latest developer version" and no upgrade would be available...
I tried to flash the firmware with TWRP - without success...; when i try dload the phone stuck on 5%... i also
tried the "-PV" versions - without any luck...
So i really have no idea left how to upgrade from this version?!
Click to expand...
Click to collapse
Use Firmware Finder to force the upgrade, download it from the store.
VPN method worked fine for me (i was on android 7).
Inside the app all the info, anymore
a thread is present here on XDA.
Give it a try...
You're on B160, go for B370 PV version, check compatibility otherwise choose for full ota one.
Good luck
Cheers

P9 Lite - VNS-L31C432B226 to Nougat

Hi guys!
Recently, one of the users of my app reported an issue with his Huawei P9 Lite VNS-L31C432B418. It's impossible to him to use my app, network calls are blocked in the app, the app won't connect to my backend endpoints for no reason. Logging is quite unclear, so it's hard to reproduce this issue.
Because of my dedication and urge to fix this issue, I ordered an Huawei P9 Lite on Amazon. (amazon.de/-/en/gp/product/B01DYN5OLE) It got delivered today, installed my app and woosh... Everything was working fine. The phone came with VNS-L31C432B160/EMUI 4.1.3; but the user of my app is using P9 Lite VNS-L31C432B418/EMUI 5.0.4. Hitting the "check for updates" did not result in receiving any update (Thanks Huawei!) so I started looking around the internet. I prefer to use exactly the same build version because I want to reproduce this (hard) issue.
So far so good, I used Firmware Finder to incrementally update to VNS-L31C432B226. I'm quite new in these firmware-hacks and tried installing the VNS-L31C432B418 version, but I got stuck at the 5% progress indicator. Using Firmware Finder on my PC, it checked that I'm able to install versions with G 2190 and g 1789. These params do not tell that much for me... Currently, I'm stuck at VNS-L31C432B226 as this is the last one that has G 2190 and g 1789. All the other ones have G 190 and g 1755, are these for other devices as the one I have since I am not able to install these ones?
Someone who can help me in order to get VNS-L31C432B418? Is this even possible on my device?
Thanks in advance, kind regards
Joren

JorenVos said:
Hi guys!
Recently, one of the users of my app reported an issue with his Huawei P9 Lite VNS-L31C432B418. It's impossible to him to use my app, network calls are blocked in the app, the app won't connect to my backend endpoints for no reason. Logging is quite unclear, so it's hard to reproduce this issue.
Because of my dedication and urge to fix this issue, I ordered an Huawei P9 Lite on Amazon. (amazon.de/-/en/gp/product/B01DYN5OLE) It got delivered today, installed my app and woosh... Everything was working fine. The phone came with VNS-L31C432B160/EMUI 4.1.3; but the user of my app is using P9 Lite VNS-L31C432B418/EMUI 5.0.4. Hitting the "check for updates" did not result in receiving any update (Thanks Huawei!) so I started looking around the internet. I prefer to use exactly the same build version because I want to reproduce this (hard) issue.
So far so good, I used Firmware Finder to incrementally update to VNS-L31C432B226. I'm quite new in these firmware-hacks and tried installing the VNS-L31C432B418 version, but I got stuck at the 5% progress indicator. Using Firmware Finder on my PC, it checked that I'm able to install versions with G 2190 and g 1789. These params do not tell that much for me... Currently, I'm stuck at VNS-L31C432B226 as this is the last one that has G 2190 and g 1789. All the other ones have G 190 and g 1755, are these for other devices as the one I have since I am not able to install these ones?
Someone who can help me in order to get VNS-L31C432B418? Is this even possible on my device?
Thanks in advance, kind regards
Joren
Click to expand...
Click to collapse
Hi Joren,
sorry if i ask but the weird (B226) update you done is android 6 or 7 ?
Starting from B160, you should have chosen B370 FULLOTA-MF-PV
to upgrade to android 7, then to latest B418...

Dadditz said:
Hi Joren,
sorry if i ask but the weird (B226) update you done is android 6 or 7 ?
Starting from B160, you should have chosen B370 FULLOTA-MF-PV
to upgrade to android 7, then to latest B418...
Click to expand...
Click to collapse
Hi, thanks for your reply! My device gotdelivered with version B172...
Today, I got an update to VNS-L31C432B228! This version is not visible in Firmware Finder... Any ideas how to update to Nougat?
Is it possible to force the update? I always get the message that the update is not compatible with my version.

JorenVos said:
Hi, thanks for your reply! My device gotdelivered with version B172...
Today, I got an update to VNS-L31C432B228! This version is not visible in Firmware Finder... Any ideas how to update to Nougat?
Is it possible to force the update? I always get the message that the update is not compatible with my version.
Click to expand...
Click to collapse
Dude,
how did you got that update and is this B228 android 6 or 7 ?

Dadditz said:
Dude,
how did you got that update and is this B228 android 6 or 7 ?
Click to expand...
Click to collapse
B228 update got over the air after having B226 from Firmware Finder , and it's still Android 6...

JorenVos said:
B228 update got over the air after having B226 from Firmware Finder , and it's still Android 6...
Click to expand...
Click to collapse
Ok,
use the app, same method and choose B370 FULLOTA-MF-PV.
It's 1.99 gbyte - date 21/03/2017 - G 753 - g 104.
Into my PC version of FF i see (2) two versions, looks the same, try one or the other..
If you will succeed you can update to the latest firmware (B418)..

Dadditz said:
Ok,
use the app, same method and choose B370 FULLOTA-MF-PV.
It's 1.99 gbyte - date 21/03/2017 - G 753 - g 104.
Into my PC version of FF i see (2) two versions, looks the same, try one or the other..
If you will succeed you can update to the latest firmware (B418)..
Click to expand...
Click to collapse
Thanks for your effort!
It seems to be the same URL for those two entries. Note that it's in fact a "downgrade", the "v" value is 80460. My device got delivered with B172 (which is also not found in FF), B173 is already 110304... Currently, B228 is also not visible in the list, B227 is 143951.
http://update.dbankcdn.com/TDS/data/files/p3/s15/G753/g104/v80460/f1/full/update.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G753/g104/v80460/f1/full/update.zip
http://update.dbankcdn.com/TDS/data...-L31_hw_eu/update_data_full_VNS-L31_hw_eu.zip
http://update.dbankcdn.com/TDS/data...-L31_hw_eu/update_data_full_VNS-L31_hw_eu.zip
Unzipped "update.zip", copied it into dload folder on my SD card, *#*#2846579#*#* =, ProjectMenu -> Software Upgrade -> SDCard Upgrade ->OK
"Software install failed" "Incompatibility with current version. Please download the correct update package". Same story for the contents of the update_data_full_VNS-L31_hw_eu.zip.
I'd like to wipe the current firmware instead op updating/upgrading it, but I've already done lots of research, some docs are so outdated that they're not relevant anymore. Any clear steps on how to force install the version instead op upgrading it?

JorenVos said:
Thanks for your effort!
It seems to be the same URL for those two entries. Note that it's in fact a "downgrade", the "v" value is 80460. My device got delivered with B172 (which is also not found in FF), B173 is already 110304... Currently, B228 is also not visible in the list, B227 is 143951.
http://update.dbankcdn.com/TDS/data/files/p3/s15/G753/g104/v80460/f1/full/update.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G753/g104/v80460/f1/full/update.zip
http://update.dbankcdn.com/TDS/data...-L31_hw_eu/update_data_full_VNS-L31_hw_eu.zip
http://update.dbankcdn.com/TDS/data...-L31_hw_eu/update_data_full_VNS-L31_hw_eu.zip
Unzipped "update.zip", copied it into dload folder on my SD card, *#*#2846579#*#* =, ProjectMenu -> Software Upgrade -> SDCard Upgrade ->OK
"Software install failed" "Incompatibility with current version. Please download the correct update package". Same story for the contents of the update_data_full_VNS-L31_hw_eu.zip.
I'd like to wipe the current firmware instead op updating/upgrading it, but I've already done lots of research, some docs are so outdated that they're not relevant anymore. Any clear steps on how to force install the version instead op upgrading it?
Click to expand...
Click to collapse
Dude, i'm here to help, at least for what i know...
I think i explained not so good...
You should use the app to upgrade not to download the firmware.
Take a look HERE, also some videos are on YT..
Just change the firmware with yours... :fingers-crossed:

Dadditz said:
Dude, i'm here to help, at least for what i know...
I think i explained not so good...
You should use the app to upgrade not to download the firmware.
Take a look HERE, also some videos are on YT..
Just change the firmware with yours... :fingers-crossed:
Click to expand...
Click to collapse
Tried in the app, it told me that B370 "The firmware is not approved for installation". B418 is approved (FullOTA-MF), so:
- I've downloaded the firmware (3 files)
- Setup in-app proxy
- Change wifi proxy to localhost:8080
- Check for updates, update is available
- Switch back to wifi, disable proxy
- Download update
- Install
Same story, update is incompatible... So I think I'm still doing something wrong while changing the firmware instead of upgrading. For me, the tutorials are skipping essential steps. Or I might have received a f*cked up device. Why on earth is it so hard to update, thanks Huawei..

JorenVos said:
Tried in the app, it told me that B370 "The firmware is not approved for installation". B418 is approved (FullOTA-MF), so:
- I've downloaded the firmware (3 files)
- Setup in-app proxy
- Change wifi proxy to localhost:8080
- Check for updates, update is available
- Switch back to wifi, disable proxy
- Download update
- Install
Same story, update is incompatible... So I think I'm still doing something wrong while changing the firmware instead of upgrading. For me, the tutorials are skipping essential steps. Or I might have received a f*cked up device. Why on earth is it so hard to update, thanks Huawei..
Click to expand...
Click to collapse
Are you choosing B370 fullota-mf-pv one ? (not B370 fullota-mf nor B370 ota)
Also now i see there a third B370 fullota-mf-pv with date 2017.08.03 - G 1258 - g 104..
If you don't upgrade to this version first,
you couldn't upgrade anyway to android 7
and then to latest version.
Come on try again...

Dadditz said:
Are you choosing B370 fullota-mf-pv one ? (not B370 fullota-mf nor B370 ota)
Also now i see there a third B370 fullota-mf-pv with date 2017.08.03 - G 1258 - g 104..
If you don't upgrade to this version first,
you couldn't upgrade anyway to android 7
and then to latest version.
Come on try again...
Click to expand...
Click to collapse
Yup, but that one: "Most likely, the firmware was removed from the server".
The other ones with B370 are both telling "The firmware is not approved for installation".
I'm testing all the FullOTA-MF-PV's, they are all telling "The firmware is not approved for installation". Some of the "FullOTA-MF" do show the message that they are available. What's the difference between the "-PV"?

JorenVos said:
Yup, but that one: "Most likely, the firmware was removed from the server".
The other ones with B370 are both telling "The firmware is not approved for installation".
I'm testing all the FullOTA-MF-PV's, they are all telling "The firmware is not approved for installation". Some of the "FullOTA-MF" do show the message that they are available. What's the difference between the "-PV"?
Click to expand...
Click to collapse
That version is used to upgrade to android 7 from 6.
Maybe the version you updated before (B226/B228) don't allow you to upgrade.
Downgrade to B160 and redo your steps..
How to do this ?
Download THIS FILE, extract update.app, create a folder and name it DLOAD.
Put update.app into that folder and put the folder into your SD card.
Turn off the device then reboot holding vol+ & vol- & power buttons together
until flashing starts then release them...

Dadditz said:
That version is used to upgrade to android 7 from 6.
Maybe the version you updated before (B226/B228) don't allow you to upgrade.
Downgrade to B160 and redo your steps..
How to do this ?
Download THIS FILE, extract update.app, create a folder and name it DLOAD.
Put update.app into that folder and put the folder into your SD card.
Turn off the device then reboot holding vol+ & vol- & power buttons together
until flashing starts then release them...
Click to expand...
Click to collapse
Done, thanks for those clear instructions, I do have B160 for now. The B370 is still resulting in "The firmware is not approved for installation"... :/

JorenVos said:
Done, thanks for those clear instructions, I do have B160 for now. The B370 is still resulting in "The firmware is not approved for installation"... :/
Click to expand...
Click to collapse
That's really weird dude..
Is your device dual sim one ?
What happen if you choose B371 (fullota-mf-pv) instead of B370 ?

Dadditz said:
That's really weird dude..
Is your device dual sim one ?
What happen if you choose B371 (fullota-mf-pv) instead of B370 ?
Click to expand...
Click to collapse
Yup, the device is the dual sim one, B371 also "The firmware is not approved for installation". It's really weird...
I'll try updating manually incrementally, so update by update the ones with G 1258 - g 104?

JorenVos said:
Yup, the device is the dual sim one, B371 also "The firmware is not approved for installation". It's really weird...
I'll try updating manually incrementally, so update by update the ones with G 1258 - g 104?
Click to expand...
Click to collapse
Back to B370,
skip the verify access firmware, go directly to 'get an update via dns',
tap ok, select 'auto' dns method and tap change dns.
VPN service should start...
Open settings > internal updater
and see if download come for you... check several times ...

Dadditz said:
Are you choosing B370 fullota-mf-pv one ? (not B370 fullota-mf nor B370 ota)
Also now i see there a third B370 fullota-mf-pv with date 2017.08.03 - G 1258 - g 104..
If you don't upgrade to this version first,
you couldn't upgrade anyway to android 7
and then to latest version.
Come on try again...
Click to expand...
Click to collapse
I don't know what's wrong with this device.
I've downgraded my device to B160 (66015), tried upgrading to B370 80460, 80466, 80582, all with the same result: Incompatibility with current version. The only version I'm able to upgrade to is 80562, which is B210. From that point, Firmware Finder suggests that it should be possible to update to the B370 builds, but every time, "Incompatibility with current version".
The only B370 that I was not able to try is the one you're suggesting in your comment. That one gives a 404 so I'm not able to download that one (92405). Any other suggestions...?

JorenVos said:
I don't know what's wrong with this device.
I've downgraded my device to B160 (66015), tried upgrading to B370 80460, 80466, 80582, all with the same result: Incompatibility with current version. The only version I'm able to upgrade to is 80562, which is B210. From that point, Firmware Finder suggests that it should be possible to update to the B370 builds, but every time, "Incompatibility with current version".
The only B370 that I was not able to try is the one you're suggesting in your comment. That one gives a 404 so I'm not able to download that one (92405). Any other suggestions...?
Click to expand...
Click to collapse
Sorry dude have you tried skipping the firmware access ?
Could we have missed something in the procedure ?
If this doesn't work, try opening the FF app and from the main menu select 'instructions'.
Video and text guides will open. You can try the update with HiSuite
or with eRecovery or as a last resort you could try the one with a TWRP,
but for this you will have to unlock the bootloader and
it would cost you some time and an additional 4 € ...
Please Note: I have never upgraded from A6 to A7 with this device via twrp,
you do this at your own risk ...

JorenVos said:
I don't know what's wrong with this device.
I've downgraded my device to B160 (66015), tried upgrading to B370 80460, 80466, 80582, all with the same result: Incompatibility with current version. The only version I'm able to upgrade to is 80562, which is B210. From that point, Firmware Finder suggests that it should be possible to update to the B370 builds, but every time, "Incompatibility with current version".
The only B370 that I was not able to try is the one you're suggesting in your comment. That one gives a 404 so I'm not able to download that one (92405). Any other suggestions...?
Click to expand...
Click to collapse
With B160, install firmware finder on your phone.
Add model as VNS-L31C432
Settings > Show firmware for this region only and Show full OTAs only.
Check firmware approval one or two times. (Make sure you've provided phone permission for firmware finder)
Get an update via DNS and it'll turn on vpn.
Check for updates and download.
I can help you on teamviewer if you still can't make it work.

I think that the firmware I need is the one that returns a 404 when trying to download. I've already done successful firmware approval several times for builds that won't install after all. Only the fact that it's such a mess to get updates for this device makes me really frustrated. What if I was a "dummy" owner of this device? I should never be able to get the updates I'm looking for. It's just impossible without doing too much effort or rooting the device. For me it's really important to have the original firmware of Huawei and not a custom rom, because I have to investigate the issue of my app user, which is device-specific. How complicated can it be to provide a solid update platform. Huawei, please.
I've decided to ship this piece of sh*t back to Amazon. Ordered a second hand Huawei P9 Lite that has already the build VNS-L31C432B418. Thank you guys for all the effort in trying to help me getting Nougat on this device, unfortunately it seems to be impossible.