Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 6 of 37 FirstFirst ... 4567816 ... LastLast
Results 51 to 60 of 361
  1. #51
    Junior Member
    Join Date
    Oct 2017
    Location
    USA
    Posts
    9
    Rep Power
    0

    Default Just another guy with a busted Nuvi 260W....

    1) Model 260W, fw 7.8 (supposedly), HWID 1091

    2) Ran Garmin Express. Accepted fw update. Ran map updates and Express said the entire map wouldn't fit so I selected just the US Northeast. Express ran, it looked like it finished, but ended with an error (don't recall details, it's been a while)

    3) It won't boot.

    4) The PC does not see the GPS as a storage device, even in pre-boot mode. Doesn't matter whether there's an SD card in it or not.

    5) After the failed map load via Garmin Express the PC was able to see the device. I tried to copy the Garmin directory to the PC HDD - no joy. I discovered that several files were corrupted, including GarminDevice.xml and GUPDATE.GCD. Part of the directory structure was also corrupted. I have several other Garmin GPS units (GPSMAP 295, GPSMAP76S, Nuvi 680) that I maintain with WebUpdater and Garmin Express, and this is the first time I've had a problem. This is the point where I started searching forums. I saw comments about people reformatting their Nuvi and I was concerned until I read somewhere that a reboot would replace GarminDevice.xml and GUPDATE.GCD if they were missing. So, you guessed it, I reformatted the unit as Fat32 using Windoze 7 in an attempt to recover from a corrupt file directory. The format ended with an unknown error, but I was able to create a Garmin folder and the device booted up. Is seemed to follow the normal boot sequence, but hung up at "no detailed maps found". At this point I should probably have run WebUpdater and maybe we wouldn't be here today. I wasn't thinking clearly and just copied a gmapprom.img file from my Nuvi 680. Also, stupid me failed to copy out the new GarminDevice.xml and GUPDATE.GCD files. At this point every time I tried to boot it hung up on loading maps. I decided to try the update again and found that the PC was no longer recognizing the GPS. Back to forums and more research. I learned about preboot mode and GarminCure3 and g7towin and RMPrepUSB. I can get into preboot mode. When in preboot mode, even though the PC doesn't recognize the GPS as a storage device, WebUpdater does find the device and tries to run, but fails with the error “The update file is corrupted”. Garmin Express doesn’t recognize the unit. RMPrepUSB doesn’t see the unit.

    6) Yes, drivers are installed and work with all of my other Garmin GPS units

    7) Yes, I ran g7towin and it reports HWID 1091

    8) Yes, I have tried Cure3. I get 2 really quick messages that I think say “Loader Loading” and “Software Loading”, followed by the GARMIN screen with “Loader” in the upper center of the screen. I have tried both Cure and Original. EVERY time I run Updater I get the same series of 3 messages on the GPS, and the GPS drops out of preboot mode seemingly as soon as the software finishes loading. Forum post [Only registered and activated users can see links. ] contains 4 screen shots of the progress I should see. I only get the first screen, pretty much at the same time as I hear the ding-dong of the GPS dropping out of preboot mode.

    9) Yes, I can get into preboot mode and the GPS connects to the PC (dong ding), but the GPS does not show up as a connected drive/device. It will stay in preboot mode for about 40 seconds before disconnecting (ding dong) if I don't run Cure3.

    10) No NV backup. How do I do that?

    Thanks for reading all of that. I'd really like to get this unit working since it belongs to my mother-in-law and has a Lifetime maps license. I realize I made the mistakes of 1) not creating a complete backup before running the initial update; 2) formatting with Windoze instead of RMPrepUSB; 3) trying to use a map from another unit; 4) being the IT guy for the in-laws. My bad, I know it's my fault, please don't abuse me too much. Any suggestions (on fixing the GPS)?

  2.    Advertissements


  3. #52
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,448
    Rep Power
    1033

    Default

    Quote Originally Posted by insearchof View Post
    If this is often questioned I'm sorry. Here's the problem with Garmin Nuvi 250W not going past "GARMIN" without anything else start up status and will not go into preboot mode even tried all the software including garmincure3 (updater error pops up when attempting to start updater and will not do anything else). The reset button does not help either.
    Is there a way to get HWID (I can open the garmin up if know where to look or serial number decoded?) even cannot use G7ToWin utility due to failing to enter into preboot mode?
    If you have a backup of the file system look at your GarminDevice.xml for this: "<PartNumber>006-Bxxxx-00</PartNumber>". "xxxx" is the HWID.

    An otherwise healthy device which has been 'bricked' can still access preboot mode. Try this method: First make and load Cure3 fw into Updater.exe then select the radio button beside 'USB Device'. Ensure the nuvi is completely OFF, you may need to force it off by holding the power slide to the left for ~10 seconds. Connect using a 'known-good' miniUSB cable to a REAR port only of PC [not thru a hub]. Hold the top LH corner of the screen before connecting the miniUSB plug to the socket and keep holding it firmly. If the device details appear in the windpw next to 'USB Device' immediately hit enter on PC keyboard or 'OK' with mouse cursor on Updater's GUI. Keep holding the screen firmly until the flash successfully finishes or at least until 'Loader' or similar shows on the screen.

    If it really cannot access preboot then there may be damage to the flash chip, but it's not a common problem so unlikely.

    The official garmin express, win updater will not find the 250W either. Even tried garmin usb driver. Did not activate when connected.
    You must have Garmin USB drivers installed on the PC to use preboot mode for flashing. GE doesn't detect your device in preboot, only in mass storage mode.

    @hancock
    If you can't see it listed under Garmin Devices in Device Manager when it's in preboot then it's not reliably connected to PC or Garmin USB drivers aren't loaded. Reload the usb drivers and try different miniUSB cables and use Rear PC ports only [no hubs].

  4. #53
    Junior Member
    Join Date
    Oct 2017
    Location
    USA
    Posts
    9
    Rep Power
    0

    Default

    ok, tried that. 2 different cables, each in a different USB port on the rear of the PC. Same response of not seeing the Garmin show up as a storage device. I also got the same result when I tried connecting to a netbook running Windoze 10. The drivers loaded, I get the same dong-ding tune, but the Garmin doesn't show up in Windows Explorer as a storage unit. HOWEVER, based on Butters comment I checked the device manager and I have 'Garmin USB GPS' listed under 'Garmin Devices'. This goes away when the ding-dong sounds and the unit drops out. My old Nuvi 680 shows up as 'nuvi'' under 'Portable Devices'. A different Nuvi 260W and a Nuvi 200W both show up as 'Garmin' under 'Portable Devices'. None of these working units show up as 'Garmin USB GPS' like the problematic Nuvi 260W does.

    Next?

  5. #54
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,448
    Rep Power
    1033

    Default

    It's normal that a Garmin device connected to a PC when it's in preboot will not show up as a drive in Windows Explorer. That's because it's not in Mass Storage Mode. It will also not be detected in Disk Management as a Garmin Device and in Device Manager it will only show up under 'GARMIN Devices' as 'Garmin USB GPS'. When it shows there it's certainly in preboot and will be recognized by Updater.exe and can be flashed.

    [Only registered and activated users can see links. ]


    When preboot period expires or you remove pressure from the top LH corner of the screen, a healthy device will disconnect and then re-connects in Mass Storage Mode provided the USB connection is maintained. Once in MSM, it's visible normally in Windows Explorer, Disk Management and again in Device Manager but this time under Disk Drives.

    [Only registered and activated users can see links. ]


    However, your device is not healthy. Because it's bricked it can't default to MSM. It's by loading Cure firmware that we enable MSM to allow a re-format with RMPrepUSB.

    Summing up: You can get it to enter preboot, load Cure3 firmware to Updater.exe but it drops out of preboot or loses the USB connection before the flash completes.

    Please post a picture of the error screen displayed by Updater.exe.

  6. #55
    Junior Member
    Join Date
    Oct 2017
    Location
    USA
    Posts
    9
    Rep Power
    0

    Default

    I can't seem to figure out how to insert a screen shot. Here's the message text:

    App: Updater
    At: 11/9/2017 7:08:32 AM (UTC)
    OS: WIN32 Windows Platform, Major Version: 6, Minor Version: 1 Service Pack 1
    Processor: Pentium Pro or Pentium II, RAM: 4194303 KB
    IOU_UTILITIES.CPP-203-2.8

    Other than the date and time, I get the exact same message every time I run.

    I'm running 64 bit Windows 7 (version 6.1.7601) on a Core i7.

    Since I don't know what updater is doing, I don't know that the GPS is disconnecting before the flash is complete or not - it gets as far as the first screen in your post #48 in [Only registered and activated users can see links. ], and it looks just like your screenshot showing "100% Complete, 0.0 remaining". It's just that the ding dong sounds right about the same time as that screen comes up and then everything waits until updater times out and displays the error message.
    Last edited by hancock; 9th November 2017 at 09:02 AM.

  7. #56
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,448
    Rep Power
    1033

    Default

    What are you naming the Cure3 [*.RGN] file?

  8. #57
    Junior Member
    Join Date
    Oct 2017
    Location
    USA
    Posts
    9
    Rep Power
    0

    Default

    I'm not renaming the file. Every file that has been created has been named 109101000780.rgn. I'm using nuvi2x5W_GCDFile-MTK__780.GCD as the input file. GarminCure3.exe, Updater.exe, and the input file are all in C:\Users\Jim\Desktop\GarminCure3. I see no new files after hitting the Make Firmware button, but after I click the Updater.exe button something creates a new directory in C:\Users\Jim\Desktop\GarminCure3\GarminCure3-TEMP and writes the 109101000780.rgn file to the new directory.

    Should I be renaming the .rgn file, or trying to move it to somewhere other than where Cure3/Updater is putting it? Should I be seeing a new file when I hit the Make Firmware button but before I run Updater?

  9. #58
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,448
    Rep Power
    1033

    Default

    That's correct. No file is created until you click the 'Updater.exe' button in the GUI. It's indeed the correct firmware for nuvi 260W (2nd generation, 2009) HWID 1091 with MediaTek chip. It has the same hardware as 2x5W so uses it's firmware.

    Try this. Open the RGN file from the temp folder with RGN_Tool and overwrite the SW Version with '781' and then save it as 109101000781.rgn. See if that will flash successfully.

  10. #59
    Junior Member
    Join Date
    Oct 2017
    Location
    USA
    Posts
    9
    Rep Power
    0

    Default

    Tried 2 different ways to build and flash a 109101000781.rgn file:

    1. Edited the 109101000780.rgn file with RGN_TOOL per your instructions and saved it as 109101000781.rgn. Copied the new 109101000781.rgn to the same folder as Updater.exe. In Windows Explorer I dragged 109101000781.rgn onto Updater.exe and let it run.
    2. Ran RGN_TOOL on nuvi2x5W_GCDFile-MTK__780.gcd and changed the s/w version to 781. Saved the modified file as nuvi2x5W_GCDFile-MTK__781.gcd and ran Cure3. Updater created a new 109101000781.rgn file and attempted to flash it.

    In both cases everything behaved the same as it always has (ding dong and drop the connection as soon as the 100% message pops up) except that I did not get the usual pop-up message asking "Do you want to replace the current software version with the same software version?". That's understandable since the rgn file has been changed to 781, but does that mean that there was enough of a connection that Updater was able to read the unit and determine that 7.80 was already loaded? Is that something that Updater does?
    Last edited by hancock; 10th November 2017 at 07:53 AM.

  11. #60
    Important User IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow thisIMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,448
    Rep Power
    1033

    Default

    Quote Originally Posted by hancock View Post
    Tried 2 different ways to build and flash a 109101000781.rgn file:
    ......
    In both cases everything behaved the same as it always has (ding dong and drop the connection as soon as the 100% message pops up) except that I did not get the usual pop-up message asking "Do you want to replace the current software version with the same software version?". That's understandable since the rgn file has been changed to 781, but does that mean that there was enough of a connection that Updater was able to read the unit and determine that 7.80 was already loaded? Is that something that Updater does?
    Yes and yes.

    Updater.exe checks the current fw version on the device. By 'fooling' it with a faked higher version fw it saves having to click thru' that message, the reasoning being that then you may gain a little more time get the flash well-enough established to stop the problem you've been having. Usually when the flash is already established however the device won't exit preboot nor will updater.exe time out. The problem is elsewhere I think.

    What is the visual symptom of the bricking? Is it stuck on splash screen with or without text like 'loading maps' at the bottom of the screen, or is it boot-looping (as examples)?

 

 

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
  •