Database Users

AdaptROM unable to connect

I can't figure out why AdaptROM cannot connect to my XDA. I am running Active Sync 3.7 on Windows XP pro. I have Norton Anti-Virus and several other applications that are always running. I have tried disabling all of them and it didn't make any difference. I am running the new T-Mo WME2003 and the new 6.4 radio stack on my SX-56. It syncs just fine with the PC and has a pairing relaitionship set up.
Neither AdaptRom or any of the .exe upgrade programs, nor Mobipassword can connect to my XDA. Anyone have any ideas why this might be? I have tired using a serial cable and the USB cradle and changing the connection settings. When I originally upgraded it way back when to the ATTWS SX-56 PPCE2002 rom it worked just fine. I hadn't tried it since.
The only thing I can think of is a registry setting being hosed up. I am going to try uninstalling active sync and reinstalling and see if that makes a difference.
Suggestions will be greatly appreciated.

I tried removing and reinstalling Ative Sync and it didn't have any effect. Both programs show an Active Sync error cannot connect to device.
It's as if something must have the port tied up.

Same Here
I upgraded to the 4.00.10 rom on my xda but I can't get either adaptrom or Programme A to run so that I can downgrade the device or reflash it.
Any help would be appreciated as I don't have access to an sd card writer.

Re: Same Here
qtzar said:
I upgraded to the 4.00.10 rom on my xda but I can't get either adaptrom or Programme A to run so that I can downgrade the device or reflash it.
Any help would be appreciated as I don't have access to an sd card writer.
Click to expand...
Click to collapse
I had the same problem U had before. the best solution is to buy a SDcard reader to do the job.
Read more from here http://xda-developers.com/forum/viewtopic.php?t=1717.
Good luck :wink:

I noticed that the 3.x CE developer environment also cannot connect
to a 2003 device.

XDA developer Itsme said:
I noticed that the 3.x CE developer environment also cannot connect
to a 2003 device.
Click to expand...
Click to collapse
Could this mean that some supporting files are missing from the T-Mobile rom? If somebody could get a list of all the files that are different between the 4.00.05 and the 4.00.10 roms then it might point to something...

You can try another hard reset of your xda. That happened to me about a month ago and a hard reset fixed it. Unfortunately I had to create a new relationship etc.. - Jim

Help please using XDAtools as I am a dummy!!!

Sorry folks but I have already posted this and don't know how to delete the previous post. after I reviewed the previous post I don't think I made myself clear enough. Please accept my apologies. But would appreciate help on this.
I have read the majority of the info on XDAtools on the forum and installed I believe correctly. I currently run on Win98SE. I have installed Jeff summers version of XDA tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using
XDAtools OSImage. But have noticed that I can only appear to dump
this as NB1(windows CE(*.nb1) type files if I try to call this NBF I get
the following errors:
”error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for
reading. the system cannot find the file specified”
”error opening source bootloader from C:\program
files\xdatools\bootloader_v5_15.nb0ea. error opening target device”
Is it possible to dump my ROM to a file called ‘xxxx.NBF’? or must I stick with *.NB1? this is not a problem as long as the NB1 file can be reloaded.
2: When I try to upgrade my ROM by using OSImage tool and selecting
source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via Programme A) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory
(via Programme A) I always get the following message:
”Programme A not found - run with --register error opening target device”
I originally ran the ProgrammeA with ‘--register’ when first installed and tried numerous times since. Can someone please help as I am sure it is something simple I am missing. I only want to be able to use XDAtools to dump and restore ROMs.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks in advance John.

May you tell your current ROM version and device type?
Some ROMs do not accept the EXE or the XDAtools with NBF files upgrading methods. You may have to use the SD card flashing in this case.

Thanks Bis
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files. Though I have followed all instructions for definition. There is probably something simple I am missing. You see I only want to be able to use XDAtools to dump and restore Roms without the need for SD/MMC cards.
Thanks John

