Database Users

Cant open play store or connect to any google account

After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?

Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.

gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.

I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.

No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware

raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?

I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..

sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.

since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161

HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !

simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.

HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset

medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.

Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server

Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you

HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:

MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.

HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?

Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.

Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.

HUAWEI P9 LITE NRD90M(test-keys) TO MM HELP Urgent

Plzzz help im stuck I want to rollback my huawei p9 lite VNS-L31 where its build number is NRD90M(test keys) to marshmallow 6.0 help don't know what to do . Plz if you can explain step by step what can i do because i'm not good in these things , My bluetooth not workng , there no calculator , no software updater , i am not able to check if got update or not and so on......, im stuck plz help

Well hey.. first download this rollback package from this link:
http://download-c1.huawei.com/download/downloadCenter?downloadId=93645&version=371484&siteCode=np
Extract and move all the files to dload folder on your external SD Card then install it with the 3 button method. If there's no dload folder then create one.
So the phone will reboot and now you can downgrade to any mm rom
Now just download this mm rom from this link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66015/f1/full/update.zip
And again extract and move the files to dload folder on your sd card.. Install with 3 button method.
Done! Everything should work now!
In case If you don't know what the 3 button method is..lol
•Power the phone off ?
•Just press and hold on POWER + VOLUME UP + VOLUME DOWN buttons
The phone will start installing the rom and that's the 3 button method ?❤

this is not working for me. it says incompatibility with current version and to download the correct version.

lennie27 said:
this is not working for me. it says incompatibility with current version and to download the correct version.
Click to expand...
Click to collapse
Man, you have to do entire procedure: unlock bootloader, install twrp for Nougat and flash oeminfo for your phone. Before that you have to put in dload folder MM firmware (B130/B131),
because after flashing oeminfo phone try to repair firmware from dload folder. If repair do not start, power off phone and power on with 3 keys combination.

Hi All,
I'm having a similar issue as lennie27 however I think I might have strayed down an incorrect path during the process of upgrading to Nougat. My device shipped with VNS-L31C16B120 with no updates available through the stock updater. I tried the Firmware Finder guides which listed options for VNS-L31C169B13x and VNS-L31C432B13x however none of these updates would work, updater would say it's incompatible with current version. I also tried manually downloading the VNS-L31C432B160 firmware and installing that with the 3 button method as well as the EngineerMenu option with the same result (found guides that stated needing to be on B160 or B161 before making the jump to Nougat). Eventually I decided to unlock the bootloader and install Nougat through TWRP and followed the obeygeekupdate-huawei-p9-lite-to-android-7-0-nougat-manually guide (can't post links ) on manually installing Nougat (stupidly never paying attention to the fact that it's a beta build guide). I've installed TWRP to the device again using the P9 Lite Toolkit v0.0.0.11 found here on XDA (used this when on MM however the upgrade seemed to restore the stock recovery) with the idea of downloading the build from the ministryofsolutions huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe page and pushing that to the device instead (however now the device doesn't want to boot into recovery)
Now my only concern is, will this work? I've noticed a bit of commenting going back and forth on the ministryofsolutions site which essentially boiled down to the need for debranding the phone (apparently C19 is MTN South Africa specific and I need to debrand it and get it onto C432 Europe before mucking about with Nougat, but alas to late) which seemed to be something I should have done while on MM still. If I can find a full firmware link for VNS-L31C16B120 can I flash that through TWRP without needing to follow any prerequisite steps? So far nothing that I've tried to flash using the three button method has worked, I'd just like to get back onto an official stable firmware again.
Any advice will be appreciated

