Database Users

Upgrade to 5.1 beta?

Hello Everyone, I have ALE-L21 and my current firmware is C185B130 (apparently C185 is UAE region but i live in pakistan). Device is bootloader unlocked, rooted with TWRP installed.
I have a TWRP backup of current rom. I wanna try the 5.1 beta released for Europe but it says here ( http://forum.xda-developers.com/p8lite/general/beta-firmware-p8-lite-ale-l21-c432b008-t3243228 ) that i need C432B132 to upgrade to this. So I downloaded this firmware(C432B132) from Huawei website. There were two folders in it, dload and CUSTOM(not sure what that for). I extracted system.img, recovery.img, CUST.img, boot.img from UPDATE.APP given in the dload folder. So here is what i'm thinking.
1) Flashing the extracted system.img, recovery.img, CUST.img, boot.img would get me to C432B132?
2) After i install B132 can I upgrade to 5.1 using EMUI local update?
3) If something goes wrong, can I just flash TWRP and restore the backup?
-
Or this whole idea is foolish and i would screw up my phone after flashing system, cust and boot of some other firmware designed for some other region???

SobanAmin said:
Hello Everyone, I have ALE-L21 and my current firmware is C185B130 (apparently C185 is UAE region but i live in pakistan). Device is bootloader unlocked, rooted with TWRP installed.
I have a TWRP backup of current rom. I wanna try the 5.1 beta released for Europe but it says here ( http://forum.xda-developers.com/p8lite/general/beta-firmware-p8-lite-ale-l21-c432b008-t3243228 ) that i need C432B132 to upgrade to this. So I downloaded this firmware(C432B132) from Huawei website. There were two folders in it, dload and CUSTOM(not sure what that for). I extracted system.img, recovery.img, CUST.img, boot.img from UPDATE.APP given in the dload folder. So here is what i'm thinking.
1) Flashing the extracted system.img, recovery.img, CUST.img, boot.img would get me to C432B132?
2) After i install B132 can I upgrade to 5.1 using EMUI local update?
3) If something goes wrong, can I just flash TWRP and restore the backup?
-
Or this whole idea is foolish and i would screw up my phone after flashing system, cust and boot of some other firmware designed for some other region???
Click to expand...
Click to collapse
No this is wrong
1. You need to downgrade to B052
2. Install B136a
3. Install B008(Android 5.1.1)
After each install is recommended to make wipe

Thanks
sokkoban said:
No this is wrong
1. You need to downgrade to B052
2. Install B136a
3. Install B008(Android 5.1.1)
After each install is recommended to make wipe
Click to expand...
Click to collapse
I dont think that you need to go all the way to B052 and then flash the required version
This is what i did:
1) Flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( I dont remember exactly :silly: ).
2) I flashed the UPDATE.APP file that was in the CUSTOM folder (that came with B132 rar file) via EMUI and it restored my build to B132.
3) Tried updating to 5.1 via EMUI but failed.
4) To give it a last try, I downloaded and flashed my phone with CUST, recovery, system, boot.img of B136a and then the update worked. My phone is now 5.1.1 B006
Thanks for the reply mate :good:

Confirmation ?
sobanamin said:
i dont think that you need to go all the way to b052 and then flash the required version
this is what i did:
1) flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( i dont remember exactly :silly: ).
2) i flashed the update.app file that was in the custom folder (that came with b132 rar file) via emui and it restored my build to b132.
3) tried updating to 5.1 via emui but failed.
4) to give it a last try, i downloaded and flashed my phone with cust, recovery, system, boot.img of b136a and then the update worked. My phone is now 5.1.1 b006 :d
thanks for the reply mate :good:
Click to expand...
Click to collapse
i also have p8 lite c185b130 is this confirmly working ?

wahaj0892 said:
i also have p8 lite c185b130 is this confirmly working ?
Click to expand...
Click to collapse
yeah its working fine. I think the battery life has improved a little bit or maybe it is just because i haven't installed much apps after flashing this rom compared to when I was using the B130. The only thing i miss from B130 is that small 2g, 3g written on the signal bars. This one only shows the 2g or 3g network type when the mobile data is turned on. Huawei cloud is also not present in it so you may wanna backup your contacts and stuff

SobanAmin said:
yeah its working fine. I think the battery life has improved a little bit or maybe it is just because i haven't installed much apps after flashing this rom compared to when I was using the B130. The only thing i miss from B130 is that small 2g, 3g written on the signal bars. This one only shows the 2g or 3g network type when the mobile data is turned on. Huawei cloud is also not present in it so you may wanna backup your contacts and stuff
Click to expand...
Click to collapse
thanks for the reply ...
some more question do i need a unlock bootloader ?
secondly i have a wired problem while typing my phone has a double tap issue is that gone ?

Hello,
Double tap issue still present in beta

sokkoban said:
Hello,
Double tap issue still present in beta
Click to expand...
Click to collapse
I dont use it often so I cant tell for sure

please im on b130 (5.0.1)
can you tell me (step by step) how can i get (5.1.1) my (bootloader unlocked with stovk recovery) please please

mimoriich said:
please im on b130 (5.0.1)
can you tell me (step by step) how can i get (5.1.1) my (bootloader unlocked with stovk recovery) please please
Click to expand...
Click to collapse
Hello,
Read this post, will help you http://forum.xda-developers.com/showpost.php?p=63993458&postcount=3

sokkoban said:
Hello,
Read this post, will help you http://forum.xda-developers.com/showpost.php?p=63993458&postcount=3
Click to expand...
Click to collapse
please tell me how u flash it i putted dload file to sd card & i reeboted (home + vol down + vol up ) its said error

SobanAmin said:
I dont think that you need to go all the way to B052 and then flash the required version
This is what i did:
1) Flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( I dont remember exactly :silly: ).
2) I flashed the UPDATE.APP file that was in the CUSTOM folder (that came with B132 rar file) via EMUI and it restored my build to B132.
3) Tried updating to 5.1 via EMUI but failed.
4) To give it a last try, I downloaded and flashed my phone with CUST, recovery, system, boot.img of B136a and then the update worked. My phone is now 5.1.1 B006
Thanks for the reply mate :good:
Click to expand...
Click to collapse
Can I apply this process for my ALE-L21C636B150...?

mimoriich said:
please tell me how u flash it i putted dload file to sd card & i reeboted (home + vol down + vol up ) its said error
Click to expand...
Click to collapse
If you are in stock recovery and have B132 try to put dload folder in internal memory and use software updater
Rifat Nurr said:
Can I apply this process for my ALE-L21C636B150...?
Click to expand...
Click to collapse
No, you can't. This beta is only for B136a(may be work also in B132)

sokkoban said:
Hello,
Double tap issue still present in beta
Click to expand...
Click to collapse
what about b170 ??

