Develop Bugs

[Q] Back to full stock with s-on

Hi guys,
need your help.
I have Europe M9, with S-ON.
Rooted it, and installed TWRP, installed custom rom.
How to revert it to full stock? I have sold the phone, and now buyer wants it back to way it were.
Thanks.

Thankfully it's pretty easy; just download your carrier specific RUU to restore to full stock. It's a Windows executable that completely wipes & return your phone to factory state.

I have bought it in Telenor Serbia it was on 1.32.401.15. Should I use any Europe RUU, or do I need to find one exact to match my carrier, and-or my firmware version?
sorry if being noob, but cannot understand this HTC's nonsense (s-on/s-off, cid, hboot...) thats the exact reason why I have sold it. to complicated for me...
I just want it up and running, and trust me, I will never EVER buy another HTC again.

acasmc said:
I have bought it in Telenor Serbia it was on 1.32.401.15. Should I use any Europe RUU, or do I need to find one exact to match my carrier, and-or my firmware version?
sorry if being noob, but cannot understand this HTC's nonsense (s-on/s-off, cid, hboot...) thats the exact reason why I have sold it. to complicated for me...
I just want it up and running, and trust me, I will never EVER buy another HTC again.
Click to expand...
Click to collapse
Since there are two different versions of your firmware and I don't know which one is the correct one for you I would suggest you to use this firmware and downgrade to 1.32.401.8. This works because the aboot has not been updated until now. The process itself is very easy:
Download the RUU
Rename it to 0PJAIMG.zip (that's a zero at the beginning not an O)
Copy the file on an external SD card that is formatted to fat32 and not bigger than 32 gb
Boot into download mode
Follow the instructions that are shown on your M9's screen
Congratulation you are now back on stock rom and firmware
You have to use either this way or the fastboot flashing method since there are no RUU executables for the european version.
Btw: No one here forced you to buy the M9. Since it's simply a matter of taste it's up to you which device you choose. I personally prefer HTC's user friendliness in regard to bootloader unlock and rooting (compare it for example with Samsung's Knox system). But this is not the right place for that debate.
Edit: Since my phone is S-OFF I'm not completely sure but you might have to relock your bootloader or step 5 might no work properly.

I have the same problem, i wanna know how to restore it to full stock, i need it just in case something happens to phone and i need to use my waranty. I'm also on telenor serbia. Any detailed instructions would be much appreciated. And one more thing, will i be able to recevie OTA updates even though its rooted ?

Djomla87 said:
And one more thing, will i be able to recevie OTA updates even though its rooted ?
Click to expand...
Click to collapse
Root by itself doesn't prevent OTAs, but changes to the recovery do. As far as I know, acquiring root (for this device) always involves flashing a custom recovery. So OTA aren't possible until the stock recovery is restored.

Do I need to have sd card, or can I flash it from pc using adb?
I have already tried this method, and fastboot gave me an error 22? Maybe I got wrong firmware. Will try again, thanks.

computerslayer said:
Root by itself doesn't prevent OTAs, but changes to the recovery do. As far as I know, acquiring root (for this device) always involves flashing a custom recovery. So OTA aren't possible until the stock recovery is restored.
Click to expand...
Click to collapse
Ok so how do i restore stock recovery?

You flash stock recovery zip that can be found on xda.

acasmc said:
You flash stock recovery zip that can be found on xda.
Click to expand...
Click to collapse
What version ?

As far as I know, there is only one. Search in forums.

This is what I get when try to flash from adb.
used the file from post on first page,

try this RUU: http://androidruu.com/getdownload.p...6.02.50306G_2_F_release_429340_signed_2_4.exe

I'm also interested if it's possible to go back to stock from a S-ON with RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4.exe
Good to know basis

dondavis007 said:
I'm also interested if it's possible to go back to stock from a S-ON with RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4.exe
Click to expand...
Click to collapse
If you are S-ON you can only flash a RUU for your carrier and device. If that's the correct RUU for your phone, it will do it.

iElvis said:
If you are S-ON you can only flash a RUU for your carrier and device. If that's the correct RUU for your phone, it will do it.
Click to expand...
Click to collapse
The question is where can you find correct RUU from specific carrier

