Editing Splash Screen on V26-09a Beta
 

Hello everyone,

I'm hoping with the help of some rudimentary HEX editing to change the beta splash screen to either the original splash screen or a new one I have made in Photoshop..

Stay tuned! Hopefully it won't blow up in my face!

I've managed to find the original embedded image that we are seeing:


Paul Martin
Australia

I'm hoping to replace it with this

:)

Paul Martin
Australia

OK... I've just burnt the v26.09A (with my logo modification) and I'm about to go out and test it. Will report back...

Paul Martin
Australia

Not quite!

It rebooted, started installing... the progress bar got to the end and then it said there was an error.

I think I know why this is the case - the image I'm inserting into the file is larger than the 26.09A image.

The 26.09A image is 4,536 bytes
My image is 11,325 bytes

I don't think it is a simple matter of substituting the images within the file. It is in the file called NAVBOOT in the following folder:
V_2\RR\0101\BMWC01S\app_sw

There must be some sort of checksum or something... I don't know. I'll fiddle for a little bit more but I'm almost at the end of my technical abilities!

Paul Martin
Australia

So close and yet so far...

This is how I did it (for anyone that may know how to pull this off...)

Using a HEX editor (HEX Workshop v4.2), I opened each file in the v26.09A CD image file, searching for the text string 'GIF89a' which is the header for the splash screen image.

Having this small update, rather than a full CD, helped narrow down the file that contained the splash screen.

The 'trailer' for a GIF file is the first HEX value equaling '00 3B' that comes after the 'header'. This is how you can isolate embedded GIF files - and indeed how I got the GIF file showing '26.09A' above. It is ripped directly from the HEX editor.

A few files had images in them, but only the NAVBOOT file (located in \V_2\RR\0101\BMWC01S\app_sw\) had the splash screen. The other images were much smaller and were related to other aspects of the navigation system.

I selected the appropriate GIF 'chunk' and pasted my new GIF image into its place (I created the GIF file in Photoshop and then opened it in the HEX editor)

I have tried a few different images and all of them have failed to install (the navigation computer gives an error and promptly switches off!)
I've tried a larger image and a smaller image with no success. It is almost impossible to get the image size 'exactly' the same and I'm tired of trying.

Hopefully this information may be of some use to someone who knows more about HEX editing and compiling than I do (I'm a doctor in my day job!).

Even after all of this messing around, placing v26 back into the navigation computer gets me right back to where I was before, so no harm done!

I hope someone here can change that image!

Cheers,

Paul Martin
Australia

It'd be very cool if you could customize the splash screen.

I think your conclusion is logical: almost any installer on any system uses checksums to ensure the data that is to be installed is correct. So we need to find the location of those checksums.

Hope you will be successful.

Edit: I composed my message while you posted your last message. I don't think that the size of the image matters (maybe the dimension). There must be somewhere a receipt file for the installer that has the checksums for the various files that will be installed. If one changes the boot screen, the corresponding checksum for that file must be changed accordingly.

This is only my guess, and the kind of checksum is also unknown.

Good to hear that you can downgrade to v26 without any problem. I think I will try the beta this weekend... :-)

Nice endeavor, hope you complete this. Good luck!

I just noticed that you use a transparent color in the new splash screen.

Maybe that's another source for errors?

Paul - nice work. I'm keeping my fingers crossed that you can get this figured out :thumbup:

Paul - don't give up man, you're off to a great start! I love your idea!! Perhaps now that daylight is slowly beginning to sweep across the US, one of our coding geniuses will be able to help you out! Thanks for trying!

Once you make this amazing thing work let us know. I'm sure there will be a 1000 requests for custom splash screens :)

Hey Paul, I was just thinking. There must be something in the code that tells the logo where to position itself on the screen and maybe if you don't give it that info it doesn't know what to do with it and causes the error. - just a thought, I'm certainly no code guy...

i edited the navboot file now with a individual startlogo. but i am not able to burn a cd. all burn-modi that i try with nero7 are not accepted at my MK4. actually i throw 11 cd into trash :(

did anyone burn successfully a software-cd that is readable by the MK4?

please send infos about the burning-software and the burn-modus.

thx

Hi,
I wrote a program with which you can extract and exchange the gif images from the navi software:
GifExtractor
The exchange works flawless but I didn't upgrade my navi system with the patched files.

You have to edit the following file:
\V_2\RR\0101\BMWC01S\app_sw\navboot

I will keep you updated.

Tino

Hmmm... that should not have been an issue. Myself and some others have been trying to add custom logos and have a different problem which I will explain at the end.

First I used a CD image editor (UltraISO) to open "Mk4 3D.mdf". I then navigate to the file NAV_SW/V_2/RR/0101/BMWC01S/app_sw/navboot. I renamed "navboot" to "navboot_BACKUP" and then I extracted it to my desktop.

I used a hex editor (Cygnus Free Editor) to open the desktop file "navboot_BACKUP" and scrolled down to the beginning of the GIF89a used as the "T 26.09A" startup logo (address: 00B1FE84-00B21D8F) and cut the code to a new Hex page where I pasted it and saved it to my deskto as BMWLOGO.

I then used a graphics editor (CorelXARA) to edit this:

Attachment 5159

to this...

Attachment 5160

making certain to retain the original GIFs properties:

400x234 pixels
96x96 dpi
bit depth of 8
1 frame
GIF89a file type

and saved it as BMWLOGO2.

I opened the new logo in the hex editor copied the code, then opened navboot_BACKUP and pasted the code at address 00B1FE84. Then I saved the file as "navboot".

I then used CD image editor (UltraISO) to re-open "Mk4 3D.mdf". I then navigate to the file NAV_SW/V_2/RR/0101/BMWC01S/app_sw/ and added the newly created navboot file to the directory and saved the image.

Using Alcohol 120 I burnt a CD and proceeded to the X for install. CD boot install routine ran... progress 100% at which point I received (5 times) an installation failure message as did the guys at RoadFly and BimmerBoard. The screen goes blank and you can not view any menu ites, though of course the radio still works.

*Note: By placing the original unadulterated Beta CD in drive, the Nav will restore itself.

So, I am temporarily stumped. If anyone has any ideas, I anxiously await to hear them as I can not have my buddy (who owns an Acura) walking around with custom nav logo while I have monochrome number displayed :) My current attempt involves trying to get my logo precisely (exact address numbers) the same size as the original... will update you when done.

-RSZ

Thanks Tino
 

Looks like while I was entering my post Tino produced the answer. Nice work Tino!!! Okay school me. What did I do wrong???

I'm curious what happens if you extract the original image and then put that same exact image back in and burn it. Does it still work, or do you have the same issue as the custom image? :dunno:

If you still have the same problem then the issue isn't the custom logo, it's something with the extract and reinsert process (or some other hidden trigger)

I am going to give that a try. But man if Tino's app work... WOW! Working with it now... it is so easy... I intend to customize the circle cursor to an X5 as well.

If you DO get that working, will you post up a copy of the whole download with a more generic splash screen too please? Something like the Roundel with "the Ultimate Driving Machine" underneat it - and nothing else?

I'm sure so many of us would appreciate it!

THe reason why you can't simply replace the Gif89a image in the navboot file and expect it to work is simple... BMW will have employed a checksum mechanism to ensure that the sat nav computer doesn't try and install software that it thinks may be corrupt..

What I'd suggest you need to try and do to maintain the correct checksum, is for the original GIF image in thh navboot file total up the bytes..

Say the original image is 30kb in length... Total each and every byte within that 30Kb.. Say that gives you a number like 236553434..

Now when replacing the original image in the navboot file with a replacement one, ensure that the replacement image is smaller than the original GIF image..and use the difference in size between the original image and the replacement image to correct the checksum..

e.g. if original image was 30Kb, and your replacement image is 25Kb, then the checksum over the original 30Kb of data, where 25Kb is now your new image, will not equal the original checksum of 236553434

so from the end of your replacement image data which is 25Kb in size you have 5Kb of spare data with which to correct the checksum..

