Hier de links naar het engelstalige tomtom forum, met oplossingsgerichte adviezen.
https://discussions.tomtom.com/en/discu ... nt_1640174
https://discussions.tomtom.com/en/discu ... ing#latest
op pagina 7:
https://discussions.tomtom.com/en/discu ... booting/p7
Ok, so the great news is that my bricked GoLive 1005 camper is now fixed.
First of all, many thanks to the following users: 5150user; Johnst; Harleydee. To 5150user thanks for pointing me at the Johnst post, and for including an extract of it.
It is fixable but you need to use you computer and the TOMTOM software MY DRIVE CONNECT to change the map from the FULL map to a SMALLER “ZONE” map
Towards the end of page 1 of thread below and continued onto page 2:-
https://discussions.tomtom.com/en/discu ... booting/p1
The key bit is here and posted by johnst:-
I will tell you how I have succeeded:
- hold the start button until drum sound is heard.
- wait 10 to 20 seconds
- press the start button again to switch off
- briefly press the start button again
repeat until the device starts normally
We tried the above multiple times and timing as they say is everything. Got the drumroll; released the button; randomly tried 10 – 30 second delays before the switch off. Length of time on the switch off is also critical. We held the button too long and got to the command line reset as well inadvertently. Bottom line, each time it still hung at the welcome screen.
We also followed instructions by Harleydee which suggests tapping the screen immediately (and I mean IMMEDIATELY) after the power on. We tried a few times as above and it didn’t seem to make any difference. We then got quite aggressive and did some machine gun tapping of the screen immediately after the power on (gently but frequent taps). And this did appear to work and the device started up with the map displayed
Whether this (the tapping) was exclusively the solution I don’t know. Maybe it was a combination of things… but for me the finger tapping worked.
I already had my Mac booted up and Caffeine started (probably not familiar to Windows users – this prevents it from sleeping). MyDrive/Connect was up and running and we were already plugged into the USB.
MyDriveConnect immediately recognised thedevice and gave me the option of updating maps. Connection to MyDriveConnect only works if the TomTom has started normally.
I decided to follow generic advice and NOT install the whole map. Used this article:
http://uk.support.tomtom.com/app/answer ... e-connect)
to download and install EuropeZone1. This is only a couple of Gb in size. Took about 30 mins to download, and 30 minutes to upload to the device.
I was somewhat nervous the entire time the map was downloading and uploading to the device. Basically I didn’t touch anything, either the TomTom or the Mac the entire time.
Curiously, my South Africa map which was also on the device was still there.
Once the upload has completed, I had the option of selecting either of the SA or EuropeZone1 map. To be honest, I decided not to push my luck and just selected Zone1 without trying the SA map.
It appears to no longer be an expensive paper weight. But have not yet been out for a drive to test it. Will report back if there are any issues
I have been suffering the dreaded 'stuck on welcome screen' problem. Rebuilding after a drumroll reset and holding until the text screen appears followed by three quick button pushes etc has proved to be useless for restoring normal operation.
After days of fiddling I have succeeded in restoring apparently normal operation three times. My most succesful method for reconnecting the machine to my computer is to do a normal on/off restart and then when the welcome screen appears, rapidly press the on/off button 3 times, then pause, then 4 times, then pause and finally 5 times and wait. The waiting is the hardest part. When a readable screen is obtained, usually the machine connects to the computer and updates a but and then restarts after a minute or two bringing up the welcome screen problem again. So I try this process again and again until I get to normal operation and proper responses to menu option.!
My machine is now fully updated. All is well when I am at home but soon after beginning a drive, the machine emits a few beeps and then crashes and refuses to restore, even after a drumroll reset. I have contacted TomTom but they were no help really; just offered me a discount on a new device or their smartphone app. I think it probably is a 'stack overflow' issue as described earlier by someone else who knows more about the problem than me.
There is nothing wrong with the 1005 hardware. In my opinion TomTom recent software updates have killed my machine after just 5 years. TomTom's website says that the life of a machine is limited by them; when they decide not to support it any more it is 'life extinct' (my words not theirs). I paid over £300 for my motorhome version and its now useless; that is £60 per year on top of the cost of the traffic services and it leaves me now with several months of unusable traffic and speed camera updates I don't suppose I will get a refund of this money despite it being TomTom's fault that my machine is now inoperable.
I would prefer TomTom to either fix the current software OR allow affected owners to revert to the previous versions of map and Navcore software so that we have a usable if not updateable device. This Dutch company does not seem to understand that people are unlikely to pay more money for TomTom products when they have treated existing customers so shabbily.
My family now has 3 unsupported TomTom devices! I will not be purchasing a fourth.