Develop Bugs

Evo ruu problems

Yesterday I ran my evo through an ruu to get it to stock 2.2. After I did this I realized that there was a newer ruu. So I downloaded it but when I ran it it said that it could not find my evo. I have been running the ruus through fastboot. Any help would be greatly appreciated.

Did you run the 3.70 RUU?

Yes. I also went ahead and tried to do the HTC sync way but it says it can't find my phone after I start it.

You have sync still installed? Also the HBOOT drivers? Try uninstalling sync and run it again.

Alright. Do you mean the hboot drivers that you use when rooting?

Yurp, the very same drivers.

So I just install the hboot drivers then run the ruu through fastboot?

Right. Boot the phone into fastboot, connect to pc, once it shows up as fastboot usb on the phone, then run the RUU exe.

Alright thanks ill try it when I get home.

Why dont you just download the PC36IMG.zip and run it in the boot loader? So much easer IMO.

How do I do this?

http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.70 ruu /jan 2011, boot your phone into fastboot, connect to pc, once is shows fastboot usb on your phone, then run the ruu exe.

No I meant the other guy that posted.

Ah, well basically you find a PC36IMG with the RUU things in it. Though I'm not sure if its the img or the exe, but it should be an RUU .img.

Alright ill try the thing you told me earlier.

Well it should work, but I'll be lingering by.

Do I also need to uninstall the drivers that come along with htc sync?

No, just un-install the program, you need the drivers.

It didn't work.

Actually I think I had a really old version of sync. I downloaded the one from the evo download section of their website and I think it will work this time.

Unrooting Evo

Alright I have an Evo with a broken usb port. I have tried flashing the 3.29 RUU that always worked for me before but that doesn't seem to unroot it because I can still get to the recovery. I downloaded the 3.70 RUU from here http://goo-inside.me/evo/stock/RUU/ but it just says "(bad)" and it aborts the installation. And every time I try to flash the stock PC36IMG it says the main version is older. I tried running the .exe update from my computer but it says it doesn't detect the phone I'm not sure what settings it supposed to be on i.e. USB debugging, just as a disk drive, or... I really need to take this phone back to sprint so if anyone has any suggestions.

http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip
Have you tried flashing a 3,70 RUU in PC36IMG form? Just place on the root of the sdcard. If you're still able to get into recovery, flash the S-On tool first, then the ruu.
http://unrevoked.com/rootwiki/doku.php/public/forever scroll down to Q&A for the S-ON tool.

gamefreke89 said:
Alright I have an Evo with a broken usb port. I have tried flashing the 3.29 RUU that always worked for me before but that doesn't seem to unroot it because I can still get to the recovery. I downloaded the 3.70 RUU from here http://goo-inside.me/evo/stock/RUU/ but it just says "(bad)" and it aborts the installation. And every time I try to flash the stock PC36IMG it says the main version is older. I tried running the .exe update from my computer but it says it doesn't detect the phone I'm not sure what settings it supposed to be on i.e. USB debugging, just as a disk drive, or... I really need to take this phone back to sprint so if anyone has any suggestions.
Click to expand...
Click to collapse
If you try the ruu again, try running it with the phone set in fastboot mode. Select fastboot from the bootloader menu, and see if it detects the phone then. Be sure USB debugging is checked.
Sent from my PC36100 using XDA App

Unrooted!
The bootloader would check the PC36IMG but it wouldn't actually flash it. I managed to get the usb port working long enough to run the ruu through my computer. Thanks for your help guys.

Is My Phone Bricked?

Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.

Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.

S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.

Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.

S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...

Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.

If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.

Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!

No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app

S-On Problem

Hey guys,
I have an unlocked At&T M8 which I'm currently using in the UK, but for some reason won't receive OTA updates (still stuck on 4.4.3). HTC Sync doesn't seem to work either, with it stuck on 'loading data'. So I stupidly decided to flash a rom without backup...
Since my hboot is still 3.16, WiFi doesn't work on any with any of the roms i have flashed. Is there anything I can try to at least get the WiFi working without paying $25 for sunshine? I can't seem to find a rom that supports 1.x firmware; if anyone could point me in the direction that would be awesome.

