Error Code 1008

Thought my update went to smoothly.

When logging into traffic getting the following error message

Error Code 1008 Warning there is something wrong with your SIM card. Please contact Tom Tom customer support.

I am in the process of doing this but at 1800gmt probably will not get through till Monday so any comments welcome.

Julian

Following the above discovered that tomtom support are aware of problem.

Thought I would restore my backup and informed that the sd card was invalid and so no restoreavailable even though that was the one that was in the unit.

Well, we know you're in the UK, and have one of the old SIM cards! That's where the problem is occurring.

Yes, TomTom is very aware of the problem, and you should expect an update to 9.400 very soon.

Are you running your application off your SD card? If not, I don't understand the message you were getting. How did you do your backup? With Home or your operating system?

Hi I am running the unit from my SDcard and have both explorer and home backups.

Below is a copy of the fault log.

ERROR: Note: Some volumes (for example, a storage card) that were present during a previous backup are not currently present on your navigation device, and cannot be backed up or restored.
Stack:
0. chrome://tthome/content/ui/bindings/commit.js:82
error(textOrException);
1. chrome://tthome/content/ui/bindings/ttwizard.xml:1061
this._commitFailed(i, commitPage);
2. chrome://tthome/content/logic/util.js:80
return func.apply(obj, arguments);
3. chrome://tthome/content/ui/subtask/restore/restore.js:72
errorCallback(errorStrOut.value);
4. chrome://tthome/content/logic/util.js:80
return func.apply(obj, arguments);
5. function _startCommitFunction chrome://tthome/content/ui/bindings/ttwizard.xml:1057
{
6. chrome://tthome/content/ui/bindings/ttwizard.xml:1021
}
7. function onPageChange chrome://tthome/content/ui/bindings/ttwizard.xml:681
]]></body>
8. chrome://tthome/content/ui/bindings/ttwizard.xml:467
}

Time: Sun, 19 Feb 2012 18:29:08 GMT


The sdcard has not been removed or changed. as the unit is working well,bar traffic, will stay as I am for now hoping for no traffic jams assuming the fix is not to long

Thanks for help

Julian

In the meantime until TT has a fix for the SIM 1008 issue, for those who don't have backups, but want to return to the funtional 9.058 app, just download the cab file below, open it with winrar, and extract to the root folder of your Tomtom drive (overwriting when prompted). It will drop your app back to 9.058.

GO 540/740:
http://download.tomtom.com/sweet/nav...navcore-GO.cab

GO 940:
http://download.tomtom.com/sweet/nav...navcore-GO.cab

Thank you back to 9.058 see if it finds traffic in the morning at least the error message has gone and showing connected to network.

Thanks Julian

Hi
Made the mistake of updating the operating system late on Sunday evening and believe me Monday morning I was not a happy soul. Found this fix by doing a Google search, followed the process listed above and now have fully functioning live services again. Got stuck on Monday morning in a huge jam and had nothing to help me avoid it. I also use the local google search function significantly and was lost without it, I was expecting to have to wait until TT finally got around to developing a fix. Not really impressed with the support they offer.

Thanks again

Spanner-do

Glad you found us here. Have to believe the solution will be readied soon. Too many unhappy users, and TomTom is WELL aware of the problem.

This is a bug in the new app. software. First line support say DO NOT delete new version and then reinstall old version from Home. (This was suggested when the same fault occurred on the last app upgrade.) Second line support have said a bug fix will be available ASAP

Almost a week, doesn't look like there's a fix out yet. Any idea how much longer it wil take?

I have no way to know what the timeline looks like at TomTom for bug fixes, but I do have experience with what it is like in another industry. One week would be incredibly quick for any software change other than the wording of an on-screen message - and even that type of change might take longer.

The problem is that it is necessary to do a lot of testing to make sure that you have not broken something else in the process of fixing this bug. When thousands - or even tens or hundreds of thousands - of units already in customer hands are potentially impacted, the prudent course is to "Make haste slowly".

Having said this, I would be surprised if TomTom does not get the fix out in the relatively near future, just because of the visibility of the issue.

- Tom -