Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 43

Hybrid View

  1. #1
    Garmin/GPS Systems GMod. Nuvi 265WT bricked
    Nuvi 265WT brickedNuvi 265WT brickedNuvi 265WT brickedNuvi 265WT brickedNuvi 265WT brickedNuvi 265WT brickedNuvi 265WT bricked
    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    6,707
    Rep Power
    2567

    Default

    A most pleasing albeit unexpected result. Well done kunix for the insight, and pgardella for following his advices so trustingly and precisely. Another trick worth trying before 'end-game'....

    In summary kunix, is this understanding correct?: His unit couldn't flash fw_all.bin using the boot.bin in full firmware, but following successfully flashing boot.bin solely a copy of bootloader was properly retained, which in turn was found to flash fw_all.bin alone.

    Thread marked as Solved. WOW indeed.
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

  2.    Advertissements


  3. #2
    Navigation software Moderator kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    908
    Rep Power
    440

    Default

    Quote Originally Posted by Neil View Post
    In summary kunix, is this understanding correct?: His unit couldn't flash fw_all.bin using the boot.bin in full firmware, but following successfully flashing boot.bin solely a copy of bootloader was properly retained, which in turn was found to flash fw_all.bin alone.
    I think bootloader was correct all the time and the issue was caused by the difference in flash writing algorithms in boot.bin (ramloader) and bootloader. And somewhat degraded flash chip, of course.
    So, boot.bin's flash writing algo was failing somewhere.
    But bootloader's algo did the job.

 

 

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
  •