Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 15 of 24 FirstFirst ... 51314151617 ... LastLast
Results 141 to 150 of 235
  1. #141
    Navigation software Moderator kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    908
    Rep Power
    438

    Default

    @turboccc
    Look at this: [Only registered and activated users can see links. ]
    I don't know when the signature was introduced.
    And I don't share your optimism because Garmin can easily sign everything and even on old devices. Then we will be flashing firmwares through broken IMG files causing buffer overflows. Notice that buffer overflows are not easy on ARM because of existence of I-cache and D-cache.
    Then also we will have to forget about cure firmwares.
    As for me, I'm already suffering from the signature because I need flawless and easy update of patched firmwares.

    @lolypop000
    If you could break properly implemented digital signatures you'd already be a famous cryptographer.
    Last edited by kunix; 2nd December 2011 at 08:19 PM.

  2.    Advertissements


  3. #142
    turboccc
    Guest

    Default

    Whoa! It is not a signature, its a full book! LOL! I think I have seen this in the past, but I thought it was some garbage at the end of the file. I compared 34xx v350 with v360 and it is a very different garbage which does not even look like garbage. So it may well be a 256-byte signature.

    If you have seen it in the dissasembly, that just means we need to bypass it in the boot.bin or X-loader.bin, right? Have you tried to do so and flash a gcd without the signature? Or, do you need to flash the modified boot.bin first with updater.exe before you can update with a regular gcd?

  4. #143
    Navigation software Moderator kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    908
    Rep Power
    438

    Default

    The signature is checked in fw_all.bin before running boot.bin from the GCD file.

  5. #144
    Navigation software expert Convert 3790/3760/3750 to 3490
    Convert 3790/3760/3750 to 3490Convert 3790/3760/3750 to 3490Convert 3790/3760/3750 to 3490
    Giomen's Avatar
    Join Date
    Apr 2009
    Location
    Suomi-Russia
    Age
    56
    Posts
    2,155
    Rep Power
    684

    Default

    Quote Originally Posted by kunix View Post
    I have to say that due to our 'efforts' Garmin has started to protect their devices from flashing patched firmwares. In particular, GCDs for nuvi 24xx, 34xx, 30, 40, 50 are digitally signed.
    It is nine days news! As long ago as this summer I read the one of Garmin bulletin about new 2012 series of Nuvis at one of Western Europe distributor. Garmin declare in it what new series will more closed in variant of SW modification by functions. Also Garmin ask to report about all "modified" device that detect in service points. Especially Garmin ask to indicate the seller of such device. And so on...

    Kunix! You are not citizen of advanced capitalist country and so must know about real illegal market of software and hardware in your countries. I think our forum is a little bit of Garmin problems. They deal with a frank criminal sellers in much more size. Welcome to East, the brother Garmin, what could i say...
    Last edited by Giomen; 3rd December 2011 at 02:05 AM.
    Garmin, how much is 30 pieces of silver for Judas today? Were they worthy for crucifix of GPSPower?

  6. #145
    Senior Member
    Join Date
    Oct 2010
    Location
    Oz
    Posts
    114
    Rep Power
    26

    Default

    After reading thread here seems I would need to reflash 37xx logo if I converted to 34xx and wanted to go back to 37xx.
    So using 37xx boot.bin (extracted from GUPDATE.GCD version 4.6), I did following to create a rgn file to allow return to 3790 logo.
    Opened Region Tool (84) and loaded boot.bin (from 37xx 460 version) then loaded logo.bin (37xx from turboccc post on how to change logo) then saved file as 37xx_460_logo_hid1101.rgn.

    Surprised to see that the logo.bin file size for 37xx in RgnTool was 3145728 compared to only 10281 for 34xx logo bin. Does this sound right or did I screw up logo somehow?

  7. #146
    turboccc
    Guest

    Default

    Logo in 37xx is a 800x480 image in a 1024x512 frame. LOgo in a 34xx is a 800x480 image in a 800x480 frame. Yes, logo in 37xx sh9ould be bigger than the logo in a 34xx but the size on your 37xx is way to high. Replace logo with GIR_Editor then check the final size of the logo.bin. There should not be that much difference.

  8. #147
    Senior Member
    Join Date
    Oct 2010
    Location
    Oz
    Posts
    114
    Rep Power
    26

    Default

    @turboccc
    37xx logo.bin size in gir editor is 10604 bytes, resolution 1024x512 (double clicked on opened file for details). Looks ok in preview 800x480 inside frame.
    Now when I import this bin file into region tool section is 1005 and size is 3145728...
    Just not sure why the 34xx is so much smaller file size.

    Edit 1
    Uhmmm.... maybe because 37xx logo.bin is 3MB and 34xx logo.bin is 11KB!! I find I have two 34xx logo bins and one is same size as 37xx logo and other is VERY small. Both look ok in GIReditor though.
    Last edited by fringe; 3rd December 2011 at 08:04 AM.

  9. #148
    Kanopus
    Guest

    Default

    Logo with 3MB size is a direct dump form nuvi memory. You can remove trailing FF from it. Maybe GIR_editor could have an option for truncating bin file?

  10. #149
    turboccc
    Guest

    Default

    I think GIR_Editor already cleans the trailing FF, no? It rings a bell, but I am not sure. Maybe if you just extract the logo and replace it, it will.

  11. #150
    Senior Member
    Join Date
    Oct 2010
    Location
    Oz
    Posts
    114
    Rep Power
    26

    Default

    @turboccc and Kanopus
    I opened the 3MB logo and edited file by loading the tmp.png auto generated by gir editor as the new logo. Saved the result and the new file size is only 11KB. Sound like the 'truncating' has been carried out by Gir Editor.
    At least now I am not concerned at the large discrepancy in logo file sizes. Clearly some logo files had been truncated and some not.

 

 

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
  •