TomTom 700 - Flashing X

[smileface]

I know this is a long shot because the TomTom 700 is no longer support and old, but here we go....

My TomTom 700 was working perfectly and I wanted to install some US maps on that I have previously purchased a few years ago. During the installation there was a power cut and it didn't complete. The TomTom was working fine, but the US maps didn't seem to install after that. So I followed these instructions to reformat my TomTom via my Mac.

Since then my TomTom has displayed a flashing red X on start up.

I've tried copying the backup files onto manually. Doing this allows it to be seen by TomTom Home, but it still displays the flashing X.

Any ideas how I can fix it.
Steps I have tried:
-Reformatting on Windows as Fat 32
-Reformatting on Windows as Fat

Reformatting it, downloading the following file and installing them:
http://download.tomtom.com/sweet/navcore/navcore_7.903.9183.go700.cab

Using ClearFlash:
https://uk.support.tomtom.com/app/answers/detail/a_id/6178/kw/clearflash/sno/1

Not sure what more I can do. All my troubles start when I reformatted the unit, so perhaps it hasn't be formatted correctly? I run "Check for Errors" in Windows (via "This PC") and it says the drive is fine.

 

[dhn]

Fat32 is what you want.

 

[smileface]

I've tried both Fat 32 and Fat but no dice.

Do I need to set a particular allocation size? (I just leave it as default). Is there a better tool to use for reformatting?

 

[dhn]

You can try this. NO promises...……..

https://files.extremeoverclocking.com/file.php?f=197

 

[smileface]

You can try this. NO promises...……..

https://files.extremeoverclocking.com/file.php?f=197

Thanks! I will give it a try.

Also, is there any way I can get a fresh copy of the TomTom files. I wonder if my back up might be the issue.

I have this one:
http://download.tomtom.com/sweet/navcore/navcore_7.903.9183.go700.cab

But as I understand it, this only replaces the lose files in my back up and not the directories

Thanks again for all your help!

 

[dhn]

When you expand the .cab file you have with WinRar, the file and folder structure will be maintained on the device.

 

[smileface]

When you expand the .cab file you have with WinRar, the file and folder structure will be maintained on the device.

So do I delete all the files that are already on the TomTom device before using the cab file?

Thanks for your continued help.

 

[dhn]

The loose files in the root of the device, yes. By 'loose', I mean those not in any folders.

BUT FIRST...…………..

Make a manual backup, not Home, of your device's contents. See here:

https://www.tomtomforums.com/thread...-to-the-computer-and-how-to-restore-it.17864/

 

[smileface]

Is there anyway I could get a cab file back up that didn’t require me to use existing back up files? I wonder if my existing back up files are the issue?
Thanks again for your help.

 

[canderson]

Just be SURE you have all of your map folder information for UK and/or full Western Europe before you do this.
The last application for the 700 was v7.903.
Too big to attach here. You can download it at this link >> http://download.tomtom.com/sweet/navcore/navcore_7.903.9183.go700.cab

 

[smileface]

Thanks! So can I wipe everything (take care to keep a back up) and then install this. Or do I need to delete only the lose files and then install this.

 

[canderson]

It is only necessary to delete the loose files in the root of the device in order to replace the firmware. Files such as system and ttsystem are the key ones in this case.
WHATEVER you do, again, be SURE you have a copy of your map folder available as a backup. That's the one thing you can't readily replace from TomTom or any other source.
Your map folder contains files such as cline.dat, cnode.dat, cname.dat and poi.dat.

Only in the event that things don't go well might we suggest further deletions.

 

[canderson]

Ah - meant to ask. By any chance do you have a map set or device backup from BEFORE you attempted that update of the maps?

 

[smileface]

I have a back up that was made by TomTom Home in Dec 2017, which was before I attempted the update.

It's interesting:

If I restore from my Dec2017 back up, I get the red X, but the device can still be read by TomTom home.

If I restore from my back up, delete the lose files and then copy the files over from the Cab file, I get the red X, but the device can not be read by TomTom home.

Here is what my Dec 2017 back up looks like:
https://ibb.co/mWSy0p

I've already deleted the loose files, but are there any other files I should delete?

 

[canderson]

OK. Watch out for Home. Any subsequent backups overwrite the previous one. Don't do that!

I would delete all loose, copy over the *.cab, then copy ONLY the original backup version of the map to the unit (you can use Home, or just copy - at a minimum - the Western Europe file and folders directly to the unit). If that doesn't work, we're in trouble.

 

[smileface]

Ah, I think it's trouble.

I've tried restoring both my Dec2017 back up and my Aug2018 back up. No dice, but it can read and updated by TomTom Home.

The moment I delete the lose files and copy over the cab, nothing works not even TomTom home.

Out of interest, when formatting, what do I select for "allocation size". At the moment, I select "default".

Thanks for all your help.

 

[canderson]

Any formatting must be done as FAT32, and allocation would be 4KB for a 2.5GB drive (which is probably what the default does).

After 13 years, this one is probably headed to the dust bin. Remember -- it's a micro hard drive, not solid state memory. Wish I had better news.

 

[smileface]

Looks like it's for the bin. Still strange that the back up makes it work with TomTom Home even though the Cab one doesn't.

Anyway, thanks for all your help.

 

[canderson]

One last thing - though I'd be surprised if it worked, given your exact symptom...
Get a version running that allows you to use Home. Delete the mapsettings.cfg files anywhere you find them in your map folders (you have at least two, Western Europe and North America, as I recall).
Disconnect, reboot the device and see what happens.

 

[smileface]

@canderson Sadly, it didn't work. But I am touched that you came up with another suggestion after I gave up, so thanks for that!