Yes, but as you hopefully can imagine there is a very good reason why it's one-way by default: since OData is a server-side model, each update you do will fire a request to your backend, and that may have a big impact on performance!
Only use two-way ODataModel binding for very specific usecases, and leave it one-way for everything else