Database Develop

[Q] Vivid Leaked ICS to Official ICS

I upgraded my phone using the leaked ICS build that hit a little bit before the final one was released. I would like to get my phone updated to the official ICS build. I was looking through GSLEON's thread in the dev forum and he mentions:
GSLEON3 said:
The absolute safest way to update to ICS is to relock your device & return it to as close to stock as you can get it. Relocked you can flash the leaked GB AT&T rom in football's thread.
Click to expand...
Click to collapse
I found the thread: http://forum.xda-developers.com/showthread.php?t=1338919 and am downloading RUU_Holiday_Cingular_US_1.63.502.4_Radio_1.11.1020.03_30.77.551061.02L_release_221238_signed.exe
In the "Official AT&T Vivid ICS RUU from HTC" thread GSLEON3 says
GSLEON3 said:
Make sure that if you have a custom recovery that is is updated & double check that it is. Write the version numbers down to confirm, both before & after.
There was an early recovery that could not (CANNOT) be overwritten without flashing a modified PH39IMG file first, then flashing stock or new modified recovery.
If you update with your device with that original recovery, you may be very sorry.
Click to expand...
Click to collapse
I'm pretty sure this applies to me, here's my information:
Code:
Locked
Holiday PVT Ship S-On RL
Hboot-1.85.0024
MICROP-0360
OpenADSP-v02.6.0.226.00.0202
eMMC-boot
Feb 10 2012,22:49:47
Software Information
More Screen
My problem with this is two-fold:
1. I'm not sure where to get the specially modified ph39img
2. I'm really nervous because I like my phone a lot!
Any help you can offer would be really appreciated!
Here's a screenshot of my homescreen because I accidentally took one while getting it out of the case!

newsaint said:
I upgraded my phone using the leaked ICS build that hit a little bit before the final one was released. I would like to get my phone updated to the official ICS build. I was looking through GSLEON's thread in the dev forum and he mentions:
I found the thread: http://forum.xda-developers.com/showthread.php?t=1338919 and am downloading RUU_Holiday_Cingular_US_1.63.502.4_Radio_1.11.1020.03_30.77.551061.02L_release_221238_signed.exe
In the "Official AT&T Vivid ICS RUU from HTC" thread GSLEON3 says
I'm pretty sure this applies to me, here's my information:
Code:
Locked
Holiday PVT Ship S-On RL
Hboot-1.85.0024
MICROP-0360
OpenADSP-v02.6.0.226.00.0202
eMMC-boot
Feb 10 2012,22:49:47
Software Information
More Screen
My problem with this is two-fold:
1. I'm not sure where to get the specially modified ph39img
2. I'm really nervous because I like my phone a lot!
Any help you can offer would be really appreciated!
Here's a screenshot of my homescreen because I accidentally took one while getting it out of the case!
Click to expand...
Click to collapse
Well firstly the RUU your referring to is for official gingerbread. You dont need to flash the modified file unless you have the old recovery so thats un needed. Use this official RUU link http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe to flash your phone to the official ics build.

Thanks for the heads up, sorry for misinterpreting things. I'll give this a go when I get off work!

Looks like it worked! Thanks again

TWRP OK?
I have done some research on this and have found that I can get s-off by flashing a RUU rom. The thing is is that I have to have an updated recovery. Right NOw i have the TWRP 2.4.4.0 and wondering if Im good to flash the RUU or if i need to return to stock recovery.
I dont mind losing root as I can re root it.
Originally Posted by sketchscarz View Post
I used the steps and it gives me this message. I am s-on
Old beer detected...... Ple
Starting up......
Connecting to device...
Backing up......
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.....
Try it again but you have to use original RUU ICS for your device before following these steps
you can download that from here : http://forum.xda-developers.com/show....php?t=1564776

vivid almost unlocked need to verify recovery or flash stock recovery
config.dat ran to change radio, since not s=off failed.
need to flash recovery to stock recovery/ current recovery could brick phone whjen flashing stock RUU .IMG ROM
Not positive that i have the recovery that makes brick sandwich, becasue there is a old recovery that does not allow certain system files to fetch the files needed to install RUU.
Need to verify recovery/flash stock RUU rom
if recovery is not verified / flash stock recovery
proceed to write radio
---------- Post added at 03:58 AM ---------- Previous post was at 03:25 AM ----------
sketchscarz said:
config.dat ran to change radio, since not s=off failed.
need to flash recovery to stock recovery/ current recovery could brick phone whjen flashing stock RUU .IMG ROM
Not positive that i have the recovery that makes brick sandwich, becasue there is a old recovery that does not allow certain system files to fetch the files needed to install RUU.
Need to verify recovery/flash stock RUU rom
if recovery is not verified / flash stock recovery
proceed to write radio
Click to expand...
Click to collapse
Found some more research with the borked ROm which seems to turn s-off. The rom is compiled from a stock ruu so im thinking I can still flash this Unlock_code.bin and get me unlocked with this awesome rom
http://forum.xda-developers.com/showthread.php?t=2171741
all thanks goes to homeslice976 and please dont beat me up for posting your link as I am looking for easier ways to get this phone unlocked so i can activate it on tmobile.
It seems that I have found an alternative to having the bootloader unlocked and the s-off to be able to change the radio to tmobile with Unlock_code.bin on the stock RUU img
I have since flashed the WXC recovery pretty awesome wildchild, great work!