SobanAmin said:
I dont think that you need to go all the way to B052 and then flash the required version
This is what i did:
1) Flashed 132 cust, recovery, boot, system. My build number changed to something like balong ( I dont remember exactly :silly: ).
2) I flashed the UPDATE.APP file that was in the CUSTOM folder (that came with B132 rar file) via EMUI and it restored my build to B132.
3) Tried updating to 5.1 via EMUI but failed.
4) To give it a last try, I downloaded and flashed my phone with CUST, recovery, system, boot.img of B136a and then the update worked. My phone is now 5.1.1 B006
Thanks for the reply mate :good:
Click to expand...
Click to collapse
can i flash c136a direcly over c185b130

MAYBE
wahaj0892 said:
can i flash c136a direcly over c185b130
Click to expand...
Click to collapse
Give It a try. If i doesn't work then you can just flash 132->136 and then apply update. But there maybe some problem with the version number changing to "BALONG". I faced this problem when I flashed 132 over my 130 but then I applied UPDATE.APP file(the small file in the custom folder) via EMUI Updater and it fixed the version number. But the 136a rom did not had any UPDATE.APP in custom folder so I dont know what to do if you get a version number problem. You can try flashing the 5.1 update via EMUI and maybe it will fix the version number problem (if it happened in the first place) or you can always goto 132->136 and apply 5.1

wahaj0892 said:
thanks for the reply ...
some more question do i need a unlock bootloader ?
secondly i have a wired problem while typing my phone has a double tap issue is that gone ?
Click to expand...
Click to collapse
yes you need to unlock the boot loader. What exactly do you mean by double tap issue? are you talking about the double tap to wake feature not working sometimes? Yes the DoubletapToWake dont works sometime which can be very annoying so I just disabled that feature and using the power button ever since. As for the typing issue, No I'm not facing any typing issues, never did on the B130 and not on this 5.1 version. Try using someother keyboard app?

SobanAmin said:
yes you need to unlock the boot loader. What exactly do you mean by double tap issue? are you talking about the double tap to wake feature not working sometimes? Yes the DoubletapToWake dont works sometime which can be very annoying so I just disabled that feature and using the power button ever since. As for the typing issue, No I'm not facing any typing issues, never did on the B130 and not on this 5.1 version. Try using someother keyboard app?
Click to expand...
Click to collapse
it is related to typing .. fast typing cause this issue .. i tired many apps nothing fix the issue

wahaj0892 said:
can i flash c136a direcly over c185b130
Click to expand...
Click to collapse
I tried to install b132 and b136a on my c185b130 but it failed both times.
---------- Post added at 06:27 PM ---------- Previous post was at 06:22 PM ----------
SobanAmin said:
Give It a try. If i doesn't work then you can just flash 132->136 and then apply update. But there maybe some problem with the version number changing to "BALONG". I faced this problem when I flashed 132 over my 130 but then I applied UPDATE.APP file(the small file in the custom folder) via EMUI Updater and it fixed the version number. But the 136a rom did not had any UPDATE.APP in custom folder so I dont know what to do if you get a version number problem. You can try flashing the 5.1 update via EMUI and maybe it will fix the version number problem (if it happened in the first place) or you can always goto 132->136 and apply 5.1
Click to expand...
Click to collapse
I have c185b130, there is c185b131 update on consumer.huawei.com for UAE region uploaded on 31-12-2015, will it work on my device? What are the changes in c185b130 and c185b131?

Missing some settings and system apks (Nougat B336)