So if you're an European open you can't really flash without s off?
Skickat från min HTC One M9 via Tapatalk

Djomla87 said:
The question is where can you find correct RUU from specific carrier
Click to expand...
Click to collapse
There is a RUU list in the General forum. Not all configurations have RUUs, unfortunately, as it has always been with HTC.
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545

By far the easiest way for the inexperienced is to use the windows exe version linked to a few posts ago .
If you're on 1.32.401.15 then simply flash 1.32.401.17 using the exe version. Simply run windows program and follow on screen prompts .
Main limitation if you're S on is it will only allow upgrade that is to go to higher number as described .
I think there is also a 1.32.401.8 exe but that's an earlier version so if you tried to use that and you were on higher version such as 1.32.401.15 then it wouldn't allow unless you had obtained S off.
Sent from my HTC One M9 using XDA Free mobile app

One more thing, i received lates OTA update, but it wont instal because recovery isnt stock. I found stock signed, when i flash it will the phone factory reset or not ?

Flash stock rom with broken HTC M8

Hello,
I've got a damaged HTC m8 That lost the system and s-off, i know the MID and CID, Already have a working Recovery manager (TWRP),but when i try to install cyanogen it stucks in the cyanogen logo pulsing then reboots, i'd like to know if there's a way to make it S-off and install a stock rom in it.
Attachements contain the information.

Eislei said:
Hello,
I've got a damaged HTC m8 That lost the system and s-off, i know the MID and CID, Already have a working Recovery manager (TWRP),but when i try to install cyanogen it stucks in the cyanogen logo pulsing then reboots, i'd like to know if there's a way to make it S-off and install a stock rom in it.
Attachements contain the information.
Click to expand...
Click to collapse
Your M8 is sprint, your firmware is too old, that's why newer rom's wont boot. Try flashing this cm11 http://get.cm/get/jenkins/90466/cm-11-20141112-SNAPSHOT-M12-m8.zip . I'll try to find stockish sprint 4.4.x rom so you can do S-off.
https://www.androidfilehost.com/?fid=23622183712460230 Viper is based on stock, you can try to flash this and see if boots and if boots, do s-off via sunshina($25) and flash latest sprint ruu

Eislei said:
I've got a damaged HTC m8 That lost the system and s-off
Click to expand...
Click to collapse
What does that mean "damaged"? It just started not booting, and lost s-off? Or did you physically damage it? Describe exactly what happened, in detail; otherwise we can't help properly.

Only software damaged, the phone worked for a week and shut down, even with full charge, then it didn't want to turn on at all, and no system is found in it now, it's not my phone i just took it from a friend to repair it, but it appears that there's no backup system

Imotep95 said:
Your M8 is sprint, your firmware is too old, that's why newer rom's wont boot. Try flashing this cm11 http://get.cm/get/jenkins/90466/cm-11-20141112-SNAPSHOT-M12-m8.zip . I'll try to find stockish sprint 4.4.x rom so you can do S-off.
https://www.androidfilehost.com/?fid=23622183712460230 Viper is based on stock, you can try to flash this and see if boots and if boots, do s-off via sunshina($25) and flash latest sprint ruu
Click to expand...
Click to collapse
Will try cyanogen first, because i tried CM12 / 13 And it get stuck in boot loop while it's trying to load
Downloading viper too.
Update :
When i installed Viper, and i swipe to unlock the lock screen, there's only an HTC logo for minutes, then i go past the configuration (like it's its first use), at the 4th step the phone reboots on its own
Thanks

Eislei said:
Will try cyanogen first, because i tried CM12 / 13 And it get stuck in boot loop while it's trying to load
Downloading viper too.
Update :
When i installed Viper, and i swipe to unlock the lock screen, there's only an HTC logo for minutes, then i go past the configuration (like it's its first use), at the 4th step the phone reboots on its own
Thanks
Click to expand...
Click to collapse
So, the phone just shuts down? Than it's the hardware issue.

