Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Likes Likes:  0
Results 1 to 4 of 4
  1. #1
    Junior Member
    Join Date
    Jun 2011
    Age
    36
    Posts
    9
    Rep Power
    0

    Default

    Hello all,
    I was given a Dakota 10, which has been said that after firmware upgrade with basecamp lost ability to fix gps (I have seen more complaints like this .
    I already tried reset, downgrading firmware (till 4.1, but gps chipset version is still 5.0) and nothing.
    Both RGN and CDG flashing won't go below 4.1/4.04, they get sutck on loader.
    When outside , during clear sky , the satellites are grey and don’t get a fix.
    Any hints ?

    =========

    here is what I've done (my workflow)
    Downloaded a bunch of RGNs,GCDs, exes from different sources:
    Perry's site (using [Only registered and activated users can see links. ])
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ], together with webarchieve for the [Only registered and activated users can see links. ]

    Went downgrading firmwares from 5.80, till 4.1 via GCD files. All seamless.
    Although, in the "about" section, the gps software is still 5.0...and it doesn't get a fix.

    Under 4.1 , I tried beta 4.04 (using webupdater.exe), all good, version under it don't flash. Stuck on Loader Loading.

    Decided to try RGN Flashing a go.
    Open RGNTool 0.94, and opened the various RGNs I downloaded. Out of it, only the ones in "recovery packages" like this [Only registered and activated users can see links. ]"]one [/URL]worked, all others said "this is not a valid GCD file" . If I convert a GCD to RGN, RGN tool opens it fine.

    Decide to try to use RGN tool to flash RGN under 4.0, no go, stuck on Loader loading, and updater.exe

    Downloaded [Only registered and activated users can see links. ] to retriev HWID.

    First thing I noticed, it says software version 5.2, while it is running firmware 4.1

    I've tried all this both in windows 7 64bit and windows XP 32bit. Different Cables.
    Reading [Only registered and activated users can see links. ], makes me think it may have similar issue, and could be software, also more [Only registered and activated users can see links. ]had the same issue after update.

    So I guess something is not ok, and that I am missing something. Screenshots and garmindevice.xml of each firmware [Only registered and activated users can see links. ]

    EDIT: Different approach I have tried combining fw_all.bin from ancient firmware in 5.8 firmware, and flash it with RGN. No go, device boots and locks on garmin screen. (I was able to flash 5.8 original rgn all it came to life again, except it still doesn't pick signals).
    Last edited by skinniezinho; 18th September 2022 at 07:16 PM.

  2.    Advertissements


  3. #2
    Member
    Join Date
    Jan 2019
    Location
    Russia
    Posts
    24
    Rep Power
    36

    Default

    Try leaving the device turned on for a few hours outdoors.

    If it does not help, then try downloading the almanac from another working device and uploading this almanac to Dakota.
    This can be done using the program g7towin.

    From another device:
    1) GPS->Download from GPS->Almanac

    To problem device:
    1) File->Open { Almanac Files(Garmin Only)(*.alm) }
    2) GPS->Upload to GPS->Almanac

    PS:
    What is the current time on your Dakota? If it's wrong, try to fix it first.
    g7towin: GPS->Commands->Get Time (UTC)

  4. #3
    Junior Member
    Join Date
    Jun 2011
    Age
    36
    Posts
    9
    Rep Power
    0

    Default

    Thanks for the help
    I already left the device overnight, didn't change anything.
    Regarding the almanac, very good idea, but I just have a Forerunner 945 LTE and don't arrive to g7towin to read it. If someone has an almanac to share, it would please me.

    The time is not correct, and it doesn't change when I sync with garmin express.
    On g7towin, when I do g7towin: GPS->Commands->Get Time (UTC) it says: USB Error: waitcomplete: error waiting for overlapped I/O
    Last edited by Boki; 19th September 2022 at 07:03 AM. Reason: removed excessive quote, approved

  5. #4
    Member
    Join Date
    Jan 2019
    Location
    Russia
    Posts
    24
    Rep Power
    36

    Default

    Quote Originally Posted by skinniezinho View Post
    Regarding the almanac, very good idea, but I just have a Forerunner 945 LTE and don't arrive to g7towin to read it.
    Almanac management may not be supported in Pre-boot mode.

    g7towin: GPS->Commands->Get Supported Protocols

    Check the list of protocols for:
    A500 – Almanac Transfer Protocol
    A600 – Date and Time Protocol

 

 

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
  •