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
Related
i dont know exactly whats happened here, but i've tried to get my WFS sorted with a different rom than the carriers bloated version.
what i've done is updated hboot to 1.08.0099 and unlocked the boot loader sucessfully (hboot has *** UNLOCKED *** across the top; i used the HTCDEV.com process).
i believe i've got permanent root too.
when i attempt to flash CWM (via PG76IMG.zip), it appears to flash ok, but if i reboot the phone and try to access recovery, it just gets stuck on a white HTC screen.
i've redownloaded the CWM file to see if it's a corrupt download, but still the same problem.
CWM isnt a big issue, although it is nice to have.
however i also am unable to flash another rom either via the PG76IMG.zip SD method, or RUU.
i beleive i've done everything right, and i'm not entirely new to unlocking/rooting devices; only did my HTC Desire last week so the general process is still new in my head.
If your rooted install rom manager and flash recovery from there.
I had problems installing cwm from sd, so used the tool from here http://forum.xda-developers.com/showthread.php?t=1431969
previously was this one mediafire.com/?b0bsb4ms4lo714b
just plug the usb in sync and folow the instructions
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Pepie said:
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Click to expand...
Click to collapse
Firstly, I don't think it has anything to do with "not researching" enough but more to do with NOT reading what you "researched" already. You post a link to the RUU .zip that you wanted to use and obviously haven't picked up on the fact that the OP in that thread specifically stated: S-Off is Required with Eurpean CID right after admitting that you are NOT S-OFF.
Secondly: You don't need S-OFF to flash a custom ROM. You just need an unlocked bootloader and a custom recovery, that's it. You'll need S-OFF to fully convert the device to GPE though, as it makes changes to partition sizes.
Try to get back into bootloader again. Hold Volume UP + Power for 10 seconds the moment the feel a vibration and/or screen goes dark immediately hold Power + Volume Down to enter bootloader. You should still have TWRP on the device you didn't mention anything about taking it off. Head over to the RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection grab a nandroid backup for your device. Unpack it and place it inside the TWRP backup folder on your device. If you don't have one, make a backup of just "Boot" it'll then create the path for you.
Once done, restore the nandroid. That'll take you back to "stock" then.
Else, just place a custom ROM on the SDcard enter TWRP again and try to flash a custom ROM again.
What ROM did you try to flash? Perhaps give the link...
Oh and remove the 0P6BIMG.zip from the SDCard else it'll just keep on trying to flash it through HBoot.
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
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.
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