Database Develop

Problem with installing Nougat firmware and apps onto Huawei P9 EVA-L09. Please help!

Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.

Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.

chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.

I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...

I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &

tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!

If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....

chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.

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!

Problem to update to 7.0 or go back to original ROM

Good morning all:
I am having a problem with my phone.
The history...
Bought a P9 EVA-L19 in Belgium and it came originally with version B127 (I think).
So, I decided to root it and so I used SRKTool to unlock bootloader, install TWRP and root.
Problems started when I tried to update to a newer ROM.
It lost the original look and some functionalities, like the random imagens in lock screen and some original apps (FM Radio?)
In the meantime I managed to update to B137. The look was ugly but I managed to solve it using Nova Launcher.
Then the phone started giving me the message there was an update to B342 but everything fails.
I tried to reblock bootloader with SRKTool but it fails, I tried to download and install with dload method and fails.
So, I'm stuck with B137.
I even tried to debrand using this method: https://youtu.be/JZVsIKtdgV4
But after the first step "changing oeminfo and custom.bin" I even lost the keyboard so I gave up following the next steps.
So now my phone has a ROM EVA-L19900B137 and I can't find a way of updating to android 7.0 and I can't go back to the original ROM with all the functions.
Tha only thing I haven't tried is an Update using TWRP.
Is there a final release of 7.0 that can be flashed using TWRP?
Or even the original ROM?
(no, I know I am stupid but didn't made a backup before root and updates :crying: )
Thank you so much in, in advance, for your time.

I am not expert in these stuff but when I completely removed my system I installed a rom with different cust after that I got c900 then again I removed system and just installed the old cust "c185" and version b161 and then it worked like a charm even updates are working

your original dload method should be working. Just flash an original firmware with your original cust. This will lock your bootloader and turn your phone to original. You will even get the OTA updates.
After that if there is still no nougat update for your phone, there is 2 option. 1st one is check if there is an update that has the same cust number with your phone and apply it.
If not so, you can do a debranding procedure. Here is the link for it: https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523

I managed to fix it.
Just in case someone has the same problem, I used the solutions/methods described on these threads:
1st
https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
2nd
https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
thank you guys for your replies!

[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. :/

Bootloop on pra_lx1 p8 lite 2017 oreo twrp and hurupdater issue

Hello everyone.
Last night i am tried to update my EMUI 5.0.2 Pra-lx1 p8 lite 2017 phone to the Oreo update 8.0.0.322 downloaded from Team TMs' huawei firmware finder.
My phone is allready "Bootloader unlocked" and "FRP unlocked" there is no problem. I can reach to TWRP( there is a huge problem i will explain it).
on the top of my way i got EMUI 5.0.2 and i unlocked the bootloader and FRP.
then i installed the EliteTWRP-3.2.1.
after this i downloaded
HuRUpdater 0_3.zip
and the 3 neccesery FullOTA-MV-OP files that includes the
update.zip
update_data_full_public.zip
update_full_PRA-L11_hw_eu.zip
then i do everything exatly on this thread
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
and voilla!!! i got the Oreo update installed.
BUT....
i dont get the file manager app its lost!
i can not get themes or get in any of huawei apps sign in or get in!
so for this. my next step is goint to do reflash the oreo how i did it again.
BUT....
i can not do this because the instaled TWRP does NOT support OREO. Applause for this
so i'am tried 3 different TWRP that can be used on HUAWEI phones.
First one is this i dont know who is the developer but ists intercafe is chinese or korean.
https://drive.google.com/file/d/1rlQPRP234PoXY_yqup3oK_joOZGSIker/view
i tried to instal this over adb fastboot. BUT I can NOT. Because Oreo will do this on RAMDISK_RECOVERY!!!! WOOOWWWW
i did this and i reinstaled the oreo update like i did it first but in this new TWRP.
İt flashed my OREO but on the bootlogo the HUAWEI opening sound curropted before finished the sound and gets to restart.
after restart eRecovery opens and give me TWO funcional choises!!! Like Jig SAW
anyway...
the first option is DOWNLOAD LATEST VERSION AND RECOVERY
BUT for my chanse!!!! or mean bad LUCK!!! eRecovery WiFi doesnt see the EDUROAMs ACCESS POINTS WELL RIGHT!!!!
so i passed the first one and we are on the MAGICAL point.
the second option is the WIPE DATA/FACTORY RESET
on this time i CAN NOT DO THIS BECAUSE THE ORGININAL RECOVERY PART IS GONE!!!! YEAP I CAN NOT DO FACTORY RESET.
WHEN i choose this option it will go to the TWRP recovery nice huh!? NO.
so what will i do i know my phone is not BRICKED YET! İF THERE İS TWRP THERE İS HOPE!
BUT I DO NOT KNOW WHAT SHOULD I DO RIGHT KNOW
please help me....

with this Recovery (TWRP)( not usefull beacuse you can not use them )
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/recovery-recoveryoreonocheck-install-t3777974
i found this under a members signature and i give a try but it wont work this gives me just a big error
But this error gets my phone a factory reset after than i flashed this Recovery (better then the chinesee korean languges type one ;D )
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/unofficial-twrp-3-2-1-0-oreo-t3773970
and i tried to flash the Oreo update again with HuRUpdater_0_3.zip
but now I am at the begining. System works there is no issue over hardware.
But there is missing system apps like File Manager. Themes and so on....
And the best thing is The BUILD NUMBER is 8.0.0.046(08TO)
BUT I flashed the f*ckn' 8.0.0.322!!!!! WHY GOD!!!! WHY!!!!
Could anybody iluminte about what the hell is going on right now please i need to know why is why

Dude you need to rename the files before you put them in the folder
HuRUpdater 0_3.zip --> just delete the number (HuRUpdater.zip)
update_data_full_public.zip --> update_data_public.zip
update_full_PRA-L11_hw_eu.zip --> update_all_hw.zip

marstonpear said:
Dude you need to rename the files before you put them in the folder
HuRUpdater 0_3.zip --> just delete the number (HuRUpdater.zip)
update_data_full_public.zip --> update_data_public.zip
update_full_PRA-L11_hw_eu.zip --> update_all_hw.zip
Click to expand...
Click to collapse
thanks for your response. but i mention it i did it everything right. i do not think that only delete 3 piece of character get back the File manager or themes or huawei applications .

z1rqdym said:
thanks for your response. but i mention it i did it everything right. i do not think that only delete 3 piece of character get back the File manager or themes or huawei applications .
Click to expand...
Click to collapse
It would, main issue is that HuRUpdater is made for many Huawei phones not just for prague, when you flash the HuRUpdater.zip it can only flash the update.zip because you don't need to rename it. It doesn't flash the other zips because they're not named correctly, hence the updater can't find the zips to flash.

marstonpear said:
It would, main issue is that HuRUpdater is made for many Huawei phones not just for prague, when you flash the HuRUpdater.zip it can only flash the update.zip because you don't need to rename it. It doesn't flash the other zips because they're not named correctly, hence the updater can't find the zips to flash.
Click to expand...
Click to collapse
there is a misunderstood i allready rename the 3 update files. i used two times the nocheck recovery method and works well but the issue is the same. i only dont rename the hurupdater file. i will give a try now.

Let me know if it works, if that doesn't work for you too I can't help you but I just uploaded the stock oreo erecovery to GDrive and you can download it and flash it to recovery_ramdisk partition (because you are on Oreo) then make a factory reset or go back to nougat https://drive.google.com/open?id=157C0CI5CqSEzvQRB7Yt5K1WPtYBcaO08
EDIT: I didn't read it right sorry that you can't connect to wifi. Try wiping data-cache-dalvik-system on TWRP and then flashing the HuRUpdater.zip
You may also have a bad download, I mean one of the zip files you have may be corrupted

marstonpear said:
Let me know if it works, if that doesn't work for you too I can't help you but I just uploaded the stock oreo erecovery to GDrive and you can download it and flash it to recovery_ramdisk partition (because you are on Oreo) then make a factory reset or go back to nougat https://drive.google.com/open?id=157C0CI5CqSEzvQRB7Yt5K1WPtYBcaO08
EDIT: I didn't read it right sorry that you can't connect to wifi. Try wiping data-cache-dalvik-system on TWRP and then flashing the HuRUpdater.zip
You may also have a bad download, I mean one of the zip files you have may be corrupted
Click to expand...
Click to collapse
same result i did it just you are said. it flashed oreo and it booted and works. But there is no File manager can not use themes. Build number is 8.0.0.046(08TO). I can make call connect to internet over LTE / 3G / EDGE.
is this issue are from that my phone is from another region instead from europe? İ downloaded the PRA-LX1C432B322-(8.0.0.322) from Team MT FirmwareFinder over Huawei host servers three times. even i download the stock nougat rom in the same way. I flashed the nougat but this time build number is NRD-testkeys . same issue file manager themes not appear or work.

z1rqdym said:
same result i did it just you are said. it flashed oreo and it booted and works. But there is no File manager can not use themes. Build number is 8.0.0.046(08TO). I can make call connect to internet over LTE / 3G / EDGE.
is this issue are from that my phone is from another region instead from europe? İ downloaded the PRA-LX1C432B322-(8.0.0.322) from Team MT FirmwareFinder over Huawei host servers three times. even i download the stock nougat rom in the same way. I flashed the nougat but this time build number is NRD-testkeys . same issue file manager themes not appear or work.
Click to expand...
Click to collapse
If you get that build number issue on nougat it might be about your oeminfo partition. Try flashing PRA-LX1C432 oeminfo on this thread : https://forum.xda-developers.com/8-lite/how-to/share-oeminfo-t3740734
Beware, it locks your bootloader, so unlock it after you flash the file. Then start erecovery and download the nougat firmware to get your device ready for Oreo, then flash the HuRUpdater.zip . I hope this works!

marstonpear said:
If you get that build number issue on nougat it might be about your oeminfo partition. Try flashing PRA-LX1C432 oeminfo on this thread : https://forum.xda-developers.com/8-lite/how-to/share-oeminfo-t3740734
Beware, it locks your bootloader, so unlock it after you flash the file. Then start erecovery and download the nougat firmware to get your device ready for Oreo, then flash the HuRUpdater.zip . I hope this works!
Click to expand...
Click to collapse
is this rebranding changes my device IMEI adress? if it is so my unlock code do not work?

z1rqdym said:
is this rebranding changes my device IMEI adress? if it is so my unlock code do not work?
Click to expand...
Click to collapse
I don't think it changes the IMEI. I had a pra-lx1c464(Turkey) and I rebranded it to c432 I had no issues with it. It will change your device to Dual-SIM though if you have a single SIM device, which has no effect at all. I can still use my bootloader unlock code, and I have used it many time again and again after rebranding the device. Also you're trying to install PRA-LX1C432B322 Oreo right? Your device should be branded as PRA-LX1C432 first

is it neccesery to download the nougat rom from eRecovery over wifi?

z1rqdym said:
is it neccesery to download the nougat rom from eRecovery over wifi?
Click to expand...
Click to collapse
I'm not sure but it is necessary to have it branded as PRA-LX1C432

I will give a try flash the oeminfo c432 then try to flash nougat with nocheck image.

nope nothing works... I flashed the oem info from the link that you givin here. but the oeminfo doesnt change the Build number but the device changed to honor 8 lite chinese normal version on nougat. After flashed the oreo the build number dont changed and the themes not working file manager also not excist.

Factory reset
z1rqdym said:
nope nothing works... I flashed the oem info from the link that you givin here. but the oeminfo doesnt change the Build number but the device changed to honor 8 lite chinese normal version on nougat. After flashed the oreo the build number dont changed and the themes not working file manager also not excist.
Click to expand...
Click to collapse
Have you tried to reset the phone to its factory defaults . In this way I fixed missing apps problem .

I tried factory reset over Recovery bu it doesnt changed any thing. Then i tried the factory reset from the settings of the rom. Same result.

I just installed it manually. I have the 8.0.0.46 (08TO) but I don't have any issue, I have apps and themes..is it correct the version not should I expecting something different?
Please let me know

Same build number as in my settings. Themes wont work because regional issues. When i change phones language to english themes apps works well. Thats the themes app i admit it but.. in the other hand i dont get the in games(i dont remember the original name of it) app comes with oreo. I dont have the huawei login future anymore i think this is because of the unlocked bootloader not tried to look again then do a factory reset. I can not rebrand my phone. I know because when i flash europen oeminfo or not if i install the stock emui 5.0.3 again it says no build number against test keys . On the other side i can use my phone well i dont have any problem. And i forgot to say i dont even the file manager i installed the hidisk apk that i found on internet.
My advise is dont do this to your phones wait for a official update. But for us this is a long hard road