Develop Bugs

Bootloader Unlock Question

Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.

JJGLive said:
Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.
Click to expand...
Click to collapse
You don't have to replace hboot unless you want to get rid of certain firmware messages, like the tampered flag. Unless you are sending your phone in for warranty work, you won't likely care about it, since you only see it in fastboot/hboot mode. The only thing the token does, besides unlock the boot loader, is remove certain preloaded apps, like the flashlight, which will screw up further OTA updates.
However, I would suggest you look into going S-off, as it makes locking/unlocking the boot loader possible without contacting HTC at all, and without messing up OTA updates. You also gain the freedom to change your CID (if you ever want to convert to stock Developer Edition), SIM unlock, and revert to older firmware if necessary (such as restoring an older RUU to go back to stock) However, S-off is "security off", so there is an increased chance of bricking the phone if you aren't careful.

Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.
Edit: I have also found this link: http://forum.xda-developers.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.

JJGLive said:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.
Click to expand...
Click to collapse
I would suggest you use this guide.
Im going to use it this friday to root my phone.

Ok so if I understand correctly now...using that guide I will not need to use htcdev and it will not be neccesary for me to flash boot.img after every rom flash?

JJGLive said:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
Click to expand...
Click to collapse
Not quite. To flash a custom ROM, all you need to do is unlock the bootloader, install custom recovery, and flash a ROM. In addition, I highly recommend you make a nandroid backup before flashing anything
S-off is only needed if you want to avoid the bootloader unlocking method via HTCDev.com (and HTC therefore having a record of you unlocking by IMEI); or to flash hboot, radio, firmware, or a few other things (such as SIM unlock). S-off is not needed to flash a ROM.
One caveat, if your phone presently has older firmware, you will experience some severe bugs on any Sense 2.x based ROM (long boot times, broken WiFi or Bluetooth) and having S-off is required to manually update the firmware. So, while in literal terms, S-off is not needed to flash a ROM. But if the above applies to you, you need s-off to manually update the firmware and get the ROM to work correctly. Alternately, you can OTA to the latest firmware before modding the phone. You will need to list your phone's hboot and present software version for us to tell you what firmware you are on.
Also, its not necessary to root before flashing a custom ROM. You will be rooted after you flash a custom ROM.
JJGLive said:
Edit: I have also found this link: http://forum.xda-developers.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.
Click to expand...
Click to collapse
Definitely not correct. That guide is for the M7. Be careful what device forum section you are in, and stay in the M8 section.

Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.

JJGLive said:
Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.
Click to expand...
Click to collapse
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.

redpoint73 said:
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.
Click to expand...
Click to collapse
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?

JJGLive said:
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?
Click to expand...
Click to collapse
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).

redpoint73 said:
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).
Click to expand...
Click to collapse
Thank you very much...I feel much more welcome in the htc one m8 thread than I did when I first started on the samsung s4 thread. You have made me feel very welcome!

Thankfully we have freegee for LG OG. Bootloader is really dangerous please keep in mind before you go for any tutorials

Rooted, ROM'd, and wondering!

I've just finished rooting and installed a custom ROM on my device, but now I'm looking into S-Off. My question is, how?
I did this ROM: http://forum.xda-developers.com/showthread.php?t=2706391
and now I don't have Wi-Fi, which apparently means that my firmware needs to be updated.
How, exactly, does one do that when you're no longer on the service provider it was on?
I'm on T-Mobile now, it was on AT&T. The phone is an AT&T HTC One M8.
I've got the files for Firewater, but I'm not 100% sure how to go about it, other than following tutorials I've found. Anyway, if someone could assist me in this search, it would be greatly appreciated.

Chances are firewater is not going to work, you'll need to use Sunshine S-off (pay 25$), S-off jas nothing to do with carrier
Sunshine: http://theroot.ninja
Firewater instructions: http://firewater-soff.com/instructions/

If I try Firewater, is there a chance to royally mess up my work? I.E. brick me, or will it error out beforehand?

firewater does NOT work. and will never work again. You can own the files but they won't work as it has has to establish a connection to the s-off server which is offline. sunshine is the one and only way. you can read that in the s-off thread here on xda and on their website !
and also questions belong in the Q&A section so please use that board the next time instead of the general subforum.
good luck with sunshine

