Quote:
Originally Posted by clueless25
Dont know if this matters, but I did a manual installation and found I got the same message. When reading over at XDA.. found that turning off sense then installing it, turn sense back on was the trick..
Since this is cooked in. Shouldnt break anything.. turn off sense, try and start it, then turn it back off, then sense back on.. Not sure if that would make it read properly or not.
|
This doesn't work with the cooked in version. However, downloading the 1.6 version from cookie's thread and installing it, then disableing sense to run it... did. Don't know if I had to disable it but no way to check now. Afterward, delete the shortcut the new install made in the start menu using the file explorer or total commander and you can run it as normal from the tools folder without disableing sense.