# [DEV][Discontinued] - VNS-L21/22/23/31 [EU] Toolkit [0.0.0.12] All-in-One

#### k1ll3r8e

##### Senior Member
This project is not longer maintained!
-
For a new version of this project (P10 Lite Toolkit) have a look at this thread.

The latest build of this project is still available.
---

But anyways, i'm not responsible for any damage done to your device!

According to this post i strongly recommend that u check if your device is SIM-unlocked, before u flash any SIM upgrade! It's not guaranteed that u encounter the same issue see this post there were no problems after the unlock on an already flashed device.

!WARNING!
According to this post and an personal encounter of that behavior, there are a few devices which ends in an "black screen" after an "dload" based firmware update. - The only solutions to fix this "black screen" problem are currently the "Service-Center" or DC-Phoenix.
(For the DC-Phoenix solution see this post, there's everything explained and linked.)
-
1) Why this happens?
I found no answer so far... (i think, the update script went wrong or something couldn't be written during the update...)

2) Which devices/builds can encounter this problem?
So far i saw, its "LxxC02Bxxx", "LxxC440Bxxx" and some other maybe.

Tested Devices
Huawei P9 Lite [VNS-L31] [SINGLE-SIM]
Huawei P9 Lite [VNS-L21] [SINGLE-SIM]

Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4

Mirror: See attachments

Oeminfos
Mirror #1: My FTP
(Legend: DS = Dual-Sim | SS = Single-Sim)

Special THX goes to
@cybero2912 for sharing the...
@OldDroid for the permission to use his awesome TWRP
@miz_pimp for the links (Rollback L31C185B300 & Update L31C185B150) and info's
@SevenSlevin for the links to L31C432B385
@Chisetdel31260 for all the info's, links and tests (1, 2, 3, 4)
@Miss Montage for all the tests and confirmations
@kingjiji for the tests on P10 Lite
@witgit for the tests on P10 Lite

and for the oeminfo's & custom.bin's
@tw1st3d83 (VNS-L21 dual-sim C66)
@EasySR (VNS-L21 dual-sim C432)
@steven81 (VNS-L31 single-sim C109)
@SevenSlevin (VNS-L31 single-sim C432 & C113)
@Billy141 (VNS-L22 dual-sim C636)
@LuxZg (VNS-L21 single-sim C432)
@wakaru (VNS-L31 single-sim C440)
@mishuseby (VNS-L21 single-sim C02)
@oss_mosis (VNS-L23 dual-sim C605)
@radwan020 & [Farouk Nasri] (VNS-L31 dual-sim C185)

XDA:DevDB Information
VNS-L21/22/23/31 [EU] Toolkit, Tool/Utility for the Huawei P9 Lite

Contributors
k1ll3r8e

Version Information
Status:
Stable
Current Stable Version: 0.0.0.12
Stable Release Date: 2017-08-14

Created 2016-08-04
Last Updated 2018-04-05

#### Attachments

• vns_tk_disclaimer.png
119.9 KB · Views: 86,943
• vns_tk_packages.png
111.4 KB · Views: 86,854
• 2017-08-14.1922.zip
33.6 MB · Views: 203
Last edited:

#### k1ll3r8e

##### Senior Member
How - To

[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging! (see the screenshot)
(Only in adb mode my toolkit can detect ur device!)
3. Make sure that u granted adb access on ur device!
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.

U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:VNS-L31 model:HUAWEI_VNS_L31 device:XXXXXXX
XXXXXXXXXXXXXXX device product:VNS-L11 model:HUAWEI_VNS_L31 device:XXXXXXX

XXXXXXXXXXXXXXX device product:VNS-L23 model:HUAWEI_VNS_L23 device:XXXXXXX

XXXXXXXXXXXXXXX device product:VNS-L22 model:HUAWEI_VNS_L22 device:XXXXXXX

XXXXXXXXXXXXXXX device product:VNS-L21 model:HUAWEI_VNS_L21 device:XXXXXXX
XXXXXXXXXXXXXXX device product:VNS-L01 model:HUAWEI_VNS_L21 device:XXXXXXX

If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.

[Q:02] I updated to the LxxC432Bxxx/LxxC900Bxxx build, and now my device is shown as L01/L11 what should i do?
1) If u are on LxxC900Bxxx simply flash the LxxC432Bxxx build over it. And proceed with the following part.

