Database Info

Fastboot flashing radio under new hboot

Question for the experts here:
I am on the new hboot 1.14.0002 after taking the OTA update on my 1.88 Asian stock rom (I chose to bite the bullet and go down this route) and now I'm getting "Failed (remote: signature verify fail)" when trying to flash radio.imgfastboot.
I have supercid and am rooted, htcdev unlocked. I also flashed custom recovery (TWRP) and recently a custom rom (KingCobra1x). Interestingly I flashed the boot.img in fastboot without any problem, but not the radio. This is the bit I don't understand.
Am I missing something here? I've read posts that say radio flashing in fastboot still works after upgrading, but that may not be for hboot 1.14.
Thanks in advance,
Sunster

sunster00 said:
Question for the experts here:
I am on the new hboot 1.14.0002 after taking the OTA update on my 1.88 Asian stock rom (I chose to bite the bullet and go down this route) and now I'm getting "Failed (remote: signature verify fail)" when trying to flash radio.imgfastboot.
I have supercid and am rooted, htcdev unlocked. I also flashed custom recovery (TWRP) and recently a custom rom (KingCobra1x). Interestingly I flashed the boot.img in fastboot without any problem, but not the radio. This is the bit I don't understand.
Am I missing something here? I've read posts that say radio flashing in fastboot still works after upgrading, but that may not be for hboot 1.14.
Thanks in advance,
Sunster
Click to expand...
Click to collapse
Typically we can't flash new radios without S-Off. There was a sort of loophole found that allowed us to do it before but I believe it has been fixed with the new hboot.

sunster00 said:
Question for the experts here:
I am on the new hboot 1.14.0002 after taking the OTA update on my 1.88 Asian stock rom (I chose to bite the bullet and go down this route) and now I'm getting "Failed (remote: signature verify fail)" when trying to flash radio.imgfastboot.
I have supercid and am rooted, htcdev unlocked. I also flashed custom recovery (TWRP) and recently a custom rom (KingCobra1x). Interestingly I flashed the boot.img in fastboot without any problem, but not the radio. This is the bit I don't understand.
Am I missing something here? I've read posts that say radio flashing in fastboot still works after upgrading, but that may not be for hboot 1.14.
Thanks in advance,
Sunster
Click to expand...
Click to collapse
If you are rooted you can try just dd'ing it right from android, assuming there's not WP on that partition.

beaups said:
If you are rooted you can try just dd'ing it right from android, assuming there's not WP on that partition.
Click to expand...
Click to collapse
Thanks guys for the replies. I tried dd'ing but no there's WP on partition mmcblk0p17 so that's a no go...

I just thought I would throw in my 2c, I'm on HBOOT 1.11 and am unable to flash radio via fastboot due to the same error. I am able to install the radios in this thread,
http://forum.xda-developers.com/showthread.php?t=1694012&highlight=radios
by just flashing the zip though? Is this expected behaviour?
EDIT:
Scrap that, here is everything I did in order, I can't make any 'sense' out of it...
1) running CM10-20121006 with HTC TELSTRA 1.89(0.18c.32.09.01_10.93a.32.20L) baseband
2) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio via fastboot
fastboot flash radio ~/Downloads/radio/radio.img
FAILED (remote: signature verify fail)
3) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio from zip
SUCCESS!!!
4) dirty flash CM10-20121008, radio has changed to ATT 1.85 (0.17.32.09.12_10.86.32.08L)? WTF?
5) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio from zip
no error but no change in reported baseband
6) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio using dd
no error but no change in reported baseband
7) dirty flash back to CM10-20121006, radio has reverted to HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L)? WTF?

[Q] Phone won't boot up normally and cannot flash RUU

Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred

fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )

ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred

A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred

fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID

Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred

fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place

dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred

fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred

fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery

ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work

rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred

wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary

ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.

fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )

ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.

fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom

[Q]Bootloader downgrade?flashing firmware(FAILED (remote: 99 unknown fail)),MaximusHD

