IMEI Numbers lost - P8lite Q&A, Help & Troubleshooting

I flashed my ALE-L21 to beta 6.0 from 5.0.1 B170 and couple days later flashed b170 back. I have no IMEI number now. (Imei1=null imei2=null) Pls help

You must downgrade to B052 then update OTA B170. IMEI will be back

I have the same problem:
I had chinesee android 6.0
- changed region to hw/eu
- flashed to b052 - imei - gone
- flash to b136 - lack of imei
- flash to b170 - lack of imei
- tried to update to full b170 - update failed by local update and force update
- tried to flash to b046 - lack of imei
- tried to local and force update to full b046 - still nothing
STILL NOTHING ;(;(

dzamej said:
I have the same problem:
I had chinesee android 6.0
- changed region to hw/eu
- flashed to b052 - imei - gone
- flash to b136 - lack of imei
- flash to b170 - lack of imei
- tried to update to full b170 - update failed by local update and force update
- tried to flash to b046 - lack of imei
- tried to local and force update to full b046 - still nothing
STILL NOTHING ;(;(
Click to expand...
Click to collapse
My last post for this issue! When read careless and do not understand their guilt only yours
Flash with fastboot B052(IMEI gone)
Make a wipe then update via OTA
IMEI will be restored!

Is there any method to back up imei on our p8 lite? I was wondering, if i can flash to 6.0 again, but u don't want to do this things again if i lost imei again... I saw xposed module to write imei and coule tools for ****ty mediatek cpus but xposed is not working on our p8 lite and we have kirin chipset so...

sokkoban said:
my last post for this issue! When read careless and do not understand their guilt only yours
flash with fastboot b052(imei gone)
make a wipe then update via ota
imei will be restored!
Click to expand...
Click to collapse
i have made wipe after each flashing - still lack of imei!
Cant update via ota - there is information - update failed
dude cant you read?!?!

can't find the b52 firmware. Does someone have a link forme/us?
@edit: Links can be found here -> http://forum.xda-developers.com/p8lite/general/huawei-p8-lite-android-6-0-marshmallow-t3309796
snitch

sokkoban said:
You must downgrade to B052 then update OTA B170. IMEI will be back
Click to expand...
Click to collapse
Is this just the modem image, or the whole system.
Currently having the same problem in the exact same situation (upgrading to Marshmallow, then downgrading to B170 directly); will try your fix when I get home .
I guess that's why there's huge notices on the B170 downloads that 'your device must be on at least B052 first'...
---------- Post added at 04:45 PM ---------- Previous post was at 04:36 PM ----------
dzamej said:
i have made wipe after each flashing - still lack of imei!
Cant update via ota - there is information - update failed
dude cant you read?!?!
Click to expand...
Click to collapse
Probably means that you need to do a complete internal system wipe via TWRP (which is recommended).
OTA validates using the IMEI, which it can't do the ROM needs the B052 baseband (which isn't present).
Seems that upgrading directly to Marshmallow also fixes the issue:
Download B170 (and install it, via Fastboot [you need the Huawei Update Extractor Tool to extract the system images from UPDATE.APP])
Download Marshmallow & transfer to SD
Flash the STOCK recovery via Fastboot
Install Marshmallow via the standard local update method via the OTA updater
Once Marshmallow is installed, re-install TWRP via Fastboot
I plan to upload the raw system imgs of the updates to my blog later (will probably post links here tomorrow), if you don't fancy using the HUET yourself.

Thanx. This way it worked. OTA update got IMEI back

StarZ123 said:
Thanx. This way it worked. OTA update got IMEI back
Click to expand...
Click to collapse
Please can you describe exactly what you did? I've got the same problem of IMEI lost and can't find a solution.

Related

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?

Software update: v20k

Hi all!
Yesterday I received a software update for my H850 (made for Italy market): v20k
Official changelog says that it includes google security patch (as of 1-aug-2017).
The size of the update is approximately 104 Mb.
Have anybody also received this update? How's your experience? What other improvements have you noticed?
Update.
I also received update in Croatia.
Lucky people... Unfortunately, the versions sold for Israel market do not offer update after version 20c. I bought my device in Romania from a reputable store but it is made for Israel, world zone IL, and no updates... Is there any way to turn it into european version, to receive firmware updates for EUR-XX and not have error messages at restart regarding wrong locale?
Thank you.
We already have it on TMO few weeks ago.
ruh01 said:
Lucky people... Unfortunately, the versions sold for Israel market do not offer update after version 20c. I bought my device in Romania from a reputable store but it is made for Israel, world zone IL, and no updates... Is there any way to turn it into european version, to receive firmware updates for EUR-XX and not have error messages at restart regarding wrong locale?
Thank you.
Click to expand...
Click to collapse
I suppose you bought the phone from QuickMobile (like me) if you have the Israelian version. And no, you cannot bypass that error message without root (which is not available on this version of H850).
Btw, do you have VoLTE?
From Pcgarage. I understand that people buying from Evomag some 2-3 month ago got the same variant. How should I check for VoLTE?
ruh01 said:
From Pcgarage. I understand that people buying from Evomag some 2-3 month ago got the same variant. How should I check for VoLTE?
Click to expand...
Click to collapse
From what I have read, there should be an option in the Call sub-menu in Settings. I don't have this option.
to get this update onto stock rooted devices:
1.) backup data with TWRP
2.) download firmware update
3.) flash fw 20i with LGUP
3.) reboot phone to be able to install the 20k update (this is possible because all data are not erased!)
4.) install update
5.) reboot into fastboot mode and install TWRP
6.) reboot into TWRP and install no-verify-opt-encrypt.zip
7.) reboot into TWRP and install Magisk 14
8.) format data
9.) reboot into TWRP and restore data
10.) reboot phone and freeze all unnecessary apps
that’s it!
i followed this way and now i am on 20k rooted with Magisk 14
I'm on V20i-EUR-XX and i don't receive it
Ysfzone said:
I'm on V20i-EUR-XX and i don't receive it
Click to expand...
Click to collapse
yes, but you are not living in the EU as i have seen. I am not sure, that this update will be available all over the world.
But 20k is available for H850 there -> https://lg-firmwares.com/lg-h850-firmwares/#firmwaresList!
Search for Eu 20k! You can flash it with LGUP by yourself.
20k is the July security patch on TMO-US
On LG BRIDGE i have this Error
Any Solution !? :crying:
---------- Post added at 06:40 PM ---------- Previous post was at 06:35 PM ----------
non-toxic said:
yes, but you are not living in the EU as i have seen. I am not sure, that this update will be available all over the world.
But 20k is available for H850 there -> https://lg-firmwares.com/lg-h850-firmwares/#firmwaresList!
Search for Eu 20k! You can flash it with LGUP by yourself.
Click to expand...
Click to collapse
i will lose all data with LGUP ??
because i have a previous experience with LGUP i got after upgrade from (v10) to (v20D) screen tell me "Reset Phone" !
1.) as i wrote, it seems, that the update is not available for Morocco.:crying:
Ysfzone said:
i will lose all data with LGUP ??
Click to expand...
Click to collapse
2.) if you have installed TWRP recovery, you will lose!
( in this case, you can follow my description)
if unrooted and without TWRP you will only update your phone without loosing your data!
to use LGup, you need the tool "uppercut" too!!! Otherwise LGup can’t connect to your phone!
non-toxic said:
if you have installed TWRP recovery, you will lose!
if unrooted and without TWRP you will only update your phone without loosing your data!
to use LGup, you need the tool "uppercut" too!!! Otherwise LGup can’t connect to your phone!
Click to expand...
Click to collapse
I'm on stock.. No TWRP No Root..
LGUP Work with me WITHOUT uppercut..
then go on now!
Good Luck!
non-toxic said:
than go on now!
Good Luck!
Click to expand...
Click to collapse
Thank You !
BTW: normally you cannot destroy something. If update fails, you can flash full fw 20i or k with LGup again!
and don’t forget to press the "thanks" button if suggestion was helpful to you
non-toxic said:
2.) if you have installed TWRP recovery, you will lose!
( in this case, you can follow my description)
if unrooted and without TWRP you will only update your phone without loosing your data!
Click to expand...
Click to collapse
I didn't quite understand your guide, I think.
If I have TWRP and root on a v10 software version, then I should just backup via TWRP, flash v20i via lgup, then do the Ota update to v20k, then reinstall TWRP etc. and lastly I can just restore my data via TWRP?
What do you mean here:
"3.) reboot phone to be able to install the 20k update (this is possible because all data are not erased!)"
Did you mean to say this is possible because all data is now erased?
Thx in advance and kind regards
Toztil said:
I didn't quite understand your guide, I think.
If I have TWRP and root on a v10 software version, then I should just backup via TWRP, flash v20i via lgup, then do the Ota update to v20k, then reinstall TWRP etc. and lastly I can just restore my data via TWRP?
Click to expand...
Click to collapse
i think yes, it should go. But you should clean cache and dalvik too.
( i tried this way only between 20i -> k, but the data storage should have only custom installed app’s and data inside.
But think about, if you have done any changes to 10i system, you will lose them because system will be fully changed after this procedure.)
Toztil said:
What do you mean here:
"3.) reboot phone to be able to install the 20k update (this is possible because all data are not erased!)"
Did you mean to say this is possible because all data is now erased?
Click to expand...
Click to collapse
No!
In the case you have downloaded the update file using the update option in setup at first, you will be now able to continue updating from i to k without new connection to the net or cloud because the update file persists in memory.
(sorry, my English seems to be not good enough to describe this procedure perfectly!)
-> See 1. &2. of my signature!
h85020n
New version available on lg-firmwares, h85020n

