Related
Please help. I flashed 2.16.9.x and now ActiveSync doesn't work anymore, it connects all the time. PDA doesn't show activesync syncronization icon.
I tried to flash another versions of ROM, but it didn't help.
The problem may lie with the PC as opposed to the PDA. Have you tried a remove / re-install of AS4.1 on the PC?
Bebbo said:
The problem may lie with the PC as opposed to the PDA. Have you tried a remove / re-install of AS4.1 on the PC?
Click to expand...
Click to collapse
Of course I have. Even I tried on another computer.
vishny said:
Of course I have.
Click to expand...
Click to collapse
Fair enough, I was just trying to help. Perhaps if you had stated that in your original text I would not have provided such an "Obvious" answer. I will leave it up to others now to take guesses as to what you "might or might not have done"......
vishny said:
Please help. I flashed 2.16.9.x and now ActiveSync doesn't work anymore, it connects all the time. PDA doesn't show activesync syncronization icon.
I tried to flash another versions of ROM, but it didn't help.
Click to expand...
Click to collapse
Try to make your computer or laptop restore on earlier date then since it started. I had once this problem i don't know but sometimes it with the system files in computer missing then the problem occurs.
Although my ActiveSync works almost fine after the same rom-upgrade, I encounter its strange behaviour sometimes (rear, not always!) - PDA slows down to a crawl right after you disconnect it from a desktop PC (either USB or Bluetooth). It becomes so terribly slow that it takes 20-30 sec to draw the Comm-manager window! then you better soft-reset, then it works just fine. Why am I... to prove that ActiveSync 4.1 is not quite stable with new ROM version 2.16. There is a bug somewhere, and it has to be reported to i-Mate firmware writers.
Have you followed Microsoft rules about configuring firewalls for ActiveSync 4.1? Does it create a network connection 169.254.2.1 on a desktop PC?
Thank you guys, but I guess my case is harder:
1. I have firewall switched off. I didn't change any setting in computer. I just flashed new ROM.
2. I flashed my original ROM, but it didn't help.
3. I tried to sync on several computers and had the same result.
By the way I cannot return to original ipl/spl, I don't know how to do that.
Today I visited repairing service's office and they've prooved me my device is not broken, it synchronizes succesfully via USB on their computer. :shock:
So, the problem is related to my computer(s). If I'll find something I report in this thread.
it probably has to do with one of the cabs you installed that are on your original extrom or someone elses. Most people who have had problems after the upgrade on an 8125 (Cingular) have installed cingular cabs from the old rom. I had to to figure out the MMS configuration and after I foundthe one that did my activesync no longer worked. after a reflash and only installing some of the default cabs that came with the new rom and manually configuring the mms and gprs I don't have any problems at all.
well maybe it is the version of activesync we are using when this does happen.
I'm running the ROM that came with the Cingular 8125, and it does the same thing ... 1 in 10 times after disconnecting the device from the PC, the 8125 slows to a crawl, and the only way to recover is a soft-reset. 9 out of 10, it works fine.
OS ROM: 1.8.11.1 WWE
Radio: 01.09.11
Protocol: 4.0.13.20
not overclocked
soon to be ROM upgraded (hopefully)
ethorn said:
well maybe it is the version of activesync we are using when this does happen.
Click to expand...
Click to collapse
I use 4.1 for a long time.
I didn't install anything on my pda. It happens even after hard reset. I even tried to flash original rom. In all cases ActiveSync displays "Connecting...", pda even doesn't display sync icon.
I tried to sync with standalone notebook and it was successfull. I'm really shocked why pda cannot sync with my desktop(s). It seems to me it could happen after some windows unattendant updates or something, I'm still investigating...
I have Qtek 9100 and have installed rom 2.16.9 and i also have activesync 4.1 refusing connection to my pda. After some googling i have found this interesting site: http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x-connection.htm
I did cheks described there and found out that activesync doesnt have any network adapters and/or activity. USB driver installs, but it, again, doesnt generate anything. Maybe problem is there?
Ehhh... I even cannot return to any previous rom version, because there is no rapi for updaters to work with
reverting back to original cingular rom
How would you go back to original ROM using Lokiwiz tool if your active sync was working OK?
Thanks,
Each time I have done HARD RESET--I uninstalled active sync from my computer AFTER DELETING PARTNERSHIP. I deleted PC from Active sync on my 8125. I deleted all files on my computer related to active sync using search.
I then reinstalled active sync 4.1, being sure WINDOWS FIREWALL was off. I went thru all the steps with my TREND MICRO VIRUS PERSONAL FIREWALL EXCEPTIONS listed on http://www.microsoft.com/windowsmobile/help/activesync/default.mspx
and I got it to work (1st install always takes time for calendar)
Hope that helps--it seems ridiculous to have redo all that-but so be it.
I'd like to know how to get back to CINGULAR ROM as I am still in 30 day return window.
Well there is a magical combination of buttons as described in http://forum.xda-developers.com/viewtopic.php?t=37386 (somewhere around 2-4 page):
Voice+Camera + Reset. Colored bootloader shows up. After that you can connect it to usb and run .exe with rom you want.
The problem with me is that i dont use any 3rd party firewall (i have hardware router for my connections)
reverting back to original cingular rom
You don't think there would be a problem going DOWN in ROM'S?
Do I need to UNLOCK again first?
I must confess. I did (i think veeery lucky) sucseded in running activesync. Altough what was the cause i cannot say. I reverted to 1.6.7 version of the rom. and reinstall everyting several times. and reboted several time. and i saying loud magical words. (and deleted checkpoint vpn software that i have installed). AND it worked!
Maybe trouble was in vpn soft, but it worked pre 4.1 activesync. So... Here is my experience.
Boki said:
I have Qtek 9100 and have installed rom 2.16.9 and i also have activesync 4.1 refusing connection to my pda. After some googling i have found this interesting site: http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x-connection.htm
I did cheks described there and found out that activesync doesnt have any network adapters and/or activity. USB driver installs, but it, again, doesnt generate anything. Maybe problem is there?
Ehhh... I even cannot return to any previous rom version, because there is no rapi for updaters to work with
Click to expand...
Click to collapse
Thank you very much for this link, it helped me to find the reason. It's not new ROM fault. The Microsoft Firewall Client (ISA 2000 component) on desktop blocks communication between PDA and desktop. I disabled it and now ActiveSync works fine.
Thank you again.
Your Are Welcome
I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Drake008 said:
I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Click to expand...
Click to collapse
I'm using a Vista PC.
After the Radio update to 1.15 the error described above is not to go away yet.
What to do, I'm nearly in tears.
Finally I got it back but with an old Romupdate from T-Online. Is there someone who got the QTC 9090 update (latest one)
That was fast..
im glad you solved your problem.
i think someone here has it.
just post what you need and make it as a title for others to read in the digest.
Im not a expert but is vista the problem??
Most likely.
Failed MDA II flash with vista notebook
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
mda3newbie said:
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
Click to expand...
Click to collapse
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
mda3newbie said:
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
Click to expand...
Click to collapse
In vista i dont know...sorry for my late reply too.... in XP u must kill ActiveSync process called wincecom.exe. in vista, maybe u have to kill the Windows Mobile Device Center....i dont know...
Dont forget, put the Qtek 9090 in Boot Loader Mode (Pressing Power Button + Record Button + Reset), maybe will appear USB and u can format the device.
If this does not work, try on Windows XP....Find a friend with Windows XP and ask him to use his PC only to do that.
Maybe somebody in forum have the Windows Vista and can help u....
Sorry my terrible english....
Sjogos said:
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
Click to expand...
Click to collapse
hi guys I tried the step by step process and when im enterin( Task 28 ) then pressed Enter -
Invalid command : Task28
For a help screen, use command ? or h
does any one know where the problem is??
Try this
Downlaod the XDA IIs .exe file and run it - no need to put into USB mode
http://www.o2online.ie/wps/wcm/conn...es+&+accessories/Xda+Range/Software+upgrades/
this should reset to factory default (o2)
it runs on vista too
I am not 100% sure it will work but worth a try
diesel_dog said:
Im not a expert but is vista the problem??
Click to expand...
Click to collapse
Yes, i know my reply is late but the problem ist 100% Vista! i Tryed 2 ours with vista...then i decided to format my pc and to install XP. At the first try it worked!
Hello.
Im new here, first of all sorry for my english, and second thanks for this forum.
I have problems with upgrading my Siemens SX66 WM6.0 pro to a WM6.1
The ROM upgrade software tells me there is an Error 101: Connection Error
exactly like this
bilbo--baggins
Every time I try to do the rom upgrade for my PDA2K the device does a soft reset (when it's reset it then reconnects to activsync, and the green logo reappears) and after a while the ROM upgrade software tells me there is an Error 101 Connection Error. It's driving me nuts, I've tried all sorts of variants, soft reset first, hard reset first, USB port, USB2 port, Activesync 3.7.1, activesync 3.8, Windows XP, Windows 98. I don't understand why there is a connection error, because I can connect to activesync correctly, it even reconnects after the ROM upgrade causes it to do a soft reset. Please help! I've even tried following directions to copy the temporary files and running those directly but the result is the same.
Click to expand...
Click to collapse
can anyone help to solve this problem.
i have no problem with active syn connection, its synchronized with out any problem. my OS is winXP sp2.
This is a well known issue, I am sure its addressed in the Wikki on this site. The solution is don't reset your device when the on screen instructions ask you to do so, just continue with the upgrade.
Enjoy your new device once you have upgraded.
ok
i run upgrade program, the i like in instruction i put sx66 in to the cradle, active sync starting to synchronize well. then i push the next button in the upgrade program, the active sync is turning off and after couple minutes there is a message 'bout Error 101
p.s. the upgrade file i download from this thread http://forum.xda-developers.com/showthread.php?t=372485
I've spent whole day reading through the froum and the trinityguides.info site but can't find any proposed solution to work for my situation.
Device info:
ROM version: 3.00.707.17 (WM6)
ROM Date: 6/29/07
Radio version: 1.46.00.11
I've tried using all 3 versions of hard-spl but they all end up with the same result. With active sync linked and ready, ran the "romupdateutility.exe" at the end the PDA prompts if I want to run the "enterbootloader.exe", the moment I press yes the active sync connection would drop and eventually the program timed out with error "260" while PDA stuck in the tri color screen displaying the following:
TRIN100
SPL-1.07.ds
I've found some similar problems in the forum but those users are using vista however I am running XP sp3 in this case. I've tried all other solutions in the FAQ areas but none of them works.
My unit came with the WM6 already but I just want to upgrade the radio and get some cooked ROM to get faster performance. What am I missing here?
Any help is appreciated.
Once it drops to the tri-colour screen and is in bootloader, run the RUU again. Should be all that you need.
I've tried running it over and over but on the bottom it just kept on saying "serial" when it suppose to say USB.
Anyways, problem solved and it turned out to be the cable. For some reason the cable is good for anything, except keeping the phone connected/recognized while in bootloader mode.
I think this should be listed as one of the FAQ in the trinityguide. This might be a rare problem but it surely took me a lot time to figure out.
on Vista
Hi,
I have similar problem but I'm using Vista (Business). Is there any workaround ?
Regards,
Daneal
Hi
I have the same problem
spl 1.20 Olipro display serial instead of usb
I tryed several usb cables and still the same
when trying to update the rom it refuse to connect the ppc and end displayng the 260 error no connection
My system is vista and the first time I upgrade everything was fine, I followed all tutorials and no problem at all.
Do you think that could be this new 6.1 Mobile device center I recent install the cause?
best regards
Inabox
The problem isn't the WMC as such more the fact its Vista. Find an XP PC and do it from there.
Hi there, I had the same problem just now and cured it(in Vista). Just upgrade the htc driver in device manager again with "wceusbsh.inf" previous file, then should be ok. It seem to be Vista replaced the driver during it switched to Tri color menu.....
HI.. Im a newbie here, just got my g3 wizard ipl2.25 / spl2.25 couple weeks ago and seen what you can do with them. phone is sim and cid unlocked. i would like to flash to wm6 eventually all thought im running into problems. i followed all the guides to upgrade. tried on my vista 32 bit and win xp sp2. every time i run the button rom to downgrade, i get "romupdateutility mfc application not responding" on vista and "error 260 or 274" with the xp. ive tried it in bootloader mode, restarting pc and wizard, tried different driver for vista, and shut down AS and WMCD before attempting to flash. ive been at this thing for weeks. firewall and antivirus turned off on both pcs, phone is at 100% charge. once in bootloader i get usb at bottom of screen. so i know i have connectivity. run rom not in bootloader, identifies version, then goes to bootloader, then i get error. run again and it dont even identify wizard. happens with both pcs. any ideas please help. i have already read, read, read and still cant figure this out. any ideas are greatly appreciated.
First of all,as you say its SIM/CID unlocked already then why are you trying to downgrade with Button's Rom,its only needed to downgrade if its required to CID unlock.If you are sure its already CID unlocked than simply download any wm6 rom and flash to upgrade,but if you are not sure if its CID unlocked,download WST_4.2.2 tool and run it to verify the CID lock/unlock status.
sorry i made a typo. it is Locked both sim and cid. typed last night at 3:30 in the morning. i ran the wizard service tool and thats what it told me. sorry again
check firewall (even XP one) / anti-virus settings, avoid using front panel USB, avoid usb cables with electric components, try different RUUs, avoid Vista, try another XP computer
Take all the precautions mestrini has posted above and always try on a winXP machine,don't use vista for flashing.May be the Button's rom you downloaded is not a correct package,try to download it again or from a different download link,you can even downgrade with official AKU 1.xx rom if you can find and download.
thanks for all the idea. definately stop trying with vista. i already have tried downloading button rom from a different link, no electronics in usb cable, and firewall and anit-virus have been disabled. i just found a aku 1.xx rom last night so im going to try that tonight. thanks again
well i tried all that and still nothing always get a error 274 connection code. my xp is ran through virtualbox on a ubuntu machine. could that have anything to do with it? i can run WST that works fine. one thing i have noticed though is when my wizard goes into bootloader my connection gets lost and usb connection icon comes up with unknown device and a different pid # then if phone is just turned on, and no check next to it. i tried activating it while ruu is searching and that immediately gives me a 274 error. is it normal for product id to change when in bootloader? by the way i was using the cingular 1.08 ship rom this time, tried it about 15 5itmes with same result everythime. never touched the phone and never took out of bootloader.
litlldevill666 said:
... my xp is ran through virtualbox on a ubuntu machine. could that have anything to do with it? i can run WST that works fine. one thing i have noticed though is when my wizard goes into bootloader my connection gets lost and usb connection icon comes up with unknown device and a different pid # then if phone is just turned on, and no check next to it. i
Click to expand...
Click to collapse
I think you touched the wound!!
I guess RUU can't communicate properly through virtual box. Please try another XP machine before anything else (i think you can manage a friend with one since M$ is so spread - unfortunantely )
cheers
well thats what it was, i did a dual boot on my linux laptop with xp sp2. ran button rom and flashed first time. thank you both very much.
litlldevill666 said:
well that's what it was, i did a dual boot on my linux laptop with xp sp2. ran button rom and flashed first time. thank you both very much.
Click to expand...
Click to collapse
Thanx ! it was pleasure to help you,hope you upgrade it successfully,do let us know if there's any problem,we are always here to help,Thats what this excellent forum is all about !!!