if you are not using the same environment, you cannot help.
Well, not really true. If you can explain your environment, then help can often be given.
However, you didn't even bother to tell us your environment. We had to drag it out of you, kicking and screaming. That took a month.
To go back to the broken car analogy, you called a mechanic and refused to tell him what kind of car you have, and got mad that he couldn't repair it over the phone. And you left out the most important part - it's electric. And, BTW, the mechanic is working for free.
There is nearly no MVC4 experience here, and that I've seen very few reports of MVC4 success with jQuery Mobile. If you are attempting to make this combination work together, I suggest you seek-out advice from MVC4 forums, where you will most likely just commiserate with others who find themselves in the same boat.
I think that what has happened here is that Microsoft stuck JQM in a package in a rushed way with inadequate documentation on how to make the two play well together. The same has happened with an IBM product (Worklight) and an Adobe product, with the result being that their customers come here expecting help.
Hopefully, they will clean-up their documentation to show how to make the products work together and explain the limitations. (Not that JQM documentation is anything great...)