Database Develop

DEAD QTEK 9090 after update to 1.40 - please help me.

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.

operator code killed?????

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.

thanks for all the hard work, please help me with my 8125

hello there, i have been a member of this board for a little while, but never posted, here goes. i have a cing 8125 and do not know what i am doing wrong updating the rom. got it right when it released in cali with rom 1.??. tried using Lokiwiz 02a, 02b, plain, ect. every time the dos screen just dissapears, no reboot, nothing on the phone. i have been able to update to submitters 2.17. at least it changed a few things. got the new comm manager screen, icons in different places on today screen, ect. however, no updated themes or ringtones ever. i have tried 2.17, the latest 3 in 1 installer, the 2.25 update from cingular and htc. i AM able to change the os number on the boot screen. i have even paid and downloaded an unlocker program from some uk company, but it wants me to select a key file which i do not possess. i think my problem is that it is not unlocked. just today i downgraded to 1.8.11.1 and tried to use lokiwiz and lokiwiz02b. same deal, screen just dissapears. no listing of an unlock number. :?: i am now confused.... also, never have had a rom implant a2dp but have been able to send it manually and it works fine. any help would be greatly appriciated. i have tried lokiwiz with/without sim, with/without mem card. is there somethin that i am missing??

Easiest way to do this is to extract lokiwiz to the root of your hard drive ie c:\
Copy enablerapi.cab to your device and run it from there.
Open a Dos windows <Start> <Run> type "cmd" without the quotes.
You will have a black box now on your screen. Type "cd\" again without the quotes and <enter>
type "lokiwiz" without the quotes and <Enter>
Now Unlock and CID Unlock.
You'll now be able to see the status as you do this.
Your phone will soft reset after each action.
Any more questions, ask
btw, the original Lokiwiz thread is http://forum.xda-developers.com/viewtopic.php?t=33796 and faria's tutorial is http://forum.xda-developers.com/viewtopic.php?t=47848.
Good luck!

thanks steve
thanks for the insight. i wanted to ask one question really quick. after doing the procedure that way everything appears correct except my phone never re booted. i get this screen
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Jonathan>cd\
C:\>lokiwiz
'lokiwiz' is not recognized as an internal or external command,
operable program or batch file.
C:\>cd\lokiwiz
The system cannot find the path specified.
C:\>cd\
C:\>lokiwiz
machinagod's HTC Wizard Unlocker v0.2
NOW WITH CID Unlocking POWER!
--------------------
WARNING: This tool is highly experimental!
I will NOT be held responsible for any problems caused by this tool.
--------------------
Thanks to xda-developers, spv-developers, and especially itsme by the work they
released. This solution would not be possible without them.
--------------------
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter: u
Unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Your phone is now unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
ECHO is off.
"Standing on the shoulder of giants"
Ricardo Afonso, 2005
C:\>lokiwiz
machinagod's HTC Wizard Unlocker v0.2
NOW WITH CID Unlocking POWER!
--------------------
WARNING: This tool is highly experimental!
I will NOT be held responsible for any problems caused by this tool.
--------------------
Thanks to xda-developers, spv-developers, and especially itsme by the work they
released. This solution would not be possible without them.
--------------------
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter: c
CID unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
ECHO is off.
"Standing on the shoulder of giants"
Ricardo Afonso, 2005
C:\>
is this correct?? cannot find file?? i guess maybe if it actually is already unlocked and i run the program it wont reboot? thanks again :?:

