I have read a lot of threads about this stuff, but I still need help. I just bought this thing... used, so there's no warranty.

Here it is.

The remote worked fine with defualt settings and ccf when I first got it. Can't remeber the firmware version but it was old.
During my first attempt at updating the firware to the latest, through PE4.0.5, the download failed. The exact message I didn't notice as I was not too concerned at the time.

So then I reset the remote and it just gives me the 4 beeps and nothing on the screen. I've since tried downloading new and old firmwares directly and through PE4.0.5, PE2.0, and Tonto1.39.

Each time seems to give me different messages. The first few times it asked my if I wanted to update segments and then failed. Now, the most common error in PE is:

"Could not get information of your BOOT segment!"

Actually now I don't even get that, now when the update program asks me to reset the remote, I do so and nothing happens. The update never kicks in and the remote gives me the 4 beeps.

I've tried every COM setting I could think of and that has been suggested, I've removed and replaced battery (although only for 2 hours) and I've connected through hyperterminal to see if there's anything going on there.

The first time when resetting the remote while connected to hyperterminal this is what popped up:

¸2
04
�
ãOOT,400000[00],UDB V3.0 AMD S2 ,09/20/2000,17:24:57,ãRC OK
20
PSOS,404000[02],V1.0 ,06/19/2001,09:53:47,ãRC OK
60
_APP,440000[11],UDB V5.1 ,09/20/2000,17:28:26,ãRC OK

There are some garbage characters there that concern me.

Now when I reset the remote while connected to hyperterminal this is what popps up:

¸¸
¸»
04
��
Booting...��ãOOT,400000[00],UDB V3.0 AMD S2 ,09/20/2000,17:24:57,


And that's it. The remote continues to the 4 beeps

Any help... Please? I have no idea what to do now and I'm considering going back to my HTM MX-1000. I had so many problems with that remote so I would rather not. But at least it worked.
Is there no way to revert this thing to factory setting?

Thanks for any help... those four little beeps are going to give me nightmares
eric

This message was edited by ericdork on 10/16/02 23:43.00.

wow... that's long! Sorry about that folks.

eric

Much MUCH better than not enough information.

I only wish I could help you, but my T2K has never died on me. I'm sure someone will chime in here pretty soon.

Seems like you've covered most of the bases, except leaving the battery out for at least 8 hours (more seems to be even better).

Also, please see Rule #43.

    MIKE

CLICK ON THESE LINKS
FAQ | Files | Reviews | Play with it | Phases | Planning | ALIAS.CCF | Copying .BMPs & Galleries | Discretes | Docking Station | NEO | X-10 | Parts | Cable | Buy/Sell

I have an RC5200 that got corrupted during a download. It went into a continuous reboot mode and wouldn't work after the four beeps. I connected it to my PC using the Marantz version of ProntoEdit (Touch Screen Setup). I dowloaded the latest firmware updater from the Marantz site. I launched the firmware updater and it told me it was ready to update my firmware and to reset my device. Since it was continuosly rebootoing itself, I didn't have to push reset, I just waited a few seconds and essentially the updater was given the impression I had pushed reset when it detected another reboot starting. It then proceeded to update my firmware and asked me the question: Do you want to keep your old .ccf configuration? I figured the .ccf was corrupt, so I told updater "no". It finished and voila, the RC5200 started working again, albeit withe the factory default .ccf. I then downloaded my original (uncorrupted) .ccf into the device and I was good to go. I've read in the FAQ that sometime it will take many attempts to get the firmware to install on a corrupted device. You might keep trying. Also, you might try leaving the batteries out for 24 hours and see if this either clears the problem or at least allows you to update the firmware and replace the .ccf file with the factory default in the process. Good luck.

Eric,
It has happened to my tsu-2000 not once but twice. Of course the first time I came on here just like you did. But I didn't know how to use hyper term, still don't.
So what I did the first time was the leave the batteries out for a day, a gruling day. Reconnect them and updated the firmware once again. I don't remember if I said yes or no to the save currect ccf. However, it did work.

A week or so later, it happened again. But this time I was just looking on prontoedit.com or whatever it is. And found something to the fact of taking the batteries out, and to drain the charge hit the volume up and down buttons back and forth. I did it for a few times. Replaced the batteries after about a few minutes later. It then rebooted as normal, I didn't even have to update the firmware.

So whatever works for you, hope it does.

Rob

Looks like some of the information on the segments is corrupted. That could cause the problems your seeing. When using Tonto to flash firmware, check the option to 'Reload current segments' which has the side-effect of causing it to ignore this garbled info. It just might work.

I saw that too and it didn't work. I also tried leaving my batteries out for about 14 hours, thinking that was my last hope, but still nothing.

But... I finaly got it to work. I took it to a NT4.0 machine (I use 2000pro) and first try, no fuss, re-flashed like a charm (just straight from the update program). Don't know if it's coincidence or there is some difference in downloading from NT... but, it's yet another solution for all those dead Prontos.

So... I'm happy now that I don't have to throw it out. I hope I don't have anymore troubles though... I would have found great cathartic pleasure in smashing it into small pieces with a hammer.

Thanks all

......But now, just think of the great pleasure you'll get from sitting in your favorite comfy spot, remote in one hand, icy-cold beer in the other . . . pressing just one button and thinking to yourself . . . "..ya know?. If it just did it this way instead of that way........hang on, I'll be right back.........."

Yours sincerely,
Brigadier N. F. Marwood-Git [Mrs.](MPD)


As always . . .
Doin' it myWay