Database Develop

[Q] About S-Off

It seems like the only way to S-Off Vivid required some wire trick. I never done something like that b4...
What do I miss if I leave it S-ON? I already unlock bootloader, custom recovery and rooted.
Thanks anyone for answering.

Apart from being able to flash radios (to the best of my knowledge there aren't any custom/better ones for the vivid, yet), there are kernals being built that require s-off. And with s-off you can flash roms/images that are unsigned to the phone, regardless of what carrier or region you're in; other words, you can flash whatever Rom you like so its imperative that everything about the Rom you're installing is read and understood to avoid confusion and ultimately, a bricked device... That's pretty much it in a nutshell. I hope that cleared it up for you
Sent from my HTC Velocity 4G using xda premium

g33mt4z said:
Apart from being able to flash radios (to the best of my knowledge there aren't any custom/better ones for the vivid, yet), there are kernals being built that require s-off. And with s-off you can flash roms/images that are unsigned to the phone, regardless of what carrier or region you're in; other words, you can flash whatever Rom you like so its imperative that everything about the Rom you're installing is read and understood to avoid confusion and ultimately, a bricked device... That's pretty much it in a nutshell. I hope that cleared it up for you
Sent from my HTC Velocity 4G using xda premium
Click to expand...
Click to collapse
First part about radios is wrong. You need an ENG HBOOT to do it, which we still don't have. Sure, S-Off lets us flash custom HBOOTs, but we're still not there yet.
Second part about kernels requiring it is also wrong. You can always flash kernels as a fastboot flash boot boot.img, then CWM the modules in. It's always been the case, and is not changing with AOSP or any of that stuff. AOSP doesn't require S-Off, neither does Sense 4, neither does any preexisting nor future kernel.
Third part about unsigned ROMs is partially wrong. You can flash other regions' RUU updates with the superCID. Still doesn't let you do custom ROMs themselves; for that, the unlocked bootloader process is still valid, and you will need some form of recovery (CWM, WCX, TWRP, etc).

Aus_Azn said:
First part about radios is wrong. You need an ENG HBOOT to do it, which we still don't have. Sure, S-Off lets us flash custom HBOOTs, but we're still not there yet.
Second part about kernels requiring it is also wrong. You can always flash kernels as a fastboot flash boot boot.img, then CWM the modules in. It's always been the case, and is not changing with AOSP or any of that stuff. AOSP doesn't require S-Off, neither does Sense 4, neither does any preexisting nor future kernel.
Third part about unsigned ROMs is partially wrong. You can flash other regions' RUU updates with the superCID. Still doesn't let you do custom ROMs themselves; for that, the unlocked bootloader process is still valid, and you will need some form of recovery (CWM, WCX, TWRP, etc).
Click to expand...
Click to collapse
Actually my kernel does require s-off now if you want to keep it up to date. If you are fine using a less feature rich and possibly unstable s-on version of it then that's fine
Sent from my HTC PH39100 using xda premium

Thank you everyone for replying.
So this is what I get:
with S-OFF,
1) I can flash hboot (boot.img)
2) Within recovery (CWM or alike), I can flash Custom ROM zip that has build-in kernel
Is that correct?
BTW, is there SuperCID for Vivid yet?
Thanks again,

RayYung said:
Thank you everyone for replying.
So this is what I get:
with S-OFF,
1) I can flash hboot (boot.img)
2) Within recovery (CWM or alike), I can flash Custom ROM zip that has build-in kernel
Is that correct?
BTW, is there SuperCID for Vivid yet?
Thanks again,
Click to expand...
Click to collapse
1. HBOOT is not a boot.img, it's an .nb0 file (the bootloader itself). boot.img is a kernel.
2. Yes.
3. Yes, it's 11111111 like most other HTC devices.

Thanks Aus_Azn,
I guess I mixed up hboot and kernel....
I know 11111111 is THE SuperCID for all device but is there a SuperCID hack for Vivid yet?

[Q] what triggers "TAMPERED", "SECURITY WARNING", and red text on boot

[Q] what triggers "TAMPERED", "SECURITY WARNING", and red text on boot
Hi Guys and Gals,
So I'm really trying to understand what triggers "TAMPERED", "SECURITY WARNING" (though I haven't seen it), and the red text on bootup, and how to undo them.
It was my general understanding that these are caused by a custom recovery, and in theory should disappear when you relfash stock rom and stock recovery, and possibly relock booltoader.
For some this seems to work, for others not.
I'm not looking for the methods using S-Off, such as revone -t or modified hboots. Just the general requirements (short of running RUU), that would allow these flags to go back to normal.
Thanks

