topblog Ivoire blogs

23/01/2018

Opcom firmware 1.90 and 1.70, which better?

Opcom firmware 1.95 released recently, saying it works with Vaux-com 120309a and much more better than opcom 1.70 and 1.65.

Is it true? Does Opcom 1.95 any good?

Upload photos..

the first photo: opcom fw 1.95
the second photo: opcom fw 1.70

opcom-firmware-1.95-pcb Opcom-firmware-1.70-PCB-1

Opinions from three professionals/users might help you.

  1. opcom 1.95 and 1.70 - the same

I can see that the 1.95 and the 1.70 are the exactly the same.

From photos I can see difference only with some tantalum caps. In 1.95 they are through hole and in 1.70 they are the smd type. Also you can see from the pictures they have the same silkscreen markings C20 and C21, also rest of components have the same markings. Also the firmware number of the 1.70 is fake as said mattydr67.
Also I think the Opcom V1.70 have better PCB quality compared to another version 1.95

  1. original PIC chip - the most important

Most important is to have an original PIC chip that can program new firmware.

The version 1.70 have a flashable PIC mcu inside. I kill my Opcom twice and I flashed it with PICkit 2 without any problems, but the problem was not with mcu and with FT232 with wrong firmware. Also in ver. 1.70 there is ICSP connector with which you can flash MCU directly with PICkit programmer.

  1. opcom 1.64 - last official

The last official firmware is 1.64
Check also the official op-com.hu and you will see there the newest firnware version that it will come in the new version of opcom and it will be fw1.66
So I suppose I answare to you about this new firmwares versions that all are fake one.
For vaux-com 120309a you need only Opcom fw1.45
Even you are using the fake vauxcom 120309a+131223a version you need also fw1.45
Not any newer. But you can use any newer versions of firnware but you will have nothing new and it will not help you more then fw1.45

To answare to your question about which tool to buy the DO NOT buy the last one. ( its using a not real MCU )

Good luck

18/01/2018

Xhorse VVDI2 latest software version V5.1.0

Xhorse VVDI2 latest software version update to V5.1.0 on Jan.18,2018.

Require firmware V5.1.0.


VVDI2  V5.1.0 detail update information:

===== VAG V5.1.0 =====

1. Improvement MQB NEC35xx immoblizer/KM function, support following cars:

Audi A3/S3 2014+
Audi Q2
VW Golf7
VW Polo(MQB)
VW Tiguan II
VW Touran II
VW crafter 2017+
VW Passat B8 without virtual cockpit
Skoda Octavia III 2014.07+
Skoda Rapid 2015.06+
Skoda Kodiaq
Skoda Superb III
Seat Ibiza/Ateca/Toledo 2015.06+

Attention 1: This type only support cars with cluster Continental/VDO. JCI type and virtual cockpit was not includ

Attention 2: MQB Immobilizer function support original blank key and MQB key made by VVDI2

Attention 3: part of original blank key not support write data

Attention 4: MQB Immobilizer function require extra license. Customer who have copy 48 (96 bit) license will get MQB license for free

2. Improvement for autodetct in IMMO4 system

3. Add spanish language

4. Bugfix

===== BMW V5.1.0 =====

1. Improvement for read ISN from MSx8x ECU, require VVDI2 database file verison V1.0.0
2. Improvement for load MEV17xx EEPROM dump
3. Support change second hand FEM/BDC ISN and make original key working
4. Add spanish language
5. Bugfix

===== Porsche V5.1.0 =====

1. Add spanish language
2. Bugfix

===== PSA V5.1.0 =====

1. Add spanish language
2. Bugfix


===== Transponder Programmer V5.1.0 =====

1. Bugfix for update remote database
2. Bugfix for save points
3. Immobilizer data tool: bugfix for Fiat Ducato 93C56
4. Add spanish language
5. Bugfix

===== J2534 V5.1.0 =====

1. Add spanish language
2. Bugfix
===== Online Upate Tool V5.1.0 =====


1. Add spanish language
2. Bugfix

===== Quick Start V5.1.0 =====

1. Bugfix

https://mega.nz/#!PoJBSBKD!nn1ai-JfcoqAM4hbnitabziaSWY-5v...

Xhorse VVDI2 Product details:

http://www.xhorsetool.com/wholesale/vvdi2-full-version.html

15/01/2018

How to change VCMII module type

I fixed the issue with error 500 on the VCMII module type change.

vcm-type

All standard recovery functionality has been preserved
You can still boot to recovery and flash software via normal methods.

Additional Features:

  • Root password “hackedVCM” (no quotes)
  • Telenet server
  • FTP server
  • Testmode web server (all original testmode functionality preserved including serial number change)
  • Added change module type (Ford, Mazda, whatever) to web server
    ‘Other Functions’ > ‘Set Module Type’
  • SD card & JFFS2 partition are mounted RW in the same place they would be in production, /mnt/sd & /etc/vci/config respectively.
  • Added WiFi support in recovery but leaving the interface disabled for now. I have concerns about browning out the device if external power isn’t present as USB only power isn’t sufficient. If you want to test it out you can use standard linux ifconfig commands to bring the interface up, all drivers are present.
  • Custom recovery currently survives reflash (until they change the way they deploy updates)

To Do:
The next thing I am working on is my custom web browser based flasher.

To deploy the firmware:
If you are updating from my previous firmware you only need to perform steps 1, & 4-7.

  1. Download and extract the firmware from this post
  2. Use the testmode exploit from my first post and then launch telnet
  3. Run the following commands to change the root password (non persistent):
    1. echo “root:$1$quzG9B6u$qqNRmEdJ0igLcxha0qzp3/:0:0:root:/:/bin/bash” > /etc/passwd.tmp
    2. tail -n 14 /etc/passwd >> /etc/passwd.tmp
    3. mv /etc/passwd.tmp /etc/passwd
    4. chmod a+r /etc/passwd
  4. launch your favorite FTP client and connect to 192.168.171.2 using user ‘root’ and password ‘hackedVCM’
  5. upload the two firmware files ‘mtd4.new’ & ‘mtd5.new’ to the ‘/tmp’ folder
  6. Returning to the Telnet session, run the following commands to flash the new recovery firmware:
    1. /usr/local/mtd/flash_unlock /dev/mtd4
    2. /usr/local/mtd/flashcp -v /tmp/mtd4.new /dev/mtd4
    3. /usr/local/mtd/flash_unlock /dev/mtd5
    4. /usr/local/mtd/flashcp -v /tmp/mtd5.new /dev/mtd5
  7. Reboot your VCMII into recovery (hold the button in while applying power and keep it depressed until the VCM beeps)

Congrats, You are now on the hacked recovery firmware. You should be able to cross-flash to Ford/Mazda/Landrover/whatever after changing the module type to an appropriate value. Same goes for serial number changes.

As of right now I don’t see a reason to modify the production firmware that normally boots as everything we are trying to accomplish can be done in recovery.

 

Download: VCM2 FW 20151219

https://mega.nz/#!IFJznTpb!4EQRcpXggxp148Qhr_VUb4aYuIEZaL...

BIG THANKS to ColtB45