[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?

S-on ROMs?

As title states, What is a GOOD ROM that will still work with S-on? I have Elegancia ROM on it now, But I am not too fond of it. Battery life is pretty rubbish and it's sorta buggy. Why don't I S-off? Because I'm afraid of bricking my ONLY phone.. and where I live isn't close to someone who can do it for me (Nor would anyone, anyways) But I want a GOOD ROM that will work with S-on and is de-sensed. Thanks

As far as de-sensed goes you only have three choices- wajeeh's desensed Rom, virtuous Rom, or MIUI. All of those work with S-on as I've tried all of those. If you want completely stable with great battery but not de-sensed then check out the Illuminati Rom. I switch between MIUI and Illuminati regularly and both of them are real good as far as battery life go.
I'm S-on and will probably stay that way until I find a different phone.
Sent from Illuminati land.

I screwed up my S-OFF a couple of times (because I missed a vital prep step). It was frustrating, but to my surprise it didn't brick the phone. I was able to restore the stock software etc. and try again.
Anyway - Isn't it possible that any custom rom could work with S-ON? (as long as the extra step of manually flashing the kernel/boot.img is done?)
I was on Wajee Desensed 1.5 for a while - I really liked it... but eventually I missed sense. Now I'm on the latest PureVelocity and loving it.

Anyway - Isn't it possible that any custom rom could work with S-ON? (as long as the extra step of manually flashing the kernel/boot.img is done?).
Click to expand...
Click to collapse
Yes as long as you flash the boot.img via fastboot

ronnie498 said:
Yes as long as you flash the boot.img via fastboot
Click to expand...
Click to collapse
Another question!! What exactly does S-on prevent me from doing? Can I still install a new / different kernel with fastboot even if I am S-on? A co-worker said my battery life might be crap because of the "stock-ish" kernel I am using. Or does S-on prevent me from flashing a new kernel even through Fastboot / USB?

ZackFearheart said:
Another question!! What exactly does S-on prevent me from doing? Can I still install a new / different kernel with fastboot even if I am S-on? A co-worker said my battery life might be crap because of the "stock-ish" kernel I am using. Or does S-on prevent me from flashing a new kernel even through Fastboot / USB?
Click to expand...
Click to collapse
S-on
Cannot flash boot.img via recovery
S-off
Can flash kernel & Rom via recovery

ronnie498 said:
S-on
Cannot flash boot.img via recovery
S-off
Can flash kernel & Rom via recovery
Click to expand...
Click to collapse
So basically all that means is if I wanna flash a kernel I HAVE to be s-off? Or does that just mean I have to use fastboot / usb / cmd to do it?

ZackFearheart said:
So basically all that means is if I wanna flash a kernel I HAVE to be s-off? Or does that just mean I have to use fastboot / usb / cmd to do it?
Click to expand...
Click to collapse
I may not have said that clearly, S-OFF means you do not have to flash boot.img (kernel zip) via fastboot, you can flash it through recovery
with S-ON you have to use fastboot to flash the boot.img.

ronnie498 said:
I may not have said that clearly, S-OFF means you do not have to flash boot.img (kernel zip) via fastboot, you can flash it through recovery
with S-ON you have to use fastboot to flash the boot.img.
Click to expand...
Click to collapse
So, Basically if I wanna install a new kernel with S-on, I can still do it... just through fastboot? I'm lost. I wanna flash Elegancia's custom kernel, And not the "stock-ish" kernel to my device.

ZackFearheart said:
So, Basically if I wanna install a new kernel with S-on, I can still do it... just through fastboot? I'm lost. I wanna flash Elegancia's custom kernel, And not the "stock-ish" kernel to my device.
Click to expand...
Click to collapse
that is correct you can still flash a new kernel through fastboot, how ever the customize kernel in the rom is for s-off and can not be flash with fastboot. I know it gets confusing at times but he makes a kernel that u can flash http://d-h.st/rBg it is customizable. The kernel devs will let you know in their threads if you need s-off to use them etc.

[Q] rooting and return to stock without S-Off

Hi everyone,
I recently switched from my Galaxy Nexus to the HTC One. Coming from a nexus device, the general rooting procedure seems to be a bit more complicated on the one. After browsing the web for a few hours, a couple of things are still not completely clear and I would appreciate any help as I do not intend to break a recently bought 550€ device So thanks in advance.
Rooting, flashing roms and kernels, and installing a custom recovery works after unlocking the device with htcdev.com. I do not need S-Off for those things. Is this correct?
When it comes to returning the device to stock for let's say, a warranty-related issue, is this also possible with S-On? If this is the case, how would I do that as I mostly found guides to return to stock that require S-Off? I'm currently on hboot 1.54 so S-off is not an option right now.
Also, if I lock the bootloader again (which should work with fastboot oem lock I assume?) I read somewhere that it will say Relocked instead of Locked. Out of experience, would this be a problem if I need to send the device in?
Tl;dr: Rooting, flashing roms and kernels, installing a recovery is possible after unlocking the bootloader with htcdev.com. Can I also return the device to stock if I need to send it in with S-On or does that require S-Off?
Thank you.
Any help is appreciated.

All the rooting, etc. can be done with just an unlocked bootloader. It's the downgrading that required S-OFF

EddyOS said:
All the rooting, etc. can be done with just an unlocked bootloader. It's the downgrading that required S-OFF
Click to expand...
Click to collapse
That's quite pleasant news, thank you. Can I also return it to stock for warranty-related issues with S-on? And what do you mean with downgrading and why would I do that?

As there is no RUU available for anything over 1.29.401.16, being S-OFF gives the option of using an older RUU to get the phone back to 100% stock and then you can get the OTA updates to get to the latest version again. If you're S-ON you can only restore a nandroid backup (which I would say a million times to do before flashing a new ROM), restore the stock recovery and then relock the device

b0ld said:
That's quite pleasant news, thank you. Can I also return it to stock for warranty-related issues with S-on? And what do you mean with downgrading and why would I do that?
Click to expand...
Click to collapse
Well first thing you should do when you unlock your bootloader is do a nandroid backup of your stock rom. that way you can flash it back if you ever want to return to stock; so you won't need to look endlessly for an RUU or other backup, which may or may not exist.
However, once you do unlock and install custom recovery your bootloader will say:
*** UNLOCKED ***
*** TAMPERED ***
and if you re-lock your bootloader, it will only go back to *** RELOCKED ***, it will never go back to *** LOCKED *** (unless you're S-Off with revone)
I'm not sure about the TAMPERED, as there are some conflicting reports, some say TAMPERED will go away once you flash stock recovery, and others say it will not go away.
So for warranty issues it really depends on your country and/or repair center, some will "overlook" the unlocked/relocked status if it's a hardware defect and either repair or send you a new one, but then again there are some that will blame the fault on you, saying that unlocking and flashing custom roms was the cause of the malfunction.
We don't have warranty where I live so I can't really help there. You could post your carrier and country, and see what other people have experienced.

Thank you all, this has been really helpful. What happens in case I brick my device while having S-On? Would you say that S-off is really important or doesn't it really matter at all if I don't care for OTA updates? And can I obtain S-Off if I am already rooted and on a custom Rom if it should ever be available for hboot 1.54?
I'll post my information as you suggested.
Country: Austria
Carrier: 3, but I don't think that matters as I bought the device unlocked.

b0ld said:
Thank you all, this has been really helpful. What happens in case I brick my device while having S-On? Would you say that S-off is really important or doesn't it really matter at all if I don't care for OTA updates? And can I obtain S-Off if I am already rooted and on a custom Rom if it should ever be available for hboot 1.54?
I'll post my information as you suggested.
Country: Austria
Carrier: 3, but I don't think that matters as I bought the device unlocked.
Click to expand...
Click to collapse
With S-On you can do pretty much everything (custom ROMs, even Radios). The only thing you won't be able to flash is the firmware. You would either need to find a signed firmware for your CID and MID, or if an OTA comes in your country (which includes newer firmware), you would have to flash back to stock + stock recovery, relock your bootloader, accept the OTA then unlock again and restore whatever custom ROM you were using. (not that difficult)
Anyway, from what I've seen so far, most ROMs are not being dependent on any specific firmware version. Are you already on 2.24 firmware? I think that's the currently official version.
And with S-On, it's very hard to brick your device as you can't mess with the hboot which is the main reason for bricks.

Thanks for the quick reply. In this thread it is stated that after flashing s nandroid backup without s-off it might result in problems like the touchscreen not working. (1st post) http://forum.xda-developers.com/showthread.php?t=2358738
Is this always the case?

That is if you flash a 4.1.2-based nandroid when you have the 4.2.2 FW. If you flash your own one (which is why you should ALWAYS make a backup before doing anything else) you should have no issues

What if I flash a 4.3 custom rim and decide to flash my current 4.2.2 stock nandroid?

That'll be fine as you won't be on the 4.3 FW (as you can't flash FW when S-ON)

b0ld said:
What if I flash a 4.3 custom rim and decide to flash my current 4.2.2 stock nandroid?
Click to expand...
Click to collapse
Firmware version is not tied to ROM version, even if you run a 4.3 ROM, your firmware will still be 2.24 (from 4.2.2). And since you're S-On you can't flash any unsigned firmware. So no worries.
EDIT: EddyOS was faster

That's good news.
Why would I need a newer firmware then (probably noob question)? Would it also be possible to flash the official htc stock 4.3 rom with sense once it's released? And is it possible to get s-off once the bootloader is unlocked etc.?
If i understand correctly, even with s-on I can do pretty much anything, and if I should screw up something, flashing my nandroid backup will resolve it?

b0ld said:
That's good news.
Why would I need a newer firmware then (probably noob question)? Would it also be possible to flash the official htc stock 4.3 rom with sense once it's released? And is it possible to get s-off once the bootloader is unlocked etc.?
If i understand correctly, even with s-on I can do pretty much anything, and if I should screw up something, flashing my nandroid backup will resolve it?
Click to expand...
Click to collapse
1- Newer firmware can (should ) have improvements (performance, stability, battery) over previous ones, e.g. the firmware 2.24 showed significant improvement of the touch drivers, but after 2.24 firmware I haven't seen any noticeable remarks from other threads.
2- Once the official 4.3 stock OTA rolls out, you will be able to get it after you restore your phone to stock (ie stock rom from your backup + stock recovery + relocked)
3- You won't be able to get S-Off (even with unlocked bootloader) until a new exploit is found (if ever )
4- with s-on you can flash back your original backup, or any custom rom, kernel, radio. the only thing is your phone will show ***UNLOCKED***/***RELOCKED*** and ***TAMPERED*** in the bootloader.

Thanks again, very informative! One (hopefully) last question (for now), do I have to flash the boot.img seperately when flashing a new rom on the PC with s-on or can I jhst flash the .zip, just like on the nexus?

Boot.img flashes with the ROM as a Nexus does, only the One X needed to flash the boot.img manually after a ROM

b0ld said:
Thanks again, very informative! One (hopefully) last question (for now), do I have to flash the boot.img seperately when flashing a new rom on the PC with s-on or can I jhst flash the .zip, just like on the nexus?
Click to expand...
Click to collapse
boot.img usually comes in the zip of the ROM, no need to flash separately.
EDIT: EddyOS does it again :laugh:

So, long story short: The only thing that's different from the nexus is that the bootloader will say "relocked" or "tampered". I can still receive OTAs as soon as I flash the nandroid backup I made after flashing the custom recovery. I can still switch between 4.2 and 4.3 ROMs if I'd like to. I can basically do anything with S-On besides modifying system files (which I do not intend to). I could even receive the next firmware updates (the ones after the current 2.24) if I restore my nandroid, restore the original recovery image, and relock the bootloader. There are no "real" downsides for me if I stay S-On as I can return everything to stock anyway. Is this correct?

b0ld said:
So, long story short: The only thing that's different from the nexus is that the bootloader will say "relocked" or "tampered". I can still receive OTAs as soon as I flash the nandroid backup I made after flashing the custom recovery. I can still switch between 4.2 and 4.3 ROMs if I'd like to. I can basically do anything with S-On besides modifying system files (which I do not intend to). I could even receive the next firmware updates (the ones after the current 2.24) if I restore my nandroid, restore the original recovery image, and relock the bootloader. There are no "real" downsides for me if I stay S-On as I can return everything to stock anyway. Is this correct?
Click to expand...
Click to collapse
Yep sounds right :good:
If you had S-Off then you could remove the tampered and unlocked/relocked signs, and you could mess around (upgrade & downgrade) unsigned firmwares.
With S-On you have to stick with the official OTAs.

nkk71 said:
If you had S-Off then you could remove the tampered and unlocked/relocked signs, (...)
Click to expand...
Click to collapse
If there should ever be a method of getting S-Off with hboot 1.54, it makes no difference if I root it right now and install a custom rom, as I can relock and restore everything again. Right?

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.