The tampered flag seems to pop up when you're using a non-stock recovery, or have changed something in the ROM. Same with the red warning text on the splash screen. As soon as you flash a custom recovery (but leave the ROM 100% stock) you get the 'this is a test build, etc.' warning come up
If you're S-OFF, there are guides in General on how to remove these warnings (and not using revone too), e.g. to remove the tampered label, read this http://forum.xda-developers.com/showthread.php?t=2477792

EddyOS said:
The tampered flag seems to pop up when you're using a non-stock recovery, or have changed something in the ROM. Same with the red warning text on the splash screen. As soon as you flash a custom recovery (but leave the ROM 100% stock) you get the 'this is a test build, etc.' warning come up
Click to expand...
Click to collapse
Agreed, but shouldn't going back to a 100% stock ROM and 100% stock RECOVERY, remove the "this is a test build" and TAMPERED. or do these stay in either case because you did "at one point in time" use a custom recovery?
I've read people returning to stock, where these have gone away, and for other people they stayed.
I know you can achieve this with S-Off, but I'm just trying to understand the basic "logic" of these warnings, and when (and when not) they will appear.

I'm bumping this for more info. Still no conclusive results.
Sent from my HTC One using xda app-developers app

Unsigned kernel or recovery causes tampered warning, flashing RUU will clear tampered.
Sent from a van down by the river.

When I unlocked my phone, there was no TAMPERED message until I flashed a custom recovery

akuma24 said:
When I unlocked my phone, there was no TAMPERED message until I flashed a custom recovery
Click to expand...
Click to collapse
mine (TAMPERED message) never goes away even with a stock recovery and no root
not until i got s-off and run the adb command

[Q] Flashing AOSP and GPE roms S-Off?

