[Android] BigCountry907:
I know this stuff gets confusing fast.

I will try to explain a little different.

This is 100% correct.

One thing, I'm pretty certain of, RUUs will go through (at least) the following checks:

1.MID -> if wrong -> MODEL ID NOT ALLOWED

2.CID -> if wrong -> CID NOT ALLOWED

3 .version-main -> if not properly edited before -> Main version NOT ALLOWED

To work around MID: change or remove theese lines in meta.inf updater script

assert(check_mid("full", "0PM911000") == "t");, this is the MID "0PM911000"

To work around CID: change or remove theese lines in meta.inf updater script

assert(check_cid("00000000", "11111111", "22222222", "33333333",

"44444444", "55555555", "66666666", "77777777", "88888888", "99999999",

"METRO001") == "t");

It is probably necessary to change these lines in the lines in meta.inf updater script to downgrade roms.

ui_print("Verifying current system...");

getprop("ro.build.fingerprint") == "htc/a32eul_metropcs_us/htc_a32eul:5.1/LMY47O/637541.3:user/release-keys" ||

getprop("ro.build.fingerprint") == "htc/a32eul_metropcs_us/htc_a32eul:6.0.1/MMB29M/774853.1:user/release-keys" ||

abort("Package expects build fingerprint of htc/a32eul_metropcs_us/htc_a32eul:5.1/LMY47O/637541.3:user/release-keys or htc/a32eul_metropcs_us/htc_a32eul:6.0.1/MMB29M/774853.1:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");

So that will take care of the first 2 checks. By Editing the Updater-script.

This I need to research, I'm not familiar with the process.

You can change version-main, by editing the misc partition...

What are the Android_Info .txt and Android_info2.txt ?

I mean how are they used by the RUU.

Example of android info 2

modelid: 0PM911000

cidnum: T-MOB010

mainver: 1.23.531.3

aareport:1

btype:1

Can those be edited to match my current device. ( Not considering the signing issue )?

AS FAR as Signing

Changing anything in an RUU will break HTC signature -> no go -> and you cannot "fake it", stock recovery has nothing to do with it

You cant fake it is true, you can't get the HTC Private Key Either.

But you can make your own keys.

Same as here.

https://source.android.com/devices/tech/ota/sign_builds.html

Which specifically says

before installing a package, recovery will verify that it is signed with one of the private keys matching the public keys stored in the recovery partition, just as it would for a package delivered over-the-air.

Update packages received from the main system are typically verified twice: once by the main system, using the RecoverySystem.verifyPackage() method in the android API, and then again by recovery. The RecoverySystem API checks the signature against public keys stored in the main system, in the file /system/etc/security/otacerts.zip (by default). Recovery checks the signature against public keys stored in the recovery partition RAM disk, in the file /res/keys

So to beat the signing you have to create your own keys.

Then you put the public half of the key in the /res/keys file replacing the HTC key.

Now simply sign the final zip package with the Private key you created.

Flash the modified recovery using Fastboot Flash recovery recovery.img

Load the rom off the SD card or using fastboot.

It should pass the signature verification.

When I get home tonight I will try this out.

You cant hurt the phone flashing the recovery.

If it don't work its easy enough to flash again.

I'm not worried about my phone.

If I brick it I'll fix it.

I use it just for testing.

I'm trying to find a way to help people flash the RUU they need without s-off.

You never know what it could lead to. Maybe find a new way to s-off.

At any rate I'm thinking I'm going to by the xtc2 clip.

Can do a lot with it and for the money its not bad.

I just wonder if it can unbrick a hard bricked phone.

I only worry about flashing the Bootloader and the Radio.

If they get messed up is there a current method to recover the device.

Can that clip do it?