Database Users

error getting device data after T-Mobile (4.00.10) update

Hi developers,
first of all I'd like thank you for your excellent work. I used a couple of roms and really appreciate your efforts.
This time I updated my device from WM 2003 (4.00.01 ENG, Radio 4.21.00) to the T-Mobile release whitout radio update, posted in this forum by Aurora13. After a backup of my data and removement of the T-Mob. stuff like suggested by Aurora13, I noticed that my backlight was turned of and I couldn't turn it on again either.
So I tried to downgrade again, because working without backlight really is a pain, by I'm unable to.
Not depending on which ROM I use, I get the message: "error getting device data" (CMD.exe) & "execute remote communication program error" (prog. a 1.09).
My active sync (WinXP) seems to work.
The device & telefone seems to work either.
How can I fix this?? Any suggestions?? I'd really like to go back to 4.00.01!!!!
Thanks in advance!!!

If you restored your applications from a former version of WME 2003 you will see this happen. I don't know what registry setting or file is getting changed but after a restore from say 4.00.01 or 4.00.05 backups (I use SPrite Backup) you will see this phenomenum occur after a soft reboot no backlight. Do a hard reset and resinstall your applications and all will work fine.

error in CMD.exe window after T-Mob 4.00.10 update
Hi developers,
I have similar problem, I’d like to go back to 4.00.005 too.
Using the ROMkitchen_4.00.05.exe, in the CMD.exe window I got an error message:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting connection”
My activesync seems to be working properly.
What has gone wrong? How do I fix it?
Thanks in advance

Experienced the same with the backlight.
So NEVER do a restore from a different ROM!!! Alway do a clean install.

error in CMD.exe window after T-Mob 4.00.10 update
Do a hard reset and resinstall your applications and all will work fine.
Click to expand...
Click to collapse
Always do a clean install.
Click to expand...
Click to collapse
So in plain words: how do I do that when this occurs during the flashing-procedure :
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting connection”
Click to expand...
Click to collapse
It's not only the backlight, the problem is the "execute remote communication program error" which makes flashing the ROM impossible .
I used do update with *.exe-files which won't work out anymore :evil: . Can anybody post a step by step guide how to fix it and go back to the ROM before :? (Which would obviously be the best)?
Or does anybody know which registry key has to be changed to fix the backlight :idea: ?
Thanx!!!

Does it work OK after a hard reset?
Because you shouldn't have to go back, do a hard reset and do a clean install of your apps and 4.00.10 should work ok.

Thanx Aurora13,
it now seems to work !
I'm on 4.00.10 again with all the T-Mob. stuff and backlight working.
In my case, going back to 4.00.01 and restoring my backup seems to be less time consuming than doing a clean install (would loose adress book & calendar).
I actually can't spot a lot of differences besides the version numbers in the OS anyway :? .
:evil: But trying to do that, I still have the same problem with the cmd.exe:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting devicedata (cmd.exe)”
Click to expand...
Click to collapse
and
"execute remote communication program error" (prog. a 1.09).
Click to expand...
Click to collapse
:evil:
Seems to me like a serious bug that I can't flash my ROM with the USB-cradle anymore :x .
Anybody any suggestions how to get rid of this OS-version without SD-card-writer?? I'd really like to have evrything working again like it was before!
Thanks a lot in advance!!!

Most importantly: do not upgrade to a T-Mobile ROM 900/1900 MHz (American) ROM on anything but a 900/1900 MHz phone. The T-Mobile ROMS contain the RSU phone upgrade, which will run as soon as WinCE boots. You will ruin your 900/1800 (European/Asian) phone if you do.
Click to expand...
Click to collapse
Could that be the problem that I'm unable to fllash my ROM again?
You will ruin your 900/1800 (European/Asian) phone if you do.
Click to expand...
Click to collapse
What does that mean?

"What does that mean?"
i suspect it means that your xda will only work in US
untill you find some way to flash it back to the 900/1800 gsm mode
which is used in EU and much of the rest of the world [/quote]

untill you find some way to flash it back to the 900/1800 gsm mode which is used in EU and much of the rest of the world
Click to expand...
Click to collapse
Anybody know how to do that when unable to flash ROM due to
Quote:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting devicedata (cmd.exe)”
and
Quote:
"execute remote communication program error" (prog. a 1.09).
Click to expand...
Click to collapse
Only via XDArit?????????

