Database Users

MAGIC - 32A - S-ON (Signature Verification ON) & Memory Card not accepted now

I am getting similar problems as this user
http://forum.xda-developers.com/showthread.php?t=664124
But in my case i am having my radio and spl is correct.
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
Radio: 3.22.20.17
Click to expand...
Click to collapse
I have access to fastboot and recovery so far
I have tried many firmwares in this radio as well as 6.xx radio new one. Had no problems so far. I was running a ROM on this radio itself. Then i wished to switch back to cyanogen latest. So i wiped and tried flashing the following
1/ flashed first - defaged firmware
2/ updated cyanogen 15.1 over it
3/ flashed the port of 32A
After this on booting, phone was stuck @ htc boot screen. So i again came back to recovery, and tried flashing again. This time it said a signature fail on defaged firmware file as well as other files in it.
Tried few times and still same issue.
Tried formatting sd card mounting on phone - recovery usb. but then after that it is no more detecting. I tried partitioning fat32, ext2-512mb, swap 32mb, manually through paragon and put again, still memory card not detecting. I get similar errors
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
Click to expand...
Click to collapse
Just to know if it is a recovery issue, tried updating recovery in fastboot mode.
I get a similar error as below
INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
This is when i noticed, the S-ON on top, my phone signature verification was off, that is before all this my fastboot said
SAPPHIRE PVT 32A ENG S-OFF H
Click to expand...
Click to collapse
I dont know how it went from S-OFF to S-ON. And that is the reason why fastboot was not accepting anything
Then to update recovery i did adb push to /sdcard and then flashed from there. And then i got my recovery updated to 1.6.2. This confirms somewhere phone is able to write to memory card through adb, but i cannot use recovery to flash from it. memory card has no prob neither phone hardware
Still no use, memory card is not detected + cannot flash files.
My current scenario
-- my radio and spl is correct, i have recovery lates 1.6.2
-- phone has no rom now
-- i can access fastboot and recovery
-- my signatures - S-ON so cannot use fastboot to flash anything
-- memory card not detecting, tried 1-2 memory cards. All detecting on pc

didnt you forgot to flash samming.img? BEcause without that, it wont turn off. Try flash again, use a gold card if doesnt work. Download from here:
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
hope it helps

I did not forget to flash that, it was not something i wanted. My phone was a completely rooted phone with everything running perfect. I was just reinstalling cyanogen from start.
Regarding goldcard, I couldnot find my sdcard CID, so could not create it.

create a new one. Create gold card from the recovery option. You can coonect your SD card to your computer with the phone in recovery mode, there is a MS Connect menu, select that one. you can get the CID and do the process again.
If i were you i would run HTC update from a SPL edition wich would be able to root and do all over again for safe keeping.

how to create gold card from recovery ? my memory card is anyway not mounting on recovery now
regarding getting cid, on memory card reader i couldnot get cid, maybe my card reader is not worth providing such info
thirdly, i have tried updating using original ruu, it fails in the stage of update where it says rebooting into bootloader.
I tried the same in fastboot mode, normal mode and recovery. Nothing works, except 1 change that in fastboot mode, it turns the phone to stuck at the fastboot screen and i have to pull out battery.
Any other options ?

before starting the phone, you press Power+Home, and you'll have the custom recovery option right?
There is a option called: "USB MS-Toggle" activate it , From that option you can get a CID without any problem and recover everything

have you tried a G1 method?
http://www.krishnendu.com/my-g1-android/rooting-my-google-g1-htc-dream-t-mobile-uk-edition_137.html

jgcaap said:
before starting the phone, you press Power+Home, and you'll have the custom recovery option right?
There is a option called: "USB MS-Toggle" activate it , From that option you can get a CID without any problem and recover everything
Click to expand...
Click to collapse
I dont know whether its my english that u r nt following or you dint read my post carefully. i had mentioned in my posts that it is not mounting my memory card. In recovery when i do that i get an error
Can't mount /dev/block/mmcblk0
.......................

oh sorry . My english sometimes tricks me. the issue you are passing, there is sure a way out. Could you describe the exacly process you used for installing CM please?

