Hot sync loop HELP!! - Treo Forums

Blancosito · 08-12-2006, 04:20 PM

Okay my treo 650 is a cingular unlocked gsm. It has been working great but is now useless and i need to fix it if possible. When ever i start it up it immediaely goes into a hot sync loop. whenever i hit cancel it returns to hot sync mode. If i can put the key guard on as soon as i start it up it wont go into the hot sync loop, but its useless becasue as soon as i undo the guard it starts it right back up? please help and offer any advice.

Stillrockin · 08-13-2006, 05:56 AM

If it were me, I would go ahead and perform a hard reset. Have you installed anything new lately? You said that everything had been fine until lately. Just wondering what might have changed to suddenly cause you the problems. If you have added something new in the last few days, I would remove it in the back up folder before syncing everything back to the Treo.

jtland · 09-04-2006, 06:48 PM

Quote:

Originally Posted by Blancosito

Okay my treo 650 is a cingular unlocked gsm. It has been working great but is now useless and i need to fix it if possible. When ever i start it up it immediaely goes into a hot sync loop. whenever i hit cancel it returns to hot sync mode. If i can put the key guard on as soon as i start it up it wont go into the hot sync loop, but its useless becasue as soon as i undo the guard it starts it right back up? please help and offer any advice.

Yes, I have the same problem with a Cingular Treo 650. Resets do not solve the issue. I'll call Cingular and will post any solution, but am fearful it's a "send back."

Stillrockin · 09-05-2006, 05:13 AM

Please do let us know what you find out jtland.

jtland · 09-12-2006, 06:42 PM

I'm sorry to report I found no solution. Neither Cingular or Palm could help. After returning to Cingular from Palm the fix was a new Treo 650 @ $425.00.

Stillrockin · 09-12-2006, 06:51 PM

Well, glad your back up and running but sorry it took another $425 to solve the problem.

Honestly, as long as I have been a Cingular customer, if they couldn't do me a better deal than a new price, I believe I would leave them for Sprint or Verizon just to spite them . . . .

After all, you can get a 700P/W for $125 less . . . . Heres to hoping the new 650 is trouble free for years to come!!!

jtland · 09-12-2006, 07:09 PM

I agree - it's not worth $425. I certainly did enjoy the Treo 650 while it was working.

ajdele · 03-08-2007, 12:34 PM

I just bought a treo 650 on ebay and am having the same problem. I have asked questions of the seller but dont expect to find a solution along those lines, will probably only be able to leave appropriate feedback. Regardless, I would like to be able to fix the problem and keep the divice.

Here's where I am so far. I have determined that the unit is getting a button input that tells it someone is pushing the hotsync button on the cable. Easy way to confirm this: in the "Prefs" application, under "Buttons" change the hotsync button response to another application besides "Hotsync." I changed mine to open the "Phone" application, immediately after turning the unit off, the phone screen popped up. This at least confirms what the palm thinks is happening to it.

I have also done the hard reset thing and the problem persisted, even before putting any software or data back on the divice.

A few strange things (in my case) that lead me to believe that the problem (and possible solution) are not so simple. First, the ghost response does not work the same as the actual button response. Plug the cable in and hold down the button, hotsync screen comes up, cancel the hotsync (while still holding the button) and see what happens. Nothing. It does not insistently pop back on trying to hotsync. Mine also seems to wait random periods of time before coming back on. At times it will go for several hours, then go a whole day coming back on a second after the power-timer has shut it off.

Last night I opened the casing and cleaned it out extensivly, there was a lot of dust and small hairs in it. After cleaning this out the problem persisted. I was so disgusted with it I took out the battery (so I wouldnt have to see it flashing all night), SD and sim cards to use them elsewhere. Today I put the battery back in and ..... its not ghost-inputing anymore. I even hotsynced and its fine. I am going to keep my sim and SD cards out right now and try to use the unit as if it were just an organizer. Its been powered for a couple hours now and no indication of the old problem.

So now I am wondering if it is something on my SD or SIM that is causing a strange conflict.

I am scouring the internet and will post this where I can hoping for help. Please post if you are having a similar experience.

Stillrockin · 03-08-2007, 07:09 PM

I think the next thing I would do if it were me, would be to get the SIM in it. Also, if your SIM is an older one, you might consider upgrading to the 2g sim card. I am told the smaller memory sims cause problems with the 650. If that SIM works with no issues, I would plug in another SD card. If it still works, I would probably toss the other SD in the Garbage . .

Good Luck and keep us in the loop. I am curious as to if it is the Sim or SD card . .

alexcoupe · 05-15-2007, 07:21 PM

My Treo was stuck on an endless hotsync loop without it being connected to cable. I researched and from different sites it was pointing to pins being shorted were you plug your cable. I looked at mine and did not see anything. I also cleaned the treo in the contacts and inside the unit with no help. I am a pc tech and started to troubleshoot as if I were working on a machine and cleaned the treo leaving the default apps. The device did not hotsync after that. So I determined that it was a software conflict. I installed all apps seperately creating a new hotsync profile on the pc with no loop. I read somewhere that corrupt contact files in you palmone folder on machine gets placed on treo after first hotsync. So I moved my contact files stored in C:\Program Files\palmOne\(Profile name)\Backup and hotsync fixing issue.

I hope this helps anyone having this issue.