OK. The "The system cannot find the path specified." message says it all. You're NOT unlocked as the unlock program can't run.
Download the program. Extract it to c:\ (Download Winzip if you're confused ... www.winzip.com )
Until you can get past the "path not found" you're not going to work. It really shouldn't be that difficult.
Post you results after you try this please.
Good luck!

THANK YOU
somehow it worked. could be one of a few things i was doing wrong. before i was just executing the .bat file. also was not extracting the entire file to the root of c. i was just copying the bat file to c. could it be that this time i left the sim card in??? thanks.. the odd thing is that i COULD switch around some rom versions including 1.5.4.2 WWE and the latest cingular 2.25 update with no problems, just didnt get all the benifits of all the cooked roms you great people have to offer. let you know how it goes.. thanks again

just wanted to add another note... which rom in your opinion is the most stabe, fastest one out??? the 2.25 from htc and cingular sucks bad. lots of hangups, programs locking up, ect. do not recommend it at all. except decent signal strength... later

I personally like and am using the T-Mobile ROM 2.26 Molski cleaned up Custom T-Mobile 2.26 Rom (Dutch and WWE)
Search for (if you don't have) and install the Cingular Connection cab and you're set to go!

BA imate PDA2K upgraded to AKU3.2 and want to Ug Radio to 1.15 but having a problem

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

Flash ROM problems - it refuses to flash

Ok, I am having a difficulty in flashing ROM using MaUpgradeUt_noID.exe and/or BaUpgradeUt.exe
Using MaUpgradeUt_noID.exe
I have the system rom (Aku's version) and a radio rom (1.5). Next, I run MaUpgrade tool; it detects the device flash as follows:
{
"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"
}
(Okay, you might have questioned why is the device v5; that's because it worked before with baupgradeut tool, but right now, it doesn't work anymore and I wasn't sure how I managed to get it to work in the first place. The main reason I wanted to upgrade again was the radio rom (the connection is really bad) and the transcriber failed to function properly as an extended rom but that was like months after I did this. I often had to reset the device to fix those issues.)
Then after pressing Next, ActiveSync (I tried final version 4.5 as well as an older version 4.2 - both failed) would then get disconnected and ma utility will give me a Connection problem error as follows. I have to reset the PDA device to get activesync reconnected.
Using BaUpgradeUt.exe
Now this is the annoying part. I loaded the GetDeviceData.exe on the PDA and obtained the following:
Code:
P H 2 0 B 1 W W E AT%CID? 5 . 0 4 . 1 0 . 1.02.10 % 4
Removing all of the spaces, I get something like this:
Code:
PH20B1 WWE AT%CID? 5.04.10. 1.02.10 % 4
I wasn't able to find the device operator. So I just edited EditFix.bat like this (and of course, I run this batch - both files are modified (nk and radio_ ones)):
Code:
xda3nbftool -sd PH20B1 -sl WWE -so "" ms_.nba
xda3nbftool -sd PH20B1 -sl WWE -so "" nk.nba
xda3nbftool -sd PH20B1 -sl WWE -so "" radio_.nba
where I also tried to replace "" with T-MOB101, XGULB001, and XGULA001. (since the device is a Siemens SX66 purchased on ebay) All failed and returned a model error.
Is there anything I should do?

Your operator code seems to be deleted (should be sth like T-MOB101 - read here: http://wiki.xda-developers.com/index.php?pagename=GetDeviceData ). Now you can only use MaUpgradeUt_noID.exe untill you repair it (anyway operator code is not needed after all) by installing ROM with correct Operator code for your device (if you know/remeber it) set by operator or you using xda3nbftool.
Apart from this, you seem not to follow the procedure: you should put BA in Bootloader mode, not leave ActiveSync mode when you initiate upgrade.
Please post your results here, when you finish.

pichus said:
Ok, I am having a difficulty in flashing ROM using MaUpgradeUt_noID.exe and/or BaUpgradeUt.exe
Using MaUpgradeUt_noID.exe
I have the system rom (Aku's version) and a radio rom (1.5). Next, I run MaUpgrade tool; it detects the device flash as follows:
(Okay, you might have questioned why is the device v5; that's because it worked before with baupgradeut tool, but right now, it doesn't work anymore and I wasn't sure how I managed to get it to work in the first place. The main reason I wanted to upgrade again was the radio rom (the connection is really bad) and the transcriber failed to function properly as an extended rom but that was like months after I did this. I often had to reset the device to fix those issues.)
Then after pressing Next, ActiveSync (I tried final version 4.5 as well as an older version 4.2 - both failed) would then get disconnected and ma utility will give me a Connection problem error as follows. I have to reset the PDA device to get activesync reconnected.
Click to expand...
Click to collapse
Hello,
I've the same 101 error...
I don't really understand how to find a solution to upgrade without that problem...could you help me ?

Once I had a problem like this one and I figured out that I could not flash my device + radio at the same time.
Try removing the radio.nbf from the folder where MaUpgradeUt_noID.exe and then try to flash your device.
If it works, then remove the nk.nbf from the folder, put back the radio.nbf and try to flash it.

Tks.
I've put a topic for that.
It seems to be a Vista OS problem...

eleger91 said:
Tks.
I've put a topic for that.
It seems to be a Vista OS problem...
Click to expand...
Click to collapse
I confirm everything. Same problem for me with Vista. Upgrade is possible only under Xp. Maupgrade is not compatible with Vista. Someone should make a Vista version of it.

Nope not only vista. my xp home is having excatly the same problem. Completely stuck now and getting PreSetUSB along with other error msgs now on the device.

hi all of you
how can I fix sam problem

I'm having the exact same problem as you guys. anyone managed to find a work around to it ?

try this workaround...
1. avoid Vista... use XP
2. flash in BOOTLOADER mode. (press and hold Record+Powerbutton then softreset) then just ignore if the Device info FROM is missing... just click upgrade.

Hi Silver Samurai,
I am flashing in Winxp using bootloader mode and Maupgrade. Doesn't seem to work. I have followed everything in the wiki step by step. Such as disabling activesync.
Really don't know where i have gone wrong.

mtnbikefreak said:
Hi Silver Samurai,
I am flashing in Winxp using bootloader mode and Maupgrade. Doesn't seem to work. I have followed everything in the wiki step by step. Such as disabling activesync.
Really don't know where i have gone wrong.
Click to expand...
Click to collapse
what error numbers are you getting?
when does it fail?

Well i make a hard reset (No for the first option and yes to the 2nd and 3rd options.) After that leaving it in bootloader mode - showing serial and bootloader version number v2.08.
I make sure that activesync (usb connection is disabled). Close wcecomm.exe and other files related to activesync in taskmanager. Connected the usb cable and it changes from serial to usb. Invoked the Maupgrade noid.exe. It hangs there indefinately for more than 30 mins showing the screen that it is checking the xda. If i pull the cable out, it immediately shows device error.
I know that there is nothing wrong with the cradle as i can connect to activesync in normal mode and install programs / files.
I can still boot up after that with wm2005 helmi. Cannot seem to erase the rom. Funny thing is that with wm2005 my sd card cannot be detected. Previously with wm2003 it can be detected. However when the screen is off, and when i insert the sdcard, it does turn on. Likewise when i remove the card and the screen is off, it would also come on. But that is a total different aspect altogether. Anyway i figured that if i can reflash to the official wm2003 rom, it would solve that problem.
Sorry for the wall of text, but i just wanted to fully describe the problem i am facing. Could it be that the DiskOnChip is already corrupted ? Don't think that it's the Intel SRAM/Nand Flash chip as it's only 128Mbits. which only stores the bootloader.

is there an SD Card inserted when you are trying these procedures?
can you try both with or without it?
try without an SD first
please post your result.

Yes i have tried both with sd card and no sd card. If the SD card is inserted, in bootloader mode, the serial won't change to usb until i eject the sdcard. The screen would just get stuck showing the msg, checking the xda.