Hello,
I get an Error when i try to flash the firmware.zip for MaximusHD
Code:
sending 'zip' (36985 KB)...
OKAY [ 2.699s]
writing 'zip'...
(bootloader) zip header checking.
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.146s
I figured out it may relyto my bootloader.
I'm currently on HBoot 1.14.0002,so i guess its bootloader 2.31
S-ON and unlocked
I read it worked on 2.16, so how do i downgrade.
I really dont want to mess up my bootloader, so i better ask for some advice here
I found this Thread
http://forum.xda-developers.com/showthread.php?t=1990043
But i'm not sure if i took the JB OTA(Had an JB based Rom before)

You gotta be s-off and unlocked and do the commands one by one in command promt. First time it will give u an error...re-do the command right away and it should work.
Also as an advise read the instruction carefully at least 3 times so u undestand what u doing.

So i have to follow this guide
http://forum.xda-developers.com/showthread.php?t=2155135
Read it before, but couldn't figure out if it will help me.
Thanks so far.

Try this one.
http://forum.xda-developers.com/showthread.php?t=2325590
And don't worry about bricking the phone, it's almost imposible. As long as you can go into bootloader you can bring it back to life. I've done it many times.
Also I'm using unknown 2.0 becuase maximus 10 gave me too many problems. I recomend you to use the same as me is basically the same.

Well already got superCID and did everything the guide told me.
Was a bit confused about SuperCID since it didnt sayed CW_001 or something similar.
Could now flash the firmware.zip.
Only messed up my sdcard but i saw that one coming
Thank you very much!

jenenser83 said:
Try this one.
http://forum.xda-developers.com/showthread.php?t=2325590
And don't worry about bricking the phone, it's almost imposible. As long as you can go into bootloader you can bring it back to life. I've done it many times.
Also I'm using unknown 2.0 becuase maximus 10 gave me too many problems. I recomend you to use the same as me is basically the same.
Click to expand...
Click to collapse
Hi Jenenser, I'm on Maximus, Hboot 2.16, s-off, unlocked. I'm trying to get back to Unknown 2.0 because I find Maximus to be too buggy as well. I can't seem to flash anything from fastboot (not recovery, not firmware, can't run RUU, nothing seems to take). How did you get back to Unknown?
Thanks!

Go back to complete stock or RUU than repeat the while unlocking process again.
Unlock bootloader, root the phone, install recovery and then from twrp recover install ROM.

k2_CL RUU freezing @ black HTC screen

