V139 JLR Mangoose SDD Pro
I purchased this from UODB2 and have struggled with the software install. First the initial install file (SDD_DVD139_FULL) was corrupted. After trying the install twice I contacted UODB2 and they gave me a link to download the file. I uninstalled everything and started over. I have installed it completely twice and I noted that when the patch file ran it displays a message box at the end that is blank. It should show "License Finished"
After installing with the uncorrupted file but getting the blank patch message I connected it to the car. It was able to connect but when it got to the serial number download it gave a message that the computer must be connected to the internet, if you don't have a network connection insert a usb key. It wants to write an exe to the usb key so it can be run from an network attached computer and then it will write back to the usb key so you can import the data to the non-connected PC.
I suspect the patch file is corrupt but being as they are closed for the Chinese holiday until Feb 27th I thought I would throw this out and see if anyone had a good working patch that could be shared.
This version is supposed to be able to be run from Win7 and good for cars up to 2014.
After installing with the uncorrupted file but getting the blank patch message I connected it to the car. It was able to connect but when it got to the serial number download it gave a message that the computer must be connected to the internet, if you don't have a network connection insert a usb key. It wants to write an exe to the usb key so it can be run from an network attached computer and then it will write back to the usb key so you can import the data to the non-connected PC.
I suspect the patch file is corrupt but being as they are closed for the Chinese holiday until Feb 27th I thought I would throw this out and see if anyone had a good working patch that could be shared.
This version is supposed to be able to be run from Win7 and good for cars up to 2014.
Last edited by rickpwilson; Feb 16, 2015 at 10:44 AM.
Just to close off this thread. After installing on various platforms and having no luck I contacted the vendor and they sent me a new patch file which solved the problem. I now have SDD running on a Windows 7 box under the XP Mode virtual machine.
Last edited by Don B; Mar 14, 2015 at 10:15 AM.
Hi Rick,
Thanks for reporting back. Please let us know if V139 functions well since many other members have been interested.
Cheers,
Don
Could you by chance share the patch file? I am trying to install v139 on my old XP laptop but avast didn't like the .exe in the patch folder so I think I need to find a clean one for v139.
Thanks!
Thanks!
You have to disable your anti virus when you download or execute the patch file or it will quarantine the patch file.
With the amount of time I spent on the V139 loading and reloading I would try the version supplied first. My guess is the patch file is written for the specific version supplied but I am not 100% sure of that.
Trending Topics
I'm trying to run the same on a Windows 7 laptop and not having much luck...it will connect to the car but when I try to run anything a 'program running' circle comes up and just stays there...let it go for 25 minutes twice and still didn't load
guess I'll have to try the vendor too. I'm not sure I have enough ooomph in the little laptop to run XP virtual.
guess I'll have to try the vendor too. I'm not sure I have enough ooomph in the little laptop to run XP virtual.
I'm trying to run the same on a Windows 7 laptop and not having much luck...it will connect to the car but when I try to run anything a 'program running' circle comes up and just stays there...let it go for 25 minutes twice and still didn't load
guess I'll have to try the vendor too. I'm not sure I have enough ooomph in the little laptop to run XP virtual.
guess I'll have to try the vendor too. I'm not sure I have enough ooomph in the little laptop to run XP virtual.
There are a workaroung, but you will need to reinstall a SDD.
Sure it could be used. 140+ versions works just great.
I have used a 'patch' that works on both v137 and v138 but it worries me that one of the files it replaces (app.war) is half the size of the original so makes me wonder what the differences are. Does it make the app unstable?
More and more functionality is going on-line as well. Access to the TSB's was lost a few versions ago and, although I haven't tried it, v139 supposedly moves the DTC help information in to the cloud as well.
v138 seems to be the sweet spot for me as it has a lot of short cuts and functionality compared to the earlier versions but still has DTC help.
Out of interest has anyone got a version of SDD working in a virtual Windows XP PC on a host that is running Windows 8.1? My virtual PC doesn't seem to see the Mongoose any more but it worked OK on a host running Windows 7.
More and more functionality is going on-line as well. Access to the TSB's was lost a few versions ago and, although I haven't tried it, v139 supposedly moves the DTC help information in to the cloud as well.
v138 seems to be the sweet spot for me as it has a lot of short cuts and functionality compared to the earlier versions but still has DTC help.
Out of interest has anyone got a version of SDD working in a virtual Windows XP PC on a host that is running Windows 8.1? My virtual PC doesn't seem to see the Mongoose any more but it worked OK on a host running Windows 7.
Changed app.war makes some functions of SDD unavailable 
As for online functions - there's still workaround. You won't be able to view TSBs, but DTC help, keys programming and other stuff will work fine with a correct "crack" (actually not a crack, but authentification).