So total up the 30Kb of data where the original image data (30Kb) was, but your replacement image data (25Kb) is now in place, and you'll get a different checksum e.g. 223553001

In my examples, the different between the original check sum, and the new checksum is 13000433.. So you'll need to modify the data in the spare 5Kb after your replacement image, to ensure that the checksum of the 30Kb is the same as the original checksum..basically increasing the values as necessary in the 5Kb of data

So far instance if the first byte of the spare 5Kb of data is a 0, then if you change it to a 255, then your 255 nearer to the correct checksum..keep doing this over the 5Kb of data until the original checksum for the 30kb is reached..

Hope that all makes sense...

NavMan

I also thought about that. But unless I know how they create the checksum, I cannot reproduce it.
The most simple would be XOR but there is also CRC etc.

I guess without further inside info we are screwed or can just try.
My program replaces the images very exactly. So if someone can exchange the image with a smaller one (filesize) and it works, then we know that there is no checksum.
With bigger file is always the risk to "disturb" the bytes of the next file.

In my experiments, I tried to change 7 bytes in the logo part of navboot (just for testing checksum existance). After that Paint opened the logo (copied from navboot), but navi writes about error during update. I think, checksum control exists.

@DaRkY
Which bytes did you change? Did you check if the image was still valid?
Paint opened it but that doesn't anything since it might repair the file.
Best way would be to replace it with a smaller valid file.

I uploaded an altered navboot here:
www.carmes.de/download/software/navboot
Maybe someone can try that.

Tino

I think, that checksum calculating is not so easy:( For example, checksum of 1 FF byte file is 3045181057, and checksum of 1 FE byte file is 1738016605.

If we know where the checksum is and how it is calculated. We just calculate it for the altered navboot.
But that need more inside information or luck finding it ;)

I have the same issue, how did you solve it? thanks

Why dont we extract the original BMW image used on the MK IV navs and see if that works... and then go from there

Bytes was in the centre of gif. I'll chek it with Paint. It is sensitive to the file format. It did not open edited files, that other progs opened.
Diferense between files I must fill with 00?

I can do it only tomorrow:(

I thought, that checksum calculating method is the same for all files. I'm a newbie in it.

Yes. But my program does it automatically when you insert a smaller image.

No, there are many ways. CRC32 is the most common and quite safe.
XOR is very easy and just used for smaller codes like the IBus/KBus communication.

Paul- I along with everyone else here applaud your efforts and your methods!

JV

I can't run your program:( It writes, that there is an error during initialization (0xc0000135). Maybe I don't have some library?

I don't know, how this calculating works.
Is there any possibility to make a logo, that have an equal checksum with the original logo? Or there are no deal in this, because checksum of navboot changes even if we paste a gif with right checksum?

Great stuff with this gif-extractor! But why doesn't it extract the MINI-Logo?

I think it has somethiing to do with checksum. May be have to edit the file that reads the checksum for the new checksum. :dunno:
Thanks Paul for your efforts. :bow:

@Darky
Please load the newest version of my program and be sure .NET Framework 1.1 is installed.

Just replacing the image with the same image won't change the checksum since no byte changes.
But unless we know which method is used to calculate the checksum we can't do anything.

Sorry yes, I should have realised, that if the checksum is calculated by XORing, then my idea of just altering the spare space after the replacement GIF data won't work.. we would need inside info for that..

Can someone do a test... Alter one byte in the original GIF, and add one to it, then take another byte from the original GIF, and subtract one from it.. If when burnt to disc, the update goes OK, the the checksum is a simple totaling of the bytes in the file, and therefore my original idea could be used..

NavMan

It's almost certain that there will be some sort of checksum on the data uploaded to the nav computer. It's very likly that this will be written at the end of one of the files. The best way of finding this would be to try and work out the checksum on the origional unaltered file in various ways and see if you can find a match for that value. Once you know how to calculate the check sum and where it is, the rest should be easy! :)

It appears that Tino's CarMES points to a different GIF (00B438C8) than the one I was modifying at 00B1FE84-00B21D8F. Let me see if modifying this one instead makes a difference.

Wow... it's almost half the size of the file I have been working on.

OK...

