JP1 Remotes

I was learning new codes via the ir learn function of my URC-8210 and it suddenly "locked" itself - the EL stays on and no reaction to any key press.
After removing the battery it "locks" again after a couple of commands - the EL stays on, no reaction to any key press, no device highlighted.
I have tried the 981 reset code but that doesn't help.
I have tried uploading and older image via the JP1.3 cable using the latest RMIR, that didn't help either.
When trying to read the remote after the 981 reset, it's looking OK.
When trying to read the remote after a "lockup" I get an error and I can only download as raw.
My theory is, there is some part of memory corrupt, which isn't fixed by the reset.
I hope I can make the URC-8210 working normally again by resetting/cleaning the corrupt part but I don't know what and how.
Here is the raw download from the remote after a 981 reset: https://www.hifi-remote.com/forums/dload ... e_id=13987

Any ideas how to solve this problems?

Thank you.

Edit: Here is a raw after corruption for comparison: https://www.hifi-remote.com/forums/dload ... e_id=13988

Some more files for comparison: https://www.hifi-remote.com/forums/dload ... e_id=13989

There are two pairs of files
ir - download with ir
raw - raw download with rmir

I uploaded an older working image to the URC-8210, then immediately downloaded it. Then tried to use the RC, it locked up. Then I downloaded the files with index 2.
I hope someone more knowledgeable can figure out what is wrong comparing these file sets ...

That's what it does when the batteries are low. Put in new ones.

Thank you for your suggestion.

I've tried 5 different pairs of batteries, sadly it didn't help.

Sounds like it's time for a new remote. If you can get it going, the $16 Nevo C2 would be a nice upgrade.

So is it broken beyond repair ... ?

When you say trying to use it again, was that using to capture or using to send IR signals?

I was trying different things, learning ir signals too.
When learning ir codes, it locked during learning the first or second signal.
But I was also trying to use it normally - sending commands.
It mostly locked when selecting device or sending the fist command.

I looked at your E2 area, and it looks like the a low battery situation to me too. Examine your battery connections. If there are signs of corrosion clean them. Then take a small flat blade screw driver and insert it between each coil of the spring and give it a quarter turn to make sure the spring isn't overly compressed. Then put your batteries in the remote. If the batteries can be shaken out of alignment then the batteries are too loose.

Also make sure you are using alkaline batteries, not rechargables.

These remotes hate to encounter low power situations. The symptom of low batteries is a corrupt e2 area.

Sorry for the late reply, I was away.

I'll test your suggestions tomorrow and report back.

I have examined the battery connections - they are clean and shiny, no signs of dirt or corrosion.
The springs are strong, holding the batteries firmly.
I bought brand new alkaline cells, each measured 1.55V.
Sadly the problem is still there.
My last idea is that maybe there is a loose connection between the battery contacts and the PCB, but I have no idea how to disassembly the RC to check it.
There are no visible screws.

Just some notes
- this RC was sold with Duracell NiMH rechargeables and a charging cradle, so I think it should work with rechargeables (and it was working with them for years)
- this RC indicates a low battery condition by blinking the signal transmit indicators