Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 32
  1. #21
    Navigation software Moderator

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

    Default

    ceco134
    GarminCure3 can't break the firmware flashing functionality in the real pre-boot mode (as in your case) by design. Something else has happened.
    If you can't flash a longer (newer) firmware but you can flash an older (shorter) firmware, then probably the flash chip is dying. You can try comressing fw_all.bin with gfwpack.exe (you can compress both CURE-ed and and ORIGINAL) and making it shorter.
    Or it has something to do with boot.bin version (older boot.bin works but newer doesn't), which is also bad (some hardware is failing). Then you can try using the older boot.bin with the newer firmware.

    Also if for some reason you can't flash GarminCure3-ed firmware (well, I've seen some devices that refuse running any firmware except some particular version due to unwriteable flash chip blocks), then flash the working firmware and use QuickCure3 for accessing the mass storage mode.
    Last edited by kunix; 26th December 2013 at 08:40.

  2.    Advertissements


  3. #22
    GPSPower Helper

    dasilvarsa's Avatar
    Join Date
    Feb 2011
    Location
    Global
    Posts
    1,160
    Rep Power
    351

    Default

    We have to be very careful when Nuvi USB is Dodgy, but Nuvi can still Navigate.
    Best route to explore is Reading, Writing and deleting files via SD Card and even Updating Firmware via SD Card. (If Possible ?)
    Rationale: A working Nuvi without USB is better than a brick.
    The difference between stupidity and genius is that genius has its limits.
    Albert Einstein.

  4. #23
    Garmin/GPS Systems GMod.

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

    Default

    Quote Originally Posted by dasilvarsa View Post
    ....... and even Updating Firmware via SD Card. (If Possible ?)
    .....
    Yes, of course. You can both delete gupdate.gcd from .System [or Garmin folder on older units] and write the later .gcd to the unit using ldr bin together with update.txt in sd. Or simply put gupdate.gcd in a Garmin folder on the sd, insert and reboot.
    '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. ].

  5. #24
    Member
    Join Date
    Jan 2012
    Location
    Chicago
    Posts
    29
    Rep Power
    0

    Default

    Hello,as Kunix suggested I made a custom firmware:a boot loader from PouchX rgn file and the new core from the latest nuvi13xxand14xxseries_GCDFile__620.gcd.Finally I managed to update the device but is still unrecognized from the computer.I probably will better give up and use it this way till it die.
    Quote Originally Posted by kunix View Post
    ceco134
    GarminCure3 can't break the firmware flashing functionality in the real pre-boot mode (as in your case) by design. Something else has happened.
    If you can't flash a longer (newer) firmware but you can flash an older (shorter) firmware, then probably the flash chip is dying. You can try comressing fw_all.bin with gfwpack.exe (you can compress both CURE-ed and and ORIGINAL) and making it shorter.
    Or it has something to do with boot.bin version (older boot.bin works but newer doesn't), which is also bad (some hardware is failing). Then you can try using the older boot.bin with the newer firmware.

    Also if for some reason you can't flash GarminCure3-ed firmware (well, I've seen some devices that refuse running any firmware except some particular version due to unwriteable flash chip blocks), then flash the working firmware and use QuickCure3 for accessing the mass storage mode.

  6. #25
    Navigation software expert

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

    Default

    If you now can flash try this.

    - With cure tool create Cure FW
    - try if you can flash your unit with cure FW and if you can then enter in mass storage.
    If you wish, you can [Only registered and activated users can see links. ]

  7. #26
    Member
    Join Date
    Jan 2012
    Location
    Chicago
    Posts
    29
    Rep Power
    0

    Default

    Already tried and updated with the cure firmware and old bootloader-no result at all, the device is still recognized as removable device....
    Quote Originally Posted by lolypop000 View Post
    If you now can flash try this.

    - With cure tool create Cure FW
    - try if you can flash your unit with cure FW and if you can then enter in mass storage.

  8. #27
    Navigation software expert

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

    Default

    Do you use in cure tool custom made FW or you create new FW?
    If you wish, you can [Only registered and activated users can see links. ]

  9. #28
    GPSPower Helper

    dasilvarsa's Avatar
    Join Date
    Feb 2011
    Location
    Global
    Posts
    1,160
    Rep Power
    351

    Default

    Have you tried to downgrade normal firmware via SD Card ?
    Version 5.1 Gupdate.gcd is my choice.
    Nothing is without risk !
    The difference between stupidity and genius is that genius has its limits.
    Albert Einstein.

  10. #29
    Member
    Join Date
    Jan 2012
    Location
    Chicago
    Posts
    29
    Rep Power
    0

    Default

    Not sure I correctly understand the question.Cure firmware was made from old boot and new core 6.10 firmware,using the garmincure3 made the rgn file,updated by updater.exe.
    Quote Originally Posted by lolypop000 View Post
    Do you use in cure tool custom made FW or you create new FW?
    Tried this too.Found:nuvi13xxand14xxseries_regionfileonly__510.gcd 25.5MB that is bigger than nuvi13xxand14xxseries_GCDFile__580.gcd 15.7MB.Updated (downgraded) via SD card,still removable device in my computer....

    Quote Originally Posted by dasilvarsa View Post
    Have you tried to downgrade normal firmware via SD Card ?
    Version 5.1 Gupdate.gcd is my choice.
    Nothing is without risk !

  11. #30
    Garmin/GPS Systems GMod.

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

    Default

    It is possible to live with the device as it is. However, if the usb socket is faulty it maybe can be repaired by reflowing [quite vulnerable to being stressed by the design of the board attachment, particularly so in 14xx but also other 1xxx].

    If you feel it's not worth your effort to pull it down to do that, i would agree. Anyway, it may be that the socket itself is ok and the problem is in the unit's flash disc itself as kunix has speculated. I have a 1490 with a usb socket that will work intermittently and keeping it charged is the biggest problem. Everything can be done from microSD though, even map updates, full backup, erasing and updating individual files such as voices and vehicles. So i guess that is how you stopped it flashing back to 5.80 from the gupdate.gdc in .System, you deleted that gcd file via txt command from sd?

    If you can be bothered, there are some other things to attempt [if you haven't already] to see if the PC then recognises it. So, before you give up on it you may like to try:

    (i) Clear unprotected Non Volatile memory [On Map Screen press 'Speed', then press and hold Speedometer for ~6 secs>Developer Info>Nonvol Available>Yes].

    (ii) Backup the entire internal file system to sd, and provided that's successful, then erase it [using sd commands]. Reboot it empty [1xxx will reboot like that] then check if it's seen by pc.

    (iii) Backup protected NV [region 41], if successful it should be 4096KB in size. Erase 41, check if unit's seen by pc and then restore it.

    The commands for doing these things can be found here: [Only registered and activated users can see links. ] [Only registered and activated users can see links. ].
    '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 4 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.