jgcaap said:
oh sorry . My english sometimes tricks me. the issue you are passing, there is sure a way out. Could you describe the exacly process you used for installing CM please?
Click to expand...
Click to collapse
Just as we do any flashing. put to sd card and flashed through recovery in this order(PLZ READ MY FIRST POST COMPLETELY)
1. defaged firmware
2. cyanogen latest update over it (without rebooting)
3. 32A port

what did you had before as radio ? Hboot? Etc
Have you tried to download a oficially signed from HTC Hboot and in fastboot flashing it ?

try the following to see if works.
1)Link your Phone to your computer, run it in fastboot mode.
2)Run a HTC update (choose anyone)
3)Click next until the update confirmation part.
4) run %temp% and you'll find Rom.zip and rom1.zip , copy to a folder and unzipit. Close the update app.
5) collect the following files:
userdata.img
system*.img
Splashe*.nb0
recovery.img
radio.img
hboot*.nb0
boot.img
(The ons with * are the version of the following update you are applying)
6) Zip to a samppimg.zip, put on the SD card and enter in HBoot mode (Volume down+power)
PS: i dont know if works, and it might become worst but try at your own risk. Never passed throught that situation. Last optiion read: http://forum.xda-developers.com/showthread.php?t=655097 and follow the JTAG Hack option. I Dont know any other way.

please post here exacly what you have done:
http://forum.xda-developers.com/showthread.php?p=6243163#post6243163
Lets hope to try to see what we can do.

Can't install RA recovery onto rogers magic - please help

I am using this website, and am at step 6. Everything up to this point has been going well, but i cannot get the recovery image to copy over. BTW I have the recovery-RA-sapphire-v1.7.0H.img file i'm using. When I type to push the file to the SDcard, it says, the transfer failed because the file system is read only.
How do I fix this? I've restarted the phone, taken the SD card in and out, i've typed adb remount, and nothing is working.
. Open command prompt and go to the Tools folder in Android SDK that you downloaded to create the gold card.
Assuming that you have not changed the file name of the recovery, use the following commands:
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img (file name of the recovery you downloaded)

OK, i've got that working, now another problem...
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img (file name of the recovery you downloaded)
7. After the recovery has been flashed, go to the following link to download the ENG SPL for HTC MAGIC 32A (SPL: 1.76.2007)
http://www.4shared.com/file/21114537...07-signed.html
8. Now copy the SPL to your memory card.
adb push update-hboot-1762007-signed.zip /sdcard/
9. Restart your phone using the home + power key till it boots up into the recovery mode.
(or just type 'adb shell reboot recovery')
10. Using the 'Flash zip file' option from the recovery, select the SPL file from the memory card and flash the HBOOT on your phone
Now i've done most of that, but when I restart into recovery mode, it keeps on randomly rebooting even though I don't want it to. I clicked on 'flash zip file' and it just rebooted right away.
Now when I flashed the recovery, the command prompt said that it did it, BUT nothing happened on my phone, it was just sitting there and didn't say it was doing anything. Could this be a problem?

OK i kept trying, and finally i got it to go into 'flash zip file', I clicked on the correct zip file, but right after clicking the screen went black and it restarted.
Does this sound like it worked? How do I check to confirm if it worked and it's rooted?

Ok I did this, and it said ADB is already running in root in the cmd, so i think i'm good!!!
Thanks!
The easiest way to test if the device is rooted is to open another command prompt in the tools dir and type
adb root
If it returns that adab is already running in root, then you're all set.

So as i said, i installed the sapphire recovery, but now i'm reading on the wiki page that you need the HERO recovery file. I need to change the radio, but then it is saying i needed the HERO recovery.
This is so damn confusing why can't anyone get this all straight and not have so many different and totally contradicting methods.
http://wiki.cyanogenmod.com/index.p...agic32A_Firmware_to_CyanogenMod#6.35.x_Radios
The wiki here says to use the HERO recovery, but this thread only gives the sapphire recovery for the HTC magic.
http://forum.xda-developers.com/showthread.php?t=530492
Now to clarify i checked and i think i have successfully rooted, but the specs are this.
Sapphire PVT 32A ship s-on H
Hboot-1.76.0008
CPLD-12
RADIO-6.35.08.29
I'm told i need to change the radio now before I can install the cyanogen rom, is this true?
I can't find out what to do because no one seems to talk about the 1.76.0008 spl...
Any help?

