Database Info

Can't Apply ICS OTA update

I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone

funkbro2 said:
I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone
Click to expand...
Click to collapse
man, mustn't update with official ota updates when you are rooted or s-off!

How can I s-on?

funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves

funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
you can be S=OFF but you must have stock recovery installed not 4ext and with the rooted part you will loose when you update, so just flash the stock recovery back on your phone and you are set to update.

What may work for you is to try to install the stock Gingerbread RUU for your phone first. Since you can't boot into GB, you may have to extract the rom.zip file from the RUU, rename it to PG58IMG.zip and place it in the root folder of your sdcard. Then restart your phone into the Bootloader and Gingerbread should reload. You do not need to be S-ON. If that is successful, your bootloader and recovery will be back to stock and you should still be S-OFF. The OTA should work at that point.

Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested

funkbro2 said:
Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested
Click to expand...
Click to collapse
Didn't know you were able to recover from a backup. Thought you were stuck on the white HTC screen. In that case, go ahead and try to fall back to a stock recovery, then try to do the OTA.

OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error

funkbro2 said:
OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error
Click to expand...
Click to collapse
As long as you don't have the stock recovery the OTA fails.. Read my previous post.. For God sake
Sent from my pyramid.. Through blazing fast sonic waves

Used RUU to flash back to "original"
Then did OTA update and it worked no problems
Now using ICS from OTA
Thank you everyone

ganeshp said:
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?

alza6991 said:
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?
Click to expand...
Click to collapse
probably you have to change your cid to original
and yes after ota update flash 4ext again

rzr86 said:
probably you have to change your cid to original
and yes after ota update flash 4ext again
Click to expand...
Click to collapse
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.

alza6991 said:
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.
Click to expand...
Click to collapse
install cid getter app from play store
it will show the original cid

Signature verify fail

I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.

Did you flash a signed stock recovery before locking the bootloader?

reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s

touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?

In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)

bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though

milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.

i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards

Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium

kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards

blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo

Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.

stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.

khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

HTC Update push

