Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 7 of 7
  1. #1
    Junior Member
    Join Date
    Jan 2016
    Location
    Reading
    Posts
    5
    Rep Power
    0

    Default Is there something odd about Bootloader 5.050?

    I'm having troubles updating a fresh (from eBay) TomTom One V1. This was bought to replace my old ONE V1 that recently died - bought another ONE V1 as it was cheap, I'm familiar with it, and while waiting for a newer one to come up.

    Anyway, I am using Navcore 9.170SE for 32MB devices, exactly the same as I was on my old TT. I did download it a new map (960 UK and ROI) but also cracked one of my old maps, Western Europe 937. Fastactivate said dct ok for both maps. I put them on a new SD card with the Navcore and . . . The TOM TOM booted but repeatedly says my maps don't work on this device. The maps have the right dct files - all as I have done many times before on the old TT.
    Now this new TT has Bootloader 5.05. Puzzlingly my 9.170SE Navcore has that looks like a much newer Bootloader - 5.4201. But, when I look at my ttgo.bif file, it says Bootloader is still 5.050. What is stopping it updating? On my old TT the Bootloader uploaded with each Navcore I used. (I know now that Bootloader is not important as all it does is, well, load to enable booting. Well it does boot, so no problems there. I'm only concerned if the 5.050 Bootloader is somehow making my maps look incompatible.
    Any ideas on what I can try next. Does anyone know anything odd about Bootloader 5.050? I have already tried another couple of maps I have, each time Fastactivate says I get good dct file, but each time my TT says not compatible. Puzzled? I've run out of things to try.

    Thanks for a great forum. I hope someone cn shed some light on this. Or maybe I just look out for an XXL or whatever. I actually like the ONE V1 and it does fit the carholders I have in 2 cars, so it would be nice to get it going.

  2.    Advertissements


  3. #2
    TomTom Expert

    biggerdave's Avatar
    Join Date
    Dec 2011
    Location
    Darn sarf
    Posts
    1,775
    Rep Power
    508

    Default

    Remember this new device needs a newer bootloader installed BEFORE it can read SDHC cards see [Only registered and activated users can see links. ]

    Another thought/suggestion. Did you just copy all the old stuff from your old card (plus a new map) to the new card & then run FastActivate (using a card reader) BEFORE inserting the card in you device & rebooting which is when you would get the required new ttgo.bif for activation? If so then it would have created dct's for the old device/ttgo.bif
    Last edited by biggerdave; 8th February 2016 at 10:05.
    Please do not post "thanks" but use the "reputation" star(*) bottom/left or "like" bottom/left buttons
    S i m p l e s

    PS If you find any dead links on MY posts please pm me & I'll try to fix/reload

  4. #3
    Junior Member
    Join Date
    Jan 2016
    Location
    Reading
    Posts
    5
    Rep Power
    0

    Default

    I am only using a 2GB SD card, so should not need to change the Bootloader for that reason - only if the SE Navcore needs it, which I don't think (but am not sure) is the case.

    I created the dct by putting the maps on an SD card, then deleted the old dct for the maps that had one. I also copied the ttgo.bif from the SD card that came with the "new" TomTom onto my SD card. Then I used a card reader in the PC to do the patching. I don't see that the dcts could be wrong, but, just to make sure, I intend today to re-do the patching using the ttgo.bif that has been created on the new SD card. I suppose the fact that a ttgo.bif has been created proves that my SE Navcore is up and running OK.

    I'm also a bit puzzled because the ttgo.bif from the SD card that came with the "new" TomTom contains a line user password=xxxxxxxx (not actual xxs but the password itself). Could this line be messing something up I wonder? I don't need to enter a password when I use the SD card that came

  5. #4
    TomTom Expert

    biggerdave's Avatar
    Join Date
    Dec 2011
    Location
    Darn sarf
    Posts
    1,775
    Rep Power
    508

    Default

    Sounds like you have done everything right then. Created a new ttgo.bif (or at least are using the one for this new device) & running F/A to get new dct's

    Couple of suggestions, maybe try copying F/A.exe and the ttgo.bif into each map folder & running options 1/2/3 again from inside the map folder(s) This would automatically replace/overwrite any older dct's
    The "password" shows that this has been registered in TTHome (not password protected input) so you may struggle to access/update this through TTHome without the username & password from previous owner

    PS the only time a new/updated bootloader would be needed is if/as/when you try to run an SDHC card in an older, pre-x20 device, no other time.
    Last edited by biggerdave; 8th February 2016 at 10:41.
    Please do not post "thanks" but use the "reputation" star(*) bottom/left or "like" bottom/left buttons
    S i m p l e s

    PS If you find any dead links on MY posts please pm me & I'll try to fix/reload

  6. #5
    Junior Member
    Join Date
    Jan 2016
    Location
    Reading
    Posts
    5
    Rep Power
    0

    Default

    Many thanks for the good pointers. I re-did everything from scratch again, with even a different SD card. I also deleted the dcts and did as you said putting the ttgo.bif and F/A inside the map folder. I also put "cleanflash" in the setconfig file of the Navcore when I first ran the TT with the maps for the first time (even though I had run cleanflash originally as well.
    It worked - though which bit was important and did the trick I don't know. Maybe my experience might help someone - if it doesn't work re-do it all again and take extra care.
    Replacement TT is now working just the same as the old one did.

    As for the bootloader, it is unchanged and working just fine. I had updated it on my old TT but it was not necessary. One day I might move to a bigger SD card and then need to update the bootloader for that reason, but for now I just make sure my maps are under 2GB and with this TT only running from SD (it has no internal memory for maps) it is easy to have different maps on different SD cards.

  7. #6
    TomTom Expert

    biggerdave's Avatar
    Join Date
    Dec 2011
    Location
    Darn sarf
    Posts
    1,775
    Rep Power
    508

    Default

    Told it was was SIMPLES didn't I? Now do a full Windows backup & away you go (remembering the next 965 map release is imminent this month)
    Please do not post "thanks" but use the "reputation" star(*) bottom/left or "like" bottom/left buttons
    S i m p l e s

    PS If you find any dead links on MY posts please pm me & I'll try to fix/reload

  8. #7
    Master
    Join Date
    Apr 2014
    Location
    Germany
    Posts
    311
    Rep Power
    69

    Default

    Quote Originally Posted by wildsparrow View Post
    ...I also deleted the dcts
    I think that was the solution. The previous dct-files were for the old Tomtom. Sometimes F/A don't create/overwrite the old ones, better is deleting these before a new map-activating.
    Last edited by Alfred_ML; 22nd February 2016 at 07:46.
    Please, no reply with full-quote, not even for stupid people, who have already forgotten the previous post.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.