[AT&T, Rogers HTC One X, Telstra One XL] cafonez:
After many hours of unsuccessful rooting attempts here is what I have come to the conclusion of :

If you take the files from the temp directory that the ruu places in there and use the Aruwizard directly I noticed you cannot edit the rom zip due to the signatures, however you can extract the zip and then rezip it, and then replace the original rezip and when aruwizard is run again I believe it actually resigns the zip b/c you cannot add files again to the newly made zip.

I also noticed that by changing android-info.txt with something like this "modelid: PJ8310000cidnum: CWS__001hbootpreupdate:3mainver: 2.30.502.3 DelCache:1" the aruwizard.exe will indeed try to write the new files and rom.zip to the phone. This is where I get stuck. It does the phone connection, message stating you'll see the phone reboot wait ten minutes bla bla part .. then on the waiting for boot loader ...... ...... it keeps hanging at a HTC screen with grey htc and white outline. I also tried changing the cws line to be 1's for su but it didnt work.

During this part I figured the phone might be writable so just to mess around I kept running different .bat files that attempt to push files to the phone to make root and in 1 of the 5 different times I tried, beaups script connected and tried to push the files. It appeared almost as if the files had gotten onto the phone then in the ruu log I got this

<LOG>

<T175817><INFO><VERSION>1.0.6.2012</VERSION></INFO></T175817>

<T175817><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>

</DEBUG></T175817>

<T175825><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>

</DEBUG></T175825>

<T175825><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175825>

<T175826><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175826>

<T175826><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175826>

<T175828><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175828>

<T175828><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175828>

<T175829><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175829>

<T175829><DEBUG><CMD>adb -s HT********* shell cat /sys/class/power_supply/battery/capacity</CMD>

</DEBUG></T175829>

<T175830><DEBUG><OUT>93</OUT>

</DEBUG></T175830>

<T175830><DEBUG><PAGE>====== VerificationDlg ======</PAGE>

</DEBUG></T175830>

<T175830><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175830>

<T175831><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175831>

<T175831><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175831>

<T175832><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175832>

<T175832><DEBUG><CMD>adb -s HT********* shell getprop ro.build.description</CMD>

</DEBUG></T175832>

<T175834><DEBUG><OUT>2.20.502.7 CL79936 release-keys</OUT>

</DEBUG></T175834>

<T175837><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>

</DEBUG></T175837>

<T175837><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175837>

<T175838><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175838>

<T175838><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175838>

<T175839><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175839>

<T175839><DEBUG><CMD>adb -s HT********* shell getprop ro.build.description</CMD>

</DEBUG></T175839>

<T175840><DEBUG><OUT>2.20.502.7 CL79936 release-keys</OUT>

</DEBUG></T175840>

<T175849><DEBUG>MainVer: %s2.30.502.7

</DEBUG></T175849>

<T175855><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>

</DEBUG></T175855>

<T175856><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175856>

<T175858><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175858>

<T175858><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175858>

<T175859><DEBUG><OUT>List of devices attached

HT*********	device

</OUT>

</DEBUG></T175859>

<T175859><DEBUG><CMD>adb -s HT********* shell /system/bin/reboot oem-78</CMD>

</DEBUG></T175859>

<T175901><DEBUG><OUT />

</DEBUG></T175901>

<T175901><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175901>

<T175902><DEBUG><OUT>List of devices attached

</OUT>

</DEBUG></T175902>

<T175902><DEBUG><CMD>fastboot devices</CMD>

</DEBUG></T175902>

<T175903><DEBUG><OUT />

</DEBUG></T175903>

<T175904><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175904>

<T175905><DEBUG><OUT>List of devices attached

</OUT>

</DEBUG></T175905>

<T175905><DEBUG><CMD>fastboot devices</CMD>

</DEBUG></T175905>

<T175906><DEBUG><OUT />

</DEBUG></T175906>

<T175907><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175907>

<T175908><DEBUG><OUT>List of devices attached

</OUT>

</DEBUG></T175908>

<T175908><DEBUG><CMD>fastboot devices</CMD>

</DEBUG></T175908>

<T175909><DEBUG><OUT />

</DEBUG></T175909>

<T175910><DEBUG><CMD>adb devices</CMD>

</DEBUG></T175910>

<T175911><DEBUG><OUT>List of devices attached

</OUT>

</DEBUG></T175911>

two ideas, one is someone who might be really good at programming might be able to manually alter the ruu, reconstruct the dll's its using and figure out what commands its pushing with the dlls b/c Im thinking the ruu can write/modify the phone. all it takes to trick the wizard to do an attempt to install is by modifying the version of mainver for it to make the effort.

I am assuming once it sees the keys do not match, it sends the signal for the phone to hang at the htc screen b/c the log shows its trying to see fastboot devices but the phone never comes back. I had even changed the names in the rom.zip after extracting to try and make it look like a higher hboot to rewrite the older hboot and hex edit them as well with fake version numbers. It did not alter the file size of the renamed files that were hex edited when I rezipped them. the zip file changed by a few bytes, but even so I think the ruu may have resigned the zip itself b/c it was not longer able to add new files to the zip after one attempt of the aruwizard.

If someone found a way to completely reassemble the ruu there might be command switches to turn S-OFF and bypass CL key check. I tried to also force the phone to connect to att update over my computer but apparently I now have to wait 23 hours before I can make the attempt again, dont know if I tried to many times but im trying to sniff the strings that go back and forth.

If anyone has any ideas let me know. if this has been tried before i apologize, just trying to think outside the normal box.