Help Crack NAV Screen Diag PIN Code
Advanced
Joined: May 2010
Posts: 66
Likes: 0
Yes, this is back from the dead. Possible "new" update.
I Google'd a bit and found something interesting from a Camry Hybrid sub-forum:
By analysis, it seems that a certain loading.kwi file may have the override provisions we need. In the case of the Camry owners, it was 5.1. So what they've been doing is making hybrid DVDs to maintain this functionality.
Seeing how we are at version 6, maybe someone can look into previous loading.kwi files and start making hybrid discs. It might be that previous loading.kwi files support some of the Range Rover override codes, etc.
Something to think about.
the only way to find out the version of the kwi file is to open the map dvd on a pc, look at the filesize of the loading.kwi file. if it is anything BUT 46,956kb(or around 45kb - actual size may vary dependant upon the physical disk it is stored on(sector size)), it is NOT a v5.1 file. it is callled a v5.1 file because the 5.1 version of the map dvd data was the version that offered this overide capability. other later versions that were released did not have the same functionality (i.e., versions 6.1, 7.1 and 8.1). hence the modified 8.1 mapdata file with a 5.1 loading.kwi file.
Seeing how we are at version 6, maybe someone can look into previous loading.kwi files and start making hybrid discs. It might be that previous loading.kwi files support some of the Range Rover override codes, etc.
Something to think about.
2nd Gear
Joined: Jan 2010
Posts: 2
Likes: 0
The header includes the strings "rGpaihDc BV 5046" and "91990--4511 :000" which look pretty mysterious until I n-nUxi'd (byte swapped) them, then I get "GraphicD VB 0564" and 1999-04-15 10:00" which make more sense. The GraphicD could mean a lot of things, the VB is ominously suggestive of a certain vendor in Washington (but this is just an image, remember).
Byte-swapped, the string is actually:
Code:
"rGpaihDc BV 5046" "GraphicDB V0564"
2nd Gear
Joined: Jan 2010
Posts: 2
Likes: 0
Progress - LOADING.KWI Denso Nav Toyota/Lexus Gen 4
I've been working on this for a while, on and off on my Lexus. I gave up years ago when I upgraded my nav system to a gen4 toyota which allowed me to use the override menu. That plus lockpick and it solved my problem...until 8.1 data version (which removes the override menu). Since this seems to be the best forum I've seen on taking apart LOADING.KWI, I thought I might post my updates here. My goal is to restore the override menu to 8.1 and above, but perhaps the changes I make could help someone else.
I PMed Buffy but he never got back to me, so I had to start from scratch on some of the stuff he did.
Right now I have extracted the "loading" image for my system, similarly to what Buffy did. I can confirm this is what the system shows when a new disc is inserted.
I have identified 4 separate blocks in the kwi file which represent (I believe) the loading firmware for 4 separate models. I have confirmed that, upon loading said firmware with three of those blocks zeroed out, my car loads the firmware fine. When the fourth is modified in any way, however, my car will not load it (yet!).
I attached my image for fun.
By the way, this is a 400x240 image as Buffy mentioned. I read that the Toyota Nav head units had a res of 400x234, which may explain the black bars at the bottom. Ironically, this file is saved in simple RLE format (and 256 color palette), which results in it taking more space than an uncompressed 256 color BMP file (it requires two bytes per pixel unless a pixel repeats, something that happens pretty rarely on this dithered graphic, whereas a BMP would use one byte per pixel). Not sure I think much of this "GraphicDB" format.
I PMed Buffy but he never got back to me, so I had to start from scratch on some of the stuff he did.
Right now I have extracted the "loading" image for my system, similarly to what Buffy did. I can confirm this is what the system shows when a new disc is inserted.
I have identified 4 separate blocks in the kwi file which represent (I believe) the loading firmware for 4 separate models. I have confirmed that, upon loading said firmware with three of those blocks zeroed out, my car loads the firmware fine. When the fourth is modified in any way, however, my car will not load it (yet!).
I attached my image for fun.
By the way, this is a 400x240 image as Buffy mentioned. I read that the Toyota Nav head units had a res of 400x234, which may explain the black bars at the bottom. Ironically, this file is saved in simple RLE format (and 256 color palette), which results in it taking more space than an uncompressed 256 color BMP file (it requires two bytes per pixel unless a pixel repeats, something that happens pretty rarely on this dithered graphic, whereas a BMP would use one byte per pixel). Not sure I think much of this "GraphicDB" format.
Last edited by adipose; Jun 2, 2010 at 04:01 PM.