2) If u are already on the LxxC432Bxxx, just follow the instructions under Dual-Sim, except the update to the LxxC432Bxxx, and proceed with the upgrade. After that, follow the steps written right under the Upgrade button.

[Q:03] What does the Lxx Cxxx Bxxx mean?
The L21/L22/23/L31 is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.

Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL

More comming soon...

Big THX for some of those "identifier" goes to:
@lost3

[Q:04] I want share my custom.bin & oeminfo, what i need to do?

U can get the files via the "Dual-/Single-SIM -> Export" tab or u can do the following steps (root required).

Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.

[Q:05] How can i avoid the factory-reset after the boot-loader unlock? (Work only on B130 or below)

1. When u confirmed the dialog with Yes and the device shutdown, start immediately pressing and holding [Vol- Power] until u see the boot-loader screen again. (The device must stay connected to the PC)
2. Now u need to flash the TWRP recovery to avoid the auto factory-reset.
3. Reboot ur device and boot into android with an unlocked boot-loader and without losing ur data.

[Q:06] How can i manually boot into a specific mode?

[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]

E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[fastboot] = N/A

Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[fastboot] = N/A

Normal Boot:
[device] = Power button / Power button menu
[fastboot] = fastboot reboot

Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[fastboot] = N/A

[Q:07] Does the Dual-Sim upgrade survive an OTA?

Yes, the Dual-Sim modification will stay until u flash another oeminfo.

[Q:08] I upgraded to Dual-SIM and there is only one IMEI shown?

That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim.

[Q:09] How can i craft my own package for the toolkit?

Well, that's pretty simple - Just open a text-editor like notepad++ and create a new xml file with the following content:
Main object
Code:
<Package xmlns="urn:Package-schema" id="UR_PACKAGE_ID" product="VNS-Lxx" author="UR_NAME">
...
</Package>
Now u can decide what a kind of package u want build:

Single-/Dual-SIM
Code:
...
<sim>
<version>LxxCxxxBxxx</version>
<type>Dual-SIM or Single-SIM</type>
<custom>custom.bin</custom> [I](The real filename)[/I]
<customMD5>CUSTOM_BIN_MD5</customMD5>
<oeminfo>oeminfo.img</oeminfo> [I](The real filename)[/I]
<oeminfoMD5>OEMINFO_MD5</oeminfoMD5>
<author>THE_FILE_PROVIDER</author> [I](The user from which u got the sim settings)[/I]
</sim>
...

Recovery-Stock
Code:
...
<recovery_stock>
<version>LxxCxxxBxxx</version>
<file>recovery_stock.img</file> [I](The real filename)[/I]
<md5>RECOVERY_MD5</md5>
<author>MANUFACTURER_NAME</author> [I](Should be Huawei)[/I]
</recovery_stock>
...

Recovery-TWRP
Code:
...
<recovery_twrp>
<version>Lxx - TWRP x.x.x-x</version>
<file>recovery_twrp.img</file> [I](The real filename)[/I]
<md5>RECOVERY_MD5</md5>
<author>MANUFACTURER_NAME</author> [I](Should be the user which compiled the image)[/I]
</recovery_twrp>
...

SuperSu
Code:
...
<superSu>
<version>x.xx (xxxx-xx-xx xx:xx) EMUIx.x</version>
<file>superSu.zip</file> [I](The real filename)[/I]
<md5>SUPERSU_MD5</md5>
<author>MANUFACTURER_NAME</author> [I](Should be the user which created/modded the zip)[/I]
</superSu>
...

