I already made a backup to restore the gps to it's present state. What I'm asking is if I'll be able to restore the gps using the backup if I update the gps from navcore v9.510 to navcore v.9.541. In other words does the backup also restore the gps to it's previous navcore version?If you don't have enough space on your GPS.
You do not have to have the 3 maps of the United States, Mexico and Canada installed on your GPS.
You do not keep the map of the United States on your GPS and you delete the map of Mexico and Canada.
if you go to Mexico you delete United States to install the map of Mexico.
If you install an old Navcore, the map 11.25 risks no longer working
No, the firmware isn't keyed to the serial number of the device. As long as the firmware was built for the exact same model of device, it can be installed.I already made a backup to restore the gps to it's present state. What I'm asking is if I'll be able to restore the gps using the backup if I update the gps from navcore v9.510 to navcore v.9.541. In other words does the backup also restore the gps to it's previous navcore version?
i did a copy and paste of all the files and folders of the gps and put them into a folder on a thumbdrive. I also did a backup using tomtom home and copied the application, map and voices using tomtom home to my hard drive. the application, map and voices are in zip files along with toc files in folder tomtom home preferences>Copy to computer>Just remember that Home overwrites a previous backup, which is why we prefer to do it manually using the operating system's copy function with hidden files visible.
That's for your 930, though. Can't be 100% positive the XXL build will look like yours -- though that is a good sign.@canderson
I have the 42MB 9.541.1-2042-CAB-navcore-GO.cab in my930 folder.
I could not find a sys file in there and have no cloud based service to eMail the 42 MB to you.
Unless both devices were running the same level firmware as delivered by TomTom (and hence, the same bootloader), there's always the chance of the same problem I've already described, and I don't have enough context from your question to answer it.Can I use the the backup from one XXL550TM and install it into another?
I'm experimenting with this thing but don't want to turn it into brick. It's obsolete. Sort of like a slide rule. I haven't used in years.From any downloaded or 'moved from device' item, you can selectively restore items using Home.
If you use Backup from Home, you restore the whole kit and kaboodle or none.
That said, you can go to the 'backup' folder that Home creates and pick and choose any items you want to manually copy back to the device.
As for reversion to the old build, I've already noted that I can't predict this. Only someone who still has access to the 9.541 update package (*.cab file) for your model can inspect it to see if it contains a new 'system' file that might make trying to reload the 9.510 'ttsystem' code an impossibility due to compatibility issues. Read post #8 carefully. It may be possible to back up, or not. I no longer have access to the full package files, and the old 'format' for direct download doesn't seem to work with 9.541.
Good grief - the thing is years old. Try it and see how it works out!
So if the firmware is delivered by tomtom and installed using tomtom home the new firmware for the device will work because the bootloader code will match. And if you try to install firmware that was provided by tomtom for the same model but a different device it may or may not work as the bootloader code may be different.Unless both devices were running the same level firmware as delivered by TomTom (and hence, the same bootloader), there's always the chance of the same problem I've already described, and I don't have enough context from your question to answer it.
I'll just make up some numbers for three hypothetical 'releases' from TomTom:
Device A = system version 20, ttsystem (firmware) version 400.
Device A = no new system code, ttsystem (firmware) version 405.
Device C = system version 21, ttsystem (firmware) version 410.
Note that not EVERY new firmware release came with new bootloader code (ala the second line, above).
Loading 410 firmware backed up from Device C onto device A or B may create issues.
Loading 400 firmware backed up from Device A or B onto device C may create issues.
It would be safe to copy the 405 firmware to Device A, and safe to copy the 400 firmware to Device B. Same underlying system / bootloader code.
It's not at all uncommon for it to be necessary to match the system / bootloader code to firmware. And the bootloader code can't be copied back and forth, upgraded or downgraded manually, etc. Once it's on the device, it's in an area of memory you cannot see or touch. Any firmware loaded after that either better work with the existing installed bootloader or some with new, matching bootloader code!
The damaged one is DAMXAGED as in not working and has an earlier bootloader. From what your saying non of the firmware versions I have backed up from the damaged gps will work on the working gps. From what I learned here non of the maps backed up from the damaged gps will work either because they're keyed against the serial #.Yes, that's what I'm talking about, though it appears it may have worked in your favor. You can safely install the newer bootloader/firmware package that you received for your 'Working' XXL550 onto your 'Damaged' XXL550, since the bootloader will be upgraded concurrent with the device firmware.
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.