Develop Bugs

[Q] s-off issue

Well...this is the second day of countless hours i have invested trying to s-off. i think i may have a unique situation. so let us get started...
phone: Att htc one m8
recovery: twrp
rom: venom
s-off: no
hboot: 3.16.00.00 <-- sprint??
firewater...no
sunshine...no
revone...no
stock ruu...no
what i'm i missing? i can't change cid, hboot, or s-off. i can't ruu. and i am quite familiar with adb, fastboot, and cmd commands in general.

chaosjh said:
hboot: 3.16.00.00 <-- sprint??
Click to expand...
Click to collapse
That is the correct hboot for the AT&T version.
firewater worked for me on the AT&T version, same hboot. I did it on the stock ROM (1.54) rooted. So you might try to go back to a stock ROM. Several folks seem to be having trouble getting s-off on various custom ROMs.

I think this is the only thing that you got left, before considering paying or give it up. Retry S-OFF from stock rom.

What version of Windows? You sure adb/fastboot is connecting? I don't see why the RUU wouldn't run, as long as you have the right one.
What response to:
adb devices
and also
fastboot devices

Yes fastboot/adb commands work. I can getvar, see devices, reboot, push, ect. Recoveries flash fine. I removed HTC sync but I am using win 8.1 however I have never had issues like others have and I tried compatibility mode. Stock rooted Rom, still no go. I guess I can pull a win 7 out...
Any other ideas?
Edit: I have tried two ruu for att. Started both with sync installed, not installed, in system, in boot loader, and ruu mode...

here is more info

Have you also installed stock kernel with the stock rom
Renovated

Win 8.1 should work, although I think a minority of folks have had to jump through some hoops to get RUUs to work on 8.1. Here is what one guy did to get the RUU to work on Win 8.1: http://forum.xda-developers.com/showpost.php?p=53081344&postcount=94
May or may not be your issue, but its worth a look.

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

Lots of trouble unrooting M8...

