First, I want to echo milinpatel17 's answer.
If they are not cooperating NOW, at the start of the process when people should be psyched about it (see http://www.1000advices.com/guru/project_mgmt_7phases.html ), how would they be a few month into the project?
Specifically to your question: If you give them the scripts you now run manually, you will get an automated version of the scripts. But this is not efficient and not scalable. What you want is to re-think the test strategy with automation in mind. Think of types of actions you need automated (later, a number of actions will be put together into tests). This way the automation framework will be more modular, and allow you to bundle a number of action calls in a row into a test.
Think also in term of flows: The automation system should help you create possible flows through the system. Some of these flows are the tests you already have. But you don't have a whole lot since scripting flows for manual testing take a long time. If your automation system has flow building blocks (these are the "actions" mentioned above), and a way to specify a number of these via a text file, you now have a way to create many more flows than you had before, and can find all kind of assumptions the developers did on the order in which things HAVE to be in order to work well.
I like to compare your situation to Disney's "the sorcerer's apprentice" (https://www.youtube.com/watch?v=T8gOh0wEgLg). Is moving water from one place to another is best done with - albeit automated - pails? Automation allows you to think of totally different ways to achieve the same result. A pipe and a pump for example - which is way more efficient.