U can use the 4 parts (sim, recovery_stock, recovery_twrp, superSu) all together or u can just build a package which hold only 1 or 2 components. The file it self must be saved as UTF8.

U can use the attached "package.xsd" file to validate ur package.

Now we come to the package structure, create a zip file with the following content:
Code:
./package.xml
./custom.bin
./oeminfo.img
./recovery_stock.img
./recovery_twrp.img
./superSu.zip
the files may vary, depending on what kind of package u build. Take care that the checksum's match with the provided files.

[Q:10] I get always "Software Update Failed!" what should i do?

First of all, check ur current build number LxxCxxxBxxx after that check the rom/update u downloaded. If ur version is greater/newer as the package u have, u can't install the package. In that case u "can" flash another oeminfo which is from an lower version.

For example: U have an L31C432B160 (device) and a L31C432B130 (package) u can't install this package via the default Huawei recovery, maybe it will work with TWRP (never tested it myself).

How to fix: Get u a package of the current installed firmware or a newer version. Or, downgrade ur oeminfo to a lower version and flash the package u have.

#### Attachments

• usbdebug.png
29.9 KB · Views: 11,698
• package.xsd
2.8 KB · Views: 663
Last edited:

#### k1ll3r8e

##### Senior Member
Changelog

DD.MM.YYYY | (A) = Added | (C) = Changed | (D) = Deleted | (F) = Fixed | (R) = Recoded | (U) Updated
----------------------------------------------------------------------------------------------------------------------------------------------------
28.05.2017
The toolkit images (coming soon)
[F] A Few UI freezes
[R] The UI and dialogs
[R] The complete root (Tab)
[A] Dual-/Single-SIM -> Export (Tab)
[A] Unbrick (Tab)
[A] Support for Nougat
[A] Support for L23 - Thx for the oeminfo + custom.bin + firmware goes to @oss_mosis

-- Not working --
The OTG under "Tweaks" currently only work on MM, i still working on it to get it also in N working.

22.02.2017
The toolkit images (coming soon)
[F] A few UI freezes and minor bugs
[C] The dual-/single-SIM guide
[A] An application manifest that request administrator permissions. This will fix the startup crash on Win 8.x and up. Because, if we have no admin permissions, we can't deploy the needed adb/fastboot binaries nor create any file or folder, like the backups.
[A] Tweaks, Double-Tap & USB-OTG (currently only on MM)
[A] Package-System, Package-Management - To make the toolkit a bit more flexible

22.02.2017 - 23:17
[F] Missing text string on the Bootloader -> Relock tab which caused the toolkit to crash.

27.09.2016
The toolkit images (coming soon)
[A] L22C636B140 Recovery

The recovery (huawei) view and the dual-sim (upgrade) view. I removed the buttons and added a combo-box.

[F] A bug which causes the device to be busy during the reboot dialog

.: History :.

01.09.2016
The toolkit images
[A] Ability to lock the bootloader (oem relock)
[A] Ability to flash a custom/backup custom.bin & oeminfo
[A] Ability to disable the device check

19.08.2016
The toolkit images
[A] All functions for the VNS-L21
[A] The L21C432B130 recovery
[F] The Dual-Sim guide, aligned it to the VNS-L21

09.08.2016
The toolkit images
[A] Detection for an running ADB-Server
[A] The ability to flash an individual recovery (with md5 sum check)
[F] The Dual-Sim guide, i explained it now with a bit more details
[A] A solution if u end in an Factory-Reset loop after the firmware update

07.08.2016
[A] Detection for the L11 bug

06.08.2016
[A] More debug messages e.g. wrong device state, no connected device etc.
[F] The unzip issue on some machines (oeminfo.img is now unzipped)
The guide how to flash the firmware

05.08.2016
Updated the dual-sim guide, according to the L31C432B130 update!
[C] The [Asia-Pacific] stock recovery to the [L31C432B130] recovery
[A] The links to the L31C432B130 update

04.08.2016
1st Release

Last edited:

