Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 50
  1. #21
    Global Moderator

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

    Default

    Clear! Still a novice when it comes to modding FW which may have caused confusion on my part. A typo (41 versus 14) could not be excluded. Thanks for clarification. As mentioned, I'll be home after 1500 UTC, so will report back later.

  2.    Advertissements


  3. #22
    Global Moderator

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

    Default

    I performed the steps from post #4 combined with the instructions in post #11. The process went well, but had no effect on the problem. Content of the update.log file is as follows:

    Code:
    Please Login or Register to see the links
    The unit rebooted twice. I suspect this is normal, as it reboots once as instructed by the command in the update.txt file and reboots again on detection of a missing rgn41 (?).

    Anything else I can try? How about the suggestion by Neil in post #8?

  4. #23
    Navigation software Moderator

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

    Default

    Well, this kinda sucks. It should have recovered after taking this step.
    Yes, try flashing gfwpack-ed fw_all.bin.
    If it doesn't help, I would suggest dumping fw_all.bin with rrgn,14,1:/14.bin and comparing it to the flashed one.

  5. #24
    Global Moderator

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

    Default

    From post #8:

    Quote Originally Posted by Neil View Post
    Just as quick to make it for you really, so here it is:
    Spoiler: Click
    [Only registered and activated users can see links. ]

    Usual stuff, drag it onto Updater.exe, connect in preboot mode and hope it flashes.
    The flash was successful, but it made no difference to the symptoms of the zumo.

    Well... not completely true. There is a difference in that the unit does not switch off anymore after 3 seconds when on battery power. It stays on now (still frozen on the Garmin splash screen) until switched off manually by pressing and holding the power button for more than 5 seconds.

    Quote Originally Posted by kunix View Post
    If it doesn't help, I would suggest dumping fw_all.bin with rrgn,14,1:/14.bin and comparing it to the flashed one.
    I don't fully understand. There is a rgn14 in the unit which I can dump as described. What exactly do I compare it with?


    Edit 1:
    I notice that since the above action, the zumo is not recognised anymore by the PC, WebUpdater or Garmin Express.

    Edit 2:
    Had to flash CURE FW into the unit via GarminCure3 and Updater.exe to get it recognised again by PC etc.
    Last edited by smokefree; 2nd November 2014 at 20:35.

  6. #25
    Garmin/GPS Systems GMod.

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

    Default

    Quote Originally Posted by smokefree View Post
    ..... I don't fully understand. There is a rgn14 in the unit which I can dump as described. What exactly do I compare it with? .....
    As one firmware mug to another, i'll try to help you understand to my limited extent, while kunix wrestles with some more advanced possibilities for your very sick unit. The dump of region 14 is the unit's firmware, i.e. fw_all.bin. Even though 14.bin may be quite a bit larger by a lot of FFs tacked on at the end, they otherwise should be the same before there. I think comparing them in hex to see if there are any other differences before the padded bytes will show whether fw_all.bin is being properly flashed.

    Dump it and kunix will tell you what to do if the hex compares don't match. This might help you, HexCmp2:
    Code:
    Please Login or Register to see the links
    Last edited by Neil; 2nd November 2014 at 21:15.
    '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. ].

  7. #26
    Global Moderator

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

    Default

    Please bear with me, but just to get things clear for myself, this is what I understand I am expected to do:

    1. Since I flashed CURE FW after post #24, I assume this may have affected the fw_all.bin which I flashed in post #24. Am I correct in my assumption I need to flash the packed fw_all.bin again?
    2. I then dump rgn14 as described and compare it in a hex editor to the packed fw_all.bin file. Correct?

  8. #27
    Garmin/GPS Systems GMod.

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

    Default

    SF, i'm waiting for kunix to answer you learnedly, but my horse-sense is that it's pointless comparing the packed fw_all.bin to the dump of 14.bin [whether dumped after either original, cure or packed fw_all flash] as the differences will be profound because of the packing regardless if the flash does complete or not.

    It's only worth comparing the original fw_all.bin with the 14 dump obtained after the original fw_all has been flashed in my [uneducated] opinion. Best wait until kunix is back on-line, but if you want to do something now flash rgn made with original boot and original fw_all, then dump 14 again using patched boot.bin>rgn method.

    Compare original fw_all.bin with new 14.bin, except for the trailing FFs in 14.bin they should be the same, if not then the flash didn't complete for sure i would think.
    '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. #28
    Navigation software Moderator

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

    Default

    Neil, it does make sense to compare the fw_all.bin being flashed and the fw_all.bin dump, regardless if fw_all.bin is packed or not.

    Unpacking is always made in RAM, after fw_all.bin is copied there from flash.
    And by comparing fw_all.bin being flashed and dumped one we test the flash chip.
    I've seen some flash chips not saving data to some blocks.

    Actually It's better to compare the original fw_all.bin, as it's bigger and we can test more flash blocks.

  10. #29
    Global Moderator

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

    Default

    OK, here's the result. I used the original (non-packed) fw_all.bin:

    - As of offset 0081BF00, fw_all.bin is empty, where 14.bin contains only FF's up to and including offset 0087FFF0.
    - The only real difference found, is in offset 00000010. fw_all.bin reads 0C 80 A0 E1, where 14.bin reads 0B 80 A0 E3. See screenshot below:

    SG0UBHe

    This difference looks a bit like step 2 in post #4, but there 0C 80 A0 E1 in the original file is changed into 0C 80 A0 E3 (the 0C at the beginning is left unchanged there).
    What does this indicate? How did the 0B end up inside 14.bin?

  11. #30
    Garmin/GPS Systems GMod.

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

    Default

    @kunix
    Yes, much as i thought. Just one point though, SF posted this:
    Quote Originally Posted by smokefree View Post
    ........
    2. I then dump rgn14 as described and compare it in a hex editor to the packed fw_all.bin file. Correct?
    That's what i meant is pointless because the packed file will always differ when compared to the dumped 14. It seems logical to me only by comparing 14 to the original [or unpacked] fw_all can there be a valid comparison. So in essence, whether the flash was done with original or packed fw_all, the compare of the dumped 14 has to be to the full [not packed] fw_all, is that right?.

    @both
    I'd have thought there should be no difference other that the empty padding at the end of the 14 dump. In a 265W i've removed the extraneous FFs and the fw_all and 14 bins are then identical in hex and hash check. Why should a zumo 220 be different? A fault?
    Last edited by Neil; 3rd November 2014 at 11:10.
    '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 5 FirstFirst 12345 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.