Database Develop

The great brick - help!!

I came from a long way to this point. In this thread (https://forum.xda-developers.com/p9-plus/help/bluetooth-issue-vie-l09c25b320-t3548885) you have all the steps that I made but, summarizing, I unlock the bootloader using a official code, I failed flashing the first time so I ended with a NRD90M version with no Bluetooth, no keyboard... I managed to update again using the finnish rollback package for VIE-L09, in this point I ended with a L09C900 and BT working. As everything works it seems that was the moment to flash again to a final version so I access through SRK Tool and change the OEMINFO to the EU one (mine was LA) and flash directly through the 3 buttons mode the full C432B180 (or 181, not sure) but ended with C432B181, wich doesn't receive OTA, so I decided to flah to the final stock rom, the C432B360 version with Nougat. It fails at 63% (more or less). Then I tried with a MM version so I force the update again but this time to the C432B170. And failed. On this point a message saying that my phone is encrypted and that I must access a decryption password appears. So I decided to force it again to the C432B160 and now my phone is stuck in the BOOT screen (the one that warns about that my phone it unlocked with orange letters), does't boot in to Recovery, or ERecovery. The 3 buttons method don't work anymore and the phone doesn't turn off till the battery is drained
I only managed to enter to Fastboot mode and shows that the phone stills unlocked and the FRP too.
What can I do to unbrick my device?? DC Phoenix?? Fatboot flashing BOOT.img, RECOVERY.img??
PLEASE HELP :crying:

Dude.. sorry to hear it!
Maybe a flash of original recovery.img would help? FAstboot works as it should?
If you can get Power+Vol Up/Down to work again, you should rollback with finnish .APP, then flash B181, .. then find the complete guide in this thread
---------- Post added at 11:12 AM ---------- Previous post was at 10:55 AM ----------
Have you tested DC?

deecept said:
Dude.. sorry to hear it!
Maybe a flash of original recovery.img would help? FAstboot works as it should?
If you can get Power+Vol Up/Down to work again, you should rollback with finnish .APP, then flash B181, .. then find the complete guide in this thread
---------- Post added at 11:12 AM ---------- Previous post was at 10:55 AM ----------
Have you tested DC?
Click to expand...
Click to collapse
Thanx @deecept for your reply.
Well I think that Fastboot works as it should and I will try as soon as I turn back home to flash RECOVERY.img and I will let you know how it goes.
I'll try again if I could fix the Pwr+VOL Up/Down but I not really sure if it would work.
Dc Phoenix I try it a few weeks ago but with no results. But, in this case, probably it would be the best option. But I want to do it nowing what to do exactly because the last time I spend 23€ for nothing.

I would maybe try to flash the original marshmellow recovery.img, to see if that makes any difference.
Here is some files to aid you.

deecept said:
I would maybe try to flash the original marshmellow recovery.img, to see if that makes any difference.
Here is some files to aid you.
Click to expand...
Click to collapse
Thankyou @deecept as soon as I arrive home I'll try and text what happens.

Any news, @Kifivierito?

deecept said:
Any news, @Kifivierito?
Click to expand...
Click to collapse
Hey @deecept, nothing. No changes. Yesterday I flash through fastboot Recovery.img, System.img, Boot.img, cache.img, Cust.img and even Userdata.img. But nothing changes. The device still in a bootloop. I'm thinking to use again DC Unlocker, but I'm not sure exactly what to do? If I need to flash a whole update.app or something else. I don't want to spend the money if im not sure what to do.
Btw, something strange happens in fastboot mode. When I try to erase the cache.img it shows the message that Remote command not allowed. But it let me flash every file that I mention. ¿?¿?
In fastboot mode it shows that Phone is Unlocked and FRP too...

@deecept I finally managed to flash and function L09C432B360 usind DC Phoenix. But I found that, again, I havent the data_full package installed so I dont have AGAIN :crying: neither BT or themes or the update section in adjustments. I want to kill my self.... :cyclops:
How can I add them??
If I use DC Phoenix in which order I must flash the files? I have the file update_data_full_hw_eu. I tried to flash it after flash the update.app of the L09C432B360, but dont work

Kifivierito said:
@deecept I finally managed to flash and function L09C432B360 usind DC Phoenix. But I found that, again, I havent the data_full package installed so I dont have AGAIN :crying: neither BT or themes or the update section in adjustments. I want to kill my self.... :cyclops:
How can I add them??
If I use DC Phoenix in which order I must flash the files? I have the file update_data_full_hw_eu. I tried to flash it after flash the update.app of the L09C432B360, but dont work
Click to expand...
Click to collapse
Downgrade to B181 and follow this guide.
What you need?
1. Charged phone
2. Enabled installing unknown apps
3. Download Firmware Finder from Google Store (the free version)
what next?
1. Run Firmware Finder
2. Go to settings and Enable Installation via system update.
3. Tool will prompt to download Firmware Finder Proxy - do it then install it
4. Go back to the tool and select firmware of your choice - make sure you select FULL (not OTA)
5. Firmware Finder Proxy window will open - do as described - go to Wifi, advanced add manual proxy as local host with 8080 port
6. Go to phone Settings - System update, DO NOT CLICK ON UPDATE, just click on Menu and choose to "Download latest full package" and then click on Update the phone
7. It will attempt to download it but it may fail (as in my case) with message about unstable internet connection - go back to wifi settings and disable proxy, go back to update and resume it - update should start to download then follow as on screen instructions
Sent from my VIE-L29 using XDA Labs

Mostar088 said:
Downgrade to B181 and follow this guide.
What you need?
1. Charged phone
2. Enabled installing unknown apps
3. Download Firmware Finder from Google Store (the free version)
what next?
1. Run Firmware Finder
2. Go to settings and Enable Installation via system update.
3. Tool will prompt to download Firmware Finder Proxy - do it then install it
4. Go back to the tool and select firmware of your choice - make sure you select FULL (not OTA)
5. Firmware Finder Proxy window will open - do as described - go to Wifi, advanced add manual proxy as local host with 8080 port
6. Go to phone Settings - System update, DO NOT CLICK ON UPDATE, just click on Menu and choose to "Download latest full package" and then click on Update the phone
7. It will attempt to download it but it may fail (as in my case) with message about unstable internet connection - go back to wifi settings and disable proxy, go back to update and resume it - update should start to download then follow as on screen instructions
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
I downgrade back to C181. Everything was fine. I had my BT, themes, everything... Ok I perform the FF upgrade (changing advanced proxy settings and everything). Go to FF, send the ROM to the updater, in the updater I select full package and start upgrading. The device perform the upgrade weirdly fast (3 or 4 mins maximum), and restart and perform a System optimization. When it stops, restart again and susrprise! I have AGAIN NRD90M Test-keys! How is this even possible @Mostar088???

Kifivierito said:
I downgrade back to C181. Everything was fine. I had my BT, themes, everything... Ok I perform the FF upgrade (changing advanced proxy settings and everything). Go to FF, send the ROM to the updater, in the updater I select full package and start upgrading. The device perform the upgrade weirdly fast (3 or 4 mins maximum), and restart and perform a System optimization. When it stops, restart again and susrprise! I have AGAIN NRD90M Test-keys! How is this even possible @Mostar088???
Click to expand...
Click to collapse
Did u choose this Firmware FULL OTA MF-PV?
Sent from my VIE-L29 using XDA Labs

Mostar088 said:
Did u choose this Firmware FULL OTA MF-PV?
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
Yes. I selected that one.
I'm trying to repeat all the process again. I just flash via DC Phoenix B181 again without problem via fastboot but again (previously I dont mentioned it) when performing the second step in DC Phoenix, the upgrade mode flash, fails writing the VERLIST.img.
The firs time that I did it also fails but as I restart and everything works fine I forgot it.
Do you think it could affect to the FF process??
Should I continue redoing again everything??
Thx again @Mostar088. It's being a very long and boring process.

Kifivierito said:
Yes. I selected that one.
I'm trying to repeat all the process again. I just flash via DC Phoenix B181 again without problem via fastboot but again (previously I dont mentioned it) when performing the second step in DC Phoenix, the upgrade mode flash, fails writing the VERLIST.img.
The firs time that I did it also fails but as I restart and everything works fine I forgot it.
Do you think it could affect to the FF process??
Should I continue redoing again everything??
Thx again @Mostar088. It's being a very long and boring process.
Click to expand...
Click to collapse
Dont know if it affects the FF, i realy dont know what can be wrong.
U have 72h to use Dc Phoenix so try again.
Try flash a MM with a lower build like B170 or 161 and see if u recive OTA to update B181 just to see if that works before u proceed to upgrade N.
Edit: when u downgrade try update by dload method from B170 to B180 and then if u recive OTA for B181.
Sent from my VIE-L29 using XDA Labs

Mostar088 said:
Dont know if it affects the FF, i realy dont know what can be wrong.
U have 72h to use Dc Phoenix so try again.
Try flash a MM with a lower build like B170 or 161 and see if u recive OTA to update B181 just to see if that works before u proceed to upgrade N.
Edit: when u downgrade try update by dload method from B170 to B180 and then if u recive OTA for B181.
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
Ok. I'll work on it and tell you about

Mostar088 said:
Dont know if it affects the FF, i realy dont know what can be wrong.
U have 72h to use Dc Phoenix so try again.
Try flash a MM with a lower build like B170 or 161 and see if u recive OTA to update B181 just to see if that works before u proceed to upgrade N.
Edit: when u downgrade try update by dload method from B170 to B180 and then if u recive OTA for B181.
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
Nothing. Again bricked. This time DC Phoenix either can't flash. Still having an error when writing VERLIST.img. No matter which version. I tried B170 and B160.
I read in DC Unlocker forum that a way to fix the VERLIST.img flash fail in upgrade mode is trying to repeat flashing using the dload mode. But it also fails.
Really I think I'm cursed... I'll try to go to the very first step. I'll change oeminfo to the original one (LA) and there I'll try to downgrade. I don't know what else to do

Kifivierito said:
Nothing. Again bricked. This time DC Phoenix either can't flash. Still having an error when writing VERLIST.img. No matter which version. I tried B170 and B160.
I read in DC Unlocker forum that a way to fix the VERLIST.img flash fail in upgrade mode is trying to repeat flashing using the dload mode. But it also fails.
Really I think I'm cursed... I'll try to go to the very first step. I'll change oeminfo to the original one (LA) and there I'll try to downgrade. I don't know what else to do
Click to expand...
Click to collapse
I think it's the best to try that.
Sent from my VIE-L29 using XDA Labs

Mostar088 said:
I think it's the best to try that.
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
Did you know where I can find a LA oeminfo?? Because in SRT Toolkit just appears Chinese, Euro, African and Asia.

¡¡¡YESSS!! FINALLY. I MADE IT!!!
VIE-L09C432B360 Working properly with Bluetooth, Themes, Apps and all the great stuff from a Huawei Stock version!
I have two theories about why I was failing over and over after flashing B181 and updating to higher versions:
1. Phone was updated properly but as soon as it synchronize with google, something doesn't match with the ner version and end in NRD90M Test-Keys. So previously to the last update, after flashing with DC Unlocker (to exit the bootloop), I go to my google account Device Manager and delete the previous VIE-L09 that I have registered.
2. The other theory was that, all the times that I flash and update I allways was with the bootloader unlocked. This time, after flashing the B181 version y relock the bootloader.
One of this steps help me finally made the update:
I will wrote a thread trying to explain how I did it and adding the files that I use.
I wanna thank @Masters_2017, @CNHowardLai, @deecept and specially @Mostar088, @M.KK for their selfless help for nearly a month.
Best regards!

Help i'm stuck
Hey @Kifivierito! can u help me? i'm stuck with your same problem. Ok i was on C900B174 (or173, yes a global one) then i've tried to update to C432B360, but i've got the "test key version" without the keyboard, (NRD90M Test-keys).
So, i rollback to MM with a package, and i got the C900 version again. Through an update i went on Nougat C900 version without many things that were missing (like the updater app). I go back again to MM and this time i've changed the oem file to C432, then, first i unlocked my bootloader and i rooted sucessfully my phone, installing TWPR recovery too. I would come back to stock with a C432B103 version to lock bootIoader and restore. i've decided to download w "firmware finder" the full rom version C432B360 u installed,following all the instructions, but i cannot install it (i think 'cause of my stupid modifications xD ). Now i'm tring to go stock w C432B181, hoping that the bootloader will be locked again. Idk really what should i do now, i'm really getting frustrated.
Pls help me!
EDIT: Ok this one works great C432B181, now i'm scared to update xD

dr.feelgoodthedj said:
Hey @Kifivierito! can u help me? i'm stuck with your same problem. Ok i was on C900B174 (or173, yes a global one) then i've tried to update to C432B360, but i've got the "test key version" without the keyboard, (NRD90M Test-keys).
So, i rollback to MM with a package, and i got the C900 version again. Through an update i went on Nougat C900 version without many things that were missing (like the updater app). I go back again to MM and this time i've changed the oem file to C432, then, first i unlocked my bootloader and i rooted sucessfully my phone, installing TWPR recovery too. I would come back to stock with a C432B103 version to lock bootIoader and restore. i've decided to download w "firmware finder" the full rom version C432B360 u installed,following all the instructions, but i cannot install it (i think 'cause of my stupid modifications xD ). Now i'm tring to go stock w C432B181, hoping that the bootloader will be locked again. Idk really what should i do now, i'm really getting frustrated.
Pls help me!
EDIT: Ok this one works great C432B181, now i'm scared to update xD
Click to expand...
Click to collapse
Hey @dr.feelgoodthedj,
sorry for the late reply. Well that last edit of your post are good news. If you have C432B181 running without problem now you only have to follow the steps tu upgrade via FFinder with the FF Proxy settings. If you follow step by step the guide, you will end up with your P9 Plus with Android 7 and everything working.
If you perform it and fail again, don't hesitate and repeat the process trying one of the two points that I write In my last post. Try to access to google my devices and delete the previous P9 that you have. And after that, if still don't working try to relock your bootloader.
With one of this two steps it MUST work.
Good luck!

P9 eva-l19 (dual sim) and nougat update problems

I have tried several ways to install nougat to Huawei P9 dual sim, but it's almost impossible.
First i tried to install beta version, and it works ok but some apps are missing and keyboard is missing as well, it installs only google voice as a keyboard, so I restored it with Huawei rollback package.
Second, I tried debranding it so I can install some other version but I have similar issues. Here are my steps:
1. unlock bootloader
2. twrp recovery
3. root
4. change oem info and custom.bin, and this is where the problem starts.
After step number 4 the phone restarts and the letters during initial startup are red like system had been modified and after it goes to the part where it says "type password to decrypt storage". When I do that, it accepts the password (google) and says the phone storage is corrupted and I have to reset it, and then it resets the phone to default settings. After that I don't have root and no custom recovery. I tried this procedure several times and it's always the same. After the reset procedure, it installs some initial version (C900B136).
I finally gave up on that, and tried to get back to L19C432B161 but I have issues as well. First I had to restore my oem info and custom.bin so it accepts the C432 version, but after install some apps are gone and the theme manager is not working (it won't change icons or the wallpapers).
I tried using HiSuite to restore it back to stock but it won't accept the L19 version (only L09 and L29).
The tool I was using is SRK Tool Huawei 2.0, and I tried to follow procedure as described here on xda.
Any clues what I do wrong?

elvirr said:
I have tried several ways to install nougat to Huawei P9 dual sim, but it's almost impossible.
First i tried to install beta version, and it works ok but some apps are missing and keyboard is missing as well, it installs only google voice as a keyboard, so I restored it with Huawei rollback package.
Second, I tried debranding it so I can install some other version but I have similar issues. Here are my steps:
1. unlock bootloader
2. twrp recovery
3. root
4. change oem info and custom.bin, and this is where the problem starts.
After step number 4 the phone restarts and the letters during initial startup are red like system had been modified and after it goes to the part where it says "type password to decrypt storage". When I do that, it accepts the password (google) and says the phone storage is corrupted and I have to reset it, and then it resets the phone to default settings. After that I don't have root and no custom recovery. I tried this procedure several times and it's always the same. After the reset procedure, it installs some initial version (C900B136).
I finally gave up on that, and tried to get back to L19C432B161 but I have issues as well. First I had to restore my oem info and custom.bin so it accepts the C432 version, but after install some apps are gone and the theme manager is not working (it won't change icons or the wallpapers).
I tried using HiSuite to restore it back to stock but it won't accept the L19 version (only L09 and L29).
The tool I was using is SRK Tool Huawei 2.0, and I tried to follow procedure as described here on xda.
Any clues what I do wrong?
Click to expand...
Click to collapse
i had a similar issue where i was unable to flash any particular firmware, finally had my phone taken to the service center and they replaced the motherboard (twice)..

umair9001 said:
i had a similar issue where i was unable to flash any particular firmware, finally had my phone taken to the service center and they replaced the motherboard (twice)..
Click to expand...
Click to collapse
Well during this process I run into a bootloop and no recovery, so I unlock the bootloader, flash the stock recovery and then install stock firmware.
My phone is working now but it's not complete, some things are missing and not working properly so I am waiting some instructions what to do next. I really like Huawei phones but this firmware thing is a nightmare

elvirr said:
I have tried several ways to install nougat to Huawei P9 dual sim, but it's almost impossible.
First i tried to install beta version, and it works ok but some apps are missing and keyboard is missing as well, it installs only google voice as a keyboard, so I restored it with Huawei rollback package.
Second, I tried debranding it so I can install some other version but I have similar issues. Here are my steps:
1. unlock bootloader
2. twrp recovery
3. root
4. change oem info and custom.bin, and this is where the problem starts.
After step number 4 the phone restarts and the letters during initial startup are red like system had been modified and after it goes to the part where it says "type password to decrypt storage". When I do that, it accepts the password (google) and says the phone storage is corrupted and I have to reset it, and then it resets the phone to default settings. After that I don't have root and no custom recovery. I tried this procedure several times and it's always the same. After the reset procedure, it installs some initial version (C900B136).
I finally gave up on that, and tried to get back to L19C432B161 but I have issues as well. First I had to restore my oem info and custom.bin so it accepts the C432 version, but after install some apps are gone and the theme manager is not working (it won't change icons or the wallpapers).
I tried using HiSuite to restore it back to stock but it won't accept the L19 version (only L09 and L29).
The tool I was using is SRK Tool Huawei 2.0, and I tried to follow procedure as described here on xda.
Any clues what I do wrong?
Click to expand...
Click to collapse
Before you debrand, download the ROM of the cust you want to debrand to, place in dload folder on your sdcard. After step 4, your device will reset to factory, use sdcard ROM upload method and you will succesfully debrand your device. After that, if you debrand to L19C636B190 (for example), it will be OTA to L19C636B361.
My Al-10 was debranded and OTA successfully to L19C636B361 using this method.

elvirr said:
Well during this process I run into a bootloop and no recovery, so I unlock the bootloader, flash the stock recovery and then install stock firmware.
My phone is working now but it's not complete, some things are missing and not working properly so I am waiting some instructions what to do next. I really like Huawei phones but this firmware thing is a nightmare
Click to expand...
Click to collapse
Totally agree, once you are on nougat it really becomes hard to flash the firmware..till marshmallow, it was easier to control and flash the firmware..

swedenboy said:
Before you debrand, download the ROM of the cust you want to debrand to, place in dload folder on your sdcard. After step 4, your device will reset to factory, use sdcard ROM upload method and you will succesfully debrand your device. After that, if you debrand to L19C636B190 (for example), it will be OTA to L19C636B361.
My Al-10 was debranded and OTA successfully to L19C636B361 using this method.
Click to expand...
Click to collapse
Well this was the missing part
After i copied the L19C636B190 rom to dload folder on sd card it was successful.
Then I just connected it to HiSuite and it found the nougate update.
Thank you!

Hi Guys,
Any links available for download??
My device is P9 DUAL SIM(EVA-L19)
Thnx

mohammad.nomaan said:
Hi Guys,
Any links available for download??
My device is P9 DUAL SIM(EVA-L19)
Thnx
Click to expand...
Click to collapse
Did you find the links for L-19? I need B136 for a rollback

I got the OTA last Friday so didn't do anything else
It's now on 7.0 EMUI
Sent from my SM-N920C using Tapatalk

mohammad.nomaan said:
I got the OTA last Friday so didn't do anything else
It's now on 7.0 EMUI
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Damn I need to rollback mine just to reroot it :crying:

swedenboy said:
Before you debrand, download the ROM of the cust you want to debrand to, place in dload folder on your sdcard. After step 4, your device will reset to factory, use sdcard ROM upload method and you will succesfully debrand your device. After that, if you debrand to L19C636B190 (for example), it will be OTA to L19C636B361.
My Al-10 was debranded and OTA successfully to L19C636B361 using this method.
Click to expand...
Click to collapse
How did you get the OTA? I got it right after dload B190 (which I didn't update it yet) then I didn't have it anymore 5 mins later
UPDATE: Somehow got the OTA when my dload update to B361 failed

[Q] How to debrand P9 when already on Nougat (B361)?

I'm on EVA-L09C09 and would like to go to L09C432 so I can use the RROS ROM. Is it possible to debrand it without downgrading to 6.x? (I have an unlocked bootloader)
Thank you!

I was with a situation very similar and did it.
I was on EVA-L09C02B345 and debranded to EVA-L09C432B383 to test OTA Updates and received the EVA-L09C432B386 correctly via System Update and applied it successfully.
The process was not very clean I was with the same problem all tutorials are for android 6.x and none for 7.x, but I risked to follow this one:
https://forum.xda-developers.com/p9/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410045
Of course before, I unlocked bootloader, installed TWRP and rooted, with help of latest topics about the subject, but you already have this.
Now, the problem on that tutorial was after applying the oeminfo and custombin of C432 the phone needs reboot and it was supposed to reboot and do some more actions on the system but when you reboot it enters in a bootloop that sent me to erecovery... At this point I had another problem, because after this I tried to put with dload an original C02 rom and give up, but the original rom on FF available for C02 was from a test branch(I didn't kown) and it didn't have updates and some other things, at this point I din't have updates to receive the latest C02 rom and had to try again for the C432 so I unlocked again and put TWRP and as a desperate measure I installed via TWRP the zip files of C432B383 and despite my beliefs it didn't gave any error, after reboot It booted correctly and phone info was already EVA-L09C432B383 and all working. At fist the OTA update to B386 didn't apear but after a factory data reset it appeared right after initial setup and wifi configuration, downloaded full update and applied successfully.
This was my story, after this I am with the idea that after the problem of oeminfo and custombin I should have gone to TWRP and flash the C432 rom and everything would be ok but I'm not sure if the "test" rom influenced anything on the process...
Hope it helps...

So did it go out of the bootloop after re-unlocking?

WhatWhatInTheRoot said:
So did it go out of the bootloop after re-unlocking?
Click to expand...
Click to collapse
After re-unlock I didn't followed the tutorial I just unlocked bootloader then installed TWRP and on TWRP installed the zip files of the EVA-L09C432B383 firmware.
I assume that the oeminfo and custombin from the tutorial was still in place because I ended up with a L09C432 and not with a crossflashed L09B900, so probably you can't skip the bootloop, but I'm not sure I'm no expert I just risked and got lucky I guess!
It would be nice If someone who really understand this procedure, to tell us what's the appropriate procedure to do this without problems and bootloops...
If you're willing to risk my recipe is this:
1 - unlock bootloader (you already have this)
2 - install twrp (https://forum.xda-developers.com/p9/development/twrp-t3565703)
3 - root (https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258)
4 - follow tutorial until reboot after apply C432 oeminfo and custombin (https://forum.xda-developers.com/p9/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410045)
5 - when the phone boot to e-recovery, don't do anything just reboot it to TWRP
6 - on TWRP install the zip files of EVA-L09C432B386 previously saved on the sdcard
If step 5 and 6 fail try to flash the EVA-L09C432B386 via dload folder on sdcard. If this fails too I don't really know what I did more to solve the problem because at that point I was a bit scared and trying everything...
Don't forget before you do anything make sure you have your original firmware available don't do like me that only had a old test keys firmware available, and do a full nandroid backup on TWRP so you have more options to revert back!!!
Probably it's best to way for a more expert opinion/tutorial...

Thanks, but sounds way too risky, I think I'll wait for a more proper method.

Sorry for bumping, but has anyone found out a solution?
I and mfPPC can't be the only ones with this problem, surely. :/

Huawei p9 l19 firmware

Hi all, i have problem with my p9 l19c432 eu version. I had l19 c432b386 android n and i wanted to go bac to mm. My device doesn't have root or unlocked bootloader or custom twrp. I have all stock.
Tried to go back to mm dload method
1. Rollback package c900b300
2. Full firmware
I did step 1 and instalation was successful 100% but now when i go to about phone my android version is 5.0 NRD90M test keys, not c900b300.
I didn't try to do step 2. because i don't know so much about nrd90m.
Maybe my rollback package is not good, is there difference about rollback package for l19 and l09?
Can anyone help me with my problem? Thank you very much

Kovacc56 said:
Hi all, i have problem with my p9 l19c432 eu version. I had l19 c432b386 android n and i wanted to go bac to mm. My device doesn't have root or unlocked bootloader or custom twrp. I have all stock.
Tried to go back to mm dload method
1. Rollback package c900b300
2. Full firmware
I did step 1 and instalation was successful 100% but now when i go to about phone my android version is 5.0 NRD90M test keys, not c900b300.
I didn't try to do step 2. because i don't know so much about nrd90m.
Maybe my rollback package is not good, is there difference about rollback package for l19 and l09?
Can anyone help me with my problem? Thank you very much
Click to expand...
Click to collapse
That is the correct rollback. You just need to download and flash your stock Marshmallow firmware. In my case (eva-l29c636) it was B191. I had the exact same test keys in "about phone" , so just go ahead with step 2.

brookie229 said:
That is the correct rollback. You just need to download and flash your stock Marshmallow firmware. In my case (eva-l29c636) it was B191. I had the exact same test keys in "about phone" , so just go ahead with step 2.
Click to expand...
Click to collapse
Thanks for your help. I was suspicious because it's not c900b300 after rollback package, it's ''NRD90m test keys'' and i didn't know can i flash full firmware when build number is nrd90m, so i stoped there. I will try to flash full firmware tomorrow.
Do i need to factory reset now or enable OEM in developer options before flashing full firmware or maybe flash rollback package again and maybe then i will get c900b300?
Thanks

Kovacc56 said:
Thanks for your help. I was suspicious because it's not c900b300 after rollback package, it's ''NRD90m test keys'' and i didn't know can i flash full firmware when build number is nrd90m, so i stoped there. I will try to flash full firmware tomorrow.
Do i need to factory reset now or enable OEM in developer options before flashing full firmware or maybe flash rollback package again and maybe then i will get c900b300?
Thanks
Click to expand...
Click to collapse
No, you don't need to factory reset or anything---just flash your correct M firmware.

brookie229 said:
No, you don't need to factory reset or anything---just flash your correct M firmware.
Click to expand...
Click to collapse
I will try. But before that i must ask, do i need to install something more, because many people have problem as i can see on forum with missing apps like camera, keyboard, calculator..??
One more thing, do rollback will erase my personal data and aplications? And when? I asking because when i flashed rollback package, after that my data and aplicafions was still there. Maybe it will erase after flashing full firmware?
Thanks for answer

Kovacc56 said:
I will try. But before that i must ask, do i need to install something more, because many people have problem as i can see on forum with missing apps like camera, keyboard, calculator..??
One more thing, do rollback will erase my personal data and aplications? And when? I asking because when i flashed rollback package, after that my data and aplicafions was still there. Maybe it will erase after flashing full firmware?
Thanks for answer
Click to expand...
Click to collapse
Yes, your data and apps will be gone. When you flash your M firmware it's going to make everything new as if you just opened the box. Sorry if you did not know that. I don't think there is any way to avoid that. I was just setting my device up and noticed an OTA update to B386 Nougat which I successfully updated to BUT then I found out that my P9 will not work on Nougat. I cannot scroll at all with it so I had to find the rollback firmware. I flashed it then immediately after that I flashed B191 Marshmallow and all is well. Nothing else. As I said, you will, however, lose all your data and I don't know if a backup can restore it for you.

brookie229 said:
Yes, your data and apps will be gone. When you flash your M firmware it's going to make everything new as if you just opened the box. Sorry if you did not know that. I don't think there is any way to avoid that. I was just setting my device up and noticed an OTA update to B386 Nougat which I successfully updated to BUT then I found out that my P9 will not work on Nougat. I cannot scroll at all with it so I had to find the rollback firmware. I flashed it then immediately after that I flashed B191 Marshmallow and all is well. Nothing else. As I said, you will, however, lose all your data and I don't know if a backup can restore it for you.
Click to expand...
Click to collapse
Hey friend, i just install full mm firmware and everything is good now, i don`t have nrd90mtest keys, i have now l19c432b182, i found on huawei site for l09 they have rollback package and full firmware b182 so i found for l19. I think good firmware is the key of rollback, and b182 is the best for it. Thanks so much for your help!
I have only one problem, i can`t change themes. I can see themes and when i click apply it, it is successful but it didn`t change. Did you have that problem too?
Thanks again so much

Kovacc56 said:
Hey friend, i just install full mm firmware and everything is good now, i don`t have nrd90mtest keys, i have now l19c432b182, i found on huawei site for l09 they have rollback package and full firmware b182 so i found for l19. I think good firmware is the key of rollback, and b182 is the best for it. Thanks so much for your help!
I have only one problem, i can`t change themes. I can see themes and when i click apply it, it is successful but it didn`t change. Did you have that problem too?
Thanks again so much
Click to expand...
Click to collapse
Happy that it worked out for you. I have an icon on my desktop called "Themes", but when I tap on it there is nothing. I just assumed that was something that you would have to download and install from a Huawei website or get from a 3rd party app. Anyway, it does not concern me as I only care about throwing a pic on for my desktop. What really annoys me is that I cannot run Nougat on my P9
Anyway, good that you have it running again. I am on B191 and it looks like that will be all I can do.

update to emui 5
Hi everyone My current version is EMUI 4.1 and Android 6.0, I have not received an update for Android 7
The mechanic version currently is EVA-C900B136
How do I update to the latest version?
Thanks

brookie229 said:
Happy that it worked out for you. I have an icon on my desktop called "Themes", but when I tap on it there is nothing. I just assumed that was something that you would have to download and install from a Huawei website or get from a 3rd party app. Anyway, it does not concern me as I only care about throwing a pic on for my desktop. What really annoys me is that I cannot run Nougat on my P9
Anyway, good that you have it running again. I am on B191 and it looks like that will be all I can do.
Click to expand...
Click to collapse
I don`t know why is it like that, like some data folders missing from system. Old icons and theme problem, idk how to solve that.
You can see my screenshot of it, rly weird.
https://forum.xda-developers.com/album.php?albumid=14536&pictureid=56441
Can you see my image?
Maybe it`s better for you my friend, emui 5 have great design and everything i must say but battery life is better on mm, bcs of it i rollback to mm. But i don`t know why u can`t get official uograde. When i rollback to mm b182 i got instant upgrade to emui 5. Maybe your version of mm is not good bcs when i had emui4.1.3 i got upgrade to b386 and now when i have 4.1.1 i got upgrade to b383. Maybe you can try to install another version of mm.

adi128 said:
Hi everyone My current version is EMUI 4.1 and Android 6.0, I have not received an update for Android 7
The mechanic version currently is EVA-C900B136
How do I update to the latest version?
Thanks
Click to expand...
Click to collapse
You can update with firmware finder app on playsore, search on forum, you will find tutorial for it.
Or with 3 buttons combination and dload if you can find update, or with twrp if you have it and you will need update file too. Just search on forum tutorial for it and CORRECT update for your phone, single or dual sim whatever you have and with c900 bcs u have global version.

Wrong build number - How to reflash ?

Hi !
I have a NEM-L51C432. I recently installed the new update available (B357) using Huawei Firmware Finder.
Due to some issues, I then decided to rollback to a previous build using the dload method. I succeeded, although I can't recall if the one which worked was B350 or B355.
The problem is, my build is still B357 in the "About phone" menu even though I have the March security patch.
I also noticed that the clock app is missing. Moreover, I get a notification telling me that apps are non-compatible with my phone when I install/update them, even though they work fine.
I can't update system apps (like Chrome or WebView for instance) due to different signature.
I have no idea if these things are related.
So, can someone please tell me how can I get my phone to display the correct build number and eventually correct the other issues in the process ? I'm ready to wipe and re-flash if I have to.
Side question, when I download from HFF in order to use the dload method, most of the time I have the choice between one, two, or even three zips to download.
Each contain a UPDATE.APP file, but I don't get the same files when I extract from it, depending on the zip I downloaded.
Can someone explain me this as well as which file I should prefer (update.zip or one of the other two if available) ?
Thank you.

You need to flash all 3 files via dload.
There is a detailed quide in my signature for dload method. You can flash b350/355/357 or above using that.

shashank1320 said:
You need to flash all 3 files via dload.
There is a detailed quide in my signature for dload method. You can flash b350/355/357 or above using that.
Click to expand...
Click to collapse
Thank you for your answer.
Do you mean I need the three zips from HFF ? For instance, if I try to download B355, I have the choice between these :
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v84990/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...90/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/NEM-L51_hw_eu/update_full_NEM-L51_hw_eu.zip
They all have a UPDATE.APP within them, but they don't have the same files when I extract. What should I do ?

Zarou said:
Thank you for your answer.
Do you mean I need the three zips from HFF ? For instance, if I try to download B355, I have the choice between these :
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v84990/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/NEM-L51_hw_eu/update_full_NEM-L51_hw_eu.zip
They all have a UPDATE.APP within them, but they don't have the same files when I extract. What should I do ?
Click to expand...
Click to collapse
Let me check the files on PC. Will guide you further

shashank1320 said:
Let me check the files on PC. Will guide you further
Click to expand...
Click to collapse
Okay, thanks.
Today I tried re-flashing the update.zip file of all versions via dload, even MM versions. In the end, the only one which worked was the FullOTA-MF-PV of NEM-L51C432B350. All other versions failed to install at 5 %.
I don't know if this is related, but this is the only update which is available as "PV", whatever that means.
In any case, as I said in my first post, my build number is still B357 (while it should be 350) and I don't have the Huawei clock app. Some system apps are impossible to update as well. Plus, this will probably cause issue with future updates...

Zarou said:
Okay, thanks.
Today I tried re-flashing the update.zip file of all versions via dload, even MM versions. In the end, the only one which worked was the FullOTA-MF-PV of NEM-L51C432B350. All other versions failed to install at 5 %.
I don't know if this is related, but this is the only update which is available as "PV", whatever that means.
In any case, as I said in my first post, my build number is still B357 (while it should be 350) and I don't have the Huawei clock app. Some system apps are impossible to update as well. Plus, this will probably cause issue with future updates...
Click to expand...
Click to collapse
Pv is something you can flash via twrp. Regarding misssing apps, flash the smaller file, around 600-800 MB, via twrp and it will restore apps, themes, fm radio etc.

shashank1320 said:
Pv is something you can flash via twrp. Regarding misssing apps, flash the smaller file, around 600-800 MB, via twrp and it will restore apps, themes, fm radio etc.
Click to expand...
Click to collapse
Can't flash the update.zip with TWRP (at least, with OldDroid's). However, I did managed to get back missing apps by flashing the second zip file, thank you about that.
Doesn't work with the third one though, and my build number is still wrong. Any idea about how to fix this ?

Zarou said:
Can't flash the update.zip with TWRP (at least, with OldDroid's). However, I did managed to get back missing apps by flashing the second zip file, thank you about that.
Doesn't work with the third one though, and my build number is still wrong. Any idea about how to fix this ?
Click to expand...
Click to collapse
Which build number you flash and which is the one showing?
yes, only 2nd file will work and bring back the missing apps.

shashank1320 said:
Which build number you flash and which is the one showing?
yes, only 2nd file will work and bring back the missing apps.
Click to expand...
Click to collapse
In the end, I solved the issue by extracting the VERSION.img file from the UPDATE.APP of the third zip and flashing it with TWRP.
I then updated to B355 and B357 with HFF proxy.
Weird thing is, the B357 update re-locked my bootloader and when I unlocked it again, I was stuck with an old version of Google Play Services which couldn't be updated (different signature issue). Luckily, I had a backup from the previous update but this is weird.
Thanks for your help. You've done a lot.