As for online functions - there's still workaround. You won't be able to view TSBs, but DTC help, keys programming and other stuff will work fine with a correct "crack" (actually not a crack, but authentification).
Thanks Mr. MoscowLeaper, I'm not sure - is that part of the SDD program or part of the install? I had an IT friend do it, took him much longer to install that he thought.
It takes a long time, since a SDD in big program with a lot of files...
Been trying to work out some transmission issues while getting v139 installed. After several aborted attempts, I got a version installed that could read diagnostics, but seemed to fail to allow any service adjustments.
1. Getting vehicle data as is requires an internet connection. Should we allow that ?
2. I got an error on one file copy during install related to horns.xxx? Otherwise install went OK. Others get this? Where can I get another copy of v139?
3. Running the patch license file, completes ok. However after running it only, the connection errors after reading the VIN.
In the PATCH directory, I saw there were two hidden directories. One has some files that say to be copied to jlr/ids and jlr/runtime.
After I copy these, then I can read the VIN, and run full system error diagnostics, but not run any adjustments.
4. Can the patch file execution run with the v141 version?
Nothing seems to be quite as simple as it should be...
Have tried this on xpmode on win7, as well as trying VMware.
VMware has the advantage of allowing more CPU usage. Xpmode only allows 1 CPU.
Appreciate any additional guidance and help.
1. Getting vehicle data as is requires an internet connection. Should we allow that ?
2. I got an error on one file copy during install related to horns.xxx? Otherwise install went OK. Others get this? Where can I get another copy of v139?
3. Running the patch license file, completes ok. However after running it only, the connection errors after reading the VIN.
In the PATCH directory, I saw there were two hidden directories. One has some files that say to be copied to jlr/ids and jlr/runtime.
After I copy these, then I can read the VIN, and run full system error diagnostics, but not run any adjustments.
4. Can the patch file execution run with the v141 version?
Nothing seems to be quite as simple as it should be...
Have tried this on xpmode on win7, as well as trying VMware.
VMware has the advantage of allowing more CPU usage. Xpmode only allows 1 CPU.
Appreciate any additional guidance and help.
Been trying to work out some transmission issues while getting v139 installed. After several aborted attempts, I got a version installed that could read diagnostics, but seemed to fail to allow any service adjustments.
1. Getting vehicle data as is requires an internet connection. Should we allow that ?
2. I got an error on one file copy during install related to horns.xxx? Otherwise install went OK. Others get this? Where can I get another copy of v139?
3. Running the patch license file, completes ok. However after running it only, the connection errors after reading the VIN.
In the PATCH directory, I saw there were two hidden directories. One has some files that say to be copied to jlr/ids and jlr/runtime.
After I copy these, then I can read the VIN, and run full system error diagnostics, but not run any adjustments.
4. Can the patch file execution run with the v141 version?
Nothing seems to be quite as simple as it should be...
Have tried this on xpmode on win7, as well as trying VMware.
VMware has the advantage of allowing more CPU usage. Xpmode only allows 1 CPU.
Appreciate any additional guidance and help.
1. Getting vehicle data as is requires an internet connection. Should we allow that ?
2. I got an error on one file copy during install related to horns.xxx? Otherwise install went OK. Others get this? Where can I get another copy of v139?
3. Running the patch license file, completes ok. However after running it only, the connection errors after reading the VIN.
In the PATCH directory, I saw there were two hidden directories. One has some files that say to be copied to jlr/ids and jlr/runtime.
After I copy these, then I can read the VIN, and run full system error diagnostics, but not run any adjustments.
4. Can the patch file execution run with the v141 version?
Nothing seems to be quite as simple as it should be...
Have tried this on xpmode on win7, as well as trying VMware.
VMware has the advantage of allowing more CPU usage. Xpmode only allows 1 CPU.
Appreciate any additional guidance and help.
SDD itself runs fine on a x86 Windows7, even w/o a xpmode. Never had any problems with any version from 115(it was an IDS) and up.
Unless your car is 2012, there is no need to have such a new version that needs hacks to work, you could use an older version that will run without being hacked. e.g. V129 or V130.
There are no updated files/functionality for the older models in the latest updates anyhow.
There are no updated files/functionality for the older models in the latest updates anyhow.
I bought a Mongoose Pro cable with 139 software froma Taiwan supplier suggested in a older post.
The Mongoose driver didn't load on my Win7 64 bit system. The vendor told me to use an XP OS. I tried. The driver loaded on the XP system but the SDD said the software won't load on this OS.
Any suggestions on solving this or where I can buy replacement software at a reasonable price that will actually load and work?? The total lack of documentation - such as system requirements - and then false solutions that don't work - is a real stumbling block for me. I'm not a computer expert.
The Mongoose driver didn't load on my Win7 64 bit system. The vendor told me to use an XP OS. I tried. The driver loaded on the XP system but the SDD said the software won't load on this OS.
Any suggestions on solving this or where I can buy replacement software at a reasonable price that will actually load and work?? The total lack of documentation - such as system requirements - and then false solutions that don't work - is a real stumbling block for me. I'm not a computer expert.