if it can be flashed using the sd flash card and you have an sd flash card reader / writer for the pc it would be possible

Similar discussion going on here:
http://www.xda-developers.com/forum/viewtopic.php?t=2134
T-Mobile update 4.00.10 sucks!!!

@reiggue
4.00.10 does not suck.
The problems you are experiencing are not real problems but a lack of knowledge on your side.
If you asked how to solve them I can help you to solve EACH one. But you are not asking, but only being negative.
As with all ROMs if you don't know what you are doing, then don't do it.
If you read this forum more securely, you already got answers of a few of your problems:
- How to go back to an old ROM
- Removing the TMobile stuff
- Backup of previous version does not work
All the answers of the above and how to solve them you can find in this forum.
So use the knowledge of the people of this forum and don't be so negative.

I want to second Aurrora13's statement. Over and over in this forum it is stated that you should not attempt these ROM updates if you don't have an SD reader. Sometimes it is the only way to save your bacon (XDA)! If a user insists on ignoring sound advice, then he shouldn't complain about suffering the consequences.
In general, the more experienced users on this forum provide good advise and are more than willing to ehlp others. Personally, I think this forum is awsome!
We all know we are taking risks but being techno-junkies we jump in there trying to improve our XDA's and learn more about its capabilities and ways to improve it. I hope when the next majore WME phone becomes available (I'm hoping for the TI WANDA, though XDA II will probably be first) that we are able to do the same with it.

4.00.10 user wanted to revert back to old rom
You need to use SD card reader to revert back to older rom, Activesync doesn't work properly in windows, even you had sync with your windows.
I had the same problem before, but I found out this 4.00.10rom is more stable then others WM2003roms.
Please follow Aurora13 instruction,removing a few item under program/AIM -/Tmobile and if you have radio signal problem You might want to try to bootloader setting 900/1800 or 900/1900, it works for me.
This is my second time flashing v4.00.10 and I'm using XDA asian unit.
Good Luck.
:lol:

@Aurora13
You might be right in me being negative.
As I read through the forum, there are other people experiencing the same problems.
I think that people should be warned to use the 4.00.10 version instead of hyping it, because, you might agree on that, you loose the ability to go back to an old ROM via activesync, which is the most convenient procedure so far.
I didn't know that I lose this ability, especiallly after performing 4 successfull ROM-updates so far with ROM from this site. That in fact frustrated me.
I agree that the information provided in this forum should help restoring the old ROM.
To close this message, I'd like to thank everybody in this forum who contributes to help fools like me, obviously not knowing what they're doing! This forum is great and I don't want anybody to get the impression I'm blaming anybody else for my faults.
Thanx!

imho then buying a SD reader is a pretty good idea no matter what
they come in versions which read 6 or 7 different flash types so one can also read ones digi cams card if it's a different type
and they are only about 50$ or EUro or something like that
i'm sure getting 2->3 flash readers one of these days

@reiggue
Yep this forum rules big time.
If you check the Sticky thread:
http://xda-developers.com/forum/viewtopic.php?t=1624
There is already enough warnings for the 'beginner', that's why I didn't warn it can be dangerous.
But enough said, good luck with your downgrade and/or if you will stay with the 4.00.10 ROM I'll be glad to help solving some problems you may experience or talk you through the downgrade.

I appreciate your assistance, Aurora13!
Thanx! :lol:

For those of you in the UK - I bought an SD card reader (only reads SD and MMC cards) from PC World for only £6.99 - I've used it to change ROMS back and fourth several times on four XDA's without incident so far - I bought it after an activesync update (genuine O2 upgrade) went horribly wrong and trashed my XDA. I think that everyone "playing" with these ROMs should get one.

and what if someone (me) can not afford to break anything?