#### k1ll3r8e

##### Senior Member
The DualSIM its my method?

It's the same method as on the P8 Lite, u need an oeminfo.img from an dual-sim device. Then u need a full firmware package which u can flash. I used for example the [Asia-Pacific] coz it was the only firmware available. Now, with the new L31C432B130 update i use this firmware, cos it's the Europe version for the device.

Regards,
Sebastian

Last edited:

#### Zeph1990

##### Senior Member
Nice work! Can't be a problem flash a dual sim firmware over a single sim device?

#### k1ll3r8e

##### Senior Member
Nice work! Can't be a problem flash a dual sim firmware over a single sim device?

I did the steps my self, on my P9 Lite [Single-Sim] and i had no problems. So far i know, only the oeminfo.img decides which phone u have, a single-sim or dual-sim. Also the [Asia-Pacific] build is a "single-sim" build which has dual-sim functionality inside, coz when u upgrade ur device to dual-sim with this rom, u have a dual-sim rom after the upgrade.

I made the same with the EU rom, reverted back to single-sim, installed the rom and reverted back to dual-sim no issues!

Hope that helps u

Regards,
Sebastian

##### Senior Member
false in the P8 Lite no OEMFILE needed... in P8LITE with FULL FIRMWARE its good...
But in P9LITE its needed de "private OEMFILE"...

#### k1ll3r8e

##### Senior Member
false in the P8 Lite no OEMFILE needed... in P8LITE with FULL FIRMWARE its good...
But in P9LITE its needed de "private OEMFILE"...

Well, i'm wrong? Seems u can't read?
Have a look at this thread specialy this post!

PS: If u have ever inspected the oeminfo with an hex-editor, u must had seen that it contains the curver or the verlist img (part wise) from the update package... (the oeminfo is a chunk divided file so far i can see, it includes more as only 1 build info...)

Edit:
Just to respond to ur "Is that my method?" maybe u've got "ur method" from here?^^

Regards,
Sebastian

Last edited:

#### k1ll3r8e

##### Senior Member
I think that @BadWolfYe meant this method: http://www.htcmania.com/showpost.php?p=23861935&postcount=2
He probably didn't invent all of it, but he put some effort into research and writing the tutorial in Spanish and English

Hi Miss Montage,

to end the discussion who invent which "wheel". I can only say the following things, i got my device on 02.07.2016 from t-mobile. Since that day i have read about how to unlock the dual-sim. I also called Huawei Customer Service and spoke there to some technical guys. I have tried my self a lot different ways to get dual-sim unlocked. I started my research here on XDA and on Android-Hilfen (see the links i have already posted, and i have a lot more to read about...). Finally i found a link to this ROM which i used until yesterday and a collection of 2 different oeminfo's on some chinese website. I compared them and don't tried to flash the oeminfo's, coz i don't wanted to brick my device! Then i found this post here on XDA and asked for a partition backup of an dual-sim device, to compare the partitions with mine. And got this response. I compared the file with the both i already had and one of them matched with md5 checksum. So i started research where this file comes from and found after hours this post as linked here.

There i got the confirmation that the file and idea i already had don't brick my device!

So, sry, but i have not copied any other work!
(And if u want say so, then at least ALL CREDITS go to this post coz, there are the logic what u have when to do^^)

I hope that make some things clear...

Regards,
Sebastian

Last edited:
Miss Montage

#### Miss Montage

##### Senior Member
I didn't imply that you stole anything, sorry if my post came across this way. It just happens that two people work on a similar idea and come to similar results I can't check out your tool, I am a linux user and it won't open in Wine.

#### mqdjo

##### Member
Can we use this toolkit with VNS-L21?

just_me_4lexutzu

#### k1ll3r8e

##### Senior Member
Can we use this toolkit with VNS-L21?

Heyho,
nope sry, it's currently only for the L31 coz i can't test the toolkit on the L21 so i included a device check which will only accept the L31.

