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

Hybrid View

  1. #1
    Important User Running programs from SD on nuvi
    Running programs from SD on nuviRunning programs from SD on nuvi
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Quote Originally Posted by Raupe View Post
    ............
    So with the tool I have the files :
    127.bin
    158.bin
    Just converted the hex addresses in the name of the files created by RNG tool to decimal.

    The file 14.bin could not be generated in this way. These I brought as described in post #125 with rrgn from the device to the card.
    What do you mean by it "could not be generated in this way"? RGN_Tool can extract fw_all (14.bin) from a GCD or RGN firmware file in exactly the same way as it can extract 127 & 158. Do you mean you've generated a firmware BIN file by dumping region 14 from the device using "rrgn,14,2/14bin"? If so, you'll be flashing back the exact same data for the main system software to region 14 (hex 0x0E) and if that's the case, what's the point?

    From my point of view I have now everything together

    The update.txt has this content :
    ....................
    and is located in Garmin/updater/1772/update.txt
    There is also the Ldr.bin .

    Could this work, can I have made a mistake ?
    Certainly the txt commands are correct to delete any gupdate.gcd file from .System, dump the nonvol memory to the card and rewrite data to the 3 fw regions from the card. So yes it will work provided you're using the right Ldr.bin in the HWID folder made from the correct 1772's boot.bin extracted from the appropriate firmware. However, again, what's the point? Even if the GCD in .System was corrupt, it's not being initiated anyway. If it was corrupt and initiated the device would be soft-bricked and stuck on the logo splash screen.

    Please explain precisely what you wish to achieve as i must be missing something as to your ultimate intentions. If you're simply doing this as a practice exercise for updating future firmware versions it would be far simpler (and much safer) to do higher version updates with a GUPDATE.GCD in a Garmin folder on a microSD.

  2.    Advertissements


  3. #2
    Junior Member
    Join Date
    May 2022
    Location
    Netherlands
    Posts
    6
    Rep Power
    0

    Default

    The goal was to reawaken the USB interface by replacing the firmware.
    After the hint on a possibly mechanically defective USB interface, post # 148, brought no success.
    The pictures of the USB interface in #149 . was the hope to achieve an improvement by replacing the firmware.
    Since it already has the version 8.80 is an exchange via gupdate.gcd not possible #148.
    The error with the RGN_Tool and the 14.bin is really embarrassing me.

    My goal was and is not to practice flashing firmware.
    Last edited by Boki; 14th June 2022 at 11:36 AM. Reason: approved

 

 

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
  •