OK so more playing and more following guides, I installed the HERO recovery tool (1.6.2), and updated the radio to 6.35.10.18, changed my SPL to 1.76.2007, and have my PVT 32A ENG S-OFF H setup.
I'm confused though, because I did all of this work so I can install the lastest cyanogen rom, but it says it can't use this version of the radio... what the hell?
Someone REALLY needs to fix these tutorials to be self consistant.
http://forum.xda-developers.com/showthread.php?t=605239
follow this, got it all done, then go here to get the cyanogen mod...
http://forum.xda-developers.com/showthread.php?t=673394.
What do I do now?? Do I downgrade my radio or just use a different rom?

thesmoth said:
OK so more playing and more following guides, I installed the HERO recovery tool (1.6.2), and updated the radio to 6.35.10.18, changed my SPL to 1.76.2007, and have my PVT 32A ENG S-OFF H setup.
I'm confused though, because I did all of this work so I can install the lastest cyanogen rom, but it says it can't use this version of the radio... what the hell?
Someone REALLY needs to fix these tutorials to be self consistant.
http://forum.xda-developers.com/showthread.php?t=605239
follow this, got it all done, then go here to get the cyanogen mod...
http://forum.xda-developers.com/showthread.php?t=673394.
What do I do now?? Do I downgrade my radio or just use a different rom?
Click to expand...
Click to collapse
Here is a link to a test kernel port file for CM 5.0.8 from Brian Crook. This should allow you to run CM using your current Radio. Like I say it's a test port and I haven't tried it but Brian is the one that does all the ports to the Rogers 3.x radios.
http://briancrook.ca/android/testing/
you'll need to download the file bc-5.0.8-6355-ebi1-signed.zip
You would use recovery to flash CM 5.0.8 then flash this kernel port file. After that don't forget to flash the gapps package that should be linked in one of the URL's that you already posted or you can get it here http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
PLEASE NOTE
Do not change your radio from it's current 6.x version without flashing the matching SPL for the new radio. If you fail to flash the SPL/Radio combination correctly you WILL brick your phone.

wildfire doesnt boot

hi,
i got a used wildfire device. it boots always into fastboot. i have tried to reflash RUU. that seemed to finish successfully but it stuck in boot screen when rebooted after finishing.
i can access the device via fastboot but what could be done next?
dont know the history of that device. maybe hardware defect? but would firmware update finish successfully then?
thanks for sharing your ideas
didi
Sent from my Nexus One using XDA Premium App

hboot 1.01.0002
buzz pvt ship s-on
Sent from my Nexus One using XDA Premium App

turn it to S-OFF then downgrade to hboot 1.01.0001... you must unbrand it first before you can flash custom roms.. you can find guides on the development section..