If u want, i can write up a toolkit for the L21 but in this toolkit i can't add an dual-sim upgrade, coz i have currently no L21-oeminfo from an dual-sim device.

Regards,
Sebastian

#### k1ll3r8e

##### Senior Member
The l21 and l31 are same oeminfo i used the l21 in l31

Heyho,

maybe this will work here is a hex view of the EU L31 oeminfo:

Code:
00011200h: 68 77 2F 65 75 FF FF FF FF FF FF FF FF FF FF FF ; hw/euÿÿÿÿÿÿÿÿÿÿÿ
...
00043200h: 72 65 73 63 75 65 3A 56 4E 53 2D 4C 33 31 43 34 ; rescue:VNS-L31C4
00043210h: 33 32 42 31 30 34 FF FF FF FF FF FF FF FF FF FF ; 32B104ÿÿÿÿÿÿÿÿÿÿ
...
0004d200h: 56 4E 53 2D 4C 33 31 43 34 33 32 42 31 33 30 00 ; VNS-L31C432B130.
...
0005a200h: 48 55 41 57 45 49 20 56 4E 53 2D 4C 33 31 00 00 ; HUAWEI VNS-L31..
...
00060200h: 56 4E 53 2D 4C 33 31 FF FF FF FF FF FF FF FF FF ; VNS-L31ÿÿÿÿÿÿÿÿÿ
...
00064200h: 56 4E 53 2D 4C 33 31 43 34 33 32 42 31 30 34 00 ; VNS-L31C432B104.
...

Regards,
Sebastian

#### mqdjo

##### Member
Heyho,
nope sry, it's currently only for the L31 coz i can't test the toolkit on the L21 so i included a device check which will only accept the L31.

If u want, i can write up a toolkit for the L21 but in this toolkit i can't add an dual-sim upgrade, coz i have currently no L21-oeminfo from an dual-sim device.

Regards,
Sebastian
I need it mostly for dual sim upgrade, thank you anyway

Sent from my HUAWEI VNS-L21 using Tapatalk

#### mastermoon

##### Senior Member
using adb devices -l i have this result device product:VNS-L11 model:HUAWEI_VNS_L31 device:HWVNS-H and it doesn't recon by toolkit... mine is p9 lite single sim there is a workaround?

#### k1ll3r8e

##### Senior Member
using adb devices -l i have this result device product:VNS-L11 model:HUAWEI_VNS_L31 device:HWVNS-H and it doesn't recon by toolkit... mine is p9 lite single sim there is a workaround?

Heyho,

yes i just write the update for my toolkit, so that u can use it with the "L11" fake/bug and restore to the EU rom with aligned oeminfo.

Regards,
Sebastian

#### mastermoon

##### Senior Member
Heyho,

yes i just write the update for my toolkit, so that u can use it with the "L11" fake/bug and restore to the EU rom with aligned oeminfo.

Regards,
Sebastian

tnx a lot... only one thing i suggest you to write all the procedure step bt step in a pdf that can help newbie to use it...

### Top Liked Posts

• There are no posts matching your filters.
• 97
This project is not longer maintained!
-
For a new version of this project (P10 Lite Toolkit) have a look at this thread.

The latest build of this project is still available.
---

But anyways, i'm not responsible for any damage done to your device!

According to this post i strongly recommend that u check if your device is SIM-unlocked, before u flash any SIM upgrade! It's not guaranteed that u encounter the same issue see this post there were no problems after the unlock on an already flashed device.

!WARNING!
According to this post and an personal encounter of that behavior, there are a few devices which ends in an "black screen" after an "dload" based firmware update. - The only solutions to fix this "black screen" problem are currently the "Service-Center" or DC-Phoenix.
(For the DC-Phoenix solution see this post, there's everything explained and linked.)
-
1) Why this happens?
I found no answer so far... (i think, the update script went wrong or something couldn't be written during the update...)

2) Which devices/builds can encounter this problem?
So far i saw, its "LxxC02Bxxx", "LxxC440Bxxx" and some other maybe.

