Related
Updated 25th September - Summary points added at bottom of post.
Updated 27th September - More detail concerning DeviceData and use of HEX editor added.
IMPORTANT: Updated 28th September - I now know that if you have bootloader v1.06 on your XDA II, you cannot downgrade your ROM (at the moment). We will see if we can find a way round this but cannot promise anything. My thanks to gerald8297 for his patience and help using his device and thus enabling me and him to determine this.
Please read all of this post before attempting any upgrade.
This post is the second of two posts and (hopefully) contains the solution to the Country ID error problem during upgrade/downgrade of the XDA II. The first post contains the background and conclusions to an investigation into the problem and can be found here:
ROM upgrade/downgrade Country ID errors - an investigation
If you haven't already done so, I recommend that you read it so that you are aware of the reasons for the following procedures.
Firstly, something I must say to protect myself .
The procedures described in this post are the ones I used on my own XDA II and they worked for me. Although they should work for anyone else, there can be no guarantee. I cannot be held responsible or liable for any damage to, or malfunction of, your device caused by a failed upgrade. By deciding to upgrade your XDA II, you are taking full responsibility for any consequences arising out of doing so, and you may void your warranty. Flashing the ROM may cause Data Loss or even Device Malfunction.
Secondly, I would like to acknowledge all the posters to this forum for, in one way or another, providing clues to the solution to this problem and also a big thank you to itsme and softworkz for the utilities and information that have proved so helpful. And, of course, thanks to my friend merlin_uk whose input was invaluable.
These procedures require the following tools:
xda2nbftool: A description, explanation of passwords required, examples of usage and a download link for xda2nbftool are here.
A Hex editor: Any Hex Editor will do, but this is the one I used and which I describe the use of here.
IMPORTANT: Make a full backup of your XDA II as all data in main memory will be erased. Storage card and storage data should remain intact (but don't take my word for it!).
NOTE: The passwords specified in the commands and the exact format I used may be different for you depending on the version of HimaUpgradeUt you intend to use. See here for more information. Also, the operator and language strings used by me may be different to those you need to use. Don't just copy the commands listed below verbatim. Check what you need first. In my case my original operator ID was O2, but it got changed to CDL because of the reasons stated in my first post. Therefore, I wanted to get my device back to O2. This meant, for the first upgrade, using CDL as the operator ID in the nbf headers (to get past the verification) and O2 in the extra block of data (to set my device back), and then for the second upgrade, I was able to specify the correct operator for me (O2) in the nbf headers.
Obtain the set of upgrade files you require. If you have an operator-provided .EXE file, you can extract the files using Winzip or Winrar. The set of files will normally consist of:
[list:def15107cd]HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf
[*]Copy all these files into a folder of your choice on your PC (it is probably easier to create a new folder), then copy the xda2nbftool.exe program into the same folder.
[*]Copy the HimaGetDeviceData.exe file to any folder on your device.
Warning: DO NOT under any circumstances copy and run HimaClearJumpCode.exe on your device as it will render it unbootable. It is used by the upgrade utility to put you device into bootloader mode prior to upgrading.
[*]Execute HimaGetDeviceData.exe on your device. There will be no visible indication that it has run, but it will produce a file called DeviceData.txt in the Windows folder of the device.
Here is an example of the contents of DeviceData.txt:
Code:
U S B 3 2 1 . 7 2 . 0 0 W W E P H 1 0 C D L W W E 1 . 7 2 . 1 2 6 1 . 1 4 . 0 0
"USB 32 1.72.00WWE " is the OS Version
"PH10" is the Device Type
"CDL" is the Operator ID
"WWE" is the Language ID
"1.72.126" is the Extended ROM Version
"1.14.00" is the Radio Version
Obviously the actual content will depend on your device, but the layout of the information will be the same.
[*]Copy the DeviceData.txt file to your PC and open it using Notepad. Make a note of the current operator ID and language ID specified in this file (see step 4 above), for use later. These values are what your device is currently set to and it may surprise you to find that they are different from what you expected!. I will refer to these noted values as <operator> and <language>, to avoid confusion with specific values.
[*]Start a command prompt session on your PC and set your current directory to the folder used in step 2.
[*]Extract the decrypted versions of the nbf files by entering the following commands at the command prompt (but see note above):
Code:
xda2nbftool -x NK.nbf NK.nba 0x20040304
xda2nbftool -x ms_.nbf ms_.nba 0x20040305
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
[*]Now modify the operator and language strings in the nbfs using the values noted from the DeviceData.txt file above by entering the following commands at the command prompt substituting <operator> and <language> with the noted values (but see note above):
Code:
xda2nbftool -sd PH10 -so <operator> -sl <language> NK.nba
xda2nbftool -sd PH10 -so <operator> -sl <language> ms_.nba
xda2nbftool -sd PH10 -so <operator> -sl <language> Radio_.nba
[*]Run the hex editor and in that open the file ms_.nba. If you are using xvi32, it will display the hex contents of the file to the left of the window and the character representation to the right of the window. At offset 74 (0x4A) you will see the operator string your device will be set to and at offset 94 (0x5E) you will see the language string your device will be set to.
NB. Your device will be set to these values irrespective of the values specified in the normal nbf headers.
To change the operator ID:
Click on the Address menu item then click on Goto.
In the window that is displayed, ensure decimal and absolute are selected, type 74 into the entry field then click OK. This will position you at the operator string location.
Using either character entry on the right or hex entry on the left, enter the operator string device should be (or what you want it to be ). Note that any non-used character positions should be edited to contain null (0x00) which can only be entered in the left hand side of the window.
To change the language ID:
Again, click on the Address menu item then click on Goto.
In the window that is displayed, ensure decimal and absolute are selected, type 94 into the entry field then click OK. This will position you at the language string location.
Using either character entry on the right or hex entry on the left, enter the language string your device should be. Again, any non-used character positions should be edited to contain null (0x00) which can only be entered in the left hand side of the window.
[*]Save the ms_.nba file.
[*]Update the crc values for each of the decrypted files by entering the following commands at the command prompt:
Code:
xda2nbftool -c -u NK.nba
xda2nbftool -c -u ms_.nba
xda2nbftool -c -u Radio_.nba
[*]Encrypt the files back into the nbf files by entering the following commands at the command prompt (but see note above):
Code:
xda2nbftool -x NK.nba NK.nbf 0x20040304
xda2nbftool -x ms_.nba ms_.nbf 0x20040305
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
[*]Delete the nba files using Windows Explorer or by entering the following command at the command prompt:
Code:
del *.nba
[*]Run the upgrade from Windows Explorer by executing HimaUpGradeUt.exe
The first part of the upgrade is the verification process which is non-destructive, in which it generates the DeviceData.txt file on the device then compares the information in it to the information in your nbf headers (specifically the device type, the operator and the language). If an error is displayed, double check the steps detailed above and try again.
If all is well it will then display the current and new settings and give you the option to proceed with the upgrade. If you cancel at this point, nothing has changed on your device.
[*]Click the upgrade button... ONLY if you want to proceed with the upgrade.
Go make a coffee or even dinner because it takes at least 30 minutes to complete the full upgrade.
As eDsuB has pointed out, it is possible that the upgrade will fail or stop for some other reason and you are left with the bootloader screen (screen is dark and may display 'SERIAL' or 'USB'). If this happens, don't be too alarmed. Just remove your device from the cradle, reset your device, replace it in the cradle and restart the upgrade.
You may even still hit a Country ID error after it has started the upgrade, but I believe that it is some other sort of problem and it just reports it as Country ID error. If you do end up with a bootloader screen, and this was the first of two upgrades, it is OK to restart the upgrade using the second one - that is, the one with the nbf headers and the extra data in ms_.nbf set to the correct language and operator.
[*]Once the 'Congratulations' window appears, the upgrade is complete (even though the device may still indicate that the radio upgrade is in progress).
[*]Remove you device from the cradle and hard reset.[/list:def15107cd]
Hopefully your XDA II is now upgraded/downgraded.
To summarise
If, as was the case with me, you have successfully run a previous upgrade and your device has been unwittingly configured with an incorrect operator ID, you will need to run the steps detailed above twice. The first time, it is purely to set the device's language and operator IDs back to their correct values, with the nbf headers needing to be set to the incorrect values in order to allow the upgrade to proceed. The second time then becomes the 'real' upgrade, because, this time, in step 8, you will be using the desired language and operator IDs which will now match those of your device.
The information specified in the extra block of data in the operators ROM image (ms_.nbf) is used to set the device/operator/language in the device. It doesn't need to match what the device is set to already. It is this information which HimaGetDeviceData will retrieve at the beginning of any subsequent upgrade and return via the DeviceData.txt file.
The information specified in the nbf headers of all the ROM images (NK.nbf, ms_.nbf and Radio_.nbf) is used to set the device/operator/language in the software of the device. It must match the device/operator/language currently specified in the device.
Neither the ER2003Edit tool nor xda2nbftool, by themselves, update the extra block of data in the ROM image.
Anyone upgrading should check and amend (using step 9), if necessary, the information contained in the extra block of data in the operators ROM before performing any upgrade. This should be done even if the nbf headers are already correctly configured. Failure to check could lead to your device being set to an unwanted operator ID or language ID at the end of the upgrade.
Feedback concerning these procedures is most welcome. If any errors or omissions exist, please post a reply to let me know so that I can correct them. Also, please post a reply if you upgrade successfully, stating the original version/operator/language and the new version/operator/language. By doing this it will help others decide whether to upgrade or not.
You are missing a possible step that often occurs during 15.
The upgrade is canceled because of some vague reason and the device is stuck in bootloader (USB or SERIAL on screen).
This is the point when cold sweat starts drippingof your forehead . . .
Remedy: Reset device and restart the upgrade. It will take longer than 30 minutes. I flashed two times now and this happened both times . . .(didnt have any country-id or language issues)
Also: In the posting you should mention the operator you use is CDL (chances are that people take your posting literally wich for sure get a lot in the country-id trouble.)
Thanks to edsub for his comments. His advice has been incorporated into the post.
maybe this post should be sticky so it will not be lost in the mists of time
A new hope is born
Impressive discoery by dcs.
Anyway, can anyone confirm that this method is usable or workable for downgrading imate ver1.72WWE to Asia Rom 1.60 WWE.
One major doubt that, if the xda2 is in 1.72 and presumably it was wrong operator coded CDL, so the changes (suggestion by dcs) should take place on the 1.72 imate rom again or the 1.60 Asia Rom.
I once tried to change the 1.60 Rom using er2000edit to set the operator name to CDL instead of O2. The first upgrade screen was passed successfully but i was blocked in the 2nd screen which left me cold dead xda2 with 1.06 serial.
I guess much research shall be done before pursing this method. Anyhow it was a good finding. :lol:
This method does work…
I too was in a position were I could not upgrade or downgrade my O2 XDAII ROM because the operator code on the device had been changed to CDL…
Following dcs’s method sorts this nasty problem out once and for all – I can now downgrade, upgrade to any version of ROM I want!!!
Nice one dcs!!
I have exactly the same problem like yours. Thanks to dcs for your hard work.
I have updated the post slightly to (hopefully) lessen confusion about operator and language values used.
maybe incorporate this post in wiki.xda-developers.com ?
Answer to gerald8297 post - A new hope is born
Theoretically it shouldn't matter which version of the upgrade you run first.
The first upgrade is done purely to set your device operator and language values back to the values they should be (or the values you want them to be), and the nbf headers will have to match the values currently defined in your device.
The second upgrade is done to actually install the version of software you want onto your device. The nbf headers should be configured to match the (now correct) operator and language values defined in the device. Also the ms_.nbf file should be checked to ensure the extra block of data isn't going to set your device back to an unwanted value.
You say that your previous attempt at a downgrade failed at the second screen. Do you mean that the OS was installed, but it failed at the extended ROM part? If so, did you edit all 3 nbf file with ER2003Edit to set the operator before running the upgrade? If you only edited the NK.nbf file it would explain what happened. If this is the case, and you are stuck on the bootloader screen, you should be able to reset your device and rerun the upgrade.
It looks like you used the same i-mate 1.172.00WWE upgrade as I did in which case your device has been set to operator CDL and language WWE.
Good luck!
I have updated the post by adding some summary points at the end. These, hopefully will provide a better overall understanding.
FINALLY!!!!! IT WORKED!!! Thanks 102035492304923049 million times, dcs. This is the manual to use!
Excellent! I am very pleased.
Updates Made
I have made a few changes to the post to try and make things a little clearer
IMPORTANT
Updated with information about downgrading restriction.
dcs,
I am now at step 13
I edited ms_.nba ONLY using the hex editor. The 74th block is set the CDL so i changed it to O2 and put a null value on the 76th block where L of CDL used to be.
WWE remains as WWE. I am about to proceed but just a few questions.
(1)since this is my first upgrade, i need only run this once right?
(2) is ms_.nba the only file i need to edit or i also need to edit the Radio_.nba and NK.nba files?
So after upgrading... my xda2 should be 1.72 WWE and 1.17 radio right?
Thanks for all the updates on your post. Things are getting a bit clearer.
i3oyi3astos said:
dcs,
I am now at step 13
I edited ms_.nba ONLY using the hex editor. The 74th block is set the CDL so i changed it to O2 and put a null value on the 76th block where L of CDL used to be.
WWE remains as WWE. I am about to proceed but just a few questions.
(1)since this is my first upgrade, i need only run this once right?
(2) is ms_.nba the only file i need to edit or i also need to edit the Radio_.nba and NK.nba files?
So after upgrading... my xda2 should be 1.72 WWE and 1.17 radio right?
Thanks for all the updates on your post. Things are getting a bit clearer.
Click to expand...
Click to collapse
(1) As it is your first upgrade, you should only need to run it once, as long as the your device information (retrieved in DeviceData.txt) is already set to the values you want (in your case, O2 and WWE). Two upgrades are required only if the device information is incorrect to start with.
(2) Only the ms_.nba file requires editing with the hex editor.
You can see what versions of OS, Extended ROM, and Radio you are upgrading to in step 14, before you click the Upgrade button.
Hopefully, all should progress OK now
@dcs: This topic is getting better and better.
I would vote to have your info instead on the wiki pages instead of the info that is there now on upgrading.
Because there is a risk of others still wanting to stick to the old info, for starters you may want to setup a new wiki page that is linked to from the old 'upgrade' wiki page.
Its quite simple to create a wiki page, as I have just experienced for a subject on IIWPO.
I have stumbled upon sumthing last night.....
1. Waxx's Rom would make my XDA2 a CDL Device right? (I upgraded without modification of Waxx's ROM)
2. Waxx's ROM uses O2 headers (verified through ER2003edit) and the extra code on MS_.nbf says its CDL
3. If I loaded Waxx's ROM (which I did) it would turn my unit from an O2 to CDL.... correct? I could not verify since my GETDEVICE Data does not work... I dunno why.
4. Here comes the weird part..... I followed your instructions to modify my operator to become O2 again..... (change headers and offset 74).... If I understand it correctly, I should change Waxx's ROM headers from O2 to CDL ( to pass the operator test..am I correct?) and I should change OFFSET 74 to O2... correct?
5. When I tried upgrading.... (all headers = CDL, Offset = O2).... the upgrade failed.... error 120 (country code error...me thinks)....
6. I tried changing all headers to O2 and offset was still set to O2..... tried a second time..... and it worked.... get device data works now.... and it says I have an O2 machine
7. IMO Radio rom 1.17 is better than 1.14..... thanks for your help mr DCS, Mr Waxx, Mr. Gollum
Z-man said:
I have stumbled upon sumthing last night.....
1. Waxx's Rom would make my XDA2 a CDL Device right? (I upgraded without modification of Waxx's ROM)
2. Waxx's ROM uses O2 headers (verified through ER2003edit) and the extra code on MS_.nbf says its CDL
3. If I loaded Waxx's ROM (which I did) it would turn my unit from an O2 to CDL.... correct? I could not verify since my GETDEVICE Data does not work... I dunno why.
4. Here comes the weird part..... I followed your instructions to modify my operator to become O2 again..... (change headers and offset 74).... If I understand it correctly, I should change Waxx's ROM headers from O2 to CDL ( to pass the operator test..am I correct?) and I should change OFFSET 74 to O2... correct?
5. When I tried upgrading.... (all headers = CDL, Offset = O2).... the upgrade failed.... error 120 (country code error...me thinks)....
6. I tried changing all headers to O2 and offset was still set to O2..... tried a second time..... and it worked.... get device data works now.... and it says I have an O2 machine
7. IMO Radio rom 1.17 is better than 1.14..... thanks for your help mr DCS, Mr Waxx, Mr. Gollum
Click to expand...
Click to collapse
I think the error must have been related to the problem with HimaGetDeviceData, because everything you did was correct and your assumptions were also correct. Perhaps the first attempt failed, but at the same time it sorted out the HimaGetDeviceData, and also got as far as setting your device to O2?
Difficult to say what happened exactly, but main thing is you are up and running - Well Done!
I'm truly sorry about the delay.
I've finally got round to posting a a STAR100 SuperCID guide.
1. Get itsutils: http://www.xs4all.nl/~itsme/projects/xda/tools.html
2. Run pdocread.exe with no args. Take a note of the "uniqueid" value.
3. Run "pdocread -n 1 0x000000 0x10000 -b 0x4000 original-bdk1.nb" - you'll get a file.
4. Head over to http://www.spv-developers.com/strtrkCID/. Feed it the DOCID and the file you got from steps 2 and 3. It'll give you back anoter file.
5. Run "pdocwrite -n 1 patchedfile.bin 0x000000 0x10000 -b 0x4000" where patchedfile.bin is obviously to be replaced with the patched file you got from step 4.
6. There is no 6. Report feedback.
Click to expand...
Click to collapse
All credit goes to itsme - he wrote all the tools and scripts which made all this possible.
Spawning script: perl startrek_cidedit.pl cid1e62995dd1db197b00b697388760b5e3.bin -i DOPOD601 -c 11111111 -o supercid1e62995.bin 2>&1
decrypting
bufend=44bdd4609845fd0931a871b4a31ddba42d4b96386f9 e9c5dff947c035432fc15
result=b2c7c4eede400853eb232eba436f394b3d75a9adf4c e9a1e452b26ea9059dc59
sha64k=8a7e3a8462b8c851ac125710d44abc05da4916f215e 331f98420db7ae5d87a5d
buffer checksum failed
why ?
Looks like the DOCID value you entered is incorrect. It should be a long stream of hex numbers.
Fantastic !!! Working Ok on SPV F600. Now, we need how to simunlock this smartphone.
Thank you very much Zone Mr.
i run pdocread in step 1 and got a dos screen that desaper in a second,and were i find the file in step 2.
Zone-MR said:
Looks like the DOCID value you entered is incorrect. It should be a long stream of hex numbers.
Click to expand...
Click to collapse
thank you Zone-MR,can u tell me how to get a long stream of hex numbers.
wlinsong said:
thank you Zone-MR,can u tell me how to get a long stream of hex numbers.
Click to expand...
Click to collapse
i know how to do,thank Zone-MR very very much
is there someone know how to flash rom use T-flash Card?
someone can't get the docid ,because you must use the old one!
I tried to do first step but when I ran pdocread.exe I get the following message :
Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart activesync
or maybe your device is application-locked.
I've app-unlocked my device, activesync works ok, and restarting does not help. Phone is Qtek8500.
Any ideas?
Thanks
Is the script to calculate CID area for startrek available?
I think this should use the same method on Artemis or Herald, the problem is that they have G4 DOC and we'll not be able to use pdocwrite, but on those phones we're already able to place a hacked SPL in mem with psetmem.exe and jump into it's address with modified haret version. If we have the right CID area we can use the hacked SPL to flash it.
sorry for the ignorance...
I have downloaded itsutils but where is the dpocread.exe??
do I have to connect to the device with the mtty??
Maybe a bit more explanation
I've CID unlocked my Qtek 8500 and installed new ROM 3.6.251.0. Thanks Zone, great work!
Maybe it would be useful to write more detailed instructions, so here it is :
1. Application unlock your phone using regeditstg and do the following :
HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000 1001 = 2 -->Change the value data from 2 to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000 1005 = 16 --> Change the value data from 16 to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000 1017 = 128 --> Change the value data from 128 to 144
Reboot the phone
2. Run SDA_ApplicationUnlock tool. Reboot the phone after it finishes.
3. Download itsutil.zip from http://www.xs4all.nl/~itsme/projects/xda/tools.html , version from 2005-6-28. There is even newer version, but with that version you can not use pdocread without arguments.
4. Connect the phone with activesync
5. Run Command Prompt, go to subfolder named "build" in itsutils folder, and run pdocread without arguments
6. Note the value of "uniqueid". It will be something like : "00 00 00 00 12 03 02 14 3b 07 1b b2 04 05 07 54"
7. run pdocread again with these arguments : "pdocread -n 1 0x000000 0x10000 -b 0x4000 original-bdk1.nb". This will make original-bdk1.nb file in build folder (where the pdocread is located).
8. Upload this file and value of uniqueid to http://www.spv-developers.com/strtrkCID/. It will open a new page after few seconds. Go to bottom of the page and click the link "Download patched BDK1"
9. Download the file (it will be named like "supercidxxxxxxx.bin) to "build" folder
10. Run the pdocwrite from command prompt with these arguments : "pdocwrite -n 1 supercidxxxxxxx.bin 0x000000 0x10000 -b 0x4000". Replace supercidxxxxxxx.bin with the original name of downloaded file from step 9.
11. Wait 15-20 seconds and that is it. Reboot the phone and install the ROM you like
It works! I've got now 3.6.251.0_02.67.30 on my Qtek!
Thank's, damird, your guide is unreplaceble for such lamers like me
But maybe anyone can suggest me were can i find and how to install (if it possible) Russian t9 or only russian lang to input? Or maybe how to rollback to original ROM with this that lang... (1.02.261.1)
Thank's
added:
Problem's gone, Russian T9 added.
Damird!
Cheers mate
Hello, can you share with us this script to calculate CID area in StarTrek?
With this script we can SimUnlock the StarTrek very easy (at least I think...)
Thank you very much.
I'm confused here... is CID unlock not the same with SIM unlock?
my carrier is tmob but I'm getting cing 3125 at ebay so I need to SIM unlock the phone for it to work on tmob right?
wow, pof, I can't wait for it! i had bought one herald in China but wireless was disable by default. I hope I could unlock the CID and get a WWE rom to enable the wireless.
sokelut said:
I'm confused here... is CID unlock not the same with SIM unlock?
my carrier is tmob but I'm getting cing 3125 at ebay so I need to SIM unlock the phone for it to work on tmob right?
Click to expand...
Click to collapse
Correct, you still need to pay to carrier unlock the phone. Check the wiki for links to a few services that are known to work.
CID unlock? Error installing ROM
I'm getting an ERROR [294] INVALID VENDER ID
I did the CID unlock
It starts to install the rom but when it gets to 4% I get this error. How do i fix this?
Can anyone help?!
Need a little clarification
Im stuck in steps 3-11. I've downloaded itsutils and I don't know how to proceed.
What is this file ???
Is it aku 3.3 in english or russian????
-----------------------
MODERATOR EDIT:
Changed the subject, use this as the main thread to discuss HTC 2.05 WWE AKU 3.3 ROM issues.
Download and ROM details in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
BE SURE TO READ THE WIKI BEFORE ASKING QUESTIONS PLEASE
English.
If you need Russian one look for it in Upload/Temp directory
It is in English, I just flashed it using 1.10mfg method
An still no MUI I presume ?
What Where Who Its New The Wwe Version?
Plz Give The Link And Why Dont You Say Anything?
bubu23 said:
What Where Who Its New The Wwe Version?
Plz Give The Link And Why Dont You Say Anything?
Click to expand...
Click to collapse
ftp://ftp.xda-developers.com/Uploads/Hermes/
Here you have.
BuT WhY TyPinG LikE ThAt ! Are YoU PaRkInsOn ?
Is it from HTC or cingular? I've heard both are about to release an AKU 3.3 rom
loll no im not parkinston maybe my keboard is
but why the file finish with test?
its not good its just test???
plz tell me im horny on that fileee(rom)
English confirmed.
Just flushed OS and Ext rom.
ROM Version:2.05.255.1
ROM Date: 01/17/07
ExtROM Version: 2.05.255.101
OS 5.1.461 (build 15671.3.3.0)
I can't get to FTP :/ what user and password ?
reg
Sar
Username = xda
Password = xda
You get to the ftp by this link no pass needed...
ftp://xda:[email protected]/Hermes/
Cheers
Seems very fast...
cant see where it says TEST though. My of been a test for the carriers, so likely the RTM for the carriers to then implement.
So far, so good... at least this one is english, unlike the Swedish update i did yesterday
in the ftp thers only the swedish rom i cant find the wwe rom??
RUU_Hermes_2.05.263.1_6275_1.34.00.10_108_SVE_HTCEUR.exe is now up... Guessing it is an official release from htc?
Cheers
Well i flashed it also.
the Test is included in the splash.bmp. =)
really... But imho the swedish one is a bit faster, but that is just subjectiv i didnt tried to test it with a benchmark program.
btw. any update from cingular?
Somethings fishy about this.
This is supposed to be AKU 3.3, but theres no WPA2 support???
not sure this is a complete ROM?
Does this mean MS Voice Command over bluetooth is fixed without the hacks?
I have detect problems with this rom! Is better wait for another!
Problems detect:
- No wpa2
- Phone connection always breaking down
- Can't go to my contacts!
- ActiveSync always says pocket is out of memory (yes I reset several times)
Flash Using Lnb
This is my first time flashing using lnb and i followed the wiki about using mtty..i just wanted an experimented persons to examine the output of mtty and tell me if the update was perfectly done and if there was no problems in nand please...
Thanks
Iverson....
USB>
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 461
Storage Total block: 475
Total Bad Block in CE: 0
NeedToEraseBlockStart: 474
Storage format success
USB>lnb 06_OS.nb
:F=06_OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image downloadSH
Load ADDR: 501A0000 Length: 3C0C800
*********************************************
*********************************************
*********************************************
*********************************************
*********************************************
*********LAST BLOCK, dwBytesCollected=0x13800
Code entry point at 0x53DA0000
Write Nand Success
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 473
Storage Total block: 463
Total Bad Block in CE: 0
NeedToEraseBlockStart: 486
Storage format success
USB>
Fix:
- Input Types: (注音) + (倉頡) + (手寫) + (全螢幕手寫) works with no doubt
- relpllog.exe error exixts if 手寫(mboxcht.dll) is called, i dunno why, have checked so many versions from ATOM LIFE to ATOM AKU2.2....still finding. But I think 全螢幕手寫 is good enough.
- Finally I am able to change the program links in the initflashfiles.dat to unicode 16
- SMS issue: If you have SMS issue, please go to phone - options - service and check the SMS default gateway number, for HK it is +8536800852 somewhat like that, just change it to the number your operator provided.
Programs added:
- Total Commander
- Regedit
- pBar
- 1 extra IME is hidden (CHS 併音), a registry hack need to apply in order to activate this IME
Download Link: http://www.mediafire.com/?ffklanjl2gy
Missing eBoot.nbo: http://www.mediafire.com/?1xrxmtlymrz
If you do not want a CHT version WM6 but wanna have CHT input, check this: http://forum.xda-developers.com/showthread.php?t=332012
Version:
Windows Mobile 6 Professional AKU0.3.0
CE OS 5.2.1413(17913.0.3.0)
NEVER ATTEMPT TO FLASH WM6 USING SD CARD FLASHING!!!
Upgrade Procedure:
1. just extract the rar file and flash you phone in BOOT LOADER MODE!!!
Congratulations!!! Great stuff.
Anybody know whats happen with me?
Atom show
Mar 29 2006
CPLD Ver:A0060109
.
.
.
Downloading progress:100%
Usb Transfer Completed
Write Bootloader...
Please wait...
I reflash Xda-Atom-CHT-20060426-MOT0822 and its worked(Thanks God)
Goodbye WM6..
How about atom exec?
Would that be released soon as well?
help ~....
nthan said:
Anybody know whats happen with me?
Atom show
Mar 29 2006
CPLD Ver:A0060109
.
.
.
Downloading progress:100%
Usb Transfer Completed
Write Bootloader...
Please wait...
Click to expand...
Click to collapse
i faced the same problem too ~!oh my god ~! ~!~ some more i can't open my atom now ~! ? jst the screen show up update utility `!??? isn't it the rom spoil d ?~!~? help me pls ~! ........
Guys....
the rar file consists of 6 files:
- (268,288)7zr.exe
- (258,048)Device Software Update Utiltity.exe
- (65,536,012)diskimage_Ver.nb0
- (16,384,000)ExtendedROM.img
- (110,261)nova_pda_033105.mot
- (6,022,611)vl1d_pda_Ver.mot
- (524,288)eBoot.nb0 - http://www.mediafire.com/?1xrxmtlymrz
If one of these files are missing / corrupted, the upgrade / flash will failed.
Here are the size the dump screen
dcoloane said:
Guys....
the rar file consists of 6 files:
- (268,288)7zr.exe
- (258,048)Device Software Update Utiltity.exe
- (65,536,012)diskimage_Ver.nb0
- (16,384,000)ExtendedROM.img
- (110,261)nova_pda_033105.mot
- (6,022,611)vl1d_pda_Ver.mot
If one of these files are missing / corrupted, the upgrade / flash will failed.
Here are the size the dump screen
Click to expand...
Click to collapse
Hi dcoloane
It seems the CHT input doesn't compatible with the WM6 WWE version so is possible to rip the original CHT handwriting file to be cab let us try this ????
Or just translate the CHS 0.4 to CHT is much faster to solve the problem ?
dcoloane said:
Guys....
the rar file consists of 6 files:
- (268,288)7zr.exe
- (258,048)Device Software Update Utiltity.exe
- (65,536,012)diskimage_Ver.nb0
- (16,384,000)ExtendedROM.img
- (110,261)nova_pda_033105.mot
- (6,022,611)vl1d_pda_Ver.mot
If one of these files are missing / corrupted, the upgrade / flash will failed.
Here are the size the dump screen
Click to expand...
Click to collapse
i think this folder must have eboot.nb0 to completed rom-update
Missing eboot.nbo
tube216 said:
i think this folder must have eboot.nb0 to completed rom-update
Click to expand...
Click to collapse
You are correct.......................sh.......there are too many versions in my PC now and I forgot to dump a eboot.nbo to the rar file!
That's why.................thank you tube216.........
Sorry guys, mmmmissing the most important file for eBoot
http://www.mediafire.com/?1xrxmtlymrz
I'm using pArtizAn's WM 6.1 Pro Rom, but this amazing Rom only supports xt9 for Russian and English. I'm a German and writing SMS without t9 really sucks!
So I was looking for a Language Pack like they exist for the Standard-Roms.
I found this Language Pack from MoDaCo. I installed it and - contrary to all other exisiting Language Packs - the t9-key was working and I was able to write with the dictionary, but the keymapping was totally mixed up!
Eg. my Hardware-Button 2 was mapped to 1, e & r (so if I wanted to type an r in the ABC-Mode, I had to press the HardwareButton 2 twice !)
Or if I wanted to write "test" with dictionary I had to press 3,2,6,3 instead of 8,3,7,8!
So I tried to copy only the 2 Files "hpd.5x4.German.kdb" & "DElsUN_xt9.ldb" from the cab to my windows-dir and I modified/created this 3 registryvalues:
"HKLM\Software\Tegic\eT9\IME\KDbFiles\0607" value = "hpd.5x4.German.kdb"
"HKLM\Software\Tegic\eT9\LdbFiles\0107" value = "DElsUN_xt9.ldb"
And appended on the 3 value (HKLM\SOFTWARE\Tegic\eT9\AvailableLanguages) ",0107"
After that, the keymapping was correct! But after selecting German in the XT9-Menu, it wasn't displayed in the XT9-Menu to be selected, but by typing with the dictionary the t9 suggested me some german words and by selecting them, the xt9-bar freezed and was visible everywhere until I did a softreset.
Let's simply say: It acted really confused!
My guess is, that this is connected with the file eT9.HQD.kdb
So. Is there any genius out who can help me???
post german language pack here.
i will add it in the next release, maybe.
Yes, please! I'd really appreciate that! Thank you!!!
XT9 German.zip:
The 2 language-files I suppose to be responsable for german.
Is this enough or should I try to upload the cab including Czech, Danish, German, English, Spanish, Finnish, French, Italian, Dutch, Norwegian, Polish, Portugese, Russian & Swedish ???
I had some troubles uploading this file - I guess my Connection is too slow (512 kbit up) and the server is getting into a timeout. But I can also put the file on my server and send you a direct download link via PM for this file (also tried to upload it via URL - no chance!)
When are we going to get the pleasure of a new wounderful release? I'm looking almost every day on this site to be the first downloader of the new release
Hi
Same Problem here... I hope Erofich can do this...
StefanV3
Med0ric0 said:
When are we going to get the pleasure of a new wounderful release?
Click to expand...
Click to collapse
In the middle/end of May, when i will get startrek.
Erofich said:
In the middle/end of May, when i will get startrek.
Click to expand...
Click to collapse
... So you are going to make me a birthday-gift
PS: Thanks for all your past, present and future work on this ROMs!!!
Hi
Yesterday i've played araound with the files from HTC Touch Dual. Is there anyone who can tell me how to edit key mapping??? The current keymapping is:
Code:
key letter/symbols
"1" !; w; q
"2" 1; e; r
"3" 2; z; t
"4" 3; u; i; ü
"5" .; o; ö; p
"6" ?; s; a; ä
"7" 4; d; f
"8" 5; h; g
"9" 6; k; j
"0" ,; l; s
The files are from http://forum.xda-developers.com/showpost.php?p=1672748&postcount=4 and the howto i used is here: http://forum.xda-developers.com/showpost.php?p=1946530&postcount=263
I know that these are files from HTC Niki that uses a 5x4 keypad but how to change to 3x4??? I couldn't find a 3x4 xt9 kdb file for pocket pc.
StefanV3
Hi
Thanks for mailing me. But there is no need to upload it because it is available here at http://melgurth.ovh.org/index.php?page=downloads .
But, could you tell us how to activate it??? I installed it but i don't know how to activate it. There is no menu entry...
StefanV3
Hi
@ husbender
Thanks, i will try it again. Did you really mean the '#' key??? In private message you told me that you holding down the '*' key. '#' key gives me the list with symbols...
Back to Topic:
I've played around again with the files from the XT9 lang pack from the first post of this topic. It should be that the problem is related to the kdb files that Erofich uses for english and russian xt9. It should be special ones for the qtek keyboard. Is this right Erofich??? Could you tell us how to develope a german kdb file???
StefanV3
Hi
Please send it...
Stefan
Thank you very much for your help, husbender.
But this t9 languagepack isn't working on my WM 6.1 Pro Rom. After the installation I'm only able to write numbers and I'm unable to open the t9 menu by pressing the *-key! So I've uninstalled it and everything went back to normal - without a German t9...
I'm looking forward to Erofichs new rom /w german t9 or someone who could remap the keys from the t9 shadow languagepack.
But thank you husbender!
I'm looking for Spanish xT9
Hi, does somebody have the file Spanish xT9 only?
because I found a international languages, but i don't need all the other ones.
Thanks