Related
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
Hi,
Here's my story: I have a factory unlocked M9 bought in Belgium. After reading in XDA, I unlocked the loader, and install TWRP (2.8.5.0). I then made a backup and installed ARHD 5.2.
Everything worked fine, until I decided to sell my device (I live in Argentina, and although I bought the international version, it does not cover 4G band 4). So in order to sell it I wanted to wipe everything back to factory settings. I went ahead and restore my backup. Again everything worked flawlessly, but then I saw some folders in the internal storage that were not supposed to be there (such as maildroid folder, among others). So I went back to TWRP, wipe, advanced, "delete internal SD". oops, wrong choice...
I rebooted and then notices appeared "Unfortunately UI has stopped..../ unfortunately easyaccess has stoped...", losing all functionalities (no touch buttons, I had to restart every time I wanted to change menus).
I restored again the backup...no luck. I then installed again AR 5.2...no luck.
I wanted to RUU (I am not sure I know what it is, but I do know how to follow step by step guides...well at least sometimes...). my phone is S-ON. I tried installing sunshine to S-OFF, but I got the message "No SD card", so it wouldn't let me install it. in fact when I use the HTC file explorer it looks as if there is nothing in the internal storage.
I don't think I can fastboot (USB not recognized). I read that phones needed to be S-OFF ( http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545 ), so I don't know what else to do.
I really tried all related posts but I can't find the answer....
Any help is really appreciated (of course I couldn't sell the phone). Thanks.
A RUU is a Rom Update Utility. It's a little program made by HTC to reinstall a stock firmware and/or rom on a phone that is S-ON. Depending on the build number and the CID of your phone the needed RUU is an *.exe or a *.zip.
Are you still able to enter Settings>About>Software Information>More? (Not completely sure whether these are the correct english terms. On my phone it's Einstellungen>Info>Software-Informationen>Mehr.) There you can find the build number of the installed firmware if you are on stock rom.
Otherwise you need to boot into download mode where you can find the build number (written in the line with "OS" at the beginning) and the CID of your phone. Since you never mentioned any branding and you bought the phone in Belgium I'm assuming that the CID is something like HTC__*** and that you can use a European RUU.
Next you need to download the corresponding RUU for your build number (just use Ctrl+F for easier searching) and your CID. Since the CID isn't explicitly mentioned in the RUU names you may have to search for the meaning of your phones CID (for example in a list like this one).
If the needed RUU is a *.zip then you have to rename the file to 0PJAIMG.zip (that's a zero not an O), copy it on an external sd card that is not bigger than 32gb and formatted to fat32 and put the sd card into your phone. If you now enter download mode your phone should guide you through the rest of the procedure.
If the needed RUU is an *.exe then you just have to connect you phone to your pc and start the file (on windows).
Flippy498 said:
Are you still able to enter Settings>About>Software Information>More? (Not completely sure whether these are the correct english terms. On my phone it's Einstellungen>Info>Software-Informationen>Mehr.) There you can find the build number of the installed firmware.
Click to expand...
Click to collapse
I had access, the build number is 1.32.401.17 CL506785 release keys. However from download mode I got Mainversion: 1.32.401.15. So I guess I have to use the latter right? I do not need to be S-OFF, because I can't make it....
Flippy498 said:
Then you need to downlad the corresponding RUU (just use Ctrl+F and enter the build number for easier searching), rename it to 0PJAIMG.zip (that's a zero not an O), copy it on an external sd card that is not bigger than 32gb and formatted to fat32. If you put this sd card into your phone and enter download mode your phone should guide you through the rest of the procedure.
Click to expand...
Click to collapse
Ok there are two 1.32.401.15 version for Europe,that only differs in the release: Which should I use
1. 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
2. 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R2_Radio_01.01_U11440261_56.02.50306G_2_F_release_427846_signed.zip
Flippy498 said:
Edit2: I forgot another important thing. (Sorry, I'm in a little hurry right now.) Your CID needs to correspond to the RUU you want to run. Since you never mentioned any branding I'm assuming that it is something like HTC__*** so that you can use a European RUU. You can find out by booting into download mode. (I'm not completely sure whether it's written there if you are S-ON. If not you can either try using an app like CID Getter or the fastboot command "fastboot getvar all".) If your CID differs from HTC__*** I would suggest you to post it here together with the build number so that it's easier for me or someone else to guide you to the correct RUU.
Click to expand...
Click to collapse
I cannot install anything as the internal storage is not recognized by the OS. However I was able to fastboot:
OS-1.32.401.15
HTC__031
Kernel: lk
Thank you for your help!
gsember said:
I had access, the build number is 1.32.401.17 CL506785 release keys. However from download mode I got Mainversion: 1.32.401.15. So I guess I have to use the latter right? I do not need to be S-OFF, because I can't make it....
Click to expand...
Click to collapse
I think that the original stock was 1.32.401.15 as ARHD 5.2 that I flashed comes with the 1.32.401.17
Yes, that's right. Since there has not been an aboot update until now you can also try to install the 1.32.401.8 RUU and then update via the stock OTA function. I've done this with my phone before I got S-OFF so I know that it works. This way you can be sure that the correct version of the 401.15 firmware gets installed.
Flippy498 said:
Yes, that's right. Since there has not been an aboot update until now you can also try to install the 1.32.401.8 RUU and then update via the stock OTA function. I've done this with my phone before I got S-OFF so I know that it works. This way you can be sure that the correct version of the 401.15 firmware gets installed.
Click to expand...
Click to collapse
Ok, I already installed the first release of 1.32.408.15. it worked flawlessly. Should I relock (or lock) the phone to receive OTA?
Use a 32 GB card tip saved my day! ( I had a 128 GB which the phone didn't read)
Thank you all.
I am now trying the second release as the first one did not recognize 5G wifi networks.
Is it possible to receive OTA once you have an unlocked bootloader? XX.15 is the latest version? because ARHD has XX.17?
thanks again
Actually I don't know whether it's necessary to relock the bootloader if you want to install an OTA but I would guess it is. The 401.15 version is the latest European one. 401.17 is only receivable on HTC__J** but llabtoofer stated on his twitter account that the next European update is waiting around the corner.
You mentioned earlier that you cannot connect your phone with your PC and that fastboot isn't working. Did you try to connect your phone to another PC/Laptop (maybe your parents/siblings/friends can help you out if you don't own another one)? As far as I know there is no way to relock bootloader without a PC.
Flippy498 said:
Actually I don't know whether it's necessary to relock the bootloader if you want to install an OTA but I would guess it is. The 401.15 version is the latest European one. 401.17 is only receivable on HTC__J** but llabtoofer stated on his twitter account that the next European update is waiting around the corner.
You mentioned earlier that you cannot connect your phone with your PC and that fastboot isn't working. Did you try to connect your phone to another PC/Laptop (maybe your parents/siblings/friends can help you out if you don't own another one)? As far as I know there is no way to relock bootloader without a PC.
Click to expand...
Click to collapse
Thanks. Everything is working smoothly. Actually fastboot is working. I won't continue to play.....
Appreciate your answers
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0
Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).
Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA
I recently bought an Unlocked HTC one M9 from eBay. It was on Android 5.0.2 (1.32.617.6) and I received an update notification for 1.32.617.30. When I clicked to install it, it fails saying error in cache with error 7. I think since it's a used phone the device software has been tampered before therefore the OTA update fails. I don't know the device history.This is what I found in bootloader mode.
Software status: Official
S-OFF
Bootloader:Locked
It is super CID (11111111)
And it has stock recovery.
I have tried flashing 1.32.617.6 stock ROM from stock recovery after I found it on XDA. It also failed saying signature verification failed. I searched this forum and found that someone had the same issue and they had to flash 1.32.617.6 using a SD card formatted to FAT32. I don't have a SD card so I couldn't try it.
I also tried HTC's latest RUU. EXE for Unlocked/Developer edition but it doesn't run well. It starts and shuts down after it asks me to agree to terms and conditions. I have latest HTC sync manager and it recognizes my phone. I will be trying this again on some other computer.
I really want to update my device to the latest version of OS. Please help me! I don't know what else to try.
You cannot flash an ruu because the device is modified. The easiest option is to flash an unsigned update. Unlock your bootloader and enable usb debugging first though.
Beamed in by telepathy.
I don't understand in what way the device is modified because it says bootloader Locked not relocked and everyrhing is stock. I thought it might have been restored to stock after rooting or what not. If that is the case shouldn't I be able to install OTA update?
Anyways I wanted to know if there is some way where I don't need to unlock bootloader or root it. I want to stay on stock OS.
Update: used RUU.EXE on Windows 7 computer and it worked. For some reason Windows 8/10 is not good with running external exe files.
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