I have the problem.
I miss app twin and private space from settings(it doesn't exist) also missed (Files and Huawei ID, but installed apks for them), how to get them without downgrading to MM and installing again?
Is it possible by extracting apk for those files and installing or by dload method?
Or will I get these things if I upgrade when next nougat version is available via 3 buttons method?
Please someone help.

Coolyou said:
I have the problem.
I miss app twin and private space from settings(it doesn't exist) also missed (Files and Huawei ID, but installed apks for them), how to get them without downgrading to MM and installing again?
Is it possible by extracting apk for those files and installing or by dload method?
Or will I get these things if I upgrade when next nougat version is available via 3 buttons method?
Please someone help.
Click to expand...
Click to collapse
You do not install it corectly (for Files and Huawei ID). You have to install both zip one by one.

I did like its written in badwolf's thread. Flashed with meticulus both zip files in order without reboot. But i flashed new files b336 for the first time not b328/9. And saw some more people missed some system apks and features

b336 still need update_data_full, It should flash somehow like this:
* twrp > restore OEMINFO_VNS-L31 ( only for non vns-l31 models )
* twrp > format Data ( only for nougat twrp )
twrp > install update_data_full_VNS-L31_hw_eu.zip
* bootloader > flash recovery_stock.img ( if dload flash not work)
flash update.app by dload
eRecovery > Factory reset ( not wipe data in twrp, it will wipe the update_data_full )

Hello. Thanks for respond but my bootloader locked after i used 3buttons method and cant unlock again with same code. It says invalid. What can i do now? Also cant get new one from huawei site says to check imei/serial code

Coolyou said:
Hello. Thanks for respond but my bootloader locked after i used 3buttons method and cant unlock again with same code. It says invalid. What can i do now? Also cant get new one from huawei site says to check imei/serial code
Click to expand...
Click to collapse
Your former unlock code is okey.
Make sure your settings> developer option> oem unlock is enabled and do the unlock thing properly
Code:
adb reboot bootloader
fastboot oem unlock your_formor_unlock_code
if it can't work, the response shoud be "FAILED (remote: password wrong)", not invalid.

Is it possible to have single apks for Nougat apps like Huawei backup and Huawei ID? Cause I had problem to install the data pack and I'm running B336 on my L-31 with bootloader locked. But I want to back everything up before try again with the installation...
Cheers.

drleto said:
Is it possible to have single apks for Nougat apps like Huawei backup and Huawei ID? Cause I had problem to install the data pack and I'm running B336 on my L-31 with bootloader locked. But I want to back everything up before try again with the installation...
Cheers.
Click to expand...
Click to collapse
Saved with pc hisuite. it's easier.

Thanks for the reply!
The problem is that hisuite wants huawei backup to backupping my phone..
Cheers

drleto said:
Thanks for the reply!
The problem is that hisuite wants huawei backup to backupping my phone..
Cheers
Click to expand...
Click to collapse
Ok, I found inside data.zip all the single apks. Now the problem is that I can't install every single app (file manager yes, but Huawei backup no) cause it gives me some error messages. Any ideas?

DO NOT USE BADWOLF'S THREAD BECAUSE IT'S OUTDATED.
Use the "Ultimate guide for Nougat" THREAD.
---------- Post added at 09:48 AM ---------- Previous post was at 09:48 AM ----------
You can install Nougat using 3 button method too....

Johnny TDN said:
DO NOT USE BADWOLF'S THREAD BECAUSE IT'S OUTDATED.
Use the "Ultimate guide for Nougat" THREAD.
---------- Post added at 09:48 AM ---------- Previous post was at 09:48 AM ----------
You can install Nougat using 3 button method too....
Click to expand...
Click to collapse
ok, thank you. Posted right now.

Rollback NXT-AL10 TO EMUI 6 ?

HI
can anyone help me to rollback my nxt-al10 to emui 6 please

drlsd said:
HI
can anyone help me to rollback my nxt-al10 to emui 6 please
Click to expand...
Click to collapse
Emui 6 ?? or maybe you want to say emui 4 and android 6 ??

Yes ,thank you very much ,i mean emiu 4.1 please

drlsd said:
Yes ,thank you very much ,i mean emiu 4.1 please
Click to expand...
Click to collapse
unlock & flash TWRP recovery & flash another firmware using TWRP
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146

I would like too to rollback my nxt-al10 from emui 5.0 (android 7.0) to emui 4.0 or 4.1.
Now my rom is nrd90m test-keys (AL10).
I read last post and I don't know how to unlock & flash TWRP recovery - before emui 5.0 I use SRKToolHuawei but now SRKTool don't support emui 5.0
Guys pleas help me.

bodzio3333 said:
I would like too to rollback my nxt-al10 from emui 5.0 (android 7.0) to emui 4.0 or 4.1.
Now my rom is nrd90m test-keys (AL10).
I read last post and I don't know how to unlock & flash TWRP recovery - before emui 5.0 I use SRKToolHuawei but now SRKTool don't support emui 5.0
Guys pleas help me.
Click to expand...
Click to collapse
If you're​ on nrd90m test key ,you can simply dload your last EMUI4 or 4.1 rom
Sent from my Huawei Mate 8 using Tapatalk

amin318 said:
If you're​ on nrd90m test key ,you can simply dload your last EMUI4 or 4.1 rom
Sent from my Huawei Mate 8 using Tapatalk
Click to expand...
Click to collapse
I tried with dload method rom NXT-AL10C00B386 and while after boot in update I see that:
Software install failed!
Incomatibility with current version.
Please download the correct update package.
Please help

​
bodzio3333 said:
I tried with dload method rom NXT-AL10C00B386 and while after boot in update I see that:
Software install failed!
Incomatibility with current version.
Please download the correct update package.
Please help
Click to expand...
Click to collapse
Did you change your phone's cust version? If u changed it you should dload a firmware (4/4.1) that match with your new cust
I rolled back with this method dozen times when EMUI 5 was not officiall!
Sent from my Huawei Mate 8 using Tapatalk

amin318 said:
​
Did you change your phone's cust version? If u changed it you should dload a firmware (4/4.1) that match with your new cust
I rolled back with this method dozen times when EMUI 5 was not officiall!
Sent from my Huawei Mate 8 using Tapatalk
Click to expand...
Click to collapse
No. this time my rom was stock I dload NXT-AL10C00B386, lost root and unlock bl and them do OTA to EMUI 5.0.
I realy don't know when I stuck od NRD90M. One time I pull the phone out of my pocket and see red message after reboot... that's all.
Hisute can't help me, I try.
Some advices, please.

bodzio3333 said:
No. this time my rom was stock I dload NXT-AL10C00B386, lost root and unlock bl and them do OTA to EMUI 5.0.
I realy don't know when I stuck od NRD90M. One time I pull the phone out of my pocket and see red message after reboot... that's all.
Hisute can't help me, I try.
Some advices, please.
Click to expand...
Click to collapse
Is that red message verification failed message?
If yes then please unlock the bootloader again even if it says unlocked. Then it will do factory reset and the red message will disappear.
You can then try to flash the stock firmware in TWRP. You can use B368 or B386 stock firmware from another thread and flash in TWRP. That is if you have TWRP. If you don't then unlock bootloader and then install TWRP using SRK tools. You can use SRK tools for adb commands also. Just type 000 on first page off srk tools and you will get into command prompt. Using that push the TWRP into your phone. ADB is very stable in srk tools and it will always identify your device. So that problem you won't have.
I couldn't find a proper rollback for AL10 . May be some one else can give if it is there for this model. If it was L29 model then rollback package is available and you can easily rollback using that in this type of situation.
If the flashing of stock ROM worked then you try to debrand your phone to L29 later. You will have many options then and L29 firmwares are more stable. I have AL10 which I debranded to L29 & I totally recommend debranding to C432 once your problem is solved
Do the above steps only if you are on marshmallow firmware.
Don't forget :good::good::good::good::good:

I created a al10 roll back for all al10 phones. It converts it to a DL0017 dual active sim. Message me for details how to obtain it from me .. MUST have twrp installed .

Samavb said:
Is that red message verification failed message?
If yes then please unlock the bootloader again even if it says unlocked. Then it will do factory reset and the red message will disappear.
You can then try to flash the stock firmware in TWRP. You can use B368 or B386 stock firmware from another thread and flash in TWRP. That is if you have TWRP. If you don't then unlock bootloader and then install TWRP using SRK tools. You can use SRK tools for adb commands also. Just type 000 on first page off srk tools and you will get into command prompt. Using that push the TWRP into your phone. ADB is very stable in srk tools and it will always identify your device. So that problem you won't have.
I couldn't find a proper rollback for AL10 . May be some one else can give if it is there for this model. If it was L29 model then rollback package is available and you can easily rollback using that in this type of situation.
If the flashing of stock ROM worked then you try to debrand your phone to L29 later. You will have many options then and L29 firmwares are more stable. I have AL10 which I debranded to L29 & I totally recommend debranding to C432 once your problem is solved
Do the above steps only if you are on marshmallow firmware.
Don't forget :good::good::good::good::good:
Click to expand...
Click to collapse
Thank you for help
Yes it is red message verification failed message.
I'll change AL10 to L29C432 when I can do that
The bigest problem is that I stuck on androit 7.0 emui 5.0.
So maybe you help me unlock bl (I have unlock code) and flash TWPR....

Unlock bootloader ADB commands + Stock + Debrand
bodzio3333 said:
Thank you for help
Yes it is red message verification failed message.
I'll change AL10 to L29C432 when I can do that
The bigest problem is that I stuck on androit 7.0 emui 5.0.
So maybe you help me unlock bl (I have unlock code) and flash TWPR....
Click to expand...
Click to collapse
If you want to unlock bootloader through ADB?
Here are the steps.
In your phone go to settings - >developer options - > put usb debubbing ON
switch off the phone.
Press and hold the down button for 3 seconds & then connect it to the computer
It will then go to fastboot mode.
then open SRK tools
type 000 to enter the command prompt.
Type the following command
fastboot oem unlock xxxxxxxxxxxxx
In this command xxxxxxxx is your bootloader code. just replace xxxxxxx with your code and press enter.
This will unlock your bootloader & will do a factory reset.
In SRK tools there is an option for bootloader unlock but I think that is only if you are in EMUI 4.0 or EMUI 4.1 that is what I think may be anyone else who tried this option in android 7.0 can confirm but the adb commands will work.
I have enclosed screenshots for better understanding.
you have mentioned that you are in Android 7.0
Can you tell me your exact firmware that you have on your phone at the moment?
After you get rid of that red message. Your bootloader is unlocked.
There is Erecovery process - > steps below (but there is a problem with this process)
1)Switch off the phone.
2) Press and hold the volume up button and then connect your phone to computer or charger. Yes charger. Then you can download stock firmware through your WIFI - > this will also install stock firmware. But I think this won't work because of unlocked bootloader
So once again install the TWRP for Android 7.0 I think it is Twrp 3.0.2 or Twrp 3.0.3 - > this is definitely for nougat.
ADB command to install twrp recovery is
fastboot flash recovery twrp.img ( rename the TWRP to twrp.img ) in the adb.
Try to flash the stock firmware zip files in TWRP.
Here you have two options - > You can either try flashing B386 files (only one zip file) or B562 (android 7.0 - > 2 zip files - first update.zip and then the other zip file)
If you are successful in this step then your TWRP will be overwritten with stock recovery.
That is ok. don't worry. Kangvip ROM is pre-rooted ROM. So you will get root in the end. For now its ok to be on Stock at this step.
Stock Recovery + Stock ROM + bootloader locked -> then you can dload back to EMU 4.1 using B386 firmware.
Then you can unlock bootloader (again) yes its a pain + followed by TWRP + ROOT - one after the other in SRK tools its all there. you can use the options in SRK tools this time.
And once you have root again.
Take backup and save it on your SD card. (except DATA , take backup of all options listed there, why? bcoz if you include data - > it will increase the backup size and it will take more time.
*Disclaimer* -> Very tricky & risky process - proceed with caution & full attention
Then - > you can debrand - > to C432 -(debranding is very tricky process, so keep your backup handy) This should be done very carefully because any problem here means you might find less space on your internal memory. Then you will have to restore that backup to get back your space.
Here is the link to excellent tutorial by somboons Watch it carefully.
https://www.youtube.com/watch?v=JZVsIKtdgV4
Just follow that as it is for debranding from AL10 to L29-C432
I am very very sorry for all these confusing and tricky steps. Please proceed with caution when you are doing the debranding process. Do not get diverted during that process.
Yes I did all this when I debranded my Huawei Mate 8 AL10 to L29. I had lot of anxious moments, doubts & my mind started playing tricks if mate 8 was dead on few occassions. But in the end my phone prevailed. Now I am happily using L29 - Kangvip B577. That is where I want you to land up in the end.
Do not worry and do not panic any time. Be prepared to face few challenges during this process. I will help you but please share your experience and follow the steps carefully.
During debranding you might have your phone rebooting or something might happen. That time do factory reset and continue from where you left off. If you get red message - > then you have to unlock bootloader. Otherwise continue.
This whole process will test your patience & consume time. So I hope you are willing to do this. Its worth it. I learnt my lesson, I am never buying chinese version of Huawei phones/tablets again. Only European models from now onwards.
Finally
Do not forget to click on :good::good::good::good::good::good::good:
I hope you understand.

I stared few hours ago.
First unlock bl - red message disapire
After bl I was error durind format bus system run witout any problem.
Then flash TWRP 3.1.0-2 and try to flash NXT-AL10C00B368-update.zip but I see this:
http://gofile.me/6tsPr/sHOJ4cLcr
http://gofile.me/6tsPr/cXniG4g8D
Some advices?

Options
bodzio3333 said:
I stared few hours ago.
First unlock bl - red message disapire
After bl I was error durind format bus system run witout any problem.
Then flash TWRP 3.1.0-2 and try to flash NXT-AL10C00B368-update.zip but I see this:
http://gofile.me/6tsPr/sHOJ4cLcr
http://gofile.me/6tsPr/cXniG4g8D
Some advices?
Click to expand...
Click to collapse
TWRP 3.1.0.2 is actually used for flashing nougat firmwares.
Which firmware are you on right now?
Are you on nougat or marshmallow? Please provide the full firmware build number.
if your phone is on marshmallow.
TWRP version depends on your firmware.
If you are on EMUI 4.0/4.1 then pls use the TWRP 3.0.2
you can use SRK tools to install that TWRP if you are on EMUI 4.0/EMUI 4.1
Install that version. Then
Factory reset
Flash the B386 zip file in TWRP.
You can get the B386 from here https://forum.xda-developers.com/showpost.php?p=69331930&postcount=1338
If your phone is on Android Nougat.
Then you have to use dload method.
Unzip the B386 zip file.
Put the update.app in the dload folder inside your external sdcard.
Go to your dialer
*#*#2846579#*#*
Select "software upgrade"
then Select - > SD card upgrade.
And then it will reboot and install the stock firmware.
This thread has all the Stock firmwares.
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727
Hope the above steps solve your problem. If not, then we will try something else. please answer all the questions to help you better especially your full build number (firmware version).
:good::good::good::good::good:

Thank you
I'm on emui 5,0 android 7,0 nugat ROM nrd90m test-keys - before I don't remember, upgrade ota for AL10 model. Maybe AL10C00B552.
So I have to try flash nugat ROM AL10 by TWRP 3.1.0.2.
Dload method dont work - I never need sd card for this.
Can I flash nugat rom dload method? And where I find stock recovery for nugat?

TWRP & Erecovery methods
bodzio3333 said:
Thank you
I'm on emui 5,0 android 7,0 nugat ROM nrd90m test-keys - before I don't remember, upgrade ota for AL10 model. Maybe AL10C00B552.
So I have to try flash nugat ROM AL10 by TWRP 3.1.0.2.
Dload method dont work - I never need sd card for this.
Can I flash nugat rom dload method? And where I find stock recovery for nugat?
Click to expand...
Click to collapse
Since you are on nougat with test keys, try to flash the latest nougat firmware on your phone model NXT-AL10 (Try flashing firmwares using TWRP )
Link for the firmware
link 1 https://mega.nz/#!Y4IVEbxY!7C8u3FP3V8eAV4jVNmbRUfj2W1nc8p5gMtaScVmzeA0
if the link 1 doesn't work then try link 2
link 2 https://mega.nz/#!U9ZkTZzI!fbPnyDIxCGGFkiGxtF3SMicLqmTDNTq8SG8fVw8lfz8
download & flash it using TWRP.
Once you finish flashing - you should have android nougat stock B584
Go to settings - > about you should see that B584. in build number.
If your build number is showing anything other than test-keys then you will be able to use dload method or Hisuite method using PC.
Now if IT IS showing B584, then you can dload to B386. then unlock bootloader -> TWRP using SRK tools - > Root - > and then debrand to L29C432. - > this is the road map for you. we will go through this only after you succeed in the above steps.
Try the below steps only if the above steps don't work
if you want to flash the nougat recovery
then unzip the zip file in link 1.
Use Huawei update extractor software HuaweiUpdateExtractor_0.9.9.3
and then extract the recovery.img from the update.app file.
now
switch on usb debugging in your settings.
switch off the phone
press & hold volume down and then connect to phone to laptop
put the extracted recovery.img file in the same folder as the SRK tools
open SRK tools
type 000 to enter command prompt
type fastboot flash recovery recovery.img
(please remember all these steps that use adb commands come with element of risk. so please proceed with caution and go slow. Proceed with these steps only if you know what you are doing otherwise do not proceed)
Try the TWRP steps first and see if that will resolve your issue before flashing any stock recovery. If your flashing through TWRP then it will install stock recovery & stock ROM.
Please share your progress.
:good::good:

Samavb said:
Since you are on nougat with test keys, try to flash the latest nougat firmware on your phone model NXT-AL10 (Try flashing firmwares using TWRP )
Link for the firmware
link 1 https://mega.nz/#!Y4IVEbxY!7C8u3FP3V8eAV4jVNmbRUfj2W1nc8p5gMtaScVmzeA0
if the link 1 doesn't work then try link 2
link 2 https://mega.nz/#!U9ZkTZzI!fbPnyDIxCGGFkiGxtF3SMicLqmTDNTq8SG8fVw8lfz8
download & flash it using TWRP.
Once you finish flashing - you should have android nougat stock B584
Click to expand...
Click to collapse
You must know that I'm very grateful for your help
Do I have to format data before start flashing B584.zip or do nothing?
Do I need update_data_full_all_cn.zip ?

2 Answers
bodzio3333 said:
You must know that I'm very grateful for your help
Do I have to format data before start flashing B584.zip or do nothing?
Do I need update_data_full_all_cn.zip ?
Click to expand...
Click to collapse
Glad to read Ur kind words but V have a long road ahead. So let's fix ur phone :good:
Answers
1) Yes, you can format DATA before flashing this zip file. you can also do factory reset before flashing the zip file. (Remember we are doing this step only to get ur phone out of that test keys & this firmware is not ur final firmware that u will use. )
2) I was searching for a firmware that u can flash on ur phone and I found B584 and felt this might help. The guys in the other thread mentioned it as full firmware. After u flash this firmware, check in settings - > about - > build number if it is anything else other than test keys then u succeeded in this step.
Goal of this flashing of B584 is only to get rid of that test keys in build number. Once that is gone then U can downgrade to B386 using steps in my previous posts followed by the road map.
:good::good::good:

