Hello,
I try to update my Blue Angel to new 1.40 ROM from post “New Rom Qtec BA_WWE_14000_147_11200_Ship” I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf files to my setings:
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 T-MOB009 ms_.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 nk.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 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 I miss some warning message, then I run BaUpgradeUt.exe and update ROM successfully.
But when I restart after update I see:
No GSM
D 1.40.00 WWE
My Device Information is:
ROM version: 1.40.00 WWE
ROM date: 03/10/05
Radio version: [empty]
Protocol version: [empty]
ExtROM version: [empty]
Now I can't load any kind of ROM, always I see message:
ERROR 120: COUNTRY ID ERROR : No-No-42-42-42 (last three numbers change)
I already changed the RUU.conf ([CHECKCEID_TYPE]=1) - but before MDA switch to “USB 2.05” no COUNTRY ID ERROR and then setup making one more checking and display COUNTRY ID ERROR.
I try all of ROMS from ftp.xda-developers.com – 8( always error.
DeviceData.txt before wrong update:
PH20B 0 B WWE G T-MOB009 1.06.00 0 0 1.06.135 1.00.00 00.00
now my DeviceData.txt is as in attachment for this message
(I can connect with ActiveSync and run GetDeviceData.exe).
PH20B 0 B WWE 1.40.00 0 0
Please help me, I’m going crazy and spend on that problem last 48 hours, read and try everything on forum, wiki.
Go to the thread http://forum.xda-developers.com/viewtopic.php?t=16953
It is the Wiki: Help me! And yes I have read getting started
There are nice people who will help you surely!
mariusz said:
.... I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf ....
Click to expand...
Click to collapse
1. How did you convert a type II to a type I...?
2. Upgrading a type II to a device that does not allow it will give you the Country Code error.
Have you tried to reinstall your ORIGINAL ship ROM...? This should work. See the FAQ link in my sig for more prob solving (red one).
HappyGoat said:
mariusz said:
.... I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf ....
Click to expand...
Click to collapse
1. How did you convert a type II to a type I...?
2. Upgrading a type II to a device that does not allow it will give you the Country Code error.
Have you tried to reinstall your ORIGINAL ship ROM...? This should work. See the FAQ link in my sig for more prob solving (red one).
Click to expand...
Click to collapse
1. I don't convert type II to type I. I download converted type I from:
http://forum.xda-developers.com/viewtopic.php?t=20770
2. YES 8)
3. I don't know my ORIGINAL ship ROM. 8(
4. I read all of the FAQ at your link - nothing help, I can't find my qtek with T-MOB009.
I have now wrong DeviceData.txt and I think is the main problem. Can't set nbf files to settings from my DeviceData.txt file. 8(
You took a tpye I CE Rom and Type II radio and Ext Rom.
Flashed your device and got stuck, no point explain how or why you did it, lets move on.
1) Radio rom, go to wiki, download the radio 1.12 and the tools, fix it with fix.bat, run the upgrade.
This should give you 1.40 rom and radio 1.12
2) extended rom. You now need to get any extneded rom on your device so that you can then unlock it and copy the 1.40 one over.
So following the wiki getting started download the I-mate 1.62, extract and remove all *.nbf BUT the ms_.nbf, fix the file, run the upgrade.
This will now put a 1.22.162 EXt rom on your 1.40 rom with radio 1.12. Sorry you will have to live with the i-mate splash screens, you can fix that in another thread.
Now unlock, unhide that (also on wiki) delete all and replace it with the extracted 1.40 Ext Rom out of wiki (were else) avalible Extended roms. Lock and hide, hard reset and you should be up and running.
Oh Yes and please if it says extract or download what ever files please do it so that you dont get a version problem.
Have fun
MDAIIIUser said:
...
1) Radio rom, go to wiki, download the radio 1.12 and the tools, fix it with fix.bat, run the upgrade.
This should give you 1.40 rom and radio 1.12
Click to expand...
Click to collapse
U la laaaa...
I can't update radio ROM as in step by step instruction at wiki becouse I ALWAYS STOP on ID COUNTRY ERROR.
My DEVICEDATA.TXT is wrong. I don't have in this file some versions numbers and somthing like T-MOB009.
8(
If you know how I have set fix.bat for my DeviceData.txt please send more details.
DeviceData.txt :
PH20B 0 B WWE E 1.40.00 0 0
so try the Country Code error hack, its for type II but it might work on type I, You have a type I rom so the file is called HTCRUU.conf
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
What happens if you try to flash the I-mate 162 with out the fix.bat, its a clean Type I install and you don't have a Operator code to check against, its also a wwe rom.
La laaaa
MDAIIIUser said:
so try the Country Code error hack, its for type II but it might work on type I, You have a type I rom so the file is called HTCRUU.conf
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
What happens if you try to flash the I-mate 162 with out the fix.bat, its a clean Type I install and you don't have a Operator code to check against, its also a wwe rom.
La laaaa
Click to expand...
Click to collapse
1. Hack dosen't work.
2. When trying I-mate 162:
ERROR 120: COUNTRY ID ERROR: NO-No-12-12-12
8(
Hmmmm....ok, I think the problem is T-MOB009. Are you sure that was your original config? Was your operating system German to start out with (G)?
Here's an idea (perhaps):
Try the Type II Ship ROM (1.40) complete, but with country code hack.
You probably have tried that already, not sure.
Last alternative I can think of, is to put PDA in bootloader mode, and use mtty.exe to remove everything from your PDA.
See also itsme website for such rapi tools: http://www.xs4all.nl/~itsme/projects/xda/tools.html
I have never tried this procedure, so not sure if it will work for ya.
Perhaps my Boss MDAIIIUser has another great idea...he's good at this stuff...so await his reply.
HappyGoat said:
Hmmmm....ok, I think the problem is T-MOB009. Are you sure that was your original config? Was your operating system German to start out with (G)?
Here's an idea (perhaps):
Try the Type II Ship ROM (1.40) complete, but with country code hack.
You probably have tried that already, not sure.
Last alternative I can think of, is to put PDA in bootloader mode, and use mtty.exe to remove everything from your PDA.
See also itsme website for such rapi tools: http://www.xs4all.nl/~itsme/projects/xda/tools.html
I have never tried this procedure, so not sure if it will work for ya.
Perhaps my Boss MDAIIIUser has another great idea...he's good at this stuff...so await his reply.
Click to expand...
Click to collapse
1. Yes, I'm sure T-MOB009 is my ORYGINAL setting - 8)
2. Yes, I try type II with hack - it dosen't work.
3. Could you send more detail instruction how remove everythink from PDA using mtty.exe (link or description step by step)?! - now i have this tool but I don't know how I can I use it.
...and I waiting for replay from Boss and Master of Raster MDAIIUser.
Please confirm that you can connect to your device with acticve sync.
Thus that you are able to browse your documents on your device form your pc.
Next check your dont have that pc issue that is in the wiki getting startted last section of the thread.
I am going to tell you the same as what is in that thread so read it. before I tell you.
@ HappyGoat ,
I must be sick I turned very Green <Grin>,
so can't be your boss no more, will never get that respect now will I? (don't answer )
MDAIIIUser said:
Please confirm that you can connect to your device with acticve sync.
Thus that you are able to browse your documents on your device form your pc.
Next check your dont have that pc issue that is in the wiki getting startted last section of the thread.
I am going to tell you the same as what is in that thread so read it. before I tell you.
@ HappyGoat ,
I must be sick I turned very Green <Grin>,
so can't be your boss no more, will never get that respect now will I? (don't answer )
Click to expand...
Click to collapse
1. Yes I can connect via ActiveSync and browse file from desktop PC.
2. I don't know what are you asking for ?! PC issue, last section... hmm...
If you are asking for:
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted
but I can't find anythink about pc issue at last section, please send it here.
Ok the thead started here.
http://forum.xda-developers.com/viewtopic.php?p=112036#112036
The porblem was that the guy could not get his radio to flash which is some what the same as you at the moment, his solution was to move to an other pc.
Anyway there are a few steps that I think you should try.
On the i-mate 162, did you use the upgrade tools from the extracted ship.exe and did you run the fix.bat.
PH20B 0 B WWE G T-MOB009 1.06.00 0 0 1.06.135 1.00.00 00.00
Click to expand...
Click to collapse
Were did the "G" come from should be "E" ?
Hrmm... I would attack this as follows (don't actually expect this to work, you've probably already even tried it, this is just the first thing I'd try).
Download this rom:
ftp://xda:[email protected]_139_10600_SHIP/Xda_IIs_v131139_upgrade.exe
Then do this, since we know that this method works with that rom:
Edit the RUU.conf file
Add the following line
[CHECKCEID_TYPE]=1
Save changes
Now run BaUpgradeUt.exe
It will say that it will upgrade to this version.
However when the device enters bootloader mode the upgrade util gives a country error. (Don't panic)
Simply restart BaUpgradeUt.exe while the device is still in it's cradle.
Now it will install without a country error.
I hope that this trick works with other BA devices and not only with the XDA IIs.
Hopefully it will install. I'm betting that the bad upgrade messed up your country code, so instead of getting the country code it expects (as you enter with xda3nbftool) it receives something else, or null characters. I'm hoping a rom change can fix this.
Hi Mariusz
Have You suceeded, if no and You have mda3 bought thru era
i can send You my version of rom which is working well without problem on my era mda3
its 1.40 rom 1.12 radio and 110 extrom
i've upgraded it from original era 1.20 rom
rgds
lukasz
TheLastOne said:
Hrmm... I would attack this as follows (don't actually expect this to work, you've probably already even tried it, this is just the first thing I'd try).
Download this rom:
ftp://xda:[email protected]_139_10600_SHIP/Xda_IIs_v131139_upgrade.exe
Then do this, since we know that this method works with that rom:
Edit the RUU.conf file
Add the following line
[CHECKCEID_TYPE]=1
Save changes
Now run BaUpgradeUt.exe
It will say that it will upgrade to this version.
However when the device enters bootloader mode the upgrade util gives a country error. (Don't panic)
Simply restart BaUpgradeUt.exe while the device is still in it's cradle.
Now it will install without a country error.
I hope that this trick works with other BA devices and not only with the XDA IIs.
Hopefully it will install. I'm betting that the bad upgrade messed up your country code, so instead of getting the country code it expects (as you enter with xda3nbftool) it receives something else, or null characters. I'm hoping a rom change can fix this.
Click to expand...
Click to collapse
Dosen't work... 8( I add [CHECKCEID_TYPE]=1 and run it one more after recive coutry id error.
My log file HTCRUU.log :
23:57:25:802 [msg] : Config Info : [667685],[1],[0].
23:57:30:409 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
23:57:34:835 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
23:57:36:988 [msg] : Get Device Backup ID.
23:57:36:988 [msg] : Device BL VER : [2.05 ] [].
23:57:36:988 [msg] : Device ID Is Incompatible.
23:57:36:988 [msg] : START UnInitialization !
23:57:36:988 [msg] : END UnInitialization !
23:57:37:008 [msg] : IsBL. BL : [1]
Now my sytuaition change some:
1. After change PC I try to install qtek ship 1.40 and update hold for 30min with no meesage.
2. Now My CE don't start only program mode (Serial/USB 2.05), hard reset don't help. ONLY PROGRAM MODE START.
lukjod said:
Hi Mariusz
Have You suceeded, if no and You have mda3 bought thru era
i can send You my version of rom which is working well without problem on my era mda3
its 1.40 rom 1.12 radio and 110 extrom
i've upgraded it from original era 1.20 rom
rgds
lukasz
Click to expand...
Click to collapse
Oooo, No I'm still in truble... If you can please put your ROM on FTP and send link. 8(((
Wait for any solution... 8(
8( still at same point... only bootloader, and always Country ID error...
Pleaseee, help... 8(
I am lost, Thelastone tells you to install the o2 rom, you say that you have installed the qtec.
So what have you done?
What rom are you trying?
MDAIIIUser said:
I am lost, Thelastone tells you to install the o2 rom, you say that you have installed the qtec.
So what have you done?
What rom are you trying?
Click to expand...
Click to collapse
I try everything from XDA-dev ftp, with all known hacks and without... still only COUNTRY ID ERROOR.
I try backup to SD card but it is impossible:
Add record error... 8(
I can't find any image file to send it to SD by ntrw.exe, try send .nbf files from shipped ROMs but after insert card into MDA III and restart, ROM restore from SD don’t start.
i think you need to know this before i begin...
PH20B 0 B ENG G T-MOB008 1.06.00 0 0 1.06.116 1.00.00 00.00
SIM: ORANGE
SOLD AS: T-MOBILE QTEK 9060
SIM UNLOCKED by T-MOBILE
MODEL: PH20B
LANG: WWE
ROM: 1.06.00 ENG
RADIO: 1.00.00
PROTOCOL: 1337.30
EXT ROM: 1.06.116 WWE
So u see i have a pretty old ROM. I was reading the WIKIs FAQ (How to upgrade to the lastest ROM) and everything was clear until i hit the Getting started section (((#How do I find the correct upgrade ROM that will work for me?))), now i'm absolutly not sure about what to do. There is NO upgrade for my T-MOB008 so i don't know what should i download in stead.
I was thinking about iMate PDA2K_WWE_14000_176_11200 and about overwriting the radio_.nbf with the new 1.13.00 ver, so i would not need to update RADIO again and i would use the MaUpgradeUt_noID.exe to UPGRADE cause of the different versions. So am i right or no ?
And i have 1 more question can i use Xbackup to backup contacts and apointments and after the upgrade restore them or do i have to create them again manualy ?
thx for any kind of help :wink:
Well it seems for a person that got stuck you picked up all the needed info.
The wiki page with the roms has got lost, I will just jot down a few steps for you details can be found in wiki.
If you use blackberry then it seems you need to stay with radio 1.06.
1 unlock ext rom and save files to pc. (wiki kitchen)
2 sync cotacts to outllook
3 save any docs data you need
4 run the imate 1.40 wiki upgrade
5 run the radio 1.13 upgrade (dont mix the files)
6 unlock ext rom and remove the I-mate carrier cabs (wiki kitchen available ext roms will list them.)
7 add the t-mobile carrier cabs back to device, edit config.txt
8 reset and have fun.
thx for reply...
so here is whats happened:
i got all to the point 4 but when i run the maupgradeut_noid.exe after somethink like 30seconds the ACTIVE SYNC disconnects and i get an ****RY ERROR. THE BA screen is completly BLACK and won't start when i push the POWER BUTTON. I have to take out battery and then it's working( but the device is hard reseted ).
i tried to run the maupgradeut_noid.exe again like the WIKIs FAQ saiz but it's not detecting the BA. I use the cradle via USB connection.
should i edit the RUU.CONF ? or is it getting too high risk ?
Did you use the files from wiki ?
Reboot the pc or kill the active sync session and re run the maupgradeut_noid.exe. You might need to run it twice so after the first error close it and rerun it.
Lets work on the normal way before we try the other tricks.
i forgot to say that i did get all the way to the UPGRADE button and after i pushed it then i did get the COUNTRY ID ERROR.
It happened in the UPGRADING PROCESS. :shock:
Then you did not use the maupgradeut_noid.exe twice
sorry about not answering i had some house moving problems :lol:
i have done the upgrade just like u said it's working.
only the config.txt did not need modification there was an autorun.exe
thx very much :lol:
I have the simillar pb
MDAIIIUser said:
Then you did not use the maupgradeut_noid.exe twice
Click to expand...
Click to collapse
Procedures mentioned XDA Developers do not work.
RUU.log shows:
16:06:42:715 [msg] : Version : [1.5.0-1.0.0.1].
16:06:42:745 [msg] : Config Info : [667685],[1],[0],[0].
16:06:42:745 [msg] : RadioFile Not Exist !
16:06:42:755 [msg] : MSystemFile Not Exist !
16:06:46:751 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
16:06:50:847 [msg] : Disconnect ActiveSync .... [2]
16:06:50:997 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
16:06:53:100 [msg] : Device BL VER : [2.08 ] [].
16:06:53:100 [err] : Device CID Error.
16:06:53:100 [msg] : Update Image. CE : [4], MSystem : [0], Radio : [0]
16:06:54:672 [msg] : Check Ac in BL mode. AC : [1]
16:06:56:175 [msg] : IsBL. BL : [1]
16:07:01:222 [msg] : =============================================
16:07:01:222 [msg] : START UpdateCE !
16:07:02:303 [msg] : Upgrade 0 : 0 Start.
16:08:36:649 [err] : Wipe Data Error.
16:08:36:649 [err] : BL UpdateCE Error.
16:08:36:649 [msg] : START UnInitialization !
16:08:36:659 [msg] : END UnInitialization !
16:08:36:679 [msg] : IsBL. BL : [1]
In this stage "Wipe Data Error." becomes display black and starts in bootloader mode after hard reset only.
hello
i patched my ba several times but yesterday i got the failure message country code wrong.
i run getdivicedata and get this info:
P H 2 0 B W W E AT%CID? 5 . 0 3 . 0 2 0.0 1.13.00 % 4
how can i "repair/fix" my operator code
thanx
Your operator is 'T%CID?'
It is fine - same as mine
This proceedure is all over the forum.
This is what I do:
1) create a new file on ur desktop C drive - call it ROM
2) copy and paste NK.nbf and setoperator files to this new file
3) start - run - type 'cmd' - ok
4) type 'cd\'
5) type 'cd rom\'
6) type 'setoperator T%CID?' - enter
7) your NK.nbf file is now changed to your operator code
8) copy and paste NK.nbf back to your file
9) and flash your ROM using BaUpgradeUt
to flash your ROM:
1) press softrest+pwr+record button at the same time
2) you will see a white screen on your BA with 'SERIAL' letters on top
3) put BA in cradle and allow few seconds for the computer to pair with it
4) run BaUpgradeUt to flash your ROM
Should work
No dude, its not your operator code thats gone wrong...How did you set the operator in the first place? if you used the setoperator, did you enter the 8 digit alpha numeric code, ie. T-MOB001 or XGULA001 or whatever ur code is?
Well, what i would suggest is that you open the Setoperator.bat file using Notepad, make sure it is for you device and language. Then change the operator code using the normal procedure.
Now, use xda3nbftool to check that the values have been set correctly (hint: see how the commands display in DOS when you do the setoperator procedure)
Hopefuly this might help! Good Luck!
Yaantra
all my device data became scrambled during a rom update once, i just reflashed again, using the no_id tool and it went back to normal.
Operator version : AKU3.2
Rom V 5.04.06 WWE
Rom date 03/02/05
Radio v 1.12.00
Protacol v 1337.42
Ram size 96mb
Flash size 32mb
Storage size 43.26nb
Model PH20B
Pocket PC
IMEI 3530300008641
GetData: PH20B AT%CID?
5 . 0 4 . 0 6 . 1.3 1.12.00 % 4
1st problem: Downloaded the Radio 1.15
and unrared it, fixed country code. (That was the error when tried to run it)
The download (Radio 1.15)does not show the ms_.nbf or the nk.nbf
Shows: Getdevice, Enter BL, BAupgradeut, HTCRUU.dll, HTCRUU and the radio_ (just like that, no ext.)
downloaded MaUpgrade_noid.exe. when I ran this gave me: Unable to locate Component. (this application failed to start because RUU.dll was not found. Re-installing the application may fix this problem
Please help
primbcadman said:
Operator version : AKU3.2
Rom V 5.04.06 WWE
Rom date 03/02/05
Radio v 1.12.00
Protacol v 1337.42
Ram size 96mb
Flash size 32mb
Storage size 43.26nb
Model PH20B
Pocket PC
IMEI 3530300008641
GetData: PH20B AT%CID?
5 . 0 4 . 0 6 . 1.3 1.12.00 % 4
1st problem: Downloaded the Radio 1.15
and unrared it, fixed country code. (That was the error when tried to run it)
The download (Radio 1.15)does not show the ms_.nbf or the nk.nbf
Shows: Getdevice, Enter BL, BAupgradeut, HTCRUU.dll, HTCRUU and the radio_ (just like that, no ext.)
downloaded MaUpgrade_noid.exe. when I ran this gave me: Unable to locate Component. (this application failed to start because RUU.dll was not found. Re-installing the application may fix this problem
Please help
Click to expand...
Click to collapse
Just rename the HTCRUU.dll to RUU.dll and you're good to go
thanks for help now new problem
new when I try to download get error:101 connection error
and ends my connection to active sync
By the way this is a fantastic place great people here
I have a generic Wizard that I upgraded using the T-Mobile update on thier website to flash it to 2.26. I have a T-Mobile SIM.
I flashed my T-Mobile MDA and it works fine. However when I did it to my non-branded Wizard (which is the Cingular form factor) it causes a curious problem. Everything appears to be working fine but for some reason in the background it continually is building log files in the root directory that over about a week causes it to have a low memory problem.
The files that are being generated are XPanelLog11.pco; XPanelLog2.1.pco; etc.
Also DbgToStorageLog1.txt; DBgToStorageLog2.txt; etc
I opened up one of these text files and it is has things like this;
PHP:
Windows CE Kernel for ARM (Thumb Enabled) Built on Oct 25 2005 at 17:27:50
ProcessorType=0926 Revision=3
sp_abt=ffff1000 sp_irq=ffff0800 sp_undef=ffffc800 OEMAddressTable = 8c101084
ModemUartPath from 0 to 0
+InitHtcHookUserDbgTrap
-InitHtcHookUserDbgTrap
Sp=ffffc7cc
CreateProcess(fbb4002,NK.EXE,8c100000)
LoadDLL(ffffffff,8fbb47e0,coredll.dll,03f60000)
LoadDLL(ffffffff,8fbb4524,osaxst0.dll,8c159000)
LoadDLL(ffffffff,8fbb42cc,hd.dll,8c155000)
HtcCeLog: Register logging functions with kernel success
CreateProcess(fba4c1e,filesys.exe,04000000)
LoadDLL(fba4c1e,8fbb47e0,coredll.dll,03f60000)
LoadDLL(ffffffff,8fba4f04,certmod.dll,03f50000)
LoadDLL(fba4c1e,8fba4f04,certmod.dll,03f50000)
LoadDLL(ffffffff,8fba7efc,fsdmgr.dll,03f30000)
LoadDLL(fba4c1e,8fba7efc,fsdmgr.dll,03f30000)
LoadDLL(ffffffff,8fb81ddc,trueffs.dll,03d80000)
LoadDLL(fba4c1e,8fb81ddc,trueffs.dll,03d80000)
MMMAP - gDrvGlobBase = 1c0000
Is there anyway for me to correct this? Do I need to reflash with something else or change a registry setting to get these log files to stop?