Nav In-Motion Disable Completed, Patch Available!

[Vindes]

I would love to see this go Bye Bye.
Start the car and have the nav screen there up and running would almost be as good as the no in-motion pop up hack

Well, just so everyone's expectations are set appropriately, there are two (really three) pieces to that nag screen.  First there is the warning/disclaimer text that takes up the majority of the screen.  We could eliminate that fairly easily I believe, or modify it to say whatever we want (which lxloon has already done.)

The second piece of that is the "Loading..." bar that pops up underneath while the system is validating the item database, probably probably looking at the voice files and such as well, and doing other misc. initialization.  While we could probably eliminate the "Loading..." bar the Nav part of the unit probably won't function until the process is done.  So I don't think I'd want to remove that.

The third piece is that the "Loading..." bar gets replaced with the "Press ENTER" nag bar when it's all done.  That's really the piece that I suppose everyone wants gone.  I'll take a look for that part of the code and see what we can do.

As for the better patcher...  Yeah, we could definitely use one of those.  Definitely outside my area though.  I don't do visual basic or fancy user interfaces.

[flexion]

vindes, how does the upgrade routine find the version number in the main.apn file?

do we need to parse the ELF headers in order to get the exact offset of the version number? or is there a quicker way to calculate the position?

[lsitter]

Can I simply just copy the NewDVD Folder to a DL DVD or must I do the ISO image thing? Thanks, Lou

BURNING A NEW DVD...



Burn the entire contents of the NewDVD folder to a new double layer DVD. It should have 6 folders and 14 files in the top level directory



There are many ways to do step 8. Personally, I use UltraISO to create an ISO image first, then use Nero to burn that image to disc. You may have other burning software you prefer. I use the two-step process because I could not get Nero to burn a properly formatted DVD otherwise. The REC nav units, or at least mine, is picky about the DVD format.

[Vindes]

vindes, how does the upgrade routine find the version number in the main.apn file?

do we need to parse the ELF headers in order to get the exact offset of the version number? or is there a quicker way to calculate the position?

I thought I had posted info on where the version # is stored in the file, but I guess I didn't.  Or maybe I posted it somewhere else.  Locating it manually, visually, is pretty easy.  Just open the file with a hex editor and jump to the very end of the file, then scan backward a couple hundred bytes.  The version number is stored as a word, with each decimal group a seperate byte.  So you'll see a word as "00 04 02 00", which is how 2.04 is encoded.  In the patched version it'll be "01 04 02 00" for 2.04.01.  It's also pretty easy to locate with code through the ELF header info, but I don't have that off hand.  I'll post it sometime in the next day or so.

The patch file locates it by just going to the exact offsets that need to be changed.  It first verifies that it's working with an unmodified MAIN.APN version 2.04 file by checking the file size and doing a CRC check.

Can I simply just copy the NewDVD Folder to a DL DVD or must I do the ISO image thing? Thanks, Lou

Maybe, depending on your burning program.  There are a lot of ways to burn a DVD.  I've made a number of discs the Nav unit rejects, and from what I can tell the requirements are:
a) Joliet turned OFF
b) Filename format as Windows/Unix
c) ISO 9660 version number ON

That is highly unlikely to be the default format, so however you choose to burn it you'll need to make sure you set those.  I could not find a way to do that with Nero without making an ISO first, but your milage may vary.

[DeepSIX]

lsitter,
You can, but you run the risk of making a coaster. As long as you are sure that the files are correctly applied to the disk. (No extra folders or embedded in a folder)

Vindes,
As for the start-up screen an Auto enter is OK by me. and if possible to select the nav after.
Wow your fast I should stop watching TV also.

[HaTaX]

I would think if the end result would be that we would end up with the map on our screen with no interaction, that would be what people are looking for.   Correct me if I'm wrong on this one...

Now I'm seriously looking at the TvandNav2Go mod for my Nav system... Throw a dvd player in under the passenger seat and get some use out of the damn thing.