Samavb said:
Glad to read Ur kind words but V have a long road ahead. So let's fix ur phone :good:
Answers
1) Yes, you can format DATA before flashing this zip file. you can also do factory reset before flashing the zip file. (Remember we are doing this step only to get ur phone out of that test keys & this firmware is not ur final firmware that u will use. )
2) I was searching for a firmware that u can flash on ur phone and I found B584 and felt this might help. The guys in the other thread mentioned it as full firmware. After u flash this firmware, check in settings - > about - > build number if it is anything else other than test keys then u succeeded in this step.
Goal of this flashing of B584 is only to get rid of that test keys in build number. Once that is gone then U can downgrade to B386 using steps in my previous posts followed by the road map.
:good::good::good:
Click to expand...
Click to collapse
When I flash B584.zip see this error in twrp:
Failed to mount '/cust' (invalid argument)
Failed to mount '/version' (invalid argument)
E:unknown command [errno]
E:unknown command [errno]
Update process ended with ERROR: 7
No good.....

[SOLVED] Need help to upgrade from L31-C900B151 to latest Nougat build

SOLVED: please check my 2nd post.
Hello guys,
I would like to upgrade my P9 Lite L31 from M to N official. I've tried the past few days but it always ends up with "NRD90M test-keys" on build number and missing apps. I have read A LOT of threads/posts about this issue, really everywhere, but I can't figure out how to update my device without problem.
Also I do know there are some Q&A threads/GUIDES/HOW-TOs in the forum but I don't find the right procedure for my case.
I assume it's because I've flashed the wrong package or forgot something in the procedure...
I've followed this GUIDE by @simo255: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
Here is my info:
P9 Lite VNS-L31
3 Gb RAM
Build: VNS-L31C900B151
EMUI 4.1.1
So, I'm on C900B151 and I'd like now to upgrade to C432B380 (or C432B381 ?) (or above if available).
If I understand well, the correct procedure is:
1- unroot (necessary?)
2- change from C900 to C432, by flashing an C432 OEMINFO.img through Meticulus TWRP (v4)
3- flash the latest Nougat update.zip package (B370/B371 or B380/B381) through Meticulus TWRP (v4)
4- flash the latest data full EU zip (B370/B371 or B380/B381)
5- reboot
Is it OK?
At steps 3 and 4, do I have to get UPDATE.app for B3xx and use the dload method instead?
FYI, I didn't follow step 2 when I tried, is it the culprit of my CUST errors in TWRP/"NRD90M test-keys"/missing apps problems? Or is it because I've flashed B370 instead of B371?
A few questions:
1- Is it a problem to currently run B151 firmware for my L31 for the Nougat upgrade process? I've read that the last digit means dual SIM or single SIM. I think I have a single SIM version but I'm not sure... How to know for sure? Sorry for the dumb question
2- If I don't follow the procedure above but if I relock my BL and then check for updates, do you think I will get a Nougat full OTA for C900 (C900B151 > C900B3xx)? Is it really necessary for me to change from C900 to C432?
3- In any cases, would it be possible to upgrade directly from B151 to B38x? Or do I have to go through B16x or B37x?
4- I can't figure out how to get the correct full OTA for Nougat, the one bigger than 1,9 Gb. I always get 1,25 Gb package through OTA update in settings, even when I'm running C432B160...
5- Is it possible to use Firmware Finder to update from B151 directly to B38x (or above)?
I already tried to flash a B370 update.zip and data full EU (from this GUIDE) but I have error about CUST in TWRP and as already said, then I get "NRD90M test-keys" on build number and missing apps after reboot.
After this, I successfully downgraded to C432B160 (maybe it would be better to downgrade to B161?) and I get the B370 OTA (1,25 Gb), but as you know it's not the FULL OTA... So AGAIN: "NRD90M test-keys" on build number and missing apps.
Sorry for the long post but I find really hard to flash/update stuff on this P9 Lite. I'm really confused. I was before on a Samsung S3 LTE and it was easier...
Any advices?
Thanks in advance.

