The official 172601 ROM for Qtek is out, get it here:
ftp://xda:[email protected]/Qtek172601
(Hope it's ok that I upped it here :? )
Edit: Looks like the ROM contains Norwegian settings etc.. but you could easily edit the ROM using er2003edit, password is 0x20040305
Late...
Editing new ROM
Hi, I have been editing the new ROM from Norway and I found a file that is not usual.
Anyone knows what is provis.cpf and load_provis_cpf.exe?
Thanks for your help
Only the extended ROM differs w.r.t. the iMate 1.72 ROM
ms_.nbf (extended ROM)
Password: 0x20040305
Operator: Qtek (country code)
Language: WWE (english)
Version: 1.72.601
Checksum: 0x3138393534336639
Files:
Code:
03/01/2004 12:10 46,798 3_networkname.CAB
03/01/2004 12:10 7,680 AutoRun.exe
03/01/2004 12:10 172,176 BizMobile.cab
03/01/2004 12:10 46,763 Broadcast_WWE.sa.CAB
03/01/2004 12:10 908,198 CallerIDB31_Hima2_WWE.CAB
03/01/2004 12:11 2,789,548 CameraRC132_WWE_1.5.sa.CAB
03/01/2004 12:10 648 Config.txt
03/01/2004 12:11 13,420 itibm.ARM.CAB
03/01/2004 12:10 4,096 Load_Provis_cpf.exe
03/01/2004 12:11 114,901 MIDI56.sa.CAB
03/01/2004 12:12 1,345,025 MMS1.6.0.14WWE.CAB
03/01/2004 12:12 148,321 Norsk_Dansk_PPC_Tastatur.CAB
03/01/2004 12:12 601,773 Norway.sa.CAB
03/01/2004 12:12 47,014 Norway172_Customize.sa.CAB
03/01/2004 12:12 382,019 OEM_WWE_04051001.sa.CAB
03/01/2004 12:10 222 provis.cpf
03/01/2004 12:10 4,608 TPDisable.exe
03/01/2004 12:10 4,608 TPEnable.exe
06/29/2004 16:21 46,754 Version_AKU2_172.sa.CAB
splash images: "Qtek/keep the world in one" blue sky w/ clouds
Identical files w.r.t iMate 1.72 ext ROM (binary file compare):
3_networkname.CAB, Broadcast_WWE.sa.CAB, CallerIDB31_Hima2_WWE.CAB, CameraRC132_WWE_1.5.sa.CAB, MIDI56.sa.CAB, MMS1.6.0.14WWE.CAB, OEM_WWE_04051001.sa.CAB
Version_AKU2_172.sa.CAB, config.txt (obviously): minor differences.
Not in iMate ROM:
BizMobile.cab
itibm.ARM.CAB
Load_Provis_cpf.exe
Norsk_Dansk_PPC_Tastatur.CAB
Norway.sa.CAB
Norway172_Customize.sa.CAB
provis.cpf
You will find these files attached in Qtek172FilesNotInImate.zip so you don't have to download the entire ROM to experiment with these.
NK.nbf (OS ROM)
Password: 0x20040304
Operator: Qtek (country code)
Language: WWE (english)
Version: 1.72.00
Checksum: 0x3464366438653234
same checksum as the 1.72 iMate ROM
Radio_.nbf (Radio ROM)
Password:0x20040306
Operator: Qtek (country code)
Language: WWE (english)
Version: 1.14.00
Checksum: 0x6231343161636634
same checksum as the 1.72 iMate ROM
The only differences appear to be in the operator/country code, and in the Extended ROM. (Note: You do NOT need to flash to add/remove/edit files in the extended ROM area).
More info on flashing/upgrading
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
http://forum.xda-developers.com/viewtopic.php?t=1624[/code]
HTH HAND
Re: config.txt differences, provis.cpf
Config.txt contains
Code:
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\Broadcast_WWE.sa.CAB
CAB: \Extended_ROM\CallerIDB31_Hima2_WWE.CAB
CAB: \Extended_ROM\CameraRC132_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MIDI56.sa.CAB
CAB: \Extended_ROM\MMS1.6.0.14WWE.CAB
CAB: \Extended_ROM\OEM_WWE_04051001.sa.CAB
CAB: \Extended_ROM\3_networkname.CAB
CAB: \Extended_ROM\Version_AKU2_172.sa.CAB
CAB: \Extended_ROM\BizMobile.cab
CAB: \Extended_ROM\Norway172_Customize.sa.CAB
CAB: \Extended_ROM\itibm.ARM.CAB
CAB: \Extended_ROM\Norsk_Dansk_PPC_Tastatur.CAB
CAB: \Extended_ROM\Norway.sa.CAB
EXEC:\Extended_ROM\Load_Provis_cpf.exe
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset
Presumably, Load_Provis_cpf knows how to handle the data in provis.cpf, which is one XML file called _setup.xml
Code:
<wap-provisioningdoc>
<characteristic type="SecurityPolicy">
<parm name="4107" value="3220" />
</characteristic>
</wap-provisioningdoc>
The 4107 paramater is apparently the parameter for "WAP Signed Message Policy: PPG_AUTH | PPG_TRUSTED | OPERATOR_TPS | OPERATOR"
http://msdn.microsoft.com/library/d...m/amo_pocket_pc_security_policy_xml__kqra.asp
The value is 3220, or 2048 + 1024 + 128 + 16 + 4
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sp_amo/html/consecurityroles.asp
This apparently enables WAP push and over-the-air PROVISioning of WAP settings. (I wonder if that is in any way supported by any network operator).
itibm appears to be a battery monitor of some sort.
BizMobile appears to be an application that adds information about Norwegian businesses to your contacts (and callerID) via the BizWeb.no website.
http://www.windowsmobile.no/modules.php?name=News&file=article&sid=26
translate at http://www.tranexp.com:2000/InterTran/
popsi said:
Edit: Looks like the ROM contains Norwegian settings etc.. but you could easily edit the ROM using er2003edit, password is 0x20040305
Click to expand...
Click to collapse
How do I open the Extended ROM?? :? Do I have to install first or..
The downloaded install file RUU172601WWe.exe cant be opened..
Could you explain me about the file in Q-tek that are not i-mate?
each one is used for??
i have never haven experience about Q-tek ROM.
what about "Biz mobile","itibm"?
thank a lot
tumtum said:
Could you explain me about the file in Q-tek that are not i-mate?
each one is used for??
i have never haven experience about Q-tek ROM.
what about "Biz mobile","itibm"?
thank a lot
Click to expand...
Click to collapse
Since I'm norwegian I installed the rom as is. Here is what I believe the changes are
BizMobile.cab
Is a software that works like 411 in the US. Is a gprs based service that let you search for people, firms and their phonenumbers etc.
itibm.ARM.CAB
It's a plain and simple battery monitor. Useless if you use a software such as batterypack
Norsk_Dansk_PPC_Tastatur.CAB
Installs a Norwegian/Danish keyboard.
Norway.sa.CAB
Norway172_Customize.sa.CAB
provis.cpf
Load_Provis_cpf.exe
Believe all these files does customizations. After installation and reboot the splashimage was chaged, and also the startpage in IE had different links than the original roms. That's about all the changes I've found. Maby someone here can explain these better...
And to all:
Thanks for a great forum.
:wink:
Installed 172 ROM. Keyboard layout is Danish, how to change?
I just installed ROM 1.72. I did not do any editing before installing. Everything went fine exept the keyboard layout :? . It is now Danish and before I had US. Is there any way to change it back to US. For now I can live with it, but if possible......
Arjan
You just need to remove program through "settings->systen -> Remove programs -> ePocket Solutions ASA Norsk_Dansk..."
kind regards - Jannick Fogh-Nielsen
--------------------------------------------------------------------
Jeg spiser både skovsneglen og puden
--------------------------------------------------------------------
Re: Remove epocket Solutions ASA Norsk_Dansk
Thank for your reply.
I tried that but the program cannot be removed because there is a dll in use "\windows\imsnord.dll"
I have no programs running. How can I deal with this dll?
Re: Remove epocket Solutions ASA Norsk_Dansk
AHSB said:
I tried that but the program cannot be removed because there is a dll in use "\windows\imsnord.dll"
I have no programs running. How can I deal with this dll?
Click to expand...
Click to collapse
Switch to an input method other than the keyboard (such as block recognizer). Soft reset. Remove the program. That should work, since the keyboard will not have been started, and its DLLs should not have been loaded.
I am thinking of upgrading from T-Mobile rom 1.60.00WWE to rom 1.72.
Main motive: Bluetooth improvements
Since the OS and Radio ROMS of both iMate and Qtek are the same, one can conclude the quality must be ok (well, at leats two companys say its OK).
For the extended rom maybe it is a better idea to just re-use the old one (1.60.36) I am currently using, thus making sure all (T-Mobile) customisations are just like I have them now, instead of using the iMate of Qtek extended rom?
Can anyone confirm that will be a wise idea?
Hi!
I just upgraded to the new ROM. Everything went fine during the upgrade (no errors, no ID codes, perfect!)
I found the keyboard to be a bit unusual, but can live with it.
I tried to remove the .dll, file, with no success.
Any other idea?
:?:
Re:
Could have figured that out myself
But I was impatient so I deleted te dll myself using BT. After that I was able to delete the program without the error, however I now do not have any keyboard at all en most of my programs don't start anymore.
Unfortunally I also cannot connect my PDA using BT and at the moment I do not have a USB cradle at hand. I managed to copy the dll back to the device using IR, but since my programs do not start (like fileexplorer) I cannot put it in the right folder (windows).
I will have to try to replace the dll tonight and I hope this will do it. At least I kept a copy of the dll on my laptop.
If that doesn't work I will reinstall the ROM 172 or does anyone have a suggestion?
Found another ROM avaliable for the Norwegian market. This one should not be as customized as the other one.
It's avaliable here:
http://www.idedata.no/programmer/qtek2020_172ID.zip
2 programs added to EXT ROM
1: Norwegian Keyboard (Should be no problem uninstalling)
2: BT Tools (The bluetooth tools we all love... )
Did not try it yet...
ANYBODY knows how to edit the extended ROM with er2003edit ?? :shock: Should the file be extracted from the .EXE setup file in some way??
Do not delete imsnord.dll
I did that and I had to hard reset my device in order to get in working again. Most apps stopped working when I deleted imsnord.dll.
So now I cannot change the keyboard layout and I saw that imate has an 172 ROM update to. I guess this one is english, including the keyboard so my question is:
does anyone have this rom (and tried it?)
Arjan
GeirFrimann said:
ANYBODY knows how to edit the extended ROM with er2003edit ?? :shock: Should the file be extracted from the .EXE setup file in some way??
Click to expand...
Click to collapse
Just unpack the .exe file with Winrar/Winzip so you get to the files. The one you want to edit is the ms_.nbf which is the ext rom. Use this password: 0x20040305
GeirFrimann said:
ANYBODY knows how to edit the extended ROM with er2003edit ?? :shock: Should the file be extracted from the .EXE setup file in some way??
Click to expand...
Click to collapse
I have not edited the extended ROM the old fashened way (er2003edit) since Itsme introduced this great tool http://forum.xda-developers.com/viewforum.php?f=10
After I flash a new ROM, the first thing I do is unhide/unlock the extended ROM, delete and add the required files with a file explorer and lock it again, followed by a new hard reset. This tool also allows you to e.g. store critical backups/settings in the extended ROM (even with sub-directories, which er2003edit cannot).
Ronald
popsi said:
GeirFrimann said:
ANYBODY knows how to edit the extended ROM with er2003edit ?? :shock: Should the file be extracted from the .EXE setup file in some way??
Click to expand...
Click to collapse
Just unpack the .exe file with Winrar/Winzip so you get to the files. The one you want to edit is the ms_.nbf which is the ext rom. Use this password: 0x20040305
Click to expand...
Click to collapse
Thanks alot for your help!
Related
Hi,
now that we have a very nice tool to edit the contents of the extended-ROM file before upgrading the device I am trying to figure out which CABs to leave in the ext.-ROM and which better to install later.
Perhaps someone could help me out with what the following CAB-files exactly install (It is the original, german T-Mobile ROM-Update) and if I can safely remove them or bette keep them:
CAB: \Extended_ROM\TMD_DE.sa.CAB
CAB: \Extended_ROM\TMCOMREG.sa.CAB
CAB: \Extended_ROM\MIDI56.sa.CAB
CAB: \Extended_ROM\CameraRC131_GER_1.5.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_GER_1.5.sa.CAB
CAB: \Extended_ROM\MMS1504_GER.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_GER.sa.CAB
CAB: \Extended_ROM\ClearVue_GER.sa.CAB
CAB: \Extended_ROM\TMD_AP_DE.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_GER.sa.CAB
CAB: \Extended_ROM\OEM_GER_03120301.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\Broadcast_GER.sa.CAB
CAB: \Extended_ROM\t-mobile_shortcuts_only_DE_PPC2002_ARM.CAB
CAB: \Extended_ROM\TMDDECustomize.sa.CAB
Thx ind advance
DLSkyNet
Hi,
could you post the ms_.nbf file here, I would like to compare the settings to those of T-Mobile NL, Qtek and O2.
What I found so far (all names refer to the T-Mobile NL ROM):
Broadcast_WWE.sa.CAB:
Seems to only set the CellBroadcast setting to enabled or disabled. (I guess this refers to the Reception of News via SMS by selecting channels of interested. Quite expensive I think and only interesting for phones that do not have any other capabilities of receiving and displaying information).
T-Mobile NL sets it on, with O2 it's switched off.
CallerIDRC11_WWE_1.5.sa.CAB:
Installs the CallerID application from IA Style and the Photo Contacts extension. There are other programs that are able to provide this functionality but I use it.
CameraRC131_WWE_1.5.sa.CAB:
The camera application for taking pictures and recording videos. AFAIK there is currently no alternative to this one, you should leave it in your ROM.
GPRSMonitor_WWE.sa.CAB:
Includes the GPRS Monitor from SPB Soft. Very useful I would recommend it unless you aren't going to use GPRS anyway.
MIDI56.sa.CAB:
RingTone plugin player. Allow you to play back RingTones in the following formats: mid,3gp,mp4. Also seems to register the audio/midi MIME type for playback of midi files directly from Internet Explorer.
By default the xda can play back only wav and wma audio files (AFAIK)
MMS1507_WWE.sa.CAB:
Installs the Arcsoft MMS application for composing and sending MMS messages.
VideoMMS.sa.CAB (not contained in Qtek):
Installs the "Video MMS.exe" file into the Windows folder. When you start it you are in camera mode immediately and after you have recorded a picture or video you get into MMS composition mode.
This seems to be just an easier way to compose MMS messages since the main MMS Application (see above) is already able to compose MMS messages.
OEM_AKU1_WWE_4AP.sa.CAB (named OEM_4AP_WWE.CAB in Qtek ROM)
Installs the following files: GPRSAuthentication.exe, BTSetting.exe, STK.exe and WModem.exe
I am not sure if these are customized versions or if the normal ROM doesn't contain them. Well perhaps not because these are specific to the Phone edition so they can't be present in the main ROM, maybe they are contained in the Radio ROM, but probably they are only contained here, meaning you shouldn't remove this cab file.
OEM_WWE_03120301.sa.CAB (named OEM_WWE_03122301.sa.CAB in Qtek ROM)
Installs files for Bluetooth: AudioGW.dll, BthASPlugIn.dll, rilgsm.dll, Serial3.dll and Wavedev.dll. Also contains the new feature of mapping a (dynamic) serial port for BT.
I think you should not remove it.
TM_phone_class10.CAB (not contained in Qtek):
Installs several registry settings regarding phone functionality. (See my other post regarding this topic: http://forum.xda-developers.com/viewtopic.php?t=5539)
TMCOMREG.sa.CAB (not contained in Qtek):
Contains some of the settings contained in the previous one anyway. I'm not sure if it does anything else but I don't think so.
TMD_AP_NL.sa.CAB (not contained in Qtek):
Implements several settings specific to T-Mobile (NL): Restricts video types for MMS. Adds connection and gateway settings for MMS connection via T-Mobile NL. Adds a T-Mobile profile to GPRS Monitor.
I would not install this cab unless you live in NL!
TMD_NL.sa.CAB (not contained in Qtek):
Sets the HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3rdversion\MSYSTEM1 value to the provider name.
Not required!
TMDNLCustomize.sa.CAB (not contained in Qtek):
Adjusts all the "theming" stuff: Changes colors, installs Today-theme, installs T-Mobile Dialpad, sets T-Mobile ringtone.
If you don't like you xda2 look like a pink pig you should leave this out.
(You can extract single items from the cab file if you like)
t-mobile_shortcuts_only(UK).PPC2002_ARM.CAB (not contained in Qtek):
Contains some strange things that seem to me rather useless: "WebDisplayText t-zones", "T-Mobile Resetter.exe", "T-Mobile PIE Launcher.exe", "TMobileWebToday.dll", "T-Mobile Homepage Plugin".
I wouldn't install this one!
Version_AKU1.sa.CAB (Version_AKU1_160.sa.CAB in Qtek):
Seems to only set the version number of the extended ROM in the registry.
Any comments are welcome...
softworkz
Hi Softworkz,
I hope to manage the upload-functionality - it is the original and unmodified ms_.nbf of the German T-Mobile 1.60.07 ROM-Update
I did a hardreset yesterday and softreseted the MDA II before customization started. Afterwards I manually installed only the following aplications:
CAB: \Extended_ROM\MIDI56.sa.CAB
CAB: \Extended_ROM\CameraRC131_GER_1.5.sa.CAB
CAB: \Extended_ROM\MMS1504_GER.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_GER.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_GER.sa.CAB
CAB: \Extended_ROM\OEM_GER_03120301.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\Broadcast_GER.sa.CAB
The whole re-installation is now finished and I am happy to have gained approx. 2,5 hours of batterylife!
Greetings
DLSkyNet
Hi,
and thanks for the ROM. I will have a closer look at it during the next few days!
You are welcome softworkz - thanks for your great tool!
DLSkyNet
The whole re-installation is now finished and I am happy to have gained approx. 2,5 hours of batterylife!
Greetings
DLSkyNet
How does removing files/programs affect battery life?
Hi cruisin-thru,
just take IA-Caller as a very good example. IA-Caller is (only) responsible for displaying pictures or photos for incoming phonecalls. To achieve this it has to run in the background all the time. And as far as I know it is not programmed that "well-behaving" (battery-saving) as it should or could be.
I do not need those pictures for incoming calls (name and/or number are still displayed) so I decided not to install IA-Caller. And there seem to be many more tools like IA-Caller, not necessary but battery-wasting...
DLSkyNet
Can anyone confirm some of the CAB files in the O2 EXT ROM?
I've pasted the list here and tried my hand in discribing some based on the posts on this thread.
My assumptions here are merely guesses, so we pretty much need a confirmation form people like softworks or itsme.
Feel free to correct any mistakes/misunderstandings so I can edit my post immediately to reflect the correct information.
---------------
Somewhat familiar CABS in O2 EXT ROM
xmailinstaller2003.PPC_ARM_2003.CAB (3rd party email app?)
Broadcast_WWE.sa.CAB (already listed above)
MIDI.sa.CAB (already listed above as MIDI56.sa.CAB)
CallerID_WWE.sa.CAB (already listed above as CallerIDRC11_WWE_1.5.sa.CAB)
MMS_WWE.sa.CAB (already listed above as MMS1507_WWE.sa.CAB)
Camera_WWE.sa.CAB (already listed above as CameraRC131_WWE_1.5.sa.CAB)
ClearVue_WWE.sa.CAB (3rd party doc viewer)
o2ActiveUI.CAB (O2 ActiveUI Today plugin?)
O2UKCustomize.sa.CAB (listed above as TMDNLCustomize.sa.CAB)
Version.sa.CAB (listed above as Version_AKU1.sa.CAB)
O2_AP_UK.sa.CAB (listed above as TMD_AP_NL.sa.CAB)
Questionable CABS in O2 EXT ROM
OEM_WWE.sa.CAB (listed above i guess as the OEM cabs, but in O2 there's only one and in the post above there are 2 OEM_AKU1_WWE_4AP.sa.CAB / OEM_WWE_03120301.sa.CAB)
temp.sa.CAB
msmsgs8.CAB
CABS Not included in O2 EXT ROM:
VideoMMS.sa.CAB
GPRSMonitor_WWE.sa.CAB (wonder why it's not included in ALL types of handhelds, or maybe they just renamed the cab)
TM_phone_class10.CAB
TMCOMREG.sa.CAB
TMD_NL.sa.CAB
WIth regards to the cabs not included I wonder if it's possible to plug some of them in the O2 (such as the VideoMMS.sa.CAB, as it seems pretty nifty)
---------------
Also checked the config.exe and want to clarify commands based on the few lines at the end of the Config.txt
CAB: \Extended_ROM\xmailInstaller2003.PPC_ARM_2003.CAB
CPY1:\Extended_ROM\o2ActiveUI.CAB
CPY2:\Windows\V2R\setup\o2ActiveUI.CAB
CPY1:\Extended_ROM\o2ActiveUI_Eng_Setup.exe
CPY2:\Windows\V2R\o2ActiveUI_Eng_Setup.exe
EXEC:\Windows\V2R\o2ActiveUI_Eng_Setup.exe
So I'm assuming that the line containing:
"CAB:" installs the cab to whatever default installation path.
"CPY1:" and "CPY2:" are your verbose copy commands, the latter being the destination
EXEC: obviously is an execute command.
If my assumptions are correct then it's possible to put whatever kind of file in the EXT rom (e.g. Themes) and use the CPY commands to put them in the directory for the handheld to recognize them right?
Finally the update for imate is available!!!!!!!
you can download from
http://www.cddnet.com/Support/ruu166131wwe_cdl_sku1.zip
Somebody can post a utility to upgrade from the last O2 to this upgrade????
thank you in advance!!!!!!!
Can u confirm that the upgrade contains new ROM with WM2003SE?
Please check, because there has already been some discussion before...
Thanks
bobopopo
here's the util you need:
http://wiki.xda-developers.com/wiki/ER2003Edit
well ...it seems pwds are changed! :shock:
mdkia said:
well ...it seems pwds are changed! :shock:
Click to expand...
Click to collapse
Use the following:
NK.nbf - 0x20040304
ms_.nbf -0x20040305
radio_.nbf - 0x20040306
xda2nbftool -x NK.nbf nk.nba 0x20040304
xda2nbftool -x ms_.nbf ms_.nba 0x20040305
xda2nbftool -x radio_.nbf radio_.nba 0x20040306
the setup procedure of the extended rom has changed a bit.
now autorun.exe will create the config.txt in \windows, from the available
.cab files. and then call setup.exe to process it.
MattM - itsme >
thanks :wink:
it isnt WM2003 SE...
I just finished to upgrade to 1.66 imate rom.
1.66 rom isn't WM2003 SE and cleartype font look uglier....
Somebody can confirm that???
Now the extended rom can't be modified with ERedit2003.
Sombody figured out how to make your own extended rom?
[update]
Im now trying to delete the cab files i don't use, and rename some cab files that i do use to that name and put them in the extended rom...
And guess what it works for now. .
[/update]
mdkia - no problem
ilvanni - confirming that it's not Second Edition, and yes - cleartype does look uglier.
Also concerned about battery life.
HTH
This is a very unpolished ROM in comparison to the O2 ROM - Bluetooth Serial Port Profile for GPS is not working for me either with the native ROM or with Pocket Bluetooth tools. Battery life seems terrible, and Bluetooth headset is nowhere near as smooth (although it is improved).
I find it very hard to recommend updating to this ROM.
Wassup All,
Is this a Second Edition? (note the minor version number - 167)
http://www.cddnet.com/Support/RUU166167WWE_CDL-SKU2.zip
Waiting for your reply!
ps: I know this is an Arabic version!!!
Last time when I was upgrading my I-Mate, the difference between Arabic and English versions was only in sku1 and sku2.
And now, do you people think they changed minor version just to show the Arabization incorporation to ExtRom?
For those who download Arabic version: Please, provide us some device info (rom, radio and ext, ppc) after this (167) upgrade. Thanks in advance!
It is Arabic Language version !
HTC said:
Wassup All,
Is this a Second Edition? (note the minor version number - 167)
http://www.cddnet.com/Support/RUU166167WWE_CDL-SKU2.zip
Waiting for your reply!
ps: I know this is an Arabic version!!!
Last time when I was upgrading my I-Mate, the difference between Arabic and English versions was only in sku1 and sku2.
And now, do you people think they changed minor version just to show the Arabization incorporation to ExtRom?
For those who download Arabic version: Please, provide us some device info (rom, radio and ext, ppc) after this (167) upgrade. Thanks in advance!
Click to expand...
Click to collapse
I am Arabic speaking so I downloaded and installed the Arabic version, but you will find two versions on www.clubimate.com site; one for English and the other for Arabic.
English version = ruu166131wwe_cdl_sku1.exe
Arabic version = RUU166167WWE_CDL-SKU2.exe
Hope this helps!
Delusion!
BIG BIG delusion..i expected Windows 2003 Se in v 1.66 upgrade rom!!
and ..there isn't!!
So,please tell me how do I modify the O2 upgrade for my i-mate,couse i receive country id error..
http://forum.xda-developers.com/viewtopic.php?t=7278
Password Error
I'm getting an error while trying to Customize the Extended ROM (ms_.nbf), see attached file... Help needed please...
Re: Password Error
alkandery75 said:
I'm getting an error while trying to Customize the Extended ROM (ms_.nbf), see attached file... Help needed please...
Click to expand...
Click to collapse
pwds:
NK.nbf - 0x20040304
ms_.nbf -0x20040305
radio_.nbf - 0x20040306
Thanx! ..but I simply passed the country id error in this mode:
I downloaded the upgrade v1.03 (that it seems to be the base for all XDA2,MDA2,I-Mate,Q-Tek..) so after that I upgraded to latest Rom from O2 wothout problem! ;P
Good luck for all u !! lol
I cant seem to be able edit or extract the cab files from the extended rom using ERedit2003 even after decoding it with
xda2nbftool -x ms_.nbf ms_.nba 0x20040305
can anyone help.
thanks.
I've jest received from CE Communication service (O2 and T-Mobile official repair center) my MDAII and it has a new ROM:
ROM-Vers. 1.72.01GER
ROM-Date: 03/16/04
Radio-Vers. 1.17
Prot. vers. 1337.28
ExtROM-Vers. 1.72.170
Only improvement is the new Radio, and no trufax in the ExtRom.
Ciao.
are you sure that 1.72 is your radio version? ( and you didn't mix it up with your os version ? )
latest I've seen is 1.14.
Yes I did mix it up with os version, the new radio v. is 1.17
Thanks to notice me the mistake!
Gibbo said:
I've jest received from CE Communication service (O2 and T-Mobile official repair center) my MDAII and it has a new ROM:
ROM-Vers. 1.72.01GER
ROM-Date: 03/16/04
Radio-Vers. 1.17
Prot. vers. 1337.28
ExtROM-Vers. 1.72.170
Only improvement is the new Radio, and no trufax in the ExtRom.
Ciao.
Click to expand...
Click to collapse
hihi..
will u b kind enough to post the ftp for us to download?
cheers
j0shua
How to do!? that's my problem.
I'm Windows habits and I'm lost with command line!
Ciao.
Hi
Where i can get this new Radio Version?
Tnx Steve
I wrote a description howto make a copy of the radio rom here:
http://wiki.xda-developers.com/wiki/HimalayaHowtoCopyRom
hope you understand it. if not, tell me. I may create a simple tool for you to just copy the rom using only your xda.
Radio 1.17 sdradio.img
Have I done it well ?
My question now is how to do the reverse, how to write it back.
I've tried:
psdwrite -3 0 0x03400000 sdradio.img
also: psdwrite sdradio.img
but without "effects"
It has been a my pleasure!
Ciao.
itsme, you are always very helpful!
Setup radio ver.1.17
Thank Gibbo for uploaded file!
I try to install Radio 1.17 sdradio.img in my XDA II anyway but no success
Any idea?
:?:
Re: Setup radio ver.1.17
I've successfully installed 1.17. I've made a Radio_.nbf file so you can use it in normal upgrade process, it is attached.
Use this file at your own risk, backup your ROM to SD before installing!!!
Re: Setup radio ver.1.17
mamaich said:
I've successfully installed 1.17. I've made a Radio_.nbf file so you can use it in normal upgrade process, it is attached.
Use this file at your own risk, backup your ROM to SD before installing!!!
Click to expand...
Click to collapse
Any comparisons to 1.14.00 stack Bro?
Re: Setup radio ver.1.17
[Krueger said:
Dr.Stein]Any comparisons to 1.14.00 stack Bro?
Click to expand...
Click to collapse
I have not found any differences. It has the same problems with data calls like 1.14
Re: Setup radio ver.1.17
mamaich said:
I have not found any differences. It has the same problems with data calls like 1.14
Click to expand...
Click to collapse
Alrighty Bro thanks for the prompt reply.
Guess I will wait until my Xda II's next hard reset or a newer O2 ROM or WM2003SE - whichever comes first.
thanks gibbo for the rom, andthanks to mamaich for posting the nbf.
for those interested, this is how to convert the sd-image to an nbf:
- extract the raw-image from the sd-image
Code:
perl sdtool.pl -ri sdradio.img -wm bin
this will write a file named bin-60000000.nb
- create an empty file of exactly 1 Mbyte:
Code:
dd if=/dev/null of=1m.bin bs=1M seek=1
- create a file of exactly 64 bytes, containing only dashes, by first typing 64 dashes into a file, and then truncating the CRLF at the end with:
Code:
dd if=/dev/null of=64.bin bs=64 seek=1
- then concatenate all together with:
Code:
copy /b 64.bin + bin-60000000.nb + 1m.bin radio_.nba
- then set the header parameters with:
Code:
xda2nbftool -sd PH10 -so Qtek -sl WWE -sv 1.17.00 radio_.nba
- then encrypt it for the upgrade tool with:
Code:
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
- dd can be found in cygwin
- sdtool is part of the xda-developers romtools and can be found here
- xda2nbftool can be found here.
extract the raw-image
itsme you're unsurpassable one!
Good news, a new MDAIII is comming to me, but would it be possible do the same as with XDAII/MDAII (extract the image from the device, etc.)?
My be is a stupid question, inasmuch as we still do not have it!
Extended Rom 1.72.170
Could someone please upload the new extended rom 1.72.170 German, too.
thx a lot!
itsme said:
I wrote a description howto make a copy of the radio rom here:
http://wiki.xda-developers.com/wiki/HimalayaHowtoCopyRom
hope you understand it. if not, tell me. I may create a simple tool for you to just copy the rom using only your xda.
Click to expand...
Click to collapse
Itsme, you are unbelievable!!! :mrgreen:
That tool will be great!
Could you please post the content of ExtROM too?
Thanks.
Thanks Gibbo & mamaich
Radio v.1.17 in my device now
Sorry guys,
I havent it any more, jest overwrite it, but nothing more from previus or less of T-M ROM 1.72ENG_beta.
I have only a sd.img but I'm no shore if I done it well and I havent it with me now.
Tomorow I'll see if it's good and I would post it.
This is the procedure to convert the dumped ROM into NBH "flashable" file. I take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from wiki.
Well, i manage to reconstruct the spanish dumped rom from my Raphael. This thread is about how to reconstruct a dumped Raphael ROM, to have the original ROM that cames with your Kaiser, so you can revert to origin.
This is only the process to get back the original OS for your device, neither the SPL nor the radio ROM.
1. First of all is to Dump the ROM from your device.
Here are the proces (thanks to RezzZ)...
HTC Touch Pro DUMP:
Open a reg editor (dooFred TaskManager, TotalCommander or PHM Registry...) on your Touch Pro
Change:
HKLM\Security\Policies\Policies
valuename '00001001'was set to dword:2, change it to dword:1
After this change you need to soft reset your device.
Download itsutilsbin (http://www.xs4all.nl/~itsme/projects/xda/tools.html)
Extract the zip file and copy itsutils.dll to \windows on the Touch Pro (don't do it using ActiveSync, instead copy the file first to SD, and using TotalCommander or Resco Explorer copy from SD to \Windows).
Run (copy paste):
“pdocread.exe -l” (it’s the letter L not a 1)
you get something like:
Code:
457.75M (0x1c9c0000) DSK1:
| 3.12M (0x31f000) Part00
| 4.50M (0x480000) Part01
| 126.50M (0x7e80000) Part02
| 323.63M (0x143a0000) Part03
7.61G (0x1e6e80000) DSK7:
| 7.60G (0x1e6a80000) Part00
.....
Now run:
“pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x31f000 Part00.raw”
“pdocread -w -d DSK1: -b 0x800 -p Part01 0 0x480000 Part01.raw”
“pdocread -w -d DSK1: -b 0x800 -p Part02 0 0x7e80000 Part02.raw”
“pdocread -w -d DSK1: -b 0x800 -p Part03 0 0x143a0000 Part03.raw”
notice the part before Part0X.raw is the same as you got with pdocread.exe –l, same for the name of the disk.
dumping part02 and 03 wil take some time. be patient.
After dumping the ROM you'll have 4 RAW files. Move in one folder the Part01.raw that contains the XIP and Part02.RAW that contains the IMGFS, both needed for the reconstruction process.
2. Download the WWE BaseROM to use in the reconstruction process here http://rapidshare.com/files/138980371/RUU_Raphael_HTC_WWE_1.90.405.1_Radio_Signed_Raphael_CRC_52.33.25.17_1.02.25.19_Ship.exe
3. Download the Raphael Kitchen v0.62 here, that allows to reconstruct the ROM from the dump. The Raphael Kitchen allows to cook a ROM from a dumped one and from base NBH shipped one. You need to put the NBH file from the step before in the BaseROM folder (the Shipped ROM is a huge EXE file, and you'll need WinRAR to extract the content), and put the RAW files too.
Then execute the RAPHAELKITCHEN.CMD and choose the next options from the menu it this order:
e, b (for dumped ROM),space key, c, a, press BuildOS Play icon and wait to finish, Close BuildOS, close PagePool Changer and press space to go back to main mene. As a result of this process you will have a RUU_Signed.NBH file you can flash on to your Touch Pro to go back using the F option from main menu.
Thanks to JugglerLKR for help me and the knowledge to solve the issues into reconstructed ROMs, and Alex to make a better script, and of course all the ppl make wonderfull apps that make this possible...
Cheers.
Reconstructed ROMs
List of Reconstructed ROMs
HTC SVE 1.90 Part1 and Part2 * note the RAR is a multipart file (many thanks to easycure1974 for this one)
HTC FRE 1.90.406.5 (many thanks to geek78 for this one)
HTC ESN 1.90 (recompiled light and tested by me )
HTC ITA 1.90
O2 German1.90.407.4 (many thanks to chrisge)
HTC WWE 1..90.871.3 (thanks to ruffruff)
Vodafone UK 1.90.161.5 (thanks to annonymouse)
HTC CHT 1.90.709.5
HTC GER 1.90.407.4
HTC WWE 1.90.401.1 Multilanguaje (include Czech, Slovak, Polish, Hungarian and Romanian)
HTC WWE 1.90.707.4 Asia (Thanks try for the dump)
TMobile Austria 1.69.112.6 (Thanks licht77 for the dump)
Vodafone ITA 1.90.165.5 (Thanks to TauRho for the reconstruction)
HTC Norway 1.90.409.6 (Thanks to Verbato)
HTC Russian 1.90.411.3 (Thanks to sergr)
HTC Danish 1.90.403.6 - Part1/Part2 (Thanks to danny_and_2)
HTC Egypt's 1.90.485.3 - Part1/Part2 (Thanks to microfox and karimartine)
and this one too
jcespi2005 said:
This is the procedure to convert the dumped ROM into NBH "flashable" file. I take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from wiki.
Well, i manage to reconstruct the spanish dumped rom from my Raphael. This thread is about how to reconstruct a dumped Raphael ROM, to have the original ROM that cames with your Kaiser, so you can revert to origin.
This is only the process to get back the original OS for your device, neither the SPL nor the radio ROM.
1. First of all is to Dump the ROM from your device. For this you only need to go to Pof post here and follow the instructions (take care about values, cause not all devices have same ROM sizes). After dumping the ROM you'll have 4 RAW files. Take apart in one folder the Part01.raw that contains the XIP and Part02.RAW that contains the IMGFS, both needed for the reconstruction process.
2. Download the WWE BaseROM to use in the reconstruction process here http://rapidshare.com/files/138980371/RUU_Raphael_HTC_WWE_1.90.405.1_Radio_Signed_Raphael_CRC_52.33.25.17_1.02.25.19_Ship.exe
3. Download the Raphael Kitchen here, that allows to reconstruct the ROM from the dump. The Raphael Kitchen allows to cook a ROM from a dumped one and from base NBH shipped one. You need to put the NBH file from the step before in the BaseROM folder (the Shipped ROM is a huge EXE file, and you'll need WinRAR to extract the content), and put the RAW files too. Then execute the RAPHAELKITCHEN.CMD and choose the next options from the menu it this order:
e, b (for dumped ROM), c, a, press BuildOS icon and wait to finish, Close BuildOS. As a result of this process you will have a RUU_Signed.NBH file you can flash on to your Touch Pro to go back.
Thanks to JugglerLKR for help me and the knowledge to solve the issues into reconstructed ROMs, and Alex to make a better script, and of course all the ppl make wonderfull apps that make this possible...
Cheers.
Click to expand...
Click to collapse
Great walkthrough!
Is it possibly to include (optional) steps for restoring SPL and radio ROM also ?
/Rgds, Hans
HansN said:
Great walkthrough!
Is it possibly to include (optional) steps for restoring SPL and radio ROM also ?
/Rgds, Hans
Click to expand...
Click to collapse
Thanks mate
About restoring SPL, you have the needed info in the HardSPL thread http://forum.xda-developers.com/showthread.php?t=410150, for now there are only one SPL, version 1.90, so the follow the steps and you'll get the stock SPL.
About Radio ROMs, you only need to download the desired one from Wiki here http://wiki.xda-developers.com/index.php?pagename=Raphael_ExtractedRadioRoms
Cheers
Hi,
Your link for WWE BaseROM says:
"http://rapidshare.com/files/138980371/RUU_Raphael_HTC_WWE_1.90.405.1_Radio_Signed_Raphae l_CRC_52.33.25.17_1.02.25.19_Ship.exe"
but it actually points to:
"http://rapidshare.com/files/57816419/RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar.html"
Is it OK?
I would like to try rebuilding my original ROM which is the 1.90.401.1 with radio 1.02.25.19
Ops, thanks for the report... i copied the post from the Kaiser thread and forget to change the link... now is corrected.
Cheers
crocodile010 said:
Hi,
Your link for WWE BaseROM says:
"http://rapidshare.com/files/138980371/RUU_Raphael_HTC_WWE_1.90.405.1_Radio_Signed_Raphae l_CRC_52.33.25.17_1.02.25.19_Ship.exe"
but it actually points to:
"http://rapidshare.com/files/57816419/RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar.html"
Is it OK?
I would like to try rebuilding my original ROM which is the 1.90.401.1 with radio 1.02.25.19
Click to expand...
Click to collapse
No problem.
I get the error "Could not update itsutils.dll to the current version, maybe inuse?
Try restarting device or activesynch or maybe your device is application locked?"
I have tried two PCs and restarted my phone many times. I'm desparately wanted to backup my vodafone image before placing my own on.
Any help is greatly appreciated.
Scribe said:
I get the error "Could not update itsutils.dll to the current version, maybe inuse?
Try restarting device or activesynch or maybe your device is application locked?"
I have tried two PCs and restarted my phone many times. I'm desparately wanted to backup my vodafone image before placing my own on.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Try copy the itsutils.dll to SD, and after with Total Commander, or Resco Explorer copy from SD to \Windows folder.
Remember to edit the Policy registry too and restart after do it.
Cheers
After I pressed the icon BuildOS I get an error in BuildOS:
External component has thrown an exception.
Any idea?
Thanks.
chrisge said:
After I pressed the icon BuildOS I get an error in BuildOS:
External component has thrown an exception.
Any idea?
Thanks.
Click to expand...
Click to collapse
What OS version on your PC? Do you have .NET framework 2.0?
I have tested on XP and Vista and works fine...
Cheers
Win XP with .net 2.0 on a Mac runs in Parallels.
I cooked a Rom a week ago (Version 0.5) with no Problems.
chrisge said:
Win XP with .net 2.0 on a Mac runs in Parallels.
I cooked a Rom a week ago (Version 0.5) with no Problems.
Click to expand...
Click to collapse
Strange, cause BuildOS.exe hasn't changed since v0.5
Can you give me more details about the process you did untyl you get the error? step by step, please
Cheers
After I reinstalled .net and dumped the Rom again everything works fine.
Thanks for your help...
Chris
chrisge said:
After I reinstalled .net and dumped the Rom again everything works fine.
Thanks for your help...
Chris
Click to expand...
Click to collapse
Nice
If you finally get the NBH for your ROM/Languaje, please, post the link here so i can update the second post with yours.
Cheers
Vodafone UK image.
I get my Raphael (HTC Touch Pro) on Tuesday from Vodafone UK, i'll dump and upload the RAW files if it will be of any help to anyone, i would offer to do the whole reconstruction thing but it will be the first time i would be playing with RAW files and 1) I'll probably mess it up and 2) Take me a year to do lol, would be easier for someone experienced to do it.
Just let me know.
RavenY2K3 said:
I get my Raphael (HTC Touch Pro) on Tuesday from Vodafone UK, i'll dump and upload the RAW files if it will be of any help to anyone, i would offer to do the whole reconstruction thing but it will be the first time i would be playing with RAW files and 1) I'll probably mess it up and 2) Take me a year to do lol, would be easier for someone experienced to do it.
Just let me know.
Click to expand...
Click to collapse
Upload your Part01 and Part02 RAW files and i reconstruct for you
Cheers
will this method work with the diamond? i have been trying to reconstruct the dumped rom for a few days now and cant seem to find the answer! i have succesfully dumped, just need someone to show me how to recontruct, please help.
thanks
idrisito said:
will this method work with the diamond? i have been trying to reconstruct the dumped rom for a few days now and cant seem to find the answer! i have succesfully dumped, just need someone to show me how to recontruct, please help.
thanks
Click to expand...
Click to collapse
I think is the same and the procedure is valid 100%, but can't verify cause i haven't a Diamond...
Build is 23016
download and extract to a folder with no space maybe Nike_kitchen
Kitchen part 1 base
Kitchen part2 EXT folder and Extra Tools put inside kitchen folder if named Nike_kitchen just put this inside that folder
open Erviuskitchen.exe
press load ROM and choose nike then scroll down and set the keyboard you need and what languages
press Create ROM now wait
when finished just close Erviuskitchen.exe
now goto RELEASE_Nike folder and use the custom_ruu.exe to flash your new rom
In Extra_tools folder I have added some other apps found on XDA
EXT Package maker
Put you OEM package in the EXT Package maker folder then drag and drop it on the EXT_PAckages_rebuilder.exe and you should have a EXT package ready to put in you kitchen.
note that some oem packages you download are separated into 2 folders exsample PACKAGE_MEGA_Album and PACKAGE_MEGA_Album_0409
just drag the PACKAGE_MEGA_Album_0409 (language pack) onto EXT_PAckages_rebuilder.exe and it will a folder called 0409 inside PACKAGE_MEGA_Album
now just drag and drop PACKAGE_MEGA_Album onto EXT_PAckages_rebuilder.exe and you have a finished EXT package with language files inside.
The package will be named appname then followed by the build number of the app
CAB Converter by Jason8
How to use:
open CAB_Converter.exe brows for you cab
then choose cab -> OEM or cab->EXT wait for dosbox to close and you have a new OEM or EXT ready to use.
althought it a good app some cabs don't work
Have questions go here for suport
cabdump it is actualy Package Converter by Ervius
that is in most of the older kitchens and works with most all cabs
dubble click on cabConverter.CMD and follow the instructions in the dos box
you should now have a OEM in the same location as where the cab was located
some links most of them are from development and hacking
Get the newest wm6.5 build here and many other usefull tips
Get the newest wm6.1 build here
porting the newest XIP/SYS here
Change the name in the bootscreen and build date of the rom
Open Ervius kitchen and coose the XIP you are going to modify
now press Xipporterex & rom tool
press find date/Version on\ROM\XIP\
change rom date and rom version press change for bouth and you have a new name in bootscreen and rom is set to new date
Change rom info in settings/Device information
go to Nike_Kitchen\EXT\SHARED\Mods\my mods\files
open mxipupdate_OEMVERSION_100.provxml with notepad
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\OEM">
<parm name="ROMVersion" value="5.2.23016" datatype="string"/>
</characteristic>
<characteristic type="HKLM\Software\OEM">
<parm name="OperatorVersion" value="gullum" datatype="string"/>
</characteristic>
<characteristic type="HKLM\Software\OEM">
<parm name="ROMDate" value="20/08/09" datatype="string"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
change the info to what you want it to be
taking this one too
Why not just take this also
Here are the links of gullum's kitchen, with permission of gullum. (Thanks gullum)
Part 1
Part 2
Have fun
Cool I think I will try next week when I have some more time. Thanks again Gullum!
Hi Gullum...
thanks for sharing your kitchen... i will compare with mine because i dont know why my device does not boot when adding notifications or dialer with build 23016 or superior. With previous builds it boots perfectly.
Thanks again.
PS - by the way which build is your kitchen based: 23016 or 23017... in the post you have 230176
thyogo said:
Hi Gullum...
thanks for sharing your kitchen... i will compare with mine because i dont know why my device does not boot when adding notifications or dialer with build 23016 or superior. With previous builds it boots perfectly.
Thanks again.
PS - by the way which build is your kitchen based: 23016 or 23017... in the post you have 230176
Click to expand...
Click to collapse
sorry big finger or small keyboard it's 23016
Very good kitchen, thanks.
Last week I 've builded my first rom with it, works really easy and fast. Again great work.
One question though where can I remove the shortcuts (in startmenu) to packages/ windows components (like microsoft marketplace) I remove from the rom. Is that in the OEM folder?
Gr8 kitchen
Gr8 work gullum.congrats & thanks for sharing with us.
just wanted to know where,in which folder,do i keep other pkgs or prgrms made by pkg builder.
and how to change the sys boss?
hope u will respond!
again hats off to u for such nice work
Help
Help please
I can't find how to chnage languages and keyboard.
Can you help me?
Great Work
Thx alot for your great work
WELL DONE
Keep it up
Re do links
Can anyone redo the link on the first page as there no working
so i can downnload and start cooking....PLEASE PLEASE PLEASE and one more PLEASE.
Invalid or deleted file.... could someone reupload the files....
Thanks.
Yeah, same here.
Added links on post 4 with permission of gullum.
Thank you Rataplan, and of course, thanks to Gullum.