Sorry there must me some other evil leftover im not able to see without plugging an SX mod in here, but i thought the registry keys we nixed would have done the job...weird....
If you like im happy to teamviewer later and have a look. Up to you.
For those playing along at home or wondering how this panned out, after some teamviewering and using an earlier version of the SX software, the OP was able to get the SX connected and updated to the latest firmware
I remoted in and forensically removed the remaining traces of registry keys that werent in the regscanner
report i got from him the other day and made the custom NSudo + reg remove script for, there were still some entries pointing to the oemX.inf files (where X is an the (incremental number windows gives to custom driver infs when you install them)), i then removed the remaining oemX.inf files and tried reinstalling the latest SX software on the page...it failed...couldnt connect to device. So i thought wonder if an early version would work? He had tried it but not with the reg and file detritus removed.
So then i removed the SX software, and removed the reg and oemX.inf files left over, again.
Then downloaded the above version, and we had a connection. Then tried the upgrade to the latest firmware, and it went though.
Great job!
Sometimes poor programming is helpful when you need to force a firmware on a device. Good thing YiHi keeps old versions of the software on the site.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.