Fubukiyo said:
I've just finished rooting and installed a custom ROM on my device, but now I'm looking into S-Off. My question is, how?
I did this ROM: http://forum.xda-developers.com/showthread.php?t=2706391
and now I don't have Wi-Fi, which apparently means that my firmware needs to be updated.
How, exactly, does one do that when you're no longer on the service provider it was on?
I'm on T-Mobile now, it was on AT&T. The phone is an AT&T HTC One M8.
I've got the files for Firewater, but I'm not 100% sure how to go about it, other than following tutorials I've found. Anyway, if someone could assist me in this search, it would be greatly appreciated.
Click to expand...
Click to collapse
Theirs a AT&T RUU here >>link removed by request
that will let you flash some roms here, not all
You'll have to relock your bootloader to flash it - fastboot oem lock -
and when your finished updateing unlock the bootloader and flash TWRP and root

Mr Hofs said:
firewater does NOT work. and will never work again. You can own the files but they won't work as it has has to establish a connection to the s-off server which is offline. sunshine is the one and only way. you can read that in the s-off thread here on xda and on their website !
and also questions belong in the Q&A section so please use that board the next time instead of the general subforum.
good luck with sunshine
Click to expand...
Click to collapse
Ah, see, this is the info that I couldn't find at all. I had no idea it was server-related, so it wouldn't work. I thought all the files were local, that's why I was investigating. Well, as long as Sunshine will work and not mess anything up, I guess that's what I'm going to have to do. Even though there's another ROM on my phone, I should still be able to use Sunshine and get the firmware updated without any issues, yeah? I would just like to get confirmation from someone who knows my exact situation and not search the forums to a situation "Similar" to mine and eff up my phone.

Fubukiyo said:
Ah, see, this is the info that I couldn't find at all. I had no idea it was server-related, so it wouldn't work. I thought all the files were local, that's why I was investigating. Well, as long as Sunshine will work and not mess anything up, I guess that's what I'm going to have to do. Even though there's another ROM on my phone, I should still be able to use Sunshine and get the firmware updated without any issues, yeah? I would just like to get confirmation from someone who knows my exact situation and not search the forums to a situation "Similar" to mine and eff up my phone.
Click to expand...
Click to collapse
S-OFF means do as you like, change firmwares, convert to GPE and back to sense. S-OFF is freedom

Okay, here's where I'm at, if anyone would inform me in the direction I should take...
I've unlocked the bootloader, flashed a ROM, and rooted. Wi-Fi doesn't work because I need the newer firmware on the device.
In order to get the newer firmware, I need to have S-Off. I don't. Sunshine doesn't work because the ROM I have flashed is a 5.0.1 version.
http://forum.xda-developers.com/showthread.php?t=2706391 If it helps.
Can I go digging to find a KitKat-based ROM and see if Sunshine will work then, or do I need to go through the BS to flash stock everything on my phone and THEN run Sunshine? I'd really like some advice before I royally mess something up.
Thanks in advance!
Edit: I found this and it looks like something that might work. Flash InsertCoin, download and pay for Sunshine, S-Off, flash firmware, go back to SkyDragon?
http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/

You simple need the stockest rom you find.. Best is restore your backup ..make it root and than do s off.. Or flash the rooted stock of mike s thread not arhd ..

Alex-V said:
You simple need the stockest rom you find.. Best is restore your backup ..make it root and than do s off.. Or flash the rooted stock of mike s thread not arhd ..
Click to expand...
Click to collapse
Forgive me for asking, but I've searched... Where is this rooted stock one you're talking about?
All right, I've flashed back to as stock as I can find, but it's still not allowing Sunshine to be installed.
However, I've stumbled upon something saying that if the Recovery is fastboot booted, it acts as though the device is S-Off? If I run the recovery in such a manner, could I possibly flash a new Firmware on there like that?

Fubukiyo said:
Forgive me for asking, but I've searched... Where is this rooted stock one you're talking about?
All right, I've flashed back to as stock as I can find, but it's still not allowing Sunshine to be installed.
However, I've stumbled upon something saying that if the Recovery is fastboot booted, it acts as though the device is S-Off? If I run the recovery in such a manner, could I possibly flash a new Firmware on there like that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2694994
I did it with that one..

Okay, here's an update:
I flashed that ROM you showed me, Alex, and then used Sunshine to S-Off my M8. That worked. I paid for it, all is well.
Flashed the Viper ROM, but didn't have Wi-Fi. So, I went back to SkyDragon, same thing.
I flashed firmware 4.28.401.9 (I think. I did typed that from memory..) but I still have no Wi-Fi.
I'm going to try to flash the GPE firmware now. I'll edit once I get it up and running!
Thanks so much guys! I really appreciate your help!

