I've got exactly the same problem, except the worst thing is that it is my friend's mk3!

So it's bad! I've taken the mk4 out of my car and put it into his while I try and revive his mk3. I had same symtoms, started upgrade (v26) and then the screen just went black. Stayed like that for ages. Then the disk wouldn't come out. Eventually figured out how to get the disk out, held the eject button for about 3mins, the light went out, then press eject and the disk *should* pop out. See here http://www.xoutpost.com/articles/all-...ion-drive.html

Anyway, put in another copy (v22.1), and it still didn't like it. Except this time it didn't even say "Updating software...", just nothing. I've had this problem in mk4 but as soon as I burnt a new copy it was fine. And then the cd wouldn't eject at all, no matter what. So I took the top off and wound the cog round. Ejected very easily (and took less than 3 mins!). I wound it with my finger and used a small screwdriver to stop the cog from spinning back while i repositioned my finger. I didn't want to damage the cog.

My next try is burn another copy of the cd using Jochen's instructions http://www.xoutpost.com/navigation-sy...heres-how.html. My cd's aren't called nav_sw and not done in mode2 burn.

Incidently, all my cd's so have have had a new splash screen added, I wasn't sure which one my system would use so I edited all of them, including the mk4 nav_boot file. I hadn't read this article and saw the splash screen in the usw_load file in NavTweak so thought I would give it a go. I thought that was possibly why the update failed, but obviously not!

Good luck and let me know how you get on. I hope I can fix this otherwise I'm gonna have to get him a new one!

On a side note, I read the thread about changing the VIN and vehicle type using NavCoder and IBus interface. It also mentions loading language fiules from disk. Anyone know if can you reflash the whole eeprom using this method? An alternative maybe if I can't get this working using the disk update method maybe.

thanks
Kam

shunting the battery cables together is a good thing to try for sure. if that doesnt work then you can often recover the nav by resetting the language in the unit. This can be done either with an I bus interface or with the dealer's GT1 computer using the path Conversion, IKE, Language.

__________________
DT

Ok guys...i'm scare to do this, but seems the only way to try to resolve my problem...I'm not be able to work with iBus interface and similar.
Late I'll try shunting cables and God be with me...
D'you think could dangerous, for nav system I mean, touch cables each other for awhile?

there is nothing dangerous about shunting the battery cables together. Just remove both cables from the vehicles battery and use a jumper wire or a test lamp to connect them together. Leave them connected for a good 15 minutes. There is nothing unsafe about this, all it does is remove any static electricity from the system and help to discharge capacitors in the control modules.

__________________
DT

Just to let you know, I burnt a copy of v22.1 disk (available from http://www.e38.org/nav). On the mk3 this is the jighest software version you can go to.

Anyway, I needed to revive the unit so burnt a straight copy, no changed logos. I removed the disk initially using the cog spin method. Burnt onto TDK disk at 4 speed (the lowet my burner would allow) and voila, the unit is back up alive!!! I used ClonCD (the image was CloneCd, PM me is you want a working copy).

Next, I'm going to do a v23 with changed splash screen.

Give it a go with v22.1, many failed attempts seem to have have been fixed with this.

Have a great new years.

Kam.

Hi Jammi, are you sure about 22.1 sw?

I found on a forum some threads where was written that the highest version of sw for Mk3 should be the 25 ones.
however, thanks for your contribute on my problem, I'll try also your solution.
Happy new year

Hi Symbian

Take a look here http://www.xoutpost.com/articles/all-...ystem-faq.html

Above v22, the software versino never changes for mk3, i.e. always 3-1/63

I think the key to this all is thw cd must be called nav_sw and the mode 2 burning. I know for sure the v22.1 CloneCD image from e38.org is correct in both these. Some people have suggested that the CloneCD images work better, and these were the last of the breed.

I have confidence that you will be able to fix it now having gone through the same thing and thinking I had totally screwed it up.

Good luck

Hi everyone, if you burn an OS CD you must make sure the finished CD is burnt as a MODE2/FORM1 CD.

Most CD burners will burn as Mode1, and the Mk3 cannot boot from a Mode1 CD.

All your problems are caused by Mode1 CDs.

Make the CD a mode2 and it will burn OK.

Mode2 works on Mk3, Mk4
Mode1 only works on Mk4

You should verify that you have a Mode2 CD before inserting into the nav system

I use ImgBurn to verify my CDs.

Note that 3/1-63 was the last official version for the Mk3.
I have 3/1-64, but that's with custom splash screen and custom menu text :-)

Jochen

One more thing: when the Mk3 gets in an endless loop after inserting a Mode1 CD, it stops talking on the I-Bus.

So you cannot reset the language using the DIS. The dealer will tell you the nav unit is faulty. But it is not.

You must eject the Mode1 CD, then you can insert a Mode2/Form1 OS CD and the nav unit will boot up, load the SW and come back to life.

I know, because when it happened to me, I was monitoring the I-Bus with my PC and saw everything happening.... scared me to for 30min, but I recovered OK :-)