First off, you don't appear even to have well-formed, let alone valid, XML markup there.
Your other problem appears to be that you have character encodings set improperly.
You don't describe clearly how you are passing the XML content from client to server or from server to client.
If you create HTML files, you should give a <meta> element that specifies the character encoding and then make sure the file is saved as that encoding for serving it from the server. Similarly if you prepare XML markup from form data with Javascript, you should encode properly any characters outside the typical ASCII format.
On the server side, it should transmitting to you well-formed and VALID XML. Those byte codes (\u0022) are what you might use to prepare a URI for clean transmission, but they are not for XML.
If you transmit server->client and client->server valid XML, you should be able to immediately use DOM manipulating functions to access and traverse nodes using DOM (including XPath) functions. On the client side, you can use DOMParser on received XML within Javascript. On the server side, PHP also has an object for manipulating valid XML received from the client.
In fact, I make it a point NEVER to use the string/text such as the .responseText property of the XML HTTP request object when I know the object sent is valid XML. I ONLY use the .responseXML property, because if that property is NOT presented to me (that is, its value is null or undefined), it is NOT valid XML. If you get the file not using the XML-HTTP request object, you can see if it builds using the DOMParser constructor: if it does not, it is NOT valid XML.
You have an error in coding of your web application if it is generating encoded bytes in your XML markup. You should address that first.
You should also review the code generating all your XML markup and make sure it validates. You will have to learn how to make DTDs at a minimum: don't worry, they're easy to learn, and if you don't want to learn, you can buy or probably get for free programs which will look at your WELL-FORMED but NOT valid XML markup and generate a DTD for that particular markup (just search "DTD generator"). I recommend that you learn how to make XML Schema instead of DTDs if you want to be even more careful about the validity of your XML markup. (there are probably XML schema generators you can buy or get for free too, but using these generators might take away the fun from learning)
On your HTTP client, for testing/debugging purposes, you can use the native developer tools in Chrome and latest IE version, but I still use Firebug extension in Firefox. Under the Net tab, you can see whether XML objects were parsed as valid, since it shows an XML tab in HTTP responses if they are valid.
Post the relevant parts of your code to see why you are encoding quote characters and getting \uXXXX in the output. Make sure that your HTTP headers have the proper Content-Type header set. Make sure that client encodings (<meta>, <form> elements) are set properly. If you are using XML-HTTP Request Object, you should set the request header "Content-type" too. Make sure that when you save PHP and HTML files, it is with the proper encoding. I recommend UTF-8 without the byte offset marker (BOM) in everything you do. All editor applications (Notepad, I use RJ Text Editor!) have the easy ability to save in UTF-8 without BOM.
Give us a look at how you are passing data back and forth between server and client and back.