Related
I had a hard time to upgrade and modify my xda2 so I decided to make a small tutorial for everyone with the information’s I found on the forum. It’s not perfect but it could help.
Thank's to every one who made all this possible!!
Before starting I recommend every one to make a back-up of your rom
http://forum.xda-developers.com/viewtopic.php?t=4608
1- Extended Rom:
Your XDA2 has an Invisible Extended Rom in the device containing the operator’s configuration files and software.
Modifying it will allow you to customize the boot image and to choose the programs you wish to install during the setup of the device.
To show the extended rom on your device your need to apply this small hack and then open your file explorer:
http://www.ppcw.net/index.php?itemid=1638
2- Files contained in the Extend 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.
3- Modifying and editing your Extended Rom:
Most of the latest XDA2 have a write protected Extended Rom
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
or
http://www.clubimate.com/Support/ruu113sku1.zip
2) Simply unpack the complete T-Mobile Rom update file (it's a zipped EXE) into a folder.
There you will find these 6 files:
- HimaClearJumpCode.exe
- HimaGetDeviceData.exe
- HimaUpgradeUt.exe
- ms_.nbf <----- this is the file which holds Ext Rom!
- NK.nbf (main rom)
- Radio_.nbf (radio rom)
3) Delete the other *.nbf files to prevent updating the full XDA2/MDA2 rom. You only need "ms_.nbf" and the "*.exe" files!
4) Now modify the ms_.nbf with the tool softworkz kindly provided.
http://wiki.xda-developers.com/wiki/ER2003Edit
5) After this, install the modified ext-rom to your XDA2/MDA2 by starting "HimaUpgradeUt.exe" and follow the instructions!
6) If you get a country code error during the install you will need to modify the country code included in the ms_.nbf file
- Download xda2nbftool
http://forum.xda-developers.com/viewtopic.php?t=5563
- Put xda2nbftool.exe in the same folder as your ms_.nbf file
- Run xda2nbftool.exe from Command Prompt and type the following command
xda2nbftool.exe -so O2 -v ms_.nbf
Replace O2 by your operator’s name (ex: orange, O2 etc)
It should now work!
cheers,
Yann
nice one Yann
Thanks
I had a go at doing the "if your extended rom is protected"
I down loaded the file
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
and accidentally ran it.... I know I was stupid... I now have an I-Mate instead of a XDA - O2. Please help can I get the O2 back is there a programme that does the same as the one I just have used. It has changed every thing the radio stack, the other bits of software, I am just pleased it still works of calls.
I couldn’t find the indivuiual HimaUpgradeUt.exe programme any ware.
Please help I am really stuck at the minute!!
The bit I didn’t understand was the bit about unpack the exe. Which I now understand how to do. Although I have upgraded to Rom 1.52.00wwe, radio version 1.06.01, I can haply say I have the original O2 rom back in place with additional programmes installed in the Ex-Rom. I had a fair bit of space so I popped some music files in as well!!!!
Thanks for all the help!!!!
thanks yann for the perfect summary
as newby i needed something clear like this to dare my first rom changes, and i successfully did!
it would be even more perfect if also somehow the program settings/passwords could be cooked in/restored from the extended rom. i searched the forum but could not find any hints.
Are there methods for this ?
Perhaps a silly question, but I'm fairly conservative when it comes to messing around with my device.
How do you find out or know if your Ext ROM is write protected or not? I know that I can add applications to my Ext ROM and it does not seem like I should be able to do that if it's write protected, but then again I'm not sure if this matters.
Ed
ed, if you can copy files to your ext-rom via activesync, it is per definition not write-protected.
your not that conservative, because you already run a tool or edited the registry to be able to see the ext-rom
ronald,
Well I guess you are right I do like to play around, as I get more comfortable doing so. It is this Forum, guys like you, and some other forums that have made this possible for me to do. For some reason I'm more comfortable in general hacking around a desktop pc than a PPC.
I thought my Ext ROM must not be write protected. When I deleted the TMD files, described here as useless, I got the message that they were read only, but they did go away from the Ext ROM Folder. I do not notice a big difference, however, nor did it free up that much memory. I was thinking that I might need to do more then this. Do I?
So basically, if my Ext ROM is not right protected, and I have been already loading programs into the Ext ROM, I’m pretty much at the place people are trying to get with the Ext ROM Cook ER...Edit. Is that correct or am I missing something here?
Ed
Ed,
I do not like flashing rom (or bios) on either my desktop or PDA (if not absolute sure to fix bugs). However flashing the PDA's ext-rom can basically not screw up the PDA because you don't touch the OS, so I flashed the ext-rom to get familiar with the PDA flashing in general (and also to have a restore of my standard used software after a hard-reset).
About your ext-rom; I do not recognise your situation. I would say if it is read-only the file will not disappear (like with my PDA).
I did notice while editing the ext-rom file for flashing that the file is fixed ~16MB, regardless of which cab's are included or deleted.
Maybe this is the same effect that you see when deleting the file in the ext-rom ???????? (although I can imagine both effects have no relation)
ronald
Camera Programs
Okay,
I made a custom ROM with the following programs:
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
Awesome, alot less bloat, but.... Camera doesn't work.. Application says Camera is not a valid Pocket PC application. :: grumble ::
Did I miss something?? Camera.exe is there, but doesn't work
Brandon
My Ext ROM is not write protected, and I'm able to run applications in the EXT ROM Folder. I deleted the 2 TMD and the T-Mobile cab files, but I have not nticed a big difference, nor is my GPRS back to always on, which it should be now.
Perhaps the device requires another hard reset without these cab files in place prior to the changes taking actual effect. Does anyone know if my assumption is accurate about the required hard reset?
Ed
what dictates if the ExtROM is write protected or not? is it the version? or the hardware itself? or a mix of the version with the OS checks?
cuz i believe the ROM version is dictated by the version_AKU1.sa.cab. does that mean we can hack the cab (or use a diff version) to disable the write protection?
i'm using a himalaya btw.
I have a question or two.
I'd also like to know if it is possible to modify CAB files so they install an application and then also put in your purchased key or serial depending on the application so it's already registered to yourself. It seems like it must be possible because the GPRS Monitor on the T-Mobile Extended ROM is already Registered when you try and register it yet I was under the impression it normally has to have a key entered to turn it into the full version with no limits.
This would be great if this was possible, if it's a key file then it's simple to copy it over but how about automatic registry entries? Are these done similar to Windows .reg files? Does anyone have any info if a .reg file can be make and run from the Extended ROM to make changes to the registry? This would also allow me to key in a few other things I'd like presetup.
Is there a way to see what registry changes a CAB file makes other than from purchasing MagicCAB? Is there a free program like this? It seems like a reasonable program from the info but I don't want to spend 10 dollars on a program I might only use once or twice.
Acutally, one more while I'm here. Does anyone have a CAB installation version of CabInstl which puts a shortcut in the Programs or an easy way for me to make that? I've set it up so it will copy the EXE in manually along with a shortcut but I've yet to try it. I think it should work OK I imagine, just might be neater and have an uninstall if it's in a CAB format?
Can you delete files from the extended ROM script? Just so I can clear out a few folders of things I don't want in there when I do a hard reset?
Thanks for all your help. I'm looking forward to making a super kick ass Extended ROM for myself, I'm half way there
Updating the indirect way
Had a few problems with the updating process... and thought i would explain how I got around them!
First I updated to the standard 16007DE ROM
Then I installed the Extended Rom Viewer, and then because it is protected, i copied the contents to my HDD.
Then i tried to open the Rom update from T-mobile with the Extended ROM editor, but kept on getting file access errors The only one i could open was the NL 13006 version. So I changed the splash screen, deleted the origianl contents, and then inserted the contents from my updated original Extended ROM, as well as a few other bits that i could find, IE the extended ROM viewer. It is updating at the moment, So I hope it all works.
I have a few questions though!
Does anyone know a way in which I can automatically install a few themes, and a few ringtones? I have a few MIDI files that i want to be installed into the windows\rings folder, and the themes need to go in a folder called themes in My Documents. I also wanted to ask if there is a way to extract the CAB from another program, for instance Voice Commander. It is an MSI, but only works in windows!!!
Any help would be greatly appreciated...
Greets from Hannover, Germany
Juggs :?
Is this going to work:
- Download ER2003Edit
- Download the O2 XDA2 ROM 1.60.50
- Download the T-Mobile MDA2 ROM 1.60.36
- Remove O2 apps i don't want to use
- Add applications from T-mobile rom which i want to use
- Change ROM provider from O2 rom to to T-Mobile
- Save new O2 ROM and upgrade
But... I want to add custom ring tones to contacts, and if possible also want to add custom picture. Also my camera must be able to work. Which software do i need for this?
Because.. All i want to upgrade is today theme to O2's and also the software to 1.60.50... Does the O2 rom also has an "TMDNLCustomize.sa.CAB" ?
Greek full support language for qtek 2020
Hello,
this is a very intresting site!
Can anyone tell me is exist & where can i dinf an extended rom for qtek 2020 with full support of greek language?
Also there any newer version than the 1.66.00 wwe extended1.66.130 radio 1.10.00 wihich my qtek 2020 has??
best regards
george
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
Click to expand...
Click to collapse
2 questions for you,
1. how do i know whether my rom is the editable 1 or the non editable one?
2. I tried option A, just mergly adding the CAB files into the EXTROM but... when the hard reset was perform it did not install the CAB files i added in? what could be the prob i know there is a "autorun.exe" in it but i dunno whether will it affect the process. I also notice a "config.txt" in the extrom, tried editing it but it seems that nothing happen
Reason for adding the cab files is because i was using a 1.72.00 rom with radio stack 1.12 but intend to change it to radio stack 1.14 and also try cooking up my own rom in the ktchen but after doin so its like nothing happen. need some advice for cooking roms in the kitchen been searching the forum... found a few but its all talking about Linux platform.
Hi Kelvin,
1)
The way to know if your rom is not writ protected is if you see a folder called extended_rom in the root of XDAII and if you can add files in it.
If not, there’s a nice tool to make the extended_rom visible and to make it writable.
http://forum.xda-developers.com/viewtopic.php?t=8422&highlight=extended+rom+hide
2) The config.txt is made to lunch the programs in the extended rom when you hard reset the XDA or when it starts for the first time.
You just need to put the cab files in your extended_rom folder and edit the config.txt this way:
Exemple:
I added the cab file vxIPConfig.ppc3_arm.CAB in the folder extended_rom
and added this line in config.txt
CAB: \Extended_ROM\vxIPConfig.ppc3_arm.CAB
Cheers,
Yann
hi yann,
i tried doing that way as i figured out that config is like a startup "prg" to actually start the programs installing when hard reset is performed. But the thing is i cannot make the programs i added in the install after the hard reset is perform. I don't know why but the rest of the cab files can be done. Do adding of all this cab files into the ROM consider cooking ROM??? not really fimilar with the terms of cooking ROM unless that is the way.
Hi guys,
a new version of ER2003Edit is available from the wiki page:
http://wiki.xda-developers.com/wiki/ER2003Edit
New features and improvements:
- provides support for the new upgrade tool version (0.9.1.0) used by the latest T-Mobile and O2 updates
- supports editing of the header information (DeviceID, Operator and Language) in order to circumvent the country code error
- some other fixes and improvements
Best regards,
softworkz
Thnx dude! At last we got a program to modify the header. I guess this makes a lot of XDA owners very happy.
Great work!
Late...
Thanks Softworkz, great work again. It really looks like an even more powerful tool, but there seems to be a little bug (or I am doing something wrong):
After upgrading ER2003Edit to the new version, I cannot open the ms_.nbf anymore. When I try to open the file, ER2003Edit always crashes, although I left the file unbmodified.
Downgraded to the old version again and there it works, although I have to decode and encode the files by myself.
Any suggestions?
No problems opening the ms_.nbf here after doing the upgrade. Running Win XP sp1.
Try uninstalling the old one completely then install the new one...
Works great!
Late...
is it a misunderstanding between header-information and encryping ???
I think Er2003edit does not do the encryption/decryption so far.
Hey Softworkz...
this would be a great improvement as I guess all coming
extended roms will be encrypted.
Alex
Tried uninstalling and re-install but that didn't help. As far as I remember, Softworkz tool is not able to edit encrypted ms_.nbf.
But on my machine (Win XP pro 2002 SP1) the program always crashes when opening an non-encrypted ms_.nbf...
I will use the old one as a workaround, I don't need to change the header so this should be fine.
some programming tips:
It should not be very difficult to implement the xor decryption, just xor each DWORD in the file with 0x25863614 after loading it in memory, and before saving it back to the file.
also, if you verify the header checksum after loading the file, you should be able to detect that the file you are loading is actually a decrypted nbf file.
and another check to see if at offset 0x70040 there is a valid bootsector, with
the 'MSWIN4.1' and 'FAT16' strings should prevent it from crashing on invalid files.
Ouch, I just found out that the wrong version of xda2tools.dll was included with the setup. I have made available a new version (1.2.20) to fix this. (see wiki page)
Some details about ER2003Edit:
You do not need to uninstall old versions before installing newer ER2003Edit versions.
The new version (1.2.x) is able to perform XOR-De-/Encryption. When opening an extended ROM file ER2003Edit first checks if it is encrypted by looking for the presence of the dashes in the header.
If those are present in the right places ER2003Edit opens the file as usual. If the dashes are absent ER2003Edit tries to decrypt with all of the three XOR-Passwords (). If none of those passwords produces a file with a correct header a prompt is shown which lets you enter your own password.
The decrypted (or a copy of the unencrypted) ROM file is saved to the temp folder. When saving with ER2003Edit the file is encrypted again (in case the original file was encrypted) and is saved to the original location overwriting the initial file.
Itsme: The "dash-check" was used because the CRC-check in your code was always true (didn't look into it further).
The new version supports auto-detection of the ROM type in order to edit the header of the other 2 ROM files (NK and Radio_), too. The "error accessing image files" message is now suppressed for these files.
Nevertheless modifying the header of those files is useless and I didn't figure out how to access the file structure in those files (doesn't look like a FAT image).
Best regards,
softworks
Okay, that explains the problems I experienced. As soon as I am back home I will give it a try. If it works it will be a nice & powerful tool...
==> seems to work perfectly. So there are no more obstacles. Next stage will be an Upgrade to 1.66.xx... :shock:
ok, now it works.
currently, a non-matching crc value only results in a printed warning, maybe I/you could add an extra parameter to the file processing functions, which get the result of the crc-check.
or maybe even better, raise an exception, for the warnings.
ER2003 crashes opening new O2 extended ROM Files
Hi softworkz,
first off all thanks for your great work!
Using the new version of er2003 i cant open the ms_.nbf file of the latest O2 upgrade (1.60.52). It crashes every time. Opening and editing my self created ext. ROM based on T-Mobile Update 1.60.07 works great.
Whats wrong with my installation? If you wish i can send u my Win XP error report.
Escargotet
Sorry for posting, was 2 stupid to read forum first!
Sorry for posting, was 2 stupid to read forum first!
Hi all
Please help to clarify as there are some inconsistances...
(or I am wrong, but will run into this problem)
Er2003edit will try to modify the header information in the NK and Radio_mbf but this will not be successfull and I still will get the Country ID error, is that right ???
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
So there is a missing link...
Alex
itsme said:
ok, now it works.
currently, a non-matching crc value only results in a printed warning, maybe I/you could add an extra parameter to the file processing functions, which get the result of the crc-check.
or maybe even better, raise an exception, for the warnings.
Click to expand...
Click to collapse
The CRC check does not work in your code. XORing with a wrong password results in the following message:
WARNING: this does not look like a nbf header, possible you provided the wrong password
But this gets printed as a result of the "dash-check". If the crc-check would fail, a different message would be printed:
WARNING: checksum is not ok, possibly you provided the wrong password
But this message never gets printed because (filecrc != crcsum) never occurs (for whatever reason).
Xant said:
Hi all
Er2003edit will try to modify the header information in the NK and Radio_mbf but this will not be successfull and I still will get the Country ID error, is that right ???
Click to expand...
Click to collapse
No. Er2003Edit can open NK and radio ROM files and edit the header. Er2003Edit automatically re-encrypts the newer ROM files (XOR-Method).
Er2003Edit decrypts older ROM files (DES-Encrpytion), lets you edit the header and save the file but it does not re-encrypt these ones (use xda2nbftool). A message is displayed in this case to remind you to encrypt the file.
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
softworkz said:
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
Click to expand...
Click to collapse
I confirm what bobopopo claims, i tried only flashing the ms_.nbf, and it totally messed up my machine (stuck in bootloader), i had to reflash all three to get it to work again
nargalzius said:
softworkz said:
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
Click to expand...
Click to collapse
I confirm what bobopopo claims, i tried only flashing the ms_.nbf, and it totally messed up my machine (stuck in bootloader), i had to reflash all three to get it to work again
Click to expand...
Click to collapse
I knew about this. I was just stating that the header of NK and Radio is irrelevant for the upgrade tool and is not responsible for the country code error.
SPV M1000
Does it work with SPV M1000 version
loade ER2003 started it and stay on the ROM info screen :?
Hi,
just a tip for opening the latest ROM files with ER2003Edit:
ER2003Edit has a file type selector in the file open box which is by default set to autodetect.
in autodetect mode ER2003Edit tries all encryption passwords it knows for any type of ROM (NK,Radio,ms_)
when using autodetect mode and your ROM does not get detected and you enter the correct password manually, you will receive an "Error accessing image files" message
To prevent this message choose the correct type of ROM (ms_.nbf) from the file type selector of the file open dialog and enter the password
ER2003Edit can open and edit all types of ROM files now in order to let you change the language and device type settings (to prevent country code error)
Tip: Opening ROM files is always faster when you do not use autodetect mode!
BTW here are the passwords for the ITA-Rom:
ms_.nbf: 0x20040305
nk.nbf: 0x20040304
radio_.nbf 0x20040306
A new version of ER2003Edit will have these passwords built in, but I currently do have no time for a new release just to include the passwords.
Enjoy!
fantastic
thank you very much
Works
Thanks
Softworks, are the the old passwords hardcoded into the app?
I reckon on your next update, maybe you could just make the app read an XML (or text, whatever) file with the passwords. So you can easily just add passwords in the future onto the text without having to recompile a newer version.
Also, since when talking about XDAII files, we're only talking about 3 filenames which never change. Maybe you could make a load process to simply check the filename which has been opened and use the corresponding "file process" to open it. Sort of like instead of autodetect when you open files. Have a simple check that checks wether one clicked either of the 3 files, then have a script that mimmicks selecting manually the filetype instead of "autodetect." That should eliminate the "nuances" of opening files (especially helpful for us n00bs hehe)
Cheers,
Carlo
Sorry, Iwould like to ask how / where to find the password of the images?
Thanks!
Hi All,
I have images which can't open by ER2003edit V1.2.20, it say the password is incorrect. Anyone can help or teach?
The rom image is from O2, the rom version is 1.60 or higher.
Thanks!
Can someone help me out too, it won n't seem to work with me.
d.zee said:
Can someone help me out too, it won n't seem to work with me.
Click to expand...
Click to collapse
Cant find them either.... Please help
See here:
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
Here is a patched version of ER2003Edit.exe that has the new 3 passwords. Auto detection now works. :lol:
Just unzip then copy it over installed ER2003Edit.exe usually found in
C:\Program Files\softworkz\ER2003Edit\ER2003Edit.exe
RE
Hi!
Thanks. It works.
:lol:
PDA: O2 XDA II
ROM Version: 2.06.00WWE
Radio Version: 1.18.00
ExtROM Version: 1.12.924WWE (from IIs)
OS: Windows Mobile 2003 Second Edition
OS Version: 4.21.1088 (Build 14132)
Any reason I am getting shcksum errors?
I chenaged the content of ms_.nbf save it, and tried to flash it, but I gor error 122 - checksum error?
Any known reason for that?
Looks like I am out of my depth but its worth a try
I have a blueangle and have worked out that there are more tools on in Himalaya than for us.
I have further worked out that the upgrade works in the same way.
So I would think that this tool does, Well I am either wrong or just dumb.
Is my undersatnding correct that this application would only have the paswords for the at that time Known rom realeases.
Is my understanding that even with a password out of a xda3nbtool this toll will not work if you add it in the dialog.
Thus I seem to find that if I fill in the device name, op and lang as well as pasword I fail, same is true if leave them blank.
Please help me out or point me in the correct direction
Thanks
Hi,
does anyone know a program or a howto for editing Asus MyPal ROM Updates? In fact I only have to add a single file.
Thanks for any response
Martin
Anyone know how to translate this ROM 2.20Chinese to English...
so we can have wmp10 in our XDA, and other features that is better than 2.06 and 2.02 ROM....
mamaich : can you teach us how to translate the english langguage, or you can upload this rom 2.20 that have been translate to english in this forum... big hope
Or the original rom of 2.20 CHS because when i try to download through the link you provided.... I always cannot completed the download and that file was not on your website (when i try to visit the page directly).
thx in advance
I also have mailed some days ago to Mamaich asking for some info about Win2k3se and Wmp10 translation..
Now we all waiting..
The test version of English ROM made from chinese 2.20 is uploaded to http://mamaich.kasone.com/imate/en.rar
archive contains nk.nba file that should be processe d with xda2nbftool and flashed.
I've uploaded mkrom toolkit used to create this ROM to: http://mamaich.kasone.com/imate/mkrom_220chs.rar (18.5 mb)
Original toolkit is taken from http://wiki.xda-developers.com/wiki/mkrom
To use it you'll need Linux or CygWin enviroment (I use cygwin), Perl, hex editor (I use HIEW). You should place new files to files1...files5 directories. Here is the maximal size these directories can be:
Files1: 655360 bytes
Files2: 1245184 bytes
Files3: 262144 bytes
Files4: 524288 bytes
Files5: 1114112 bytes
Toolkit would not warn you if this size is exceeded and would produce dead ROMs.
Files1 folder should contain mxip_MYXIP_100.rgu file which is a modified registry. CreateEngLinks.exe is a program that runs after hardreset and creates english folders and links. I was unable to patch the initobj.dat and default.fdf files in ROM, so I had to create this program.
cfg\os.nb1 is a "base" ROM image with some files renamed. You should not touch default.fdf, initobj.dat and kernel.rgu
When you run ./a.sh file it would produce a new ROM named nk.nb1. Use any hex editor to place this file to offset 0x40040 of NK.NBA I've posted in the prev. message and modify it's CRC and encrypt:
xda2nbftool.exe -c -u NK.nba
xda2nbftool -x NK.nba NK.nbf 0x20040304
Use this toolkit at your own risk. Addresses in ./a.sh are taken from 2.20.07 chinese simplified ROM and should be modified to be used with other ROMs. You may completely destroy your device if this toolkit is used incorrectly.
Hey mamaich,
that's perfect! THANX
Let me try it now...
buzz
Hi Mamaich... can you tell me what is the difference about this two files or links.
1. http://mamaich.kasone.com/imate/chineese_se.rar
2. http://mamaich.kasone.com/imate/en.rar
Is the number 1 totally 100% Chinnese? and the number 2 is 80% English, 20% Chinnese?
Thank You...
double_ofour said:
Hi Mamaich... can you tell me what is the difference about this two files or links.
Click to expand...
Click to collapse
hey double_ofour, it's written in mamaich's post above...
The test version of English ROM made from chinese 2.20 is uploaded to http://mamaich.kasone.com/imate/en.rar
I've uploaded mkrom toolkit used to create this ROM to: http://mamaich.kasone.com/imate/mkrom_220chs.rar (18.5 mb)
Click to expand...
Click to collapse
XDA2 WM2003 SE 2.20.07 WWE
Hi,
for your convenience I just created regular upgrade package out of mamaich's nk.nba file.
PERFECT WORK mamaich... )))
It is Country ID and Operator ID INDEPENDENT, however it will change your device to Qtek + WWE after upgrade.
If you don't like that, just edit .nbf files yourself.
OS version 2.20.07
Radio version: 1.18.00
Extended ROM is NOT included, because I believe, that anyone can build his own Ext ROM to suit his personal taste...
Get it here:
ftp://xda:[email protected]/Himalaya_SE/Himalaya_WM2003SE_2.20.07_Upgrade.zip
Unpack and run HimaUpgradeUT.exe
buzz
Hi.. is that 100% english or youve just rip it to mamaich room? still 80% English? sorry for this stupid question...
RE
Hi!
What are the major differences between the WM2003se Chinese-to-English ROM vs the available other 3 English ROMs
I suppose it can read/write chinese sms without the use of 3rd-party program?
How's the bluetooth performance? Still has the vanishiing Headset icon on the Today screen?
Thanks
i upgraded with the 2.20 file, anything runs fine, except, i can't turn on my qtek2020 with any button, neither the power button, nor the application buttons. only way to turn it on is doing a soft-reset or getting an incoming call..
what went wrong with the update??
regards epo
Great work mamaich and buzz_lightyear!!! Unbelievable work the both of you!!!
I have not yet tried and will do so in due time, but I am fairly certain that it is yet another accomplishment to be highly commended...
- Cheers and thanks again for the excellent work
Hey Epo.... is it full english? ot still like the same with mamaich rom?
it seems to be fully english.. anything works fine, except i can't turn it on with the buttons..
ok, now it works, seems to be a problem of my extended rom..
i reflashed it without executing the extended rom and now it works!
great work mamaich!!!!
Hi all, few questions ...
1. Does this ROM still have the hide&seek effect with the BT profile plug-in ?
2. The other 2 versions have only 3 alarms for the clock, and I really miss the 4th one in 1.72
3. It took me some time to localize the 2.06 one on my I-mate, did any one try this ROM with the arabic language ?
The MOST stable rom from among SEs
Hi,
Thanks Guys!
This is the most stable one from all SEs.
To make it more stable, turn off your radio when doing soft-resets and don't install or edit any language registry values! And don't use software that works with them, such as LENG and other.
Does anyone know how to enable russian language input mode now?
Rom: 2.20CHS
Radio: 1.18
Ext: 1.72-IMATE
Some Anomalies?
Hi!
When I open Programs -> File Explorer -> My Documents, I see some folders with square boxes as folder names. Any purpose for these folders? They are empty. Can I delete them?
One thing I found is that when my phone is off my O2 II will soft reset if I tap the GPRS icon on the Today screen top bar. Is this normal or am I getting a new soft reset button?
Thanks
:roll:
More square boxes
Again, when I go to Programs -> File Explorer -> Program Files I see a square box folder. Another thing is that there're two WMP folders. One of them is Windows Media PlayerCS which on opening display square boxes
Next, is if I go to Windows I see a square box folder right on the first line. If you tap on it it'll open with more square box folders and the icons - Help, Calendar, Phone, Contacts and Messaging come with square box names.
I presume all these square boxes are in chinese not properly translated yet.
Hope to see an updated version soon
Thanks
Hi,
I see square boxes in the "Connections" settings panel too.
Good work!
Thanks,
@ngel
Dear Fellas,
Where can I get a step by step ROM upgrade instruction to upgrade/flash my XDA II into WM2003SE? I have been through the forum, but still can not find a basic guide to do the upgrade.
I have downloaded "Customized_WM2003SE_Asian_Edition_Version2.zip" from ZeroXtreme. What can I do with this file? How can I start it?
Anyone can help me pleaseeee.......Thanks a lot.
Rgds,
Fendie
Ahoy there matey!
this is what you do:
1. decide on what version you want to use.
2. get them roms. (E.g. read through DCS's post on the ORIGINAL WMSE)
currently there are three versions of the WMSE namely 2.02,2.06, and 2.20.
3. check your device data for language and operator:
use getdevicedata.exe from the upgrade files, copy it to your device's windows directory, then tap on it.... it will produce a log file, copy the log file to your desktop pc, then use notepad.exe to view it.
look for the language setting e.g. WWE, CHT... etc.
look for operator settings e.g. O2, Qtek... etc.
now check your downloaded NK.nbf, MS.nbf and radio.nbf to see if they have the same settings as your device..... you can use ER2003edit.exe which can be downloaded from wiki.xda-developers.com.
if the files have the same settings, thats good... if not... change it so that they would be the same as your device.... better yet use DCS's batch file for easier conversion... (note, DCS's 2.02 rom is set to WWE,O2)
now... assuming you had made all the preparations... (language, operator settings, and that you have a complete set of roms e.g. NK.nbf, MS.nbf and radio.nbf)
put them all in one directory along with the other files that came with the upgrade package.
make sure you have a full battery before proceeding with the upgrade.
plug the charger to tha cradle and the cradle to the comnputer.
click on himalaya upgrade program.... then the program will run, put the device in the cradle and watch the screen for further instructions
goodluck...
be sure to read on DCS's post regarding upgrades for a more detailed info.
assuming everything goes well; during the upgrade do NOT take out the unit from the cradle; go watch tv or something...if you receive an error message; don't fret. the forum hosts a lot of topics on how to revive your unit...
and if your xda dies during the upgrade; make sure your tray tables are in their upright position, put your head between your legs and kiss your arse goodbye
what do guys suggest the ROM i use?
which one is the most stable?
mate, i noticed that you're from the philippines. i'm based in thailand i used the rom posted by zeroextreme; it's the wm2003 se asian rom. pretty stable that one; after upgrading my unit's power consumption improved noticeably. although as expected some apps may not display well when using landscape mode (those're the apps not designed for wm2003 use). but overall the rom upgrade was well worth it. stable and no hick ups; been using it for more than 2 weeks now i think.
others may have useful tips on the other roms they used for upgrading; not to mention experiences.
cheers
acid.... try 2.02.t1 they say its more stable than 2.06.
thanks mga kababayan!
Z-man said:
Ahoy there matey!
this is what you do:
1. decide on what version you want to use.
2. get them roms. (E.g. read through DCS's post on the ORIGINAL WMSE)
currently there are three versions of the WMSE namely 2.02,2.06, and 2.20.
3. check your device data for language and operator:
use getdevicedata.exe from the upgrade files, copy it to your device's windows directory, then tap on it.... it will produce a log file, copy the log file to your desktop pc, then use notepad.exe to view it.
look for the language setting e.g. WWE, CHT... etc.
look for operator settings e.g. O2, Qtek... etc.
now check your downloaded NK.nbf, MS.nbf and radio.nbf to see if they have the same settings as your device..... you can use ER2003edit.exe which can be downloaded from wiki.xda-developers.com.
if the files have the same settings, thats good... if not... change it so that they would be the same as your device.... better yet use DCS's batch file for easier conversion... (note, DCS's 2.02 rom is set to WWE,O2)
now... assuming you had made all the preparations... (language, operator settings, and that you have a complete set of roms e.g. NK.nbf, MS.nbf and radio.nbf)
put them all in one directory along with the other files that came with the upgrade package.
make sure you have a full battery before proceeding with the upgrade.
plug the charger to tha cradle and the cradle to the comnputer.
click on himalaya upgrade program.... then the program will run, put the device in the cradle and watch the screen for further instructions
goodluck...
be sure to read on DCS's post regarding upgrades for a more detailed info.
Click to expand...
Click to collapse
Hi Z-Man,
Thanks for your response. But still do not understand in some areas
I just got MS.nbf and some *.CAB files from the extended ROM of ZeroXtreme. There are no NK.nbf and Radio.nbf. Is it because it's an Extended ROM? Where can I get the "non-extended" ROM?
And I don't really understand on DCS's post.
Sorry, I am really really newbie.....
Many thanks.
Rgds,
Fendie
ms.nbf is the extended ROM, you still need to get the radio.nbf and nk.nbf
download the file here:
HIMALAYA_WM2003SE.zip and Operator update.zip:
http://forum.xda-developers.com/viewtopic.php?t=13588
extract all files to one directory... and add the ms.nbf that you have
you didnt mention the operator and languange settings of your device... check your device info....
then use DCS's batch file to convert the settings.... by default, DCS uses WWE and O2.
make sure all the nbf's are set to the same settings...
then begin upgrade
Himalya Romkitchen is still valid for SE