GO 6200 endlessly rebooting itself after failure during update attempt.

[willnz]

My GO 6200 advised me of updates available. I connected it and selected the updates and hit update. It connected and started downloading the updates. It then suddenly displayed a screen saying there was a disconnect. The device then rebooted itself and told me not to switch it off as it was performing a restore. I left it going and eventually got to 100% after maybe 5 minutes. It the rebboted itself again and eventually displayed the map of my home. This stayed on for 5-10 seconds then the device rebooted itself again. It now reboots in an endless loop, cant seem to stop it. It doesnt stay active for long enough to attemp to do a system reset. I have tried several times but it reboots before I can activate the reset button. Any ideas as to what I can do or has it bricked itself?
William

 

[Willy875]

To try:
Press the on/off button until you hear the sound of the drum and the device restarts.
This may take at least 30 seconds.

To try: https://help.tomtom.com/hc/en-gb/articles/360013959579-Mon-GPS-ne-démarre-pas-ou-une-croix-s-affiche

 

[willnz]

Thanks for your reply.
I have tried the link you posted. Device does as described, had to go to step 6 as no spinning wheel displayed. It then connects to MY Drive and says not to disconnect as it is restoring device (have gone through this restore thing before many times with no success). Waited for it to get to 100%, device then reboots itself and goes back to a different endless reboot sequence as follows.. (drum roll, TOMTOM logo, then a screen saying "no map available, you need to add at least one map before you can use your device". I hit the "load map" button but device then reboots back to drum roll etc before any map is offered and loops again.

 

[Radaway]

I am not sure whether this will help you at all, but I vaguely remember , once I too had an issue where : no map available, was the joy-word

I logged the issue back then :https://discussions.tomtom.com/en/discussion/1147928/map-is-gone/p1?new=1

but that site is now obsolete ...maybe if you search something like the last parts of the link: like 'discussion/1147928/map-is-gone' or something ...some hits may come up

but what I did at that time was something like:

1) I deleted 'iraq' (from 'mijn kaarten'(Dutch for my maps) , the big Image icons for each country{on PC my drive connect} ]
2) i had to : 'turn off' device---> start again (device)
3) viola....all was back on Line
3) & I had to re-installed 'Iraq' on 'system' ...this happens in a Jiffy , as this is < 25 megs. this was 'mandatory' because of some rigid reason ( as per the admin(or a Super-Guru) that time ( a Super-Guru called: " Willy875" --during my call logging session)

why 'iraq' , it's the 'smallest' map available that will not usurp valuable cache or sd card space. ..basically It could be anything(any other country)

as I said, I am sorry I can not specifically help you, but loosing all maps & getting a 'blank' was somewhere on these lines.
I shall check my previous records and see if I can come back with anything substantial here.

Good Luck !...i know it can be frustrating ...

HTH

*Post edit: ha ha ..I see u r already in touch with The 'Super-Guru'.....u r in Good hands !

 

[Willy875]

GO 6200 is updated via wi-fi
if you connect the GO 6200 to Mydrive connect it can create confusion in the updates.

So the solution if you update via Mydrive connect is to disconnect the Wi-Fi from your computer.

 

[willnz]

Ok, have had a session with tomtom help. Essentially they asked me to follow the link Willy875 gave me above using MyDrive. No mention of disabling wifi..
The help did not change anything. Still looping endlessly. They then said it is bricked and they would refund me if I could prove it is still under guarantee, which I cant.. alternatively send it in for repair at a cost in euros which is probably more than it cost originally. Which suggests it is NOT bricked...?
This really irks me as I am certain that the fault lies in MyDrive software. Reason is that I had a similar issue with my other 6200 when updating using MyDrive. The 6200 lost all its maps but didnt corrupt as badly as this one did, I was still able to access the system menu and eventually, doing a reset, it restored itself and reloaded the maps and is still working. I have also seen that I am not the only one with this problem, there are several others out there with the same issue, seemingly caused by failed update. So, either the update software is glitchy/faulty/not suitable for the 6200 or the 6200 has an inherent design fault in it, or both... with "service" like this, I will certainly not be looking for future GPS replacements from tomtom...
BTW, I also have a go600 and 2 go6000 units which are in reserve as I prefer having live traffic available which these units do not really provide unless connected via mobile phone.

 

[canderson]

alternatively send it in for repair at a cost in euros which is probably more than it cost originally. Which suggests it is NOT bricked...?

Can't address the root issue, but can provide an explanation for this bit. "Bricked" is a function of the tools available to the one trying to do the repair.

If the firmware goes completely south on one of these devices, TomTom has the ability, should they choose to do so, to reflash the entire device using current firmware, bootloader and all. That's not something that can be done at home.

 

[Radaway]

Gee..whiz..I never knew- this is what "bricked" also meant or really means or is meant to be ...profound knowledge for me, as in my vocab. it meant: 'F#$%^d due to software or firmware corruption'.
I had to read the above definition umpteen amount of times to fathom what it actually is trying to say ...Lies on me ofcourse

 

[canderson]

Gee..whiz..I never knew- this is what "bricked" also meant or really means or is meant to be ...profound knowledge for me, as in my vocab. it meant: 'F#$%^d due to software or firmware corruption'.
I had to read the above definition umpteen amount of times to fathom what it actually is trying to say ...Lies on me ofcourse

Yes, well - there's

'bricked' = beyond any chance that the user has the necessary tools to recover the device, and
'bricked' = above, but the manufacturer has hardware and software tools capable of recovering it (a 'reflash'), and
'bricked' = there aren't any tools on this planet that could put the poor thing back to rights again

From the end user perspective, once you've hit the first one, it's either a door stop (some people use a 'brick') or needs a repair trip.