Instaead of Hi I say you are great people
So the case is... I just need to have working Qtek 1010 with SOME additional soft on it inside a ROM...
I've read many pages in this forum and I'm able to find too many ways to change my ROM. I'm totaly confused.
I work for extremaly big worldwide company and they gave me q Qtek, told me to use it, gave me one simple application and web link... so I do.
But the Qtek is much powerfull than that so I need to flash my ROM.
Now comes a question: where can I find one document how to prepare for it, what tools do I need, how to do it... I know after some tries I will be confident enough to do such stuff easlily, my problem is I have only one try, they will make me w trouble if I screw my company recource.
I understand you had milion similar questions like that. Basicly I need help how to flash so I can be sure 100% not less that I can recover in case of trouble. I hope you understand I'm afraid to do it because lack of experience and you are able to tell me if I should try to flash...
or maybe it's better for me to ask my boss to by me a 512 MB SD and install all additional soft on it and stop worring about memory?
I'd appreciate any opinion... you are the best and I'm just new to this bussines...

Get an sd card, backup existing rom to sd card, very easy to do by bootloader method. Enter bootloader by holding down power while inserting stylus in the reset hole on the bottom left of pda then press top right function key, then choose ce to sd. Once you have done this you can check if it has in fact backed up your rom by putting sd card in the pda, enter bootloader, it will then give the option to program the rom, just remove the card and push the reset with stylus again, the other method to check a working backup is to put the sd card in the pda, the pda will ask to format it, say no and remove it. Once you have a backup you can either use xdatools to copy it to your pc or keep it in a safe place, no more files must be written to this card otherwise it will be rendered useless, if you wish to reuse the card sometime it will need formatting. Once you have your backup, go to www.yorch.net, cook yourself a rom and download it in the exe format, this will do a normal install from your pc while connected to pda via activesync, if it messes up you always have your backup. Once you become more proficient at using xdatools you might wish to try out lots of different roms until you are happy with the result, you can go on to sd card flashing which is a much better way of programming rom and much less prone to error because it doesnt rely on a pc connection. I would advise you to leave the radio stack alone, if you can make and receive call ok leave it alone. Have a thorough look around the forum before proceeding. Its good fun to program your pda and you can make it a much better tool, but make sure you always have a way out if things go wrong.

www.yorch.net not working... is there a place like that?
Hi!
I read the above post, one of the clearest here, and I almost got the confidence to finally do this ROM update...
But:
1) Can't find the www.yorch.net website where I could "cook myself a rom and dowload it in a .exe format"
2)It's still not very clear to me what exactly cooking a ROM means: it concerns the OS (the version 1.53, 1.72 type of stuff), the extended ROM (the default programs u get starting after and hard reset like the SW for the camera etc) or both?
Thanks!!!
Chris

Another ROM Kitchen
Try the following ROM Kitchen http://lumpistefan.dyndns.org/
I noticed that you have the XDAII. Now, someone please correct me if I'm wrong but the directions above and the ROM kitchens are all for the XDA I or Wallaby version.

Re: www.yorch.net not working... is there a place like that?
cchris said:
Hi!
I read the above post, one of the clearest here, and I almost got the confidence to finally do this ROM update...
But:
1) Can't find the www.yorch.net website where I could "cook myself a rom and dowload it in a .exe format"
2)It's still not very clear to me what exactly cooking a ROM means: it concerns the OS (the version 1.53, 1.72 type of stuff), the extended ROM (the default programs u get starting after and hard reset like the SW for the camera etc) or both?
Thanks!!!
Chris
Click to expand...
Click to collapse
Chris,
Those Roms are made for XDA1 beware it's not made for the device you have!!!!!!

What's the kitchen for XDA II
THANK YOU!
I was starting on the wrong foot... :-( :?
Anyway a couple of more question:
1) Is there a place like that for XDA II Kitchen? Is my undestanding of what a kitchen is correct?
2) The process for ROM backup outlined above, is still correct for XDA II?
Thanks!
Chris

I'm in the same boat as you CChris. I've been diligently a daily searching through the numerous topics on this site looking for similar information. I haven't found it yet - or at least nothing not-to-super-technical. I do know that you get to the bootloader by pressing the power button, reset button, and down on the toggle at the same time rather than the Wallaby way of the power and reset buttons only. It also seems that there are issues regarding 'country' and that it requires software to get around this. I haven't found the software yet - the links that I've seen all point to "itsme's" website which is currently down.
You can read the thread here: http://forum.xda-developers.com/viewtopic.php?t=9053&highlight=
Hopefully, someone with a lot more knowledge than me can go over updating the XDA II as clearly as cruisin-thru did for the XDA I.

