Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16
  1. #11
    Junior Member
    Join Date
    Feb 2015
    Location
    Italy
    Age
    50
    Posts
    9
    Rep Power
    0

    Default

    dear lolypop000,
    done, but unfortunately the device at the next boot does NOT create the garmindevice.xml file.
    Instead it creates the following folder and files structure:

    Garmin
    - Diag
    - sys_log.bin
    - gpx
    - current.gpx

  2.    Advertissements


  3. #12
    ☼ADMIN☼
    catymag's Avatar
    Join Date
    Nov 2007
    Location
    light side
    Posts
    23,605
    Rep Power
    5320

    Default

    I think it hasn't been formatted correctly
    [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. #13
    Junior Member
    Join Date
    Feb 2015
    Location
    Italy
    Age
    50
    Posts
    9
    Rep Power
    0

    Default

    Formatted again, flashed with ORIGINAL using the only firmware file I can found in "http://www.gpspower.net/garmin-receivers-firmwares/200071-how-get-needed-firmware-software-garmin-website.html"

    FIY this is the flashing response:
    Processing C:\Users\Sara\Desktop\Computer\Garmin\nuvi2xx_regionfileonly__510.gcd
    This is a GCD file.
    Patchable HWIDs: 660
    *Processing HWID 660
    Processing OK

    Still the same problem

    Would you point me to a complete firmware (if existsing)?

    Thanks, later

  5. #14
    Garmin/GPS Systems GMod.

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

    Default

    What complete firmware do you mean, and why are you using WebUpdater at this point? I think you're misunderstanding the term 'regionfileonly' and thinking that it's not as 'complete' as it could be, maybe? Whether it's called 'nuvi2xx_regionfileonly__xxx.gcd' or 'nuvi2xx_WebUpdater__xxx.gcd' or just 'gupdate.gcd' if it's the same official untouched version for the same hwid the naming of the *.gcd file is immaterial and the file content is the same [and 'complete']. Region file only was a term which Garmin started to use as they moved from uploading firmware using a self-extracting exe file to install fw for Western units [e.g. 'nuvi200_340.exe'] in favour of using WebUpdater to load the firmware [some Asian firmware is still loaded using exe files]. Don't be distracted by this change of naming convention, if you use WebUpdater or GarminExpress to load firmware by any method it will be placed on your 200 in the Garmin folder as 'gupdate.gcd' and the unit itself then updates the firmware version on the next boot cycle but only if it detects that the firmware version is higher than is already on board. If it's the same version [i.e. V5.10] as the patched cure firmware it will be ignored. The unit then cannot boot to create the garmindevice.xml file. Cure fw is not bootable, that's the very purpose of it so that the unit can be seen in MSM by a PC, corrupt files removed or a reformat done and then the original fw loaded so that the unit can boot.

    So i think you're simply not following the correct procedure to complete the 'cure' of your unit. After curing and correct reformat, flash the 'complete'/'original'/'non-cure' firmware to the unit using the method described in the GarminCure3 thread as an rgn file using updater.exe. If you have done it all correctly and the unit's not capable of creating the xml file then region 41 is damaged and will need to be erased. I don't think 2xx series is capable of copying 41 but can erase it. Please try using the fw as 066001000510.rgn flashed with updater.exe before we worry about that.
    '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
    Junior Member
    Join Date
    Feb 2015
    Location
    Italy
    Age
    50
    Posts
    9
    Rep Power
    0

    Default

    Dear Neil,
    thank you for your explanation.

    I'm pretty shure I've followed the tutorial to the letter, but I will start over again from beginning and let you know.

    FIY:
    the trouble started once I formatted the Garmin Disk, not the Garmin Volume from OSX creating a new FAT32 partition with MBR.
    Don't know if it helps troubleshooting.

    Later,
    Luca
    Last edited by Luca1967; 9th February 2015 at 12:04.

  7. #16
    Navigation software expert

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

    Default

    Try like this:

    - go to thread where you download prepusb
    - set prepusb the same way as is on picture in prepusb thread BUT set instead of Fat32 to fat and format
    - create new empty folder and add name Garmin
    - in pre boot flash with this:
    Spoiler: 2xx
    This post requires you to click the "LIKE this post" button and hit F5 to read this content.

    - after flash disconnect device from Pc and turn it on
    - turn off device and connect it to pc and run webupdater
    If you wish, you can [Only registered and activated users can see links. ]

 

 
Page 2 of 2 FirstFirst 12

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
  •  
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.