XL Black edition internal disc corrupted


Joined
Apr 16, 2013
Messages
3
Location
United Kingdom
TomTom Model(s)
One XL Black
My XL Black has died during a map update and I need to replace the internal disc / memory but can find no relevant diagrams anywhere and am hoping someone here can help.
The unit refuses to format, and a memory scan shows bad sectors that can't be recovered. I've found pictures adding a micro HCSD to increase memory size, but not for my model. The PCB is labelled PCB Rev v3.1.
I can't get the application software to complete it's download or a map, so the unit is at the moment simply a paper weight :(
Any assistance will be very much appreciated.
 
Ad

Advertisements

Joined
Apr 16, 2013
Messages
3
Location
United Kingdom
TomTom Model(s)
One XL Black
Many thanks for the reply, dhn.
Tried the DOS command and it looked like it had worked;-
C:\Users\Me>chkdsk f: /f
The type of the file system is FAT32.
Volume Serial Number is 7A1D-0C17
Windows is verifying files and folders...
The \PNDNavigator entry contains a nonvalid link.
The size of the \PNDNavigator entry is not valid.
The size of the \helpme\flags\Switzerland.gif entry is not valid.
\helpme\flags\Switzerland.gif is cross-linked on allocation unit 4480.
Cross link resolved by copying.
File and folder verification is complete.
Windows has made corrections to the file system.

2,049,740,800 bytes total disk space.
24,576 bytes in 6 folders.
31,227,904 bytes in 56 files.
2,018,484,224 bytes available on disk.

4,096 bytes in each allocation unit.
500,425 total allocation units on disk.
492,794 allocation units available on disk.

C:\Users\Me>
C:\Users\Me>chkdsk f: /f
The type of the file system is FAT32.
Volume Serial Number is 7A1D-0C17
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.

2,049,740,800 bytes total disk space.
24,576 bytes in 6 folders.
31,227,904 bytes in 56 files.
2,018,484,224 bytes available on disk.

4,096 bytes in each allocation unit.
500,425 total allocation units on disk.
492,794 allocation units available on disk.

But when trying to install the application or just the map, both bum out at around "Taiwan.gif". Not sure why I'm getting Taiwan on a Europe map, but hey ho. Look like I'll have to keep looking for a diagram of the PCB to see if I can add new memory. :(
 
Joined
Feb 11, 2011
Messages
4,683
Location
London, UK.
TomTom Model(s)
Go520,720,XL Live, Start60,Go940,950,1000,1005,New500,New5000
But when trying to install the application or just the map, both bum out at around "Taiwan.gif".
Is this when trying to restore a backup, or when reinstalling a FRESH version of software?
If it is from a backup, just delete the Taiwan.gif file and try again. It certainly doesn't sound like a vital file.

Look like I'll have to keep looking for a diagram of the PCB to see if I can add new memory. :(
Good luck with that, I've been playing with tomTom's for several years now and only once have I ever (very briefly!) seen a circuit diagram for any model posted on-line.
 
Joined
Apr 16, 2013
Messages
3
Location
United Kingdom
TomTom Model(s)
One XL Black
It's when trying both, the back-up and fresh install. Even though it looks like the bad sectors on the disc are repaired, it seems there is still an issue. I've found a photo of how to do it, but not my PCB version.
Looks like I'll just have to keep looking.
 
Joined
Feb 11, 2011
Messages
4,683
Location
London, UK.
TomTom Model(s)
Go520,720,XL Live, Start60,Go940,950,1000,1005,New500,New5000
Can you successfully write any other files to the internal mem? Something like a bunch of big audio files?
 
Ad

Advertisements

canderson

Moderator
Joined
Dec 28, 2007
Messages
11,659
Location
Colorado, USA
TomTom Model(s)
GO720, GO740TM Live, GO 1535 Live, Via 1535, Via 1605, GO 52, GO 600, GO 620, GO 630, TomTom Bridge
Swapping flash on this device is an unworkable solution. At least the boot block of flash must remain intact as delivered from the factory. Swapping a new chip of flash in would make the device completely unbootable. This block is NOT seen by the user, and is not seen by the operating system as part of the file system. There is no way to reinstall a boot system into fresh flash since one does not already exist there to perform the appropriate magic on any 'system' file that might be present.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top