Imotep95 said:
So, the phone just shuts down? Than it's the hardware issue.
Click to expand...
Click to collapse
Thanks you.
No, now it's working perfectly, left it on for the day, it didn't reboot once, the only hiccup is the camera app, no matter how many camera apps i download they crash on launch.
For now i think i'll S-Off the phone and install a stock sprint firmware, if it's possible of course.

Eislei said:
For now i think i'll S-Off the phone and install a stock sprint firmware, if it's possible of course.
Click to expand...
Click to collapse
You don't need s-off to return to stock. Additionally the only current method to s-off is sunshine, which costs $25; unless sunshine was previously used to s-off, in that case it may work again for no additional charge. But sunshine requires a stockish (Sense) ROM, anyway.
---------- Post added at 10:20 AM ---------- Previous post was at 09:56 AM ----------
Something looks really screwy here. The radio baseband in the first post isn't a number that corresponds to Sprint. It should be 1.08xxx or 1.09xxx according to this: http://forum.xda-developers.com/showthread.php?t=2700666
The radio number 1.22.21331147A1.29 is for the Euro WWE version. Since the phone was s-off as you stated, it appears somebody tried to flash a WWE radio/firmware to the phone, in an attempt to "convert" it to a Euro version. I'm surprised the phone isn't radio bricked.
I suggest you relock the bootloader and try to RUU back to stock using one of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=2729173
This should return the phone to the proper Sprint firmware.
Be warned, and I can't and won't be held responsible for anything that happens from this suggestion. Official RUU is normally very safe. But in the case where a botched conversion was previously performed, all bets are off. Severe radio issues are possible.

redpoint73 said:
You don't need s-off to return to stock. Additionally the only current method to s-off is sunshine, which costs $25; unless sunshine was previously used to s-off, in that case it may work again for no additional charge. But sunshine requires a stockish (Sense) ROM, anyway.
---------- Post added at 10:20 AM ---------- Previous post was at 09:56 AM ----------
Something looks really screwy here. The radio baseband in the first post isn't a number that corresponds to Sprint. It should be 1.08xxx or 1.09xxx according to this: http://forum.xda-developers.com/showthread.php?t=2700666
The radio number 1.22.21331147A1.29 is for the Euro WWE version. Since the phone was s-off as you stated, it appears somebody tried to flash a WWE radio/firmware to the phone, in an attempt to "convert" it to a Euro version. I'm surprised the phone isn't radio bricked.
I suggest you relock the bootloader and try to RUU back to stock using one of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=2729173
This should return the phone to the proper Sprint firmware.
Be warned, and I can't and won't be held responsible for anything that happens from this suggestion. Official RUU is normally very safe. But in the case where a botched conversion was previously performed, all bets are off. Severe radio issues are possible.
Click to expand...
Click to collapse
Tried the Non hk version and HK versions, but to no result, and yes the radio version is what took my attention when i opened the fastboot menu.
I'll try that this weekend and take screenshots of the result, because whenever i try to install them they show me a message that the device is not compatible for some reason.
I tried revolution HD, it installs but when it reboot it goes back to fastboot, tried viper (as stock), i have the setup wizard, after i skip the wifi settings it shows a screen for a split second at reboot the phone.

Eislei said:
Tried the Non hk version and HK versions, but to no result, and yes the radio version is what took my attention when i opened the fastboot menu.
I'll try that this weekend and take screenshots of the result, because whenever i try to install them they show me a message that the device is not compatible for some reason.
Click to expand...
Click to collapse
Which version numbers (file name) did you try exactly.
Try the Lolliop RUU 4.25.651 and see what happens. RUU to Marshmallow (RUUs 6.20) is slightly more complicated (you have to flash the MM firmware first, then RUU - this might be the reason for the error).

redpoint73 said:
Which version numbers (file name) did you try exactly.
Try the Lolliop RUU 4.25.651 and see what happens. RUU to Marshmallow (RUUs 6.20) is slightly more complicated (you have to flash the MM firmware first, then RUU - this might be the reason for the error).
Click to expand...
Click to collapse
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe
I tried this one, but at some point it says it's not the right device for some reason

