Database Info

[Q] PG58IMG.zip can't be installed

My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Problem is my phone can't boot into system,

pmbldc said:
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Click to expand...
Click to collapse
Hi,
What exactly are you trying to do?

malybru said:
Hi,
What exactly are you trying to do?
Click to expand...
Click to collapse
My phone can't boot into system and now s-on, so i want to do something to make it work

pmbldc said:
My phone can't boot into system and now s-on, so i want to do something to make it work
Click to expand...
Click to collapse
Hi,
Were you s-off before?
What did you flash to make you s-on?

Last night I unlocked the bootloader n been having the same problem but mind say S-on n I don't know what's next
Sent from my HTC Sensation 4G using XDA App

? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it

ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated

malybru said:
Hi,
Were you s-off before?
What did you flash to make you s-on?
Click to expand...
Click to collapse
Sorry to reply so late.
Previously, my phone was eng s-off and got super cid.
After i flash ICS firmware, bootloader was then locked.
After that i did some stupid things, the bootloader turned into "locked", "security warning" and s-on. I succeeded to unlock bootloader by htcdev and get rid of "security warning", at that time i can boot into recovery normally and wipe or flash roms. But it just can't boot into system. I tried fastboot commands to flash but failed just because "it is not allowed in the remote devices".
i tried PG58IMG files but the bootloader shows no image or wrong image.
Can you give me some advice? Thank you very much

ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
My phone had been rooted and end s-off before things happened.
i flash IMG.zip to try to flash a rom( Somebody post that ICS rom can be flash by IMG.zip) or fix the bootloader problem. It's almost the only way to flash a rom for me
I checked the cid and it is still 11111111(Got super cid before) although bootloader is s-on.
Now the state of the bootloader is
1, unlocked
2,s-on
3,cid is 11111111
4,can boot into recovery
5,can't install PG58IMG.zip
6,fastboot command can't write anyting
7,if flash some rom, phone will be stuck at the splash screen which seems splash partition is writable
Thank you!

greenhtc982 said:
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
Click to expand...
Click to collapse
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem

ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?

ilostchild said:
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
Click to expand...
Click to collapse
I format the sdcard in fat32 format and place img that revert to hboot 1.17 in sdcard. Reboot into bootloader, but it shows "no image or wrong image".
I also try fastboot command but i don't know the command format. Would you give me an example please? Just a fastboot command to install img no matter s-on or s-off. Such as "fastboot flash hboot hboot.img".
My device is now s-on.

pmbldc said:
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
Click to expand...
Click to collapse
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.

greenhtc982 said:
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
Click to expand...
Click to collapse
You mean you can flash leedroid now, don't you?
Can you boot into system？

pmbldc said:
You mean you can flash leedroid now, don't you?
Can you boot into system？
Click to expand...
Click to collapse
Yes its working, but i would like to flash other ROM's

Same Problem
Hi, I can't flash PG85IMG.zip wither except that I have S-Off??

Unlocked Unlocked bootloader S-ON, rooted, can I put custom ROM or pre-rooted ROM

Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.

dejanxxxx said:
Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.
Click to expand...
Click to collapse
Yes you can. You don't need to achieve S-OFF to install custom ROM. I don't recommend you to install Official RUU ICS because it has been reported many times to be buggy and laggy. If you want a better feeling of that, you should install IceDS or IceCreamSaga ROMs.

I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.

i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode

dejanxxxx said:
I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.
Click to expand...
Click to collapse
Is your phone branded to any mobile carrier- by any chance?
Because if it was, to override the branded version by WWE 4.0.4
( world wide english )
you should use < gold card >
http://forum.xda-developers.com/showthread.php?t=1248095
If i remember correctly, error 155 refers to CID mismatch- wrong RUU version
But in your best interest is to double check what others say
Edit: unles something has changed,
there was only one ics ruu version for desire s
to be found on htcdev website..
How come you found four of them?

seagheart89 said:
i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode
Click to expand...
Click to collapse
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)

jugg1es said:
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)
Click to expand...
Click to collapse
it didnt give me an option for boot.img it used the aroma installer

message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.

continiven said:
message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.
Click to expand...
Click to collapse
I have this problem. Because my girl friend dont want custom ROM, I install RUU-ICS. But always when start flashing,eject 155 error, bootloader first unlocked, after before process I locked again bootloader,and in HBOOT writing RELOCKED-you say this is mistake because bootloader is unlocked, it not true- on my case.
After I use HTC SYNC- register phone and recognized, everything pass easy,and ROM is installed.

seagheart89 said:
it didnt give me an option for boot.img it used the aroma installer
Click to expand...
Click to collapse
Since your device is still s-on you need flash the boot.img manually.
Extract the boot.img from the rom, boot your device into fastboot and enter
Code:
fastboot flash boot boot.img

Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium

syed.shoaib said:
Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium
Click to expand...
Click to collapse
This might be the reason http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge
"Happiness is good health and a bad memory."
- Ingrid Bergman (1917-1982)

Phone won't get past boot screen

Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?

mikel.canovas said:
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
Click to expand...
Click to collapse
Can you get to bootloader? Fastboot access? You were soff previously correct?
Sent from my One Xl using Tapatalk 2

