Fixed team tests.

Having *$routeParams* in a service is a layering violation and angularjs appears to make it so is not available in services. So when you were asking for it to be injected you got an error (at least in tests, have not tried it live).

I have cleand the way your are working with $routeParams quite a bit and it should make the code better and testable without mocking $routeParams. 
If you look now values of the $routeParams are extracted and passed to the resources service, it may have also worked to jusst pass the $routeParams object in itself but that might have unintended side effects / open holes in the API.