Hi,
I recently upgraded to WM2003SE, this introduced some errors om my Q-Tek 2020 which is why i want to downgrade to the original image.
I downloaded 'HI_TMNL_17200_190_11700_Ship.exe' from the T-Mobile (NL) site, but when trying to execute it it shows "Country ID error" and stops.
I searched the forum and found a post the said i could use the no_id patch. After reading the instructions i found out that this patch needs the extracted files, but i only have the .exe i downloaded.
Can someone give me some advice?
Cheers,
-peter
Run the .exe file and press next ONCE. (this extracts the files)
open file explorer on your pc and navigate to C:\Documents and Settings\YOUR NAME\Local Settings\Temp
in this directory there should be a temp directory (mine was called pftA4.tmp)
the ROM images are located in this directory.
once you cancel the .exe program the files are deleted, so copy them to a new directory to save them.
Good luck.
Thanks, i managed to get the files!
I've been reading a lot on the forum lately, and in particular this post:
http://forum.xda-developers.com/viewtopic.php?t=12101
When trying to get the xor keys with the command 'xda2nbftool.exe -t' it only shows the xor keys for "ms_.nbf" and "Radio_.nbf".
I'm missing they key for "nk.nbf" while the file does exist and is in the current directory.
I tried this command on two rom's and both did not gave me the nk.nbf xor key.
G:\peter\Officele T-Mobile image>xda2nbftool.exe -t
xda2nbftool -x ms_.nbf ms_.nba 0x20040305
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
Another "push" in the right direction would be appriciated
-P
search the ftp
i do beleave that god toenailed has already decompressed that files
check in the ftp
Thanks rictec, but i looked all over the ftp today but didnt find it.
Nevertheless, the xda2nbftool.exe should be able to decompress my files right? Do you know why i'm not getting a xor key for that file (nk.nbf)?
Cheers,
-P
Could anyone please help me out?
I'm still in the dark about why i can't get the key from the nk.nbf file using xda2nfbtool.exe
Help would really be appriciated!
-peter
Related
Do you want to upgrade from T-Mobile 1.60 to Dangaard 1.60.21???
This is what you have to do step by step:
1) download ruu16021wwe_dangaard.zip from the ftp specified in the post here in the forum
2) Unpack the zip file, then click with the right button on the extracted file (ruu16021wwe_dangaard.exe, make sure
you've winzip installed) and select extract to. Choose a folder where you'd like to put all the upgrade files
3) download xda2nbftool.exe from this page:
http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html and put the file in the
created folder
4) Open the MS-DOS prompt, go to the folder where all files are unpacked and digit the following
instructions:
xda2nbftool -d NK.nbf nk.nba 921211 (enter)
xda2nbftool -sd PH10 -so TMobile -sl WWE -v ms_.nbf (enter)
xda2nbftool -sd PH10 -so TMobile -sl WWE -v Radio_.nbf (enter)
xda2nbftool -sd PH10 -so TMobile -sl WWE -v nk.nba (enter)
xda2nbftool -e nk.nba NK.nbf 921211 (enter)
5) Now launch the upgrade file and enjoy!
This procedure could be adapted to any rom changes. The important thing is setting the right password for the HimaUpgradeUt.exe file. Pass is HTC for 0500 version and 921211 for 0600
version.
Many thanks to XDA developer Itsme for the support!!!
Thanks mate! I'll give it a try when I get home from my work.
Yesterday I unfortunately updated to 1.60 T-Mobile, So today I've started from T-Mobile 1.60 rom, then I’ve made all explained at the beginning of this post, ok?
But surely you can start from rom 1.52 and upgrade directly to 1.60, but you’ve to change T-Mobile with Qtek from the MS-DOS instructions, ok?
Hello:
What are the benefits of the upgrade? Is it better radio stack (GPRS and BT)? Is it the ROM itself?
Thanks for your input?
Fernando
So does this look ok?
http://www33.brinkster.com/popsiwarez/screen.jpg
(needs to be opened in a new window, please cut&paste to new browser window, ¤&/% brinkster)
Just thought the new CE image version looks a bit odd, but I guess thats what happended after the commands on the file, just wanna be sure before I hit the upgrade button. So after I have installed this T mobile upgrade the one from Qtek should work.. right...
Again thanks!
cannot access to the page you linked !
cannot access to the page you linked !
I'm sorry for my silly question. I got confused.
This method is for T-Mobile 1.60 to Qtek_Dangaard 1.60.21. However I can't find where ruu16021wwe_dangaard.exe is applied. I can see only the TMobile being extracted and updated. Does it mean we have to rea-apply the Dangaard update after this procedure? :?
Accessed!
Stop!!!!
It's wrong!!
From which Rom do you start (which is the rom you've installed?)
I got the T-mobile installed, and want the Qtek one...
You should see:
To:
CE Image version: 1.60.00
Extended image version: 1.60.21
Radio version: 1.06.01
Have you follow my instructions???
Sorry
There's a mistake in the rom link I've posted
The right rom image is the follow:
ruu16021wwe_dangaard.exe
Download it from the ftp indicated in previous posts
But you say you do the changes to the RUU16006WWE_T-mobile_NL.zip Sure you don't mean the Qtek one, since this is what I will install?
You'll find the rom here:
http://forum.xda-developers.com/viewtopic.php?t=4857
That's what I thought... Good thing I didn't install the modded T-mobile I made 8)
spanky said:
Sorry
There's a mistake in the rom link I've posted
The right rom image is the follow:
ruu16021wwe_dangaard.exe
Download it from the ftp indicated in previous posts
Click to expand...
Click to collapse
That's what i thought. Now I got it
Re: Read!How to upgrade from TMobile 1.60 to Dangaard 1.60.2
spanky said:
Do you want to upgrade from T-Mobile 1.60 to Dangaard 1.60.21???
This is what you have to do step by step:
1) download RUU16006WWE_T-mobile_NL.zip from the ftp specified in the post here in the forum
2) Unpack the zip file, then click with the right button on the extracted file (RUU16006WWE_T-mobile_NL.exe, make sure
you've winzip installed) and select extract to. Choose a folder where you'd like to put all the upgrade files
3) download xda2nbftool.exe from this page:
http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html and put the file in the
created folder
4) Open the MS-DOS prompt, go to the folder where all files are unpacked and digit the following
instructions:
xda2nbftool -d NK.nbf nk.nba 921211 (enter)
xda2nbftool -sd PH10 -so TMobile -sl WWE -v ms_.nbf (enter)
xda2nbftool -sd PH10 -so TMobile -sl WWE -v Radio_.nbf (enter)
xda2nbftool -sd PH10 -so TMobile -sl WWE -v nk.nba (enter)
xda2nbftool -e nk.nba NK.nbf 921211 (enter)
5) Now launch the upgrade file and enjoy!
This procedure could be adapted to any rom changes. The important thing is setting the right password for the HimaUpgradeUt.exe file. Pass is HTC for 0500 version and 921211 for 0600
version.
Many thanks to XDA developer Itsme for the support!!!
Click to expand...
Click to collapse
So here this should be:
ruu16021wwe_dangaard.exe
2) Unpack the zip file, then click with the right button on the extracted file (ruu16021wwe_dangaard.exe, make sure
you've winzip installed) and select extract to. Choose a folder where you'd like to put all the upgrade files
yes it is
Now I've correct the original post!
spanky said:
yes it is
Now I've correct the original post!
Click to expand...
Click to collapse
Nice work!!
Now is there somebody kind enough to cook a custom extended ROM (taking the best from O2, TMobile and Qtek)? i couldn't do it myself 'coz I do'nt have a Linux box..
Works flawlessly ... after having been a T-Mobile machine, my O2 XDA II now is a Qtek one ... hehehe
Unfortunately this did not eliminate the write protection on my Extended Rom.
I recently purchased an i-mate PPC with CDL's buggy ROM version 1.66 and would like to downgrade to 1.52 which I have downloaded from their site. The only problem is that shortly after it gets to the "Stage 1, erasing existing ROM", it aborts with Error CE 112, "perform soft reset and try again". The only option I have been able to do after that is to reload 1.66.
I figured this out and thought I would post my solution for others.
The 1.66 upgrade file from CDL uses a different version of HimaUpgradeUt.exe than the 1.52 version. So I had to unencrypt the files using the version level from the 1.52 release and then re-encrypt with 1.66 version level and then load the older(1.52) files with the newer HimaUpgradeUt.exe.
hi;
how did you decrypt and recrypt the files, did you use the xda2nbftool soft ware ??. Also, why didn't you think of upgrading to tmob 1.72 instead of downgrading to 1.52??
Yes, I used xda2nbftool. Pretty much followed the instructions from http://wiki.xda-developers.com/wiki/HimalayaRomFlashing.
I didn't go to 1.72 because I was concerned about warranty issues. I figured if I was only downgrading to CDL's own release, which is a solution on their site, I had a better chance of staying within warranty.
artiemon, if I can give you an FTP login/pass, would you be willing to upload a zip file with your modified .nbfs and the hima*.exe's so I can try to downgrade my phone. I've tried your instructions a few times but keep getting a verticle white line down the right of my screen. I'd very much appreciate it.
Jon.
Jon,
I deleted the nbf files when I was done, but here is specifically what I did to create them.
Download both ruu152113wwe_cdl-sku1.exe and ruu166131wwe_cdl_sku1.exe from clubimate.com under the device suport link. Run ruu152113wwe_cdl-sku1.exe and wait for it to unpack but don't click on any buttons. While the dialog box is still up, find the directory where it is unpacked in "\Documents and Settings\yourname\Local Settings\Temp". Mine was in a directory that started with pft.
The subdirectory should contain these files:
HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf
Copy them to a new subdirectory on you machine. From that directory, copy HimaGetDeviceData.exe to your PPC and execute from there. This will create '\Windows\DeviceData.txt' on your PPC. Copy this to your PC to determine the current Operator on your PPC. Mine was still CDL.
Get a copy of xda2nbftool at http://wiki.xda-developers.com/wiki/xda2nbftool and copy it into the new subdirectory with your extracted files. The 1.52 ROM version was encrypted at the 0.9.1.0 version of HimaUpgradeUt.exe, so decrypt the 3 files as follows from a command line in your new subdirectory:
xda2nbftool -x NK.nbf nk.nba 0x89124137
xda2nbftool -x ms_.nbf ms_.nba 0x25863614
xda2nbftool -x radio_.nbf radio_.nba 0x12345678
Since you are not changing Operators, you should not need to run the following, but I did anyway.
xda2nbftool -sd PH10 -so CDL -sl WWE -v ms_.nba
xda2nbftool -sd PH10 -so CDL -sl WWE -v Radio_.nba
xda2nbftool -sd PH10 -so CDL -sl WWE -v nk.nba
Now run ruu166131wwe_cdl_sku1.exe and wait for it to unpack but don't click on any buttons. Again, find the new temporary folder under "\Documents and Settings\yourname\Local Settings\Temp". The only file you need out of here is HimaUpgradeUt.exe, so copy it to your working subdirectory replacing the one from 1.52 ROM. The 1.66 ROM version was encrypted at the 1.0.0.0 version of HimaUpgradeUt.exe, so encrypt the 3 files as follows from a command line in your new subdirectory:
xda2nbftool -x NK.nba nk.nbf 0x20040304
xda2nbftool -x ms_.nba ms_.nbf 0x20040305
xda2nbftool -x radio_.nba radio_.nbf 0x20040306
Then all I did was run HimaUpgradeUt.exe from the command line and after about 75 minutes I had an i-mate at version 1.52 ROM.
Good luck,
artiemon
Well, I followed your instructions and still have a blasted white line running down the right side of my screen. I had another older version of 1.52 and it had the same problem.
I'm really getting annoyed!
Jon,
Are you able to load 1.66 as downloaded without any issues?
When I was originally having trouble with downgrading, I was always left with just a bootloader screen(1.06). But I could always get back to 1.66 without an issue.
If you can't get 1.66 to load, you may have a different issue than I had.
No, I can get the 1.66 to load back up without a problem, no matter what.
I don't really have any other suggestions for 1.52.
I did find that the bluetooth headset functionality in 1.52 was not acceptable and decided to go to 1.60 from O2. Here is the link. http://www.xda-2.co.uk/downloads/xda2_upgrade_download.html. I've been on it for 4 days and am very happy. It has an O2 splash at startup instead of i-mate and some other O2 specific junk I had to delete. The phone interface looks a little different, but it was way more stable than CDL's 1.66 and my Jabra headset is working great. Clear type looks pretty good too. If you're not to squimish about a non-imate ROM, give it a whirl.
I found a fix in 1.66 by changing a registry key to make the incoming COM port for bluetooth 5 instead of 4 (its under HKLM\Drivers\BuiltIn). You simply change the Index value from 4 to 5 and my sd-gps started working. I have a bad feeling my sandisk card is dead though.
Jon.
After looking for some tuts on upgrading my mda II to wm2003se i destroyed my pda, well works pda but still mine and i'm gutted.
i downloaded wm2003se from here. After not being able to get anything to work i transfered the contents of the files to sd card. then i tried booting the files on pda.
I got to 1 of these
HimaClearJumpCode
HimaGetDeviceData
xda2nbftool
then the pda reseted to
a dead screen.
all i see at the top of the screen is seriel and at the bottom is v1.06 and if i plug the cradle in the serial goes to usb?
Can i fix this myself or is my boss gonna be having it in for me?
Regards.
1 thing i know for sure, i'll not do this again
This is file i dl
Himalaya_WM2003SE_Upgrade
Your device is in bootloader mode...
Put the XDa back into the cradle and on the PC start the upgrade program again.
Brgds
Pat
Yes it is stuck in bootloader. The problem i have when running the upgrade is that the upgrade is meant for o2 xda not tmobile mda II.
I know i need to change the id and have read the read me on changing the id but i do not know how to extract nbf files so i can do this
The nbf files are configured for operator ID O2 and language ID WWE. If you need to change these, carry out all the steps below. If they are OK for you, go straight to step 5.
1. Extract the decrypted versions of the nbf files by entering the following commands at the command prompt:
xda2nbftool -x NK.nbf NK.nba 0x20040304
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
2. Modify the operator ID in the nbfs to the value you require by entering the following commands at the command prompt substituting <operator> with the required value:
xda2nbftool -sd PH10 -so <operator> -sl WWE NK.nba
xda2nbftool -sd PH10 -so <operator> -sl WWE Radio_.nba
3. Update the crc values for each of the decrypted files by entering the following commands at the command prompt:
xda2nbftool -c -u NK.nba
xda2nbftool -c -u Radio_.nba
4. Encrypt the files back into the nbf files by entering the following commands at the command prompt:
xda2nbftool -x NK.nba NK.nbf 0x20040304
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
what am i supposed to do with this lot?
Yes, that's what you have to do.
You can also download the rom editor from here and change the values with the editor. Get the rom editor from here:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Good luck'
Patric
You can also download the rom editor from here and change the values with the editor. Get the rom editor from here:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Good luck'
Patric
Click to expand...
Click to collapse
Thanks dude, the error of my ways has been playing on my mind all day.
The Mda II is now working again and is all cool. I do have and O2 boot up screen on my T-mobile MdaII and thats cool cos my t-mibile sim card works aswell.
BUT!!
1 big problem we have is that 4 or 5 of our mda's have no camera function.
Upgrading the os was only to get the cameras working so that i could get my mates cameras working, now my Mda has no camera function.Lol.
forum.xda-developers.com has many files but there is so much to search through that i find myself going round in circles in the search. Can i please ask for more help in getting my camera working.
Regards
1 thing after another eh! I find myself buzzing with joy at my upgrade but still there is a darkness lurking.
Ps
ER2003Edit is exelent, a true life saver and so simple and easy to use, thanks to the creators on that 1.
Go to the FTP section
ftp://ftp.xda-developers.com
Login as xda and xda (all in small letters)
Go to the Himalaya section. You will find there many extended ROM for 2003SE to download. Download one EXTROM, open in EREDITOR and extract the Camera cab from there.
Install the cab on your XDA.
Cheers
Pat
Go to the FTP section
ftp://ftp.xda-developers.com
Login as xda and xda (all in small letters)
Click to expand...
Click to collapse
Exellant info, thanks. Luckily i know about ftp so i can now finish this post.
Thanks to all peeps who have given me there time!
Regards...Mike
Please help! Being an avid user (I really enjoy the old system environment I was using), but not that much of a "techie". I've managed to create for myself an interesting problem/ concern. I followed a link here in xda-developers and I foolishly tried upgrading my system through the following: Himalaya_WM2003SE_Upgrade and HIMA_WM_2K3_EXTROM. I need to and want to restore back to my old system. Please help me!!!
Note: Not being a consumate techie, but a user, I may have overlooked a something below... But I desperately need to restore.
"I obtained (with many thanks to fychan) a memory image of an English version of WM2003 SE which is an earlier version than the recent Chinese release, but it is genuine English. I managed to create an installable NK.nbf file from this. Also, mamaich has provided the version 1.18 Radio upgrade included here. Many thanks to mamaich for that and also for some advice when I was building the OS nbf file. Also, mamaich has provided some CAB files for Extended ROM which I have also attached here separately.
Attached is an upgrade for Himalaya devices to WM2003 SE WWE, Radio 1.18. Unzip the attachment into a folder of your choice. The nbf files are configured for operator ID O2 and language ID WWE. If you need to change these, carry out all the steps below. If they are OK for you, go straight to step 5.
1. Extract the decrypted versions of the nbf files by entering the following commands at the command prompt:
Code:
xda2nbftool -x NK.nbf NK.nba 0x20040304
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
2.
3. Modify the operator ID in the nbfs to the value you require by entering the following commands at the command prompt substituting <operator> with the required value:
Code:
xda2nbftool -sd PH10 -so <operator> -sl WWE NK.nba
xda2nbftool -sd PH10 -so <operator> -sl WWE Radio_.nba
4.
5. 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 Radio_.nba
6.
7. Encrypt the files back into the nbf files by entering the following commands at the command prompt:
Code:
xda2nbftool -x NK.nba NK.nbf 0x20040304
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
8.
9. Place your device in the cradle, ensuring that the cradle is plugged directly into a USB port on your PC and not to a hub and that the power supply is connected to the cradle. It is also a good idea to disable any screensavers.
10. Run HimaUpgradeUt.exe
11. Sit back and wait for the Congratulations screen to be displayed on your PC. Your device will still be displaying 'Upgrading radio stack, please wait', but as long as the PC says it is done, then its all OK.
Notes:
a. I have installed this upgrade on my XDA II without any problems, and have also been able to revert back to the 1.72 ROM I had installed previously. I have bootloader v1.01, and I don't know whether it would be any different for later versions of bootloader.
b. After upgrading, a hard reset takes places and the Extended ROM is installed. I found that several applications caused a 'Application may not display properly.....' message box to appear which required tapping to dismiss. Therefore, you will need to make sure that TPDisable.exe is not run in the Config.txt script in the Extended ROM, otherwise you will not be able to respond to the messages.
Edit: I've created a .BAT file which can be run from a DOS prompt to replace steps 1-4...
Usage: OperatorUpdate operatorID
where operatorID is O2 or CDL or TMOBILE, etc.
Just unzip the attached zip file.
________________________________________
OperatorUpdate.zip
Description: Update operator ID in .nbf files.
Download
Filename: OperatorUpdate.zip
Filesize: 528 Bytes
Downloaded: 4289 Time(s)
________________________________________
________________________________________
HIMA_WM_2K3_EXTROM.RAR
Description: Extended ROM CABs
Download
Filename: HIMA_WM_2K3_EXTROM.RAR
Filesize: 2.88 MB
Downloaded: 9422 Time(s)
________________________________________
________________________________________
Himalaya_WM2003SE_Upgrade.zip
Description: OS and Radio
Download
Filename: Himalaya_WM2003SE_Upgrade.zip
Filesize: 17.52 MB
Downloaded: 17787 Time(s)
________________________________________"
now ,i has download the tools:
1.xda2nbftool
2.xda3nbftool
3.O2 xdaIIs 1.42 WWE rom
and I find the rom's uncompress password is:
nk.nbf 0x20040304
ms_.nbf 0x20040305
(ex:xda3nbftool -x NK.nbf nk.nba 0x20040304)
but the xda3nbftool always show:Warning:This does not look like a nbf header ,possible you provided the wrong password.
can anybody help me?
I have the same question,anybody can help?
Maybe you should post it in teh correct part of the forum. This have nothing to do with the Wallaby device....
Stefan