[SOLVED] Fastboot Flash failes after firmware update

Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
EDIT: The solutionwas to re-unlock the bootloader (just perform "fastboot oem unlock PERSONAL UNLOCK KEY). Thanks to AndreaEl for suggesting the solution.
i have had the same problem some days ago.
Re unlock bootloader and try again
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
opal06 said:
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
Click to expand...
Click to collapse
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
opal06 said:
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
Click to expand...
Click to collapse
Have u tried using the method on this thread?
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
AndreaEl said:
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Tried that, it doesn't work. And I'm at B381 by the way. See when I try to send the firmware update to the updater app and install it, nothing changes. The installation completes and after reboot, when I check from about phone I see that I'm still in B381(at least according to it )
---------- Post added at 12:39 AM ---------- Previous post was at 12:32 AM ----------
opal06 said:
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
Click to expand...
Click to collapse
My boatloader is already locked and I'm not rooted.
Click to expand...
Click to collapse

P9 lite No audio After TWRP restore Dload failing HELP

[SOLVED] Hi i was on l-31c432b381 firmware with emui 5.0 and android 7.0, i have unlocked the bootloader for install magisk 12.0 and have root permissions, after months i saw an update for my phone (b389) so i tried to upgrade but i had twrp so error 1 or 7, i flashed the stock recovery, redowload the update and the install failed at 5%, so i tried to unistall magisk before update, but nothing it wont update, after few tries the upgrader says that the update now is not 300mb but is full and is 2gigs, so i think is the time.. but no. so i tried to force the update with 3 buttons recovery dload method but it doesn't work at all 5% at every try. so i searched for support and i found that the ota connot be installed on unlocked devices, so i tried to relock my bootloader with oem relock and the unlock number but it says root type is risk... so i can't even relock my bootloader.. other says that i have to install to relock or can relock... but is b381 the stock? or they instend the mm version? i don't remember what version p9 lite ships. i tried to flash imgs through fastboot but even if i flash system and boot of the b389 the system boot and the info are of the b381, unisatlling app system crash, so i restored my previous backup made through twrp recovery, i immidiatly noticed that the huawei boot animations was gone and was an android stock animation. i thinked it was fine and all was working properly, i give up o upgrade and i was fine but sad. after few hours i tried to make a paper copy with my printer that have nfc but my phone keep shows and hide nfc symbol like on off on off on off over and over even after reboot, after a call i understand that the audio doesn't was working, every type of audio not work even the mic. i don't see any other problems but without sounds is unusable as a phone or mulimedia things... sorry for bad english please HELP i tried all i founded ...
Franseven said:
Hi i was on l-31c432b381 firmware with emui 5.0 and android 7.0, i have unlocked the bootloader for install magisk 12.0 and have root permissions, after months i saw an update for my phone (b389) so i tried to upgrade but i had twrp so error 1 or 7, i flashed the stock recovery, redowload the update and the install failed at 5%, so i tried to unistall magisk before update, but nothing it wont update, after few tries the upgrader says that the update now is not 300mb but is full and is 2gigs, so i think is the time.. but no. so i tried to force the update with 3 buttons recovery dload method but it doesn't work at all 5% at every try. so i searched for support and i found that the ota connot be installed on unlocked devices, so i tried to relock my bootloader with oem relock and the unlock number but it says root type is risk... so i can't even relock my bootloader.. other says that i have to install to relock or can relock... but is b381 the stock? or they instend the mm version? i don't remember what version p9 lite ships. i tried to flash imgs through fastboot but even if i flash system and boot of the b389 the system boot and the info are of the b381, unisatlling app system crash, so i restored my previous backup made through twrp recovery, i immidiatly noticed that the huawei boot animations was gone and was an android stock animation. i thinked it was fine and all was working properly, i give up o upgrade and i was fine but sad. after few hours i tried to make a paper copy with my printer that have nfc but my phone keep shows and hide nfc symbol like on off on off on off over and over even after reboot, after a call i understand that the audio doesn't was working, every type of audio not work even the mic. i don't see any other problems but without sounds is unusable as a phone or mulimedia things... sorry for bad english please HELP i tried all i founded ...
Click to expand...
Click to collapse
Hi, my english is bad too , B389 is an OTA update, its impossible upgrade via fstboot or via TWRP (error 7). IMO the right way to fix your problems - downgrade to MM , then back to Nougat etc. (remove pattern Lock , Fingerprint lock, root etc. before installing downgrade). It will erase all your phone data!!!
Download official rollback package for your VNS-L31C432
http://download-c1.huawei.com/download/downloadCenter?downloadId=93789&version=373429&siteCode=sk
and download MM firmware VNS-L31C432B161 (Single SIM)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66022/f1/full/update.zip
1) Create a new folder dload in root directory of SD card (root directory : it means dont put it in any folder .) Now unpack the rollback package and copy its contents “UPDATE.APP” to the “dload” folder. Use the 3 button combo installation. After your firmware version should now be on “B300” or "test-keys".
2) Remove from dload folder rollback package, extract the ZIP file with MM firmware to the dload folder and use 3 combo button installation.
Or you can use this method : on your phone launch the phone dialer app and dial *#*#2846579#*#*. Next, select Project Menu – > Software upgrade – > SDcard upgrade – > and confirm the flashing process that is about to be initiated.
Good luck!
bozka1 said:
Hi, my english is bad too , B389 is an OTA update, its impossible upgrade via fstboot or via TWRP (error 7). IMO the right way to fix your problems - downgrade to MM , then back to Nougat etc. (remove pattern Lock , Fingerprint lock, root etc. before installing downgrade). It will erase all your phone data!!!
Download official rollback package for your VNS-L31C432
http://download-c1.huawei.com/download/downloadCenter?downloadId=93789&version=373429&siteCode=sk
and download MM firmware VNS-L31C432B161 (Single SIM)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66022/f1/full/update.zip
1) Create a new folder dload in root directory of SD card (root directory : it means dont put it in any folder .) Now unpack the rollback package and copy its contents “UPDATE.APP” to the “dload” folder. Use the 3 button combo installation. After your firmware version should now be on “B300” or "test-keys".
2) Remove from dload folder rollback package, extract the ZIP file with MM firmware to the dload folder and use 3 combo button installation.
Or you can use this method : on your phone launch the phone dialer app and dial *#*#2846579#*#*. Next, select Project Menu – > Software upgrade – > SDcard upgrade – > and confirm the flashing process that is about to be initiated.
Good luck!
Click to expand...
Click to collapse
Ok i'm posting in real time now. i'm copy update.app in dload folder (rollback)
it have completed ... wow
same android boot animation, the version says is nrd90m test keys (still no audio)
now i'm copying full mm firmware
its installing 40% i'm loving you.. 50% 60% 70%80%90% SUCCESS
user reset... OK
huawei boot animation with audio!!!!!!!!!!!!!!! and there is not unlocked text like (......can't be trusted...)
ok wifi connected skip.skip skip.... start
song... AUDIO WORKING
recording, its working, nfc ok
i'm on b161 and it shows update, now, can i update to the latest version?
THANK YOU SO MUCH
Franseven said:
Ok i'm posting in real time now. i'm copy update.app in dload folder (rollback)
it have completed ... wow
same android boot animation, the version says is nrd90m test keys (still no audio)
now i'm copying full mm firmware
its installing 40% i'm loving you.. 50% 60% 70%80%90% SUCCESS
user reset... OK
huawei boot animation with audio!!!!!!!!!!!!!!! and there is not unlocked text like (......can't be trusted...)
ok wifi connected skip.skip skip.... start
song... AUDIO WORKING
recording, its working, nfc ok
i'm on b161 and it shows update, now, can i update to the latest version?
THANK YOU SO MUCH
Click to expand...
Click to collapse
Yes, you can. Via OTA, or you can use TWRP (Meticulus 3.0.2.0 only ! ) and flash both .zip files. You must download two files:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v80474/f1/full/update.zip
and
http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_VNS-L11_hw_eu.zip.
In TWRP set Install, then select memmory SD card, and klick on
update.zip, confirm installation. After, STAY in TWRP, go back to Install, find file ...hw_eu....zip , confirm installation. Then select rebot system. Done!
bozka1 said:
Yes, you can. Via OTA, or you can use TWRP (Meticulus 3.0.2.0 only ! ) and flash both .zip files. You must download two files:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v80474/f1/full/update.zip
and
http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_VNS-L11_hw_eu.zip.
In TWRP set Install, then select memmory SD card, and klick on
update.zip, confirm installation. After, STAY in TWRP, go back to Install, find file ...hw_eu....zip , confirm installation. Then select rebot system. Done!
Click to expand...
Click to collapse
i've done b371 thrugh updater now it doesn't show newer versions but i'm using b389 dload and it should go ok right? (full b389 update.app)
Franseven said:
i've done b371 thrugh updater now it doesn't show newer versions but i'm using b389 dload and it should go ok right? (full b389 update.app)
Click to expand...
Click to collapse
Try it, but I think, you will get a message "not compatible" . Via dload its impossible, IMO use rather Huawei firmware finder or wait for OTA update.
bozka1 said:
Try it, but I think, you will get a message "not compatible" . Via dload its impossible, IMO use rather Huawei firmware finder or wait for OTA update.
Click to expand...
Click to collapse
yes it failed with b389 dload full
i'm on b371, i've to download and flash manually the b381 and after b389? where i can find otas?
Franseven said:
yes it failed with b389 dload full
i'm on b371, i've to download and flash manually the b381 and after b389? where i can find otas?
Click to expand...
Click to collapse
If I said, it's impossible manually update to 381 or 389 using OTA firmware, trust me . Try Firmware finder. GL!
bozka1 said:
If I said, it's impossible manually update to 381 or 389 using OTA firmware, trust me . Try Firmware finder. GL!
Click to expand...
Click to collapse
i tried full ota (firmware finder) flashes from twrp but gives error 7
e:unknown command [errno]
update_huawei_pkg_from_ota_zip: failed
Franseven said:
i tried full ota (firmware finder) flashes from twrp but gives error 7
e:unknown command [errno]
update_huawei_pkg_from_ota_zip: failed
Click to expand...
Click to collapse
https://m.youtube.com/watch?v=s5hHTZ4LGMM
bozka1 said:
https://m.youtube.com/watch?v=s5hHTZ4LGMM
Click to expand...
Click to collapse
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Franseven said:
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Click to expand...
Click to collapse
FF works with proxy fine, but you must first download and install Firmware finder proxy apk. On Nougat use TWRP 3.1.0-2.
---------- Post added at 21:03 ---------- Previous post was at 20:59 ----------
Franseven said:
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Click to expand...
Click to collapse
FF works with proxy , but you must download and install Firmware finder proxy apk. On Nougat use TWRP 3.1.0-2.
OMG, sorry !

Device failed verification - is there a way to clear this message?

Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..

Categories

Resources