[shredder]

Will this work on the REC unit in the Grand Cherokee?  I noticed it was mentioned Chrysler has various folders for different vehicles.

Please say YES! 

[flexion]

Will this work on the REC unit in the Grand Cherokee?

yes, I assume this will work in the cherokee as well, if it is a REC unit. there is also a jeep logo inside the firmware

[flexion]

I thought I had posted info on where the version # is stored in the file, but I guess I didn't.  Or maybe I posted it somewhere else.  Locating it manually, visually, is pretty easy.  Just open the file with a hex editor and jump to the very end of the file, then scan backward a couple hundred bytes. 

yes, with a hex editor it is easy to find near EOF. but I couldnt find any info how to calculate the offset programmatically.. I had a look at your checksum routine, but version number is not mentioned there

I'm asking because I want to find out what it needs to locate the version with a patcher... eg. read ELF header, locate data section offsets.. or parse symbol names etc..

[Vindes]

I thought I had posted info on where the version # is stored in the file, but I guess I didn't.  Or maybe I posted it somewhere else.  Locating it manually, visually, is pretty easy.  Just open the file with a hex editor and jump to the very end of the file, then scan backward a couple hundred bytes. 

yes, with a hex editor it is easy to find near EOF. but I couldnt find any info how to calculate the offset programmatically.. I had a look at your checksum routine, but version number is not mentioned there

I'm asking because I want to find out what it needs to locate the version with a patcher... eg. read ELF header, locate data section offsets.. or parse symbol names etc..

I actually updated the checksum.c program last night so it locates and displays the version number as well.  But I forgot to upload it.  I'll do that tonight when I get home.

If you look at the code for the checksum thing and see how it's locating the checksums in the file, you'll notice that it looks 76 bytes past the end of the section header table.  The version number is 20 bytes past the end of the section headers.  So change the +76 to a +20 and you'll be at the version number.

[flexion]

great! thanks a lot! 

[titan]

As nice as that patch is, I am definitely not going to run it. Not in its current form. I want to see them change the version number BACKWARDS to something less than the AE. That would then work for everyone except people that have already installed and used the AE, which is like 99.5% of people, and still be high enough to replace AD software. That way if you ever wanted to get rid of the unit or go back to regular copies, all you would need was the AE which would have a higher version number and you would be set - it would wipe the old hacked software and make it responsive to all media again.

Why couldn't this have been done for those who had never run AE before and would therefore not have a REC that was updated?  I guess I could do the manual entry rather than using the patch to make the version number one under whatever AE's is, but that stuff confuses a programming dunce like me. 

[Vindes]

As nice as that patch is, I am definitely not going to run it. Not in its current form. I want to see them change the version number BACKWARDS to something less than the AE. That would then work for everyone except people that have already installed and used the AE, which is like 99.5% of people, and still be high enough to replace AD software. That way if you ever wanted to get rid of the unit or go back to regular copies, all you would need was the AE which would have a higher version number and you would be set - it would wipe the old hacked software and make it responsive to all media again.

Certainly a reasonable thought.  My thinking was that the update is only useful to people who already have AE.  Without AE, you don't have the correct files to patch.  And if you already have AE, chances are you've loaded it.

Why couldn't this have been done for those who had never run AE before and would therefore not have a REC that was updated?  I guess I could do the manual entry rather than using the patch to make the version number one under whatever AE's is, but that stuff confuses a programming dunce like me. 

Changing the version number is extremely easy.  If you've acquired a version that you'd like to load, but want to change the version number, there are several people that could give you simple step by step instructions.

And because changing the version number is easy, going back to the unmodified AE version is also easy.  All you'd have to do is start with the stock AE disc and increment the version number to 2.04.02 and you'd be set.

[titan]

As nice as that patch is, I am definitely not going to run it. Not in its current form. I want to see them change the version number BACKWARDS to something less than the AE. That would then work for everyone except people that have already installed and used the AE, which is like 99.5% of people, and still be high enough to replace AD software. That way if you ever wanted to get rid of the unit or go back to regular copies, all you would need was the AE which would have a higher version number and you would be set - it would wipe the old hacked software and make it responsive to all media again.

