22nd May 2014, 08:32 PM #1
Internal hardware issue on TT Go x20,x30
[Login or Register to remove this advertisement]
I have two GO520 which the internal memory has failed..... They will work fine from sd, BUT, sometimes the old navcore/maps on the internal
seems to spring into life stopped them booting, freezing, e.t.c.
When I say failed (and these are both the same) the drive shows up on pc, but cannot be accessed, it just says 'insert disk' so unable to format even through administrator
tools on pc.
Does anyone know of a way to 'disable' the internal memory either by software (bootloader mod) or by cutting a track or pin to the internal chip?
This is a well known issue due to tomtoms cheap parts and I have trawled the web for a solution for some time....
Thanks in advance.
lurchyboy Reviewed by lurchyboy on . Internal hardware issue on TT Go x20,x30 Hi all, In the chance that there may just be someone on this forum that can help.... I have two GO520 which the internal memory has failed..... They will work fine from sd, BUT, sometimes the old navcore/maps on the internal seems to spring into life stopped them booting, freezing, e.t.c. When I say failed (and these are both the same) the drive shows up on pc, but cannot be accessed, it just says 'insert disk' so unable to format even through administrator tools on pc. Rating: 5
22nd May 2014, 10:13 PM #2GPS Contributor
HelperJoin Date : Dec 2011Location : Ages beyond mystPosts : 1,071Thanks: 321
- 515 PostsRep Power : 15Reputation : (837)
can you access the content of the drive ?
then just remove all of it , formatting is not necessary
if not , try Folder Unlocker
what you also can try is boot the device without card before connecting to PC
22nd May 2014, 10:51 PM #3Join Date : May 2014Location : UKPosts : 331Thanks: 808
- 1,693 PostsRep Power : 15Reputation : (254)
The internal drives can often be salvaged using some partition software which you may as well try as you've got nothing to lose. At the very least it'll make the files on the drive inaccessible so it'll solve your problem.
22nd May 2014, 11:14 PM #4
Can't access the content at all, is recognised as 'disk drive' but on accessing just says 'no media in drive 'x', insert media in drive 'x' and try again'
Never thought of partitioning software, or folder unlocker as it can't see the fat didn't think that would work, but thanks for the advice, I will give it a shot and report back. Thanks.
23rd May 2014, 01:40 AM #5
Tried all of the above,
TomTom will not boot to internal just flashing cross... tried about 50 times in the hope it would read the Internal but no, I suspect even if it did when I connected it and clicked 'yes' to connect to computer..... It would simply reboot, then not be able to access Internal....
Tried 4 different types of data recovery and partitioning software to no avail.... Only one of them even saw the internal on tt, and the same as windows management 'no media in drive'.
Thanks to the above 2 members as I didn't try these things and anything is worth a try.
This is what I have tried -
Soft reset - Reset button pressed
Hard reset - Reset button pressed and held 30 secs +
TT Clear flash tool - On sd card, but I believe that only clears data from current drive not TT memory
Visual inspection of circuit board
Booting on USB pwr only with battery disconnected, and only battery with no external power
Changing Navcores Inc bootloaders, even installing bootloader 0.0001 in case corrupt and many up to 5.5279 (I have never managed to brick a TT yet)
All methods from windows xp, vista, 7, Nt, 8, 8.1 and Linux (Ubuntu) to try and access internal memory.
I know a lot of us would give a lot for a TT schematic diagram data file for go520 which all the x20,30 models are based on as we know, but never found one yet, only full datasheets for the two types of lcd displays... I wish someone would clear the spambots and get ope*To*.org back up and running.
If anyone can shed light on how to disable Internal via software (bootloader?) or has any info on the secret real bios, 4kb I believe, or knows which is the internal memory chip on the board I'll cut pin 1 vcc in an attempt to disable..... Your help would be greatly appreciated...
IMPORTANT- Allthough I made reference to the BOOTLOADER file, don't mess with it, leave it alone, you may end up with a paperweight....
25th May 2014, 11:11 PM #6
UPDATE - After a lot of hard work, managed to find a Schematic diagram!
U8 is the Samsung MoviNand which is the INTERNAL on a Go520 See Pic attached, I have circled U8 and reading the schematic a tiny little device Q9 seems to power it up (arrowed in attached pic). So I intend to firstly remove Q9, thus removing power from the failed internal (hopefully) then see what happens, hopefully it will then ignore the internal memory completely... And solve this problem....
I will report back when I have some news.. Thanks again for the suggestions.
27th May 2014, 01:22 AM #7
looking at the spec of this chip it also has an embedded controller so you just might get a dead unit with a fail to boot.
27th May 2014, 03:26 AM #8
Lol Yes, I removed Q9 and unit would not do anything, just lcd backlight coming on.... then after a while tomtom logo appeared and hung, changed Q9 with another from a board with other problems and it's back as it was, no internal 'no media in drive 'x', please insert media in drive 'x' and try again'.
Back to the drawing board.....
30th May 2014, 05:01 AM #9
The movinand has either gone faulty internally or is dryjointed which is probably causing the intermittent old software to sometimes work, the problem is trying to reflow such a small object and with it being leadfree the temperature is higher than the older leaded solder and near components can also be destroyed by the heat needed, there could also be damaged tracks or "vias" on the board which are preventing proper startup, as you are aware it is extremely difficult to try and diagnose without proper schematics which as far as I am aware tt have chosen not to make these available.
31st May 2014, 01:13 AM #10
Yep, I won't be attacking this one with a heatgun! the Q9 I removed probably also is needed for the SD card to power up anyway looking at the schematic, which I see you have now, hope it's of some use to you buddy..