[Q] FAILED (remote: 99 ... while trying to recover my bricked flyer - HTC Flyer, EVO View 4G

I'm stuck and have been searching and trying to follow all the various suggestions out in the thread. I ran into a problem using
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
The RUU 1.36 does not work for my best buy machine, it continually runs into errors. I followed the steps above as well as tried the new procedure but I continually get the following error:
Code:
E:\Users\manacap\Desktop\flyer>fastboot flash boot boot_signed.img
sending 'boot' (3132 KB)... OKAY
writing 'boot'... OKAY
E:\Users\manacap\Desktop\flyer>fastboot reboot-bootloader
rebooting into bootloader... OKAY
E:\Users\manacap\Desktop\flyer>adb push hboot_1.10.0000_54.img /
5918 KB/s (1048576 bytes in 0.173s)
E:\Users\manacap\Desktop\flyer>adb shell dd if=/hboot_1.10.0000_54.img of=/dev/b
lock/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.139312 seconds, 7.2MB/s
E:\Users\manacap\Desktop\flyer>adb reboot bootloader
E:\Users\manacap\Desktop\flyer>fastboot oem rebootRUU
... INFOerase sector 163328 ~ 163839 (512)
OKAY
E:\Users\manacap\Desktop\flyer>fastboot flash zip rom.zip
sending 'zip' (511861 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
I have also included the recovery log below:
Code:
Starting recovery on Sat Nov 26 22:19:57 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1024 x 600)
Revolutionary CWM v4.0.1.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /system ext4 /dev/block/mmcblk0p25 (null)
4 /misc ext4 /dev/block/mmcblk0p28 (null)
5 /data ext4 /dev/block/mmcblk0p29 (null)
6 /cache ext4 /dev/block/mmcblk0p30 (null)
7 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
8 /internal_sdcard vfat /dev/block/mmcblk0p33 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p30 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GRJ22
ro.build.version.incremental=eng.aria.20110801.184950
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Aug 1 18:50:04 EDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=aria
ro.build.host=giovanni
ro.build.tags=test-keys
ro.product.model=Desire S
ro.product.brand=htc_wwe
ro.product.name=htc_flyer
ro.product.device=flyer
ro.product.board=flyer
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=flyer
ro.build.description=2.36.405.8 CL47853 release-keys
ro.build.fingerprint=htc_wwe/htc_flyer/flyer:2.3.3/GRI40/47853:user/release-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.modversion=CyanogenMod-7.1.0-RC1-IncS-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT15TJN00086
ro.bootmode=recovery
ro.baseband=3809.07.04.06_M
ro.carrier=COMMON
ro.bootloader=1.11.0003
ro.hardware=flyer
ro.revision=132
init.svc.choice_fn=stopped
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p30 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p30 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p30 (Invalid argument)
W:Can't unlink /cache/recovery/command
I've tried just about every combination of things. I lost recovery a few times but have cwm back. The machine won't boot, it just sits at the white htc screen (actually reboots there), although one time I got it to sit at the "brilliantly something" screen, but still no finished boot. Not sure how I screwed this up. I could use some suggestions.

---

Did you check the md5sum of your download? Where did you get the zip file? Also if you upgraded using Paul's guide you're using the wrong method.

---

I'm just trying to get back do a working machine. I've successfully done Paul's procedure before. I've also successfully reverted back to Gingerbread. I made the mistake of trying to do the HC method using PG41IMG -- I should have left well enough alone. Actually I don't think it can be MDSUM since it is the same error when I used the full HC zip or when I tried the recovery rom.zip.
For some reason 7zip won't give me checksum, I'll need to find another method. Probably go to linux and do it.

---

You're making no sense whatsoever. You've got a whole muddle of bits and pieces in that post. Calm down, stop whatever it is you are doing. You appear to have made up your own procedure based loosely on something I have posted and you don't really know what state your flyer is in.
Install teamviewer and PM the login details and I'll sort you out.
---------- Post added at 11:35 PM ---------- Previous post was at 11:22 PM ----------
manacap, no offense intended here but if you need my help you'll have to be relatively quick. I'm going to be away for the next 4 days starting in about an hours time.

---

Appreciate the offer, somehow I don't seem as frantic as you make me sound. I have tried a number of things in a systematic process that was listed. In the end, I was doing some mixing and matching. Go ahead, don't worry about me. I will figure it out. You gave me one idea, and that would be to replicate Paul's process which worked before. Enjoy your time away.

---

Cool, then I misread you as the typical frantic panic case. Looking at it again, it is definitely your rom.zip that is the problem. You need it to be the rom.zip from an official RUU or else run the RUU.
if 1.36 won't work, heres the 2.27 RUU zip file:
http://www.multiupload.com/G2M7UXU4M4 MD5: d8787c7b410592448ab0b5a92b2a367d
Since your on a stock hboot now, you have to RUU to get back to a stable state there is no other way.

---

I'm back to stock. THANKS!!! It could be the ROM you sent. Although, I may not have realized that you need to be in lock to use the RUU recovery (if that is the case, I feel dumb, I did not realize that was necessary). I relocked the OEM and then followed these steps.
E:\Users\manacap\Desktop\flyer>fastboot oem lock
< waiting for device >
... INFOLock successfully...
FAILED (status read failed (Too many links))
E:\Users\manacap\Desktop\flyer>fastboot erase cache
erasing 'cache'... OKAY
E:\Users\manacap\Desktop\flyer>fastboot oem rebootRUU
... INFOerase sector 163328 ~ 163839 (512)
OKAY
E:\Users\manacap\Desktop\flyer>fastboot flash zip rom.zip
sending 'zip' (500195 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
... blah ... blah ... blah
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
E:\Users\manacap\Desktop\flyer>fastboot flash zip rom.zip
sending 'zip' (500195 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
... much more blah ....
INFO[RUU]WP,rcdata,100
OKAY
E:\Users\manacap\Desktop\flyer>fastboot reboot
Now, I may retry "[Guide][Flyer]Honeycomb S-OFF, Honeycomb Easy Install, Recovery and Root."

---

manacap
I LOVE U!
I LOVE U!
I LOVE U!
I LOVE U!
I LOVE U!
Thanks for the step by step solution!!!!!!!!!!!!!!!! You rescued my HTC Desire S.

---

OK, so Im in the same boat here. I unlocked my bootloaded via HTCDEV.... the tried RUU, only to have the same failure.
So if I read this correctly, all I need to do is run the fastboot command to lock OEM, then I can downgrade and root?
Geez if its that simple I will cry...happy tears of course...I spent 5 hours on this yesterday.
If this works, the beer is on me.

---

The beer is on me...
SWEET!.... Thanks, it was done in 5 minutes.