Tomtom Acting Up? - Part 2 - How To reinstall *fresh* Software using Home - Discussion


Ad

Advertisements

canderson

Moderator
Joined
Dec 28, 2007
Messages
11,499
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
The "Comment" button at the page takes me to nowhere, although the link in your post above works.

One thing I would note...

At the end of your material, you refer to the option of backing up and using older versions of firmware, and even include a reference to a site that is a repository for old firmware. Users should be warned that it is NOT always possible to successfully re-load old firmware. In the process of loading newer firmware, changes to what is known as the 'bootloader' may also occur, and the newer 'bootloader' code is not necessarily compatible with older firmware versions. Before attempting to go backwards with code, it would be a good idea to fly the idea past the moderators here who have a better idea of which versions are compatible.
 
Joined
Feb 11, 2011
Messages
4,683
Location
London, UK.
TomTom Model(s)
Go520,720,XL Live, Start60,Go940,950,1000,1005,New500,New5000
That might well be sensible... any ideas for a paragraph text to slot in.

But out of interest, have you personally ever had any problems with incompatible bootloaders?

Before I it was pointed out that it could be an issue, I used to go back and forth between software versions a lot, and never had any problems (maybe I was just lucky!).
Since then I've kept better records of version numbers, but it's still never stopped my reverting back when I've needed to.
 
Ad

Advertisements

canderson

Moderator
Joined
Dec 28, 2007
Messages
11,499
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
But out of interest, have you personally ever had any problems with incompatible bootloaders?
Only once - moving from a major point release (7) to another major point release (8). Reloading the v7 firmware to check some things blew things up, so it wasn't possible to go backward. I was committed to v8 code at that point.

The two big concerns we have here are

1) when a user pulls down some firmware that wasn't 'officially' released for the device (e.g., 9.061 on certain units for which we never saw it appear). It can be a one-way ticket if the bootloader that accompanies that firmware isn't compatible with the previous or 'correct' firmware for the device. Rarely, Home causes this. Rarely, we actually recommend it. Sometimes, a user just gets an urge to fiddle that they can't squash.
2) when a user 'upgrades' to new firmware, find that it has dropped functions or added bugs that really foul up their particular use of the device, and would discover that they can't back up. So far, we've been pretty lucky with this since one of the only major reversions we've needed and recommended was for versions after 8.302 (e.g., 8.351) causing problems that sent people back to 8.302 ... and fortunately, there was no compatibility issue raised in that.

What needs to be carefully understood is that the bootloader contains a lot of very low level functionality related to the hardware.

Just noting that it's not always possible to go backwards, and the article implied that it was. So a user moving 'forward' needs to be aware of the differences and whether it's worth doing before making the jump - just in case it's permanent.
 

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