Certainly a reasonable thought.  My thinking was that the update is only useful to people who already have AE.  Without AE, you don't have the correct files to patch.  And if you already have AE, chances are you've loaded it.

Why couldn't this have been done for those who had never run AE before and would therefore not have a REC that was updated?  I guess I could do the manual entry rather than using the patch to make the version number one under whatever AE's is, but that stuff confuses a programming dunce like me. 

Changing the version number is extremely easy.  If you've acquired a version that you'd like to load, but want to change the version number, there are several people that could give you simple step by step instructions.

And because changing the version number is easy, going back to the unmodified AE version is also easy.  All you'd have to do is start with the stock AE disc and increment the version number to 2.04.02 and you'd be set.

Oh I know all I would have to do is change the version number, but I am saying suppose I decide to part with my REC to get a Pioneer or something, which won't happen but you never know.  I want to be able to stick a stock, original, purchased disc in there and have it work.  I can't very well tell the person buying it that they MUST use a burnt copy which has been modified to allow for its higher version number.  So what I intend to do now is burn the AE disc, patched, as version... lets say .1 below what it is right now.  It was posted in the thread but I would have to go back to find it.  This being the case, if I ever want to go back to an unmodified version, I will just modify the stock AE to still be less than its real version number, but higher than the patched version number so that I will always have wiggle room to go back and forth up until the time I were to potentially part with it, at which point I use the version number of the stock AE disc.

I take it the easiest way for me to patch this will be to, in fact, run the patch.  Then open the file and change the version number back a couple steps to what I want it to be in a hex editor.

[dodgeboy]

As nice as that patch is, I am definitely not going to run it. Not in its current form. I want to see them change the version number BACKWARDS to something less than the AE. That would then work for everyone except people that have already installed and used the AE, which is like 99.5% of people, and still be high enough to replace AD software. That way if you ever wanted to get rid of the unit or go back to regular copies, all you would need was the AE which would have a higher version number and you would be set - it would wipe the old hacked software and make it responsive to all media again.

Certainly a reasonable thought.  My thinking was that the update is only useful to people who already have AE.  Without AE, you don't have the correct files to patch.  And if you already have AE, chances are you've loaded it.

Why couldn't this have been done for those who had never run AE before and would therefore not have a REC that was updated?  I guess I could do the manual entry rather than using the patch to make the version number one under whatever AE's is, but that stuff confuses a programming dunce like me. 

Changing the version number is extremely easy.  If you've acquired a version that you'd like to load, but want to change the version number, there are several people that could give you simple step by step instructions.

And because changing the version number is easy, going back to the unmodified AE version is also easy.  All you'd have to do is start with the stock AE disc and increment the version number to 2.04.02 and you'd be set.

Oh I know all I would have to do is change the version number, but I am saying suppose I decide to part with my REC to get a Pioneer or something, which won't happen but you never know.  I want to be able to stick a stock, original, purchased disc in there and have it work.  I can't very well tell the person buying it that they MUST use a burnt copy which has been modified to allow for its higher version number.  So what I intend to do now is burn the AE disc, patched, as version... lets say .1 below what it is right now.  It was posted in the thread but I would have to go back to find it.  This being the case, if I ever want to go back to an unmodified version, I will just modify the stock AE to still be less than its real version number, but higher than the patched version number so that I will always have wiggle room to go back and forth up until the time I were to potentially part with it, at which point I use the version number of the stock AE disc.

I take it the easiest way for me to patch this will be to, in fact, run the patch.  Then open the file and change the version number back a couple steps to what I want it to be in a hex editor.

FYI - You can put the stock AE disc in and it will work just fine (still in-motion hacked functionality)...  I tried it in mine.  I'd be very impressed if the potential buyer would ever know the difference.

Dave