Tested Devices
Huawei P9 Lite [VNS-L31] [SINGLE-SIM]
Huawei P9 Lite [VNS-L21] [SINGLE-SIM]

Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4

Mirror: See attachments

Oeminfos
Mirror #1: My FTP
(Legend: DS = Dual-Sim | SS = Single-Sim)

Special THX goes to
@cybero2912 for sharing the...
@OldDroid for the permission to use his awesome TWRP
@miz_pimp for the links (Rollback L31C185B300 & Update L31C185B150) and info's
@SevenSlevin for the links to L31C432B385
@Chisetdel31260 for all the info's, links and tests (1, 2, 3, 4)
@Miss Montage for all the tests and confirmations
@kingjiji for the tests on P10 Lite
@witgit for the tests on P10 Lite

and for the oeminfo's & custom.bin's
@tw1st3d83 (VNS-L21 dual-sim C66)
@EasySR (VNS-L21 dual-sim C432)
@steven81 (VNS-L31 single-sim C109)
@SevenSlevin (VNS-L31 single-sim C432 & C113)
@Billy141 (VNS-L22 dual-sim C636)
@LuxZg (VNS-L21 single-sim C432)
@wakaru (VNS-L31 single-sim C440)
@mishuseby (VNS-L21 single-sim C02)
@oss_mosis (VNS-L23 dual-sim C605)
@radwan020 & [Farouk Nasri] (VNS-L31 dual-sim C185)

XDA:DevDB Information
VNS-L21/22/23/31 [EU] Toolkit, Tool/Utility for the Huawei P9 Lite

Contributors
k1ll3r8e

Version Information
Status:
Stable
Current Stable Version: 0.0.0.12
Stable Release Date: 2017-08-14

Created 2016-08-04
Last Updated 2018-04-05
19
How - To

[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging! (see the screenshot)
(Only in adb mode my toolkit can detect ur device!)
3. Make sure that u granted adb access on ur device!
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.

U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:VNS-L31 model:HUAWEI_VNS_L31 device:XXXXXXX
XXXXXXXXXXXXXXX device product:VNS-L11 model:HUAWEI_VNS_L31 device:XXXXXXX

XXXXXXXXXXXXXXX device product:VNS-L23 model:HUAWEI_VNS_L23 device:XXXXXXX

XXXXXXXXXXXXXXX device product:VNS-L22 model:HUAWEI_VNS_L22 device:XXXXXXX

XXXXXXXXXXXXXXX device product:VNS-L21 model:HUAWEI_VNS_L21 device:XXXXXXX
XXXXXXXXXXXXXXX device product:VNS-L01 model:HUAWEI_VNS_L21 device:XXXXXXX

If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.

[Q:02] I updated to the LxxC432Bxxx/LxxC900Bxxx build, and now my device is shown as L01/L11 what should i do?
1) If u are on LxxC900Bxxx simply flash the LxxC432Bxxx build over it. And proceed with the following part.

2) If u are already on the LxxC432Bxxx, just follow the instructions under Dual-Sim, except the update to the LxxC432Bxxx, and proceed with the upgrade. After that, follow the steps written right under the Upgrade button.

[Q:03] What does the Lxx Cxxx Bxxx mean?
The L21/L22/23/L31 is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.

Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL

More comming soon...

Big THX for some of those "identifier" goes to:
@lost3

[Q:04] I want share my custom.bin & oeminfo, what i need to do?

U can get the files via the "Dual-/Single-SIM -> Export" tab or u can do the following steps (root required).

Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.

[Q:05] How can i avoid the factory-reset after the boot-loader unlock? (Work only on B130 or below)

1. When u confirmed the dialog with Yes and the device shutdown, start immediately pressing and holding [Vol- Power] until u see the boot-loader screen again. (The device must stay connected to the PC)
2. Now u need to flash the TWRP recovery to avoid the auto factory-reset.
3. Reboot ur device and boot into android with an unlocked boot-loader and without losing ur data.