I just received notification of an update available:
System update:
Software update: 5.08.111.3 (15.54 MB)
Any ideas on this one? I have 5.08.111.2 (Turge's from T-Mobile).
I'm guessing I shouldn't update:
Unlocked
S-Off
CID-1111111
HBoot: 2.18.0000
Thanks!

My quick look has the hboot back down to 2.15.0000 which is odd although T-Mobile only ever had 2.15 previously.
Beyond that there is app updates and a few lib updates (not openssl from what I see).
When I get home I will check a new more things like what kernel it has.

DanGeorges said:
I just received notification of an update available:
System update:
Software update: 5.08.111.3 (15.54 MB)
Any ideas on this one? I have 5.08.111.2 (Turge's from T-Mobile).
I'm guessing I shouldn't update:
Unlocked
S-Off
CID-1111111
HBoot: 2.18.0000
Thanks!
Click to expand...
Click to collapse
I updated the hboot from the ATT update, so that's why it's not the T-Mobile version.
Thanks for digging around.

DanGeorges said:
I just received notification of an update available:
System update:
Software update: 5.08.111.3 (15.54 MB)
Any ideas on this one? I have 5.08.111.2 (Turge's from T-Mobile).
I'm guessing I shouldn't update:
Unlocked
S-Off
CID-1111111
HBoot: 2.18.0000
Thanks!
Click to expand...
Click to collapse
Ditto.. but my HBoot version is 2.15.0000
Is it safe to update?
Thanks in advance.
Cheers.

shsaifee said:
Ditto.. but my HBoot version is 2.15.0000
Is it safe to update?
Click to expand...
Click to collapse
If your phone is modded, it won't install. It least it didn't for me. I decided to try it, just to see (I'm s-off, so I figured the risk is low). I am on Turge's T-Mob 5.08 stock ROM, like the OP, with TWRP. Not sure what triggered the update not installing (root, custom recover, etc). But it just gave a warning that the phone was modded, and to return to stock if I wanted to update.

redpoint73 said:
Not sure what triggered the update not installing (root, custom recover, etc). But it just gave a warning that the phone was modded, and to return to stock if I wanted to update.
Click to expand...
Click to collapse
Most "Stock ROM" remove several apps like wiper and cota plus add things like su. If you really want the OTA on your phone s-off+supercid and following the official RUU/OTA chain would be your best bet.
Obviously no one has reported success in the process so anyone attempting should be willing to accept a brick by the end. Although so far nothing points to the update being all that risky to s-off/supercid devices.

redpoint73 said:
If your phone is modded, it won't install. It least it didn't for me. I decided to try it, just to see (I'm s-off, so I figured the risk is low). I am on Turge's T-Mob 5.08 stock ROM, like the OP, with TWRP. Not sure what triggered the update not installing (root, custom recover, etc). But it just gave a warning that the phone was modded, and to return to stock if I wanted to update.
Click to expand...
Click to collapse
Even I tried to install that and got the below message:
ClockworkMod Recovery v6.0.3.1
E : Invalid command argument
E : Invalid command argument
Finding update package. . .
E : unknown volume for path [INTERNALSDCARDownload/OTA_EVITA_UL_JB_50_S_TMO_DE_5.08.111.3-5.08.111.2_release_357526.zip]
E : Can't mount INTERNALSDCARDownload/OTA_EVITA_UL_JB_50_S_TMO_DE_5.08.111.3-5.08.111.2_release_357526.zip
Installation aborted.
Hope it helps.
Cheers!

shsaifee said:
Even I tried to install that and got the below message:
ClockworkMod Recovery v6.0.3.1
E : Invalid command argument
E : Invalid command argument
Finding update package. . .
E : unknown volume for path [INTERNALSDCARDownload/OTA_EVITA_UL_JB_50_S_TMO_DE_5.08.111.3-5.08.111.2_release_357526.zip]
E : Can't mount INTERNALSDCARDownload/OTA_EVITA_UL_JB_50_S_TMO_DE_5.08.111.3-5.08.111.2_release_357526.zip
Installation aborted.
Hope it helps.
Cheers!
Click to expand...
Click to collapse
OTA won't install with custom recovery (stock recovery is needed). It was pointless to even try.
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
twistedddx said:
Most "Stock ROM" remove several apps like wiper and cota plus add things like su. If you really want the OTA on your phone s-off+supercid and following the official RUU/OTA chain would be your best bet.
Click to expand...
Click to collapse
I was actually just trying to get the phone to stop nagging me of the update. And I was travelling, so I was too lazy to look up which process to freeze (which would have been safer). If I remember correctly, after the update downloads, there is still an opportunity to abort the install, which was the goal. I figured with s-off, the risk was low and decided to take the calculated risk.

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?

Htc a9 at&t

I wanted the newest android Nougat on the phone so i paid for the sunshine s-off and changed the cid and mid. Loaded twrp recovery couldn't get anything to work with that either so i figured it was cause i didn't erase everything the right way and used twrp advanced wipe and now it looks like im really screwed! any help would be appreciated!! Also i tried the RUU from HTC nothing works !!! i want to cuss so bad AAHHHHHH

You're going to have to be more specific about what you did if you want anyone to help you. What did you try to do that didn't work the first time? What all did you wipe? What is your device doing now? How did you try and use the RUU and did it give you any clues when it didn't work? Can you boot into fastboot mode at all?

JohnRogers23 said:
You're going to have to be more specific about what you did if you want anyone to help you. What did you try to do that didn't work the first time? What all did you wipe? What is your device doing now? How did you try and use the RUU and did it give you any clues when it didn't work? Can you boot into fastboot mode at all?
Click to expand...
Click to collapse
Sorry for the rant last night i was extremely frustraded! here is the phones current status
hxxp://imageshack.com/a/img922/7475/b6feFX.jpg
hxxp://imageshack.com/a/img923/192/AA2vGU.jpg
I tried to install the unlocked RUU for nougat and i also tried to use ADB to install the Nougat unlocked zip file
I would like to update to the unlocked version of Nougat
when i try to install the lastest RUU for unlocked it gives me error [132] signature error

i have the same model at&t unlocked and would like to update to the latest nougat, plz if someone can write an easy step by step tutorial
thank you

If converting,soff is needed,and you have to incrementally update device to current ota.. Cannot just change cid and mid and flash the Nougat ruu...

Wonders_Never_Cease said:
If converting,soff is needed,and you have to incrementally update device to current ota.. Cannot just change cid and mid and flash the Nougat ruu...
Click to expand...
Click to collapse
So how would i get my device to the unlocked edition 2.18.617.1 from 1.27.502.5? i realized after doing some research that i can't flash 1.x.x.x.x.x to 2.x.x.x.xx.x and i got flashed back to 1.27.502.5

killerdie14 said:
So how would i get my device to the unlocked edition 2.18.617.1 from 1.27.502.5? i realized after doing some research that i can't flash 1.x.x.x.x.x to 2.x.x.x.xx.x and i got flashed back to 1.27.502.5
Click to expand...
Click to collapse
You will have to take the 1.56.X latest ruu manually (from recovery or SD download mode) and then upgrade using the OTA.
Or PM me for the firmware image for the a9 to get to nougat.