Eislei said:
http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe
I tried this one, but at some point it says it's not the right device for some reason
Click to expand...
Click to collapse
It likely seeing the firmware is the wrong number (doesn't correspond to Sprint firmware) and that is why its telling you wrong RUU.
Your best bet is to fastboot flash firmware.zip for 4.25.651.14. Then try RUU again.
http://forum.xda-developers.com/showthread.php?t=2729173

HELP need serious advice here.

Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.

kalel29 said:
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
Click to expand...
Click to collapse
For download mode SD card method:
Make sure you're using an external SD card, not internal storage.
Make sure SD card is formatted properly.
Make sure file is named 100% correctly and is meant for that specific carrier /model.
No reason it shouldn't work.
Sent from my HTC6545LVW using Tapatalk

kalel29 said:
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Click to expand...
Click to collapse
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.

Flippy498 said:
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Click to expand...
Click to collapse
Yes I flashed the one for my operator. Can I flash another RUU?
About your links, I'll check them when I get back from work. Thanks.

Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.

Flippy498 said:
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Click to expand...
Click to collapse
Hi again, the phone is giving me this error :

im still lost ,hope this helps to point me in the right direction.
Code:
D:\Francisco\Desktop\HTC\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.44.600.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: HTC__332
all:
finished. total time: 0.033s
Thanks

You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.

Flippy498 said:
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Click to expand...
Click to collapse
Ok,thanks, and yes,the RUU I was trying to flash I the telcel one.
I'm going to tell my fiend that he needs to pay in order to get his phone working.
Thanks again for everything. Have a nice day.

Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.

kalel29 said:
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
Click to expand...
Click to collapse
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.

Flippy498 said:
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Click to expand...
Click to collapse
The phone has the ICE rom,Twrp and superSU,I think it's a sense-based rom, sorry I can't give you more info, as I said I'm new in flashing HTC, but I'm learning thanks to you.

ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.

Flippy498 said:
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Click to expand...
Click to collapse
So basically, no matter what rom I flash,sense or no sense based, I will need sunshine in order to have a working baseband?

No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.

Flippy498 said:
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Click to expand...
Click to collapse
Finally i have signal again,flashed slim 6 and monokernel. Thank you so much,i've learned something new about HTC now im going to return the phone to my friend,also i explained what you told me in order to have a sense based rom.

Tmobile: Relocked: S-ON: Stuck in bootloaded

Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!

jdub1983 said:
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader?

xunholyx said:
What does it say next to "OS" in your bootloader?
Click to expand...
Click to collapse
Nothing is listed next to os in the bootloader mene
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jdub1983 said:
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
Click to expand...
Click to collapse
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
jdub1983 said:
I any attempts using flashboot do not work.
Click to expand...
Click to collapse
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.

redpoint73 said:
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
Click to expand...
Click to collapse
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
If you give me a few things to do when I'm in front of the computer I'll execute them later on and report back the results.

jdub1983 said:
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
jdub1983 said:
None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
jdub1983 said:
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
Click to expand...
Click to collapse
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?

redpoint73 said:
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
Click to expand...
Click to collapse
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!

jdub1983 said:
I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
Click to expand...
Click to collapse
I didn't specify that it had to be an error code number. If the response is all text, tell us what it is. Cut and paste, or do a screenshot, if that is easier. Either way, it will probably tell me what is going wrong.

jdub1983 said:
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
Click to expand...
Click to collapse
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off

xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?

xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.

jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
No, they aren't.
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
EDIT: I see now that Redpoint has already linked you up. :good: Easier for me

xunholyx said:
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
Click to expand...
Click to collapse
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.

redpoint73 said:
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
Click to expand...
Click to collapse
Gotcha! If I'm s-on though, how did everything get screwed up? Guess it's not important now.
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom. Something simple really, my m8 is my backup phone.

redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!

jdub1983 said:
If I'm s-on though, how did everything get screwed up?
Click to expand...
Click to collapse
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
jdub1983 said:
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom.
Click to expand...
Click to collapse
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.

redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
redpoint73 said:
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
Click to expand...
Click to collapse
I'll give it a whirl when I get home and let you know of any errors, if any, hopefully not.
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Thanks again!

jdub1983 said:
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Click to expand...
Click to collapse
I doubt it. Rather, I think your syntax was incorrect (if you typed it exactly as you did before) as the part "RUU" (no quotes) should be in caps:
fastboot oem rebootRUU
If the phone is in RUU mode, it will show a black screen, with HTC logo.

jdub1983 said:
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
Click to expand...
Click to collapse
Here's the RUU.zip for you.

you both are amazing, thank you!
I feel so silly, considering I was using sneaky ghosts unsigned fullwipe firmware... Blah!
Again, you both are awesome, kind to a moron! The universe will provide for you both!
Thanks again!!!
Everything is working wonderful!!!!!

HTC RUU exe file can't get beyond InstallShield Wizard

HTC 10
S-Off CID
BS_US001
Android 7.0 July 1, 2017 security patch
Kernel [email protected] #1 SMP PREMEPT
Baseband [email protected]_76.02_F
Build 2.51.617.1 8.0_g CL942117 release-keys
Bootloader unlocked and rooted with SU
TWRP 3.1.1
Recently installed Viper10 5.11.0 ROM. Trying to return to stock but cannot. I have tried running several HTC RUU exe files (including RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.41.617.3 RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21
PMEWL_2.51.617.32_NoWipe_TWRP3110).
Nothing works. The RUU files start InstallShield Wizard but when it gets end of the progress bar, the wizard stops and nothing else happens. I've Run As Admin and disabled AV/Firewall. Nothing.
I've tried to install zip versions of same RUU files, both using Fastboot and moving to internal/card storage of the phone. No ZIP file will return unit to stock.
Using the RUU should be the best option but the RUU file always fails when the Wizard's progress bar gets to the end. Why does the RUU fail every time?

Refer to this thread to change your CID to verizon.
https://forum.xda-developers.com/verizon-htc-10/how-to/guide-convert-unlocked-to-verizon-t3380615

adamocca said:
HTC 10
S-Off CID
BS_US001
Android 7.0 July 1, 2017 security patch
Kernel [email protected] #1 SMP PREMEPT
Baseband [email protected]_76.02_F
Build 2.51.617.1 8.0_g CL942117 release-keys
Bootloader unlocked and rooted with SU
TWRP 3.1.1
Recently installed Viper10 5.11.0 ROM. Trying to return to stock but cannot. I have tried running several HTC RUU exe files (including RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.41.617.3 RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21
PMEWL_2.51.617.32_NoWipe_TWRP3110).
Nothing works. The RUU files start InstallShield Wizard but when it gets end of the progress bar, the wizard stops and nothing else happens. I've Run As Admin and disabled AV/Firewall. Nothing.
I've tried to install zip versions of same RUU files, both using Fastboot and moving to internal/card storage of the phone. No ZIP file will return unit to stock.
Using the RUU should be the best option but the RUU file always fails when the Wizard's progress bar gets to the end. Why does the RUU fail every time?
Click to expand...
Click to collapse
What does it say next to CID, MID, and OS in bootloader mode?
You are S-Off, so instead of running an RUU, you can flash a no-wipe firmware package (an RUU will wipe your phone). With that information I can link you to a no-wipe firmware, with instructions to flash it.

Thanks, but I don't want to change CID to Verizon. It's a GSM phone, not CDMA. It's unlocked (617). But I do understand the confusion. The HTC Dev site downloads an RUU that is seemingly for Verizon even though it's listed under the Unlocked Phone section.

Thanks. Bootload mode shows CID as BS_US001, MID as 2PS650000 and OS as 2.51.617.32. I have tried to flash (using both TWRP and Fastboot) a no-wipe firmware (namely PMEWL_2.51.617.32_NoWipe_TWRP3110) but it hasn't returned me to stock. Nothing takes and the only thing I can do to revive the phone is reflash (using TWRP) the Viper10 rom. I can live with the Viper10 rom but I'd like to return to stock so I can get HTC OTA, etc. I figure the most likely way to accomplish this is to use the HTC Dev RUU but, as mentioned, it never gets past the InstallShield Wizard.
Interesting that the Bootloader shows a different OS version than checking through the phone's software. In any event, I am definitely running Viper10 and it uses an older Build as its base.

adamocca said:
Thanks. Bootload mode shows CID as BS_US001, MID as 2PS650000 and OS as 2.51.617.32. I have tried to flash (using both TWRP and Fastboot) a no-wipe firmware (namely PMEWL_2.51.617.32_NoWipe_TWRP3110) but it hasn't returned me to stock. Nothing takes and the only thing I can do to revive the phone is reflash (using TWRP) the Viper10 rom. I can live with the Viper10 rom but I'd like to return to stock so I can get HTC OTA, etc. I figure the most likely way to accomplish this is to use the HTC Dev RUU but, as mentioned, it never gets past the InstallShield Wizard.
Interesting that the Bootloader shows a different OS version than checking through the phone's software. In any event, I am definitely running Viper10 and it uses an older Build as its base.
Click to expand...
Click to collapse
Software in setting> about is your ROM base, OS in download mode is your firmware version.
Do you have HTC Sync installed on your PC? Try uninstalling it and running the RUU again. You could also try running it while your phone is booted to download mode.

Yup, I've installed fresh drivers via HTC Sync and the PC recognizes the phone no problem.
ADB and fastboot also see the phone. I've tried the RUU in download mode,
bootloader and even OEM rebootRUU. Nada. In all cases the RUU InstallShield Wizard starts and then stops when it reaches the end of the progress bar. It never even gets to the actual RUU install routine (which I've used in the past with my HTC M9, so I know how it works when it flashes correctly). I'm running out of ideas. I'm happy with Viper10, if I can't get back to stock.

Try this https://www.reddit.com/r/htc/comments/2vxite/ruu_exe_file_doesnt_load_closes/colxuoy/
I've had the same problem while running on win 10 ltsb 2016 and this seemed to fix the problem.

adamocca said:
Thanks. Bootload mode shows CID as BS_US001, MID as 2PS650000 and OS as 2.51.617.32. I have tried to flash (using both TWRP and Fastboot) a no-wipe firmware (namely PMEWL_2.51.617.32_NoWipe_TWRP3110) but it hasn't returned me to stock. Nothing takes and the only thing I can do to revive the phone is reflash (using TWRP) the Viper10 rom. I can live with the Viper10 rom but I'd like to return to stock so I can get HTC OTA, etc. I figure the most likely way to accomplish this is to use the HTC Dev RUU but, as mentioned, it never gets past the InstallShield Wizard.
Interesting that the Bootloader shows a different OS version than checking through the phone's software. In any event, I am definitely running Viper10 and it uses an older Build as its base.
Click to expand...
Click to collapse
If your OS says 2.51.617.32, then you are on the latest firmware now. Seems like the no-wipe firmware worked after all. The firmware won't return you to stock.
If you want to go back to stock and not just update your firmware, you could try flashing a 2.51.617.32 RUU.zip via your extSD instead of running the RUU.exe.
I can upload the RUU.zip if you need it.

Thanks again for the help. I have the following RUU downloaded from the HTC Dev site: RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I also found what I believe is the ZIP version of that RUU: 2PS6IMG_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I've tried both running the RUU.exe and flashing the ZIP from my externalSD. No luck with either. Viper10 stays stubbornly stuck as my ROM. If you have a better ZIP, I'd be happy to try that too.

Thanks. I saw this suggestion as well in my hunt for a solution.
I've reloaded every.... possible... redistributable... with no success.
At least my C++ Visual Studio redistributables are up to date.
I can't even get the the license acceptance screen on the RUU install wizard.
I crash out before then.

Thanks. I found the same suggestion in my hunt for a solution.
I've updated every single redistributable... with no success. At least my PC is up-to-date with C++ Visual Studio. :-/

adamocca said:
Thanks again for the help. I have the following RUU downloaded from the HTC Dev site: RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I also found what I believe is the ZIP version of that RUU: 2PS6IMG_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I've tried both running the RUU.exe and flashing the ZIP from my externalSD. No luck with either. Viper10 stays stubbornly stuck as my ROM. If you have a better ZIP, I'd be happy to try that too.
Click to expand...
Click to collapse
First of all, you should use the reply/quote button when responding to a comment. It makes it easier to tell who you are replying to, and who you are replying to will get a notification about it.
Okay, delete any RUU.zips you already have on your ext SD
Download this
Rename it by deleting everything in the name of the .zip except for 2PS6IMG (and .zip of course) and place it onto your ext SD card
Boot to download mode and your phone will recognize the .zip and prompt you to press volume up to confirm the flash. Do that
When the flash is complete your phone will ask you to press power to reboot. Do that
After the RUU has flashed, either delete the .zip or rename it again to something else (add _2.51.617.32 to the name so you know what it is). If you don't do that, every time you boot to download mode your phone will try to update again.
Good luck!

xunholyx said:
First of all, you should use the reply/quote button when responding to a comment. It makes it easier to tell who you are replying to, and who you are replying to will get a notification about it.
Okay, delete any RUU.zips you already have on your ext SD
Download this
Rename it by deleting everything in the name of the .zip except for 2PS6IMG (and .zip of course) and place it onto your ext SD card
Boot to download mode and your phone will recognize the .zip and prompt you to press volume up to confirm the flash. Do that
When the flash is complete your phone will ask you to press power to reboot. Do that
After the RUU has flashed, either delete the .zip or rename it again to something else (add _2.51.617.32 to the name so you know what it is). If you don't do that, every time you boot to download mode your phone will try to update again.
Good luck!
Click to expand...
Click to collapse
Tada! That worked. I was able to flash the ZIP you sent and restored to stock 2.51.617.32. I still have no idea why the RUU exe file won't work but as usual there is more than one way to skin a cat -- or in this case, flash an HTC 10. Also not sure why prior attempts to flash a ZIP from the external SD didn't work.
Thanks for all your help (and patience).

adamocca said:
Tada! That worked. I was able to flash the ZIP you sent and restored to stock 2.51.617.32. I still have no idea why the RUU exe file won't work but as usual there is more than one way to skin a cat -- or in this case, flash an HTC 10. Also not sure why prior attempts to flash a ZIP from the external SD didn't work.
Thanks for all your help (and patience).
Click to expand...
Click to collapse
You are welcome
I'm not sure what was going on with the .exe not working, but I knew this would.
I'm glad that I could help.

xunholyx said:
First of all, you should use the reply/quote button when responding to a comment. It makes it easier to tell who you are replying to, and who you are replying to will get a notification about it.
Okay, delete any RUU.zips you already have on your ext SD
Download this
Rename it by deleting everything in the name of the .zip except for 2PS6IMG (and .zip of course) and place it onto your ext SD card
Boot to download mode and your phone will recognize the .zip and prompt you to press volume up to confirm the flash. Do that
When the flash is complete your phone will ask you to press power to reboot. Do that
After the RUU has flashed, either delete the .zip or rename it again to something else (add _2.51.617.32 to the name so you know what it is). If you don't do that, every time you boot to download mode your phone will try to update again.
Good luck!
Click to expand...
Click to collapse
Hello! I am having the same issue; however, I am S-ON. Do you have the RUU of the file you referenced? Many thanks!

dburger66 said:
Hello! I am having the same issue; however, I am S-ON. Do you have the RUU of the file you referenced? Many thanks!
Click to expand...
Click to collapse
That is the RUU I linked.
You could get the RUU.exe that you can run from your PC from HTC's official US website here.
But if you want to flash from SD that's the one. It works with S-On as well.

xunholyx said:
That is the RUU I linked.
You could get the RUU.exe that you can run from your PC from HTC's official US website here.
But if you want to flash from SD that's the one. It works with S-On as well.
Click to expand...
Click to collapse
Thank you!

xunholyx said:
That is the RUU I linked.
You could get the RUU.exe that you can run from your PC from HTC's official US website here.
But if you want to flash from SD that's the one. It works with S-On as well.
Click to expand...
Click to collapse
Does this require an external sdcard?
Thanks

redesignni said:
Does this require an external sdcard?
Thanks
Click to expand...
Click to collapse
No. You can run the .exe on your PC, or flash the .zip in fastboot with
fastboot flash zip 2PS6IMG.zip after renaming it to 2PS6IMG.zip