[Q:06] How can i manually boot into a specific mode?

[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]

E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[fastboot] = N/A

Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[fastboot] = N/A

Normal Boot:
[device] = Power button / Power button menu
[fastboot] = fastboot reboot

Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[fastboot] = N/A

[Q:07] Does the Dual-Sim upgrade survive an OTA?

Yes, the Dual-Sim modification will stay until u flash another oeminfo.

[Q:08] I upgraded to Dual-SIM and there is only one IMEI shown?

That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim.

[Q:09] How can i craft my own package for the toolkit?

Well, that's pretty simple - Just open a text-editor like notepad++ and create a new xml file with the following content:
Main object
Code:
<Package xmlns="urn:Package-schema" id="UR_PACKAGE_ID" product="VNS-Lxx" author="UR_NAME">
...
</Package>
Now u can decide what a kind of package u want build:

Single-/Dual-SIM
Code:
...
<sim>
<version>LxxCxxxBxxx</version>
<type>Dual-SIM or Single-SIM</type>
<custom>custom.bin</custom> [I](The real filename)[/I]
<customMD5>CUSTOM_BIN_MD5</customMD5>
<oeminfo>oeminfo.img</oeminfo> [I](The real filename)[/I]
<oeminfoMD5>OEMINFO_MD5</oeminfoMD5>
<author>THE_FILE_PROVIDER</author> [I](The user from which u got the sim settings)[/I]
</sim>
...

Recovery-Stock
Code:
...
<recovery_stock>
<version>LxxCxxxBxxx</version>
<file>recovery_stock.img</file> [I](The real filename)[/I]
<md5>RECOVERY_MD5</md5>
<author>MANUFACTURER_NAME</author> [I](Should be Huawei)[/I]
</recovery_stock>
...

Recovery-TWRP
Code:
...
<recovery_twrp>
<version>Lxx - TWRP x.x.x-x</version>
<file>recovery_twrp.img</file> [I](The real filename)[/I]
<md5>RECOVERY_MD5</md5>
<author>MANUFACTURER_NAME</author> [I](Should be the user which compiled the image)[/I]
</recovery_twrp>
...

SuperSu
Code:
...
<superSu>
<version>x.xx (xxxx-xx-xx xx:xx) EMUIx.x</version>
<file>superSu.zip</file> [I](The real filename)[/I]
<md5>SUPERSU_MD5</md5>
<author>MANUFACTURER_NAME</author> [I](Should be the user which created/modded the zip)[/I]
</superSu>
...

U can use the 4 parts (sim, recovery_stock, recovery_twrp, superSu) all together or u can just build a package which hold only 1 or 2 components. The file it self must be saved as UTF8.

U can use the attached "package.xsd" file to validate ur package.

Now we come to the package structure, create a zip file with the following content:
Code:
./package.xml
./custom.bin
./oeminfo.img
./recovery_stock.img
./recovery_twrp.img
./superSu.zip
the files may vary, depending on what kind of package u build. Take care that the checksum's match with the provided files.

[Q:10] I get always "Software Update Failed!" what should i do?

First of all, check ur current build number LxxCxxxBxxx after that check the rom/update u downloaded. If ur version is greater/newer as the package u have, u can't install the package. In that case u "can" flash another oeminfo which is from an lower version.

For example: U have an L31C432B160 (device) and a L31C432B130 (package) u can't install this package via the default Huawei recovery, maybe it will work with TWRP (never tested it myself).

How to fix: Get u a package of the current installed firmware or a newer version. Or, downgrade ur oeminfo to a lower version and flash the package u have.
11
Changelog

DD.MM.YYYY | (A) = Added | (C) = Changed | (D) = Deleted | (F) = Fixed | (R) = Recoded | (U) Updated
----------------------------------------------------------------------------------------------------------------------------------------------------
28.05.2017
The toolkit images (coming soon)
[F] A Few UI freezes
[R] The UI and dialogs
[R] The complete root (Tab)
[A] Dual-/Single-SIM -> Export (Tab)
[A] Unbrick (Tab)
[A] Support for Nougat
[A] Support for L23 - Thx for the oeminfo + custom.bin + firmware goes to @oss_mosis