I've been having a hell of a time trying to unroot my HTC One M8... It was an AT&T one I converted to Skydragon GPE, S-off. All the resources I try to use keep on failing somehow—anyone have suggestions? There's a million different tutorials on how to do it and none of them seem to work for me, getting really frustrated...
(I would link the below guides I've been trying to follow but I'm too new a user so it won't let me):
- The Unlockr guide: The Hassoon toolkit no longer exists.
- DroidViews guide: Everything's good until I try to restore the RUU image, then the executable fails with no explanation. Same when flashing the RUU from HTC's website.
- Restoring from a Nandroid backup in TWRP: Also never makes it through the entire process, I'd have to rerun it to see what the particular error was.
Ughhh is there any definitive set of steps I can take to actually restore to default settings? Preferably with the tampered flags not tripped, but honestly I don't even care at this point... Do I need to flash some stock AT&T HTC One M8 firmware or something before doing this all? Where might I be going wrong? I know it's vague but I'd love a solid walkthrough.
Thanks everyone

The simplest way would be to get an RUU from htc.com for AT&T, putting your phone in fastboot mode (power off, then pressing power+volume down, and selecting "fastboot"), and then simply launching the ruu. It should restore your phone to nearly being stock, except for your CID number and s-off. There are tutorials on how to change your cidnumber, however i am not sure how to turn s-off back to s-on.
http://www.htc.com/us/support/rom-downloads.html here you can find appropriate downloads

Ok, firstly, you might check out this thread: http://forum.xda-developers.com/showthread.php?t=2733523
None of the instructions require the use of anything beyond fastboot/adb. Also, make sure you put your CID/MID back if you changed them to run GPE. That isn't required to run Skydragon, but if you have altered them, put them back. Then rerun the RUU. Finally, since you are S-off, you can trivially fix any flags, so don't worry about that. (Running the RUU successfully will clear the modified flag anyway)

jshamlet said:
Ok, firstly, you might check out this thread: http://forum.xda-developers.com/showthread.php?t=2733523
None of the instructions require the use of anything beyond fastboot/adb. Also, make sure you put your CID/MID back if you changed them to run GPE. That isn't required to run Skydragon, but if you have altered them, put them back. Then rerun the RUU. Finally, since you are S-off, you can trivially fix any flags, so don't worry about that. (Running the RUU successfully will clear the modified flag anyway)
Click to expand...
Click to collapse
So I did this, starting from the Skydragon Sense 7 ROM:
made nandroid backup
flash 1.54.401.5 firmware
set cid to CWS__001
run RUU for the latest AT&T one. It says it will update from 1.54.401.5 to 2.6.502.16.
Result? Error 155 "Unknown Error", no other information.
Any ideas?

osdiab said:
I've been having a hell of a time trying to unroot my HTC One M8... It was an AT&T one I converted to Skydragon GPE, S-off.
Click to expand...
Click to collapse
Did you actually "fully convert" to GPE, or just flash Skydragon GPE?
What color is your hboot screen?
What hboot number, radio number?
osdiab said:
- The Unlockr guide: The Hassoon toolkit no longer exists.
Click to expand...
Click to collapse
The toolkit still exists. But it hasn't been updated in a very long time, and will therefore cause many many issues. So don't use the toolkit!
osdiab said:
- DroidViews guide: Everything's good until I try to restore the RUU image, then the executable fails with no explanation. Same when flashing the RUU from HTC's website.
Click to expand...
Click to collapse
Don't know what guide that is, or what RUU it tells you to use; but be aware that there are many RUU versions for the M8, and the RUU needs to be the proper one for your CID and MID. Also, Win7 or 8.1 is recommended (Win8 and especially Win10 will cause the RUU to fail).

redpoint73 said:
Did you actually "fully convert" to GPE, or just flash Skydragon GPE?
What color is your hboot screen?
What hboot number, radio number?
The toolkit still exists. But it hasn't been updated in a very long time, and will therefore cause many many issues. So don't use the toolkit!
Don't know what guide that is, or what RUU it tells you to use; but be aware that there are many RUU versions for the M8, and the RUU needs to be the proper one for your CID and MID. Also, Win7 or 8.1 is recommended (Win8 and especially Win10 will cause the RUU to fail).
Click to expand...
Click to collapse
hboot screen is white. hboot number is 3.19.0.0000. radio number is [email protected] I was using windows 8.1, though the computer I was using only has USB 3.0 ports (Apparently people say 2.0 is better?)
This is on the firmware that I was using for Skydragon, I can reflash the other firmware I had used for the failed RUU upgrade if that would be useful.

osdiab said:
hboot screen is white. hboot number is 3.19.0.0000. radio number is [email protected]
This is on the firmware that I was using for Skydragon, I can reflash the other firmware I had used for the failed RUU upgrade if that would be useful.
Click to expand...
Click to collapse
I'd leave it alone, and just try running the RUU.
osdiab said:
I was using windows 8.1, though the computer I was using only has USB 3.0 ports (Apparently people say 2.0 is better?)
Click to expand...
Click to collapse
Yes, folks have reported issues with RUU and USB 3.0. You can always try, the worst that will happen is the PC won't be able to talk to the phone.
Another user mentioned you can "disable" USB 3.0 in settings, but I'm not familiar with that.

redpoint73 said:
I'd leave it alone, and just try running the RUU.
Yes, folks have reported issues with RUU and USB 3.0. You can always try, the worst that will happen is the PC won't be able to talk to the phone.
Another user mentioned you can "disable" USB 3.0 in settings, but I'm not familiar with that.
Click to expand...
Click to collapse
OK, I've tried doing it on a computer that has USB 2.0 ports and once again, no go.
Trying to run the Developer/Unlocked RUU on HTC's website, it's stuck forever at 0/7 sending.
Trying to run the AT&T one, it errors out with a 155: Unknown Error message as soon as it boots to RUU mode.
Any other thoughts?

osdiab said:
Trying to run the AT&T one, it errors out with a 155: Unknown Error message as soon as it boots to RUU mode.
Click to expand...
Click to collapse
I think this means you need to relock your bootloader (required to RUU with s-on).

HTC One M8

I need some help...
My friend gave me his HTC One M8... But the build he use on is not working and I cannot connect to Google Play store... So basically cannot do anything with the phone...
How could I either, try to install a new build... Or reset the phone to factory default...
I am use to follow clear steps ( Network Administrator here ) but I need help at least sending me in the proper direction.
Thanks

Is the phone s-off? Power phone off, and press power+volume down....then write what the bootloader says...
Sent from my m8 using Tapatalk

jxcorex28 said:
Is the phone s-off? Power phone off, and press power+volume down....then write what the bootloader says...
Sent from my m8 using Tapatalk
Click to expand...
Click to collapse
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-INVALID-VER-INFO
OpenDSP-INVALID-VER-INFO
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.0

pSyToR said:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-INVALID-VER-INFO
OpenDSP-INVALID-VER-INFO
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.0
Click to expand...
Click to collapse
What is your provider ? Is it an AT&T, Tmobile, etc phone ?
---------- Post added at 01:43 AM ---------- Previous post was at 01:33 AM ----------
I really could not tell you what to do with a device that is S-ON. When I first got my device the first thing I did was S-OFF, which makes it easier for me to fix my phone if something goes wrong, and also it's easier for me to fastboot flash different firmwares and change CID's/MID's. AFAIK, you can not do much with a phone that is S-ON other than gain root, but I could be wrong. There use to be two methods to gain S-OFF, but one method has been discontinued (firewater, or something like that is no longer used) and another method that cost $25, but I have forgotten the name of such method. With your phone currently not being operational, I have no idea if you would even be able to get your phone to a point to S-OFF. I do recall seeing that you said something about how you couldn't access Google, and not being able to do such pretty much makes the phone useless. Perhaps, if the phone turns on you could get onto a wifi connection and find that method ($25 S-off method), and you could gain S-Off from there. I just spent 10 minutes trying to find you some links, and maybe they will work for you....
links:
http://forum.xda-developers.com/att-htc-one-m8/help/flashing-ruu-s-unlocked-bootloader-t2979206
http://forum.xda-developers.com/htc-one-m8/help/how-to-update-firmware-s-m8-t2910344
I really need to know who your carrier is before I can assist you any further. Maybe Jball or redpoint will see this if they still even have M8's and direct you better than I can.

jxcorex28 said:
What is your provider ? Is it an AT&T, Tmobile, etc phone ?
Click to expand...
Click to collapse
The phone is from Taiwan I think... It was ordered when we were living in Dubai...
I talked with a customer support of the US or UK (forgot) and he told me that the phone was from Taiwan...
Is there any codes or serial number that I can give you that would help you with that Answer?

That is beyond me, and I really have no idea how I could help...IT is in your best of interest to try and find redpoint83, and see if he will help you. He's got more knowledge on what to do with S-ON devices because I believe he's got a phone that hasnt been S-OFF. I am sorry that I am not much help, but I do not want to tell you one thing that will end up screwing your phone up.

jxcorex28 said:
What is your provider ? Is it an AT&T, Tmobile, etc phone ?
---------- Post added at 01:43 AM ---------- Previous post was at 01:33 AM ----------
I really could not tell you what to do with a device that is S-ON. When I first got my device the first thing I did was S-OFF, which makes it easier for me to fix my phone if something goes wrong, and also it's easier for me to fastboot flash different firmwares and change CID's/MID's. AFAIK, you can not do much with a phone that is S-ON other than gain root, but I could be wrong. There use to be two methods to gain S-OFF, but one method has been discontinued (firewater, or something like that is no longer used) and another method that cost $25, but I have forgotten the name of such method. With your phone currently not being operational, I have no idea if you would even be able to get your phone to a point to S-OFF. I do recall seeing that you said something about how you couldn't access Google, and not being able to do such pretty much makes the phone useless. Perhaps, if the phone turns on you could get onto a wifi connection and find that method ($25 S-off method), and you could gain S-Off from there. I just spent 10 minutes trying to find you some links, and maybe they will work for you....
links:
http://forum.xda-developers.com/att-htc-one-m8/help/flashing-ruu-s-unlocked-bootloader-t2979206
http://forum.xda-developers.com/htc-one-m8/help/how-to-update-firmware-s-m8-t2910344
I really need to know who your carrier is before I can assist you any further. Maybe Jball or redpoint will see this if they still even have M8's and direct you better than I can.
Click to expand...
Click to collapse
By the way my phone works, but it's not able to communicate with Google Server (which is the only problem I know it's huge)... But other than that I can do everything I want with the phone... I'm actually using the Wifi sharing from that phone right now