Try downloading the XDATools from Jeff Summers site, it has all the missing bits, including the required batch file :
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
That's from the sticky XDATools thread, probably read through there and you will find most questions answered if you continue to have problems.
Remember though that the SD card method is the preferred option, and if you burn any T-Mobile ROM's the SD card is *required* to reverse that.

Re: Thanks Bis
jdoherty76 said:
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files.
Click to expand...
Click to collapse
XDAtools cannot work with WM 2003.
and you no need to backup A.30.09.ENG (ATT USA version WM2003), you can get it from online!

cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??

Biso007 said:
cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??
Click to expand...
Click to collapse
Yes, it for sure!
XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
It cannot work with WM2003 official release (AT&T A.30 or T-mobile).

Thats weird, I am positive I used xdatools to program my sd card through reader writer after downloading the official WM2003 upgrade, in fact I must have used that method because I had to seperate out the radio stack and program just the ce rom, I have no other tools to do this.

XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
Click to expand...
Click to collapse
I think you'll find that it only does *not* work with T-Mobile WM2003 ROMs. That's only because they lock up their OS to try and prevent us from changing ROMs. I don't think that's the case with any other manufacturer. I also think it doesn't make any difference whether it's WM2003 or WM2002, it solely depends on whether the manufacturer locks the OS.

Thank you cgigate & ebswift re XDAtools/WM2003
Thank you Cgigate and ebswift maybe this is why I am encountering problems with my download and restore of my ROM. I inadvertently choose a WM2003 AT&T rom to practice with. Maybe I should have chosen a PPC 2002 ROM to test??
I thought I had a problem with XDAtools and that I did not have all the correct links/files in place. Maybe I should dump my ROM and try restoring a PPC2002 and then re try my test. Thanks again guys.

i used xda tools with the AT&T WM2003 rom on my uk o2 xda with no problem. I wanted to keep my old radio stack as it was working fine and just used the os upgrade file, via SD card.
I would recommend updating activesync to 3.7 if you are doing it via the XDA cradle.
maltloaf

Did you use XDAtools to copy direct to device
Thank you Maltloaf, when you upgraded your rom did you use XDAtools directly from PC to device or copy the file onto your SD/MMC card and use the bootloader program to load ?? If so maybe you can answer the problem I am encountering. Thanks john

i have flashed twice (had to go back to 2002 for a short while)
both times using the SD card/bootloader method and I transferred the file onto the card using xdatools in the xda/cradle

Thank you Maltloaf
Thank you Maltloaf this seems to be clearer now, but in the context of upgrading etc XDAtools is only being used to copy the file from source to SD/MMC card. I was under the impression that XDAtools did not require the use of SD/MMC card. But maybe it's a matter of finding out what works for you. John

well xdatools should be able to flash directly to the xda as far as i know but it's always the safest way to do it sdcard style

Thanks to all
My thanks to all you helped with my recent questions. Thanks John

T-Mobile Rom.... Can't do anything else... Help

Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.

if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.

Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?

omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.

I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:

Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!

Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.

prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.

Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.

Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?

You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card

I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz

ha ha
I can fix all your problems!

How?

Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy

Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274

The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet

on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0

Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.

problem magician

I am new of the forum, I have just purchased a nm8 used magiacian (t-mobile MDA) it is I bring a problem.
The preceding owner has begun an updating of the rom that has not gone to good end and the device doesn't now set out anymore and from the following error:
USB V1.00 (if connected USB).
Serial V1.00 (if disconnected).
Bootloader mode ?
What must I do for going on?
I hope in a help
Best regards Luca

help
I pray you helped me, the first post is from beginners, but believe I have followed the standard procedure.
unloaded the rom
unloaded no-id
always tried upgrade more times failure.
HELP !

for the beginning you should use a standard ROM to get familiar with the device.
just go to the t-mobile website, downloads, chose your device type and then look for files named softwareupdates or so.
they will be in zip-format.
there will be an application in there. just go into bootloadermode, connect your device and start the upgrade. it's completely guided and will last about 20min.
although most of the ppl that read/write in this forum didn't install the eROM, I think you can start with all the cusomization stuff. If you have become more familiar with your mdac, you can try other modified ROM's.
just ask if you have more questions
greetz Stefan

