Switch to full style
Post a reply

8.412 Navcore on One v4 with Bootloader 1.0

Sun Apr 15, 2012 4:05 pm

Good Morning.
I have a problem with my Tomtom one v4. It's the little screen model with 1Gb of flash memory.


DeviceName=TomTom ONE
DeviceVersionHW=ONE (v8)
DeviceSerialNumber=PExxxxx
DeviceUniqueID=xxx
RamDiskVersion=20080919
BootLoaderVersion=10103
LinuxVersion=230869
ApplicationVersionVersionNumber=8041
ApplicationVersion=9645


It is actually in 8.041 navcore with the bootloader 1.0103

It work fine, but i would like to install a 8.412 or 8.414 (or higher) navcore for having IQ routes on my tomtom.

I have tested the Automatic installation of SE 8.412 navcore but it didn't work. When i Disconnect the USB cable, there is a progress bar and tomtom freeze after ...
I have tried to replace bootloader by version 5, but no changes...

Is there any chance to update the navcore on this model ?
If yes, what is the good Navcore for this One V4 tomtom who works actually with 8.041 navcore and 1.0103 BL ?


Thank for your help !!!

Sun Apr 15, 2012 4:45 pm

That is not possible. So because of the bootloader you have to stick to NC 8041.

Sun Apr 15, 2012 5:02 pm

holyhead wrote:That is not possible. So because of the bootloader you have to stick to NC 8041.


There is not any underground bootloader for install another Navcore ?

Sun Apr 15, 2012 9:02 pm

navfree wrote:There is not any underground bootloader for install another Navcore ?


If you have a Tomtom with the bootloader version number starting with 1.xxx instead of 5.xxx you have a special system and should never attempt to change your bootloader! (exception: bootloader 1.0012 is OK for updating.)
It is most likely that you have a special Navcore version as well - 8.041
Other Navcores won't work on your device the progress bar will stop at the end end the devices freezes.
The only way to use non genuine maps on these devices is by using a specially patched PNDNavigator for for the 8.041 Navcore.
Don't try to patch the ttsystem or the PNDNavigator file yourselft it won't work and the ttsystem does not need any patching.

Only the new PDA maps will work as you need at least Navcore 8.2xx for the full featured maps.

Link for the pre-patched PNDNavigator 8.041

The bootloaders 1.0100 and 1.0200 are designed for devices with a "bug" in the filesystem or the GPS hardware.
Tomtom has provided this "quick" fix to be able to sell these units (most of them being ONE V8 models) without sending them back to the headquarter in Holland.

Mon Apr 16, 2012 6:23 am

Thank you very much for this nice answer !

I have try to change bootloader many times, but I didn't have any problem. Maybe I am lucky !

I actually use non genuine maps with the 8.041 navcore, and I don't use PNDNavigator.
I just copy the maps, and run fastactivate to patch ttsytem and create a .dct files in map folder and it works.


Only the new PDA maps will work as you need at least Navcore 8.2xx for the full featured maps.


If I understand,
if I install Patched PNDNavigator with new maps, I could use IQ Routes and ALG with compatible maps for 8.2xx navcore (example : France 885.4009) ??

Mon Apr 16, 2012 7:22 am

No for IQ Routes and ALG you need at least navcore 8.2xx.
Because you can only use NC 8041 means no ALG and IQ. The latest ( so-called) new PDA maps are without Alg and IQ.
For example France 885.4058.

Mon Apr 16, 2012 7:58 am

Ok thank for this precisions.

[Help!]

Thu Jun 07, 2012 1:40 pm

tendriver wrote:If you have a Tomtom with the bootloader version number starting with 1.xxx instead of 5.xxx you have a special system and should never attempt to change your bootloader! (exception: bootloader 1.0012 is OK for updating.)

Hi there.
I've just made the big mistake, trying to force my TomTom One (30 series, bootloader 1.0103) to run a sw not supported. :doh:
I didn't do it deliberately, actually.
Now, my device freezes at any startup attempt and refuses to switch off, as well.
I've already made dozen format-restore-upgrade-copyback-and stuff... Nothing.
I'm desperately needing help to find a way out.
Thanks a lot