jrior001 said:
Can you get to bootloader?
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel

mikel.canovas said:
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/evita
From twrp's site grap the 2.6.3 recovery.IMG and with phone in bootloader where you see "fastboot usb" type in cmd promt fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
And the fastboot reboot-bootloader
Then navigate and try to get to recovery again
If you get that far flash ROM again, just that for now and relax for a bit
Sent from my One Xl using Tapatalk 2

Getting an error after writing recovery. Saying FAILED (remote: not allowed)

mikel.canovas said:
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
Click to expand...
Click to collapse
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2

jrior001 said:
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
No bootloader is "relocked". I was in fastboot when I ran the RUU since ADB is not being recognized when in bootloader. RUU was successful, didn't seem like anything went wrong

Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.

redpoint73 said:
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
Click to expand...
Click to collapse
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work

mikel.canovas said:
Bootloader says relocked.
Click to expand...
Click to collapse
You need to unlock bootloader again to flash TWRP.

unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel

mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
Click to expand...
Click to collapse
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2

mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Click to expand...
Click to collapse
Using the unlock token is known to sometimes fail and require repeated attempts, just keep trying.
Not sure why the RUU didn't work, that is weird.

jrior001 said:
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
I've done the RUU twice now. Same results. Was s-off with 2.14 hboot

mikel.canovas said:
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
Click to expand...
Click to collapse
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita

timmaaa said:
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader

mikel.canovas said:
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
Click to expand...
Click to collapse
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita

timmaaa said:
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
Click to expand...
Click to collapse
Then why has it failed 3 times? RUU is reporting successful. So what's the error?

Which error code is it giving you?
Sent from my Evita

timmaaa said:
Which error code is it giving you?
Sent from my Evita
Click to expand...
Click to collapse
RUU gives no error. It shows that it's successful

[q] 2.16 s-off tmous

This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.

pyrocide said:
This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.
Click to expand...
Click to collapse
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334

tivofool said:
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334
Click to expand...
Click to collapse
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?

pyrocide said:
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?
Click to expand...
Click to collapse
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3

tivofool said:
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3
Click to expand...
Click to collapse
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.

pyrocide said:
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.
Click to expand...
Click to collapse
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img

tivofool said:
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?

pyrocide said:
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?
Click to expand...
Click to collapse
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)

tivofool said:
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)
Click to expand...
Click to collapse
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.

pyrocide said:
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.
Click to expand...
Click to collapse
Yep, that is why. Unlock that bootloader.

tivofool said:
Yep, that is why. Unlock that bootloader.
Click to expand...
Click to collapse
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.

pyrocide said:
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.
Click to expand...
Click to collapse
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.

tivofool said:
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.
Click to expand...
Click to collapse
Thanks for the help, got it booting and charging. Gonna test the battery with the extended battery from the One X+ and see how much better this battery is vs CM10.1.3 and bootloops/reboots etc.

Cannot run Nougat RUU: Error 132 (signature error)

For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys

BrandonBaskin said:
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
Click to expand...
Click to collapse
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.

salvy' said:
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
Click to expand...
Click to collapse
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again

BrandonBaskin said:
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
Click to expand...
Click to collapse
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)

MGfusion said:
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
Click to expand...
Click to collapse
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks

BrandonBaskin said:
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
Click to expand...
Click to collapse
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified

MGfusion said:
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
Click to expand...
Click to collapse
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?

BrandonBaskin said:
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
Click to expand...
Click to collapse
I'm not sure, I don't understand what could still be "modified"

MGfusion said:
I'm not sure, I don't understand what could still be "modified"
Click to expand...
Click to collapse
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.

BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)

MGfusion said:
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
Click to expand...
Click to collapse
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?

BrandonBaskin said:
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
Click to expand...
Click to collapse
Can't remember if it said modified or not, but I am definitely s-off.

MGfusion said:
Can't remember if it said modified or not, but I am definitely s-off.
Click to expand...
Click to collapse
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.

BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing the OTA, then flashing ruu. Thats how I did I it.

BrandonBaskin said:
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
Click to expand...
Click to collapse
Oh, you are s-on? I would definitely try sunshine and then install ota or ruu then

The_scam said:
Try installing the OTA, then flashing ruin. Thats how I did I it.
Click to expand...
Click to collapse
Hey, thanks for the response. What is Ruin?

I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...

kommoncents said:
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
Click to expand...
Click to collapse
download the zip file I had given a link to above and try installing it with the stock system recovery

BrandonBaskin said:
Hey, thanks for the response. What is Ruin?
Click to expand...
Click to collapse
Lol sorry, meant to type ruu. Using my phone and autocorrect ?
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
MGfusion said:
download the zip file I had given a link to above and try installing it with the stock system recovery
Click to expand...
Click to collapse
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer

The_scam said:
Lol sorry, meant to type ruu. Using my phone and autocorrect
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
Click to expand...
Click to collapse
lol ohh! ok...I thought it was something like Odin haha
so just so I'm clear:
Flash OTA (in Recovery)?
Then immediately start the RUU?