i have to say that using standard rom (jam rom downloaded from club imate)
the upgrading applications hangs.....
and leave magician in booting mode, ready to be erased....
i was desperaded, but last experiences with motorola phones and its firmwares advice me to try again
so i had to launch againg that apps and it starts erasing actual rom....
i think there is a bug in few roms.... may be only in its installer

Have tried with the T-mobile rom but doesn't even go with that!

Caslu,
Have you tried a hard-reset?
If so: I guess you've got a decent TMO magician rom downloaded. So get maupgradeut_noid.exe from the ftp. Extract all the files from your TMO shipped-rom & put them in a directory, so you get some .nbf files, enterbl.exe & maupgradeut.exe. Now put the maupgradeut_noid.exe in the same directory. Connect your magician to the usb. It should read usb v1.00, if your magician isn't in bootloader press camera&power&soft-reset at the same time for a few secs. till you get the usb or serial reading.
After connecting it to the usb execute the maupgradeut_noid.exe twice, first execute might give an error 120 second should finish.
If this fails make sure you got a magician & not a charmer.
If it's a magician return it, cause I think it's broken. Hey why buy a device that's in an inconclusive state??
Regards, M

I think really that It broken.
Have picked it because little cost!
non one reply .......

caslu said:
I think really that It broken.
Have picked it because little cost!
non one reply .......
Click to expand...
Click to collapse
Download the latest shipped ROM for the country your magician was first sold in.
Ensure Activesync is in the normal mode (USB check is ON).
Run the executable ROM update program.

INSTALL HARD-SPL from micro-SD?

Is there a way to install HARDP-SPL from the micro SD card? I am able to flash any rom from my SD-Card, but I am no longer able to connect my Polaris to active sync. Get an error "USB Device not recognized" and I am not able to get synched. Now I have flashed several different rom's and also different radios, that works from the micro sd card. but I am still not able to connect with active sync. When I enter the bootloader mode then I just see that message "POLA100 MFG SPL-2.20.OliNex CPLD-2" So I guess the Hard-SPL is missing. Home I will get some help ;-)

If you step manually to bootlader mode and see the Olinex string, hard-spl is installed!

Thanks for your answer, didn't know that. However, I am not able to connect to active sync even though I have tried different ROM's and different Radios also, flashed from SD-card. Still no connection to activesync :-(

I have the exact same problem for almost a year now, flashing all roms with the micro sd card... and living without active sync :S
Hope someone can help us here

maybe 2 things :
1- your usb cable is ko...try with an another one
2- maybe the usb pins in your device are twisted or broken...
cheers!

ouioui01 said:
maybe 2 things :
1- your usb cable is ko...try with an another one
2- maybe the usb pins in your device are twisted or broken...
cheers!
Click to expand...
Click to collapse
1- the USB cable can't be the problem, already tried a different one, plus using my Touch pro with the same cable on the same computer
2- the pins, I don't know, they look good for what I can tell and it is strange because the phone will be charged with the usb cable
wish I would find a solution.....

fktsndr said:
If you step manually to bootlader mode and see the Olinex string, hard-spl is installed!
Click to expand...
Click to collapse
Can you dumb that down a bit? I don't have access to a windows computer, so I have to rely on the microSD. Is there a way to Hard-SPL the phone with the SD card? I performed a Hard-SPL on my Wing when I first got it, but I think it was an older out-dated version, cuz I get an "Invalid Certificate" error when trying to flash from my microSD.
Thanks,
-Adam

easy solution which I found
If you first install the .nbh file of the .72 stock spl using the micro sd card, then your device will not boot into the OS. Now run the Sony Ericsson update utility (which you can download from their website) and run it. It will try to upgrade the system through usb. After different steps, this software will ask you to reinstall the OS (the spl should match first) and then you can reinstall the stock spl and you are back to square one. Now from here, you can now go anywhere you like.
Note: The above method, I tried it myself and it worked. It might not work for everyone hence use it at your own risk. But if you have a bricked device, then there is nothing to lose.