Related
This message contains all postings in this thread
dated before January 19th 2003
Subject: SMS Backup
From: Anthony Newman
Date: 26 Dec, 2002 20:08:08
Hi Folks,
Thanks again for all your great work on the site. I was just
wondering if I could pick your brains on an issue that's been
bugging me.
I've searched google with every possible permutation of this
query, and it astonishes me that no-one's covered it - have I
been missing something really obvious?
I'd like to back up my text messages. Inbox doesn't sync them
with Outlook, nor does it offer any kind of backup tool. Short
of copying and pasting the text, date and recipient of each
message into a text file or email, is there a database I can
backup and use?
The reason I ask is because I'm trying to cover every
eventuality for when I flash my generic Spaceneedle with the
T-Mobile ROM that was released recently. I've carefully
catalogued every preference, program and file on my device ready
for fresh reinstallation with the exception of my text messages.
I could, of course, do a backup with Sprite's excellent
software, but I'd rather not do even a partial restore of a
backup from an old ROM version.
Any ideas, folks? Many thanks in advance!
Subject: Oh, never mind.
From: Anthony Newman
Date: 26 Dec, 2002 20:37:18
Having studiously backed everything up, made note of all my
settings and got everything set up just perfect...
... the T-Mobile utility won't let me upgrade my device. I
receive a check error showing device differences, and the only
difference appears to be the following:
My model: PW10B1:100
The upgrade's model: PW10B1:002
Can anyone let me know what the differences between the numbers
after the colons are?
This is really frustrating, as in terms of actual hardware my
device is the same as the T-Mobile, and I'd love the increased
speed and stability of the new ROM. Any help?
Subject: Oh, and just another thing...
From: Ant
Date: 26 Dec, 2002 20:41:57
I'm aware that I can try flashing with the bootloader method,
but I wanted to check that there weren't any known issues first
Subject: To continue my monologue...
From: Ant
Date: 27 Dec, 2002 00:21:39
My update went perfectly well, and I now have the new T-Mobile
ROM working nicely on my generic Spaceneedle with my O2 UK SIM.
Even GPRS works as well as it used to (which is intermittent at
best). Thanks for XDArit!
Subject: ROM Hack
From: mike
Date: 27 Dec, 2002 07:15:31
I was able to hack a ROM file with a hex editor to change its
version number. The version number is found within the first 32
bytes of the ROM file.
You also have to alter the checksum which is a number also found
in those first 32 bytes... three or four hex digits. IT should
be fairly obvious, since
If you increment an ASCII digit, you must also increment the
checksum. Decrement ASCII digit, decrement the checksum. Since
you'll change a 1 to a 0 (-1) and change a 0 to a 2 (+2), your
net change is +1 and you must add 1 to the checksum.
That said, whatever this ROM does to your phone is your risk. I
already screwed up my T-mobile phone, granted that was due to me
flashing the US radio with a European update, this shouldn't be
so bad, but do cross your fingers.
mike
Subject: .nbf files in RUU upgrade
From: XDA developers
Date: 29 Dec, 2002 14:21:29
You'll find that the XDArit already supports reading these files
and parsing out the bootloader and WinCE image. (We ignore the
checksum, but write the correct one for the bootloader on the SD
card...)
Upgrading Extended ROM from Imate to TMobile Extended ROM, Easy As 123 Please follow the Steps
1. Get hexeditor
2. Download TMobile 1.60 and extract it to get ms_.nbf
3. Download I-Mate Ruu15283WWE and extract to get ms_.nbf
4. Open Both Files in hexeditor, please remember both files so you will get confused.
5. if you are having T-mobile and want to upgrade to I-mate Extended ROM you have to do the following in reverse.
6. Copy "2d 43 44 4c 00 00 00 00 " (-CDL....) and paste it to T-Mobile ms_.nbf, location "2d 54 4d 4f 42 49 4c 45" (-TMOBILE) , This is the Version.
7. Copy "62 34 34 39 38 64 31 34" (b4498d14) and paste it to T-Mobile ms_.nbf, location "65 38 34 31 37 61 63" (e8417acd), this is the CountryID
8. Save the T-mobile File to c:\New folder\ms_.nbf
9. Include in the New Folder "HimaClearJumpCode.exe","HimaGetDeviceData.exe", and "HimaUpgradeUt.exe".
10. Start to run the "HimaUpgradeUt.exe" and it will start updating your mobile.
Have fun and enjoy your new extended rom.
8)
ROM Version : 1.52.00WWE
ROM Date: 10/23/03
Radio version: 1.06.01
Protocol version : 1337.16
ExtROM version : 1.60.06
Next i will try to update my I-mate 1.52 nk.nbf to T-mobile nk.nbf but not the radio because radio will not work with my area.
Thanks!!!!
Let me try it!
the 8 hex digit number is not the country code, it is the sum of crc's of 256k blocks of data of the file.
see http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html
for a tool to calculate it.
soon an adaptrom version will follow.
a warning though: if an upgrade fails, you may be left with an unbootable device. you can use xda2dmp to fix this in most cases. ( I hope )
also DO NOT consider trying out 'HimaClearJumpCode.exe', it will make your device unbootable. and you will have to figure out how to use xda2dmp to fix it.
Update I-MATE ROM to T-MOBILE or backward ?
Hello,
I have an I-MATE and sometime ago updated to T-MOBILE ROM 1.6
Later on I-MATE released their own ROM update and when I tried to install it, even knowing that it is "lower" version - I got message that "Country Code ID is incorrect" (I am sure it is already known issue for XDA II community )
1. Is it make since to go waist a time and try go back in lower I-MATE ROM?
2. and if 1 is YES, how to change Country Code ID so installation of I-MATE will proceed further?
I would really appreciate reply from XDS developers.
Thank you
Paul
I did test it.
This method not only allow to install the extended rom it self , but allow the machine to flash the full set of rom!
Moreover, after flash the new rom, it will keep the country id of the new rom, not the old rom.
I found the bug, the problem is that the language of the device is reported as 'WWE'
maybe you can change one of the language identifiers in the binary of HimeUpgradeUt.exe.
or as I just noticed. the update tool in the Update.rar attachement in this thread http://forum.xda-developers.com/viewtopic.php?t=4785 has a updated version of the upgrade tool, which does know 'WWE'.
More interesting things :
1.All rom files (extended / radio / ce rom) has countryid inside the files. However if the ms_.nbf passed the countryid check, the rest of the rom will be allowed to flash, even the country id is wrong.
2.If you just want to upgrade a radio that not belongs to that countryid, just rename the company name of the radio rom by hexeditor to the machine's countryid (it is in the first few lines of the radio.nbf),
3. I can't find the country id inside the nk.nbf but it seems himaupgradeut.exe may not regonize a nb.nbf from different upgrade set.
For safe , use the himaupgradeut.exe comes with nk.nbf to upgrade the cerom
4. If you want to upgrade the CE ROM will different countryid, you must upgrade the extended with modified countryid too.
For example, I want to upgrade the CEROM to T-Mobile 1.60 CE ROM, but I want to keep the O2 1.52 extended rom, I have to
a. mod the T-Mobile extended rom's country ID / CRC to O2 countryid /CRC
b. upgrade the moded t-mobile extended rom with himaupgradeut.exe
c. Your device is now recognized a a t-mobile device. Use T-Mobile's himaupgradeut.exe to upgrade the CE rom to T-Mobile 1.60.
d. mode the o2 extneded rom's country ID / CRC to T-Mobile's countryid /CRC
e. upgrade the moded o2 extended rom with himaupgradeut.exe
It looks like very stupid, so we need want a new adapt rom and we love XDA-developers 8) .
1: also the checksums is only verified for the nk.nbf
3: nk.nbf is encrypted, decrypt it with xda2nbftool. then you can see the countryid.
4: I saw that the extended rom, is where HimaGetDeviceData gets the language/country id from.
"XDA developer Itsme" the 8 hex digit number is not the country code, it is the sum of crc's of 256k blocks of data of the file.
Click to expand...
Click to collapse
ahhh ic.. :?
killercheung said:
It looks like very stupid, so we need want a new adapt rom and we love XDA-developers 8) .
Click to expand...
Click to collapse
I agree with this :wink:
I try to search difference between nk.nbf and the other version nk.nbf, the Qtek2020 ver 1.60 nk.nbf is almost the same as I-Mate 1.52 nk.nbf, but with T-Mobile, it is totally different.
I will still try untill my unit becomes a paper weight, just to get that countryID error. it should be flexible like the old one.
XDA developer Itsme said:
I found the bug, the problem is that the language of the device is reported as 'WWE'
maybe you can change one of the language identifiers in the binary of HimeUpgradeUt.exe.
or as I just noticed. the update tool in the Update.rar attachement in this thread http://forum.xda-developers.com/viewtopic.php?t=4785 has a updated version of the upgrade tool, which does know 'WWE'.
Click to expand...
Click to collapse
i get the update.rar from the files of I-mate 1.52.. I think the version is WWE. :roll:
XDA developer Itsme said:
1: also the checksums is only verified for the nk.nbf
3: nk.nbf is encrypted, decrypt it with xda2nbftool. then you can see the countryid.
4: I saw that the extended rom, is where HimaGetDeviceData gets the language/country id from.
Click to expand...
Click to collapse
Where can I possibly get this file "xda2nbftool"
Suceed!!!!!.. because I update Already my I-mate 1.52WWE Extended ROM to T-mobile 1.60 Extended ROM, I successfully update all the upgrade within T-mobile 1.60 (nk.nbf, ms_.nbf, radio_.nbf), The CountryID error didn't appear anymore, the upgrade that I done with Extended ROM change my Country ID to what ever Extended ROM I update my device, the countryID is in extended rom(ms_.nbf) , now everybody can change thier unit to whatever update they want.
Thanks for the Help of XDA-Developer Team. More power 8)
another thing I noticed is that the password used for the nk.nbf encryption is different for each upgrade tool version:
v0500 uses password 'HTC'
v0600 uses password '921211'
so, yet another update to my xda2nbftool
now also has an option to change the crcsum in the file.
Thanks for XDA developer Itsme again
Finally I can change countryid of a TMOBILE rom to flash on an O2 Device.
However I found that himaupgradeut.exe v0500 come with the TMOBILE can't flash the rom (It reported MODEL ID error), but v0600 is OK.
I got an XDA2 , it will report country ID error when use TMobile's upgrade utility, but I want to upgrade the CE ROM to TMOBILE 1.60 WWE version.
Here is what I did :
1. decrypt the T-Mobile 1.60 CE image
run "xda2nbftool -d nk.nbf nk.nba HTC"
Because T-Mobile 160 upgrade rom is come with himaupgradeut v0500, therefore the decrypt code is "HTC"
2. Use HEX Editor change the nk.nba countryid from T-MOBILE to O2 (It is in the first line of the rom)
3. update the crc checksum of the nk.nba
run "xda2nbftool -c nk.nba -u"
4. encrypt the T-Mobile 1.60 CE image. Because I cannot use himaupgradeut v0500 to update, I have to use v0600 and the encrypt code is 921211
run "xda2nbftool -e nk.nba nk.nbf 921211"
5. Run the himaugradeut.exe v0600 to upgrade your rom!
I got one more question.
Is that the rom content inside the decrypted nk.nba identical to the rom dump by xda2dump ?
Because I tried to copy a xda2dump version of XDA2 Chinese 1.52 rom and copy the content from address 0x1000h ( Something like D300A0E300F0 in HEX code) to the end, and overwrite the 0x411150h - the end of a TMOBILE 1.60 nk.nba with the chinese rom content , and fill the end of the file to 0x1f80030h with 00 . I can flash the rom to the device without any problem, but it stop in the 1st boot screen.
The chinese is working with the bootloader SD card upgrade method.
What's wrong with me?
Thanks.
XDA developer Itsme said:
another thing I noticed is that the password used for the nk.nbf encryption is different for each upgrade tool version:
v0500 uses password 'HTC'
v0600 uses password '921211'
so, yet another update to my xda2nbftool
now also has an option to change the crcsum in the file.
Click to expand...
Click to collapse
Hello XDA developer Itsme, can you send me this file/site "xda2nbftool", because i can not access it here, i think the site is forbiden here, thanks in advance
here are the tools attached
XDA developer Itsme said:
here are the tools attached
Click to expand...
Click to collapse
Thanks... :lol:
killercheung: it is almost the same. the decypted file has a 64 byte header, followed by the rom found with xda2dump at offset 0x80040000.
I don't think you can mix roms like you describe.
I have a Qtek 2020 from Dubai (the middle east), my Qtek has a 1.66.00WWE Rom and I want to upgrade it to 1.72WWE, I found a ROM for the iMate, is this ROM compatible (by compatible I mean will it work if I start the installer) or do I need to do something to.
I got the Rom from here
Code:
http://www.mtekk.com.au/browse/page423.html
Yes you can upgrade without problems, then, eventually, edit the extended rom to get rid of iMate unnecessary stuff (if there is any).
Salam Hussain
ther is already exist 1.72 original Rom for Qtwk2020
in this post page 9
http://forum.xda-developers.com/viewtopic.php?t=8403&postdays=0&postorder=asc&start=200
Hi Hussain,
Did you install the ROM. I too have same Qtek2020 and have downloaded the relavent Rm but would like to know if any one else has tried it and their experiences. :?:
Also I would like to put some of my standard software in ext ROM. How can I make cab files for the same and also put in registration info. If not directly at least a text file with my ids and regcodes so that I can hard reset even away from my PC.
how can i flash my rom to wm2003se....can anyone guide...izzit using the xda developers 3rd ver.zip or sin merge v2.0???
Read all the posts and decide for yourself which one is best to suit your needs. None of the ROM are perfect by any means.
Inproper flashing or mistakes in the flashing would render your unit useless. So do take note of the disclaimer carefully. Ultimately, you are responsible for what you do.
Just a note. Most of the questions and problem faced are already answered in the forum. So do read all of them and do not panic if your device failed to upgrade and become useless. Do a search in the forum and read more.
All the best in your quest for the rom upgrade.
WM2003SE
call me if you need help. i sure you know who i am.
Following are few DETAILED STEPS FOR NEWBIES to install WINDOWS MOBILE 2003 SECOND EDITION.
1. Download Windows Mobile 2003 Second Edition (DCS)
Run the .exe file and you are done and upgraded to wm2003se with builtin Radio Version 1.14.00
Download Windows Mobile 2003 Second Edition (Mysterman's Edition)
Run the .exe file and the upgrade process starts, sit back and wait till you get the "Congratulations" Screen.
(NOTE : Mysterman's wm2003se has its own radio file which is v1.14.00)
Some of you would like to upgrade to Windows Mobile 2003 Second Edition (Mysterman Edition) but would like to use a Radio Version of Mamaich (v1.18.00) here are the steps :
1. Download Windows Mobile 2003 Second Edition (Mysterman Edition)
Download 1.18.00 Radio Version by Mamaich
Create a new folder on your desktop and then right click on your .exe file of wm2003se(mysterman edition) and then click on winzip and then click on extract to and then extract the file to that new folder located on desktop.
Open that folder there you will find HimaClearJumpCode,HimaGetDeviceData,HimaUpgradeUt,ms_.nbf,nk.nbf & radio_.nbf.
Delete or cut radio_.nbf from that folder to some other folder and then extract radio_.nbf from Mamaich's 1.18.00 Radio Version.
Hit refresh in that folder and then double click HimaUpgradeUt.exe and the upgrade process starts, sit back and wait till you get the "Congratulations" Screen.
You are done with the installation of wm2003se(Mysterman Edition)with Radio v1.18.00 (Mamaich Edition)
Brief Introduction
Code:
As what I've promised before, it's right here. Please report for any existed
bugs.
For guys who think that the automatically running ActiveSync is a bug, you can
use the "patch" attached - but I myself don't think that it is.
ROM Information
MWG Atom Life WM6.1 ROM WWE_080410_B2_DS
OS Core: CE OS 5.2.21057 (Build 21057.1.6.10)
Pagepool Size: 6 MB
OEM Softwares Removed
Aplix Jblend
Quanta Image Editor
Quanta Media Album
Quanta Setup Wizard
Visual On Streaming Media Player
Westtek ClearVue PDF Viewer
OEM Softwares Implantated
All the MWG OEM softwares (Except those listed above)
Adobe Flash Lite 3.1 (IEActiveX version: 9.1.122.270)
Adobe Reader LE 2.5.1.0.404840.06
Arcsoft MMS Version 5.2.2.66
Cyberon Voice Speed Dial Version 1.2 Build 100303
Esmertec Jbed 20090506.2.1
HTC Boot Launcher Version 1.0.1915.2530.2
LockStream Version 1.2.20100721
Microsoft .NET Compact Framework Version 3.5.9198.0
Microsoft Internet Explorer Mobile Version 7.11
Microsoft Office Mobile Version 6.1
Microsoft SQL Server Compact 3.5.5692.0
Microsoft Windows Live for Windows Mobile Version 10.7.0059.0600.1000
Microsoft Windows Media Player 10 Mobile for Pocket PC Version 10.3 Build 21057
Visual On Streaming Source Filter Version 2.7.2014.1626.00
Downloads
MWG Atom Life WM6.1 ROM WWE_080410_B2_DS (52.54 MB)
Try it first..........
Could U give a screenshot ? And how many Free RAM with this ROM ?
( The 1st tester Lol......... )
Abhy-Boy said:
Could U give a screenshot ? And how many Free RAM with this ROM ?
( The 1st tester Lol......... )
Click to expand...
Click to collapse
Sorry, I can't. I've applied a lot of changes in settings and installed a couple of softwares into my device already...
But it is MWG-like. It can be regarded as an official update from MWG.
You're really the first one!
About the free RAM at startup... I can get over than 24,000 KB at the moment(I had installed a lot softwares). I didn't apply any changes to the cache of file system, which means the cache size is still 2 MB as default.
It's as much as you can get in the latest official WM6 ROM, right?
aa125690 said:
About the free RAM at startup... I can get over than 24,000 KB at the moment(I had installed a lot softwares). I didn't apply any changes to the cache of file system, which means the cache size is still 2 MB as default.
It's as much as you can get in the latest official WM6 ROM, right?
Click to expand...
Click to collapse
I hope Your new ROM can give more Free RAM. Your Build 21056 only give me about 13Mb Free RAM after install all application that I need. So hard download from Mediafire Lol..................
Have finished download, and now I'm using your ROM and add all Apllication ( and games too ) that I need. About 14,55 Mb Free of RAM and only have 651,71 Mb Free of Storage. Cool..............
Downloaded!!!!
how to install this .DIO file
Shoaib.Khan said:
Downloaded!!!!
how to install this .DIO file
Click to expand...
Click to collapse
Like Bajok! says :
HOW TO FLASH THE ROM:
1. You must have at least 70% battery.
2. Use mini-SD card and format it to FAT16 (use only 2GB capacity and below, don't use SDHC card!)
3. Copy AL1.DIO to card.
4. Insert card to memory slot of your device. Press and hold record button (beside the camera button) then push reset button with your stylus. Wait until BOOTLOADER mode appears saying "SD CARD DETECTED", release the record button.
5. Wait 'til it finishes until the O2 logo and splash screen appear. Follow the on screen steps. HAPPY FLASHING!!!
Thanks your ROM is very light, fast and battery usage is very good with this..
I surprised!! solved my problem for years on battery usage problems.
Just had to say thanks, sadly last week my old faithful HTC TYTN died, and i almost cried, and i had to get another PDA.
The one i got was an 02 Atom Life, however the stock rom wouldnt run some of the apps i use and depend apon, and couldnt do some basic stuff like send the USSD to get credit info (*100#), so i tried the official 6.1 update which still didnt run my app, or allow me access to my info, then i tried this Rom.
Everything goes again, (including USSD) ive tried your 6.5's but frankly I prefer this one alot much more, I just wanted you to know I appreciate your effort to the community.
The problem i have it they layout for the 6.5, do you have a 6.5 with the 6.1 Setup? If so i would gladly test it for you.
Regards
Andrew (New Zealand)
sastyh said:
Just had to say thanks, sadly last week my old faithful HTC TYTN died, and i almost cried, and i had to get another PDA.
The one i got was an 02 Atom Life, however the stock rom wouldnt run some of the apps i use and depend apon, and couldnt do some basic stuff like send the USSD to get credit info (*100#), so i tried the official 6.1 update which still didnt run my app, or allow me access to my info, then i tried this Rom.
Everything goes again, (including USSD) ive tried your 6.5's but frankly I prefer this one alot much more, I just wanted you to know I appreciate your effort to the community.
The problem i have it they layout for the 6.5, do you have a 6.5 with the 6.1 Setup? If so i would gladly test it for you.
Regards
Andrew (New Zealand)
Click to expand...
Click to collapse
I'm sorry, but I couldn't understand your last question... I beg your pardon?
Sorry, ill phrase it better,
with your WM6.5 roms i noticed they didnt have the standard start menu, like the WM5.0 / WM6.1, it instead your WM 6.5 has the touchflo type menu.
Is it possible to make a 6.5 rom without the touchflo ?
or can the touchflo be turned off so the old start menu works?
sastyh said:
Sorry, ill phrase it better,
with your WM6.5 roms i noticed they didnt have the standard start menu, like the WM5.0 / WM6.1, it instead your WM 6.5 has the touchflo type menu.
Is it possible to make a 6.5 rom without the touchflo ?
or can the touchflo be turned off so the old start menu works?
Click to expand...
Click to collapse
Yes... There're two ways that you could be able to use WM6.1-styled Start Menu, but both are not perfect neither:
1. Use the QuickMenu instead.
2. Recook a WM6.5 with a hexed shell32.exe file(by Sun_Dream in DFT) and other WM6.1 DPI and Lang *.dll files. I have just cooked one and that was under tweaked, but unfortunately my device broke again in the day before yesterday... So I'm afraid that you may have to cook it yourself.
My device is fixed now. I've got the thing you meant done, but themes of WM6.5 or later are not applicable for this ROM. The WM6.5 lockscreen and Titanium are not present as well...
So does anyone want to try that?
hi aa125690, been almost a year but this rom is fine!
I have a problem here =
1. when i flash the rom back to MWG original rom (.exe) through dsuu I can't find "wireless tab" under setting-connection-wifi.
2. same thing happen using original O2 wm5 or wm6 rom. no wireless tab inside.
I thought this was DSUU problem so I did =
3. using modified flash.dio as al1.dio from both original O2 rom (miniSD mode) resulting the same.
4. using modified flash.dio as al1.dio from original mwg rom (miniSD mode) resulting the same.
many hard-resets but they solve nothing. strange thing is = all rom from this xda-developer site (from you, bajok!, chrisch, etc, which are all minisd mode) are free from this problem. do you have any idea?
I just wanted to feel the "old feeling" when the atomlife was still on wm5 just like old time.