saintnite said:
Hi All,
I'm having a similar issue as lennie27 however I think I might have strayed down an incorrect path during the process of upgrading to Nougat. My device shipped with VNS-L31C16B120 with no updates available through the stock updater. I tried the Firmware Finder guides which listed options for VNS-L31C169B13x and VNS-L31C432B13x however none of these updates would work, updater would say it's incompatible with current version. I also tried manually downloading the VNS-L31C432B160 firmware and installing that with the 3 button method as well as the EngineerMenu option with the same result (found guides that stated needing to be on B160 or B161 before making the jump to Nougat). Eventually I decided to unlock the bootloader and install Nougat through TWRP and followed the obeygeekupdate-huawei-p9-lite-to-android-7-0-nougat-manually guide (can't post links ) on manually installing Nougat (stupidly never paying attention to the fact that it's a beta build guide). I've installed TWRP to the device again using the P9 Lite Toolkit v0.0.0.11 found here on XDA (used this when on MM however the upgrade seemed to restore the stock recovery) with the idea of downloading the build from the ministryofsolutions huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe page and pushing that to the device instead (however now the device doesn't want to boot into recovery)
Now my only concern is, will this work? I've noticed a bit of commenting going back and forth on the ministryofsolutions site which essentially boiled down to the need for debranding the phone (apparently C19 is MTN South Africa specific and I need to debrand it and get it onto C432 Europe before mucking about with Nougat, but alas to late) which seemed to be something I should have done while on MM still. If I can find a full firmware link for VNS-L31C16B120 can I flash that through TWRP without needing to follow any prerequisite steps? So far nothing that I've tried to flash using the three button method has worked, I'd just like to get back onto an official stable firmware again.
Any advice will be appreciated
Click to expand...
Click to collapse
you need to install nougat recovery, not the one from the toolkit. then twrp will work and the device will boot.
to go back to 120 you need to install oeminfo, and then the update.app

mjz2cool said:
you need to install nougat recovery, not the one from the toolkit. then twrp will work and the device will boot.
to go back to 120 you need to install oeminfo, and then the update.app
Click to expand...
Click to collapse
Thank you for the reply, managed to come right a few hours after posting. Turned out the copy of TWRP that I had on hand was more outdated than I thought, downloaded the newest copy and that worked on the device. Additionally I managed to find a website listing just about every firmware for the phone (Including my original MTN ZA specific variant) so I downloaded that and managed to restore the phone using the three button method. Phone is back to stock now and even the unlocked bootloader nag screen is gone so I'm guessing the bootloader is locked again as well One day when I'm brave enough to attempt this again I'll look at debranding the phone and getting it onto a C432 based ROM before getting it onto Nougat again.

phone bricked
hello guys! im currently on lineage os 14.1 by meticulus, i wanna revert back to stock mm but i cant. i flashed the custom rom from mm using twrp recovery by meticulus, but now i cant even boot into erecovery! can you pls help me!:crying: DLOAD method doesnt work!

P9 Lite VNS-L31 - Can't upgrade to nougat after rollback

