Related
Hello,
I have been researching here to find a way to downgrade to a previous version of a firmware so that I can S-Off, and to no avail unsure how to do it myself using either use Moonshine or revone.
The reason I wish to do this is that I want to install Google Play edition and of course the necessary info to install it.
Sent from my HTC One using xda premium
EvilSpants said:
Hello,
I have been researching here to find a way to downgrade to a previous version of a firmware so that I can S-Off, and to no avail unsure how to do it myself using either use Moonshine or revone.
The reason I wish to do this is that I want to install Google Play edition and of course the necessary info to install it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
If I'm not mistaken the ROM firmware is irrelevant as to if you can root or not, or get-S-OFF. The most important factor for S-OFF is the bootloader version. I haven't seen any threads about getting S-OFF on bootloader 1.54.
Reboot to your bootloader (turn device off, hold volume down and turn device on). Check your HBOOT version there. If it says 1.54, then the only possible solution is to search for an official HTC RUU with a lower HBOOT version. However I do not know if this will actually work.
RadiatorRXD said:
If I'm not mistaken the ROM firmware is irrelevant as to if you can root or not, or get-S-OFF. The most important factor for S-OFF is the bootloader version. I haven't seen any threads about getting S-OFF on bootloader 1.54.
Reboot to your bootloader (turn device off, hold volume down and turn device on). Check your HBOOT version there. If it says 1.54, then the only possible solution is to search for an official HTC RUU with a lower HBOOT version. However I do not know if this will actually work.
Click to expand...
Click to collapse
Alright. Assuming that works, is there a way to reflash?
[Edit] Just checked my bootloader it says that I have 1.44. However I have tried both Revone and S-off with no success
Sent from my HTC One using xda premium
EvilSpants said:
Alright. Assuming that works, is there a way to reflash?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Don't really know what you mean by reflash? Returning to the newer HBOOT (1.54)?
If that's the case, once you're S-OFF you can update the HBOOT to 1.54 and S-OFF will still be there. There are some threads in the development section about upgrading the HBOOT. I used these myself without issues.
As for the official RUU, this will probably be a Google search. I haven't seen a thread around with these files.
Keep in mind that flashing an original RUU will result in loss of root and custom recovery. You will need to re-root after flashing the RUU and reflash a custom recovery.
RadiatorRXD said:
Don't really know what you mean by reflash? Returning to the newer HBOOT (1.54)?
If that's the case, once you're S-OFF you can update the HBOOT to 1.54 and S-OFF will still be there. There are some threads in the development section about upgrading the HBOOT. I used these myself without issues.
As for the official RUU, this will probably be a Google search. I haven't seen a thread around with these files.
Keep in mind that flashing an original RUU will result in loss of root and custom recovery. You will need to re-root after flashing the RUU and reflash a custom recovery.
Click to expand...
Click to collapse
A little bit off topic here but ..if I am s- off already and I were to use a stock ruu on my phone all that I will I loose is the recovery and root?... So after I run ruu my device will still be s-off ?
Sent from my HTC One using xda premium
NORCALkID said:
A little bit off topic here but ..if I am s- off already and I were to use a stock ruu on my phone all that I will I loose is the recovery and root?... So after I run ruu my device will still be s-off ?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I think so yes, but I'm not 100% sure. You may find the answer, or ask the question in the hboot update threads or s-off threads. I haven't flashed a RUU myself in years.
Sent from my Viper One
RadiatorRXD said:
Don't really know what you mean by reflash? Returning to the newer HBOOT (1.54)?
If that's the case, once you're S-OFF you can update the HBOOT to 1.54 and S-OFF will still be there. There are some threads in the development section about upgrading the HBOOT. I used these myself without issues.
As for the official RUU, this will probably be a Google search. I haven't seen a thread around with these files.
Keep in mind that flashing an original RUU will result in loss of root and custom recovery. You will need to re-root after flashing the RUU and reflash a custom recovery.
Click to expand...
Click to collapse
What I mean to say is that once I have found one with an older HBoot, how do I go about flashing that so that I can do one of the two S-Off procedures?
Sent from my HTC One using xda premium
EvilSpants said:
What I mean to say is that once I have found one with an older HBoot, how do I go about flashing that so that I can do one of the two S-Off procedures?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Ah ok. The RUU should be a windows executable. Just hook up the phone to computer, start the RUU and follow the on-screen instructions.
Sent from my Viper One
RadiatorRXD said:
Ah ok. The RUU should be a windows executable. Just hook up the phone to computer, start the RUU and follow the on-screen instructions.
Sent from my Viper One
Click to expand...
Click to collapse
I assume the RUUs can be pulled from HTCdev?
Sent from my HTC One using xda premium
EvilSpants said:
I assume the RUUs can be pulled from HTCdev?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Here's an article about flashing a RUU: Flash RUU
It has a link to a website which contains several RUU files to download: HERE
RadiatorRXD said:
If I'm not mistaken the ROM firmware is irrelevant as to if you can root or not, or get-S-OFF. The most important factor for S-OFF is the bootloader version. I haven't seen any threads about getting S-OFF on bootloader 1.54.
Reboot to your bootloader (turn device off, hold volume down and turn device on). Check your HBOOT version there. If it says 1.54, then the only possible solution is to search for an official HTC RUU with a lower HBOOT version. However I do not know if this will actually work.
Click to expand...
Click to collapse
I was s-off with stock unrooted locked 2.24.401.1 firmware (ruu'ed by repair center)and tried to use revone to unlock again but it would fail, then I downgraded to hboot 1.44 (I could still do this because I was s-off already) but revone would still fail, then I decided to properly downgrade to 1.28(or was that 29).401.?? with an ruu and was able to use revone again to unlock my bootloader, so hboot is not the only factor for revone to be succesful...
downgrading hboot and other system partitions, except kernel rom radio and recovery, is not possible if you are not s-off already....
RadiatorRXD said:
Ah ok. The RUU should be a windows executable. Just hook up the phone to computer, start the RUU and follow the on-screen instructions.
Sent from my Viper One
Click to expand...
Click to collapse
My downgrade attempt failed with one of the executables. I am not sure what to try next.
EvilSpants said:
My downgrade attempt failed with one of the executables. I am not sure what to try next.
Click to expand...
Click to collapse
I'm at a loss here, sorry.
Sent from my Viper One
RadiatorRXD said:
I'm at a loss here, sorry.
Sent from my Viper One
Click to expand...
Click to collapse
I should note that I did not retry, however I figure that if it fails the first time, then it wouldn't succeed a second?
Sent from my HTC One using xda premium
EvilSpants said:
I should note that I did not retry, however I figure that if it fails the first time, then it wouldn't succeed a second?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
You could always try a second time. Maybe also post a screenshot of the failure.
Sent from my Viper One
RadiatorRXD said:
You could always try a second time. Maybe also post a screenshot of the failure.
Sent from my Viper One
Click to expand...
Click to collapse
At this point I am looking at installing a custom recovery, though from what I am reading I may not be able to do that without S-OFF, so I am stuck if this is true.
Sent from my HTC One using xda premium
EvilSpants said:
At this point I am looking at installing a custom recovery, though from what I am reading I may not be able to do that without S-OFF, so I am stuck if this is true.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
S-OFF is not needed for root or custom recovery. You do need an unlocked bootloader though. On other devices S-OFF was needed to flash radio's or kernels through recovery, but from what I have read the One can flash kernels in recovery without S-OFF
Sent from my Viper One
RadiatorRXD said:
S-OFF is not needed for root or custom recovery. You do need an unlocked bootloader though. On other devices S-OFF was needed to flash radio's or kernels through recovery, but from what I have read the One can flash kernels in recovery without S-OFF
Sent from my Viper One
Click to expand...
Click to collapse
So I have gotten TWRP on there, however I have been unable to flash a previous firmware, to downgrade, getting the error message, Unable to open zip. My guess is that S-On is stopping this process even in a custom recovery. Is there a recommendation as to how I can achieve S-Off?
Also There is something I have been thinking about it, and if I were to follow the steps here, with execption of the flashing the RUU through fasboot, could I flash the RUU through TWRP instead?
[Edit] Could I install a custom ROM, S-Off through the ROM, then follow the steps in the link to flash the RUU?
I have been trying to get AWS band to work with no luck. I tried using the ruu exe and even extracted the rom.zip from the exe to flash it manually. Even relocked the bootloader, changed my CID to T-MOB010 and flashed the stock T-Mobile rom and stock tmobile recovery then flashed the exe with no luck.
I am currently rooted, relocked bootloader and S-OFF. My CID is still T-MOB010 and I am running ViperOne 2.1. My hboot version is 1.54 Google Edition bootloader with TWRP recovery.
I did a few hours worth of searching with only one possible solution which was to flash the ruu.
Can someone please assist me with this issue?
Sent from my HTC One using XDA Premium 4 mobile app
bdjam2 said:
I have been trying to get AWS band to work with no luck. I tried using the ruu exe and even extracted the rom.zip from the exe to flash it manually. Even relocked the bootloader, changed my CID to T-MOB010 and flashed the stock T-Mobile rom and stock tmobile recovery then flashed the exe with no luck.
I am currently rooted, relocked bootloader and S-OFF. My CID is still T-MOB010 and I am running ViperOne 2.1. My hboot version is 1.54 Google Edition bootloader with TWRP recovery.
I did a few hours worth of searching with only one possible solution which was to flash the ruu.
Can someone please assist me with this issue?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If it is the AT&T/Developer variant, it won't support the 1700/AWS band. The only thing I could think of trying would be changing the CID and flashing the TMO radio. There is a pretty solid thread here about it
http://forum.xda-developers.com/showthread.php?t=2315880&page=23
Doesn't look like anyone has had much success.
jngox3 said:
If it is the AT&T/Developer variant, it won't support the 1700/AWS band. The only thing I could think of trying would be changing the CID and flashing the TMO radio. There is a pretty solid thread here about it
http://forum.xda-developers.com/showthread.php?t=2315880&page=23
Doesn't look like anyone has had much success.
Click to expand...
Click to collapse
Thanks. I am not sure how I missed this thread but I will be following it.
Sent from my HTC One using XDA Premium 4 mobile app
I recently got a HTC One and ive managed to unlock and root.
I've read quite a lot about S-Off, and im still undecided whether or not I actually need it!
Is it really necessary? benefits from using it at the moment?
Changing CID & MID/ superCID would be my only task after s-off.. You can then flash RUUs of other CID/MID, and also flash older RUUs.. You can also flash a custom hboot
Sent from my HTC One using Tapatalk 4
If you can, do it!
You can return stock and you can downgrade your hboot and much more!
Do it, do it, do it if you have the 1.44 hboot
If you could s-off, do it. If you can't who cares? S-off is overrated in my book.
Sent from my HTC One using xda app-developers app
Absolutely you should do it if you can. I just found out yesterday that my phone may go in for warranty or I might have to downgrade firmware. Thanks to s-off I can revert to stock. Do it!
There's no harm in doing it and it's a fairly simple task.
Follow the links in the tutorial:
http://www.youtube.com/watch?v=J4BWxtjaamM
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
From what I've read, having HBOOT 1.54 basically means that you can't S-off your device (as this is only available for 1.44). This means that you won't have access to deeper customisation for your phone (flashing different firmware and changing CID). CID determines what region your phone belongs to so this translates to how early you can get official OTA's as some regions get updates earlier than others. Also, if you want to fully transform your phone into a Google Edition HTC One, this is only open to units with a specific CID.
As for firmware, not really clear on what the differences between firmwares are but you can still flash different radios which are a component of firmwares (thus getting some of the benefits of newer firmware anyway).
That being said, you can flash the whole range of custom ROMs and kernels available on these forums provided that you've unlocked your boot loader. Directions for this can be found on the HTC website.
If you want an optimised stock ROM, try ARHD Sense which is basically your stock ROM with many performance improvements (especially when it comes to signal). For more customisation on Sense, you can try ViperOne.
Honestly there are so many excellent ROMs here that you can easily lose days trying every single one. The Google Edition ROMs are excellent too.
Hope this helps!
Sent from my HTC One using XDA Premium 4 mobile app
Thank you both for detailed replies! This helped me ease my mind on the HBOOT-thing. Thanks!
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Michiel0211 said:
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
Click to expand...
Click to collapse
All you have to do is unlock your bootloader via htcdev.com (note, this will wipe your data) and then flash a custom recovery. You can use this tool http://d-h.st/mas to simplify the process.
CoryTallman said:
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
sixty_oz said:
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
No matter what, you should stay s-off, it does not affect OTA's or RUU's in any way whatsoever. To flash any RUU, you need to be with a cid of 11111111
It's not possible for you to flash an ruu for something else and then flash the rogers ota I don't think
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
cristhefur said:
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
Click to expand...
Click to collapse
You can use the RUU with S-ON as long as it is not an older version than what is already on your phone - I believe you are probably talking about 1.54.654.9 right? Check the about settings on your phone to see if you have upgraded from that (1.54.654.13 or 1.54.654.15 or the 2.16 something).
If the phone version is newer, you will not be able to use the RUU without S-OFF. Since you actually have the HK version, you will not need to change your CID. Successfully running the RUU will flash all the major partions, radios, and more and will bring you completely back to stock. It will also wipe your data/media partition (internal SC card) so make sure you backup anything you need to keep.
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
cristhefur said:
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
The RUU will actually remove the TAMPERED banner because that flag is in mmcblk0p6, named "pg2fs", which is one of the images that the RUU overwrites. UNLOCKED, if you have it, will remain because that flag is mmcblk0p2, named "pg1fs" which does not get overwritten by the RUU. It can be removed by hex editing that block with an echo command http://forum.xda-developers.com/showthread.php?t=2708571
If you are already unlocked, rooted, and have version 1.54.654.9, I would highly suggest you run sunshine and get S-OFF before you run the RUU and update the OTAs; who knows if that exploit will be blocked in further updates.
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
cristhefur said:
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Not sure since I did it on .9, but I would definitely try it - in fact, if you are on 15, the only way you will be able to run the .9 RUU is if you S-OFF.
Sunshine will not ask you to pay until it has run compatibility tests and verified that it can get S-OFF on your phone - so run it and if you see the message to pay, you are good to go. Having S-OFF just makes things SO much easier.
Just follow the directions on the sunshine site http://theroot.ninja/ and run it entirely from the phone; couldn't be easier. You will need to sideload the APK, easiest if you just run the command "adb install SunShine-latest.apk" after making sure Unknown Sources is checked in your phone settings.
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
cristhefur said:
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
It's the other way around - look a few posts up - there's a "not older than your phone's version" in front of that statement.
To be clear, the .9 RUU will not work on a .15 phone if you are S-ON, you must be S-OFF to do that. However, if you had a .15 RUU (which doesn't exist) it would work on a .9 phone.
Sorry about the confusion. That is just one of the benefits of being S-OFF (not to get sidetracked but my favorite benefit is being able to flash from hboot or fastboot rebootRUU with the bootloader locked)
Ah yes, I see that now- my mistake. I guess I'll s-off tomorrow afternoon then. Thank you very much for your help!
Sent from my 831C using XDA Free mobile app
It's encouraging that the Sunshine devs recently made fixes to deal with Sprint 4.4.3 M8 devices - that's version 2.16.654.4 which is higher than yours, so I think you have a good chance of success. Good luck!
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
I'm fairly certain that if you're S-on you can only run a RUU with the same software & firmware version that's installed on the phone. It was that way on the EVO LTE and I'm fairly certain that's how it is now.
Sent from my HTC M8
you may want to try http://firewater-soff.com/ first, if nogo, then sunshine
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
nope, you can't flash a older RUU if you're s-on
Oh ok...my apologies.
Is there a reason that my phone boots directly into the bootloader every time that I relock it?
I am unable to boot into anything after using fastboot oem lock, and it only loads the bootloader until I run the RUU (granted, this was before the latest update).
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
PillowMetal said:
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
Click to expand...
Click to collapse
Is it possible to flash the recovery from SD card or do I need to use my computer?
neudof said:
Is it possible to flash the recovery from SD card or do I need to use my computer?
Click to expand...
Click to collapse
When you download say TWRP from their webiste, you get an image file (IMG) that is meant to be flashed using fastboot from your computer. But you can rename it to "recovery.img", place that in a zip file along with an android.txt file with specific contents onto your external SD Card, and then you can flash it from the bootloader (if you are S-OFF). The file has to be specifically named as well - e.g., the Sprint HTC One M8 is "0P6BIMG.zip".
If you don't have an external SD Card, you may also be able to flash from the bootloader using a powered USB-OTG cable (like we did on the M7). Again, this is only if you are S-OFF, otherwise you will have to fastboot flash the image from your computer because bootloader flashes with S-ON have to be signed.
One last method that doesn't require S-OFF, is to copy the image file anywhere on internal or external SD cards, then use the "dd" command to copy the image over your recovery block (specific numeric device block depending on phone) using either your computer or a terminal emulator on the phone.
So yeah, you have options.
Update: I achieved S-Off as suggested, locked my boot loader using an adb command from another thread then ran the HK .9 RUU. I went through the 3 updates then took the phone to sprint, had no problems at all. Thanks for your help guys. :thumbup: