Related
So,
My phone is vns-l21c66b131 and is there any way to update to newer versions without rooting and if possible can someone write steps on how to do it?
If you use <SEARCH> you find followings:
<After a few day of reading users personal experiences regarding upgrade to Android 7 Nougat i make the big step myself...
My device is VNS-L21 model and entire process goes flawless...
Device state was stock MM VNS-L21C432B150, bootloader lock, dualsim enabled.
1. Unlock bootloader folowing by Automatic Factory Reset.
2. Flash TWRP
3. From TWRP i flash Meticulus TWRP
4. Reboot to TWRP and flash update.zip and update_data_full_VNS-L31_hw_eu.zip, both flash ends with errors, without reboot between flashes.
5. After that, i reboot device and boot in system ok, start configuration, etc.
6. I reboot to fastboot and flash Nougat Recovery reworked by @BadWolfYe
I am not experienced camera bug, all works fine and i have now a fully functional phone.
BTW, dualsim remain enabled and works both sims.
Thanks to all contributors for these pieces of firmware, first of all to @BadWolfYe!>
For that's is <SEARCH>, not to open another topic for same problem...
Thanks for the reply, but I'm not talking about Nougat, I talk about MM b161 update. How to do it if my carrier is c66 and the newest update there is b131
Coolyou said:
Thanks for the reply, but I'm not talking about Nougat, I talk about MM b161 update. How to do it if my carrier is c66 and the newest update there is b131
Click to expand...
Click to collapse
If you want to stay on C66 you have to wait to OTA updates...
If you make any upgrade via dload folder on sdcard your phone will go from C66 to C900 (global)
Another alternative is to debrand your phone to C432 (hw eu)
For any of this is treated here in some topics...
So I just need to create dload folder and put the zip there?
Coolyou said:
So I just need to create dload folder and put the zip there?
Click to expand...
Click to collapse
Not the zip! Put the update.app wich is in the zip, for this method.
The zip is ok for update from TWRP.
gtdaniel said:
Not the zip! Put the update.app wich is in the zip, for this method.
The zip is ok for update from TWRP.
Click to expand...
Click to collapse
Do i lose warranty if i change to global ?
I'm at my wits end here. I copied the contents the emoji zip from https://android.gadgethacks.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/ for Android N emojis on my L02 (Telstra Australia variant ALE-L52) on 5.0.1 into my system folder and caused it to bootloop, then I got TWRP installed and actually flashed it which let it boot but with a different font and Messaging and Phone among other things weren't working. So I reflashed with 5.1 variants of those files in that zip and flashed a 6.0 stock recovery and did a factory reset and now it won't even let me log in to a Google account so I can restore my app backups which means I'm locked out of several apps I need authenticators for.
Is there anywhere I can download the full image for ALE-L02C451B280? I have access to a second device but I do not want to void the warranty on that by unlocking the bootloader and replacing the recovery just to fix my phone, so is there a way to create a flashable backup of the system without root or an unlocked bootloader
Edit: Great, flashed the official 6.0 image like suggested in the updating thread and now it won't even get past the bootloader, can't even boot to fastboot or recovery. It's officially f**ked
Well, if you can't boot to bootloader/fastboot to install TWRP, repair the phone then your phone is kinda bricked
I see the same symptoms as mine
https://forum.xda-developers.com/p8lite/help/help-bricked-p8-lite-t3522136
Any new suggestions?
What does your bootloader say? Enter it and unpack the UPDATE.APP using Huawei Update Extractor. Then flash System, cust, boot and mybe recovery with fastboot.
Vinnipinni said:
What does your bootloader say? Enter it and unpack the UPDATE.APP using Huawei Update Extractor. Then flash System, cust, boot and mybe recovery with fastboot.
Click to expand...
Click to collapse
That's how it ended up bricked in the first place
mercom said:
I see the same symptoms as mine
https://forum.xda-developers.com/p8lite/help/help-bricked-p8-lite-t3522136
Any new suggestions?
Click to expand...
Click to collapse
I ended up fixing it by doing a nandroid backup of another L02 running the original Telstra firmware and restored that, fixed it with a few minor bugs (gave me the Balong bug, so I can't even download any Huawei apps anymore, and I can't disable the stock music app for some reason, and the lock screen is weird, I can't swipe to unlock anywhere it has to be from the circle in the middle). I've just given up hope that I can get the official 6.0 on my L02
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!
[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 !
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..