Hi all,
i own a p9 lite that was on Nougat VNS-L31C432B381 and i decided to rollback to MM. Following Huawei website instructions I downloaded two packages (rollback package and MM) and with 3 buttons method I flash first the rollback package and then MM. All went right and the ROM was stable. After a while of testing (that's why i went to MM), I decided to upgrade to nougat again. From updater it download and install the new android version (1.25 GB). After reboot I noticed that some system app was missing (file manager first). At every reset/factory reset some system app disappear. I repeated the procedure to rollback and upgrade again with the same result. The only way to use the device was to reflash MM and don't upgrade. Here some information I found:
- my starting version was Nougat VNS-L31C432B381
- now I'm on VNS-L31C432B160 (B160 isn't for dual sim? i have the single sim version) stock recovery bootloader locked
- updater try to install VNS-L31C432B370 (instead of B371?)
- if I try upgrade throught updater SN became something like ndr90 test key
- I tried to restore data,syste,vendor,oeminfo ecc.. from backups made with TWRP in Nougat (maybe wahile i was on MM, I'm not sure). It show the correct SN but ROM was still unstable
- I thought to try install full Nougat ROM but i didn't find any package
Can someone help me?
Thank you

The B37x update that the phone automatically finds after rollback doesn't work and will take you to ndr90 test key as you found out B160 is dualsim so you should flash the 161 one. Then use this guide to update through firmwarefinder/proxy https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
If you want to unlock your bootloader you can also flash B3xx through twrp. If not, the guide above works fine.

Mara-X said:
The B37x update that the phone automatically finds after rollback doesn't work and will take you to ndr90 test key as you found out B160 is dualsim so you should flash the 161 one. Then use this guide to update through firmwarefinder/proxy https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
If you want to unlock your bootloader you can also flash B3xx through twrp. If not, the guide above works fine.
Click to expand...
Click to collapse
Hi Mara-X and thank you for you answer.
After I write the post i found the B161 package and i decided to give it a try. After flash (all ok) I launched updater again and it download the B371. The update went well and now i'm updating at B381 again throught updater. I think, when it was done, i'll factory reset the device for a clean install. So it seems the problem was B160/161 -single/dual version.

Help with Huawei P9 Lite Possible brick

Hi
I have the Huawei P9 Lite (from south africa)
Model number: HUAWEI VNS-L31
Build number: VNS-L31C185B381
I received the phone with Android Marshmallow and did OTA upgrade to Nougat.
Yesterday I unlocked bootloader and rooted my phone using twrp-3.1.1-0-venus and SuperSU-v2.82 and all went smoothly. I decided to unroot because of issues with banking app. I did a full unroot, but also tried to relock/lock the bootloader, and that's where things went south.
I tried multiple things including trying to flashing the stock ROM (I hope it's the right one) and by following some tutorials online managed to wipe the OS. After multiple stuff I tried I managed to get the phone to boot, but then I only had voice as input method and had none of the Huawei stock apps.
When booting into recovery mode (TWRP), I tried to flash the update.zip I downloaded, but I get error that it can't mount /data and Error code 7.
What I did now was did a complete wipe in TWRP (including OS), extracted the boot.img and system.img from the update.zip and the cust.img from update_full_VNS-L31_hw_meafnaf.zip. I flashed them in fastboot and installed update_data_full_public.zip from TWRP for the Huawei apps (I still got the error that it can't mount /data but it still installed). My phone boots successfully and has the default keyboard and apps enabled again, I thought everything was fixed. When I reached the screen to select security method, after confirming pin/password a second time, it takes me back to the screen where I should choose a security method, not saving my selection. I skipped this to just reach the phone home screen. I enabled developer option, but when clicking on developer options it closes to home screen immediately, so I can't enable USB debugging.
Can someone please help me get my phone into a fully working state (as it was shipped), preferably with bootloader locked (But it's okay if it isn't as that's where my problems started). It is possible that I had wrong versions of ROMs or recovery or something. There is no data I need to preserve, any method to get my phone to it's default working state is what I need. So any help/ links to correct ROMs would be really helpful
Edit:
Even if there is a way for me to just lock the bootloader so that the warranty is back so that I can maybe send it in for replacement

buzzlightyear1309 said:
Hi
I have the Huawei P9 Lite (from south africa)
Model number: HUAWEI VNS-L31
Build number: VNS-L31C185B381
I received the phone with Android Marshmallow and did OTA upgrade to Nougat.
Yesterday I unlocked bootloader and rooted my phone using twrp-3.1.1-0-venus and SuperSU-v2.82 and all went smoothly. I decided to unroot because of issues with banking app. I did a full unroot, but also tried to relock/lock the bootloader, and that's where things went south.
I tried multiple things including trying to flashing the stock ROM (I hope it's the right one) and by following some tutorials online managed to wipe the OS. After multiple stuff I tried I managed to get the phone to boot, but then I only had voice as input method and had none of the Huawei stock apps.
When booting into recovery mode (TWRP), I tried to flash the update.zip I downloaded, but I get error that it can't mount /data and Error code 7.
What I did now was did a complete wipe in TWRP (including OS), extracted the boot.img and system.img from the update.zip and the cust.img from update_full_VNS-L31_hw_meafnaf.zip. I flashed them in fastboot and installed update_data_full_public.zip from TWRP for the Huawei apps (I still got the error that it can't mount /data but it still installed). My phone boots successfully and has the default keyboard and apps enabled again, I thought everything was fixed. When I reached the screen to select security method, after confirming pin/password a second time, it takes me back to the screen where I should choose a security method, not saving my selection. I skipped this to just reach the phone home screen. I enabled developer option, but when clicking on developer options it closes to home screen immediately, so I can't enable USB debugging.
Can someone please help me get my phone into a fully working state (as it was shipped), preferably with bootloader locked (But it's okay if it isn't as that's where my problems started). It is possible that I had wrong versions of ROMs or recovery or something. There is no data I need to preserve, any method to get my phone to it's default working state is what I need. So any help/ links to correct ROMs would be really helpful
Edit:
Even if there is a way for me to just lock the bootloader so that the warranty is back so that I can maybe send it in for replacement
Click to expand...
Click to collapse
Seems to be bad oem.info...??? Try reinstall it...
Odoslané z HUAWEI VNS-L21 pomocou Tapatalku

mrmajco said:
Seems to be bad oem.info...??? Try reinstall it...
Odoslané z HUAWEI VNS-L21 pomocou Tapatalku
Click to expand...
Click to collapse
Hi, I am quite new to rooting and mostly followed tutorials. Can you maybe instruct me how to do this or give links to a tutorial/download link?

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..