The instructions on http://wiki.xda-developers.com/wiki/HimalayaRomFlashing are correct.
Unfortunately, there was an issue where the wiki removed the ~ from itsme's website's address. It's been replaced with %7e and now the link works.
If you download a ROM from the same vendor as your device (e.g. Qtek ROM on Qtek device, iMate ROM on iMate device, etc.) you don't need to use these instructions, you can just install the ROM upgrade from your vendor.
If you want to use the latest ROM (from iMate) and your device isn't an iMate, you need to decrypt, change the "country" code, encrypt, and then run the upgrade.
You can also edit the extended ROM when flashing, but it's easier to use itsme's extRom Tools. See http://forum.xda-developers.com/viewtopic.php?t=8422
You do NOT need to flash the ROM if you are not experiencing problems, or if you are experiencing problems which the new ROM also has (for example ugly cleartype fonts, which may be fixed without flashing). Flashing the ROM may void your warrantee. You will lose all your data when you upgrade, and you should not restore a backup, only your my documents folder.
If you are a newbie, it may be best not to flash your ROM. If you typed in itsme in google, you would have found his xs4all address as the third link, and would have quickly found out his site wasn't down at all, but the link was just wrong.
Just a warning: the things that could go wrong when flashing are potentially much worse than a wrong URL, and the answer to those problems won't be the third link in google.

NO MATTER WHAT YOU DO DON'T COME NEAR THE RADIO UPGRADE I QUOTE I FRIEND HERE THAT SAYS
DON'T MESS UP WITH A WORKING RADIO OR YOU'LL END UP WITH A SLIVER BRICK !!!!!!!!!
BEEN THEIR :x :x :x :x

Rabia said:
NO MATTER WHAT YOU DO DON'T COME NEAR THE RADIO UPGRADE I QUOTE I FRIEND HERE THAT SAYS
DON'T MESS UP WITH A WORKING RADIO OR YOU'LL END UP WITH A SLIVER BRICK !!!!!!!!!
BEEN THEIR :x :x :x :x
Click to expand...
Click to collapse
Rabia can you tell me how did you get out from there?

never got out of it

Dead - well Almost spv m5000

Hi,
I have been donated an Orange SPV m5000 to help with my disseration,
unfortunatly the rom as been tampered with or removed , well im lead to
believe. Due to this the phone no longer turns on, the only thing the handset will do is get to the bootloader screen.. after resetting the factory settings the handset still does not turn on. i think the handset therefore has no ROM files on it as I have tried to update using downloaded roms such as
Orange_SPV_M5000_v1.13.49_WWE
JASJAR_WWE_11353_137_10301
both say that they cannot communicate properly with the device...
using MaUpgradeUt_noID and following instruction posted the handset starts to update but then says that the updater is not compatable with the handset... any suggestions on how to load a new rom onto the handset would be greatly apprecieted or infact how to to fix this problem with limited technological knowlegde
thanks
cjh28

I'LL GIVE YOU 50 QUID FOR IT!!!!!!!!!!!!!
****, not even I'd be that cruel.
First off I'm 75% sure your device is fine.
ROM chips are nigh on impossible to remove without breaking the device and doubly nigh-on impossible to put back in! No one in their right mind would even concider doing such a rash thing, espcially with something that costs this much!
Now I think the problem is the same as the one I had - these ROM upgrades can contain many separate updates which are then kind of glued together - the problem is (and the problem you may have) is that they don't all match what is already in your PDA.
You therefore have to do one of 2 things:
1) Find an upgrade that DOES match - but then you'd have to know what's already in there & then find a match - unlikely.
2) Make them match with a bit of jiggery pokery. read THIS:
http://forum.xda-developers.com/viewtopic.php?t=40986
Seriously dude, good luck!
Andy

Still Dead well almost
Thanks for pointing me in the right direction, Ive been thru the directions on the link provided and still having no luck, am still getting a communications error - 101 from the update ... am thinkin ive got the incorrect orginal roms ... does any1 know where i can find the orginal roms for a UK Orange SPV m5000 ( am currently using a rom that gives me operator name as Qtek and WWE - the name of the file is on my orginal post)
any further help/guidance would be greatly appreciated....
Many thanks
cjh28