I've used Tino's excellent application (see his post in the other thread - http://www.xoutpost.com/101854-post105.html)

...and I've noticed that there are TWO identical splash screens embedded within the NAVBOOT file - maybe the checksum is as simple as having inserted two identical images??

One at B1FE84-B21044
One at B438C8-B44A88

Both have lengths of 4544 (HEX length = 11C0)

I'll try this out later today (unless someone beats me to it!)

Is it possible to bring splash screen discussion to this thread so it is all in one place?

Paul Martin
Australia

Good Work RealShakaZulu, I've found this too - and GREAT WORK Tino! Makes extraction easier!

See my post in this thread (Splash Screen - http://www.xoutpost.com/navigation-sy...sh-screen.html)

What if we just make sure that BOTH images are the same? Maybe the checksum is nothing more than making sure both images are identical?

Could we move Splash Screen discussion to the other thread to keep the topics organised? What do you think? (SEEMS TO HAVE BEEN DONE! THANKS :D)

Paul Martin
Australia

Okay so here's the challenge now... it took me almost a 1/2 hour to create the BMW logo as no stock image was large enough yet simple enough to meet the new smaller image size restriction. So I am taking this GIF

Attachment 5167

and inserting it twice... off to the burner and then the X.

sure paul-- anything we can do to help!

Now that would be totally off the hook if you can make that work :wow:

NO LUCK... created another coaster... "An Error Occurred During Programming!"

No, that didn't work. Same error on attempting the update.

The 'official' T26.09A takes 20 seconds after the progress bar has finished before it states that the installation was successful. All my modified files take much longer (in the order of a minute) and they all fail.

Now... we just need to find that checksum.

Paul Martin
Australia

I wish I was a programmer. I can understand the concept but can't help with the hacking, I mean editing :) .
So, good luck guys. I'll be waiting like the rest of us. :thumbup:

I would bet the Checksum would have a file creation date the same as the navboot file

Only a few files do
GSW_tools
lng_rel.tbl
loader.ini
lowboot
sw_rel_tbl

Now lowboot was the last file created and logically would contain the checksum.

Cruzing thru the lowboot file dec location 413417 shows the Error File %s Size %u does not match chain size of %d x %d bytes

I searched for %d and found the following at dec location 395201

Check CRC Valid modules in bootfile %d size 0x%x -> 0x%x

My guess is that you smart guys can modify the lowboot file to either remove the checksum or modifiy as needed

Also note that I have found CheckCRC=%d

Alrighty then... based on the above and

"A Cyclic Redundancy Check performs a mathematical calculation on a block of data and returns a number that represents the content and organization of that data. The idea is to have the CRC return a number that uniquely identifies the data. You can think of CRC as being the operation that generates a "fingerprint" for a block of data. The actual number, or fingerprint, that is used to identify the data is called a checksum.

The CRC is calculated by performing a modulo 2 division of the data by a generator polynomial and recording the remainder after division."

swapping the images is out and coding is definitely in order... off to the lab.

Just took a look at the old V26 "navboot" and ran Gifextractor against it. It only contained a single version of the "BMW" logo. The new V26.09A has two of the T26.09A just an observation I made. It probably doesn't help with the checksum issue.

Keep up the great work guys :thumbup:

Instead of trying to change the screen. Why don't you try to change a boring bit of text emedded in the navboot file.

Make it a very minor change. And then see if that is loaded ok i.e just swap one letter.

If this is rejected it shows the whole file is CRC checked somewhere. If it isn't rejected then either its just the gif thats CRCed or something more fundamental with the gif swapping.

It might help narrow down the search.

yea, the other logo seems to be the mini logo.

I think the loader.ini may actually have the CRC checksum, as I found this in dec location 1508209.

To set %s to %s with file checking on %s path, type bootmon -ax %s

After reading this we might be able to just turn the checksum OFF

Man, this is better than watching "24"

Keep up the great work guys!!!

I think y'all should put the dilithium crystals in the pseudoscillogism and excommunicate the redundancies in the biosphere as supercalifragilisticexpealadociously as y'all can.

Keep up the good work, everybody. I can barely type, so I'll just stay off to the side here and cheer.

JV

:iagree:

Okay, so I modified the original V26.09a navboot file so that it has the OEM splash logo. I made sure that the original file and the new file were identical. Next, using my hex editor I did a "CRC16/32 of file/block" calculation on the original and modified files and surprisingly they return identical values.

Next step is to slow burn the image using DVD Decrypter (preference thing, I hate Alcohol120%) I'll save that for tomorrow, kinda tired :yawn:

Keep my fingers crossed. Not quite there yet folks, you gotta hand it to the X5World braintrust :bow:

Good plan...

Tried the following with no luck (same error)
- changed 2 bytes (2 characters) in the middle of the GIF logo file embedded in NAVBOOT - ie. same filesize
- ensured that the NAVBOOT datestamp was exactly the same (to the second)

The good news is that when it fails, all you have to do is put the 'official' CD of v26.09A into the Navigation Computer and it installs & functions properly. This saves having to go back to v26 and then do the 'update'.

If we do find out how to get it to work I would think that we could have virtually any splash screen we like. Clearly file size is not the issue as this 'T 26.09A' image is much smaller than the '==BMW==' image (and the colour table is different too).

Paul Martin
Australia
www.paulnika.com

this suspense is INTENSE!

Hope this helps........

I have been analyzing the files.

All the data files (programmes), appear to be derived from C or C++. So I dont think we can simply recode to avoid the checksum...that would be bad!

Anyhow ALL the files end 00xx xx xx. ie the last 3 bytes of the file apper to be the check sum.

This represent not a 16 bit or 32 bit checksum but a 24 bit checksum!

Having a wander around the web I did find a reference to the fact that OS-9 does use 24 bit CRC checking.

Therefore to me me it looks like the navboot files checksum is the last 3 bytes of the file itself.....

now all I have to do is to find a 24bit CRC calculator!

Good huntin'

Altered 'navboot' with corrected CRC-24 uploaded to:
http://rapidshare.de/files/13622411/navboot.rar.html

Need to test it.

Is anyone knows a type of processor, used in MK4? I think, it's some kind of MIPS processor. I found a page with a variety of MIPS emulators and debuggers here http://www.linux-mips.org/wiki/Emulators Maybe it can help us?

It worked in my upgrade. Good Job. Cute logo.

So process is as follows, swap logo, adjust last 3 bytes of file with new 24 bit checksum. That means we can change anything we would like in that file

http://www.bimmerboard.com/members/a...l/logohack.jpg

magic iso replace the navboot file
Alcohol 120 modify the lead out to match the image

now lets figure out the bit to flip to turn on OFF ROAD GUIDENCE!

http://www.bimmerboard.com/forums/posts/139364/
http://www.bimmerboard.com/members/a...l/DSCF0617.JPG
http://www.bimmerboard.com/members/a...l/DSCF0622.JPG
http://www.bimmerboard.com/members/a...l/DSCF0626.JPG

Hi,

i have changed the sw_rel.tbl file on the T26.09a cd to the original V26 sw_rel.tbl file. All other file is original from T26.09a, and not modified. Result: after loadig original BMW logo and 4-1-60 Software Version in Set menü ! But no Birdview option.

Janos

what do you use to calculate the 24 bit checksum??

so you would change the last three bytes with this #? is that in hex then???

thanks a lot guys!

Cool.

What software are you using to work out the 24bit CRC checksum?

Rgds

Here is a free one http://www.jonelo.de/java/jacksum/

I think this is a smarter approach. Using V26 software we should just enable the features we are looking for

Martin

can u comment how this program calculates checksum?

it takes file ? excludes last 3 bytes ? calculates crc 24 and writes checksum to the end of file in place of excluded ones?

or it calculates checksum on all file?

thanks

I like this stuff. Reverse engineering at its best. :thumbup:

I've got the jacksum working, but the problem I have is if I take the navboot file, remove the the last 3 bytes, then pass it through the jacksum app. I get a different checksum to what is in the file.

So the question is: what part of the navboot file do you chop from the file before passing it through jacksum?

I hope you understand....cos I only just do!

can someone post a clone cd or iso image of the 26.09a update with the plain jane mkiv ===bmw=== logo? you'd be my hero. i know just enough hex to screw up my nav drive, i'm sure.

thanks

Okay boys I'm one step closer I haven't tried it yet. Seems as though somethings have transpired overnight and I had to do some research. Anywho, thanks to "ambishop" for pointing me to jacksum. I have indeed verifed the checksum on my hacked version of "navboot" and the original V26 file. They are indeed identical. Now the testing begins.

Off to my car. I'll report back as soon as I can. Pray for me folks :)

We're praying beedeeman!!!! You reverse engineers rock! This is better than watching 24!

:bow: :bow: :bow: :bow: :bow: :bow: :bow: :bow: :bow: :bow: :bow: :bow: :bow:

2Wires, if the method of "checksum" is discovered, could you introduce the code in your GifExtractor (http://http://carmes.de/download/sof...Extractor.exe) to correct it and make the process of change logos more easy?

Sorry for entering the party so late !!!
 

Since it seems I was the one that originally started this craze, it's only fair that I answer.

Here are a few notes, speaking from personal trials (yes, I was brave enough to try on my OWN nav computer)

1) No, you cannot "permanently" screw up your nav computer with a corrupt image. If you screw up the checksum with an invalid GIF89a image, the disc will either NOT boot, or will boot and hang during the middle of the install

2) Dont panic, turn the car off. If you have a video module, when you turn the car back on, you'll have a very rudimentary main menu. Eject the disc from the nav computer, and insert a FRESH copy of v26. Give it a few MINUTES (not seconds). It will eventually boot and load the fresh copy of v26 back onto the computer. Then you're free to go back into the house and continue hacking the OS LOL

DISCLAIMER: Just because I've flashed mine about a ZILLION times and not killed it, doesn't mean you'll do the same LOL

Now, for the other news.

I have NOT changed the logo, but I have been able to successfully REMOVE it from the code.

There is indeed a checksum, however, we need a Microware OS-9000 guru to figure out that portion.

I have a copy of IDA PRO if anyone needs it (with the OS-9000 plugin)

Only difference in tioarch.tar is in nav_gd.tio. In T26.09A: AdviceMode=3 and in V26 AdviceMode=0. Someone please make a copy of V26 with tioarch.tar from T26.09A and see what happens. Maybe it's this easy...

Update: Sorry guys, need to go back to the drawing board. I thought I cracked this nut. I'll provide an update when it's fully functional. I think I'm off by two bits.

@JBerto & All
As soon as there is a routine found to exchange the images and keep the checksum, I will implement it into the GifExtractor.

@beedeeman
What went wrong? Was the checksum incorrect or didn't the navi take the update though the checksum was right?

Tino

Some systems use multiple checksums, one on each block of code/data, and then another at the end of the data.

I have one image that works GREAT, but trying another method based on comments that the V26 files are newer

Tino, I believe @RichardP1 is right. There maybe multiple checksums. This V26.09a is indeed a completely different animal compared to the other versions.

I working on a solution and will post back.

If there are multiple checksums, these are likely to be at logical page boundries, multiples of 4K or 8K or 16K etc.

I think the approach should be to use the v26 code and figure out how to change the options.

There are a lot of options in the code such as OFF Road, Taxi Route, car rental mode, ect.

I have made new installation disks with the V26 code in the following configurations.

None of them loaded the perspective mode

All V26 files, loader.ini from V26.09

All V26 files, bsw2 from v26.09

All v26 files, lowboot from v26.09

All V26 files, navboot from v26.09 This one was odd, as the software said loading 00, then I stil had the v26 ==bmw== logo and 6.0 on the settings menu and no perspecive mode

This makes me think that the navboot file is only loaded if "needed"

I have gone thru the tioarch.tar files and they seem identical

I think the smart option would be to find the switch to turn on perspective mode

They are not identical. You have not yet tried this? http://www.xoutpost.com/102274-post76.html

This is worth exploring...however there may not be a switch to turn it on, so we could be going down a dead end.


I have been investigating the possibility of multiple CRC checks in the file and I have found evidence for it.

Each section starts :

4DAD 0002 XXXX XXXX.

If you go into the file by XXXX XXXX you find another section beginnig 4DAD 0002 YYYY YYYY.

yet again go into the file by a further YYYY YYYY and you find another 4DAD 002.....and so on.

I guess we need to work out where the header ends and the CRC starts within each section and see if we can replicate the CRC numbers.

This is like a giant game of Sudoko .....but far more fun!

Just tried and no go either.
I have made a stack of coasters, and my CD spindle is almost out
I think this is the right approach, but just not sure how to turn Perspective on with the V26.00 Software disk

Martin

Yep, definitely multiple checksums for each block within navboot. Need access to OS9 development suite. Microware has an eval copy which they will snail mail. I'm gonna give it a try.

I wish they had a download for it.

It looks like Nomads changing of the checksum works. We just need to find out how he changed it.

I am ok sticking with the V26.09 software, but would prefer to just learn how to turn on the code for Perspective mode with the v26.00 software load. This way you will know how to "turn it back on" with the next software release.

Tyre has a copy of the eval software. maybe he can FTP it to you smart guys

I am chasing this approach also and will fwd updates...

Also I have switched to CD-RWs as my spindle was growing low from making coasters... the DVD drive reads them with no problem, but it adds 5 minutes for erasing and ~8 mins for the write. Upside: Have used the same disc for the last five burns.

I am going to trying adding the entire V_2/RR/0101 directory from the beta to v26.

Burning...

Thanks Martin.

Tried that yesterday. It still contains the old splash screen.

Right, but the old splash screen (BMW) can be modified without checksum errors... correct?

RealShakaZulu
Check out BSW_tools around dec location 40,674 are what appear to be some switches for certain modes including OFF ROAD Guidance and Others.

Mine didn't... By taking the old v26.rar and using UltraISO to cut and overwrite v26 with the v26 beta 0101 directory I was able to create a working ISO that

programmed the nav
allowed perspective mode
and eliminated the splash and nag message

is this your result and have you tried modifying the GIF at this point?

Actually, I have a copy of the full RELEASE version, not just the eval.

I can "share" it with the serious programmers :)

