So, having tried DownUnders' 9.450 NavCore on my TT One V8, I'm getting mixed results.
I wiped everything from the device except the TTgo.bif, and tried to install 8.414 and 885.4055 map.
Neither NC or map would load onto the device, the device showed the data transfer (don't disconnect) symbol for
about 10 seconds, then just the plain screen.
I formatted the device to FAT32, and tried to install the 9.450 again, still the same problem.
I formatted the device again and tried to re-install the original nc and map (7.903), but the device won't accept it.

I held the power button for 30+ seconds (there's no reset button on this device) but no joy.

Have I bricked this device?

try connecting to tomtom home..has been known to work on other units..it usually downloads navcore.
just a suggestion/

Thanks Gez, that did work! Albeit it took 8 attempts, but it finally got there. So now I got 7.5xx navcore!

In case it was a problem with extracting from zips, I copied a whole folder from an existing device I have saved on my laptop, and copied in the original TTgo.bif file. This took a couple of hours.

When I run FastActivate, I get this message for the Meta:

[color="#0000CD"]Error: Could not get file time on server. Check your internet connection.
Intergrated meta.txt enabled[/color]

The other patches all work ok.
When I start the device, I get the big red cross, suggesting there's nothing on the device.

Any ideas???

You are not done with a 7.5 NC - you have to update until Home dos no longer offer an update.
That the NC was not working might be caused by your bootloader, so knowing what is actual on your device might help.
You need at least BL 5.5012, better 5.5120 for support of the higher NC and SDHC SD cards.

If by "This took a couple of hours." you mean transfering the files from your device, than I suspect you had several long pauses during the tranfer too ?
When files can't be transfered in one go at reasonable speeds it is almost certain that you installed an incompatible bootloader.
So please please post the full details, if you can't access the BL info:
press reset, start the device and as soon as the light goes on press and hold the start button.
This will give you the infoscreen from the Linux console - Line 4 should show the bootloader version.

cieranc wrote:1. Thanks Gez, that did work! Albeit it took 8 attempts, but it finally got there. So now I got 7.5xx navcore!

2.In case it was a problem with extracting from zips, I copied a whole folder from an existing device I have saved on my laptop, and copied in the original TTgo.bif file. This took a couple of hours.

1. Current maps require navcore 7.8XX or higher.

2. This won't work!!!!!!!

now follow these 2 guys instructions..best on the net in my opinion.

OK gents, got 8.395 installed now, but it's still painfully slow transferring files.
DownUnder, yes there's some long pauses whilst transferring the files, I can load up a NC but when trying a map it usually crashes.

TTGO.BIF:
DeviceName=TomTom ONE
DeviceVersionHW=ONE (v8)
BootLoaderVersion=55130
ApplicationVersionVersionNumber=8395
ApplicationVersion=1913
CurrentMap=
CurrentMapVersion=0.0

cieranc wrote:OK gents, got 8.395 installed now, but it's still painfully slow transferring files.
DownUnder, yes there's some long pauses whilst transferring the files, I can load up a NC but when trying a map it usually crashes.

TTGO.BIF:
DeviceName=TomTom ONE
DeviceVersionHW=ONE (v8)
BootLoaderVersion=55130
ApplicationVersionVersionNumber=8395
ApplicationVersion=1913
CurrentMap= ?????
CurrentMapVersion=0.0?????

Are you aware the 8.395 is a Truck navcore??
Where is your map??

Still trying to load a map!
Yep, I'm using that NC just because it's already on my laptop. I'm currently trying to install 885 map, which should be compatible with 8.395 NC.

I'm sure the right bootloader is installed now, but it's still taking ages to load the map (1 hour so far and not halfway there yet).

Another question: When I formatted the device, would the bootloader have been wiped out, if so how come it's slow to load the new navcore if no bootloader installed?

With the navcore Home installed, it was BL 5.3030.

cieranc wrote:Still trying to load a map!
1. Yep, I'm using that NC just because it's already on my laptop. I'm currently trying to install 885 map, which should be compatible with 8.395 NC.

2. I'm sure the right bootloader is installed now, but it's still taking ages to load the map (1 hour so far and not halfway there yet).

3. Another question: When I formatted the device, would the bootloader have been wiped out, if so how come it's slow to load the new navcore if no bootloader installed?

4. With the navcore Home installed, it was BL 5.3030.

1. Which 885 map?
2. You have 55130 installed. 8.395 BL is 55120.
3. We never suggest formatting, except in the most severe case. No, a new bootloader is installed to the 32MB memory at first boot. Once installed, the bootloader file goes dormant. The updated bootloader is there until the next update.
4. OK.

Using 885.4055, I have used this with 8.395 on another device, so believe it works OK???

Now got the map on the device, but it won't activate.
Same message about server time when updating Meta.
Won't activate map.
TT Home finds the map but says it isn't activated ???

1. If you want the Truck - 8.398 is current.
2. Use the latest version of FastActivate!
3. Make sure there is a meta code posted for your map.

Hi,
So out of frustration I reloaded NC 8.010 and 880.3868 map, for no other reason than I had it all set up on another device and knew it worked.

Initially I ran FastActivate 1.8.8.0, as that what was already stored on the donor device.
I ran 1.8.8.9, as advised, and it's worked!
Taken 2 days, but now I've got the NC and map working, just need to test it now and see how it runs, before thinking about upgrades again!

Thanks all

So with the above working, deleted them and tried to re-install the 9.450 and 890.4222.
Device just won't let any data transfer at all, very, very slow.
I started the map install at 11pm on Saturday and left the computer to it, went to bed. In the morning, it was halfway through the install. By 6pm it still hadn't finished.

Could this still be related to the bootloader version, or a fault with the device?