Page 2 of 5 FirstFirst 12345 LastLast
Results 11 to 20 of 48

Thread: iGuidance Hacks

  1. #11
    Raw Wave justintime's Avatar
    Join Date
    Apr 2005
    Posts
    2,695
    This list is a gem... absolutely great! I have almost all the odball colored stuff corrected now... looks very slick. How on earth did you figure out what is what? Are you peeking in assembly code?
    2002 Honda CR-V
    Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
    Spent so far: $1105.90


    Download the NEXUS Skin for Centrafuse
    ...or even Listen to my music

  2. #12
    Raw Wave justintime's Avatar
    Join Date
    Apr 2005
    Posts
    2,695
    Note that your (2) change in first post (Background color) seems to affect what the application takes for transparency color in the bmp images!
    2002 Honda CR-V
    Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
    Spent so far: $1105.90


    Download the NEXUS Skin for Centrafuse
    ...or even Listen to my music

  3. #13
    Low Bitrate
    Join Date
    Nov 2006
    Location
    Huntsville, AL
    Posts
    73
    Hi JIT,

    I'm now hunting the white colors. I've got well over 400 possibilities here, so it could take some time.

    That said, I've stumbled across the button transparency color: 0x56AC2

    The color at that location defines the button bitmap transparency.

    pb

  4. #14
    Low Bitrate
    Join Date
    Nov 2006
    Location
    Huntsville, AL
    Posts
    73
    Hello all,

    A large number of color locations have been added to the first post. I have also changed the descriptions for some of the existing locations in an attempt to standardize them.

    pb

  5. #15
    Raw Wave justintime's Avatar
    Join Date
    Apr 2005
    Posts
    2,695
    pbarrette deserves huge pat on the back for tremendous effort on this. Thanks man, this is a monster list, and most useful information here!
    2002 Honda CR-V
    Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
    Spent so far: $1105.90


    Download the NEXUS Skin for Centrafuse
    ...or even Listen to my music

  6. #16
    MySQL Error MatrixPC's Avatar
    Join Date
    Sep 2003
    Location
    Beach City, Socal
    Posts
    4,053
    dammmmmmmm perfect.
    Time for more hack.
    2004 Matrix XR A7N8X-VM/400 AMD XP-M 2500+, DS-ATX
    89 Supra Turbo P3 600E@750/Abit BE6 II, Alpine M-BUS Car2PC.
    Y2K Accord Dell GX150
    RoadRunner is the best FE PERIOD
    EmoRebellion is a SCAMMER

  7. #17
    FLAC
    Join Date
    Apr 2005
    Location
    Queens, New York
    Posts
    1,386
    Quote Originally Posted by pbarrette View Post
    Hi All,

    I've been trying to customize iGuidance3 to match my skins in RR and have discovered a few things that I haven't seen mentioned before.
    ----------------------------------------------
    1) Button transparency.
    ----------------------------------------------

    The menu buttons seem to use white (255,255,255) as a transparency color. Any white area will be subtracted from the button image and replaced with the window background color

    The "Favorites" button is an oval surrounded by white:


    But on the menu, the white is the window background color:


    Unfortunately, this doesn't create a transparency area through to the background image. It only allows you to show through to the button area background color.

    ----------------------------------------------
    2) Menu Window Background color.
    ----------------------------------------------

    By default, it's this nasty blueish, offwhite color (231,237,249). Poking around with my hex-editor, I found that I can change it to the dark-grey color you see as the area just outside the "favorites" oval above.

    The address in iGuidanceUMPC.exe is 0x19D89.

    The default color is "E7 ED F9", but you can change it to whatever suits you.

    ----------------------------------------------
    3) Menu Text Background color.
    ----------------------------------------------

    So, you changed the window background color, but now you're left with this problem with the text area background color:


    So, back to the hex editor at 0x1AA3E. Again, change the color to whatever you prefer.

    ----------------------------------------------
    4) Daytime Street Name Color.
    ----------------------------------------------

    I assume that most people reading this have used, or at least seen Purdoom's find regarding the nighttime street name color. Again with the hex-editor, finding the only block containing "A0 FF A0 00" and you end up at offset "0x8412D".

    So, like many people, you want it to be white, so you change it to "FF FF FF 00", but now your daytime street name color is this horrid purple. Well, look just a few characters back, at "0x84126" where you see "60 00 5F FF".

    This is a bit more complex. It seems that the nighttime street-name color is always set from 0x8412D. But the daytime street-name color is set by adding the 0x84126 and 0x8412D together.

    So.. When you change the nighttime color to "FF FF FF 00", you get:
    FF FF FF 00
    + 60 00 50 FF
    -------------
    = 60 00 5E FF

    Keep in mind that RGB values are usually stored as RGBA (alpha). I don't quite understand how iG3 uses that "A" value yet.

    So what's the practical application of this?
    Say we want a "White" night text, but a "Red" day text.

    Find the block that contains "60 00 5F FF 50 81 C1 A0 FF A0 00", and change it to "FF 00 01 FF 50 81 C1 FF FF FF 00".

    "FF 00 01 FF" + "FF FF FF 00" = "FF 00 00 FF" or R(255)-G(0)-B(0)-A(FF).

    Do not mess with the characters in the middle: "50 81 C1". That's the assembly code that is pushing the variables on the stack and adding the two color values together.

    If anyone has any ideas about how the day/night switch is made for these values, please let me know. IE: Why does the color addition only happen for the day street-names, when the assembly code doesn't appear to take that difference into account.
    -------------------------------------------

    Anyway, I hope this helps some of you with your iGuidance customizations.

    ==================================================
    ============ iGuidanceUMPC Color Locations ==============
    ==================================================
    0x1B45 Almanac - "Sun"
    0x1CFB Almanac - "Sunrise"
    0x1DDF Almanac - "Sunset"
    0x1E70 Almanac - "Moon"
    0x1F42 Almanac - "Moon Phase"
    0x2025 Almanac - "Moon Age"
    0x20EF Almanac - "Moon Full"
    0x21BA Almanac - "Moon New"
    0x243D Almanac - "Moon Graphic"
    0x7379 Warning Screen - "OK" Button Text
    0xF68B Map Status Bar - Outline
    0xFBD0 Map Status Bar - "ETA"
    0xFCC4 Map Status Bar - "REM"
    0xFDBD Map Status Bar - "DEST
    0xFE9B Map Status Bar - "SPD"
    0x10952 Map - Top Bar Text
    0x10D20 Map - Distance to Turn
    0x110E7 Map - Bottom Directions Bar
    0x1138C Map - Bottom Directions Bar Text
    0x1195B Map - Menu Button Text
    0x19D89 Dialog Windows - Background Color
    0x1AA3E Dialog Text - Background Color
    0x2AEC1 Current Dest - Avoid Roads - "Nav" Button Text
    0x2AEE8 Current Dest - Avoid Roads - "Avoid" Button Text
    0x2AF12 Current Dest - Avoid Roads - "Clear" Button Text
    0x2AF3C Current Dest - Avoid Roads - "Reset" Button Text
    0x2B929 Current Dest - Avoid Roads - Text Area "Shadow"
    0x2BA2A Current Dest - Avoid Roads - Highlighted
    0x2BA41 Current Dest - Avoid Roads - Highlighted Text
    0x2BA4D Current Dest - Avoid Roads - Not Selected
    0x2C1E9 City Select OSK - "OK" Button Text
    0x2C295 City Select OSK - "DEL" Button Text
    0x2C8A6 City Select OSK - Top Area Background
    0x2EA6A Current Loc - Text Area "Shadow"
    0x2EC69 Current Loc - "Save" Button Text
    0x2FB7E Current Dest - Detour - "Distance to Avoid"
    0x2FE8A Current Dest - Detour - "2 mi" Button Text
    0x2FEB1 Current Dest - Detour - "45 mi" Button Text
    0x2FEDB Current Dest - Detour - "91 mi" Button Text
    0x2FF05 Current Dest - Detour - "Reset" Button Text
    0x30DD0 Current Dest - Button Background
    0x32CF8 Destination - Address Input - State Name
    0x32E31 Destination - Address Input - "Change State" Button Text
    0x32E53 Destination - Address Input - "City First" Button Text
    0x331E1 Destination - "Current Destination"
    0x334A7 Destination - "Demo" Button Text
    0x334C9 Destination - "Avoid Road" Button Text
    0x334F3 Destination - "Stop Over" Button Text
    0x3351D Destination - "Detour" Button Text
    0x33547 Destination - "Clear Route" Button Text
    0x35A2F Menu - "Destination" Button Text
    0x35A51 Menu - "Itinerary" Button Text
    0x35A7B Menu - "Shortcuts" Button Text
    0x35ACC Menu - "Settings" Button Text
    0x35B74 Menu - "Volume" Button Text
    0x35B87 Menu - "System Info" Button Text
    0x3ADF0 State Select OSK - "OK" Button Text
    0x3AE9C State Select OSK - "DEL" Button Text
    0x52503 Most Non-OSK Item Highlights
    0x56AC2 Button Transparency
    0x5AD40 GPS Info - Text Background
    0x5E5A4 OSK - Highlighted Item
    0x5E5AC OSK - Highlighted Item Text
    0x5E5BF OSK - Non-Highlighted Items Background
    0x62A16 Left side Guidance Bar
    0x62A47 Right side Guidance Bar
    0x62A7F Bottom Guidance Status Bar
    0x64240 POI OSK - "OK" Button Text
    0x642EC POI OSK - "DEL" Button Text
    0x6A307 POI - State Name
    0x6A3C4 POI - Distance
    0x6CAD1 Route List Highlighted Item
    0x6E6E6 Street Name OSK - "OK" Button Text
    0x6E792 Street Name OSK - "DEL" Button Text
    0x7184A Speed Alert Keypad - "DEL" Button Text
    0x71F41 Speed Alert Keypad - "OK" Button Text
    0x7507C Settings->Options - Small Buttons Text
    0x76A89 Trip Info - Text
    0x78711 OSK - Top-Bar Text
    0x84126 Map - Daytime Street Name Color (see above)
    ==================================================

    pb
    Well after reading this post...It seems very interesting. But what are you using to hack into iguidance? It says u are using a hex editor? I was using my hex editor and trying to figure this out but failed... What hex editor are you using?
    2002 Mitsubishi Galant
    Progress: 90% [-▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓- ->

    Carputer Specs:
    Via M10K
    512mb Ram
    60GB HDD
    Souund Blaster Audigy2 NX
    OPUS ITX PC Case


  8. #18
    Raw Wave justintime's Avatar
    Join Date
    Apr 2005
    Posts
    2,695
    I use vi32
    2002 Honda CR-V
    Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
    Spent so far: $1105.90


    Download the NEXUS Skin for Centrafuse
    ...or even Listen to my music

  9. #19
    Raw Wave justintime's Avatar
    Join Date
    Apr 2005
    Posts
    2,695
    Pbarrette:
    There are 2 texts I am still trying to change the color...

    1) The address of the current destination (not the 'Current Destination' text, but the actual address that is below it.

    2) The text that says: "Continue to Final Destination?" as well as the address that appears right below it.

    I hope you can find those 2!!
    2002 Honda CR-V
    Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
    Spent so far: $1105.90


    Download the NEXUS Skin for Centrafuse
    ...or even Listen to my music

  10. #20
    Low Bitrate
    Join Date
    Nov 2006
    Location
    Huntsville, AL
    Posts
    73
    Hi Cheekz,

    First, let me say that quoting my entire post is overkill to the extreme, plus doubles the image requests to my web server. At least edit your post to remove the images from my quotes. Thanks.

    Now.. I use WinHex as my hex editor, but that's just personal preference. You can use any hex editor that you are comfortable with. Xvi32 is free and decent, but I prefer the way WinHex separates each row into two blocks of 8 bytes. I also like the "Position Manager" which is like xvi32's bookmarks, only more manageable.

    I also know that with 32bit software, colors are usually stored as 8 byte DWORDs, normally in RGBA format. So if I want to find the color "blue", I just start searching for values that appear as "00 00 FF 00". Looking for yellow? How about "FF FF 00 00"?

    Once I've found a possible color location, I replace it with something recognizable. For iGuidance, I haven't seen any bright purple, so I replace it with "FF 00 FF 00". Then I save the changes, start up iGuidance and hunt through the menus and screens for any purple. It's really a very tedious process.

    Yesterday, I finally gave in and downloaded AutoIt. I built a quick and dirty script to hit up a limited set of menus that seem to contain all (or at least most) of the GUI elements. As the script hits up each menu, I have it scan the screen for purple pixels, then stop when it finds any.

    Unfortunately for me, I found that there are a crapload of possible "white" color value locations. Most of the valid ones seem to start with a push to stack instruction (0x68) but there are 383 of those locations alone. So searching for "68 FF FF FF 00" reduces the hunt from 1305 locations with "FF FF FF 00" alone. Of course, the problem is that at least some of the remaining 922 locations without a preceding 0x68 also contain colors that are displayed in the GUI.

    So lately I've been cheating a bit. If you can call it cheating anyway. I disassembled iGuidanceUMPC using IDA Pro. I've already got a decent sized list of valid color locations, so I can see that some patterns have emerged. Like, damned near all of the color values related to the "Current Destination" screens are located between 0x2AEC1 and 0x30DD0.

    So now I can jump to 0x1AA3E in IDA, since it's the last known color location before the "Current Destination" stuff. Then I hunt through the assembly code for anything that looks like a static DWORD value from there until 0x32CF8 (the first known location after the current-dest stuff).

    Still, it's all a very tedious process.

    The daytime-street-name color discovery was almost accidental. I changed the nighttime value to "FF FF FF 00" and discovered the daytime color became a nasty purple. I took a screenshot to determine the actual shade of purple was "5F 00 5F".

    So I figured that the location had to be near the nighttime value and started looking. I found the "60 00 5F 00" value in the hex almost immediately and figured it's probably close enough considering that the street-name text is anti-aliased. I changed the value and the daytime color changed as well, but not to what I had expected.

    So then I had look up the 80x86 opcode instructions and discovered the values were being added. I should have disassembled in IDA at that point, because it's a lot more obvious in assembly.

    pb

Page 2 of 5 FirstFirst 12345 LastLast

Similar Threads

  1. Replies: 570
    Last Post: 11-05-2009, 02:49 PM
  2. How to setup iGuidance GPS for RoadRunner
    By MatrixPC in forum RR FAQ
    Replies: 31
    Last Post: 05-22-2009, 08:29 AM
  3. Replies: 17
    Last Post: 06-15-2006, 12:46 AM
  4. iGuidance Font Size Fix summary thread
    By Viscouse in forum GPS
    Replies: 29
    Last Post: 03-28-2006, 06:21 PM
  5. 25 lost hacks
    By P3rv3rt B3ar in forum General MP3Car Discussion
    Replies: 8
    Last Post: 10-25-2005, 12:34 PM

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
  •