Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 50
  1. #11
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    smokefree, in order to erase NV proceed exactly as Neil suggested for backing up NV, but edit update.txt and replace the whole line rrgn,41,... with ergn,41.

  2.    Advertissements


  3. #12
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,341
    Rep Power
    718

    Default

    OK, will try that when I get home. How do I get a proper rgn41 back in the unit?

  4. #13
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    You erase region 41 and fw_all.bin, when booted for the first time, rebuilds region 41 from scratch.
    Or you can restore your backup with xrgn,41,1:/path_to_backup.bin, but as you understand it can be poisoned.

  5. #14
    Garmin/GPS Systems GMod.

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

    Default

    And if it is, you'll need to erase it again and leave it to rebuild but then it won't replace the registration and unlock codes unfortunately. It really is a method of absolute last resort in my opinion if nothing else works. No codes in the GarminDevice.xml means problems loading legitimate maps in my experience ... any way around that you can tell us Kunix? [apart from codes from a backup xml inserted into one on a media card Garmin folder, i.e. fake/stunt double nuvi i mean of course].

    Maybe also someone has found a way to restore the codes from a 'poisoned' rgn41 backup into a clean re-built but codeless backup [hint, hint].
    '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. ].

  6. #15
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    I can't edit separate NV records, therefore I can't edit unlocks.
    There is a way to restore unlock codes via USB command, but it requires a service USB cable and also I've sold an utility for doing this several times, so I can't release it.
    I think that smokefree doesn't need unlock codes if his unit doesn't boot at all. Moreover, he can always restore his NV backup if it turns out to be healthy.

  7. #16
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,341
    Rep Power
    718

    Default

    Forgot to mention in post #1: there is a Lifetime Map update subscription linked to this zumo. After flasing CURE FW into the unit, I was able to update the maps via Garmin Express.

    Quote Originally Posted by kunix View Post
    You erase region 41 and fw_all.bin, when booted for the first time, rebuilds region 41 from scratch.
    Just so I understand things right... after erasing rgn41, do I also need to erase fw_all.bin (if so, how?), or is that done by erasing rgn41?

  8. #17
    Garmin/GPS Systems GMod.

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

    Default

    No, fw_all.bin is responsible for rebuilding rgn41 [albeit without codes] is my certain understanding. There's no suggestion by either of us that you need do anything, after all other options are exhausted, other than [1] back up 41 [already done] [2] Erase 41 [3] Re-write 41 to see if unit performs normally [4] If it doesn't, erase it again and let it be rebuilt w/o codes [as a last resort imo].
    '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. ].

  9. #18
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    Neil, points [2] and [3] performed successively won't change anything So, I think smokefree can omit them and proceed to [4]

    smokefree, no need to erase fw_all.bin. However, if the flash chip is broken, then erasing/writing any region (including region 14, containing fw_all.bin) can help reveal the chip failure.
    Then most probably only hardware repair will help. Though, I don't suggest doing this test right now.

  10. #19
    Global Moderator

    smokefree's Avatar
    Join Date
    Sep 2010
    Location
    @ home
    Age
    36
    Posts
    3,341
    Rep Power
    718

    Default

    Quote Originally Posted by kunix View Post
    no need to erase fw_all.bin. However, if the flash chip is broken, then erasing/writing any region (including region 14, containing fw_all.bin) can help reveal the chip failure.
    Please clarify if fw_all.bin is included in rgn41 or rgn14.
    Post 11 tells me to erase rgn41, not rgn14.

  11. #20
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    NV is inside region 41. fw_all.bin is inside region 14. There is no mistake.
    I asked you to erase region 41.
    And I didn't ask you to erase region 14.

 

 
Page 2 of 5 FirstFirst 1234 ... LastLast

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.