DVD in motion patch for NR261UM

[per kristian]

Hi! Thanks for a great forum. I have got 2007 Outlander. It had the regular radio/cd changer, but I have changed it to the MMCS. The problem is that the navi is from the c-crosser and has the Citroën start-up. Is it possible to change this to the Mitsubishi start up? Is the start-up file on the HDD or in the unit? Tried to get the video in motion upgrade to work, but the unit do not response to the burned image and will not upgrade. Does it not support my software version? Thanks

This ad is not displayed to registered members. Register your free account today and become a member on MitsubishiForum!

[Phantom3D]

Got two cars now that we wish to patch so that we can get DVD/aux video in motion:

09 Lancer
Loader: BLD-NR-261EM 1.09
Application 00.31.10

09 Outlander
Loader: BLD-NR-261EM 1.09
Application 00.40.13

Any news on these would be appreciated!

Thanks
Magnus

[dger]

Originally Posted by garywatkins1981

To give a little update on the TV-Kit I bought one for my 2008 evo x. I choose to have the local car audio shop install it for me. It only cost me 80 Bucks to have that installed and my aux cord hide to in side the glove box. It all works like a dream. Like other have said u have to switch from DVD to NAV but I don't care cant see me using both at the same time anyway. One down fall was that the part comes from Japan so it took like 3 weeks for me to get it. I would like to thank everyone for their help and the Great threads

Can you give some info on how many and what type of TV aerials you installed??
THX

[ninamarie]

I don't mean to sound rude, but can you guys start a new thread about the tv-kit. This thread is hella long as it is!

[Doublecheese]

GUYS,

I've been away for a long time .

One question though .

Did Otaku manage to FIX the VIDEO in MOTION yet ? or not ?

I know DVD in MOTION was working fine by then .

cheers

DC...

[greeneagle]

Hi Doublecheese,

Hope you have been well. No Otaku has not been able to do this yet. Even though he has been able to get his hands on some hardware to test the software, he has been tied up with work and has not been able to get to this. Hopefully, once he has finished with the projects he has at work he will be to get this done as well.

Rgds,

[Doublecheese]

Originally Posted by greeneagle

Hi Doublecheese,

Hope you have been well. No Otaku has not been able to do this yet. Even though he has been able to get his hands on some hardware to test the software, he has been tied up with work and has not been able to get to this. Hopefully, once he has finished with the projects he has at work he will be to get this done as well.

Rgds,

Hi Greeneagle and others

So nothing changed much since I left then. Well if you guys want you can order the parts that I had ordered last year and live a happy life with DVD + VIDEO IN while in motion

This DVD + VIDEO IN kit are not affected with firmware updates of Mitsubishi for MMCS as well

[JayB059]

Hi all,

I am having some difficulties when unlocking the MMCS HDD. I have version 30.99 and wanted to try and downgrade to 30.94 like some others had successfully done here.

I was able to get the HDD unlocked (sort of), but had some trouble copying files off of it. From what I had read from those that did downgrade successfully, I am supposed to replace the ALLDATA.KWI in the HDD partition and the LOADING.KWI in the HDD3 partition with the original ones for 30.94, which I found on rcotsin's site: http://www.deltainfo.ro/manuals/mitsu/outlander/ ... specifically Outlander CD, NR261-UM, Software version Version 00.30.94, original version. I had planned on saving the original 30.99 ones from my HDD and was able to copy off the ALLDATA.KWI ok, but the LOADING.KWI file would not move. I tried in Windows XP and 7 and Ubuntu and using the Isolinux boot disk...in Windows it says that the file is corrupt and in Linux I get an Input/Output error. Not sure if I unlocked it wrong. Anyway, I managed to change the name of the LOADING.KWI file using Isolinux only and then I added the other version on. I saved off my original ALLDATA.KWI and added the other version as well as the other LOADING.KWI to the HDD partition. Put drive back in MMCS and version hadn't changed but everything else was working normally. Tried disconnecting battery for a couple minutes but this didn't change anything either. I brought drive in and tried again. Since then, I have not been able to get anything working in the car as normal...even putting stuff back to original files. Not sure exactly where I messed up ... some bad things I might have done are trying to lock the drive and then unlock it again using the Isolinux xbox tool and also I might have inadvertently removed hidden files from the HDD2 partition...this partition is 124 MB but seems to be empty...not sure if there was anything in it originally. So, when putting original files back on drive and putting back in car, I got an error message saying "Program writing error. Turn the engine key off to retry". When putting the other files back on or the ones from Outlander Update CD, NR261-UM, Software version Version 00.30.94, DVD in motion allowed I just get a blank black screen.

The drive is no longer being locked by MMCS. This I imagine is the main problem, but I am not sure what caused it and more importantly, how to resolve the issue. I was hoping someone had some insight or suggestions to try. Maybe I had screwed up from the get go when unlocking the drive because of the issue I was having with removing the original LOADING.KWI from HDD3. One thing I was uncertain of was the exact syntax of the unlock key. From the 1st page of the unlock HDD thread, it mentions that the key is:

b2bab3bcb0dfacbeb1bbbedfb1add2cdc9ceaab2dfb19e8996 dfaa8c9a8ddfdf

I was uncertain whether or not the space was intended to be used or not. Usually in linux, the arguments to a command are space delimited, so I figured a space was not supposed to be used, so the exact syntax I used was:

unlockhd -p b2bab3bcb0dfacbeb1bbbedfb1add2cdc9ceaab2dfb19e8996 dfaa8c9a8ddfdf

So, did I do something wrong here? It did unlock as I was able to run fdisk -l to see the partitions ... but maybe I only partially did it. Also, in a later post from Otaku, he mentioned an alternative key for the last part:

B2BAB3BCB0DFACBEB1BBBEDFB1ADD2CDC9CEAAB2DFB19E8996 DFB29E8C8B9A8D

so I wasn't sure if that was supposed to be used instead (again, I would have thought no space).

Any help would be greatly appreciated...sorry for the long post. Thanks much.

~ Jay

edit: that's odd...when typing the key I used after the "unlock -p", I did not type a space but one was added when the post was made...maybe some sort of letter limit per word???