RSZ - hold on to that image file. That sounds like the most promising one so far. When you go to settings, what version does it display?

Jeff

I'd be happy to chip-in to help buy you guys new cds & perhaps even a little tip - heck, even if you aren't able to get this worked out. I just appreciate the hard work you guys are putting into this. How could a quick paypal account get set up for you guys?... Anyone?

i dont think so

"advice" is for voice advices i think

IMHO there is no variable we can create in tio files to enable 3d in ofiicial v26
all variables we can set are visible througt viewing software files from cd in some hex viewer

there are nothing like "3d_veiw_enabled" :(
and i think v26 compiled with no 3d option

but i think that code for procesing map in 3d mode in v26 is really present

let me explain:
i think that 26.09a software and any other version has some variable in flash or eeprom where it stores current map mode

lets imagine for example

01 - pointing N
02 - direction of travel
and in our case with 26.09a
03 - 3d view

when we alter navi screen (for example - activation of main menu and going back to navi screen) software knows in which mode to draw map when we return to navigation

i think software checks stored variable and decides how to draw map

in the same way i think it restores mode when we power off navigation module and turn it on again

and in the same way this is why when after downgrading back to v26 map displays in 3d mode

i think when we downgrade software to official v26 and if last map mode was "perspective"
software checks stored variable (in our case there is 03) and draws map in 3d

but if we push button to alter view in this mode there is no option to 3d view
there are only "pointing N" and "direction of travel" options

so only 01 pr 02 can be stored to mentioned place in flash or eeprom

perspective mode in selection menu not displayed because v26 software compiled without ability to display menu option "perspective"

and after that we lose 3d mode :(

So i think it is no ability to activate 3d mode in official v26

because even if there is ability to display "perspective" in menu = there is code for that, software always decides not to display menu option "perspective"

fot opposite of this software decides to display or not to display depending of map scale option "direction of travel"

i think enabling of "perspective" mode in v26 is not possible
not having disassembler or some tools to discover MIPS cpu code in software

maybe only other way to enable 3d mode is to change only one byte in software which software stores in mentioned place - change 02 to 03 in my case :)
and not forget to change text message "direction of travel" to "perespective" or something else :)

and agian this is only possible if there would be some kind of disassembler toll for mips os9000 code :)

and than we will get two modes

one of them will be 3d :)

P.S.
on yahoo group "hacktheibus" there some software to calculate crc24 for os 9000 files and some files for disassembler but it is for os9000 mk68

Those are the results I achieved. I think I confused the splash screens. All this back and forth has got my marbles in a tizzy. Anyway when I meant the old splash screen, I meant the "T26.09A" and not the "==BMW==" Sorry.

Although, I have another motive here. And that's to allow the use of any splash screen that one desires. Aand have the new enhancements that V26.09a brings.

Looks like we're on the same page though as far as moving the new beta files to the old V26 0101 directory. Great work :thumbup:

the only thing is that you moved over the entire contents of the flash directory. Now if you go to change the map directions, I do not think you will see all three options!!!!

A thought guys what if the checksum is only part of the requirement

During installation these files are being written to memory in the Nav Computer what if they have to be a very specific size in order to be placed in the correct position in the firmware and if the installer can't write the files to the correct area of memory it just bombs?

Or could it be that once the installer has written the files it then writes something else somewhere that tells the Nav comp bios what is where?

And it is at that stage that things don't add up so it bombs again?

Okay, my thought process is that based on the above we can not enable 3d view. So I intend to restore (since we know it was part of the original v26 but disabled) the beta to v26 and then try to enable all features and modify the splash screen.

If I am merely chasing my tail please stop me. Otherwise back to the lab...

-RSZ

Quite to the contrary, I have moved effortlessly back and forth between modes and photographed it just in case we are on the right path.

Help me understand what you are saying. Are you suggesting that adding the directory structure to the V26 image gives you perspecitve view, and the software version is 6.00 instead of 0.00?

That's correct, that's what I achieved yesterday. The only issue is the splash screen "T26.09A" which I'm in the process of fixing.

Right, now that makes sense. What you are doing is taking the entire firmware string and moving it to a new CD. I can not see how this is different from just loading the V26.09 Software disk by itself.... Or am I missing something????

I have an image that loads a custom logo that works. I think the better strategy towards this hack is to just hack the v26 disk and enable the 3d mode. I have swapped around individual files from the alpha disk to the released version one at a time and can not locate which one flips the register to enable perspective mode IF using the V26 disk files.

I guess you are right, if you compare navboot files from V26 and 26.09 there is about 840KB size difference between those so something is missing.

So Bishop, you believe that v26beta is nothing more than a patch. Therefore we are only replicating to one disk the act of installing v26 and then the beta?

Actually I do not think it is just a patch although the complete code. I think the reasons the softwre guys said "required" that you update from V26 is so that they had a baseline to work from. If some people were reporting errors it would be easier to determine that the issue stemed from the code or some legacy crap in there.

I could be todally wrong...., just ask my wife. I am sure she remembers enough times. :-)

Anyway I have jacked with this too much.

Here is where we stand.

1) You can change the logo with whatever build you want.
2) Whoever made the cool logo swap tool can add in a CRC check adjustment tool. The CRC24 bits are in each individual files so the process would be quite simple. Identify the CRC prior to making a change, and then update that line of code once you insert your custom logo. The poster Nomad figured out the process to adjust the CRC

Now, some users were reporting issues with the search feature not working properly. I did not try this, but I think the best goal would be too try and hack the V26 released code to add perpective mode. It might not be simple, but that would be the correct method.

