On www.qtek.nu, there is a new ROM (1.22.169WWE) available, with Radio, WLAN and Bluetooth updated.
Has anyone the correct link to the file? Has anyone found out what exactly was updated??
A
http://www.qtek.nu/files/BA_WWE_BP_12200_169_10602_SHIP.zip
Qtek9090 said:
On www.qtek.nu, there is a new ROM (1.22.169WWE) available, with Radio, WLAN and Bluetooth updated.
Has anyone the correct link to the file? Has anyone found out what exactly was updated??
A
Click to expand...
Click to collapse
I have tried the Dangaard Norwegian Rom, has 1.22.167 Extended and the 106.02 Radio Rom. Nearly the same as the Rom Qtek.nu has released. I was having problem with the radio (GSM) and have decided to put back the old Qtek Rom version 122.126.
I think I will wait this 122.169 Qtek rom.
will it be good this rom for the pda2k??
thank you
to see when the sack imate....
Do not seem to work
Tried this, said wrong password ???
when i run the xda3nbftool
Any ide´s
Re: Do not seem to work
backspace said:
Tried this, said wrong password ???
when i run the xda3nbftool
Any ide´s
Click to expand...
Click to collapse
Hi,
Also wrong password. My fix.bat (with German MDAIII with English ROM) works fine with BA_WWE_BP_12200_126_10600_SHIP.exe but not with this version. Please see log if it can help to solve problem.
Regards
Log:
D:\Test>fix
D:\Test>xda3nbftool -x ms_.nbf ms_.nba 0x20040522
WARNING: this does not look like a nbf header, possible you provided the wrong password
D:\Test>xda3nbftool -x nk.nbf nk.nba 0x20040521
WARNING: this does not look like a nbf header, possible you provided the wrong password
D:\Test>xda3nbftool -x radio_.nbf radio_.nba 0x20040523
WARNING: this does not look like a nbf header, possible you provided the wrong password
D:\Test>xda3nbftool -sd PH20B -so T-MOB101 -sl GER ms_.nba
D:\Test>xda3nbftool -sd PH20B -so T-MOB101 -sl GER nk.nba
D:\Test>xda3nbftool -sd PH20B -so T-MOB101 -sl GER radio_.nba
D:\Test>xda3nbftool -c -u NK.nba
updated checksum to 9f20466f
D:\Test>xda3nbftool -c -u ms_.nba
updated checksum to a895061e
D:\Test>xda3nbftool -c -u Radio_.nba
updated checksum to 472abd49
D:\Test>xda3nbftool -x ms_.nba ms_.nbf 0x20040522
D:\Test>xda3nbftool -x nk.nba nk.nbf 0x20040521
D:\Test>xda3nbftool -x radio_.nba radio_.nbf 0x20040523
D:\Test>del *.nba
D:\Test>
Does somebody has the correct checksum to make the tool work ?
maybe this has something to do with the incorrect password/checksum
http://forum.xda-developers.com/viewtopic.php?t=14877
Why I made my own ROM
Hi there,
I have a SVP M2000 from Orange France. I hate french OS, so the first thing I have done was to upgrade it to English (it's a stupid I cannot configure the French buit-in keyboard in French when I use an English ROM... but I wait for the project here to reconfigure the keyboard! :lol: )
I have tried all roms here for the Blue Angel and I wasn't really satisfied with any of them, so I have taken the best of all to make my own and my SPV M2000 works great.
My little story:
My first upgrade was the english version from Qtek BA_WWE_BP_12200_126_10600_SHIP.exe but I had some small problems. My SPV M2000 sometimes had a strange behaviour and I had to do a soft reset.
Then I tried the PDA2k_WWE_12200_162_10600_SHIP.exe and those problems disappeared. As the Radio and the Windows ROMs are identical, I thought the problems with the Qtek version were in the extended ROM.
When I heard that the french version for Qtek BA_FRE_BP_12202_558_10602_SHIP.exe had radio ROM version 10602 (and as there's not localization for the radio stack) I decided to use it.
I tried then both english versions (Qtek BA_WWE_BP_12200_126_10600_SHIP.exe and i-mate PDA2k_WWE_12200_162_10600_SHIP.exe) with the file radio_.nbf from BA_FRE_BP_12202_558_10602_SHIP.exe but with the Qtek version I had now some problems with the radio and bluetooth.
I got very excited when I heard about the norwegian version BA_WWE_BP_12200_169_10602_SHIP.exe but I had the same checksum problems described here using the xda3nbftool.
Finally, I decided to use PDA2k_WWE_12200_162_10600_SHIP.exe and replace the original radio_nbf file (10600) with the radio _.nbf file from BA_FRE_BP_12202_558_10602_SHIP.exe
Now, I don't have any problems with the radio nor with the Extended ROM from Qtek BA_WWE_BP_12200_126_10600_SHIP.exe!!!
Hope this helps
anyone figured out the password yet???
Re: Why I made my own ROM
You got this file to share
ArtZ said:
Hi there,
I have a SVP M2000 from Orange France. I hate french OS, so the first thing I have done was to upgrade it to English (it's a stupid I cannot configure the French buit-in keyboard in French when I use an English ROM... but I wait for the project here to reconfigure the keyboard! :lol: )
I have tried all roms here for the Blue Angel and I wasn't really satisfied with any of them, so I have taken the best of all to make my own and my SPV M2000 works great.
My little story:
My first upgrade was the english version from Qtek BA_WWE_BP_12200_126_10600_SHIP.exe but I had some small problems. My SPV M2000 sometimes had a strange behaviour and I had to do a soft reset.
Then I tried the PDA2k_WWE_12200_162_10600_SHIP.exe and those problems disappeared. As the Radio and the Windows ROMs are identical, I thought the problems with the Qtek version were in the extended ROM.
When I heard that the french version for Qtek BA_FRE_BP_12202_558_10602_SHIP.exe had radio ROM version 10602 (and as there's not localization for the radio stack) I decided to use it.
I tried then both english versions (Qtek BA_WWE_BP_12200_126_10600_SHIP.exe and i-mate PDA2k_WWE_12200_162_10600_SHIP.exe) with the file radio_.nbf from BA_FRE_BP_12202_558_10602_SHIP.exe but with the Qtek version I had now some problems with the radio and bluetooth.
I got very excited when I heard about the norwegian version BA_WWE_BP_12200_169_10602_SHIP.exe but I had the same checksum problems described here using the xda3nbftool.
Finally, I decided to use PDA2k_WWE_12200_162_10600_SHIP.exe and replace the original radio_nbf file (10600) with the radio _.nbf file from BA_FRE_BP_12202_558_10602_SHIP.exe
Now, I don't have any problems with the radio nor with the Extended ROM from Qtek BA_WWE_BP_12200_126_10600_SHIP.exe!!!
Hope this helps
Click to expand...
Click to collapse
ROM Files
backspace,
Unfortunately I don't have an ftp server, but the links to download the three ROM files I talked about are all in xda-developers
You can download the Qtek BA_FRE_BP_12202_558_10602_SHIP.exe (which is also called BA_FRA_BelDT_12202_558_10602_Ship.exe) at http://cyberb0b.ggu-squad.org/share/BA_FRA_BelDT_12202_558_10602_Ship.exe
This update has been released on December 17, 2004
For the i-mate file PDA2k_WWE_12200_162_10600_SHIP.exe you will find it at http://www.clubimate.com/Support/PDA2k_WWE_12200_162_10600_SHIP.exe
This upgrade has been released on December 20, 2004
For the Qtek file BA_WWE_BP_12200_126_10600.exe you will find it at http://www.qtek.nu/files/BA_WWE_BP_12200_126_10600.zip
This upgrade has been released on November 22, 2004
To extract the files inside each exe file, you can open them with WinRAR and take only the files that interest you in each package
Hello guys!
So anyone figured out how to solv this problem This xda3nfbtool needs a litlle update. For sure the next roms will have diferent encryption like this one.
Hope somone smarter than me in this matter solve this
Cheers
@ Cane
I have T-Mobile German MDAIII (PH20B) now English,
SIM is swiss on sunrise.
CE image 1.22.0
EXTRom 1.12.169
Radio 1.02.00
From :
PDA2k_CDLWWE_11222_169_10200_SHIP.exe
I Downloaded PDA2k_WWE_12200_162_10600_SHIP from above
Extracted it
Added the xda3nbftool file in same DIR
Ran the FIX.BAT that I used before:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -so T-MOB101 -sl GER ms_.nba
xda3nbftool -sd PH20B -so T-MOB101 -sl GER nk.nba
xda3nbftool -sd PH20B -so T-MOB101 -sl GER radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
Then ran the BaUpgradeUt.exe (whis is Now Version 2.3.0.0)
The screen comes up with update old to:
CE image 1.22.0
EXTRom 1.22.162
Radio 1.06.00
What I have not yet done to extract the Radio from
BA_FRE_BP_12202_558_10602_SHIP.exe
Hi every body!
I have a Qtek 9090
I upgraded my ROM from 1.12.00 to 1.22.126, I had problems but I solved it with "Country_error_fix.rar"
Now I`d like to upgrade my ROM to 1.22.169 and i heve the same country error.
The questionis could i use the same "Country fix error.bat" to solve the problem or i need another one?
thank you very much
Text of "Country fix error.bat" is:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -so DANGA001 -sl WWE ms_.nba
xda3nbftool -so DANGA001 -sl WWE nk.nba
xda3nbftool -so DANGA001 -sl WWE radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
I have found that to make it work,you have to copy the country error fix file to a new folder where you download the update to.Then unzip/unrar it , right click and edit to open, then I had to use edit>select all>file>save>exit. Then do the same procedure to update as before. I dont know why you have to open and unzip it into a new folder with the rom and all, but it has worked 2 of the 3 times I tried it. The other time I screwed up!!! LOL
Hope this helps.............. 8)
I get an error as well fixing the country code with the xda3nbftool.
Did anyone figure out the new password or change the xda3nbftool?
>WARNING: this does not look like a nbf header, possible you provided the wrong password
What exactly is improved in ROM 169?
A
Proper procedure
As far I as know this is the upgrade hack procedure:
1. Download de xda3nbftool from http://www.xda-developers.com. This program modifies the ROM upgrade files.
2. Extract the ROM upgrade executable to a folder of choice.
3. Copy the exec GetDeviceData.exe from this extract folder to the TEMP directory on the Qtek 9090.
4. Run the GetDeviceData.exe on the QTEK 9090. This exec creates a file called \Windows\DeviceData.txt.
5. Copy this file \Windows\DeviceData.txt to the desktop computer en open it. The DeviceData.txt file contains the data for the -sd, -sl en -so switches. Use this data from your own QTEK 9090, NOT the standard DANGA001 or WWE.
6. Create a CHANGE.BAT batch file :
CHANGE.BAT:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd ????? -sl ???? -so ???? ms_.nba
xda3nbftool -sd ????? -sl ???? -so ???? nk.nba
xda3nbftool -sd ????? -sl ???? -so ???? radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
Replace the question marks with the data from DeviceData.txt
'sl' stands for language, e.g. WWE.
'so' stands for operator (Country ID), e.g. BRIGH001.
'sd' stands for device, e.g. PH20B.
7. Put CHANGE.BAT, the xda3nbftool and all extracted files (ms..nbf, nk..nbf en radio..nbf...) in one folder.
8. Run CHANGE.BAT first.
9. Upgrade the QTEK 9090's ROM by running the BaUpgradeUt.exe.
This should do the trick.
Ran the GetDeviceData.exe on my Dutch QTEK 9090.
The results:
'sl' (language): WWE
'so' (Country ID): DANGA001
'sd' (device): PH20B.
So my CHANGE.BAT file would look like this:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl WWE -so DANGA001 ms_.nba
xda3nbftool -sd PH20B -sl WWE -so DANGA001 nk.nba
xda3nbftool -sd PH20B -sl WWE -so DANGA001 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
It's possible to update and dowgrade my dutch MDA III but i still have the t-mobile lock, the weired thing is that on my German MDA III the lock is gone, any clue how to remove lock on dutch MDA III
Peterdm could you please tell me\us how you exactly did it. I am really tired of waiting on t-mobile Netherlands.
You would help us a great deal!
what exactly do you want to know
I have two t-mobile MDA III's one from germany and one from Holland. The German one is upgraded to english from german, and working perfect with BA_WWE_BelDT_12200_557_10602_SHIP.exe. and without simlock I use this one with KPN card. Changed the registry with regeditor (regedit.Mrln_ARM.CAB).
Installed the same software on the dutch T-mobile MDA III everything is working but the simlock is still there on the german it's gone but on dutch one stille there.
German: -sd PH20B -sl WWE -so T-MOB101
Dutch:-sd PH20B -sl WWE -so T-MOB003
it doesn't mather if you change ENG to WWE or the other way around. My only concern is to get rid of the dutch simlock.
I think the German ones are sold simlock free!
I am also trying to update my dutch mda III but when i run getdata.exe on my device I get a devicedata.txt which only has:
PH20B in it... nothing more?
devicedata.txt
You have to copy it to PC and the open it, the you will see the rest also
When I open it in windows internet explorer i get:
PH20B0BENGGT-MOB003 1.06.00 00 1.06.1181.00.0000.00
in notepad:
PH20B 0 B
In wordpad"
PH20B
Uhmm How would my change.bat look like then?
bat file
-sd PH20B -sl ENG -so T-MOB003
So if i am correct my change.bat looks like:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -so T-MOB003 -sl ENG ms_.nba
xda3nbftool -sd PH20B -so T-MOB003 -sl ENG nk.nba
xda3nbftool -sd PH20B -so T-MOB003 -sl ENG radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
Click to expand...
Click to collapse
correct bat file
The file is correct
Ok just to be sure:
I am running now a dutch t-mobile MDA III with software versions:
ROM version: 1.06.00 ENG
ROM date: 08/05/04
Radio version: 1.00.00
Protocol version: 1337.30
ExtRom version: 1.06.118 WWE
I have downloaded from qtek.nu the BA_WWE_BP_12200_126_10600_SHIP.zip
- extracted this into a folder
- extracted the .exe into the folder: BA_WWE_BP_12200_126_10600_SHIP
- copied xda3nbftool.exe into this folder
- copied change.bat into this folder which contains:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -so T-MOB003 -sl ENG ms_.nba
xda3nbftool -sd PH20B -so T-MOB003 -sl ENG nk.nba
xda3nbftool -sd PH20B -so T-MOB003 -sl ENG radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
Click to expand...
Click to collapse
Now I should run change.bat (dubble click it? or run it in dos?)
And after this i should softreset my mda put it into the cradle let it sync and then run BaUpgradeUt.exe and wait for about a half hour?
How can i tell the update is done... and how can I hard reset the device after this?
Well I have done it and it works great! Thanks everyone.
Re: what exactly do you want to know
Does this mean that if I upgrade my UK T-mobile MDA III with the ROM BA_WWE_BelDT_12200_557_10602_SHIP.exe I would have my MDA III with the mobile phone unlocked? Thanks.
hi, i don't mean too many threads, but i'm sensing many people have this problem---baiscally,
i had wwe 1.12 installed on a german mda3/blue angel--devicedata.exe now reads:
PH20B 0 B GER R T-MOB101 1.22.01 0 1 1.22.182 1.06.00 06.00
device data used to read:
PH20B 0 B WWE T-MOB101 1.12.22 2 2 1.12.169 1.02.00 02.00
fyi-i'm in new york with cingular as my carrier (but have always seen it as tmobile and worked fine)
and i read the steps on how to update the rom with a wwe--actually my phone is the exact same mentioned in the example--
i have tried, what i think, is may roms found within this forum--english german, french, arabic, all 1.22, and i always get the country code error.
i even tried to trick the german installer with modified wwe files and got checksum errors
so i did everything as worded and here is what i used for my fix.bat (omitting the REMs):
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl GER -so T-M0B101 ms_.nba
xda3nbftool -sd PH20B -sl GER -so T-M0B101 nk.nba
xda3nbftool -sd PH20B -sl GER -so T-M0B101 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
And still got the country code error, but with a different country code error as exhibited in the little diagram i made:
ok, it seams that you have to click to see the pic. but i don't even know what all that means.
i don't know where to go, what else to do.
oh, on a side note, can on use manual cab file -- like to just overwrite my current german flash with english files, reboot the mda, and if all is well--permanent save it?
i don't really know how to mess with manual cab files, like where to put them? or what to do with them--if you overwrite other files?
i know, i'm a mess. but please help, it will help others, and if my problem is fixed, i will pay out too.
things were so much easier with the xda1 -- just downloaded the special edition rom from here, and boom--everything is peachy---wish we had an auto configuration utility for the blue angels, as we did for the xda1.
--sigh.
On my SPVM1000 (XDAII) this worked just fine.
http://forum.xda-developers.com/viewtopic.php?t=18754&highlight=
Good luck either way
(make sure you have a replacement ROM and that everything's backed up to the hilt!)
I have an MDA III from T-mobile and I want to replace the rom with:
"Qtek (Dutch) WWE DANGA001 1.40.00 1.40.556 1.13.00"
I changed the provider code & language code with editfix.bat
When I ran editfix.bat the dos windows said:
"Warning:this does noet look like a nbf header, possible you provided the wrong password"
Then I used MaUpgradeUt_noID to install the patch but it doesnt work? It said the update was complete but the rom is still from t-moble?
I seached the forum for the rom-password (like told in wiki) but didn't find it.
What do I have to do?
thx in advance,
Adrian
MDAIII_TMDE_14201_116_11300_Ship
I own a Qtek 9090 from E-PLUS germany and as I always use my company SIM Card from T-Mobile, I thought it would come in handy to have a T-Mobile GER ROM in the newest version. So I read the wiki on how to upgrade my phone and did everything stated in the wiki.
I edited the fix.bat as told in the wiki and when I run it, I get the same notification as the guy above.
Do I need a different PW forthis rom? Does anybody have it? :shock:
The ROM I try to install is the:
MDAIII_TMDE_14201_116_11300_Ship
HELP!!!
the details I edited in the fix.bat
the deviceinfo from my Qtek says:
PH20B 0 B GER R BRIGH102 1.40.01 0 1 1.40.750 1.12.00 12.00
And i edited the fix.bat to:
REM ~DeviceData.txt PH20B 0 B WWE E T-MOB101 1.12.22 2 2 1.12.169 1.02.00 02.00
REM Replace the question marks with the data from ~DeviceData.txt
REM 'sd' stands for device, e.g. PH20B.
REM 'sl' stands for language, e.g. WWE.
REM 'so' stands for operator (Country ID), e.g. T-M0B101.
REM ms_.nbf Password = 0x20040522
REM nk.nbf Password = 0x20040521
REM radio_.nbf PAssword = 0x20040523
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl GER -so BRIGH102 ms_.nba
xda3nbftool -sd PH20B -sl GER -so BRIGH102 nk.nba
xda3nbftool -sd PH20B -sl GER -so BRIGH102 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
Just follow the upgrade to newst rom 1.42 on the main page of the BA section.
Use the german rom.
Fix.bat will not work on a type II rom
Is it possible to upgrade the Radio ROM 1.06.02 with Protocol 1337.38 contained in the WM5 patched ROM from mamaich with the Radio 1.13.00 with Protocol 1337.42 from the PDA2k ROM for the PH20B device?
My DeviceData looks like this:
PH20B WWE 5.03.02 1.06.02 4
Runnig Fix.bat does not help - I get an Device Error
REM ~DeviceData.txt PH20B WWE 5.03.02 1.06.02 4
REM Replace the question marks with the data from ~DeviceData.txt
REM 'sd' stands for device, e.g. PH20B.
REM 'sl' stands for language, e.g. WWE.
REM 'so' stands for operator (Country ID), e.g. T-M0B101.
REM ms_.nbf Password = 0x20040522
REM nk.nbf Password = 0x20040521
REM radio_.nbf PAssword = 0x20040523
REM xda3nbftool -x ms_.nbf ms_.nba 0x20040522
REM xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
REM xda3nbftool -sd ????? -sl ???? -so ???? ms_.nba
REM xda3nbftool -sd ????? -sl ???? -so ???? nk.nba
xda3nbftool -sd PH20B -sl WWE -so T-M0B101 radio_.nba
REM xda3nbftool -c -u NK.nba
REM xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
REM xda3nbftool -x ms_.nba ms_.nbf 0x20040522
REM xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
When using the MaUpgradeUt_noID.exe instead of the BaUpgradeUt.exe I see Radio 1.06.02 installed and Radio 1.13.00 to be installed. When starting the upgrade the tools times out after about 20 secs and at the next attempt I see empty values reading the current configuration - communications error. Although in one posting from MDAIIIUser the Radio only upgrade should work fpr WM5 I have no idea how to get this working. Any hints?
http://forum.xda-developers.com/viewtopic.php?t=27871