I have an S-on device, and I'm not entirely sure what that entails. (I know that it means I only have permission to flash recovery and not radio or boot or anything. I'm just not clear on the consequences of that.I come from an S-off HTC Inspire, which didn't have google editions or anything like that, so all I ever worried about when I flashed a rom was backing it up. But I'm looking at the Skydragon mixed version, and it has an entirely different method of installing for S-ON phones (flashing new boot.img, etc.) None of those steps is particularly scary to me, but I'm wondering WHY they're needed.
What's with the new boot img? Does it have something to do with getting GPE roms or is it just what the guys at Skydragon have set up?
What happens if I just flash it like "normal" roms (pretending that I'm s-off and flashing from recovery)?
Right now I'm on an AOSP rom. Assuming I go through the extended procedure for installing skydragon S-on, will I be able to move back from Skydragon to AOSP again, if I want to?
Thanks for bearing with me.

Do you have a link to these instructions? I'm curious as well.

The Skydragon ROM that I'm referring to is here:
http://forum.xda-developers.com/showthread.php?t=2423492
On second look, it seems that there aren't any fancy instructions for THIS particular build of Skydragon. It says "unlocked OR S-off). I must have been pretty distracted when I was reading this. Plus all the separate builds are sort of confusing. So that's nice!
But here's a build with the extended process I was asking about, if anybody wants to answer my questions anyway.
http://forum.xda-developers.com/showthread.php?t=2319187&highlight=skydragon

middaymoon said:
I have an S-on device, and I'm not entirely sure what that entails. (I know that it means I only have permission to flash recovery and not radio or boot or anything. I'm just not clear on the consequences of that.I come from an S-off HTC Inspire, which didn't have google editions or anything like that, so all I ever worried about when I flashed a rom was backing it up. But I'm looking at the Skydragon mixed version, and it has an entirely different method of installing for S-ON phones (flashing new boot.img, etc.) None of those steps is particularly scary to me, but I'm wondering WHY they're needed.
What's with the new boot img? Does it have something to do with getting GPE roms or is it just what the guys at Skydragon have set up?
What happens if I just flash it like "normal" roms (pretending that I'm s-off and flashing from recovery)?
Right now I'm on an AOSP rom. Assuming I go through the extended procedure for installing skydragon S-on, will I be able to move back from Skydragon to AOSP again, if I want to?
Thanks for bearing with me.
Click to expand...
Click to collapse
S-ON = Security ON; S-OFF = Security OFF
some devices of HTC with S-ON does not support flashing boot partition (boot.img file) via recovery and you have to flash them in unlocked bootloader , fastboot mode, like HTC One X (S-ON) and vice versa
S-OFF gives you full access to modify all partitions (boot, radio, etc), unlike S-ON
now on our HTC One S-ON, there is no restriction to modify boot partition, in other words, you can flash every ROM without worrying about the boot.img file seperatly (because it's already in the ROM zip file and will be flashed along with the ROM)
as for the SkyDragon ROM mention, the text is from his One Xs' ROM so don't worry
i know this sounds confusing, sorry for my bad English
review this thread for better understanding S-OFF

kamilmirza said:
S-ON = Security ON; S-OFF = Security OFF
some devices of HTC with S-ON does not support flashing boot partition (boot.img file) via recovery and you have to flash them in unlocked bootloader , fastboot mode, like HTC One X (S-ON) and vice versa
S-OFF gives you full access to modify all partitions (boot, radio, etc), unlike S-ON
now on our HTC One S-ON, there is no restriction to modify boot partition, in other words, you can flash every ROM without worrying about the boot.img file seperatly (because it's already in the ROM zip file and will be flashed along with the ROM)
as for the SkyDragon ROM mention, the text is from his One Xs' ROM so don't worry
i know this sounds confusing, sorry for my bad English
Click to expand...
Click to collapse
So you're saying he just copied the text from one of his other builds? That's great. Thanks!

middaymoon said:
So you're saying he just copied the text from one of his other builds? That's great. Thanks!
Click to expand...
Click to collapse
yep
happy tension-free flashing

[Q] Confirm Stock HBOOT?

I converted my phone to a Developer Edition phone a while back, and in the process went S-OFF. I would like to S-ON, as I have read this removes the 'test device' status that apparently sends HTC information. I also read that going S-ON with a custom HBOOT is a very bad thing, but how do I tell if my HBOOT is custom? The top just reads M7_UL PVT SHIP S-OFF RH and the version is HBOOT 1.56.

hjjfffaa said:
I converted my phone to a Developer Edition phone a while back, and in the process went S-OFF. I would like to S-ON, as I have read this removes the 'test device' status that apparently sends HTC information. I also read that going S-ON with a custom HBOOT is a very bad thing, but how do I tell if my HBOOT is custom? The top just reads M7_UL PVT SHIP S-OFF RH and the version is HBOOT 1.56.
Click to expand...
Click to collapse
From Rumrunner documentation
How to get rid of S-OFF warnings
There are two visual differences that will indicate that your device is S-OFF (other than checking in the bootloader):
1. Go to Settings > About. You should see "Tell HTC and error reporting" option right under "Software updates".
If you don't see that option, then you're already using a custom ROM and you can skip this step. But if you see the "Tell HTC and error reporting" option, select it and scroll down to read a warning message in red text. The "Tell HTC" option is permanently enabled and cannot be turned off without flashing a custom ROM. If you are not comfortable with HTC collecting information from your device, you can load your custom recovery, wipe data, cache, dalvik and install a custom ROM - the "Tell HTC and error reporting" option will be gone.
2. Boot up or restart your phone. In the boot splash screen, if you see a warning message in red text: "This build is for development purposes only..." you can remove it by flashing a custom hboot, now supplied by the developers of Rumrunner: http://rumrunner.us/hboots/. If your phone's firmware and carrier are not listed, the custom Hboots provided on the Rumrunner site will not work and you will likely brick your device. But you can look for other sources. Try this one: http://forum.xda-developers.com/show....php?t=2316726. Alternatively, you can request for a custom Rumrunner Hboot for your specific firmware and carrier. Instructions: Do fastboot getvar all and don't forget to remove your serialno and imei. Paste the info into an email. Upload your RUU or firmware.zip from OTA to dropbox and add link in email and don't forget to mention your carrier, if any. Send to: [email protected]. Then, check the Rumrunner Hboots page regularly for the update: http://rumrunner.us/hboots/.

mb_guy said:
From Rumrunner documentation
How to get rid of S-OFF warnings
There are two visual differences that will indicate that your device is S-OFF (other than checking in the bootloader):
1. Go to Settings > About. You should see "Tell HTC and error reporting" option right under "Software updates".
If you don't see that option, then you're already using a custom ROM and you can skip this step. But if you see the "Tell HTC and error reporting" option, select it and scroll down to read a warning message in red text. The "Tell HTC" option is permanently enabled and cannot be turned off without flashing a custom ROM. If you are not comfortable with HTC collecting information from your device, you can load your custom recovery, wipe data, cache, dalvik and install a custom ROM - the "Tell HTC and error reporting" option will be gone.
2. Boot up or restart your phone. In the boot splash screen, if you see a warning message in red text: "This build is for development purposes only..." you can remove it by flashing a custom hboot, now supplied by the developers of Rumrunner: http://rumrunner.us/hboots/. If your phone's firmware and carrier are not listed, the custom Hboots provided on the Rumrunner site will not work and you will likely brick your device. But you can look for other sources. Try this one: http://forum.xda-developers.com/show....php?t=2316726. Alternatively, you can request for a custom Rumrunner Hboot for your specific firmware and carrier. Instructions: Do fastboot getvar all and don't forget to remove your serialno and imei. Paste the info into an email. Upload your RUU or firmware.zip from OTA to dropbox and add link in email and don't forget to mention your carrier, if any. Send to: [email protected]. Then, check the Rumrunner Hboots page regularly for the update: http://rumrunner.us/hboots/.
Click to expand...
Click to collapse
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.

hjjfffaa said:
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
Click to expand...
Click to collapse
Bump. Just need to know if I have the hboot for the Developer Edition so I can run the RUU and S-ON, or where I could find it. Been searching.

hjjfffaa said:
Bump. Just need to know if I have the hboot for the Developer Edition so I can run the RUU and S-ON, or where I could find it. Been searching.
Click to expand...
Click to collapse
After running the RUU you know for sure you have stock hboot because the RUU installs it
I still can't recommend s-on for any reason

hjjfffaa said:
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
Click to expand...
Click to collapse
You understand correctly.
If you *really* object to the Tell HTC reporting *and* you do not wish to run a custom ROM, S-ON may be your only choice, and I have to say I personally would never S-ON not even for warranty repair.
As you correctly concluded, going S-ON with a custom HBOOT is fatal. If there is no question (ie you had total control over the phone during its entire lifetime and prefect memory of what you did to it), just go S-ON . Odds are, unless you *know* you flashed a custom HBOOT (which is invariably for the sole purpose of getting rid of annoying red warning text), you have a stock HBOOT. Life is short. It's only a phone. Just flash.
If you're *not* sure what HBOOT you may have flashed, the best way to prevent disaster is to just take total control of the situation and manually flash a stock HBOOT yourself just before attempting S-ON. There are plenty of threads that have the zip files you need. One caveat, a failed HBOOT flash is also fatal, so start with a fully charged battery and if you see "FAILED" during flashing, be sure NOT to reboot the phone before you fix it and confirm success.
Or, as suggested above, just RUU. Drastic, but failsafe.
Note *any* stock HBOOT, regardless of version, will allow the phone to boot after S-ON, although good style dictates you use one of the same vintage as all the other firmware and software you are running.
Sent from my HTC One using xda app-developers app

NxNW said:
Or, as suggested above, just RUU. Drastic, but failsafe.
Click to expand...
Click to collapse
Thank for taking all the time to write this up. Am I to gather from this sentence here that an RUU will reinstall the stock HBOOT? I'm not bothered about wiping the phone since I am not keeping it and already have all of my data backed up. I have had total control of the phone, the only problem was that I was getting android-info parse errors trying to run the Developer Edition RUU with the stock, but S-OFF, HBOOT. Someone provided an HBOOT for me that apparently had the correct android-info setup and it worked perfectly.

Well, yes, RUU touches every partition and puts each one back exactly the way HTC approves of, including the partition containing HBOOT. (And the write method it uses is safer than flashing things manually.)
But you have already observed it can be a pain to get RUU's to succeed sometimes. In your case, S-OFF helps greatly so you should eventually be able to run a RUU just fine. If, in the process, you change your CID to "SuperCID" (11111111) be sure to change it back to your phone's real CID before going S-ON. S-ON is the absolute last step in any procedure you are contemplating.
Sent from my HTC One using xda app-developers app

Is it worth to s-off?

Hello guys
Is it worth to s-off or I can install custom recovery and rom with no problem.
What are the benefits of s-off

S-off is good, as long as you can do it without issues. I broke my USB port while trying to s-off. I can't plug my phone into pc, it goes to car mode, and refuses to charge at all. Many people have faced this issue, and this is a software + hardware issue. Just warning you, tho im running ARHD with my own mods on it for about 2 years all without s-off.
Cheers ^_^

I've got hboot 1,61 so i need to know if it is worth buying sunshine or if a free option is avalible

AleXand3rr said:
I've got hboot 1,61 so i need to know if it is worth buying sunshine or if a free option is avalible
Click to expand...
Click to collapse
As far as I know sunshine is the only way to get s-off on that hboot so you'll need to pay $25. On the matter if it's worth buying that's up to you. Personally s-off allows you to flash ROMs easily since you don't have to worry about firmware and I know some ROMs require s-off. Always research what could go wrong just to make sure you can s-off in the safest way.

AleXand3rr said:
Hello guys
Is it worth to s-off or I can install custom recovery and rom with no problem.
Click to expand...
Click to collapse
You don't need S-OFF to flash a custom recovery nor a custom rom. Is it worth it? Well if you don't need it, no.
What are the benefits of s-off
Click to expand...
Click to collapse
If you don't know what are the benefits of having S-OFF then you probably don't need it. Unlocking the bootloader remove the signature check and disable security from the /system, /boot, /recovery and /radio partitions so you can flash custom software like roms, kernel, recovery and radios. S-OFF remove the signature check and security on the remaining partitions like /hboot, /pg1fs, /pg2fs and /mfg which make it possible to flash flash unsigned firmware like a custom hboot for example. This also make possible to downgrade or change your firmware version. With access to the mfg partition you can change your MID number and with the pgfs partitions you can remove the ***tampered***, ***re-locked*** and ***security warning*** flags. S-OFF also enables some blocked "fastboot oem" commands like "fastboot oem writecid" which make it possible to change your CID number. Well a lots of useful things but nothing required to flash a custom recovery and rom.
alicarbovader said:
I broke my USB port while trying to s-off
Click to expand...
Click to collapse
Achieving S-OFF itself can't broke your USB port, its most likely an hardware problem only or you did something wrong once s-off.
AleXand3rr said:
I've got hboot 1,61 so i need to know if it is worth buying sunshine or if a free option is avalible
Click to expand...
Click to collapse
There isn't any free alternative to sunshine on hboot 1.61.
Mikecosta64 said:
Personally s-off allows you to flash ROMs easily since you don't have to worry about firmware
Click to expand...
Click to collapse
Since he is already running hboot 1.61 he already have one of the latest 7.xx.xxx.x firmware version which is all he need to run all the recent roms. So even if he keep is phone S-ON, firmware isn't something to worry about.
and I know some ROMs require s-off
Click to expand...
Click to collapse
Custom roms requires an unlocked bootloader only, not S-OFF. :good:

alray said:
Custom roms requires an unlocked bootloader only, not S-OFF. :good:
Click to expand...
Click to collapse
Well most of them but Skydragon ROM for htc one m7 says it needs s-off and there are some kernels which require s-off as well. I've only seen one, don't remember the name of it.

Mikecosta64 said:
Well most of them
Click to expand...
Click to collapse
All of them can be flashed with S-ON . There isn't anything justifying the need to have S-OFF when flashing a custom rom or kernel.
but Skydragon ROM for htc one m7 says it needs s-off
Click to expand...
Click to collapse
Yeah I know its in the OP but you don't need s-off to flash and use it. There are a lot of members reporting successfully flashing this rom on a S-ON phone, even in the Skydragon thread.
and there are some kernels which require s-off as well. I've only seen one, don't remember the name of it.
Click to expand...
Click to collapse
I never seen any kernel requiring S-OFF and that wouldn't make any sense since the kernel is written on /boot partition which is not a secured partition once the bootloader is unlocked.

alray said:
All of them can be flashed with S-ON . There isn't anything justifying the need to have S-OFF when flashing a custom rom or kernel.
Yeah I know its in the OP but you don't need s-off to flash and use it. There are a lot of members reporting successfully flashing this rom on a S-ON phone, even in the Skydragon thread.
I never seen any kernel requiring S-OFF and that wouldn't make any sense since the kernel is written on /boot partition which is not a secured partition once the bootloader is unlocked.
Click to expand...
Click to collapse
Are you fairly knowledgeable about *old* HTC devices as well? (obviously you are very knowledgeable about current ones). Old meaning, gingerbread and older. I personally am not, but I'm wondering if the functions of S-on vs S-off have changed over the years. Because, if you run a basic google search for S-on vs S-off, the *vast majority* of the information you will find is false information-- or at least it is false now, but I do not know if it was always untrue. Countless websites that say "In order to root, you must be S-off." "In order to flash ROMs, you must have S-off." Stuff like that. I know the internet is full of false information, but it seems to me the amount of false information regarding S-off is disproportionate.. I find it odd.
That said...it's not completely necessary, but it *is* nice being able to remove the Tampered flag, and to have the red text be gone, and to be able to lock and unlock my bootloader and have it say 'locked" instead of "relocked." Is it even still the case that S-off allows you to flash the /system partition? I am S-off, and I have never been able to successfully flash /system. It always returns a permission denied error of some kind. Maybe it works with KitKat and below, and from Lollipop on you need an Eng bootloader to flash /system through fastboot?
I'm kinda curious how the one poster broke his usb port trying to S-off.... did it involve that one old S-off method that involved stripped wires...I think it was called the wire method.. I like the term "hot wiring"

firejuggler86 said:
Are you fairly knowledgeable about *old* HTC devices as well? (obviously you are very knowledgeable about current ones). Old meaning, gingerbread and older. I personally am not
Click to expand...
Click to collapse
Me neither, my first HTC device was in 2012, the One X (Tegra variant)
but I'm wondering if the functions of S-on vs S-off have changed over the years.
Click to expand...
Click to collapse
Probably, there a lot of old guides (back in the nexus one days) saying that you need S-OFF in order to ROOT which is false when speaking about the One M7 but not so false when speaking about the Verizon One M7 (this one requires s-off since bootloader unlock is not available from htcdev.com)
Because, if you run a basic google search for S-on vs S-off, the *vast majority* of the information you will find is false information-- or at least it is false now, but I do not know if it was always untrue. Countless websites that say "In order to root, you must be S-off." "In order to flash ROMs, you must have S-off." Stuff like that. I know the internet is full of false information, but it seems to me the amount of false information regarding S-off is disproportionate.. I find it odd.
Click to expand...
Click to collapse
I think its a combination of false informations and outdated informations. For example, some ppl are still saying that you must flash the kernel (boot.img) using fastboot after flashing a custom rom on a S-ON phone. This was true for older HTC devices, but not needed on the M7 (and i guess newer devices) since the boot partition isn't secured and can now be flashed from custom recovery. There are some ppl confusing ROOT and Unlocked bootloader (they think unlocking the bootloader = rooting the phone which are 2 totally different things). A lor of outdated/false(or applying to a specific device only) information online. Better to look for the most recent information available for the correct device. :good:
That said...it's not completely necessary, but it *is* nice being able to remove the Tampered flag, and to have the red text be gone, and to be able to lock and unlock my bootloader and have it say 'locked" instead of "relocked."
Click to expand...
Click to collapse
Yep, exactly what I was saying above, its very useful to have s-off. But is it needed to flash a custom recovery and rom (question asked at post #1)? Absolutely not.
Is it even still the case that S-off allows you to flash the /system partition?
Click to expand...
Click to collapse
You don't need s-off to flash the system partition, only an unlocked bootloader but it can only be done from custom recovery, not from fastboot.
If you absolutely want to flash /system from fastboot then I suppose you can make a custom ruu.zip with the system image only and flash it in RUU mode. In this case you will need S-OFF since its required to flash an unsigned ruu.zip.
I'm kinda curious how the one poster broke his usb port trying to S-off.... did it involve that one old S-off method that involved stripped wires...I think it was called the wire method.. I like the term "hot wiring"
Click to expand...
Click to collapse
Me too but imo its a coincidence only. The methods used to achieve S-OFF doesn't requires any hardware modification. You only have to use the appropriate exploit (software) for your bootloader version and the only one requiring your phone to be connected with a usb cable is rumrunner. The other exploits like Revone or Sunshine for example are running directly from your phone, without any computer. I'm 99.99% sure achieving s-off itself can't cause hardware damage since its done using software as opposed to the hot wiring method you described. Anyway what I'm saying in this thread might not apply for other HTC devices but I'm pretty sure everything I'm saying is 100% correct for the M7.

Yes. Plain and simple.