Jump to content
AVIC411.com

dzo

Members
  • Content Count

    80
  • Joined

  • Last visited

Posts posted by dzo

  1. Dear dzo, 

     Thank you so much for your contribution of changing the language from japanese to english. I have an AVIC-MRZ02 and I successfully converted it to english. Can you please update the files so I can have a blue background as well?

     

    Thank you in advance,

    Andy 

    Did you use the zip from post 169?

    What color is the original background?

  2. I managed to delete some folders while trying to paste. Now the the system will not work at all. Somebody please assist. I would love to get it to work again

     

    I do have a complete backup of an mrz99, let me know exactly what you have deleted and I'll post it somewhere.

     

    The other thing to try is to use the other APP folder, just delete /DATA/PRG.FLG if it exists or create it if it doesn't.

  3. Hi DZO,

     

    Sorry to bother you again, but could you please advise if there is any instruction how to change boot splash screen on mrz77?

     

    Here are instructions on how to change the mrz99 splash screen.

     

    First get an 800x480 image to use. Save it in 16 bit rgb565 format, strip the header off so it is exactly 768000 bytes long.

    add a 512 byte header that starts like this:

     

    00000000  a5 5a 5a a5 00 b8 0b 00  bc ea cd 15 00 00 00 01  |.ZZ.............|

    00000010  01 00 00 00 00 00 00 00  4e 41 30 39 30 4f 50 4e  |........NA090OPN|

    00000020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|

     

    with the other bytes 0xff

     

    call it NA090OPN.DAT

     

    compile the makever.c program from my github and run it with NA090OPN.DAT to generate NA090OPN.VER.

     

    On a usb stick or sd card create a directory called AVICMRZ90 with a directory OPN090 inside it.

     

    copy NA090OPN.VER to AVICMRZ90 as PF090OPN.VER and OPN.VER (I can't remember which is correct so just put both in there)

    copy NA090OPN.DAT to the OPN090 directory and rename it as PF090OPN.DAT

     

    start testmode and select "forced firmware update" in japanese, I think it's the third entry but check first using google translate.

    select "opening image", i think it's the last entry but again, check.

     

    select usb or sd card and a new version number should appear, if not, check your directory structure and file names.

    hit menu (or it could be another key) and it will write the splash screen.

     

    I have done this and it works but as you can see it's not a simple process, it took me a long time to figure out the directory structure and

    when it finally worked I had the DAT and VER files in lots of places with different names so the above may not be 100% correct but with some trial and error you should be able to get it to work. There is no way to go back to the standard image.

     

    I'm happy with the splash screen I have now so I'm not going to change it or spend time making this process easier.

    I'm definitely not going to take requests to convert splash screen images into dat and ver files!!

     

     

     

     

     

     

     

  4. Hey Dzo, i followed your installer and extracted it onto USB however when i plug in usb it says copying with red screen then it says done with green screen. However it doesn't seem to work.

     

    I tried to turn off the car when doing installation and after completing restart.

     

    This was for the AVIC MRZ90.

     

    First i was trying to convert to english and once that's done hopefully i can load NZ maps on it

    any help would be appreciated it. 

     

    Mrz90 is a bit older than mrz99 so it probably has different strings. Can you get into testmode and copy all of /USER to an sd card then post /USER/PRG1/APL/MENU/Image.img and everything in /USER/PRG1/APL/LANGDATA/ here. I'll see what I can do.

     

    I'm in NZ too, I don't think putting NZ maps on these devices will be easy or worthwhile because the english versions never had NZ maps and Google maps is far bettter anyway.

  5. DZO hi. Tell me please what is the reason, after the translation, and the subsequent compilation of PF090JPJPN.LNG through the command ./recode translated.txt PF090JPJPN.LNG, the terminal produces a segmentation error (a memory dump is made)

     

    There's no error checking so it'll do this if it can't open the input file. 

  6. Hi DZO

     

    Thank you for your work here. I have a question if you don't mind. I've installed the translation on my MRZ77, all is fine and the question is, i have spotted other LNG files in LANGDATA folder of my device like PF090JPENG.LNG, do you know, if  these files contain translations or what are they used for?

     

    They are language files with slight changes, it looks like they are mostly for different car companies, e.g. NA090JPMZD.LNG for Mazda.

    There is a PF090JPENG.LNG but it only has a few English strings. 

  7. Hi DZO.

    I was wondering if there's a step by step guide anywhere showing how to edit these .LNG files / translate them to English, because I'd really like to learn how it works.

    I understood how to access, backup and replace the files, but I just can't get the decoding and stuff to work. I've seen your post on github but I'm not sure how to use the scripts.. 

     

    If a guide doesn't exist and you prefer to not make one, which I understand, do you still take requests?

    Thanks for reading!

     

    The source on github are small C programs. To run them you need a compiler, it's possible on windows but much easier on a linux box.

     

    For a debian based distribution you need unicode libs so do:

     

    apt install libunistring-dev

    git clone https://github.com/dzo/mrz99.git

    cd mrz99

    make

     

    to extract strings from a .LNG file do:

     

    ./decode PF090JPJPN.LNG | iconv -f utf16 > untranslated_090.txt

     

    to create a new .LNG file do:

     

    ./recode translated.txt PF090JPJPN_new.LNG

     

    where translated.txt is the translated text.

     

    To extract the images from an Image.img file do

     

    mkdir bmp

    ./extractbmp

    cp -r bmp bmp_d

    cd bmp_d

    for i in *.gz; do gzip -d $i; done

     

    to make a new Image.img file put your new images in the updated directory (must be 16 bit rgb565) and do:

     

    cp -r bmp bmp1

    cd updated

    sh ./update.sh

    cd ..

    ./extractbmp encode

     

    I do have a way to change the splash screen on the mrz99 but it's a little fiddly so I'll only make it available if there is lots of demand.

  8. Thanks for the speedy response! The car was out of town so I couldn't pull the files until today. I've attached them as requested. FYI the button combination worked fine on the unit, there was no need for the testmode key file. Hope that means good things.

     

    Link: https://mega.nz/#!N1wyFCZa!7FPQRHklxRglhJMqP5goW1CZ-she9gIElC6Zk0TKzCs

    (I had to use mega because I couldn't attach the file here, some error about no file was selected whenever I tried)

     

    Also, since you are familiar with the file structure, what the purpose of the PRG0 folder? its almost identical to the PRG1 folder. Is it for some alternate mode? or language?

     

    Thanks, it's very similar to mrz09 but with a few more strings and slightly different images.

     

    Here is an update that might work:

     

    https://github.com/dzo/mrz99/releases/download/v2.1/mrz02_update.zip

     

    extract it to a usb stick, plug it in and wait.

     

    If the images don't work, replace the Image.img file with your original and try again.

     

    PRG0 and PRG1 are used for updates, when the system is updated it copies the new files to the unused directory and then adds or removes a PRG.FLG to say which one is now in use. no PRG.FLG means use PRG0, PRG.FLG means use PRG1.

  9. Ok I have downloaded the code, now how to use the programs ? what tool do you use to edit the strings ? with notepad++ I cannot see the japanese strings file correctly as it doesnt detect the right encoding characterset.

    I have an mrz77 unit and I want to make sure that all japanese strings for this unit are translated but I read in one of the posts in this thread that mrz77 has more strings than the mrz99 for which you provide the translated LNG file so I would like to be able to translate these additional strings unless there is a language file already complete for mrz77 ?

     

    decode generates utf16 strings so you need to convert them to utf8, I use iconv for this, most editors can handle utf8.

    I just checked and mrz77 only has one extra string which is already translated so you should be able to use the latest mrz99  PF090JPJPN.LNG file. Don't install the image file from mrz99, use the one from post #67.

  10. Hi Dzo

    thank you for you great work, as I was desperate to ever be able to easily use the MRZ77 that is fitted in my Nissan March. I have not yet tested your language files as I am not home currently but I will surely.

    My question is : where can we find the updated code you are talking about in the quoted post above ? I have a link to a V2.1 release (https://github.com/dzo/mrz99/releases) but it was released on 7 feb and your post is dated 23-march.

    Thanks again

    Fabrice

     

    That's the release which is a zip built from my code, but it's only english so it hasn't changed.

    The code is here:

     

    https://github.com/dzo/mrz99

  11. Hey guys, Just bought a Nissan with the MRZ02 unit. Has anyone tried this method on this version of the unit? Or the MRZ04, or MRZ06 models? Just want to know if the platform version is the same and if its compatible before I try anything.

     

    The mrz02 is from 2013 so you'd expect it to be a much newer platform than mrz99 but it does look very similar in the screenshots.

     

    The best thing to do is try to dump the firmware and post some of the files here.

     

    Try to get into testmode using the key combination or the testmode key in post #90. If these don't work then it's probably a different platform.

     

    If you can get into testmode, copy all of /USER to an sd card then post /USER/PRG1/APL/MENU/Image.img and everything in /USER/PRG1/APL/LANGDATA/ here. 

  12. DZO hello, please do from the txt file to the LNG format.

    This is the updated Russian language on MRZ 0047.

    Here it is:

     

    mrz0047_ru.zip

     

    If changing the font doesn't work (did it display at all?) then it's not going to be easy to fix the spacing problem, I guess they hardcoded a fixed spacing for chars above 255 to display Japanese correctly. This is most likely in the platform rather than the apps code, your only choice may be to convert the text to non Cyrillic chars. 

  13. DZO привет а может в txt файле при переводе заменить межбуквеннвй интервал?

    Перевод Ñо временем отредактируем на данный момент он имеет ошибки.

    DZO а Ñ‚Ñ‹ не подÑкажешь как txt переделать в LNG нам было бы легче при редоктировании перевода проверить его на уÑтройÑтве. Так как не понÑтно какое Ñлово в какой кнопке поÑвитьÑÑ.

    Sorry, I don't understand what you want to do. The spacing issue is caused by the font, not the language strings. Fixing the font should make the text fit in the buttons.

  14. DZO помоги шрифт выровнÑÑ‚ÑŒ.

     

    Looks like the font spacing is not correct, one thing you could try is to change the system font, it's in PRGX/FONTS/DFHSMaruGothic.pgf

     

    Here's a font from f30bt:

     

    https://www.dropbox.com/s/5sl9r6k2j32860a/tahoma_09H.pgf?dl=0

     

    Replacing the font may not be 100% safe because I don't know if it's compatible or what would happen if it tries to draw a Japanese character. Also it's possible that the TestMode executable uses this font so that could become unusable which would be very bad. For these reasons I'm not going to try this but if you are brave...... 

     

    edit:

     

    Looks like somebody has tried replacing the font file on a european model:

     

    http://avic411.com/index.php?/topic/31534-condis-hackmode-v22-autoinstall-working-also-with-f40bt-x940bt-etc-updated-27092012/?p=242146

     

    and it didn't destroy anything so it might be safe...

  15. DZO вот попробуй пожалуйÑта, возможно его надо будет проверить

    [Вложение = 16548: Mrz99_translation_0047.txt ru.txt]

     

    OK, here are langdata files using that translation:

     

    russian.zip

     

    I had to fix up quite a few things for it to work but I tested it and Cyrillic text does appear.

    The two files are  PF090JPJPN_RU.LNG for mrz99 and PF090JPJPN_0047_RU.LNG for mrz0047.

     

    Rename the one you want to PF090JPJPN.LNG and put it in the correct place.

     

    The icons and some text are still in english. I've updated the github repo with the new translations, edit this rather than the one in the previous post if you want any improvements.

  16. Good afternoon. I would also like a translation in Russian. If someone would sort out how to collect from the source, I would deal with the translation myself.

     

    OK, I've updated the code so it'll accept utf8 chars. To do a translation into a new language, fork my github project and edit the "translated.txt" file to create a new one (translated_ru.txt perhaps).

    Some rules:

     

    No double quotes (") allowed anywhere except the start and end of a string (some are on multiple lines).

    Don't change anything that has a % followed by some characters (google translate will mess these up so you will have to fix them by hand).

    Don't add lots of new text, the final langdata file must be less than 128K and it's quite close to that.

     

    I'm happy to create the langdata file for you when the strings are translated but make sure you follow the rules above or it won't work. 

  17. Good afternoon. I would also like a translation in Russian. If someone would sort out how to collect from the source, I would deal with the translation myself.

    The source is here:

     

    https://github.com/dzo/mrz99

     

    You'll have to make some changes to the code because it doesn't support utf chars in the translation.

    The langdata is stored as utf16 so Cyrillic will probably be supported but the translated strings will probably need to be utf8.

     

    I've also added translations for mrz0047. 

  18. Hey dzo, i have managed to back up the user folder from the mrz0047. The generic testmode key worked like a charm. As per your instructions i have zipped the LANGDATA and MENU folders from PRG0 and PRG1. Here are the zip files. Kindly see what you can do with these. Any effort i truly appreciate.

     

    OK, the language strings are similar to the old verson of mrz99 (but not the same).

     

    Here's a new  NA090JPJPN.LNG that should work. Just replace the old one in either PRG0/LANGDATA or PRG1/LANGDATA depending on the existence of  PRG.FLG (if it exists in /USER use PRG1).

     

    mrz0047.zip

     

    The images are a bit trickier, they are completely different, It'll take me a while to make an image file.

     

    edit:  I've taken a look at the images and it would be a lot of work to redo them because it uses a dark background while mrz99 has a light one. You'll have make do with the original images.

  19. dear dzo,

    Am new to this forum and have gone through the thread.. if i got to this point is because i got a similar challenge. Only difference is that the device i got is a

    AVIC-mrz0047 on a Nissan tiida 2009 model. 

    Is there a way to have the language to change from Japanese to English. Am not sure but i think the mrz0047 is on a different platform from the mrz99 and mrz09 (i encourage clarification on that).

    Could you kindly look into it, Any help is highly appreciated.

    I'm fairly sure that mrz0047 is pioneer's generic name for the platform that mrz99 is based on. Yours is customised for nissan. So it should be possible to translate your unit. It's older than mrz99 so don't do anything yet. Can you try the generic testmode key I posted last week and make a backup of USER then post the contents of LANGDATA and MENU here

  20. That TESTMODE.KEY didn't work either. Same problem.

    OK, it must be a completely different platform, the only thing I can suggest is that you try to make a testmode key using this:

     

    https://github.com/bassrock/AVIC-NEX/tree/master/TestKeys

     

    This is the newer format for testmode keys.

     

    You can also experiment to see if there is a key combination to get you into testmode.

     

    I took a look as the user manual for mrz099 and the UI is completely different to the mrz99 so it's very unlikely that anything here will be of use to you.

×
×
  • Create New...