Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25
  1. #21
    Junior Member
    Join Date
    Mar 2016
    Location
    UAE
    Posts
    9
    Rep Power
    0

    Default

    SOLVED ...


    My great thanks to Neil for all his care and help in solving this issue

    The device is back alive working with no problem ..

    "lolypop000" has solved it and I really want to thank thank you very much


    I guess the explanation of solving the problem with her

  2.    Advertissements


  3. #22
    ☼ADMIN☼
    catymag's Avatar
    Join Date
    Nov 2007
    Location
    light side
    Posts
    23,578
    Rep Power
    5314

    Default

    Loly is a magician
    I will mark thread as solved
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    You have to navigate to get to the good.
    Nuvi1250/Nuvi 34xx/Nuvi 2200/Nuvi 66/Oregon 600/Galaxy S5 MM 6.0.1/TomTom GO/iGO Nextgen Avic,Basar,Isr.Gift/Navigon
    Please don't flood my pm box with questions you can post on forum!! You won't hear back from me.

  4. #23
    Navigation software expert

    lolypop000's Avatar
    Join Date
    May 2010
    Location
    EU
    Posts
    2,925
    Rep Power
    849

    Default

    I like to thank you to have courage

    If i explain here what i do, a lot of user will do this in wrong way and they will brick device to point with no return.

    If someone will have the same problem, i will create files and step by step tutorial like i do it for you

    I am happy for you that your device is now back in normal condition.
    If you wish, you can [Only registered and activated users can see links. ]

  5. #24
    ☼ADMIN☼
    catymag's Avatar
    Join Date
    Nov 2007
    Location
    light side
    Posts
    23,578
    Rep Power
    5314

    Default

    @Loly
    magician and wise
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    You have to navigate to get to the good.
    Nuvi1250/Nuvi 34xx/Nuvi 2200/Nuvi 66/Oregon 600/Galaxy S5 MM 6.0.1/TomTom GO/iGO Nextgen Avic,Basar,Isr.Gift/Navigon
    Please don't flood my pm box with questions you can post on forum!! You won't hear back from me.

  6. #25
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,388
    Rep Power
    1434

    Default

    Great work Loly! As Caty said 'magician and wise', i agree.

    A warning here for others from this unfortunate experience which has ended happily only because of lolypop000's knowledge and experience dealing with Garmin firmwares. When flashing firmware whether original or modded by RGN file, unless you know exactly what you're doing, you must always use the 'fail-safe' naming convention of XXXX01000xxx.rgn where 'XXXX' is the HWID of the FIRMWARE being used which should also match the HWID of the DEVICE. See here to find them: [Only registered and activated users can see links. ]. Also 'xxx' is the firmware [unit software] version without decimal [i.e. V8.30 is shown '830']. Even though the OP used the25x9 firmware in error, if the naming convention of 194701000830.rgn had been used for that firmware then Updater.exe would not have flashed it and reported there are no updates for the device. So when the HWID of the device doesn't match the first 4 numerals in the rgn file name you will get that message and the process is stalled. Change that naming convention [OUT.RGN is most commonly used by experienced modders] and the flash is forced. Even removing one zero from XXXX0100xxx will tell Updater.exe to ignore HWID mismatch and force the flash. Another 'trap' is when using SD card flashes, if the Ldr.bin [boot.bin] is not correct for the device then incorrect information is written to the boot sectors of the unit and it may become irreversibly bricked. Thankfully Loly was able to recover this unit, he'd be one of the few ppl in the world outside of Garmin who could do so using firmware mods.
    '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. ].

 

 
Page 3 of 3 FirstFirst 123

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.