dedeep said:
hi,
i got a used wildfire device. it boots always into fastboot. i have tried to reflash RUU. that seemed to finish successfully but it stuck in boot screen when rebooted after finishing.
i can access the device via fastboot but what could be done next?
dont know the history of that device. maybe hardware defect? but would firmware update finish successfully then?
thanks for sharing your ideas
didi
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Fastboot will not work as you are S-ON. So you first have to downgrade your hboot version to 1.01.0001 and then install a custom bootloader with the use of revolutionary. Tutorials for downgrading and gaining root with revolutionary can be found in the developement section (cant link you as I'm using the xda app).
Once rooted, you can use fastboot or the custom recovery to flash a new rom.
Good luck!
Erwin
EDIT: I've just seen that the [full guide] on how to root with hboot 1.01.0002 is on the main page of "wildfire general"!

http://forum.xda-developers.com/showthread.php?t=1145035
Sent from my HTC Wildfire using XDA Premium App

Unable to downgrade without an OS?
1st thanks a lot for your answers!
I am bit in trouble, because I dont have a running (bootable) Android on that phone. As I understand all the downgrade guides I will need an ADB connection (which requires some booted Android OS I think - please correct me if I am wrong).
My plan was to install an OS version to 1st check if device works so far and boots an official OS.
I successfully flashed a new ROM from shipped-roms. Cause it was originally branded I needed to create a goldcard. I realized that I can only install newer ROMs. Whenever I wanted to install an older RUU the setup gave me an error 140.
So I have installed an australian Telstra 2.38 RUU (http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_167270_signed.exe) which successfully finished. But after installation the device reboots in normal mode and stuck after Telstra logo.
Is there a way to see why it does not boot successfully?
Is there a chance that this is a software error and NOT an hardware error?
Thanks & regards
didi

fastboot oem boot
Found some nice fastboot command which gives me bunch of information - unfortunately I dont understand 'em Maybe of help for anybody?
Code:
./fastboot oem boot
... INFOsetup_tag addr=0xBC900100 cmdline add=0x9C0734A0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x1
INFOTAG:skuid 0x24903
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is VODAP129
INFOsetting->cid::VODAP129
INFOserial number: HT076PYxxxxx
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =487
INFOactive commandline: board_buzz.disable_uart3=0 board_buzz.us
INFOb_h2w_sw=0 board_buzz.disable_sdcard=0 diag.enabled=0 board_
INFObuzz.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=
INFOfalse androidboot.baseband=3.35.20.10 androidboot.cid=VODAP
INFO129 androidboot.batt_poweron=good_battery androidboot.carrie
INFOr=VODA-DE androidboot.mid=PC4910000 androidboot.keycaps=qwer
INFOty androidboot.mode=normal androidboot.serialno=HT076PYxxxxx
INFO androidboot.bootloader=1.01.0002 zygote_oneshot=off no_cons
INFOole_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFODelay 99992(us) for dpram command before goto AMSS...
FAILED (status read failed (Protocol error))

dedeep said:
1st thanks a lot for your answers!
I am bit in trouble, because I dont have a running (bootable) Android on that phone. As I understand all the downgrade guides I will need an ADB connection (which requires some booted Android OS I think - please correct me if I am wrong).
My plan was to install an OS version to 1st check if device works so far and boots an official OS.
I successfully flashed a new ROM from shipped-roms. Cause it was originally branded I needed to create a goldcard. I realized that I can only install newer ROMs. Whenever I wanted to install an older RUU the setup gave me an error 140.
So I have installed an australian Telstra 2.38 RUU (http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_167270_signed.exe) which successfully finished. But after installation the device reboots in normal mode and stuck after Telstra logo.
Is there a way to see why it does not boot successfully?
Is there a chance that this is a software error and NOT an hardware error?
Thanks & regards
didi
Click to expand...
Click to collapse
Have you tryed to connect your phone when hangin in that tesla logo, and check if you can run adb now? With a little luck.. A simple "adb devices" will allow you to check.
Erwin

I think alpharev (and hence revolutionary) needs a full booted phone with USB debugging on. So maybe you can't use them.
Try to make a hard reset from the hboot menu. Power off the device and hold volume down + power button. Then clear storage there and see what happens.
If it still had the issue, then install the RUU by pc49img method. Download the correct ruu for your phone. Donot connect phone to PC. On windows PC click on start and type %temp% and enter. This opens the user temporary folder of your PC. Now run the ruu. Now if you observe the temp folder, there will be extra folders created which have folder name enclosed in {} brackets. Search in these folders for the file ROM.zip. Copy the ROM.zip to a safe location. Now format your memory card to fat32 (must) and put the ROM.zip to the root of memory card. You should use memory card reader. Then rename the ROM.zip to PC49IMG.ZIP . Then insert memory card in phone and reboot to hboot menu from where you can update/reflash the partitions. If still not working, clear storage again from hboot menu.
Give these things a try. If they won't solve you mostly need to give your phone to service center, because you can't do anything on a phone with heavily locked bootloader and S-ON when it is not bootable (AFAIK).
Sent from my Blade using XDA App

Still fails
Thanks so much for your support!
@Erwin: I've tried to connect via ADB but it failed. I dont get an ADB connection to my device.
@Bharatgaddameedi: A problem is, that I cant select anything in the HBOOT menu. The VOL-/+ keys dont work in HBOOT menu. I doubt it has an hardware error (keys damaged), because I can use them to boot either in HBOOT or HBOOT/fastboot. But problem is: I cant clear storage
I have created a SD card with PC49IMG.ZIP but it failed with error "Main version is older!". I will order a XTC clip and try to S-OFF this device. Hope that helps. Or some other idea out there?

dedeep said:
@Bharatgaddameedi: A problem is, that I cant select anything in the HBOOT menu. The VOL-/+ keys dont work in HBOOT menu. I doubt it has an hardware error (keys damaged), because I can use them to boot either in HBOOT or HBOOT/fastboot. But problem is: I cant clear storage
I have created a SD card with PC49IMG.ZIP but it failed with error "Main version is older!". I will order a XTC clip and try to S-OFF this device. Hope that helps. Or some other idea out there?
Click to expand...
Click to collapse
Remove sdcard and boot into hboot mode and try to clear storage. There shouldn't be hardware issue regarding volume keys since you are able to boot into hboot mode.
And regarding the error "main version is older", it is because the ruu you are using must be having hboot 1.01.0001 (or even lower) whereas your phone hboot is 1.01.0002. As it cannot downgrade it gives the error. The solution is you should use an ruu with hboot 1.01.0002 . I don't know if there is one. You may also need goldcard.
And lastly , I would suggest to give in service centre rather than purchasing xtc clip. Because it is not confirmatory that you can solve it after making s-off by xtc clip. And moreover s-off by xtc clip will not enable fastboot flashing by default.
Sent from my Blade using XDA App

http://shipped-roms.com/download.ph...45.55.24_3.35.15.31_release_142213_signed.exe
try to flash it .It may work...........

having issues fastbooting recovery

Hi my name is Luke and I'm having issues flashing a new recovery onto my mytouch 3g phone. I have to say that I am fairly new to the android rooting envirnoment, so please tell me step by step. I've done the following:
- Rooted the android phone via SuperOneClick
- I installed a root checker program = which said that my phone was rooted
- I went into the recovery and have the following version: SAPPHIRE PVT 32A SHIP S-ON H
- I went to this page: http://forum.xda-developers.com/showthread.php?t=530492&highlight=recovery and downloaded the latest version
- I made a gold card and put the .img on the root directory of the SD card
- I installed all of the necessary android SDK stuff on my computer
- typed in fastboot devices and it did find my phone
- I tried flashing it but it had a error: FAILED (remote: Write Fail)
- Please advise on what I should do - easiest as possible

luke.Janeth2011 said:
Hi my name is Luke and I'm having issues flashing a new recovery onto my mytouch 3g phone. I have to say that I am fairly new to the android rooting envirnoment, so please tell me step by step. I've done the following:
- Rooted the android phone via SuperOneClick
- I installed a root checker program = which said that my phone was rooted
- I went into the recovery and have the following version: SAPPHIRE PVT 32A SHIP S-ON H
- I went to this page: http://forum.xda-developers.com/showthread.php?t=530492&highlight=recovery and downloaded the latest version
- I made a gold card and put the .img on the root directory of the SD card
- I installed all of the necessary android SDK stuff on my computer
- typed in fastboot devices and it did find my phone
- I tried flashing it but it had a error: FAILED (remote: Write Fail)
- Please advise on what I should do - easiest as possible
Click to expand...
Click to collapse
Hi Luke.
If you're rooted, you're halfway there. Don't worry about gold cards or fastboot. You can write the new recovery using adb.
Check out mumilover's guide. Step 5 deals with writing recovery. You'll need to know what radio your device is currently running. You can get that from the same page were you saw "SAPPHIRE PVT 32A".
If you don't have adb already installed, grab roottools from mumilover's post.
Let me know how it goes. Good luck! :good:

[Q] 32A - fastboot "not allow" error, hboot won't work

I have an old T-Mobile myTouch 3G Fender with the 3.5mm jack (32A, according to bootloader). I have a renewed interest in getting it up and running again. I don't intend to use it as a phone as I have an S3 as my daily driver.
Nevertheless, I'd still want to play around with different ROMS on this device and see how far I can take things. Unfortunately, it seems like I've already taken it to its limit. I have 106 tabs open in Chrome and have already stayed up far too late in the night these past couple of days trying to make things work.
Initially, the phone was working (albeit very poorly). I decided to hunt for a reliable, stable, no-frills ROM. I found one that needed RA-sapphire-v1.7.0. Before updating the recovery, I thought it would be a great idea to wipe the phone. Following this guide, I nearly downloaded the appropriate recovery. Instead of downloading the G version, I downloaded the H version. So now I have a ROM-less device with a recovery that won't boot and does nothing more than display the HTC Magic splash image. At least I have access to my bootloader!
But both fastboot and hboot seem to be completely useless. I am consistently getting the "not allow" error message whenever I try to use the flash or boot commands through my computer. I've tried using hboot by creating sappimg.zip files with the correct recovery.img and placing them on a 4GB Kingston Goldcard (which I set up using my S3. I've read that Kingstons tend to work more often than not), but it doesn't do anything. I've tried throwing in a Engineering SPL (named hboot.img) into the sappimg.zip file. Nothing. It reads the sappimg.zip file and loads it, but right after it says 'Checking file...', it just stops. No errors, nothing. The system isn't crashing, per se: the screen just clears and displays the hboot menu as if you had just booted into it, as if you never told it to do anything.
Here's some info about the device:
Code:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27
I think it would be possible to fix this if fastboot was working properly. But I can't use fastboot because I don't have a Eng SPL. And I can't seem to find out how to install it using hboot.
Any way out of this mess?

