Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 7 FirstFirst 1234 ... LastLast
Results 11 to 20 of 61
  1. #11
    Garmin/GPS Systems GMod.

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

    Default

    @scoo
    The detailed instructions behind the spoiler in Post #4 to make the hybrid firmware should be easy enough even if you have only very basic understanding of the process. Don't do it if you don't grasp the basics and of course regardless the risk is all yours. If you want further explanation or help with modifying the firmware or flashing then just ask for specifics.

    However seeing alois72 has been successful with the hybrid flash using the 590's boot.bin it should be relatively safe to now attempt a flash using the full 595 firmware which will change the HWID to 2436. That's actually a relatively more simple process and because the hybrid method works i would happily do it myself but it does still carry an element of risk for the first attempt. Here's the tut if you want to do that instead of the hybrid method:
    Spoiler:
    First ensure that you know how to get your device into [Only registered and activated users can see links. ]. Put Zumo595_320.gcd, [Only registered and activated users can see links. ] and [Only registered and activated users can see links. ] into a folder somewhere convenient, your desktop will do for now. Remove GUPDATE.GCD file from the device's .System folder if it's present in there [it might not be present, but make sure you check and remove it if it's there]. Remove the Text and keyboard folders as they might stop the unit booting, they will have to be replaced later with the 595-specific folders. Remove any sd card if there's one in the device. Then proceed as follows:

    • Make a full files back and [Only registered and activated users can see links. ] [Important!]
    • [Only registered and activated users can see links. ] the device or preferably [Only registered and activated users can see links. ] [favourites can be restored later from your files backup, GPX\current.gpx]
    • Remove the file GUPDATE.GCD [if present in .System] and the Text and keyboard folders from the unit if not already done [don't proceed further until you do]
    • Open Zumo595_320.gcd in RGN_Tool and press 'RGN' button near top left of the GUI, save the resultant file named as OUT.rgn into your folder
    • Drag OUT.rgn onto Updater.exe, enable the radio button to the left of 'USB Device' and leave the GUI open on your desktop
    • Put your device into preboot using the method that worked however if having to hold the screen best to power it on by connecting to a rear port of PC. Keep watching the window to the right of 'USB Device' on Updater's GUI.
    • IMMEDIATELY you see the device window populated press 'OK' button on the GUI or just hit the enter key on your PC keyboard and keep holding the screen, if that method's been used to attain preboot, until the flash finishes.
    • Your device should reboot as a 595 with it's features enabled. Clear nonvol or hard reset again [if the device has not reset itself by asking for location etc info be re-entered on initial boot]. Replace the keyboard and Text folders with the ones for 595 [see Post #9].



    If you or anyone else does this please report back so that others can benefit. Remember, i haven't tried this on an actual device either so the risk is all on the user.

    WARNING: Only flash the 595 firmware to convert a zumo 590 to 595. IT IS NOT SUITABLE FOR ANY OTHER DEVICE and if the 595 fw is flashed to an incompatible device it will be bricked, probably permanently hard-bricked. The use of OUT.rgn naming removes the inherent protection of fail-safe naming [<hwid>01000<swv>.rgn] which gives some protection against flashing incompatible firmware. We can do this to change the HWID for 590>595 only because they are matching hardware. Flashing a fw to any device with a different [Only registered and activated users can see links. ] is usually disastrous.
    '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. ].

  2.    Advertissements


  3. #12
    Junior Member
    Join Date
    Dec 2014
    Location
    The netherlands
    Age
    59
    Posts
    9
    Rep Power
    0

    Default

    seems like a working change, however there is no prove off the conversion, only by word.
    Could someone upload some pictures or a video?

  4. #13
    Junior Member
    Join Date
    Aug 2012
    Location
    Austria
    Age
    46
    Posts
    9
    Rep Power
    0

    Default

    @charleyr

    I'll take a picture for you !


    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]

    You see the black "Garmin" below.
    Last edited by alois72; 14th July 2016 at 16:50.

  5. #14
    Junior Member
    Join Date
    Aug 2012
    Location
    Austria
    Age
    46
    Posts
    9
    Rep Power
    0

    Default

    Pictures for @charleyr above

  6. #15
    Junior Member
    Join Date
    Dec 2014
    Location
    The netherlands
    Age
    59
    Posts
    9
    Rep Power
    0

    Default

    Thx,

    Will try that after my holliday.

  7. #16
    Member
    Join Date
    May 2013
    Location
    moon
    Posts
    17
    Rep Power
    0

    Default

    Did it !!!
    Converted to original 595 and works perfect

    CcfQd

    cu2W7

    IWka0

  8. #17
    Member
    Join Date
    May 2013
    Location
    moon
    Posts
    17
    Rep Power
    0

    Default

    After that, I decide to replace Text and Keyboard files.
    Now all is in the same language.

    The only missed stage was the backup of the original 590 not done.

  9. #18
    Junior Member
    Join Date
    Aug 2012
    Location
    Austria
    Age
    46
    Posts
    9
    Rep Power
    0

    Default

    @scoo

    In the GarminDevice.xml.....what is on the line.....<Description>Zumo</Description>

    Not Zumo 595 ? (I convert also to original 595)

  10. #19
    Member
    Join Date
    May 2013
    Location
    moon
    Posts
    17
    Rep Power
    0

    Default

    @alois72

    In the GarminDevice.xml

    It says only <Description>Zumo</Description>. No Zumo 595 or 590

    And in the Registration codes, any code is showing.


    Even if I try to change it with notepad, all is erased when i boot. Then no very good news to a 100% conversion.

    Other problem is, Basecamp shows an error and says that the functions will be working with reduced functionality.

    When I registered the product via Garmin Express, it was registerd as Zumo 590.


    Otherwise all is working, but...
    Last edited by scoo; 29th July 2016 at 19:12.

  11. #20
    Garmin/GPS Systems GMod.

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

    Default

    Quote Originally Posted by scoo View Post
    @alois72

    In the GarminDevice.xml

    It says only <Description>Zumo</Description>. No Zumo 595 or 590

    And in the Registration codes, any code is showing.
    Entitlement of the device is detected by varying identity methods'. e.g. Lifetime map subscription is linked to the UID which never changes, not in the XML or elsewhere, nor do its registration and unlock codes change, even if the HWID does change. But of course firmware upgrades and other files ancillary to maps are given according to the HWID which can change.

    Even if I try to change it with notepad, all is erased when i boot. Then no very good news to a 100% conversion.
    The GarminDevice.xml is re-written by the device on every boot from information it holds in its non-volatile memory. You can edit whatever and the XML file will simply be overwritten. What matters is how the unit functions not how it identifies itself. e.g. nuvi 2460 converted to dezl 560 identifies in the XML and on the boot screen as 'dezl 2460' and nuvi 3790 > 3490 continues to identify itself as 'nuvi 3790' but both devices do function as the conversions intend and of course their HWIDs are changed on 'full firmware' conversion.

    Other problem is, Basecamp shows an error and says that the functions will be working with reduced functionality.
    What message and what functions please.

    When I registered the product via Garmin Express, it was registerd as Zumo 590.
    The ownership registration is a separate thing again to the identification examples given above and is linked to the fixed UID. You can change the name of the device in GarminExpress itself on your PC, but as far as your registration on Garmin's server is concerned that UID is forever identifying it as a zumo 590. Firmware upgrades are still given for a zumo 595 because the HWID is used for that purpose, even tho' also via GarminExpress.
    '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 2 of 7 FirstFirst 1234 ... LastLast

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.