GO Pro 6200 - Not starting - Not resetting/rebooting or recovering - white line Only goes 20mm only

[Landsicksailor]

Hi, going mad as was using this everyday and was great and easy to use.

On last trip noticed it wasnt charging as red battery light came on, despite being plugged in and unit started to cucyle through power ups. so i turned it off.
It has never worked again.
Now charged to 100%.
Ran reset - no good.
Ran recovery/restore from screen with red cross ( as only screen unit shows after trying to start up).
Unit starts restoring (as per mydrive connect), completes restoring.
Then unit resets, and white line moves all the way across. - all as per TomTom instructions.
Then reboots, TOMTOM logo screen and white line starts but only gets around 1/5 way across (20mm) and freezes.
Then Unit reboots and back to red cross screen with connect advicing of a comm error. (used diferent PCS with diffrent OSs and 2 original TomTom cables and other data ones, also used USB 2 and 3 _ even tried outside on a laptop! - nothing worked)

I do note that on the B&W systems page - (like old DOS system details accessed while trying other route to restore page where keep power button on to acees then you press 3 times quickly) that:
Hardware names is prato_6in
OS version: 3.10.49-g4188716-00860-g9d0c75d
but the real time clock is showing Thu Jan8 1970

Are their tools where one can flash the OS system from scratch or any ideas how to fix?
Happy to disasseble, solder and Jtag or whatever as currently it isnt even pretty to look at?

On searching I am not the only person who has been stuck in this loop on what is meant to be a 'sinking' flagship model!

Any ideas at all and if we solve it we need to let others know.

 

[canderson]

Your OS as reported on the diag page is up to date. That is the current release level. So the attempt to recover has either left the device in its prior state, or there was a least a somewhat successful reload.

Yes, your RTC is whacked. That date is the representation of a UNIX time stamp of all zeros. So we know that whatever is happening, you aren't getting any GPS information that would provide a current date/time. Given that your device has been unable to boot in order to see a satellite, that value makes sense. So no worries there apart from inability to boot.

It seems you have gone through the 'normal' recovery steps. What's troubling is that after the restore, you're not getting through a full boot, seeming to indicate that the restore process was unsuccessful (bad code load). I assume you were using the procedures out lined here >> https://uk.support.tomtom.com/app/answers/detail/a_id/1898 ??

While there may be tools at TomTom for a complete reflash (and I have good reason to believe that there are), AFAIK, they have never left their offices in Amsterdam.

How long have you had the unit? I am wondering if by chance it is still under warranty.

 

[Landsicksailor]

Your OS as reported on the diag page is up to date. That is the current release level. So the attempt to recover has either left the device in its prior state, or there was a least a somewhat successful reload.

Yes, your RTC is whacked. That date is the representation of a UNIX time stamp of all zeros. So we know that whatever is happening, you aren't getting any GPS information that would provide a current date/time. Given that your device has been unable to boot in order to see a satellite, that value makes sense. So no worries there apart from inability to boot.

It seems you have gone through the 'normal' recovery steps. What's troubling is that after the restore, you're not getting through a full boot, seeming to indicate that the restore process was unsuccessful (bad code load). I assume you were using the procedures out lined here >> https://uk.support.tomtom.com/app/answers/detail/a_id/1898 ??

While there may be tools at TomTom for a complete reflash (and I have good reason to believe that there are), AFAIK, they have never left their offices in Amsterdam.

How long have you had the unit? I am wondering if by chance it is still under warranty.

Had it nearly 2 years, March 2018, and have now opened it to see if GPS aerial or other issues.

Clock means it has been running for 8 days since it happened and if it only uses GPS time to set, rather than correct I will take it on my next trip and see what happens, regarding changing mobile operators and gps reception

 

[Landsicksailor]

Had it nearly 2 years, March 2018, and have now opened it to see if GPS aerial or other issues.

Clock means it has been running for 8 days since it happened and if it only uses GPS time to set, rather than correct I will take it on my next trip and see what happens, regarding changing mobile operators and gps reception

and thank you...

 

[Landsicksailor]

Another few hours later..... Stood out in garden and reset tomtom, moved to somewhere with better mobile phone reception - in case internal sim is used for startup. - nothing worked except my anger!
Still only 20mm of white line on startup. When recovering line goes the whole way then resets and stops at 20mm.
I cant go from the B/W bios page to Cog or similiar and then the PC and tomtom with a red cross. It goes to a tomtom sign then red cross. Which i saw somewhere is normal for this model as stuck in restore mode.
And i have had other tomtom and got the cog up - so know how, but despite hours of trying mine just goes after startup from normal TOMTOM with world and upto white line of 20mm to TomTom logo then red cross. Same as going from B/W screen.

Any ideas? Can i use a boostarp via the sd card or a starup/diag? I dont have a card inserted by the way.

I did like the unit as I really miss it - it was, once, my best so far.

 

[canderson]

Sorry if I led you astray earlier Until the device is capable of booting, you won't get a proper clock time. Was only noting what the diag screen clock was indicating was Unix 0 without any GPS correction.

Am hoping dhn has seen something that might prove useful. You've done all I know to do.
David -- you around?

 

[dhn]

I am but I would only suggest the Recovery mode which the OP already tried, apparently.

Support maybe:

United Kingdom
02079 490 134
Monday - Friday: 9:00 a.m. to 5:30 p.m.

 

[apoppitt]

Need to buy a replacement Lithuim Iron battery. This fixes the fault. Search for online instructions and battery replacement.