You can try to restore to stock by copying a sappimg.zip file (a type of operating system image) to the root of the sdcard, then start in bootloader mode and it should recognize the file and let you update the phone's rom to stock.
This is the sappimg for sapphire pvt 32a build 2.10.531.4
HTML:
http://www.4shared.com/zip/CgyRRX4O/stock-sappimg.html]stock-sappimg.zip
Just rename it to sappimg.zip and copy to the root of the sdcard

pmerced said:
You can try to restore to stock by copying a sappimg.zip file (a type of operating system image) to the root of the sdcard, then start in bootloader mode and it should recognize the file and let you update the phone's rom to stock.
This is the sappimg for sapphire pvt 32a build 2.10.531.4
Just rename it to sappimg.zip and copy to the root of the sdcard
Click to expand...
Click to collapse
This one seems to at least go past the "checking.." stage. But it says that it's an older version. Is there a way to trick it into thinking it is a newer version?
Secondly, what is it about this particular .zip file that it works? Can I just replace the hboot.img found within this file with a unperfected version?

Well, here's a new discovery I've made. I can unzip the sappimg.zip files no problem; however, once I've made the changes I've deemed necessary and after I've re-archived them, the bootloader will not go further than the "checking.." stage.
I've tried it with the stock image file above. I initially tried using the bare, unmodified file. It did get past the "checking" stage but it gave me an error message stating the main version is older. I then tried unzipping the file and immediately re-archiving after making no modifications. Theoretically, it should be the exact same file that produces the same results. But it doesn't: same problem as above. It won't proceed past the "checking."
Both Mac (via the "zip" command at the command line) and Windows (via WinRAR) have been attempted. I must be missing some sort of advanced archiving setting.
Any ideas?

Sorry to hear it didn't work my suggestion. I think that the older version rejection is the problem to solve to bring back the operation of the phone.
I read somewhere that there is a way to extract the files contained in the sappimg from a RUU update file, but the latest version I found is the same of the file I suggested. Maybe if you can find a later one then you could make a sappimg.zip from there. Make sure the files are intended for the specifications in the HBOOT screen: specially 32A and matching radio with hboot, otherwise you may brick the phone.
The problem with modifying and repacking is that the file has to be signed with HTC keys and those are almost impossible to find out unless you have a high rank job in HTC.