jxcorex28 said:
That is beyond me, and I really have no idea how I could help...IT is in your best of interest to try and find redpoint83, and see if he will help you. He's got more knowledge on what to do with S-ON devices because I believe he's got a phone that hasnt been S-OFF. I am sorry that I am not much help, but I do not want to tell you one thing that will end up screwing your phone up.
Click to expand...
Click to collapse
In the thread that you linked me... They say I don't need to be S-OFF to do anything...
Further, s-off is not required to run an RUU (another common misconception, that I don't know where people get); unless you are trying to "break the rules" and either run an older RUU ("downgrade") or run another carrier's RUU.
Click to expand...
Click to collapse

You have a EU WWE device running a very old software version.
What you can do .. update to the latest with a RUU
RUU will wipe everything on your phone including internal storage so backup all your important files like photos, musics & etc to PC.
Download RUU 4.16.401.10 from here : http://androidruu.com/?developer=M8
Put your device on bootloader/fastboot mode then relock bootloader with command
fastboot oem lock
Right click RUU and select run as administrator and follow the RUU instructions
To run a RUU .. you need USB2.0 and latest HTC USB driver installed. If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.

ckpv5 said:
You have a EU WWE device running a very old software version.
What you can do .. update to the latest with a RUU
RUU will wipe everything on your phone including internal storage so backup all your important files like photos, musics & etc to PC.
Download RUU 4.16.401.10 from here : http://androidruu.com/?developer=M8
Put your device on bootloader/fastboot mode then relock bootloader with command
fastboot oem lock
Right click RUU and select run as administrator and follow the RUU instructions
To run a RUU .. you need USB2.0 and latest HTC USB driver installed. If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.
Click to expand...
Click to collapse
Alright... HTC Sync Manager installed, now downloading the RUU you gave me:
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
This one right?
Next step will be to relock the bootloader...
And just run the .exe as an administrator...
I'll come back in a few hours when I finish downloader the RUU

ckpv5 said:
You have a EU WWE device running a very old software version.
What you can do .. update to the latest with a RUU
RUU will wipe everything on your phone including internal storage so backup all your important files like photos, musics & etc to PC.
Download RUU 4.16.401.10 from here : http://androidruu.com/?developer=M8
Put your device on bootloader/fastboot mode then relock bootloader with command
fastboot oem lock
Right click RUU and select run as administrator and follow the RUU instructions
To run a RUU .. you need USB2.0 and latest HTC USB driver installed. If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.
Click to expand...
Click to collapse
Alright I downloaded the file...
Installed HTC Sync Manager
Uninstalled I but kept the HTC Driver Installer
I ran fastboot oem locked
After I did that the phone only boots in fastboot.
I tried to run RUU but it seem to be running in an infinite loop... Stuck at "Verifying Information on your Android Phone. Please wait..."

Well you are a superhero!!!! Thanks for helping
Took me a while to figure out everything... How to do all the commands... Install what I needed find the conflicts on my computer with ADB but finally got everything to work 100%
Thanks a WHOLE freakin' lot

Great :good:
Before you unlock it again in case you feel like modding it further, do that OTA checking first.
There should be OTA to 4 .16.401.13
Settings -- about -- software update.

ckpv5 said:
Great :good:
Before you unlock it again in case you feel like modding it further, do that OTA checking first.
There should be OTA to 4 .16.401.13
Settings -- about -- software update.
Click to expand...
Click to collapse
Done Thanks!!!
No Modding for me My friend screwed it up and he didn't know...
It some there is some version of Androids that are bugged and you can only register on the google 1 time (when he did it the first time) and when you wipe the phone you can't access the server anymore... Never found a solution and I'm not the one that modded it and my friend lives 6 hours away from my (by plane) hahahaha so there was no chance he can help me!!
Thanks a WHOOLLLLEEEEE Lot!!!

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.