Fubukiyo said:
Okay, here's an update:
I flashed that ROM you showed me, Alex, and then used Sunshine to S-Off my M8. That worked. I paid for it, all is well.
Flashed the Viper ROM, but didn't have Wi-Fi. So, I went back to SkyDragon, same thing.
I flashed firmware 4.28.401.9 (I think. I did typed that from memory..) but I still have no Wi-Fi.
I'm going to try to flash the GPE firmware now. I'll edit once I get it up and running!
Thanks so much guys! I really appreciate your help!
Click to expand...
Click to collapse
If your wifi isn't working with ViperOne, then the firmware didn't flash correctly. Go to your bootloader/hboot and check the readout there. What it says under OS is your firmware version. If it is blank it is because of your recovery. TWRP 2.8.0.3 is recommended. You can also tell by the hboot number. 3.19 = 4.4.4 firmware

xunholyx said:
If your wifi isn't working with ViperOne, then the firmware didn't flash correctly. Go to your bootloader/hboot and check the readout there. What it says under OS is your firmware version. If it is blank it is because of your recovery. TWRP 2.8.0.3 is the recommended recovery to use with ViperOne. You can also tell by the hboot number. 3.19 = 4.4.4 firmware
Click to expand...
Click to collapse
That's awesome to know. I literally just flashed the GPE firmware, and I think I partitioned properly. (no errors while installing) It's currently doing the first boot.
Flashing that GPE firmware was nerve-racking. It went sooo slow. Here's hoping it goes through! UPDATES TO COME! I'm excited.
UPDATE:
HOLY HNNNNNNNNNNNNNG IT WORKED.
Good LORD I CAN FINALLY DOWNLOAD MY UPDATES.
Please excuse the caps, I'm effing excited right now. THANKS SO MUCH EVERYONE.

Nice that you have it working.. Don't forget.. If you want to go back to sense you need the sense firmware.. As the partitions are a bit different.. Btw I'm very happy ? with gpe 5

Alex-V said:
Nice that you have it working.. Don't forget.. If you want to go back to sense you need the sense firmware.. As the partitions are a bit different.. Btw I'm very happy ? with gpe 5
Click to expand...
Click to collapse
Right at this point, I don't care to go back to Sense firmware. I'm spoiled by the bright look of SkyDragon, so this is where I'm staying!

[Q] Steps to convert to Dev Edition from AT&T?

I'm currently bone-stock AT&T, 4.4.2. I'm frustrated by the lack of OTAs from AT&T, especially given that the 4.4.4 was reportedly pulled. So I'm considering converting to Dev Edition to get timely updates and I'd like to make sure I have all of my ducks in a row before I begin.
Am I correct with these steps and order?
1. Unlock bootloader (htcdev key)
2. s-off
3. Change MID and CID as appropriate
4. Run the 5.0.1 RUU that HTC posted
5. ???
6. Profit
Thanks!

Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.

jshamlet said:
Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.
Click to expand...
Click to collapse
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?

OGhoul said:
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?
Click to expand...
Click to collapse
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.

jshamlet said:
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.
Click to expand...
Click to collapse
I've already got the tabs open for the adb steps for that on my home PC. Thanks a bunch; you've confirmed that I actually have learned something from lurking around here all this time.

I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.

vjaamm said:
I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.
Click to expand...
Click to collapse
Yes, except you *DO* have to change your MID.
http://forum.xda-developers.com/showthread.php?t=2708581

And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?

OGhoul said:
And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?
Click to expand...
Click to collapse
No you won't. The Developer edition has the latest firmware needed by the latest ROMs 4.x
So you'll be good to go.

I actually had to do some monkey business to get this to work.
I changed my CID to Super CID, then adb fastboot bootloader. Then ran the RUU .exe. This started to work, however it failed at I think step 5 telling me my CID was wrong, and the .exe told me to hold power for 10 seconds to reboot.
This then booted back into 4.4.2, and settings > about still said 4.4.2.
fastboot getvar all however, revealed all of the lollipop firmware settings.
So I rebooted to fastboot again, then changed my CID to the BS_US002.
Ran the RUU again. It took, and it's currently optimizing apps.

[Q] Back to full stock with s-on

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?

Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.

There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.

jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.

ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.

Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?

ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.

Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????

So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!

ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.

jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?

ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.

jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!