I am trying to restore my phone obviously but when I try to use the RUU it keeps freezing at the update progress screen, but the bar never shows up. Any ideas?
Tried a different cable, and now I am getting error 155, (The rom update utility couldn't update your android phone.)
The reason this is such a problem, is because I can't get intpo TWRP, it gives me the twrp loading screen, but then softboots loops over and over into the twrp loading screen. I flashed recovery.img a couple of times and still can't get it working.
Basically at this point I feel like it's RUU or bust.

tootone said:
I am trying to restore my phone obviously but when I try to use the RUU it keeps freezing at the update progress screen, but the bar never shows up. Any ideas?
Click to expand...
Click to collapse
RUU will boot you into [fastboot's OEM rebootRUU] mode. Do you mean there is not a green progress bar? What ROM ver are you currently on?
Sent from my HTC Sensation using Tapatalk

eduardog131 said:
RUU will boot you into [fastboot's OEM rebootRUU] mode. Do you mean there is not a green progress bar? What ROM ver are you currently on?
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes no green progress bar. Currently there is no rom, because I cannot get into twrp. I edited my original post with some additional info.

Another update. I finally got into twrp, and now I just need a rom to flash I believe.
I have flashed a rom still no luck.
I flashed stock recovery, and relocked my bootloader. and tried the RUU again still getting error155. if anyone has a TWRP nandroid or a rom I could try that would be amazing.

bad english
tootone said:
Another update. I finally got into twrp, and now I just need a rom to flash I believe.
I have flashed a rom still no luck.
I flashed stock recovery, and relocked my bootloader. and tried the RUU again still getting error155. if anyone has a TWRP nandroid or a rom I could try that would be amazing.
Click to expand...
Click to collapse
Check this out i had the same problem than you, and this was the answer
First at all restore this backup with TWRP
http://forum.xda-developers.com/showthread.php?t=2734434
ICS preferred,
FLASH BOOT.IMG with Fastboot
Second if you can start up your HTC,
flash stock ICS
recovery.img with fastboot.
http://forum.xda-developers.com/showthread.php?t=2317379
then you can update via OTA.
Send me a message if you have problems
SORRY FOR MY BAD ENGLISH.

omarmando said:
Check this out i had the same problem than you, and this was the answer
First at all restore this backup with TWRP
http://forum.xda-developers.com/showthread.php?t=2734434
ICS preferred,
FLASH BOOT.IMG with Fastboot
Second if you can start up your HTC,
flash stock ICS
recovery.img with fastboot.
http://forum.xda-developers.com/showthread.php?t=2317379
then you can update via OTA.
Send me a message if you have problems
SORRY FOR MY BAD ENGLISH.
Click to expand...
Click to collapse
I am trying the first method you sent me, but which boot.img are we talking here?

Ics Bolt.img
Sent from my C525c using XDA Free mobile app

There is an encrypted Rom.zip pulled from the actual RUU itself posted for K2_CL.
Using fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Rom.zip
Give it time. Could take ten minutes or longer until it is complete. Had a guy do it over on AF and he has his phone back now.
Sent from my C525c using Tapatalk

Modding.MyMind said:
There is an encrypted Rom.zip pulled from the actual RUU itself posted for K2_CL.
Using fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Rom.zip
Give it time. Could take ten minutes or longer until it is complete. Had a guy do it over on AF and he has his phone back now.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yeah that fails with
C:\adb>fastboot flash zip Rom.zip
sending 'zip' (616945 KB)...
OKAY [ 23.035s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 92.353s

tootone said:
Yeah that fails with
C:\adb>fastboot flash zip Rom.zip
sending 'zip' (616945 KB)...
OKAY [ 23.035s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 92.353s
Click to expand...
Click to collapse
What shows on your device screen when doing it?
Also, if you are S-On and was on 4.2.2 prior to your device giving problems then it will fail because the RUU is 4.1.2 and would require a "downgrade" which can only be achieved if S-Off.
With that said, I went back up on this thread and saw you are having problems with TWRP. Make sure you are using the correct one. Should be 2.7.0.2d or 2.7.0.2c. If attempting to flash another version and you are on 4.2.2 then you will get boot problems with the recovery.
In addition, make sure your bootloader isn't locked if S-On while messing with TWRP or that will cause a security problem on your device.
Sent from my C525c using Tapatalk

Modding.MyMind said:
What shows on your device screen when doing it?
Also, if you are S-On and was on 4.2.2 prior to your device giving problems then it will fail because the RUU is 4.1.2 and would require a "downgrade" which can only be achieved if S-Off.
With that said, I went back up on this thread and saw you are having problems with TWRP. Make sure you are using the correct one. Should be 2.7.0.2d or 2.7.0.2c. If attempting to flash another version and you are on 4.2.2 then you will get boot problems with the recovery.
In addition, make sure your bootloader isn't locked if S-On while messing with TWRP or that will cause a security problem on your device.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
bootloader is unlocked but I am s-on maybe that is causing all of my problems. I will see what I can do to remedy that. Well nevermind, I can' t s-off without a working rom, and I can't get a working rom without s-off.

tootone said:
bootloader is unlocked but I am s-on maybe that is causing all of my problems. I will see what I can do to remedy that. Well nevermind, I can' t s-off without a working rom, and I can't get a working rom without s-off.
Click to expand...
Click to collapse
Hmm, well, there is one thing I know for sure and that it that you are definitely able to restore your phone, so I'm pretty sure that some attempts being made In regards to trying other methods are possibly not being done exactly like they should.
This device is VERY hard to wreck and I have done LOTS to my phone and have always been able to bring it back to life in 5 minutes or less.
Sent from my C525c using Tapatalk

I am fairly certain I am doing it right. My mistake here was not doing a backup before I flashed anything. Let me go through what I had tried.
The RUU, I run it with my bootloader locked and I get error 158, I run it unlocked, I still get error 158.
I have tried the rom from the RUU, fastboot into ruu mode, transfer it, and I get an error
I tried putting PL80IMG in the root of my sd, it seems to flash correctly but it boots in white htc quietly brilliant screen. and flash boot.img for that rom.
I restore a rom via TWRP boots into white htc quietly brilliant screen.
and countless other things.

What about the other backups for boost (older than 4.2.2), does none of them work?

tootone said:
I am fairly certain I am doing it right. My mistake here was not doing a backup before I flashed anything. Let me go through what I had tried.
The RUU, I run it with my bootloader locked and I get error 158, I run it unlocked, I still get error 158.
I have tried the rom from the RUU, fastboot into ruu mode, transfer it, and I get an error
I tried putting PL80IMG in the root of my sd, it seems to flash correctly but it boots in white htc quietly brilliant screen. and flash boot.img for that rom.
I restore a rom via TWRP boots into white htc quietly brilliant screen.
and countless other things.
Click to expand...
Click to collapse
1. RUU won't work because it's 4.1.2 and you were on 4.2.2. The RUU has the HBoot in it and your device will not allow the HBoot to be downgraded because you are S-On. Only time you can use an RUU is if it is equivalent to 4.2.2 which one does not currently exist for us.
2. PL80IMG.zip's only work for those who are S-Off. Which is why it won't work for you.
3. When you restore your device using TWRP you ALSO have to rename boot.emmc.win to boot.img and flash it using fastboot:
Code:
fastboot flash boot boot.img
-- This is because, once again, you are S-On and cannot write to your boot partition EXCEPT using fastboot. You could using dumlock but to get dumlock initially set up for the first time would require your device to be able to load an OS so for you that is currently out of the question.
You must restore your device using a twrp backup, AND NOT REBOOT THE SYSTEM when it is done.
Instead, reboot the bootloader, and using fastboot, flash the boot.img which comes with the twrp backup as I just stated earlier.
Then you may reboot.
That will ALWAYS work, so if it fails, then this is an end user problem.
Sent from my C525c using Tapatalk

Problem with unlocking bootloader after S-Off Pyramid

Hi,
I have little problem... I unlocked bootloader by HTCdev, S-offed by JuopunutBear 0.5b (with wire-trick) and install unbranded firmware RUU 3.32.401.5. Now I'd like to flash CWM recovery, but I receieve an error "writing 'recovery'... failed (remote: not allowed)"... I also tried to flash it by KGS Utility v8 and this didn't work for me. Can I unlock bootloader again by bin file generated by HTCdev? Somewhere who wrote that it possible to brick the phone, but few people did it and nothing happened. What can I do? Any ideas?
Greets.

caris said:
Hi,
I have little problem... I unlocked bootloader by HTCdev, S-offed by JuopunutBear 0.5b (with wire-trick) and install unbranded firmware RUU 3.32.401.5. Now I'd like to flash CWM recovery, but I receieve an error "writing 'recovery'... failed (remote: not allowed)"... I also tried to flash it by KGS Utility v8 and this didn't work for me. Can I unlock bootloader again by bin file generated by HTCdev? Somewhere who wrote that it possible to brick the phone, but few people did it and nothing happened. What can I do? Any ideas?
Greets.
Click to expand...
Click to collapse
actually why did you use a ruu.exe for flashing a custom recovery?
it was an unecessary step
nevermind
if you still are on S-OFF flash 3.33 iniversal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then you can install a custom recovery
another way is to install 4ext updater(link in my signature)
from the app download and install the latest version of 4ext recovery
edit: just to know when you are locked or relocked you are limited to some fastboot commands

I was flashed RUU because I wanted to delete Orange PL brand. Yep, I'm still on S-Off.
Can I flash by fastboot "PG58IMG 3.32 unlocked.zip" file (~14MB) to my firmware what I have now? It may unlock bootloader?

caris said:
I was flashed RUU because I wanted to delete Orange PL brand. Yep, I'm still on S-Off.
Can I flash by fastboot "PG58IMG 3.32 unlocked.zip" file (~14MB) to my firmware what I have now? It may unlock bootloader?
Click to expand...
Click to collapse
probably you can use it via fastboot command
but it would better to flash it directly from bootloader

I updated FW (PG58IMG.zip unlocked) via Bootloader, flashed CWM via fastboot tools and it works!
@rzr86, Thanks for advices. :good:
Greets.