Thu Jun 07, 2012 2:01 pm

Not really the best way to descibe what you have done ;)
Format is not recommended by the way.
Did you only install a new NC or did you try to install a new bootloader as well?
What NC was installed before you tried to "kill" it?
What NC did you try to install?
Have you tried to delete all files from the deive and to update it using TT Home?
Have you done a hard reset followed by the TT clear flash tool?

Fri Jun 08, 2012 9:40 am

Downunder35m wrote:Not really the best way to descibe what you have done

I do apologize for my poor english.


Downunder35m wrote:Did you only install a new NC or did you try to install a new bootloader as well?

Both. I tried to install a new NC and the TomTom froze. So, in an attempt to solve the problem, I also tried a new bootloader. Now, the device is doing exactly the same thing it was doing after the very first attempt: it displays the boot logo, the yellow bar just for a moment, the night cockpit view. Then it apparently switches off, but after a few seconds repeats the sequence over and over. If I keep the switch button pressed for long, an abstract with all specifics appears; at that point I can press the button once again and it switches off. :think:


Downunder35m wrote:What NC was installed before you tried to "kill" it?

DeviceName=TomTom ONE
DeviceVersionHW=ONE (v8)
DeviceSerialNumber=PEXXXXXXX
DeviceUniqueID=XXXXX XXXXX
RamDiskVersion=20090624
BootLoaderVersion=10103 (on TomTom A1.0103 clist#323018 GCC3)
LinuxVersion=323133
ApplicationVersionVersionNumber=8042
ApplicationVersion=9647
UserLanguage=Italian
LastConnectionTime=Never
GPSFirmwareVersion= (on TomTom SIRF Atlas3)
CurrentMap=Italy
CurrentMapVersion=835.2420

Downunder35m wrote:What NC did you try to install?

I'm not sure about that, probably 9.061 or 9.030.

Downunder35m wrote:Have you tried to delete all files from the deive and to update it using TT Home?

Yes.

Downunder35m wrote:Have you done a hard reset followed by the TT clear flash tool?

I've used the clear flash tool, but I am not sure about the meaning of hard reset.

Fri Jun 08, 2012 10:38 am

Ok, if you can still acces the device in the Windows Explorer and it statrs to boot it should be fixable.
Delete everything from your device - leave the map folder if the map is genuine and not activated by yourself.
Connect to Home and klick the update button.
Home will update the correct Navcore for your TT and tell you what to do.
When finnished start the TT and check if it starts again.
If so we will go on so that in the end you can install a new map.

Fri Jun 08, 2012 12:17 pm

Excuse my butting in but this situation is why I always tell people to back up their files/folders before making any editing changes. Please look at my signature.

Fri Jun 08, 2012 12:35 pm

Downunder35m wrote:Ok, if you can still acces the device in the Windows Explorer and it statrs to boot it should be fixable.
Delete everything from your device - leave the map folder if the map is genuine and not activated by yourself.
Connect to Home and klick the update button.
Home will update the correct Navcore for your TT and tell you what to do.
When finnished start the TT and check if it starts again.

Done. Unfortunately it didn't work. The only difference is: now doesn't show the night view cockpit during the endless booting routine. :(

Fri Jun 08, 2012 12:56 pm

chas521 wrote:Excuse my butting in but this situation is why I always tell people to back up their files/folders before making any editing changes. Please look at my signature.


I agree 100%, but with this issue, a back up file is of no help.

Fri Jun 08, 2012 1:04 pm

Ok, please a bit more detailed.
What do you mean "night view cockpit"?
Do you mean you see only the bootscreen after the TT logo or do you see the actual menu on the device?
I guess during those reboots no ttgo.bif is being created?
If so, please do that:
Press the reset button,
turn the device on and as soon as you see the screen light going on press and hold the power button - a DOS like status window will show up,
Line 4 schows the installed bootloader, post that please.
Post a reply