I solved my problem!
My mistake was to install build VNS-L31C432B160 instead of VNS-L31C432B161, that's why OTA available was not the correct one (1,25 Gb instead of 1,99 Gb)
B160, B370, B380 are for dual SIM
B161, B371, B381 are for single SIM
I have a P9 Lite L31 SINGLE SIM
I was on previously on build VNS-L31C900B151 and I'm now running build VNS-L31C432B381 official and everything is working well.
The steps:
1- Download Update.zip of VNS-L31C432B161 (size around 1.6+ GB) (I've found it and downloaded it with Firmware Finder)
2- Extract the UPDATE.APP of the ZIP with 7-zip or similar and copy it on External SDCARD in a dload folder
2- Make sure to be rooted (Bootloader unlocked, TWRP v4 by Meticulus installed and SuperSU flashed)
3- Flash OEMinfo.img and custom.bin for C432 Single SIM (download link: https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873, from this thread: https://drive.google.com/drive/folders/0B3CRCPqinridRXNPdDNuM2g5dTA) with Toolkit (download link: https://forum.xda-developers.com/devdb/project/?id=16538#downloads from this thread: https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873)
4- Reboot > It asks for decryption key (I entered a wrong one because I didn't even know the code) > it fails to decrypt and then ask for factory reset
5- Factory reset fails (I don't know why)
6- Reboot on Android > build is now VNS-L31C432B151 (it changed from C900 to C432 thanks to the OEMinfo.img and custom.bin)
7- Shutdown the phone
8- Start the phone with 3 buttons method: vol- ; vol+ ; power
9- Wait a few minutes L31C432B161 to be installed > It reboots and you're now running L31C432B161
10- Search for OTA in ROM settings > You will get L31C432B371 > Download and apply the update
11- Wait a few minutes L31C432B371 to be installed > It reboots and you're now running L31C432B371
12- Search for OTA in ROM settings > You will get L31C432B381 > Download and apply the update
13- Wait a few minutes L31C432B381 to be installed > It reboots and you're now running L31C432B381
14- Done!

So i have the same problem.
I've the L21 Dual sim model (2GB) and i tried to update.
Messed up with firmware finder and ended up with a wrong update. I've managed to get back to L21C432B160.
What version do I pick with Firmware finder? Or do i need to flash another OEMinfo.img en custom.bin first to get an update?
I don't want to end up with beta firmware or something messed up so I keep getting future updates. I don't understand why the OTA update is still here on my p9.

michaeldepotter said:
So i have the same problem.
I've the L21 Dual sim model (2GB) and i tried to update.
Messed up with firmware finder and ended up with a wrong update. I've managed to get back to L21C432B160.
What version do I pick with Firmware finder? Or do i need to flash another OEMinfo.img en custom.bin first to get an update?
I don't want to end up with beta firmware or something messed up so I keep getting future updates. I don't understand why the OTA update is still here on my p9.
Click to expand...
Click to collapse
Which oeminfo.img and custom.bin did you flash lately? Is it your own files or from someone else?
And you say you are currently running L21C432B160 but which OTA version is showing up now in ROM settings? Which size?
Sent from my P9 lite using XDA Labs

Haven’t flash any of these files yet. I dont have an ota in upater right now. That is The probleem. Only with the firmware Finder i can get updates but i dont know which i should pick

michaeldepotter said:
Haven’t flash any of these files yet. I dont have an ota in upater right now. That is The probleem. Only with the firmware Finder i can get updates but i dont know which i should pick
Click to expand...
Click to collapse
If you want to get OTA updates, you need to have your bootloader locked. Is your bootloader currently unlocked?
Sent from my P9 lite using XDA Labs

Yes. But the problem also occured when it was locked.

Update for Huawei P9 Lite 2016 Dual Sim (VNS-L31C900B114 to VNS-L31C432B160 firmware)
Wood Man said:
I solved my problem!
My mistake was to install build VNS-L31C432B160 instead of VNS-L31C432B161, that's why OTA available was not the correct one (1,25 Gb instead of 1,99 Gb)
B160, B370, B380 are for dual SIM
B161, B371, B381 are for single SIM
I have a P9 Lite L31 SINGLE SIM
I was on previously on build VNS-L31C900B151 and I'm now running build VNS-L31C432B381 official and everything is working well.
The steps:
1- Download Update.zip of VNS-L31C432B161 (size around 1.6+ GB) (I've found it and downloaded it with Firmware Finder)
2- Extract the UPDATE.APP of the ZIP with 7-zip or similar and copy it on External SDCARD in a dload folder
2- Make sure to be rooted (Bootloader unlocked, TWRP v4 by Meticulus installed and SuperSU flashed)
3- Flash OEMinfo.img and custom.bin for C432 Single SIM (download link: https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873, from this thread: https://drive.google.com/drive/folders/0B3CRCPqinridRXNPdDNuM2g5dTA) with Toolkit (download link: https://forum.xda-developers.com/devdb/project/?id=16538#downloads from this thread: https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873)
4- Reboot > It asks for decryption key (I entered a wrong one because I didn't even know the code) > it fails to decrypt and then ask for factory reset
5- Factory reset fails (I don't know why)
6- Reboot on Android > build is now VNS-L31C432B151 (it changed from C900 to C432 thanks to the OEMinfo.img and custom.bin)
7- Shutdown the phone
8- Start the phone with 3 buttons method: vol- ; vol+ ; power
9- Wait a few minutes L31C432B161 to be installed > It reboots and you're now running L31C432B161
10- Search for OTA in ROM settings > You will get L31C432B371 > Download and apply the update
11- Wait a few minutes L31C432B371 to be installed > It reboots and you're now running L31C432B371
12- Search for OTA in ROM settings > You will get L31C432B381 > Download and apply the update
13- Wait a few minutes L31C432B381 to be installed > It reboots and you're now running L31C432B381
14- Done!
Click to expand...
Click to collapse
Greetings ...
What do you mean " Search for OTA in ROM settings > You will get L31C432B371 > Download and apply the update " ?
Regards...

george_1234 said:
Greetings ...
What do you mean " Search for OTA in ROM settings > You will get L31C432B371 > Download and apply the update " ?
Regards...
Click to expand...
Click to collapse
I meant once you run full working Android 6, you have to go in Android settings, in a menu called something like "system updates" or similar and you should see if a newer Android version is available, meaning Android 7.
I'm running Android 7.0, so I can't show you screenshots from Android 6,sorry... Here are 2 screenshots from EMUI 5.0 (Android 7) in case it could help.

[SOLVED] NRD90M test-keys - Nougat Stock Firmware Huawei Mate 8

Hi all,
I just want to share with you all how i solved NRD90M test-keys on my Mate 8. 2 weeks ago, I've successful to debrand from L29 to AL10 and updated to Oreo EMUI 8. After awhile, i found bugs or error when i connected to PC or Laptop, my phone will go haywire like someone is touching the screen everywhere. I suspected it might be came from cust.img that i flashed to make sim and data detect.
Then i made a decision to debrand again to DL00, and successfully rollback to MM B386 using Hisuite version 8. After that i flashed dualcu_cn.zip using TWRP and successful to debrand to DL00. I checked the OTA update, there is DL00C00B577 Nougat update and i download and installed it. My Mate 8 became NRD90M test-keys after successfully updated to Nougat. For one and a half day i searched in internet and XDA on how to get rid of NRD90M test-keys and update to next build of Nougat. On XDA, I've found several thread regarding NRD90M test-keys like https://forum.xda-developers.com/mate-8/general/info-rom-nrd90m-test-keys-android-7-0-t3750147, https://forum.xda-developers.com/mate-8/help/nrd90m-test-keys-t3549124 and https://forum.xda-developers.com/mate-8/help/stuck-nrd90m-test-keys-t3590461 but without proper steps and procedures. So people like me a noob or newbies will stuck on how to solve the problem. So I've do some test for my Mate 8 by using one of this methods which are HuRUpdater, HWOTA and erecovery. I can said that 90% of chances rate it will success but you'll need to download FullOTA-MF stock firmware. I'm using erecovery so no need to download it.
Requirement:
1. Unlocked bootloader
2. TWRP Installed
3. HuRUpdater - Link : https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
4. HWOTA - Link: https://cloud.mail.ru/public/DEWc/a9fDVbgpz
5. update.zip - FullOTA-MF (for me NXT-DL00C17B592-full in erecovery)
6. update_all_hw.zip
7. update_data_public.zip
8. Back up your data using HiSuite or SD card.
Instruction
Method 1 using HuRUpdater
1. Make sure your bootloader is unlocked and TWRP is installed.
2. Download HuRUpdater.zip, update.zip-FullOTA-MF (your stock firmware), update_all_hw.zip and update_data_public.zip.
3. Make a new folder in SD Card root (you can name it base on its firmware) and put all the zips that you already downloaded in the folder.
4. Boot your Mate 8 to TWRP and choose sd card > folder > HuRUpdater.zip. It'll reboot into recovery and start flash firmware.
5. Your phone will update to the newest build number base on your stock firmware.
6. You can follow the steps in this link https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Method 2 using HWOTA
1. Make sure your bootloader is unlocked and TWRP is installed.
2. Download HWOTA.zip, update.zip-FullOTA-MF (your stock firmware), update_all_hw.zip and update_data_public.zip.
3. Extract HWOTA.zip into HWOTA folder in your PC and put all the zips that you already downloaded in that folder. Copy HWOTA folder in your SD Card.
4. Boot your Mate 8 to TWRP and choose HWOTA folder and select nxt_hwota_update.zip. It'll reboot into recovery and start flash firmware.
5. Your phone will update to the newest build number base on your stock firmware.
6. You can follow the steps in this link https://forum.xda-developers.com/mat...ate-8-t3785320. This HWOTA.zip also can use to flash OREO EMUI 8 firmware.
P/S: I think HuRUpdater and HWOTA is the same method but using different script binary.
Method 3 using eRecovery
1. Press Vol + and Power button at the same time for 3-5 sec.
2. Choose your WIFI (need strong connection), if not it will failed to download recovery firmware.
3. If your WIFI have a strong connection it'll start to download recovery firmware and install.
4. Wait until finish installation
5. Your phone will update to the newest build number base on your stock firmware.
P/S: If you're using C636,C432,C185, i think it's useless. because i'm from C636 it's never captured the recovery firmware. so in case if your phone bricked or test keys, you can use HuRUpdater method. This method only working on chinese variants is what i think.
Additional info:
DESCRIPTION FOR FIRMWARE
1- OTA Firmware: (Over The Air) That mean the update file can install on the available os and upgrade or fix some bugs. (if the update build number is compatible with your phone).
2- FullOTA: Full OTA firmware is Full package of firmware and it can unbrick your phone.
3- FullOTA-MF: Full OTA MF firmware is Full package of firmware and it can unbrick your phone model with any buid number.
4- FullOTA-PV: Full OTA PV firmware is a Point-Version firmware, which means it can unbrick your phone depend on build number.
5- OTA-PV: Point-Version, such firmware are designed to update from one version of android to another. (build number is important)
6- OTA-MF: MF is a multi-file firmware, which means that there are several update packages in it.
Source : http://huawei-firmware.com/pages/ext/a/description/index.html
All thanks goes to @zxz0O0 for HurUpdater.zip, @apat26 for his thread HWOTA, 4pda forum and Huawei community.

ceriqdesign said:
Hi all,
I just want to share with you all how i solved NRD90M test-keys on my Mate 8. 2 weeks ago, I've successful to debrand from L29 to AL10 and updated to Oreo EMUI 8. After awhile, i found bugs or error when i connected to PC or Laptop, my phone will go haywire like someone is touching the screen everywhere. I suspected it might be came from cust.img that i flashed to make sim and data detect.
Then i made a decision to debrand again to DL00, and successfully rollback to MM B386 using Hisuite version 8. After that i flashed dualcu_cn.zip using TWRP and successful to debrand to DL00. I checked the OTA update, there is DL00C00B577 Nougat update and i download and installed it. My Mate 8 became NRD90M test-keys after successfully updated to Nougat. For one and a half day i searched in internet and XDA on how to get rid of NRD90M test-keys and update to next build of Nougat. On XDA, I've found several thread regarding NRD90M test-keys like https://forum.xda-developers.com/mate-8/general/info-rom-nrd90m-test-keys-android-7-0-t3750147, https://forum.xda-developers.com/mate-8/help/nrd90m-test-keys-t3549124 and https://forum.xda-developers.com/mate-8/help/stuck-nrd90m-test-keys-t3590461 but without proper steps and procedures. So people like me a noob or newbies will stuck on how to solve the problem. So I've do some test for my Mate 8 by using one of this methods which are HuRUpdater, HWOTA and erecovery. I can said that 90% of chances rate it will success but you'll need to download FullOTA-MF stock firmware. I'm using erecovery so no need to download it.
Requirement:
1. Unlocked bootloader
2. TWRP Installed
3. HuRUpdater - Link : https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
4. HWOTA - Link: https://cloud.mail.ru/public/DEWc/a9fDVbgpz
5. update.zip - FullOTA-MF (for me NXT-DL00C17B592-full in erecovery)
6. update_all_hw.zip
7. update_data_public.zip
8. Back up your data using HiSuite or SD card.
Instruction
Method 1 using HuRUpdater
1. Make sure your bootloader is unlocked and TWRP is installed.
2. Download HuRUpdater.zip, update.zip-FullOTA-MF (your stock firmware), update_all_hw.zip and update_data_public.zip.
3. Make a new folder in SD Card root (you can name it base on its firmware) and put all the zips that you already downloaded in the folder.
4. Boot your Mate 8 to TWRP and choose sd card > folder > HuRUpdater.zip. It'll reboot into recovery and start flash firmware.
5. Your phone will update to the newest build number base on your stock firmware.
6. You can follow the steps in this link https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Method 2 using HWOTA
1. Make sure your bootloader is unlocked and TWRP is installed.
2. Download HWOTA.zip, update.zip-FullOTA-MF (your stock firmware), update_all_hw.zip and update_data_public.zip.
3. Extract HWOTA.zip into HWOTA folder in your PC and put all the zips that you already downloaded in that folder. Copy HWOTA folder in your SD Card.
4. Boot your Mate 8 to TWRP and choose HWOTA folder and select nxt_hwota_update.zip. It'll reboot into recovery and start flash firmware.
5. Your phone will update to the newest build number base on your stock firmware.
6. You can follow the steps in this link https://forum.xda-developers.com/mat...ate-8-t3785320. This HWOTA.zip also can use to flash OREO EMUI 8 firmware.
P/S: I think HuRUpdater and HWOTA is the same method but using different script binary.
Method 2 using eRecovery
1. Press Vol + and Power button at the same time for 3-5 sec.
2. Choose your WIFI (need strong connection), if not it will failed to download recovery firmware.
3. If your WIFI have a strong connection it'll start to download recovery firmware and install.
4. Wait until finish installation
5. Your phone will update to the newest build number base on your stock firmware.
P/S: If you're using C636,C432,C185, i think it's useless. because i'm from C636 it's never captured the recovery firmware. so in case if your phone bricked or test keys, you can use HuRUpdater method. This method only working on chinese variants is what i think.
Additional info:
DESCRIPTION FOR FIRMWARE
1- OTA Firmware: (Over The Air) That mean the update file can install on the available os and upgrade or fix some bugs. (if the update build number is compatible with your phone).
2- FullOTA: Full OTA firmware is Full package of firmware and it can unbrick your phone.
3- FullOTA-MF: Full OTA MF firmware is Full package of firmware and it can unbrick your phone model with any buid number.
4- FullOTA-PV: Full OTA PV firmware is a Point-Version firmware, which means it can unbrick your phone depend on build number.
5- OTA-PV: Point-Version, such firmware are designed to update from one version of android to another. (build number is important)
6- OTA-MF: MF is a multi-file firmware, which means that there are several update packages in it.
Source : http://huawei-firmware.com/pages/ext/a/description/index.html
All thanks goes to @zxz0O0 for HurUpdater.zip, @apat26 for his thread HWOTA, 4pda forum and Huawei community.
Click to expand...
Click to collapse
hello, in the meantime I thank you my mate8 is much improved the only problem is that I am still in NRD90M test-keys.

manuele16 said:
hello, in the meantime I thank you my mate8 is much improved the only problem is that I am still in NRD90M test-keys.
Click to expand...
Click to collapse
are you using HuRUpdater method?can you give me more info about your mate 8

ceriqdesign said:
are you using HuRUpdater method?can you give me more info about your mate 8
Click to expand...
Click to collapse
Of course...
Model number: NXT
No. Series: NRD90M Test Keys
Emui: 5.0
Android: 7.0
Vendor: hw
Country: meafnaf
please consider that my goal is to make it NXT-L29C432.
Originally on the box is reported NXT-AL10

manuele16 said:
Of course...
Model number: NXT
No. Series: NRD90M Test Keys
Emui: 5.0
Android: 7.0
Vendor: hw
Country: meafnaf
please consider that my goal is to make it NXT-L29C432.
Originally on the box is reported NXT-AL10
Click to expand...
Click to collapse
So originally you came from NXT-AL10 and without changing oeminfo with SRK Tool then you used the HuRUpdater?
Is it your bootloader still unlocked or locked?

I did not change oeminfo, or rather I tried with SRK tool, but I did not succeed.
Yes, I used HuRUpdater.
Bootloader unlocked

manuele16 said:
I did not change oeminfo, or rather I tried with SRK tool, but I did not succeed.
Yes, I used HuRUpdater.
Bootloader unlocked
Click to expand...
Click to collapse
I managed to get Vendor: hw and Country: eu.
but I'm still in nrd90

manuele16 said:
I did not change oeminfo, or rather I tried with SRK tool, but I did not succeed.
Yes, I used HuRUpdater.
Bootloader unlocked
Click to expand...
Click to collapse
Yup no wonder you're on NRD90M..you need to change oeminfo first before flash c432 firmware..

TWRP Huawei mate 8
Hello, my people, how are you?
I have a doubt, the truth is I am very new in this.
I have a Huawei Mate 8 NXT-L29 which updates to Android 7 with an app called "Firmware Finder for Huawei" and then I started my problems, the clock does not work, I can not enter the updater among others. What I would like is to change that rom for another or if it were for a stock.
I have the bootloader open and a TWRP (twrp-3.2.3-0-next) which is the only one that has worked for me but I have not been able to install another rom it tells me this: "error when dismounting" / '/ cust /' (invalid argument) and I do not know what I'm doing wrong ...
the compilation that this app left me is: NRD90M test-keys
and the rom that I want to install is: NXTL26C605B580
I would like to know your recommendations and corrections to what I am doing and thank you and I apologize for my English, which is very bad!

riky26 said:
Hello, my people, how are you?
I have a doubt, the truth is I am very new in this.
I have a Huawei Mate 8 NXT-L29 which updates to Android 7 with an app called "Firmware Finder for Huawei" and then I started my problems, the clock does not work, I can not enter the updater among others. What I would like is to change that rom for another or if it were for a stock.
I have the bootloader open and a TWRP (twrp-3.2.3-0-next) which is the only one that has worked for me but I have not been able to install another rom it tells me this: "error when dismounting" / '/ cust /' (invalid argument) and I do not know what I'm doing wrong ...
the compilation that this app left me is: NRD90M test-keys
and the rom that I want to install is: NXTL26C605B580
I would like to know your recommendations and corrections to what I am doing and thank you and I apologize for my English, which is very bad!
Click to expand...
Click to collapse
Sorry for late reply as for now i'm quite busy with life..can you tell me what your model before you change to NXTL26C605B580?