So we have a few accomplishments.
1) a new tool for customizing your logo (just a small refinement will need to be made to adjust the CRC in the new file)
2) Ability to run perspective mode and the v26 firmware until you change it.
3) a baseline to start from in hacking out the extra features such as off road guidence, perpective mode, taxi mode (why I do not know) and other

At this point, I think it is left to the software pros on making those last changes.

2Wires, how big of a task is this? Much appreciated if you can do it. (Also sent him/her an email)

-RSZ

PS... just got word that he is working on it

I got word that nomad is working on it as well. He is also looking at the V26 code to see if he can turn it on with the released version.

Below are the details from Nomad that should be helpful to anyone trying to make an image swap program. Nomad has already proven that this process works in an earlier post. I installed his navboot file in my V26.09 image and it worked perfectly. Although his test version has the HACKED BMW logo, with skull and crossbones.... Not sure my wife would be hip to that splash screen.

http://www.bimmerboard.com/members/a...l/logohack.jpg


System works on MIPS CPU and OS-9000 software by Microware.
Each program, library or data file stored in a structure called 'module'
Each module has a header, body and CRC value.

First thing you need to do is extract all modules from 'navboot' file.
Here is some tips:
WORDs and DWORDs are stored in big endian format (most significant byte
first)

Each module started from 'magic' bytes sequence: 4D AD 00 02 which indicates the start of module header.

DWORD at offset 0x04 is the module full size DWORD at offset 0x0C is offset to module name (ASCIIZ string) DWORD at offset 0x24 is offset to module body

There are a lot of other fields such as module type, access rights, creation date etc.
Last 3 bytes is module CRC.


Martin
www.bimmernav.com

Ok, I am looking into it.
I just implemented CRC24. It is an unusual check so I had to implement it by myself (with a little help from jacksum ;) ).

I try to exchange the image and also change the checksum now.

Thanks Martin for the extraordinary effort... this goes well beyond just upgrading the Nav software. :thumbup:

By reading the complete thread I think that not only turning the Perspective on in the release version is the sure way to go, I think that keeping the Perspective on while reloading release V26 could be another way of looking at this and probably more direct.

Right now I am running the V26 back in my Nav but with the Perspective on. We already know that if the map orientation is changed then the Perspective disappear as a selection, so what about finding whatever "flag" keeps the Perspective selection on until changed and just set the sucker as a constant instead of a variable? :confused:

:goodluck: you guys. Keep up the great work!!

Okay... so help me with a dummies version of this... so I can understand :) .

1. Open navboot in a Hex Editor, remove old gif and replace with new GIF89a file.

2. Remove the last 6 characters (00 xx xx xx) of the file and calculate the 24bit CRC checksum using Jacksum.

3. Convert the checksum into Hex (not sure how you did this) and add it as the last 6 characters of the file.

4. Save the new navboot and then overwrite the navboot in the iso with the new navboot.

5. Burn, install and enjoy?

I completed the CRC24 routine but I cannot find out about what to calculate the checksum.
I tried it with the header and took 2, 4, 6 and 8 bytes away. But no luck.

Maybe someone can connect me with Nomad. He also seems German.

his email address was sent via PM

I contacted him. So we have to wait now.
I tried some more ways for the checksum but couldn't get it.

Help with Checksum
 

Are you sure? I took "navboot" and checked the last 3 bytes (2D 4F A4) of the file. I then truncated those bytes and ran a CRC24 hex outputed checksum (java -jar jacksum.jar -E hexup -a crc24 navboot)... which returned 82 3B F4.

Am I doing it wrong?

PS I tried both (1) generating checksums of the whole file and (2) per Roscoe reducing the file to a single section defined by 4D AD 00 02 less the last 3 bytes both with and without the "4D AD 00 02" header... it still produces a checksum value that is different than the one in the last 3 bytes of the file/section.

-RSZ

u must truncate 4 bytes and than calculate checksum

download program that calculates checksum for os 9000 files "crc24.exe" from yahoo "hacktheibus" group and see how program calculates checksum - there is source of program in "delphi"

Okay, I have the program (Thank you!!) and I tried to calculate the checksums to compare them to the value at the end of the sections... different values.:mad: So just for giggles I left the checksum on the end of the section and BINGO! So can I assume that program automatically truncates the last 4 bytes?


----------------------------------------
Nevermind... figured it out. It does automatically truncate and compares the checksum of the file less the last 4 bytes to the value in the last 4 bytes. Off to the lab...

exactly :)

with crc24.exe u dont' hav to truncate bytes
program automaticaly do not use last bytes

again see source

Okay I am off to bed...

I am still searching for the switches in v26 and in parallel working on the splash screens.

I need to know how the heck Nomad was able to make a working navboot with the new splash screen??? My current process, based on all that we have learned, involves

- extracting navboot from v26 beta and opening it in a hex editor

- cut and pasting the section (defined by 4D AD 00 02) which has the GIF file to a blank editor page

- deleting the GIF ("GIF89a" to ":;") from the section (verified it was the beta logo by pasting it to a blank editor page, saving it and opening it in Paint).

- open new gif in a blank editor page and selecting it, then pasting the hex into the previously mentioned section.

- save the now modified section and run CRC24 against it. Take new checksum and overwrite the 6 bytes at the end of the section... save (re-ran CRC24 to verify I entered it correctly, got the "OK")

- select the modified section and insert it back into navboot

- save image, burn, install

and it fails on install. What's Nomad's secret recipe?

I want to tell you one thing, that I discovered. I edit a Nomad file, cutting his logo from it and pasting 2609 logo. Files (original and hacked one) becomes one size and I compared them in WinHex. Here are the differences. So not only checksum changed. Because of that your image fails.
Forums is a great thing - you go to bed, I'm go to work:)
I try to deal with it in the evening (your morning).