-- Not working --
The OTG under "Tweaks" currently only work on MM, i still working on it to get it also in N working.

22.02.2017
The toolkit images (coming soon)
[F] A few UI freezes and minor bugs
[C] The dual-/single-SIM guide
[A] An application manifest that request administrator permissions. This will fix the startup crash on Win 8.x and up. Because, if we have no admin permissions, we can't deploy the needed adb/fastboot binaries nor create any file or folder, like the backups.
[A] Tweaks, Double-Tap & USB-OTG (currently only on MM)
[A] Package-System, Package-Management - To make the toolkit a bit more flexible

22.02.2017 - 23:17
[F] Missing text string on the Bootloader -> Relock tab which caused the toolkit to crash.

27.09.2016
The toolkit images (coming soon)
[A] L22C636B140 Recovery

The recovery (huawei) view and the dual-sim (upgrade) view. I removed the buttons and added a combo-box.

[F] A bug which causes the device to be busy during the reboot dialog

.: History :.

01.09.2016
The toolkit images
[A] Ability to lock the bootloader (oem relock)
[A] Ability to flash a custom/backup custom.bin & oeminfo
[A] Ability to disable the device check

19.08.2016
The toolkit images
[A] All functions for the VNS-L21
[A] The L21C432B130 recovery
[F] The Dual-Sim guide, aligned it to the VNS-L21

09.08.2016
The toolkit images
[A] Detection for an running ADB-Server
[A] The ability to flash an individual recovery (with md5 sum check)
[F] The Dual-Sim guide, i explained it now with a bit more details
[A] A solution if u end in an Factory-Reset loop after the firmware update

07.08.2016
[A] Detection for the L11 bug

06.08.2016
[A] More debug messages e.g. wrong device state, no connected device etc.
[F] The unzip issue on some machines (oeminfo.img is now unzipped)
The guide how to flash the firmware

05.08.2016
Updated the dual-sim guide, according to the L31C432B130 update!
[C] The [Asia-Pacific] stock recovery to the [L31C432B130] recovery
[A] The links to the L31C432B130 update

04.08.2016
1st Release

6
Little Update

God bless the T-Com!
Two days ago my battery leaked out... So my P9 Lite is now official DESTROYED the acid made it's way in the whole device...
But today i got my brand new P10 Lite :victory: - So a toolkit for the P10 Lite will come up in the next days.

EDIT:
Attached a img of the corroded battery...

EDIT 2+3+4+5:
Finally it's done!
Here is the link to the new toolkit

Regards,
Sebastian
6
That sucks. How long have you had the device?

Heyho,
i got my device on 02.07.2016 (d/m/y) from t-mobile, so the device is a bit older as an year.
(Also, i never used another charger as the original one... And this one head up to 40-50° since ~5 days... Seems that the charger and the battery is made from really cheap material... When i got my new battery i'll made a vid of the disassemble and finally, how it looks when this battery will get "shorted", if it catches fire or not.)

Update:
I just got my new battery, super fast deliver!!!

Edit:
Based on the bad video codec which the cam has, i added some images from the "disassembly". The video about the battery, explosion or not, comes in the next days. I spoke to a friend which has a professional cam, he will film it this weekend.

Edit 2:
Little hint: I used a "carpet-cutter-blade" (not the "rake-blade", the "straight" one) to remove the NFC-Antenna (the white "plastic-pad").
!!! IMPORTANT !!!
If u use a blade like me, be really carefully with it, if u "stipple" the battery with the blade, it can explode instantly! U can also use a "fan / hairdryer" to head it up that u can "hopefully" remove the antenna. I didn't used a fan because, i didn't want expose the already damaged battery to such an direct heat-source.

Regards,
Sebastian