Related
I want to do ROM upgrade,but in the window of confirmation ROM version "from" and "To" there is no any version no. (as the messege below) :
Your device software is about to be update from :
Device CE image version :
Device Extended image version :
Device Radio image version :
To :
CE image version :
Extended image version :
Radio image version :
* no any version number show on that window,and then it skip to "Congratulations" ...no any update at all.
Pls help me krub. (I use Activesync Ver.3.8)
-I want to change radio version from 1.13 -> 1.17
-mine is XDAIIs krub
hi,
remove your pda from cradle, make soft reset, wait till end of activesyncronisation. after that to be sure, that radio update file is in the same directory as you try to run baupgrade or ma upgrade executable.
where is it available version 1.17? I am tired by radio 1.13.
best regards
I already put them all together in the same folder
I already put them all together,here they are :
- enterBL.exe
- GetDeviceData.exe
- MaUpgradeUt_noID.exe
- ms_.nbf
- nk.nbf
- radio_.nbf
- RUU.conf
- RUU.dll
Actually I have done success with these files once yesterday.But today it's unusual. Pls try to consider about this problem condition again. thanks and this is the link to get radio version 1.17 :
http://www.pdamobiz.com/show_news.asp?NewsID=23224&PN=1
Could you check error messages in file c:\ruu.log?
not to use
radio 1.17 that i yold u in weblink that u post is for XdaII not for xdaIIs the newest radio rom for xdaIIs is 1.13
ดีนะครับไม่อัพไปได้ ไม่งั้นพังแหงๆ 555
Not upgrading
I had the same problem. Try using BaUpgradeUt.exe and it worked for me.
DEK
Hi all,
This is my first attempt to contribute to this forum. Hope you like it. :wink:
In case of problem the FAQ below may help.
If any body want to share their Wizard ROM (e.g. CHT ROM currently doesn't have upgrade program) Yet the ntrw may not 100% reliable, they can just backup their OS ROM using aWizard and then share with others using the xda-developers ftp site.
ahlok_hk
[Attention]
This utility is created for experimental purpose only. Use it at your own risk!
!!!!Please choose the unlock CID option before you flash any new ROM!!! Or your phone may risk chance to become dead!!!!
Starting from version 1.3, please put your ROM file to the "ROM" folder and BMP file in "SplashBMP" folder
Version 1.3 beta 2 is not fully tested. If you have doubt please use version 1.2
[Introduction]
aWizard is a user friendly ROM Utility which provide a single place to do Wizard ROM related tasks. OS ROM can be backup and restore using USB ActiveSync connection. In addition to backup/restore, I have successed in modifying the OS ROM and flash it back to the Wizard. This function will be available in the coming releases depends on demand.
Some user have reported that they have successfully backup and restore their Charmer(MDA Compact II) OS and Extended ROM. But again. Please make sure you know what u are doing before your write anything to the Charmer. I don't have a Charmer device to test with. So do it at ur own risk.
Other ROM Types like Bootloader, Radio and Extended ROM will not be affected. To change those parts, please use cooresponding update programs and then use aWizard to change the OS to your desired one.
[History]
1.0
- First Release
1.1
- Add Backup Extended ROM Support (Restore Extended ROM not ready yet)
- Fix size checking problem in some locale
1.1a
- remove Backup ROM Option remark issue
1.1b
- minor enhancement to prevent some user's problem in 'e' option
- add reminder to unlock before write option
1.2
- add backup and restore radio rom option
- minor ui enhancement
- revised instruction
1.3 beta 1
- add "ROM" and "SplashBMP" folder for easy file management
- add convert and flash BMP directly to Wizard as Splash Logo
- add backup and restore Splash Logo ROM
- UI enhancement
- add readme option
1.3 beta 2
- force unlockcid in every write option
[Credits]
- The utilities and idea used by aWizard come from the following parties. I would like to thanks them for making the Wizard more interesting to play with!
- itsme for 'itsutils'
- MachinaGod for 'RapiUnlocker'
- MachinaGod for 'lokiwiz'
- mamaich for 'WM5 ROM editing tool'
- psneddon and kenu for Logo Converter
- nicob for scripting tips
- xda-developers.com, buzz.net and others
[Installation]
Unzip the aWizard.zip to C:\aWizard or D:\aWizard folder.
[Usage]
Run aWizard.cmd on DOS Prompt, or just double click the file in Windows Explorer. If fail, rename to aWizard.bat before run.
* Please put ROM(Including Splash Logo ROM) in the ROM folder, and Splash BMP files(*.BMP) in SplashBMP folder.
[Options]
< a -View README file>
< e - Enable RAPI >
- Choose this before choosing other options. This enable your PC to control the Wizard using USB ActiveSync connection.
<u - Unlock CID>
- (Strongly suggested to run this first!!!) Unlock the CID of Wizard so that the Wizard can be upgrade to other ROMs
<b - Backup OS, Radio, Splash Logo and Extended ROM from device>
- This option backup your Wizard's Radio and OS, Radio ROM to a file and files in Extended ROM to a folder. It backup OS and Extended ROM and Radio ROM only. Bootloader will NOT be backup.
- All files will be backup to a single folder for easy archive and mofication using 'm' option later.
< s - Write Backup Splash Logo (.nba) to Wizard>
- Flash backuped Splash ROM to Wizard. Soft reset is required to enable new Splash Logo. No need to hard reset.
< c - Convert + write BMP(240x320) Splash Logo to Wizard>
- Flash BMP file directly to Wizard. No pre-convertion is required. Please save a 240 x 320 24-bit BMP file to "SplashBMP" folder before running this option. Soft reset is required to enable new Splash Logo. No need to hard reset.
<w - Write OS ROM to device>
- Use this option to write OS ROM file to your device. Even you have bootloader and Radio ROM from vendor A, you can flash OS ROM from vendor B to the Wizard. No SD Card is required. Unlock CID First!!!
<r - Write Radio ROM to device>
- Use this option to write Radio ROM file to your device. No SD Card is required. Unlock CID First!!! Soft reset is required to enable new Radio ROM. No need to hard reset.
<m - Modify nba file>
- To be released depends on demand
<x - Extract contents of nba file>
- To be released depends on demand
[FAQ]
Q1 : How to flash ROM file to device:
A1:
1.run option 'e'
2.run option 'u'
3.run option 'b' if u want to backup ur current ROM
4.run option 'w' or 'r'
Q2 : What to do if the device hold at splash screen after upgrade?
A2:
- connect the device with usb cable
- hold the "voice dial" and shortly press the reset button by stylus
- release the reset button and wait for the USB color screen
- download and run the shipped ROM upgrade program (with .exe file extension) e.g. ftp://xda:[email protected]/Uploads/HTC_Wizard/Roms/
- you device will be bootable again.
- then start aWizard and run through the 'e', 'u', 'w' one by one. Of coz you have to connect your phone to ActiveSync before running the 'e' option.
Q3 : I have the follow error during the read or write operation, what should I do?
Copying C:\aWizard\lib\itsutils.dll to WCE:\windows\itsuti
Could not update itsutils.dll to the current version, mayb
try restarting your device, or restart ActiveSync
A3 :
If the error occur, that means the USB connection is interrupted.
- Please DON'T reset your Wizard.
- Please re-plug the USB cable and wait for ActiveSync to reconnect.
- Run aWizard to retry the operation again.
P.S. You need to login to download the attached file.
Why only OS? You should add 'radio' too.
Button said:
Why only OS? You should add 'radio' too.
Click to expand...
Click to collapse
I am still finding way to do so... Maybe you can help finding out how. The code of aWizard may give you some hint.
But if you really want to upgrade to latest radio ROM (e.g. the T-mobile is the latest at this moment), you can download the MDA Vario Upgrade Program from T-mobile. Then restore your backuped OS ROM. Of coz the installed program have to be backup using Backup Managers first.
b - doesn't work now! You have a mistake in .bat file 'r' instead of 'b' :wink:
Button said:
b - doesn't work now! You have a mistake in .bat file 'r' instead of 'b' :wink:
Click to expand...
Click to collapse
Updated v1.0a... Thanks for remind me :wink:
Hi, ahlok, thanks for your utility! I'm just using it to backup my MDA Compact II ROM, see if it works.
negatong said:
Hi, ahlok, thanks for your utility! I'm just using it to backup my MDA Compact II ROM, see if it works.
Click to expand...
Click to collapse
You are welcome. Looking forward to your result!
ahlok_hk said:
negatong said:
Hi, ahlok, thanks for your utility! I'm just using it to backup my MDA Compact II ROM, see if it works.
Click to expand...
Click to collapse
You are welcome. Looking forward to your result!
Click to expand...
Click to collapse
ahlok, I could successfully backup the ROM. But when I just tried to write the dumped ROM (exactly the dumped file) back to the device with option 'w', it raised error: 'File [] size not valid!'. What's wrong there?
And if I downloaded an official upgrade ROM and used Extend Tool (64HTC Extended ROM Tool) to decode the '.nbf' to '.nba', can I use that decoded '.nba' file to write the another device with your utility?
negatong said:
ahlok, I could successfully backup the ROM. But when I just tried to write the dumped ROM (exactly the dumped file) back to the device with option 'w', it raised error: 'File [] size not valid!'. What's wrong there?
And if I downloaded an official upgrade ROM and used Extend Tool (64HTC Extended ROM Tool) to decode the '.nbf' to '.nba', can I use that decoded '.nba' file to write the another device with your utility?
Click to expand...
Click to collapse
Please run cmd.exe at ur PC and go to the lib folder. Then run "pdocread -t" and reply here or PM me the result. Thanks.
On my charmer I get the following output
3 partitions, 2 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 49 0b 01 01
real nr of sectors: 116736 - 57.00Mbyte (0x3900000)
ahlok_hk i would like thanq for your time and releasing this little but very helpful application.
When i return from Xmas holidays i will try it with my Qtek 9100 (English version).
But i have a little question, what is .nba files and how they've been used?
Thanks psneddon, ur result shows that Wizard and Charmer have the same OS ROM size. I think this tool should be ok for Charmer.
I have add some code enhancement to prevent error of negatong. Please use the latest version 1.0c and see if it can write the ROM back. Wait for ur good news. : )
bill_viper said:
But i have a little question, what is .nba files and how they've been used?
Click to expand...
Click to collapse
.nba files are decryted ROM. If there is demand, later I will post new version of this tool to modify the ROM easily.
Just dumped my Qtek 9100 ROM (english) with the following info:
ROM 1.6.7.1 WWE
ROM Date: 11/28/05
Radio Version: 01.13.0
Protocol 4.6.13.24
ExtROM: 1.6.7.101
and the ROM is located at:
http://www.richardgoodwin.com/Qtek_9100_1_6_7_ENG.zip
Give it about 20 minutes to upload. Like the aWizard tools, I take no responsibility, etc If this becomes a popular ROM, I hope one of the forum folks will upload it to the xda-developers FTP...
rgoodwin said:
Just dumped my Qtek 9100 ROM (english) with the following info:
ROM 1.6.7.1 WWE
ROM Date: 11/28/05
Radio Version: 01.13.0
Protocol 4.6.13.24
ExtROM: 1.6.7.101
and the ROM is located at:
http://www.richardgoodwin.com/Qtek_9100_1_6_7_ENG.zip
Give it about 20 minutes to upload. Like the aWizard tools, I take no responsibility, etc If this becomes a popular ROM, I hope one of the forum folks will upload it to the xda-developers FTP...
Click to expand...
Click to collapse
Thanks rgoodwin! I sucessfully flash ur new ROM to my Wizard! Could u also share the extended rom? You can use total commander to copy the content of "\extended_rom" out.
Only if you promise to tell me any changes you see with this ROM version, in areas like:
speed
stability
GPRS performance/stability
http://www.richardgoodwin.com/Qtek_9100_1_6_7_ENG_Extended_ROM2.zip
Doesn't seem like there's much in there!
P.S. One more request....seems like when I find an app and install it, then if I say need to replace the installed EXE with a patched version, the Qtek says it's no longer compatible or missing a component. I thought I read this might be due to digital signatures, but I'm not sure if so or how to get around it...
ahlok_hk i would like to flash my Qtek 9100 with the new rom posted by rgoodwin. If i'll use aWizard which of ROM/Radio/Protocol/ExtROM will be updated?
Thanks rgoodwin again! I just played with the new ROM without install the Extended ROM. So far it is as stable as the other ROMs.
bill_viper said:
ahlok_hk i would like to flash my Qtek 9100 with the new rom posted by rgoodwin. If i'll use aWizard which of ROM/Radio/Protocol/ExtROM will be updated?
Click to expand...
Click to collapse
Dear bill_viper, If you download the first file by rgoodwin, you will upgrade the OS ROM. Download the 2nd one and copy to \extended_rom will upgrade ExtROM.
ROM
By reading the description of this utility I don't think this ROM will have the radio firmware in it. I could be mistaken.
Thanks again for the reply ahlok_hk.
But reading your description i found this:
"<w - Write OS ROM to device>
- Use this option to write OS ROM file to your device. Even you have bootloader and Radio ROM from vendor A, you can flash OS ROM from vendor B to the Wizard. No SD Card is required. "
According to the above i think that if i'll flash my 9100 with the new rom the radio will not be upgraded. Am i right? If yes, how can i upgrade radio rom too?
It is New release of HoneyComb Froyo Builds ...
* Working :
- Everything except Camera & BT
- Downloading from market may take long time to start at first time ..
* Features :
- Very Stable & Fast & Smooth Froyo CWM build ..
- Very Fast Wifi with No Dropping ..
- Very Good battery life ..
- Neocore : 25.6 FPS
* Kernel Related issues :
- You may not hear voice during incoming call > Just activate the speaker & deactivate it again to solve this issue ..
- Charging while in android isn't working > You should connect the charger before hitting (haret.exe) ..
-----------------------------------------------------------------
* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
2- Extract Package & Copy [npkboot] Folder to root SDcard ..
3- Copy [HoneyComb Build V.3] To root SDcard without extraction ..
4- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
5- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " HoneyComb Build V.3.zip " ..
- Then return back to main menu using " ok " key , Then choose " reboot system now "
6- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see THIS TOPIC
------------------------------------
** Very Important :
* Please don't install GAPPS after rom installation directly , Otherwise you'll have a serious problems ..
So you must :
1- Install HoneyComb V.3
2- Run the build
3- Restart it
4- Install Gapps
* Attached Kernel is highly overclocked , it may not work with all kovsky devices , so if it doesn't work with you, try to change the overclocking value from 652 to 614 mhz in startup.txt ..
- If it is still not working , replace this kernel with "Turbo kernel" attached to package ...
*********************************************
* Thanks To :
- Neopeek ( For CWM & Many others )
- TiaD8 ( Many tweaks & stuff taken from his builds )
- Highlandsun ( For his libs )
- People made these themes & icons .
- All other persons who i forgot to mention ..
**********************************
DOWNLOAD
^^^^^^^^^^^^^^^^^^
* On Screen Answer interface
* For Keyboard Freezing proplem
**********************************
If you like my work, Please just Don't Mirror my links ..
Don't Forget To click Thanks Button ...
* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
2- Extract Package & Copy [npkboot] Folder to root SDcard ..
3- Copy [HenDroiD_V2.zip] To root SDcard without extraction ..
4- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
5- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " HenDroiD_V2.zip " ..
- Then return back to main menu using " ok " key , Then choose " reboot system now "
6- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see THIS TOPIC
finally.....great work man....!!! download now....
nice work !!!
needo why you delete languages from this ROM?? ( please return choose czech language in Settings )
are the Keypad drivers modules or not ?
RenEdi said:
nice work !!!
needo why you delete languages from this ROM?? ( please return choose czech language in Settings )
Click to expand...
Click to collapse
this build isn't supporting many laguages, but you can use morelocale ( Attached to this post )
djkarl said:
are the Keypad drivers modules or not ?
Click to expand...
Click to collapse
the separate keypad modules isn't included in this package , i think you wan't need it again > i'm using it for more than 8 hours with no keyboard stoppage ..
trying now
Tried it for 2 hours now. I had only one wifi connection lost. But that was the only error. Market works. It's fast and stable LOVE IT ^^
I'll give it a try asap! =)
is AZERTY keymap available ?
can someone make a video on how to Become the process we do start the haret I've done it many times k no can do let us help someone. instructions I pay close attention but nothing.
sorry my english!
tried this for a few hours and the build is quite solid and stable, but with all other android builds ive tried, the keypad freezes all the time for me. froze 3 times so far in 4 hours. guess i still cant use any android build until thats fixed in the kernels. ill try the turbo keernel tosee if its any better
i have a problem, it don't ask me: press volume down
Do you know why that is?
(Sorry for my bad English)
Gameforce said:
i have a problem, it don't ask me: press volume down
Do you know why that is?
(Sorry for my bad English)
Click to expand...
Click to collapse
When you start android and the code is displayed there is the pinguine on the top, wenn the pinguin disapear and the code begin at the top, than press vol down
wi fi
- Very Fast Wifi with No Dropping .. ---- NOT Working for me.. when i try to start wi fi my x1 reboots back in winmo
great speedy rom, very fast!!!!
neoofoox said:
When you start android and the code is displayed there is the pinguine on the top, wenn the pinguin disapear and the code begin at the top, than press vol down
Click to expand...
Click to collapse
Oke thanks,
And do you know how long i need to wait before the pinguine dissapeared???
great rom !! but if i make a call or get incoming call,,i can't found red and green button in my screen,,so i used red/green button in under screen..thank very much
Gameforce said:
Oke thanks,
And do you know how long i need to wait before the pinguine dissapeared???
Click to expand...
Click to collapse
It should apeare after 30-60sec (normaly shorter)
PsychoAssasin said:
tried this for a few hours and the build is quite solid and stable, but with all other android builds ive tried, the keypad freezes all the time for me. froze 3 times so far in 4 hours. guess i still cant use any android build until thats fixed in the kernels. ill try the turbo keernel tosee if its any better
Click to expand...
Click to collapse
you can use the kernel with separate keyboard modulus so you can activate it with one touch everytime it freazes ...
ncw2k69 said:
- Very Fast Wifi with No Dropping .. ---- NOT Working for me.. when i try to start wi fi my x1 reboots back in winmo
great speedy rom, very fast!!!!
Click to expand...
Click to collapse
i don't know the reason , but it may be winmo related or radio related , BTW try to enable wifi in Winmo & start android ...
vannanta said:
great rom !! but if i make a call or get incoming call,,i can't found red and green button in my screen,,so i used red/green button in under screen..thank very much
Click to expand...
Click to collapse
yes it was excluded , it is always getting distorted & some times doesn't work ...
neoofoox said:
It should apeare after 30-60sec (normaly shorter)
Click to expand...
Click to collapse
it depends on the SDcard contents , if there are many files & folders it'll take longer & so on ...
needo said:
it depends on the SDcard contents , if there are many files & folders it'll take longer & so on ...
Click to expand...
Click to collapse
Ah okay I didn't know. I have quite clean sdcard.
And I have one question. After Installing gapps (after launching android) everything worked fine and I never get a force close message. But after starting Android after reboot I get a lot of force close messages. (The process android.process.acore has stopped unexpectedly. Please try again.)
I use turbo kernel (this one in the turbo kernel folder @612mHz)
The included one didn't work. I pressed harret and then phone restarted (i tried both 652 and 614 mHz) Do someone know what's the problem? But that is not so urgent
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!
Pls, before u upgrade ur single-sim to dual-sim, READ THE INSTRUCTIONS!
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.
Click to expand...
Click to collapse
!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.)
-
Since i was informed about this problem i searched the web for 2 things...
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.
Click to expand...
Click to collapse
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
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
Oeminfos
Mirror: GoogleDrive
Mirror #1: My FTP
(Legend: DS = Dual-Sim | SS = Single-Sim)
Special THX goes to
@rgomesf for uploading the L31C432B130-FULL update!
@cybero2912 for sharing the...
...L31/L21-C432B151-FULL update links (HiCloud)
...L21C432B161-FULL update links (HiCloud)
@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
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
@baduncle
[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/custom.bin.bak custom.bin.bak
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?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[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.
Changelog
DD.MM.YYYY | (A) = Added | (C) = Changed | (D) = Deleted | (F) = Fixed | (R) = Recoded | (U) Updated
----------------------------------------------------------------------------------------------------------------------------------------------------
28.05.2017
The toolkit images (coming soon)
The pkg.L31C432B370.zip (added the superSu.zip)
[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
[A] Dual-Sim upgrade for L22
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
The DualSIM its my method?
BadWolfYe said:
The DualSIM its my method?
Click to expand...
Click to collapse
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
Nice work! Can't be a problem flash a dual sim firmware over a single sim device?
Zeph1990 said:
Nice work! Can't be a problem flash a dual sim firmware over a single sim device?
Click to expand...
Click to collapse
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
false in the P8 Lite no OEMFILE needed... in P8LITE with FULL FIRMWARE its good...
But in P9LITE its needed de "private OEMFILE"...
BadWolfYe said:
false in the P8 Lite no OEMFILE needed... in P8LITE with FULL FIRMWARE its good...
But in P9LITE its needed de "private OEMFILE"...
Click to expand...
Click to collapse
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
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
Miss Montage said:
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
Click to expand...
Click to collapse
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
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.
Can we use this toolkit with VNS-L21?
mqdjo said:
Can we use this toolkit with VNS-L21?
Click to expand...
Click to collapse
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
The l21 and l31 are same oeminfo i used the l21 in l31
BadWolfYe said:
The l21 and l31 are same oeminfo i used the l21 in l31
Click to expand...
Click to collapse
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
k1ll3r8e said:
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
Click to expand...
Click to collapse
I need it mostly for dual sim upgrade, thank you anyway
Sent from my HUAWEI VNS-L21 using Tapatalk
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?
mastermoon said:
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?
Click to expand...
Click to collapse
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.
Upload starts in ~45 min
Regards,
Sebastian
k1ll3r8e said:
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.
Upload starts in ~45 min
Regards,
Sebastian
Click to expand...
Click to collapse
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...
Hi all
Back Story:
Due to a frozen OS (back /home /swipe down for notifications etc.) and bazaarthings happen with the sound settings rendering my device unusable I've had to dabble with it for the first time.
Detailed device info:
MCU version:
MTCB-KGL1-V1.77
May 142014 17:49:17
Model number:
S07
S/N
000D18A154C5
Android Version
4.2.2
Kernel Version
3.0.36+
[email protected] #555
Wed May 14 03:45:57 PDT 2014
Build number
rk30sdk-eng4.2.2 20140514.19:44:15
My first fix attempt was the "restore system from backup" option from the recovery menu, but alas a missing backup image... fail one...
Also note worthy is that my menu has less options than most screen shots I've seen on youtube etc.
menu options:
>reboot system now
>update system/mcu image from /sdcard
>recovery system from backup
Failing to find the original image anywhere, I went with malask latest ROM that looked likely to work on my device ( from what I have read here a massive upgrade anyway! )
However it is not going so well:
Attempt 1:
Pop update.img + mcu.img (kgl1 1.77) on empty SD card in gps slot
result:
-- Update rkimage...
Finding update package...
=== UPDATE RKIMAGE===
Find and check firmware...
Can not found firmware image or invalid image
Installation rkimage start.
Installation rkimage aborted.
Installation mcucfg start.
Installation mcucfg aborted.
Installation mcuimg start.
Installation mcuimg success.
System will now power off.
Rebooting...
Attempt 2:
Pop update.img + mcu.img (kgl1 1.77) on empty SDcard in media slot
result: same as Attempt 1
Attempt 3:
Pop update.img + mcu.img (kgl1 1.77) on empty usbStick
> it does not see the USB drive in the recovery screen
> ( but does once system reboots to it's slightly frozen and broken OS )
Attempt 4:
The rock chip Android Flash tool
> my windows PC does not see the unit ( I expect for same reason that unit does not see USB until it boots into the home screen
> the Rock chip driver installer tool claims to have installed the drivers correctly
Attempt 5:
getting desperate...
5.1.1 update.img for mtcb (low res / "_p") found off this forum / mega
result: same as Attempt 1
I am now officially stuck, ideas anyone?:eek
Am missing something?
Maybe links to different ROM to try on sd card?
Any help greatly appreciated !
While2>1Confused said:
Hi all
Detailed device info:
MCU version:
MTCB-KGL1-V1.77
May 142014 17:49:17
Model number:
S07
S/N
000D18A154C5
Android Version
4.2.2
Kernel Version
3.0.36+
[email protected] #555
Wed May 14 03:45:57 PDT 2014
Build number
rk30sdk-eng4.2.2 20140514.19:44:15
Click to expand...
Click to collapse
Are you certain this is a 3188 device? possibly a 3066.
And you don't need to flash mcu each time. Id stay clear of mcu. It may be the problem.
I think I got the rk3188 bit off of the original advert 2 years ago...
I will go hunting rk3066 firmwares and give them a go
Thank you for replying with the pointers
Thank you! It was a rk3066
Now successfully on standard Kit Kat
Crazy sound seams fixed by OS update!
However, still no touch response along the Android bar so can't use home / back / swipe down for notifications
For now will install a " button saver " app
Probably will end up installing a custom ROM and read up on peoples hardware button remapping attempts