Flash It Again
1. Download This:
http://www.business.orange.co.uk/se...c=PaDPage&cid=1044130840493&mid=1044129390154
2. Make sure u are not using a USB Hub
3. Make sure u are using the proper USB Lead!!!
4. Install Active Sync 4.1 On your Computer (it needs the USB Driver Within this Program to communicate with your UNI.
5. If you have followed all the above correctly your SPV will flash
especially if it is going into bootloader mode.
If you get country error or comm error, hit update AGAIN, DO NOT Disconnect.

IF the upgrade wont go 100% thru, try upgrading the radio only by deleting all the .nbf files except the radio_.nbf then run MAUpgradeUt_NOID.exe

Up and Running finally .... thanks
Just to say that my SPV M5000 is now up and running.. thanks to Andy and comp.solutions for helping me out, just followed ur instructions took a few attempts but its all gd now
Many thanks
cjh28

Damn! Bang goes my 300 quid profit!
No, seriously dude, you don't know how much 'inner glow' that gives me to know that we have helped you recover what may have seemed a lost cause.
Well done! :wink:
Now you can spend the next month trying to figure out how to get things to work 'properly' on the bloody thing..... :lol: (i.e. guess what I've been trying to figure out for the last month: Bluetooth, WiFi, ActiveShyte, installing programs, discovering what a 'uni' is, what 'BT' is blah blah blah.... :roll: )
Andy

Fixed M5000
Glad to Help, Enjoy :wink:

windows mobile 2003 software

HELLO,
IS THERE ANYWHERE ON THIS SITE WHERE I CAN DOWNLOAD A COPY OF WINDOWS 2003SE SO I CAN REINSTALL IT ON MY SPV M1000.
PLEASE HELP.....................

Hello didgeridooplayer.
First, welcome to the forum!
Second: Please refrain from typing in all uppercase letters, it's considered shouting.
As to your question:
I saw you other post in the Himalaya forum, but I reply to this one because I don't know what causes the camera problem.
I don't think you can solve it by 'reinstalling' the OS. This is not a PC. Windows Mobile is embedded in ROM, and although you can upgrade it (because it's actually flash and not real ROM), to clean up the device hard reset is sufficient.
The OS could not have been damaged by any installed program like it can be on the PC.
Now, I am not sure but there may be a Himalaya ROM on the ftp:
ftp://xda:[email protected]
However, Windows Mobile ROM images are custom tailored to a device. It's not like Win XP where you just get a disk and install it on any PC. It has to be custom made by the OEM for each device.
If you already knew this stuff and my post sounded insulting in any way, I am sorry, I just got an impression from your post that you didn't quite understand the issue.

Windows Mobile n stuff
Hi, Firstly thank you for the reply and secondly sorry for the caps. No you have not offended in any way I am a complete newbie numpty and did not know about the things you mentioned I know my way arround a pc but the ins and outs of PDA's are somewhat of a mistery to me. Anyway the reason my cam did not work was because I did a soft reset before the pda installed all its customisations to get round the password problem and therefore it did not get chance to load its camera software or album etc etc. Anyway I am trying to get the guy who sold it to me on ebay to give me a refund but doesnt look to promising (bloomin Ebay is a pain in the bot) but I will see what I can do.
Thanks again...Tim

Hi didgeridooplayer.
Glad I could help.
If you can't get a refund here are a couple of things you can try:
1) If device was locked by password, hard rest should have cleared it and you shouldn't worry about installing the customization since the password has nothing to do with it (it's just some stuff like cellular provider settings and some extra apps the OEM chose to include). Unless the previous owner changed it.
2) Customization is stored on the 'Extended ROM'. This is part of flash that is normally hidden from the user. However with some registry tweaks it can be unlocked and used like extra storage that will not be deleted during hard reset.
I don't know how to do it for your particular device, but if you look in the WiKi, I think you will find the answer. You can then replace just the contents of the Extended ROM (no need to re-flash the whole device) or just install the camera cab from it. That should solve your problem.
P.S. All installations on the device are done by *.cab files. You can launch them by tapping on the file from file explorer on the device.

