Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 32
  1. #21
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    And I don't fix checksum at all, because it works anyway

  2.    Advertissements


  3. #22
    Navigation software expert

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

    Default

    Quote Originally Posted by moddie View Post
    Which is why I use RGN_Tool because it automatically handles the checksum.
    Not always.
    If you wish, you can [Only registered and activated users can see links. ]

  4. #23
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    Here are my patches for disabling the Warning screen for nuviCam and nuvi 34xx.
    The patch for nuviCam was tested and it seems to work fine.
    The idea of the patch is to make the Warning screen timeout very quickly.
    This patch can be also easily applied to StreetPilot APK. Also, moddie, if you look inside the APK you will find why NOP-ing those function calls was a bad idea

    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

    BTW: fw_all.bin's checksums are broken (because fuck you, checksums, that's why!).
    Last edited by kunix; 28th April 2016 at 21:19.

  5. #24
    Garmin/GPS Systems GMod.

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

    Default

    Quote Originally Posted by lolypop000 View Post
    Not always.
    Isn't that just another reason to use an RGN rather than a GCD file because the checksum fix then for sure isn't necessary, also with no gupdate.gcd onboard there's one less file to 'brick' the device if the fw update goes wrong? [speaking as an 'at the coalface' Garmin guy, I'm not a coder as Loly & kunix know].
    '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. #25
    Member
    Join Date
    Apr 2016
    Location
    USA
    Posts
    24
    Rep Power
    48

    Default

    I didn't look closely enough in the APK to see why it would be a bad idea. I'll have to free up some hard drive space before downloading those but I'm guessing you changed the timeout from 0x2710 to 0x1. I thought about doing that earlier today on my 2x5W but I prefer it not displaying at all. I'll still probably try it to see how fast one millisecond looks.

  7. #26
    Navigation software Moderator

    kunix's Avatar
    Join Date
    Sep 2011
    Location
    Belarus
    Posts
    1,041
    Rep Power
    601

    Default

    Why is the thread SOLVED already ? 34xx is not tested I guess.

    moddie, on nuviCam timeout=1 doesn't show any window at all. I expect that 34xx will be similar.
    On those units timeout is probably configurable and I even remember that some file like config.xml or device.xml or OEM.xml is able to change the default timeout.
    Timeout=0xFFFFFFFF has a special meaning. I think it means infinite timeout. But maybe I'm wrong.
    Patching 0x2710 value looks like a nice idea to me, actually, as my patches are kinda complicated to port.

    Concerning NOP-ing, you've NOP-ed the calls to the constructor of the class PageStartupWarning. This doesn't solve anything, because after construction the page is pushed onto the page stack.
    So, we use an unitialized object and the firmware will crash on the first virtual function call, or maybe even sooner.
    Last edited by kunix; 29th April 2016 at 04:58.

  8. #27
    Navigation software expert

    Ellinas's Avatar
    Join Date
    May 2011
    Location
    Hellas
    Posts
    651
    Rep Power
    545

    Default

    Just tried the patch for 34xx in my converted 3790 to 3490 and it works without any Warning screen like nuvicam.
    [Only registered and activated users can see links. ]

  9. #28
    ☼ADMIN☼
    catymag's Avatar
    Join Date
    Nov 2007
    Location
    light side
    Posts
    23,633
    Rep Power
    5325

    Default

    Quote Originally Posted by kunix View Post
    Why is the thread SOLVED already ? 34xx is not tested I guess.
    I tested yesterday night in my 3790->3490 and it worked so I've put it SOLVED.
    [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.

  10. #29
    Member
    Join Date
    Apr 2016
    Location
    USA
    Posts
    24
    Rep Power
    48

    Default

    Quote Originally Posted by kunix View Post
    Patching 0x2710 value looks like a nice idea to me, actually, as my patches are kinda complicated to port.

    Concerning NOP-ing, you've NOP-ed the calls to the constructor of the class PageStartupWarning. This doesn't solve anything, because after construction the page is pushed onto the page stack.
    So, we use an unitialized object and the firmware will crash on the first virtual function call, or maybe even sooner.
    I tried patching 0x2710 on my 2x5W and it did NOT keep the WARNING screen from appearing but it just made it go away in about a second.

    I was able to port your patches to Android Street Pilot app without much difficulty but I'm finding it all but impossible to port to the nuvi 27x7/27x8.

    I understand that using an uninitialized object is bad. However, after lots of time looking over the disassembly, I'm just not seeing how to recognize a constructor of a class.

  11. #30
    Moderator

    flagmax's Avatar
    Join Date
    Jun 2014
    Location
    Ca
    Posts
    609
    Rep Power
    331

    Default

    moddie, just in case you unaware, Streetpilot 2.16 libgarminos.so has function names intact.

    Code:
    Please Login or Register to see the links

 

 
Page 3 of 4 FirstFirst 1234 LastLast

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.