Replacement Vodafone V1620 problem

[jbn]

This is my second V1620 in about three weeks: the first replacement was after about nine months because the SD card slot stopped working. The replacement suffered severe touchscreen drifting and needed alignment every five minutes so they swapped it for me.

No complaints about Blue Angels or Vodafone: here's my problem. I use SPB Backup and am very careful about this to restore my system so that TomTom continues working OK. However after restoring my system today I find that TT (Navigator 5.21) is now coming up with a different device ID than before so my continuity is broken.

Does anybody know why this would be? I have checked the ROM version and there is no change there, although I am in desperation about to flash using the same version. I have no logical reason to this but I am clutching at straws!

All suggestions gratefully received, and many thanks in anticipation.
Jonathan

[xan]

Strange.. My Vodafone v1620 has a deviceid of PH20B2, check if yours is like this, using GetDeviceData (http://wiki.xda-developers.com/index.php?pagename=GetDeviceData)

[jbn]

Thanks xan, that is quite correct. The thing is that every pocket PC generates an unique system ID every time you do a hard reset. This is stored in software and can be overwritten by restoring a backup. In this way programs that are keyed to that ID such as TomTom will continue working even after a hard reset. If you do not take a complete backup, using Activesync or any other tool, then you would find that they stop working which is the situation in which I find myself now.

The strange thing is that I have made hard resets and restores many times over the months without a problem, hence my appeal for help!

[xan]

Do you know where this id is stored?

[jbn]

No idea, I'm afraid. All I know is that if you make a full restore then it reverts. I believe that it may be referred to as System ID or SID as under W2K and WXP.