Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 13 of 14 FirstFirst ... 311121314 LastLast
Results 121 to 130 of 135
  1. #121
    Important User Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,957
    Rep Power
    1273

    Default

    Cool, now use the following .png to make your logo and see if the colors are correct when on the 66
    Spoiler: .

    [Only registered and activated users can see links. ]
    Do not PM me with questions. That's what a forum is for.

  2.    Advertissements


  3. #122
    Garmin Expert babj615's Avatar
    Join Date
    Sep 2010
    Location
    USA
    Posts
    109
    Rep Power
    55

    Default

    I had to convert the png to bmp before GIR would let me use it (has to be same format as original).

    The colors are closer, but still far off. Was very green first time, now more reddish purple, not orange yet.
    Last edited by babj615; 13th August 2020 at 09:28 PM.

  4. #123
    Important User Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,957
    Rep Power
    1273

    Default

    Ok, see if the following is better. This time I convert to .bmp for GIR and created the .bin for you
    Spoiler: .

    [Only registered and activated users can see links. ]
    Do not PM me with questions. That's what a forum is for.

  5. #124
    Garmin Expert babj615's Avatar
    Join Date
    Sep 2010
    Location
    USA
    Posts
    109
    Rep Power
    55

    Default

    8^(


    Spoiler: image
    [Only registered and activated users can see links. ]

  6. #125
    Important User Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,957
    Rep Power
    1273

    Default

    Hmmm, I don't trust GIR encoding of the 16-bit correctly. So I manually copy the 16-bit .bmp conversion from the original .png directly into .bin
    Spoiler: .

    [Only registered and activated users can see links. ]
    Do not PM me with questions. That's what a forum is for.

  7. #126
    Garmin Expert babj615's Avatar
    Join Date
    Sep 2010
    Location
    USA
    Posts
    109
    Rep Power
    55

    Default

    That one is pretty, and inverted vertically!


    Spoiler: image
    [Only registered and activated users can see links. ]

  8. #127
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,118
    Rep Power
    231

    Default

    Quote Originally Posted by babj615 View Post
    Thank you, Butters.

    I admit I am very late to the party and am trying to learn what you already know, and information of this type is not easy to come by.
    I'm far from an expert, more a hands-on enthusiast. You're probably looking for in-depth knowledge of the kind that osiris4isis has. Unlike me who's a mere journeyman, he's an experienced coder however i think the very precise inner workings of the proprietary Garmin OS are privy to only a couple if any individuals outside of Garmin's own developers.

    Are 'Regions' just a term for different 'sections' of the device firmware file?
    I'd avoid calling regions 'sections' because that term is used in regard to BIN component parts of a firmware file. You can see that yourself of course by looking at RGN_Tool's GUI. So the so-called regions i.e. 'sections' contained in a device's firmware file are really BIN files rather than regions themselves although they contain copies of the data to be flashed to some of the device's actual regions. The device's regions themselves are indeed 'parts' of the device's flash memory. A very simplistic way maybe would be to view Garmin's regions as somewhat akin to partitions in Windows although that's not really accurate either, more just a vague similarity.

    I would be ever so grateful for a crash course in what 'regions' are, what types exist, how they are used, etc. etc.
    A specific *.bin is of course a copy of the data contained in a particular RGN (region) of which there are 255 separate ones possible, however nowhere near all of them are populated or indeed even present on a particular Garmin device. You're already quite aware of RGN16 (0x10) of course and in particular of it's function to do with the splash screen/logo during boot. It can also control/suppress/enable some features in the firmware of some devices, nuvi 1xxx series being a great example of that. Some regions are virtual, RGN12 (0x0C) for example. It's responsible for flashing two physical regions, RGN5 and RGN43, in turn and it makes up the boot.bin component (section) of a firmware file, be it a *.gcd or an *.rgn file. Continuing the somewhat nebulous Windows analogy, RGN5 can be thought of as being like the BIOS/UEFI of a PC, it's in fact the device's bootloader. Messing with RGN5 is often fatal although sometimes a good copy of it is retained in RAM and can be accessed by the device if the device hasn't been forced off. The naming of "boot.bin" is therefore misleading because it in fact contains the ramloader, not the bootloader which is in RGN5 although the latter is ultimately flashed by the virtual RGN12 which is flashed by boot.bin as required. The visible file system in modern MSM/MTP devices is itself a region, RGN48 in older devices and RGN83 in recent ones, these can be 'dumped' like other regions and the resultant BIN file can be opened to reveal folders and files using several programs, 7-Zip and other archive softs, PowerISO etc. The basic operating firmware is mostly contained in RGN14 (0x0E), Garmin calls it 'System Software'. If 14 is empty or corrupt then the device cannot start and 'System Software Missing' is displayed on the screen with the device defaulting to a preboot state and accessible by updater.exe and other 3rd party programs such as G7ToWin. Many regions that are populated are not really understood and their specific purpose remains unclear, at least to mere mortals like me. Prior to their devices having visible file systems, Garmin had ones which the flash memories were entirely made up of specialized regions, this is the origin of the large number of possible regions, i.e. 255 of them. Where modern Mass Storage capable devices have Voice, Text, Keyboard etc. files in the visible file system, older 'region-only' devices have the data in specific regions, for example Voices in RGN17 in my recollection. While it's still possible to 'flash', for example, a Voice file (*.vpm) packed as an RGN file with boot.bin, it's not flashed to RGN17 as with early devices rather it's converted to a ZIP file and placed in the device's file system in RGN48 or 83 and then subsequently unpacked by the device on next boot and the VPM file placed into the Voice folder of RGN48/83. Another very important region is RGN41 in older devices/RGN154 in recent ones. It's primary function is well-known as being the device's non-volatile memory containing individual information about the particular device, it's registration and unlock codes for instance. It's generally encrypted in simple XOR and just like the file GarminDevice.xml, it's meant to be updated/rewritten on each boot cycle. It can be restored from a backup BIN file however making alterations to a decrypted nonvol BIN then re-encrypting and flashing back seems to fail badly, perhaps quite understandably. You now get the general idea i'm sure.

    Others may be able to give clearer or more detailed explanation if you wish to dive deeper.

  9. #128
    Important User Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,957
    Rep Power
    1273

    Default

    @babj615, finger crossed
    Spoiler: .

    [Only registered and activated users can see links. ]
    Do not PM me with questions. That's what a forum is for.

  10. #129
    Garmin Expert babj615's Avatar
    Join Date
    Sep 2010
    Location
    USA
    Posts
    109
    Rep Power
    55

    Default

    That one was named the same as the last ("new3"), so I named it "new4" (4th attempt).

    This one is almost perfect, the colors are correct, but slightly darker than the original. (may just be the backlight on the device....)

    How did you do this? What do I need to know to duplicate your efforts?
    Last edited by babj615; 14th August 2020 at 12:46 PM.

  11. #130
    Important User Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)Garmin  Logo.bin files (12/13/14xx-37xx-34xx-35xx-22/24/23xx-760-30/40/50-200-2x5w-Montana etc)
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,957
    Rep Power
    1273

    Default

    One more test to get the fact correct
    Spoiler: .

    [Only registered and activated users can see links. ]
    Do not PM me with questions. That's what a forum is for.

 

 

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
  •