Search for differences
1. C:\!!!\navboot2609: 12,631,320 bytes
2. C:\!!!\navboot_hacked_changed_for_compare: 12,631,320 bytes
B1F41E: 56 64
B1F41F: 74 D8
B1F46E: 61 53
B1F46F: 0B A7
B1F52E: 11 20
B1F52F: C0 24
B1F532: 1B 2A
B1F533: C8 2C
B1F53E: 2D 3C
B1F53F: C8 2C
B1F54A: 3F 4E
B1F54B: C8 2C
B1F556: 51 60
B1F557: C8 2C
B1F562: 63 72
B1F563: C8 2C
B1F56E: 75 84
B1F56F: C8 2C
B1F57A: 87 96
B1F57B: C8 2C
B1F586: 99 A8
B1F587: C8 2C
B1F592: AB BA
B1F593: C8 2C
B1F59E: BD CC
B1F59F: C8 2C
B1F5AA: CF DE
B1F5AB: C8 2C
B1F5B6: E1 F0
B1F5B7: C8 2C
B1F5C1: 00 01
B1F5C2: F3 02
B1F5C3: C8 2C
B1F5CE: 05 14
B1F5CF: C8 2C
B1F5DA: 17 26
B1F5DB: C8 2C
B1F5E6: 29 38
B1F5E7: C8 2C
B1F5F2: 3B 4A
B1F5F3: C8 2C
B1F5FE: 4D 5C
B1F5FF: C8 2C
B1F60A: 5F 6E
B1F60B: C8 2C
B1F616: 71 80
B1F617: C8 2C
B1F622: 83 92
B1F623: C8 2C
B1F62E: 95 A4
B1F62F: C8 2C
B1F63A: A7 B6
B1F63B: C8 2C
B1F646: AA B8
B1F647: 84 E8
B1F652: AD BB
B1F653: 40 A4
B1F65E: AD BB
B1F65F: 6C D0
B1F66A: AD BB
B1F66B: 90 F4
B1F676: AD BC
B1F677: B0 14
B1F682: B1 BF
B1F683: 7C E0
B1F68E: B3 C1
B1F68F: 84 E8
B1F69A: B6 C4
B1F69B: 0C 70
B1F6A6: B8 C6
B1F6A7: 94 F8
B1F6B2: BB C9
B1F6B3: 1C 80
B1F6BE: BD CC
B1F6BF: A4 08
B1F6CA: C0 CE
B1F6CB: 2C 90
B1F6D6: C2 D1
B1F6D7: B4 18
B1F6E2: C2 D1
B1F6E3: D4 38
B1F6EE: C2 D1
B1F6EF: F4 58
B1F6FA: C3 D1
B1F6FB: 14 78
B1F706: C3 D1
B1F707: 34 98
B1F712: C3 D1
B1F713: 5C C0
B1F71E: C3 D1
B1F71F: 84 E8
B1F72A: C3 D2
B1F72B: AC 10
B1F736: C3 D2
B1F737: E0 44
B1F742: C4 D2
B1F743: 00 64
B1F74E: C6 D4
B1F74F: 88 EC
B1F75A: C6 D5
B1F75B: A8 0C
B1F766: C6 D5
B1F767: C8 2C
B1F772: C6 D5
B1F773: E8 4C
B1F77E: C7 D5
B1F77F: 08 6C
B1F78A: C7 D5
B1F78B: 28 8C
B1F796: C7 D5
B1F797: 48 AC
B1F7A2: C7 D5
B1F7A3: 68 CC
B1F7AE: C7 D5
B1F7AF: 88 EC
B1F7BA: C8 D6
B1F7BB: 08 6C
B1F7C6: CA D8
B1F7C7: 08 6C
B1F7D2: CC DA
B1F7D3: 00 64
B1F7DE: CD DB
B1F7DF: 88 EC
B1F7EA: CE DC
B1F7EB: 84 E8
B1F7F6: CF DE
B1F7F7: D4 38
B1F802: D1 DF
B1F803: 24 88
B1F80E: D4 E3
B1F80F: A8 0C
B1F81A: D8 E6
B1F81B: 2C 90
B1F826: D9 E7
B1F827: 98 FC
B1F832: DB E9
B1F833: 04 68
B1F83E: DF EE
B1F83F: E4 48
B1F84A: E4 F3
B1F84B: C4 28
B1F856: E6 F4
B1F857: 68 CC
B1F862: E8 F6
B1F863: 0C 70
B1F86E: E9 F8
B1F86F: B0 14
B1F87A: EB F9
B1F87B: 54 B8
B1F886: ED FB
B1F887: 7C E0
B1F892: EF FE
B1F893: A4 08
B1F89D: 01 02
B1F89E: F1 00
B1F89F: A4 08
B1F8A9: 01 02
B1F8AA: F3 02
B1F8AB: A4 08
B1F8B5: 01 02
B1F8B6: F7 05
B1F8B7: 98 FC
B1F8C1: 01 02
B1F8C2: FB 09
B1F8C3: 8C F0
B1F8CD: 01 02
B1F8CE: FE 0C
B1F8CF: 04 68
B1F8DA: 00 0E
B1F8DB: 7C E0
B1F8E6: 05 13
B1F8E7: 68 CC
B1F8F2: 05 13
B1F8F3: 88 EC
B1F8FE: 05 14
B1F8FF: A8 0C
B1F90A: 05 14
B1F90B: C8 2C
B1F916: 06 14
B1F917: 48 AC
B1F922: 06 14
B1F923: 68 CC
B1F92E: 06 14
B1F92F: 88 EC
B1F93A: 07 16
B1F93B: F4 58
B1F946: 0A 18
B1F947: 7C E0
B1F952: 0D 1B
B1F953: 04 68
B1F95E: 10 1F
B1F95F: F0 54
B1F96A: 14 23
B1F96B: DC 40
B1F976: 18 27
B1F977: C4 28
B1F982: 1C 2A
B1F983: 68 CC
B1F98E: 20 2E
B1F98F: 4C B0
B1F99A: 32 40
B1F99B: 4C B0
B1F9A6: 44 52
B1F9A7: 4C B0
B44A89: F6 50
B44A8A: 74 4C
B44A8B: 6F B7
207 difference(s) found.

I got the OS9 CRC24 running now and can exchange images and correct the checksum.
But didn't test whether it works.
I will upload the new program version to the known places.

@Darky
Since B1F41E and B1F41F define the length of the module, Nomad seems to have changed the module.
Original 26.09a filesize: 12,631,320
Nomad filesize: 12.635.004

3,684 bytes difference.


26.09a module length 00 02 56 74 = 153,204
Nomad module length 00 02 64 D8 = 156,888

156,888 - 153,204 = 3,684

He probably knew what he did...


EDIT:
Be sure using UltraISO for exchanging the navboot. I tried WinISO but it changed the size of the image. UltraISO didn't.

I GOT IT!!!!!!!!!!!!! :):):):):):):):):):):)


I used my program to exchange the both 26.09a images found in the navboot with different images to find out which he uses.
Installing, restarting - NEW LOGO!
He uses the first one found at offset B1 F4 18.

The only problem is that we don't know how much space is reserved for those images.
Maybe I can figure that out when I get the OS9 system.

Here you can get my program:
GifExtractor

You need .NET 1.1 to run it:
http://www.microsoft.com/downloads/d...displaylang=en
Else there is an error like 0x00000035c.


I tried an image with 11,325 bytes and it worked:

http://carmes.de/download/software/new_logo.jpg

Tino

I've got it. But there are 202 more differences.

Ok,
I think I got a better idea how this all works. Still have to figure out more details.
For now my GifExtractor does what you want.
I'll work on updates to see what else can be changed.
I keep you posted.

Tino

maybe u can write program which extracts all modules as ordinary files

and the next step would be program which creates os9 module from files :)

I can extract them but it wouldn't help you. Those are just bytes.
I try to figure out the format of those modules and how the images are stored there.
Then I can embed bigger images.

The next feature is to changed the text displayed in the header
"T26.09A 2005-05-13 SW0.0"
http://www.xoutpost.com/images/member...D/V26-3D-4.jpg


Tino

hello, you can put a tutorial of since you have made the change of image? For that we do not have nor programming idea. Thanks

Select your navboot file, click extract. Find the first image with 26.09a and click exchange. If your new image is bigger than 4kb, check the checkbox ignore filesize.
Images bigger than 12kb isn't tested.
That's it.

You're the man, @2wires! I just tried with an image ~20kb and it also works! I make some photo in the evening. Really looks cool.

Thanks a lot to all who works on this project to make it possible! I hope it's still not the end.

:)

This is really cool stuff. I am running a MKIV in a range rover and have been trying to modify the software for ages! How are you guys extracting the files before writing to disc?
Are we now gong to be able to activate off road guidance as was in the range rover MKiii? Can we alter the color scheme as well?

Hey,
Look what I did now:
http://carmes.de/download/software/new_header_text.jpg
(The upper right text)

I already uploaded the new program to the known spot.
Maybe someone can write a little tutorial?


I guess that's it for today, but was a lot, eh?

Cya
Tino

as i understand navboot file is os9000 module ehich contains many files

if we can extract and compact it again we would be able to look to files
decide is this system OS files or vdo-bmw files and so on
and ... we maybe would be one step closer to modify software to enable 3d view in v26 (disassemble them or somesng....)

maybe exchange some extracted files with true 26 ...

In the navboot are modules and the modules contain file or direct information.
I can extract the modules but not the files, yet.
I would not risk patching the software.
I can give you tools when you need them but I will stay with my 26.09a and changed image.

That's What I'm Talking About!!!
 

Tino, beautiful job putting all it all together! You better get ready for all of the hits your site is about to get... I would recommend a counter, for you to really dress up the page with your products, etc and to link to the page vs. the link.

For the X5 community...

Attachment 5232

Attachment 5233

Attachment 5234

Attachment 5235

Attachment 5236

Attachment 5237

Bloody well done Tino excellent work, amazing what has been achieved in just effectively three days of collective effort

Excellent Job!!! Tino, you da man :thumbup: props also go to Martin for jacksum :)

Don't forget the "little guy" that started this whole craze by posting where the addresses were found, and in what files ;-)

Beautiful job guys....haven't tried it myself yet....no CDs at present...but it looks really good.

A real international effort.....if only everyone in the world worked so well together.... :hug:

I wonder if it supports animated Gifs.......now that would be cool.

Rgds


Roscoe

For the X5 World... http://www.wootenweb.com/downloads/software/

First X5World splash screen files
--------------------------------
NavBoot to insert into your image
MDF (image) with NavBoot inserted

Attachment 5238

Now that we can do the basics... I am about to get JIGGY WIT IT! Animated GIF, Hi Res graphics, custom cursors.... let's see what OS-9 can do!

Sorry. Hip-Hip Hoorah!!! to eveyone that helped make this happen.

Mine is like that now:

http://www.carmes.de/tino_bilder/car..._startlogo.jpg



http://www.carmes.de/tino_bilder/tinos_setup.jpg


Some advertisement:
We have adapters with which you can display your CarPC on the nav in vga quality! No TV tuner required anymore!
The device is called "CIB".
Here you can read a bit about it:
http://carmes.de/neu/en_faq.php

Very soon we will complete our new shop and website and then you can order them!
I post again as soon as we are done.

Thanks,
Tino

And, offcourse, dont forget Nomad! Without him, I think, all of this will be unreachable!

This is true !

Ok I've been trying to follow this by your posts but I am nowhere near the programmers or computer users you guys are....

Would anybody be willing to make me a graphic like 2wires original, with the BMW emblem and the ===BMW=== underneath it, perhaps with "Welcome Bryant" somewhere else on the screen as well? I'd want it with just the v26 software though, not the new beta. If anyone could do that, including creating the disc image cause I have NO idea how to do that either, I would be forever grateful. Monetary payment via PayPal would also be offered. Any takers?

Yea, he provided vital information to me.
And thanks to all the testers ;)
I think we can use images up to 100kb. I tried 15kb so far.

Very important is the image format
400x234 pixels
96x96 dpi
bit depth of 8
1 frame
GIF89a file type

I used 72dpi and got a programming error.

Maybe someone tries animated gifs?

Tino

That is interesting Tino

Questions

Just to clarify the image has to be :-

400 x 234 pixels?
and 96 x 96 dpi?
8 bits?

As when I use your app to save the original T26.09A gif I get 101 x 101 DPI?

Also Tino is there a minimum or maximum length to the header text string?

Lastly does this work with the official V26?

Finally Tino and all you others that chipped in well done again, I suggest you credit yourselves all over the place with this as I can guarantee somebody wil be on Ebay in no time at all offering personalised v26 upgrade CDs and claiming it is all there own work

What program did you create your Custom GIFs in ?

Photoshop ? Windows Paintbrush ? Etc...etc.....

Ok, I cannot be sure which formats the nav accepts. Maybe also gif87.

I just know that I got an error when I had 72dpi. But there could have been sth else wrong.
I took a fresh navboot, inserted the 96dpi images and the text and it worked.
I use Photoshop with a gif plugin.

The text is restricted to 24 character by my program. But I could only display 23.

Let's see if some people offer that on ebay. And let's what happens when they screw their customer's nav.
I wouldn't do that and I don't intend to. I just provide the software with some advertising ;)

Maybe I can sell the advertising space :rofl:

CorelXara

For any one that wants it, I've made a RAR archive in 5 parts of an ISO which has the BMW logo (with roundal) and version set to "4-1/60.09A" available here :

http://homepage.ntlworld.com/richard...V26.09A%20Mod/

each part is 4.8 MB. Available now.

Duplicate Post

With the issues people are reporting with V26.09, I think the smarter move would be to hack the logo of v26.

therefore people could load v26.09 change to perspective mode, then upgrade to V26 with the hacked logo.

To make a small MKIV only file you would only need to make an image of the following files

Files in Root
abstract
bibliorgraphy
Copyrightnotice
V_2 directory - containing RR and Voices sub directory

In the RR sub directory you will only need the contents of the 0101 folder

Martin

Guys - well done - this is a fantastic stuff.

Tdaniely do you think we can now modify using some parts of the Range Rover software I sent you? i.e. start up logo, color scheme, off -road guidance?

Quite happy to up load to any one else who may be interested!

I have just realised why mine is at 101dpi that is because I have my graphics display setting set to that

I guess yours is set to windows default of 96dpi so that is why your gif saves at that resolution

Obvious next question what is the real DPI of the original image in the Nav Boot file?

Tutorial
 

Here you go Tino. Thanks to Tino and everybody here who made this happen!!! This tutorial is my contribution and do not take credit for all the hard work of others.

This is a guide to allow one to modify the BMW Navigation startup splash screen (ie the ==BMW== image that displays on your screen when the car door is opened)

Important: You can not simply do this procedure with the same version of the SW that's already on the NAV unit. If your NAV unit has V26 installed already and you create a new CD with V26 then it will not update the splash. You need to either upgrade or downgrade to a new or old unmodified version. Then re-install the newly modifed splash version of the SW. This is so the NAV unit thinks that there is a new update.

Disclaimer: Keep in mind that changes will be made to system ROM files and could seriously damage your navigation computer. The provided set of tools which will accomplish the aforementioned task are not Guaranteed to work 100%. As always, you take on any liabilty and responsibility for damages. If you need help try searching this thread first. Now with that out of the way here's a step by step guide. You will need some manipulation tools installed first.

Download the following:
UltraISO http://www.tucows.com/preview/306129
GifExtractor
http://www.carmes.de/download/downlo...fExtractor.exe
.NET Libraries (When you install this SW make sure you're admin, and turn your internet security settings in explorer to medium/low)
http://www.microsoft.com/downloads/d...displaylang=en
CD Burning S/W (ie Nero, Alcohol120, DVD Decrypter, etc...)

Steps:
1. Obtain correct Navigation CD image of S/W version (ie V26.09aNote: this version could be bad for your unit, V26, V25, etc...)
2. Load image onto PC
3. Locate "navboot" file. Usually located in \V_2\RR\0101\BMWC01S\app_sw\
4. Copy "navboot" to hard drive on PC
5. Using GifExtractor load "navboot" by clicking "Find" button
6. Once loaded, click "extract"
7. Now in the "found images" box highlight the first entry and using cursor scroll down to the image that you will change. Located at HEX address [b1f418] it's the fourth one down.
9. NOTE! the new splash image has to fit the screen so you'll have to edit it (with Paint, PhotoShop, etc...) by making sure that it has aspect ratio of Width 400 x Height 234 x Depth 8bit 96X96dpi, single frame. And saved as a *.GIF file
10. If the new gif image is larger than 4544KB then you'll need to check the box "Do not check file size"
11. If you're running into a problem with images not being recognized even after they meet the specs in step 9. Then you need to check the box read "complicated" gifs.
12. Now select the gif you want to load by clicking at the bottom "Select image to exchange"
13. Voila!! now you have a new splash that will startup

Optional: If you want to change the S/W version that displays on the top right of your navigation display such as "4-3/60" (ie 4 is MIV system with S/W 60). And is found under menu->settings of your navigation unit, you can do that in the "New header text" box of GifExtractor

Now to create the image:
1. Start UltraISO (you will see window split into four sections)
2. Goto File->Open (locate the Navigation CD image of S/W) or Open CD/DVD
3. Once CD is loaded into "Image" window navigate to \V_2\RR\0101\BMWC01S\app_sw\
4. Now goto Actions->Add Files and locate the modified "navboot"
5. You will be prompted to verify replacement. Select "yes"
6. Now you're ready to make the new ISO image. In the top left window labeled "Image", click the first entry (it will look like 20060220_120036 with a CD Icon) edit the line to reflect "NAV_SW" and press return
7. Goto File->Save as and name the file of your choosing with "file type" as "mdf,mds" if using Alcohol120, otherwise save type as *.ISO if using Nero, DVD Decrypter
8. Almost there!!!

Follow final steps for Burning and Install outlined here:
http://www.xoutpost.com/navigation-sy...-released.html

:thumbup: thank you very much people of X5world, you've made one of my greatest dreams come true: a customizable nav-boot screen! I'll report soon if your project works in a MINI

Thanks beedeeman! You guys are great! I'm going to try this with my M3, and report back later. :D

Some startup screens for my fellow geeks...

These are 400x234, 96dpi, 8bit color I *believe*. Untested!!!

Thanks guys, this is fantastic and thanks to you Beedeman for that exellent write up :thumbup:

That's f__king great !!!!:rofl:

Great work all!!!

One question though.. As mentioned by Tino in an earlier post, the original GIF image inthe navboot file is of a certain size...say 4Kb, if we exchange the original image for a larger image, as some have already done, are we not overwriting important data in the navboot file?

I'm confused as to why someone earlier has managed to put in a 12Kb GIF image with no ill effects? I would have thought this would have trashed important data stored after the original image?

Now to try this on the original V26..hopefully this technique will work on V27, and future versions as well.. :)