Re: Windows Mobile n stuff
didgeridooplayer said:
Hi, Firstly thank you for the reply and secondly sorry for the caps. No you have not offended in any way I am a complete newbie numpty and did not know about the things you mentioned I know my way arround a pc but the ins and outs of PDA's are somewhat of a mistery to me. Anyway the reason my cam did not work was because I did a soft reset before the pda installed all its customisations to get round the password problem and therefore it did not get chance to load its camera software or album etc etc. Anyway I am trying to get the guy who sold it to me on ebay to give me a refund but doesnt look to promising (bloomin Ebay is a pain in the bot) but I will see what I can do.
Thanks again...Tim
Click to expand...
Click to collapse
Hello,
you stoped the proces of customization. in this process device install all aplication from Extended ROM.
Your album and camera, and maybe other aplication are not runnig because they aren't installed.
Just do a HardReset and wait the customization finish.

Can't seem to install anything on ATT Pure...

I can sync and copy files like several of the cabs from this site to the phone Storage card or My Documents in the phone and when I try and run any of them I always get an Unsuccessful .
is the ATT Pure Application locked? I did notice that all the applications I am running are not digitally signed or signed by a trusted provider and the phone complains and ask if if I still want to run. I pick yes and it still fails.
Any thoughts? I know some of you have ATT Pure devices!

FIXED
I did this and all is working...
1. Deleted my partnership with my laptop (Win 7 64bit)
2. boot my ATT Pure
3. Connect but dont establish partnership
4. copy over the cab files you want
5. use file explorer on the Topaz (Pure) to run them
6. all works fine!
7. loading EnergyROM now
the lesson to be learned if it does not work for you and it works for everyone else then go back to the basics!

Welcome to AT&T... yes all branded phones are app locked because they want to force you to use their apps.
You can app unlock it using a cab install... but some new phones are even rejecting that.
Official and Custom roms are the way to go. I recommend everyone with a Pure to at least flash to the newest Official WM6.5 build. It will work just the same but be clean of AT&T junk.

I have an AT&T Pure
I have no particular problems with installing Cabs
As another poster said copy the cab to a temp directory
and run it from File Explorer (delete the cab to save space after its been run)
Or you can use "CabviaActivesync" availabele on this site which makes it a little bit easier. (but I did have two cabs that had bad setups and needed manual install)
Bottom line the PURE does not block most cabs (I've tried)
(I only had a problem with the write protected weathercity database now ok)
Chances are something is wrong on your Pure or your method
To the senior poster that replied
Hey I've made tweeks and played with the stock ROM
I'd love to clean the bloated and unused ATT aps
incorporate weather into the clock ( TF3D 2.5+++)
and get a cleaner start menu (too many aps)
and certainly see an improvement in performance and snappiness
Id love to try a new ROM
but most new roms are written for Diamond2/Topaz
I'm not clear if the radios are the same on the the D2 and the Pure?
Can I burn WM and TF3D without affecting the radio part of the code?
Are the any other issues we need to be aware before we burn a new Topaz rom
onto an ATT variant of the Topaz ?
Is there a copy of the original Pure Rom available in case we need to return
it to ATT (what else would we need to insure we could return to ATT to fix any other later warrenty covered problems)
Of course I realize there is a risk invilved,
but whats the best safety prep?
I'm new to phones but an old micro hard/firm/soft ware and PPC guy
Thanks in advance
KJL

I haven't had a single problem installing anything on my stock Pure. Even software that normally requires an app-unlocked phone installs just fine.

I'm also curious about what Kenn asked. I'm getting a Pure tomorrow and I won't be able to get the crapware off there fast enough.
Specifically, can I flash the official HTC 6.5 rom to the Pure without having to hard spl? Is is just a straight flash?

I have the same problem with this ROM: http://forum.xda-developers.com/showthread.php?p=5743820#post5743820
Everything is OK but installing the cabs.
When I try to install any cab it wrote me "Instalation of ... was unsuccessful."
I tried a lot of cabs and all of them are the same
Any help please?

.
This particular problem gave me 4 day headache last week when i couldn't figure out why I couldn't HSPL my Pure. Had to Hard Reset entire phone, everything worked

Yes, I also hard-reseted my phone yesterday and everything works now!