mrzebracookie said:
Hey guys,
I have an unlocked At&T M8 which I'm currently using in the UK, but for some reason won't receive OTA updates (still stuck on 4.4.3). HTC Sync doesn't seem to work either, with it stuck on 'loading data'. So I stupidly decided to flash a rom without backup...
Since my hboot is still 3.16, WiFi doesn't work on any with any of the roms i have flashed. Is there anything I can try to at least get the WiFi working without paying $25 for sunshine? I can't seem to find a rom that supports 1.x firmware; if anyone could point me in the direction that would be awesome.
Click to expand...
Click to collapse
Run the AT&T RUU. Personally, I would gain S-Off and convert to WWE/Europe. But the RUU is your best second option.
You can find the RUU and instructions on how to update your system manually on the official US HTC website. Link here.
Realize that RUNNING THE RUU WILL WIPE YOUR PHONE!!! So make sure to backup anything that is important to you.

xunholyx said:
Run the AT&T RUU. Personally, I would gain S-Off and convert to WWE/Europe. But the RUU is your best second option.
You can find the RUU and instructions on how to update your system manually on the official US HTC website. Link here.
Realize that RUNNING THE RUU WILL WIPE YOUR PHONE!!! So make sure to backup anything that is important to you.
Click to expand...
Click to collapse
Thank you, however HTC sync doesn't work so I downloaded the RUU from the link. The installer automatically shuts off after I accept licensing (I have relocked bootloader and put the phone in fastboot mode). The only PC in my house is running windows 8.1 :crying:
I even tried this guide http://forum.xda-developers.com/showthread.php?t=2735235, but windows won't let me open the rom.zip. Is there another way to flash the RUU on to my phone?
Also, do I need to download a recovery image if I'm using the RUU?

mrzebracookie said:
Thank you, however HTC sync doesn't work so I downloaded the RUU from the link. The installer automatically shuts off after I accept licensing (I have relocked bootloader and put the phone in fastboot mode). The only PC in my house is running windows 8.1 :crying:
Click to expand...
Click to collapse
Its a somewhat common issue. Might be the Win version, or USB 3.0 ports. If your PC has USB 3.0 ports, I saw a user mention you can turn off this function (make them 2.0) and that seemed to help the RUU.
Otherwise, you might need to borrow a friend's PC.
mrzebracookie said:
I even tried this guide http://forum.xda-developers.com/showthread.php?t=2735235, but windows won't let me open the rom.zip. Is there another way to flash the RUU on to my phone?
Click to expand...
Click to collapse
That guide is very clear what CIDs it works for, and yours is not one of them.
mrzebracookie said:
Also, do I need to download a recovery image if I'm using the RUU?
Click to expand...
Click to collapse
No

redpoint73 said:
Its a somewhat common issue. Might be the Win version, or USB 3.0 ports. If your PC has USB 3.0 ports, I saw a user mention you can turn off this function (make them 2.0) and that seemed to help the RUU.
Otherwise, you might need to borrow a friend's PC.
That guide is very clear what CIDs it works for, and yours is not one of them.
No
Click to expand...
Click to collapse
Thank you for the help. I got the RUU to work on a computer running Windows 7.
I know I have to relock the bootloader to have the RUU work, but the computer, and thus RUU, doesn't detect my phone in fastboot after relocking my bootloader. Fastboot displays 'fastboot USB', but the RUU doesn't detect anything. Before relocking, the computer detected my phone.
I have installed the latest HTC sync manager, so all the drivers should be installed.

mrzebracookie said:
Thank you for the help. I got the RUU to work on a computer running Windows 7.
I know I have to relock the bootloader to have the RUU work, but the computer, and thus RUU, doesn't detect my phone in fastboot after relocking my bootloader. Fastboot displays 'fastboot USB', but the RUU doesn't detect anything. Before relocking, the computer detected my phone.
I have installed the latest HTC sync manager, so all the drivers should be installed.
Click to expand...
Click to collapse
I can't tell if you are asking for more help, or just making a comment (and the RUU ran successfully)?
Having the bootloader locked, relocked or unlocked should have no bearing on whether fastboot connects or not. I think something else is/was going on, and the bootloader lock is just a false symptom/condition.

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