NavMan

How about this :

http://homepage.ntlworld.com/richard...new-broken.gif

As mentioned before, the files are made up of modules.

The addition of a larger logo only adds more data to ONE of the modules, without altering the data in the following modules

LOL !!!!!!!!!!!!!!!!!!!!!!!!!

I think we can also exchange images in future updates because they won't change the filetype or sth. like that.
I guess images up to 100kb and more are usable. But a gif with that size won't be so big.

When I found out more about the file and module format, I can perhaps exactly tell how much space is reserved and even change it.
But for now everything we want works.

Tino

If I follow the exact procedures listed above AFTER I change the image, should I see my newly inserted graphic? Because I don't now, I see nothing- I haven't tried to load it into the nav yet...

Does the instruction also work for the V25 ? The screen of our navigation system is a little bit "milky" with the anti-aliasing graphic from the V26 and so i had to custom fit it for the V25.

PS: In march last year they launched V25. I think we have good chances for the V27 this year again.:)

I just updated my 2005 MINI Cooper S with no problem.

Only thing I noticed which is odd is no "accept screen" Which I love to not have!!!!!!!!

And I don't have a Boot up screen of the logo. It just goes right into Nav. It doesn't bother me but its different:rolleyes:

You should see it. Unless it doesn't meet the 400x234x8 96x96dpi format. Also, it has to be in GIF format.

Tino,

I've put up a tutorial. You may want to cut and paste into a readme file and bundle it with GifExtractor.

http://www.xoutpost.com/102790-post161.html

Thanks,
Ted

http://cgi.ebay.de/BMW-MK4-Navirechn...QQcmdZViewItem
:rolleyes:

This is way too exciting!
 

I am interested. How can I get a copy?

Thank you.

Is there any chance that you guys who are moding these programs can do some completed versions to download So just tugzip and burn, as this stuff is way over my head. I cant be the only one! LOL ie one like the standard logo and say one really cool one

Thanks

Have an idea
 

There is a copy here http://homepage.ntlworld.com/richard...V26.09A%20Mod/ the RAR is in 5 parts, it contains an ISO that you can burn with most software. Splash screen is BMW logo with roundal, versions says "4-1/60.09A".

The image is in that format. I will try to mess around with it some more. To try and shorten my testing cycle should I be able to see the image in the navboot file as soon as I exchange it, or do I need to recompile the cd-image and extract it again?

Two more questions:

1) I'm not sure about this step- 6. Now you're ready to make the new ISO image. On the top left window, click the first entry (it will look like 20060220_120036) edit the line to reflect "NAV_SW" and press return"
- I do not see anything that looks like " 20060220_120036" in UltraISO ?

2) The tutorial indicates- 7. Goto File->Save as and name the file of your choosing with "file type" as "mdf,mds".
- In a previous post it was mentioned that mdf files can simply be renamed as .iso files and burned with Nero etc... I assume the same can be done here? Is there any reason why the file isn't saved as an .iso file?

Thanks guys. Sorry for the **dumb** newb questions :rolleyes:

I wish it would be as easy as that. Although, some effort has to be made on the user part. It would be diffiult to figure out before hand what splash screen one desired and zip it up into a finished product. This method allows a novice to essentially do this over and over again at a moments notice if they wanted to change the splash.

Here ya go

http://www.xoutpost.com/102790-post161.html

Yes, as soon as you exchange. The image should be displayed. You may have to scroll down to it again. As you did before, there are two images at HEX address [b1f418] the first is blank and you will not see anything. The one you need is below that.

When you start UltraISO, the window will be split into four quadrents. The top left labeled "Image" has the String in it.

You do not have to save it as MDS/MDF, ISO should work fine also. Most people are using Alcohol120 and require MDS/MDF format.

:)

Great images, but I found them somewhat biased.

So find some more alternatives below :)

http://www.ltc.lu/eleves/bmw.x5/images/apple.gif
.
http://www.ltc.lu/eleves/bmw.x5/images/apple2.gif
.
http://www.ltc.lu/eleves/bmw.x5/images/finder.gif
.
http://www.ltc.lu/eleves/bmw.x5/images/tiger.gif
.
http://www.ltc.lu/eleves/bmw.x5/images/x.gif
.
http://www.ltc.lu/eleves/bmw.x5/images/starfleet.gif
.
http://www.ltc.lu/eleves/bmw.x5/images/trek.gif

I didn't try them, as I don't want to play with beta software after the reports of broken hardware, but I sure as hell will customize my v27 splash screen ;)

http://www.eonet.ne.jp/%7Eharimac/img/SadMac.jpg

:rofl:

Congratulations!!! This has been an exciting achievement.
 

First, thanks go to Ucrewx5, the gracious host for facilitating the international cooperation that made it all possible.

Also, in the midst of all these jubilations, one should not forget to give props especially to Tyre and Martin for their persistency in sparking this unprecedented passion in making the Ultimate Splash Screen project a reality. Tino, RealShakaZulu, BeeDeeMan, Appy, Darky, PRichards and those that their names eludes me.

But of course, props to those of us non-techies that were cheering them on.

Whoaaaaaaaaa, that would make for a good OSCAR acceptance speech.

Now that the splash screen project is a success, what next? :)

If you don't want to try the beta software, but still want a custom logo, why not downgrade to V25, and upgrade to V26 again, but with a modded logo...that's what I'm going to do..

NavMan

Congrats! this is a big achievement for sure:thumbup:. We need a splash screen for FF fans.
:bow: :bow:

Please excuse me if this is in a FAQ somewhere.

I might be the only casualty of this whole thing. I uploaded the image for the MINI and it worked great. I took a short drive, turned the car off for about 15min and then turned it back on. Car sat @ loading screen. I then pulled the battery and now it just loads the boot screen.

Would the fix for this be to reload and earlier firmware such as v26?

I totally forgot my manners: First of all, a great big THANK YOU! to all who worked on this little project- its fantastic! :thumbup:

As a follow-up to my previous questions- the GIF image I was using indicated all the appropriate attributes but did not work (it was made and saved using ACDSee Editor). When I loaded the same image and saved it using MS Paint it worked :) . I still don't see the 20060220_120036 entry in the top left window ??? Attached is a screenshot of what I see. "NAV_SW" was already there from the base V26.09a ISO I edited, I did not edit that entry. Is that what is being referred to?

Thanks again everyone- outstanding work!

Sorry to be off topic.. But can I noticed that people where changing the blue line info. I think that our Nav while in Full screen mode should say the street your on the bottom blue line. Can anyone do this?

I'm getting an Security error when trying to load the navboot into the gifextractor?

Thanks
-Ferrari

Yes, your correct. If "NAV_SW" was there then you're fine, good to go :thumbup: . Enjoy.

Screen shot? of error

V26.09a is not stable. Some people are also having issues. Going back to V26 will take care os that. Also, the logo mod will work with V26. :)

I've driven about 500 miles with V26.09a so far, and the perspective mode is awesome. No problems here.

Just got back in... are you still receiving the error? If so re-install v26... there should be no need to disconnect power, just put the disk in and give it a few minutes with the ignition on.

I gave it a few minutes. It just sits at the logo and the buttons don't work. So I will reload v26. Then you think a reload of 26a will work or there is another problem?

One more startup screen..

That's exactly what I am thinking.