get the upgrade file - RUU16006WWE_T-mobile_NL.exe
run the upgrade, wait for it to unpack, don't click on any buttons.
find the directory where it is unpacked, in
probably in "\Documents and Settings\yourname\Local Settings\Temp"
there should be a subdirectory, containing these files:
HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf
alternatively you can unpack the file with winrar.
to find the desired devicedata by copying HimaGetDeviceData.exe
to your device, and running it, it will create a file called
'\Windows\DeviceData.txt' this should contain the following
information ( you may need a hex viewer to see this )
"USB 32 1.60.00WWE "
"PH10" -> '-sd' option
"Qtek" -> '-so' option
"WWE" -> '-sl' option
"1.60.06"
"1.06.01"
download the upgrade.rar from this posting:
http://forum.xda-developers.com/viewtopic.php?t=4785
unpack it in the same directory, this will overwrite the
HimaUpgradeUt.exe with a newer version.
download xda2nbftool.exe from this page
http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html
decrypt the NK.nbf with:
xda2nbftool -d NK.nbf nk.nba HTC
modify the devicetype, operator and language strings in the nbfs:
xda2nbftool -sd PH10 -so Qtek -sl WWE -v ms_.nbf
xda2nbftool -sd PH10 -so Qtek -sl WWE -v Radio_.nbf
xda2nbftool -sd PH10 -so Qtek -sl WWE -v nk.nba
( this will also update the checksums in the files )
encrypt the nk file again, with the new password:
xda2nbftool -e nk.nba NK.nbf 921211
now run the upgrade tool.
ROM Upgrade 1.60.21WWE
Do I need to do anything else beside to double click the downloaded ruu16021wwe_dangaard.exe?
I'm a little anxious to just execute this file reading your 'how to install the t-mobile update'. Or can I just run the application, because it is an Dangaard Qtek ROM?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
that's great
Thanks
Othman
Thank you for all
I did the dangaard french upgrade with my MDA2 O2rom, and it works perfectly.
I had to change the language with xda2nbftool, but it was very simple.
One thing, freench rom is less complete than O2's, but I'm going to put some software on my viewable Extended rom...
Thanks a lot once .
Upgrading from WWE Tmobile160NL to new Danggard french 158
ainat said:
I did the dangaard french upgrade with my MDA2 O2rom, and it works perfectly.
I had to change the language with xda2nbftool, but it was very simple.
One thing, freench rom is less complete than O2's, but I'm going to put some software on my viewable Extended rom...
Thanks a lot once .
Click to expand...
Click to collapse
Hello Would you have a step by step guide to upgrade from Tmobile 160 NL WWE to the Dangaard french rom you are refering to? I'm a bit stucked, i have to admit
Awaiting your help, i remain
Arnaud
Rom Upgrade
I tried several times and I followed the steps. I keep getting this message . Image File Checksum Error The Rom image file to be used for the update is corrupt Download the correct Rom update and try again. I download twice and I am still getting the same error. Can u Plz assist me and tell me what could be the problem
Make shure you have the latest version of the xda2nbftool.
There was a problem with one version.
on which command do you get this?
can you run the above commands with a '-v' option added?
and download the most recent version from http://www.xs4all.nl/~itsme/projects/xda/xda2nbftool.exe
it is working
Thank u Itsme . I have used the new version and it is ok now.
sim tool kit help
I have two voice Gsm numbers in one simcard and I used to change from one to another using simtool kit . but then I upgrade my i-mate Rom(from carrier device) to new version of carrier device . then the prb starts. now if I want to move from one number to the other I ahave to do a soft rest after I choose the number. I cannot navigate between the numbers like I used to. I changed my Rom to T-mobile thinking it will solve the prb but the prb still remains. can any body help. maybe I can hear from Itsme .
thanks
Re: instructions + tools how to upgrade qtek 1.52 to tmobile
Itsme said:
get the upgrade file - RUU16006WWE_T-mobile_NL.exe
run the upgrade, wait for it to unpack, don't click on any buttons.
find the directory where it is unpacked, in
probably in "\Documents and Settings\yourname\Local Settings\Temp"
there should be a subdirectory, containing these files:
HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf
alternatively you can unpack the file with winrar.
to find the desired devicedata by copying HimaGetDeviceData.exe
to your device, and running it, it will create a file called
'\Windows\DeviceData.txt' this should contain the following
information ( you may need a hex viewer to see this )
"USB 32 1.60.00WWE "
"PH10" -> '-sd' option
"Qtek" -> '-so' option
"WWE" -> '-sl' option
"1.60.06"
"1.06.01"
download the upgrade.rar from this posting:
http://forum.xda-developers.com/viewtopic.php?t=4785
unpack it in the same directory, this will overwrite the
HimaUpgradeUt.exe with a newer version.
download xda2nbftool.exe from this page
http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html
decrypt the NK.nbf with:
xda2nbftool -d NK.nbf nk.nba HTC
modify the devicetype, operator and language strings in the nbfs:
xda2nbftool -sd PH10 -so Qtek -sl WWE -v ms_.nbf
xda2nbftool -sd PH10 -so Qtek -sl WWE -v Radio_.nbf
xda2nbftool -sd PH10 -so Qtek -sl WWE -v nk.nba
( this will also update the checksums in the files )
encrypt the nk file again, with the new password:
xda2nbftool -e nk.nba NK.nbf 921211
now run the upgrade tool.
Click to expand...
Click to collapse
You are so great!
Thank you very much, I've lost the way.
From O2 1.03.00 USA -> Qtek 1.60.00WWE -> T-Mobile 1.60.06
I found that Qtek is not suitable for me.
Thanks again.
Hi itsme, I run the HimaGetDeviceData.exe and my DeviceData.txt shows the following:
USB 32 1.03.00USA
1.03.31
1.05.14
Why don't I see your other lines
"PH10" -> '-sd' option
"Qtek" -> '-so' option
"WWE" -> '-sl' option
and what does PH10 mean ?
I got an XDA II from O2
help appreciated, thanks
my DeviceData.txt shows the following, too:
USB 32 1.03.00USA
1.03.31
1.05.14
but other people have the following:
U S B 3 2 1 . 0 3 . 0 0 U S A
P H 1 0
O 2 A S I A
W W E
1 . 0 3 . 4 3
1 . 0 5 . 1 4
why my uk o2 xda II miss the info????
maybe you are not using a correct file viewing tool? ( 'strings' for instance will not display strings shorter than 4 characters )
wit the '->' lines I mean 'this value goes after the ... option'
What's new in 1.60
I have a 1.52 Orange M1000 - and since Orange has told me, that have no plans to upgrade I am considering an update.
Could a kind soul please make a short list of changes/improvements from 1.52 to 1.60 ?
That would help me make a decision to upgrade or not.
Right now I have few problems..
Regards
Michael
oneall said:
why my uk o2 xda II miss the info????
Click to expand...
Click to collapse
You need a hex editor to properly view the file, like XVI32.
Can be downloaded @ http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
failure to update asian O2 XDA-2 with T-Mobile 1.60
Tried to use this procedure to upgrade my revived XDA-II to 1.60 to no avail, the update procedure (taken from Update.rar) complains about wrong country code. My batch file to convert *.nbf files is as follows:
xda2nbftool -d NK.nbf nk.nba HTC
xda2nbftool -sd PH10 -so O2ASIA -sl WWE -v ms_.nbf
xda2nbftool -sd PH10 -so O2ASIA -sl WWE -v Radio_.nbf
xda2nbftool -sd PH10 -so O2ASIA -sl WWE -v nk.nba
xda2nbftool -e nk.nba NK.nbf 921211
My DeviceData.txt is as follows:
USB 32 1.03.00 USA
PH10
O2ASIA
WWE
1.03.43
1.05.14
Any ideas why it may happen? O2ASIA, WWE and PH10 are listed in HIMAUpgradeUt.exe
Use O2 instead of O2ASIA.
Jos said:
Use O2 instead of O2ASIA.
Click to expand...
Click to collapse
Thanks, it helped! Now we'll see if the result will be working with our service provider (they do not support any PDAs at all, even MMS does not work )
decrypt the NK.nbf with:
xda2nbftool -d NK.nbf nk.nba HTC
How to run xda2nbftool.exe? when i double clicking the file it just open up the command prompt in the background where I cannot access it.
Rom is downloaded from the iMate server and transferred to our XDA ftp server.
Code:
When you use er2003edit you have to use these passwords:
NK.nbf = 0x20040304
ms_.nbf = 0x20040305
radio_.nbf = 0x20040306
Dont forget when you open a rom file you have to unselect AUTO DETECT ROM.
So when you open the nk.nbf file make sure you selected OS ROM.
And for ms_.nbf you selected EXTENDED ROM
And for radio_.nbf you selected RADIO ROM
Didn't test it myself, so no I don't have a clue what this rom is like.
You can discuss it in this thread.
Cheers
Panja
I have to test a new 32 MB rom that has been packaged as a nk.bin file.
The special HimaUpgradeUt lets me bypass bootloader 1.06 protection.
So I'd like to transform my nk.bin into a nk.nbf.
Is there some command line tool that allows to to this?
Thanks,
There is such a tool. It is your favorite hex-editor. Take any NBA file, and paste there your BIN just after the header. Then encrypt with xda2nbftool and flash.
nk.nbf generated this way does not boot
sorry but I'm stuck at bootloader level after flashing.
I took the .nba header (17 912 bytes), appended the .bin files (32 500 000 bytes), appended spaces to fill the exact nk.nba file (33 554 496 bytes), re-crypted the .nba into .nk.nbf, flashed with himupgradeut.exe, but no joy. Where may I be wrong?
thanks for your hint,
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
orefkov posted that
Test your SPL - can you hardspled him with gene_hspl_HT8x.
1. Copy bkondisk.exe and bk1.lnk on your device, at root (no memcard).
2. Run bk1.lnk on device. File bk_06_0001.img is appear on device.
3. Compare that file with spl.bin file (use WinHex, TotalCommander or other file compare programm)
If no difference in those files, you can run gene_hspl_HT8x.exe on your device.
Attached Files
File Type: zip test spl.zip (173.3 KB, 58 views)
Click to expand...
Click to collapse
i tried this test spl
after comparing file with hex workshop it shows file matched.
but my device specifications
gene 100
inbl 1.07.000
spl 1.07.000
radio 2.79.90
os 1.07.000
rom version 1.7.455.2wwe
protocol 4.1.13.34
so i think it will work on ht7xx
but i have no courage to change spl
my respected seniors plz clear my mind
thanks!!!!
this is test spl
http://forum.xda-developers.com/attachment.php?attachmentid=114180&d=1221807994