Where to free download Xprog V6.12 ECU programmer? https://share.weiyun.com/5m5Vkw0 Password: fxo5qz Software version: V6.12 Firmware version: V4.4 Language: English
windows xp, win7 & win8 works
What's new of Xprog V6.12 hardware?
1. Brand new hardware, run more stable and faster
2. add 2 new authorization & 4 new adapters:
AUTH-0028-3 Renesas RL78
AUTH-0028-4 Renesas M32C)
How to install Xprog V6.12 software? Tips:
1. Not compatible with older version Xprog.
2. Uninstall the older version Xprog before installing Xprog V6.12 software.
2. Uninstall all anti-virus software in your computer.
3. No internet connection.
4. Not support update.
Procedure:
1. Click on the file "installation.reg", get the file information to the regedit.
2. Install the file "AdbeRdr11000_zh_CN.exe", it is a must, otherwise, the Xprog software will not start.
3. Plug the Xprog main interface to the computer, install the USB driver.
4. Copy the folder "XPROG-BOX6.12" to the desktop, and open it, and run the "xprogdesktop.exe", then software open.
Need: looking for Iprog+ clone eeprom cable pinouts, because sprog only shows pin numbers.
Actually, theIprog+ clone software comes with the eeprom cable pinouts.
After installing Iprog+ clone V80 software, click on one menu option, then chip type, then "Description", you will see the wiring diagram (shown as below).
Image of main menu:
As you can see, it has a wide range of capabilities besides eeprom.
1. Airbag:
Read and erase crash to some cars
Read and erase DTC
Repair CFG
2. Dashboard:
Read km
Write a new km
3. Car Radio & ECU:
Car Radio:
Read and erase info
Reset count
ECU:
Immo OFF
DPF off
4. Eeprom:
Read/ write/ erase eeprom
5. Immo:
Program and copy chips for cars and truck
Unlock keys
Cover Toyota smart keys: reset key prepare
Write a key by immo dump
6. MCU:
Read and write chips
Cover chips Atmel, Fujitsu and microchips Motorola, NEC v850
7. Special functions:
Mile to km
Pincode from dump
Test reports:
1. Tested this morning 2.53 ok reading audi a3 ppd ...
2. Tested on WIN7 32bit and it's working fine.
I've read with KESS, a MED17.5.5 by OBD and i'll try a BDM read/write with KTAG tomorrow and I'll share my experience.
Question: Access violation error. SW does not work. DLL folder is just 2mb instead of more than 9mb.
Finally. I just put file i c: and all solved. It works for kess. not k-tag at the moment
Question: Is it reliable? Suggestion: Did BDM Backup, test via K-Line / OBD.
So you can back up if the problem is there.
Review 1. EDC16 should be no problem for kess.
Review 2. No problem with Kess v2 EU -> read/write
Yesterday tried with one of my friend's B6 and read write through OBD no problem.
I use an external battery as a backup for the car's voltage it holds 12,35 - 12,4 volts stable.
After writing waiting about 3 minutes until the start.
Strange this ECU could be set how much success read/write you enable.
First BDM after OBD easy job I think but needs to be careful always
Review 3. today I use Kess V2 read one of my old U31 (it is T5 2.5tdi but unimportant) Kess and Ktag work.
Offer the possible reasons and solutions to KESS V2 5.017 error "EXTERNAL EXCEPION EEFFACE".
It is normal for the computer to detect as USB device:
I tried with v2.23, v2.25 and v2.47. All the same error.
I can't replace NXP, but I can try to replace SD card.
See how everyone has suggested how to solve this problem: Advice 1. Plug it in and uninstall the 'usb device' from the device manager then unplug the device. Install drivers usbdevicedrv that comes with the correct version for your kess/Ktag. Once complete, plug in Kess and allow drivers to install and run ksuite (with internet disabled)
Advice 2. You need to create a new 5.017 SD Card Image by using the "ImageUSB-tool" program.
Remove SD-card from kess
Format SD-card Fat32
Burn 5.017 img. file to SD-card using imageUSB-tool (everything you need is on MHH forum)
Put SD-card back in to kess.
Works perfect for mine kess!(same problem)
Note: Only Kess 5.017 or 5.028, not for 3.099 etc.
2). How to create a new SD card?
Firstly, download WinHex and XorFiles v1.0 http://www.nirsoft.net/utils/xorfiles.html
Insert your Original SD-Card to Cardreader on PC.
Run WinHex, press F9 open Disk, read your SD-card.
Mark 208Bytes = 13 lines from 0x00000270 to 0x0000033F.
Copy 13 lines to a new file.
Open in WinHex my Keyfile “128 MB XOR Key01-13.img”
Search and replace line 1 in your Keyfile with all line1 lines in “128 MB XOR Key01-13.img”
Search and replace line 2 in your Keyfile with all line2 lines in “128 MB XOR Key01-13.img”
….............................
Search and replace line 13 in your Keyfile with all line13 lines in “128 MB XOR Key01-13.img”
Save your new 128 MB XOR Key01-13.img
run XorFiles v1.0
Filename 1: = your original SD-Imagefile
Filename 2: = your new createt “SD128 MB XOR Key01-13.img” (with your 13 lines ;-)
Destination: = any filename for your new uncryptet Imagefile
if you have decrypted the files, you can integrate the decrypted image file with "ImDisk Virtual Disk
Driver" as a virtual drive and save the files to the PC.
Link to ImDisk https://sourceforge.net/projects/imdisk-toolkit/
If you want to use any new SD-Card in your Kess 5017, use Winhex to fill the SD-card with 00.
put SD-card in Kess, power on Kess.
The 13-line KEY = 208 Bytes is x times on the SD.
From 0x000000D0 it is on some empty SD cards.
If you not found search any other line.
It is important that from line 0 always the 13 lines are
13, 26, 39, 52 ..... 4160 ..... 344032 etc.
that is, 0x0001040 is in decimal 4160,
13 rows = 208 bytes,
4160 divided by 208 = 20
Or 53FE0 = decimal 344032
344032 divided by 208 = 1654
that means if you think you have found the key you have to divide the address (decimal) by 208
without anything after a comma.
then the start same Procedure to create a new “SD128 MB XOR Key01-13.img” file with new SDCard
Key.
Format the new SD-card with FAT, copy Files to SD-ard and crypt it with “XorFiles v1.0”
Guys if I understand correctly fgtech 0386or 0475 is the firmware of the micro.e you can do update or change the pcb ???
0386 is ok on SW china,0475 is ok on sw eu....
Reply:
v48 is 100% not possible to use with fw from v53...this is reality because the hw is totally different...if you want to reprogram lpc you can (if you know how on v48) but the functionality from v53 are not available on hw v48
To agree the above option:
Yes, update the firmware to 0475. fgtech 0475 is more clean and stable, in combination with a rework pcb (Armageddon΄s list, few pages back)!!
Question: Is possible to use 90% of v53 functionality, just jtag not possible because obviously hw is missing. Answer: But full working OBD, and BDM updated support to v53 is possible.
Question: ok then pcb changes from v48 to v53 / 54. anyone has a picture of 2 pcb ??
Answer: Maybe you don' t understand,
about pcb:
we change the bad components of china v54 pcb with better quality (components).
v48 is different pcb and it can' t be same with v54...
0475 is the firmware-software and cooperates flawlessly with v54 pcb.
photo v54
Question: now I read that it should be done hw rework and downgrade to sw v53.
Answer: v48 it's no longer on the market. only v54. "simply" rework the components of v54 pcb (hw) and update the firmware from 0386 to 0475 if needed, because sοme sellers (obd2shop.co.uk) have already the fgtech 0475.
of course we need and good luck with these china copies...
Here is the FGTech 0475 PCB (sold at obd2shop.co.uk):
