Database Info

[Q] S-On, S-OFF, should I care?

Hi everybody,
I am thinking about getting a Sensation, but I have a little doubt.
As far as I know, the Sensations for sale now are S-ON.
Now, I am hearing that HTC wants to start selling unlocked bootloaders soon. Does that mean S-OFF?
But my main question is: should I keep myself from buying a Sensation now, if I want the ability to root later?
Does this question even make sense?

I am also curious if S-ON or S-OFF matters, I just picked this phone up from t-mobile yesterday, should I have staved off my purchase? Basically, what does this relate to rooting and custom ROM's?

just get the phone as its great, they will unlock bootloader in few weeks and if not someone else from XDA will do that.
With or without s-off still the phone is good.
Sent from my HTC Sensation using XDA

Hiya all,
I'm waiting till salary time and then I'll most probably get it. It's the main reason I registered here, to track the status of the problems and solutions... Must have it! Time to switch from the stupid Tattoo, but at least I got it for free (say, is a Tattoo to be considered as a contest prize or as a curse?)
Anyway, I definitely prefer it to be s-off because I won't be able to afford a new one for quite some time, so I want to take the best out of it.
Sent from my [email protected]

Not sure if the Sensation ever will be default s-off, this phone is already launched and far as i remember htc said they will unlock (or make it easy) on future models.
If u want the Sensation just get it It will be unlocked either by the devs or htc soon anyway. And it's still a great device so using it stock works for a while

I'm a little unclear on if S-off has anything to do with root. I've rooted several phones and am comfortable with that if it is one step. I get what I need which is access to titanium backup and control of the bloatware. I don't delete anything, I freeze it.
I just searched and read where the S-off is for security and it allows for flashing unsigned roms....I sorta get it a little LOl. I'm learning .....
But does S off have anything to do with getting root? Can you have one without the other? Unlocking the bootloader has something to do with checksums matching right? If the checksum matches, you're in? Are unlocked bootloader and S off related?
Flashing is a bit much for this neophyte....I know my limits. If I were to have a problem I wouldn't know what to do.

S off unlocks fastboot in a way that allows flashing unsigned radio roms and wiping system and such. Read up on that.
I believe but cannot be sure that s on prevents flashing unsigned recovery, but an unreleased but leaked signed recovery can fix. (say an engineering one).
That enables Custom recovery which is the holy grail
In summary I don't believe s on and s off have much to do with the locking being done by htc. My wife's htc hd is s-on.
Sent from my GT-I9100 using Tapatalk

ickster said:
I'm a little unclear on if S-off has anything to do with root. I've rooted several phones and am comfortable with that if it is one step. I get what I need which is access to titanium backup and control of the bloatware. I don't delete anything, I freeze it.
I just searched and read where the S-off is for security and it allows for flashing unsigned roms....I sorta get it a little LOl. I'm learning .....
But does S off have anything to do with getting root? Can you have one without the other? Unlocking the bootloader has something to do with checksums matching right? If the checksum matches, you're in? Are unlocked bootloader and S off related?
Flashing is a bit much for this neophyte....I know my limits. If I were to have a problem I wouldn't know what to do.
Click to expand...
Click to collapse
You can only get temp root with S-ON as every reboot the system will lose root

So what are the advantages of temp root? Can you permanently delete bloatware? Not that I would , just curious. Could you run Tit. backup and freeze stuff? Thanks, I am learning.

I'm quite positive HTC will never start shipping all retail units s-off, so all of this wondering about dates on the box and where to buy, etc is all just a waste of time. If they choose to give us a way to unlock the bootloader, it will be similar to the Nexus One and Xoom.
Now you may wonder, but how come some people have purchased s-off phones? Well they likely were originally a test or review unit of some kind that got resold or repackaged. There is simply no reason to expect HTC would intentionally ship phones with s-off.
Either they'll give us a method to unlock or we'll find it on our own. Don't bother hunting for dates and stores to find an s-off device.

karnovaran said:
I'm quite positive HTC will never start shipping all retail units s-off, so all of this wondering about dates on the box and where to buy, etc is all just a waste of time. If they choose to give us a way to unlock the bootloader, it will be similar to the Nexus One and Xoom.
Now you may wonder, but how come some people have purchased s-off phones? Well they likely were originally a test or review unit of some kind that got resold or repackaged. There is simply no reason to expect HTC would intentionally ship phones with s-off.
Either they'll give us a method to unlock or we'll find it on our own. Don't bother hunting for dates and stores to find an s-off device.
Click to expand...
Click to collapse
Thanks, I was curious about the S off phones I'd heard of. My questions are just general. I'm curious as well as the op. I keep hearing the 3 terms....unlocked bootloader, s-off, and root but am confused how they all relate. Like the op said should I care? I don't know LOL...

ickster said:
Thanks, I was curious about the S off phones I'd heard of. My questions are just general. I'm curious as well as the op. I keep hearing the 3 terms....unlocked bootloader, s-off, and root but am confused how they all relate. Like the op said should I care? I don't know LOL...
Click to expand...
Click to collapse
Basically..
Root (all phones) will let us use root apps like wireless tether and titanium backup.
S-off (the latest HTC phones) will give us unrestricted access to flashing full ROMs.
In general, they go hand in hand. There is such a thing as temporary root access (last until you reboot), which can happen with s-on. But full root access will require s-off. When people talk about wanting an unlocked bootloader, they want s-off.
Notice I said the latest HTC phones, that's because s-off is an HTC specific situation. It doesn't apply to Motos or any others.

ickster said:
So what are the advantages of temp root? Can you permanently delete bloatware? Not that I would , just curious. Could you run Tit. backup and freeze stuff? Thanks, I am learning.
Click to expand...
Click to collapse
You cant permanently delete bloatware. You can freeze stuff and run titanium.
The thing is that for now there is no vunerability to take advantage of and make root in the official rom.
Custom Roms come pre rooted...

ickster said:
Thanks, I was curious about the S off phones I'd heard of. My questions are just general. I'm curious as well as the op. I keep hearing the 3 terms....unlocked bootloader, s-off, and root but am confused how they all relate. Like the op said should I care? I don't know LOL...
Click to expand...
Click to collapse
Actually you are right, I might start to get some more information about the 3 terms. However, as far as I understood, S-ON and S-OFF don't really relate to root.
I will buy the phone and that's it
In general, they go hand in hand.
Click to expand...
Click to collapse
aaand this shows that I didn't understand...

It's a great phone with or without the s-off imo.
Sent from my HTC Sensation 4G using XDA App

miguelroboso said:
aaand this shows that I didn't understand...
Click to expand...
Click to collapse
Yes, s-on/s-off and root are two different things. One refers to write-protection and the other to privileges.
The reason I say they go hand-in-hand is that permanent root can not happen on this phone without s-off.
If XDA cracks this thing, here's is the likely order of events:
- achieve temporary root for s-on devices
- achieve a method of toggling s-on devices to s-off
- achieve permanent root
- begin custom ROM craziness
- much rejoicing

karnovaran said:
Yes, s-on/s-off and root are two different things. One refers to write-protection and the other to privileges.
The reason I say they go hand-in-hand is that permanent root can not happen on this phone without s-off.
If XDA cracks this thing, here's is the likely order of events:
- achieve temporary root for s-on devices
- achieve a method of toggling s-on devices to s-off
- achieve permanent root
- begin custom ROM craziness
- much rejoicing
Click to expand...
Click to collapse
True
Nice post

So, my understanding is that S-On is not that deleterious for the rooting process.
I thought of it as a horrible techno-disease for a phone

miguelroboso said:
So, my understanding is that S-On is not that deleterious for the rooting process.
I thought of it as a horrible techno-disease for a phone
Click to expand...
Click to collapse
Nah. It hasn't been a permanent medical condition for past HTCs. The problem we have with the Sensation is that prior exploits have been fixed, so a new way in has to be found. (you could replace "Sensation" with "G2" and find that sentence posted here about 8 months ago)

karnovaran said:
Nah. It hasn't been a permanent medical condition for past HTCs. The problem we have with the Sensation is that prior exploits have been fixed, so a new way in has to be found. (you could replace "Sensation" with "G2" and find that sentence posted here about 8 months ago)
Click to expand...
Click to collapse
Thanks; just out of curiosity, given HTC's current policy of openness, is there the technical possibility that they would help in the process?

Sensation Fully Rooted with HTCdev

I guess I will start by saying that I have been a long time 'lurker.' I started coming around XDA back when the original Dash was new and have used all the information pumping out since then.
I tried looking around as best as I could to see if there were any other threads regarding a full root with the HTCdev bootloader but could only find discussion and debates around it.
I mostly am just confirming that it can be done. Not sure if I am a lucky one or if it was even a very risky process, but it took me all of about 15 minutes so I'm not complaining.
All I did was follow the instructions from HTCdev to unlock my sensation. After that I followed this guide from Step 2.
I currently have S-OFF, superuser access, installed a new rom, and reverted to my original rom. Everything seems to be properly working without a hitch.
Also, for clarity on this part in HTCdev FAQ:
What does this mean for me?
Unlocking the bootloader means that you now have the ability to customize software on your device. Please note that changing your bootloader can cause significant issues with your device and once you have unlocked your device, you have agreed to the disclaimer that states a change in warranty status such that in the event you render your device unusable, you are responsible for the recovery of your device, whether by repair or by other means.
Click to expand...
Click to collapse
All that means is that if you brick your device through unlocking or flashing new roms that HTC will not warranty your device. If everything works properly but you end up with other issues, i.e. touch screen no longer is responsive, then you are covered. I actually spoke to an HTC rep about it and that is what I got. Now they may try to say that unlocking may have caused it, but that isn't anything new.

Hmmm -_-
Sent from my HTC Sensation 4G using XDA App

hmmmm hmmmm cough choke cough

kleanblade said:
I guess I will start by saying that I have been a long time 'lurker.' I started coming around XDA back when the original Dash was new and have used all the information pumping out since then.
I tried looking around as best as I could to see if there were any other threads regarding a full root with the HTCdev bootloader but could only find discussion and debates around it.
I mostly am just confirming that it can be done. Not sure if I am a lucky one or if it was even a very risky process, but it took me all of about 15 minutes so I'm not complaining.
All I did was follow the instructions from HTCdev to unlock my sensation. After that I followed this guide from Step 2.
I currently have S-OFF, superuser access, installed a new rom, and reverted to my original rom. Everything seems to be properly working without a hitch.
Also, for clarity on this part in HTCdev FAQ:
All that means is that if you brick your device through unlocking or flashing new roms that HTC will not warranty your device. If everything works properly but you end up with other issues, i.e. touch screen no longer is responsive, then you are covered. I actually spoke to an HTC rep about it and that is what I got. Now they may try to say that unlocking may have caused it, but that isn't anything new.
Click to expand...
Click to collapse
Not trying to antagonize here but can you supply us with some screen shots of your "About" section and kernel and ROM part...??? No disrespect meant but if you say this is true then I would like to visualize the outcome. Thanks!

I understand anyone's skepticism. So I will provide, as best I can, whatever information I can. Have a couple screens attached. Soon as I can find a camera or get my hands on someone's phone I will take a picture of the HBOOT screen.
I'm not trying to do anything other than a "Hey, this actually worked for me." HTC's method just gave me the unlock and S-OFF. I understand it hasn't been the case for everyone. In fact I even had issues with HTC's method once I got the prompt to actually unlock the device. It wouldn't accept my input the first few tries (choosing yes or no yielded nothing).

Very legitimate. You should do a tutorial video on youtube and post it here.
kleanblade said:
I understand anyone's skepticism. So I will provide, as best I can, whatever information I can. Have a couple screens attached. Soon as I can find a camera or get my hands on someone's phone I will take a picture of the HBOOT screen.
I'm not trying to do anything other than a "Hey, this actually worked for me." HTC's method just gave me the unlock and S-OFF. I understand it hasn't been the case for everyone. In fact I even had issues with HTC's method once I got the prompt to actually unlock the device. It wouldn't accept my input the first few tries (choosing yes or no yielded nothing).
Click to expand...
Click to collapse
Sent from my HTC Sensation 4G using XDA App

hmmm
why use this and not the alpharev solution?

my question exactly...
reddoni said:
why use this and not the alpharev solution?
Click to expand...
Click to collapse
What is the difference between the two unlocking methods? Does one let you go back to S-on should you want to revert back? Are more internals accessible with one over the other (like radio's)? Just curious. When I do root I want to make sure I am using the best one with optimal features. Thanks in advance.

I personally have not seen a distinct advantage with using either method. If the phone bricks with either method you are out in the cold no matter what. Both are relatively easy to do. With HTC's method your warranty will at least be intact for any issues they deem not responsible from being rooted w/o having to 'hide' that you rooted your device. HTC's method may be easier to 'relock' your device as well. After I locked my device and rebooted, I locked it again and it was as simple as a short command. Any deeper than that I will say it's beyond my ability to know.
I feel like its as simple as an apples and oranges approach or an OEM vs after market. HTC has tested and checked their method and put their stamp of approval on it. For some 'consumers' it gives them a better sense of security. AlphaRev method works just as well but will never have the clout a large corporation, such as HTC, has.
If there is an interest for Snipes' request I could try to put a guide together. I know I don't command much credibility yet. So I don't want to do something know one would trust. However, it really isn't much different then the current guide available.
Also, HBOOT picture attached. As far as locking up your device again, with the HTC method it puts **** RELOCKED **** as the header and S-ON. I believe (not sure since I haven't done it) with the revolutionary method it simply replaces the hboot screen to the original.

How did you S-OFF? Using the same adb command as those with the Nexus One did?

I simply followed HTC's method to unlock the boot loader and it gave me S-OFF.
This gist of HTC's process is that you use go through fastboot, get your device token code, submit your token code to HTC, they email you an unlock_code.bin file, and you finish up with flashing your device with the unlock code. It is not difficult and took me about 3 minutes, maybe. The only extra thing that I am not even sure you need, is to have htcsync installed (it was listed as a requirement by htc).

Also,
The only two commands you use in the process are:
fastboot oem get_identifier_token (to get the token you need to submit)
fastboot flash unlocktoken Unlock_code.bin (flash your unlock code on the device)
If you want to relock your device you simply use:
fastboot oem lock

I just tried the HTCdev way, and I did get unlock, but did not get S-OFF

Billyvnilly said:
I just tried the HTCdev way, and I did get unlock, but did not get S-OFF
Click to expand...
Click to collapse
same here, it says unlocked but still s-on... and i get an error when trying to flash recovery (step 2) what to do?

I'll get my hands on another Sensation and see what results I get.
Odd that I would be the only one with a sensation that has s-off.

miroxlava said:
same here, it says unlocked but still s-on... and i get an error when trying to flash recovery (step 2) what to do?
Click to expand...
Click to collapse
Just start with step one then. I was able to follow all steps (except i dont need supercid) after doing htcdev. took maybe 45 minutes from start to finish, including downloads, restarts, and getting new ROM installed. Which btw, the CM7 alpha is out... trying it out soon.

Ok the HTCdev site says this. Not to mention they know you S-offed cause you did it via their website and tools.
Please understand that you will not be able to return your device to the original state
Click to expand...
Click to collapse
And in the [Guide] to Installing S-off, ClockWork, Root, SuperCID & S-on [03/AUG/11](noobproof) thread it says.
For Warranty Purposes/Returns:Follow Step 4 below for removing Clockwork and Root FOLLOW STEP 5 TO CHANGE BACK TO S-ON - CONFIRMED TO BE WORKING- USE WITH CAUTION
Click to expand...
Click to collapse
Now my question is this, if you S-off your Sensation via the HTCdev site and then S-on your Sensation via the method mentioned in the guide. Does your Unlit go back like it was originally, and not say " **** RELOCKED ****" at the top of the screen. Or is the to methods of S-offing your Sensation compatible with one another. I mean will combining the two brick the device. I would like some feed back from some devs that know more about what is actually going on when you switch from S-on to S-off, or from S-off to S-on.
Edit: Also the HTCdev site says this.
going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
Click to expand...
Click to collapse
So this is at the OP, just cause you use the HTCdev site to S-off your bootloader. It does not mean it does not void your warranty. And it does not mean HTC will fix your device if things go wrong and your device is rendered usless. You have to remember it is HTCdev, key word being dev not HTC.

Possible BL unlock

I dont have my HOX yet but I read upon this thread
http://forum.xda-developers.com/showthread.php?p=24370319#post24370319
Its made for the wildfire but it according to the dev
Dont let the name fool you, though. This will work on ANY HTC unlockable phone. The other tools besides unlocking will only work for the Wildfire S CDMA, as of know however.
Click to expand...
Click to collapse
Will this possibly unlock the HOX (AT&T) bootloader?
I present, the simonsimons34 Wildfire S tool.
Unlock without voiding your warranty
The biggest thing this tool can do is UNLOCK your hboot WITHOUT ever needing to wipe your data, go to HTCdev.com or voiding your warranty. Unlike S-off we can reverse this too. Simpily let us Unlock your phone for you, and flash roms and recoveries as you wish. Just like S-Off. This will also help you get S-Off with the utility from the general section. The only thing you NEED is a proper Unlockable bootloader, and the recovery that came with the phone. If you need this tool, you already have stock recovery. So nothing besides a HTC unlockable bootloader is required. Everything else is in the package.
Universal to HTC Devices
Dont let the name fool you, though. This will work on ANY HTC unlockable phone. The other tools besides unlocking will only work for the Wildfire S CDMA, as of know however.
Sorry, It is a beta.
Being as this is still in beta, there will most likely be bugs. Things that dont work. Please report them here with a screenshot and or the exact copy of what it said. For now this is a self extracting exe, so place in a folder of your choice, thats empty preferably, and open it up. The bat file will automatically be opened. There is a good side to betas though. Improvement! Soon after we confirm it works, I will be moving to a GUI app to make everything even easier.
Credits:
bobdamnit-for helping me with some scripting problems
jmz-for some consulting
jcase- for tacoroot
theq86 developer of Bltool
benjamingwyin- For leading me to the exe packaging app I use
and anyone i forgot, just pm me and Ill try to add you
Click to expand...
Click to collapse

I want to say that the ATT HOX has an unlock-able bootloader but its just "restricted from htcdev" because of ATT

Came across that and wondered the same thing.

lets hope this is worth a shot or can atleast point us in the right direction! I'm going to try this the minute I receive my HOX

It's been on the forums for a few weeks now though. If it worked surely someone would've tried it by now.

it was in the wildfire forums and mentioned on the portal like 2 weeks back

I tried this two weeks ago and it didn't work (don't remember the exact reason), and it did not brick/softbrick my phone.

Do you know what the error was ? Like did it spit out an error message?

Tampered bootloader?

I went through the HTC unlock process normal way I have on many phones now. But still have tampered above unlocked I have seen a few.posts in threads about this butpst were relating to people that used the auto tool. Has anyone figured out what's causing this? And or a fix. I haven't tried toess with itmuch I work so much I don't have to much time to play with it atm.
Sent from my HTC VLE_U using Tapatalk 2

I did some brief research on this topic and it seems that just unlocking the bootloader following the HTCDev instructions wont show the tampered flag. Once you flash anything, you will get it. Be it recovery, root, custom rom, etc.
I think the one-click tool actually does something more than just unlocking or does it differently so the tampered appears immediately with just unlocking but I could be wrong. I am new to the whole android modding scene
Doesn't seem like a big issue if you intend to mod anyway.

[Q] No OS installed, won't flash rom, mistakenly relocked...HELP!

I have scoured the internet for a solution, but my phone is from Hell. Every single thing I have ever done has ended in errors, ranging from trying to flash the rom zip and getting a "data length is too large" to errors while my phone did still have an OS and flashing through fastboot or double clicking in an exe would give me errors regarding the version or whatever other bs. I have been actively trying to fix this phone for well over a year! When I first started, it was still under warranty, and now it's just a paperweight that continues to waste days of my time at a time.
I am by no means a noob to electronics, but it seems I must be missing something I didn't learn, as I must be a noob in rooting/unrooting/flashing phones. I hope to God nobody suggests that I should have posted this in another thread, as I have searched all similar threads (all over the internet, different phones, any website that Google could find) and tried every single method anybody suggested. Most methods would be completely useless as I wouldn't meet the prerequisites, but I tried even those methods once I exhausted all serious methods.
I have officially gone mad and am about to say goodbye to all technology and go live in a Amish community for the rest of my life. I became so desperate and crazy that I managed to mess up my phone further than it was to begin with. PLEASE HELP! I am at your humble service, and I await any and all instruction.
A little background:
I got the phone from a family member once they cracked their screen, as I am much more of a hardware techie and I got the phone as a present to fix and use for myself. My family member is trigger happy and likes to root everything he could get his hands on. I am much happier with the stock versions of things as they give the best performance for my needs, not to mention the much less hassles and headaches with updates and reception and so on and so forth. I got the phone when it had 1.73.502.1 software on it. I wanted to upgrade to the 3.18.502.6 software version that was available, unroot the phone, and take everything back to dead stock. Since then, 5.18.502.1 has become available. (Side story about this: when double clicking the 5.18.502.6 RUU exe to go into my temp folder and extract the ROM zip, this version doesn't execute for some reason when downloaded from the "HTC OTA and RUU collection" thread (http://forum.xda-developers.com/showthread.php?t=2119610), and the previous version mentioned does execute and show up in my temp folder in Windows, but there are two roms (rom 1 and rom 2), and when extracting them, I get errors, so I had to download and extract 2.20.502.7, which executed and extracted without any problems)). I tried unlocking the bootloader through HTC's website (yes, I believe I relocked it about a year ago in a stupid move because I read that in order to execute an RUU you have to be relocked), but I guess AT&T is a big douche, so I had to superCID (cid 11111111) before doing so, but simply doing "fastboot oem writecid 11111111" wouldn't work, so I literally tried a million different tools I found until magically (literally, I don't know what happened or what I did), I got to superCID, in which case I unlocked with no problem. I then tried every method possible of updating, flashing, everything, but when things got to the actual rom zip part or executing RUU or basically the last steps, I would always be presented with errors and fails. In an angry move, I went to TWRP and erased everything I could get my hands on (I know, I messed up, kill me), and so I deleted the OS and whatever else was on the phone. Since then, I also managed to relock the bootloader (which I locked and unlocked multiple times with no problem and had the unlock code, so I figured I'm safe forever), and take my CID back to cws__001 (which I thought might be the cause of all of my errors, but found that now I can no longer unlock my bootloader).....
I now have an HTC One X from AT&T that is relocked, CID is cws__001,stock recovery, no operating system to boot into adb, and not able to flash anything on it to get into TWRP at least to try and adb sideload or some other things to take back the screw-ups I did since last night.
Info on bootloader:
TAMPERED
RELOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Nov 26 2012, 18:37:14:-1
I apologize beforehand for even touching the phone's software and trying to mess with it and maybe learn a thing or two in the process. Again, I thank you greatly beforehand for all your input, and I hope to hear back soon!
Erik

You can run the 3.18 att ruu to fix the phone to the point of it booting. If you want to learn a few things (such as custom ROMs and the like) you can visit threads on how to root, unlock the bootloader, get supercid, and then s-off.
Sent from my One XL using XDA Premium 4 mobile app

Thanks for the prompt response
I tried what you suggested just now (downloaded the 3.18.502.6 RUU exe from the thread http://forum.xda-developers.com/showthread.php?t=2119610, went into fastboot, right-clicked the exe and chose to run as administrator), and I got "ERROR [158]: Image Error"
I had tried that numerous times in the past as well, with either the same error or various other errors, through fastboot and through the phone being on and fully operable.
On a side note: for some reason it's recognizing my current image version as 3.18.502.6, but there is no operating system on there now, and when there was, it was definitely 1.73.502.1
Any other suggestions?
edit: also, please don't tell me that I should have changed my CID to CWS__001 instead of cws__001....does it make a difference if the CID is lowercase or uppercase?

Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita

timmaaa said:
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
You're correct about me having rushed the process. Well, I didn't at first, but after the first few days, I began to just try anything I could get my hands on, and believe it or not, that was a year ago, so every once in a while I'll grab the phone and try searching some new things, but it's not like there are an infinite number of ways to go about things :\ Thanks for the help so far though, really
edit after seeing your edit: hahaha! yeah, you caught yourself perfectly! Also, in response to your question: I've tried flashing the unlock token through multiple different programs, but to no avail. As you said, I royally screwed myself in thinking that I could put back my CID (but my stupid self didn't put uppercase letters), and I thought I'd still be able to use my unlock token since I had gotten the code beforehand and it worked multiple times before, but I was mistaken

To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita

timmaaa said:
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
Click to expand...
Click to collapse
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time

Ruu while in fastboot mode.no?
Edit my bad just noticed the part about lower case cid
Sent from my One XL using xda app-developers app

EsoteRIcalfreaK said:
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Click to expand...
Click to collapse
Unfortunately for you there is no differing view. You've gotten the phone to a point where it cannot be resurrected via traditional means. Jtag is indeed your only option, and yes it's a repair service. They hook your motherboard up to a riffbox and push the partitions to it, you can even request things like s-off. There's a user here on XDA called zarboz who does jtag repairs, and I believe he's the cheapest you'll find. He's based out of Ohio I think. Contact him via PM for details.
Sent from my Evita

Great, I have an awesome paperweight that I made myself, and the person that I could talk to so that I could get help doesn't accept private messages from someone who has less than ten posts, hahaha
I'm so hoping that the head of HTC's development department somehow joins the forum and tells me that I just need to fastboot some crying smiley face symbol and the phone will start dancing for me until everything goes back to it's original factory settings...why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!

The RUU is HTC's version of software reset. The problem isn't a lack of reset program from the manufacturer, the problem is the fact that you changed the CID incorrectly.
Sent from my Evita

I can't believe uppercase and lowercase make a difference though
Also, I tried executing the RUU in multiple different ways, even when the OS was operable, in the last year, multiple times, with multiple different versions, but I was always presented with an error of some sort and the RUU setup would cancel and close. The first thing I tried after every exploit that I did was to run the RUU, so I really don't know what else I could have done differently to have gotten the RUU to run without errors, or else I wouldn't have gone this far and tried unorthodox measures to try and revive the poor guy

Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Sent from my Evita

EsoteRIcalfreaK said:
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
Click to expand...
Click to collapse
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
EsoteRIcalfreaK said:
I have scoured the internet for a solution, but my phone is from Hell.
Click to expand...
Click to collapse
EsoteRIcalfreaK said:
why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
Click to expand...
Click to collapse
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
EsoteRIcalfreaK said:
I can't believe uppercase and lowercase make a difference though
Click to expand...
Click to collapse
How is that so unbelievable? As timmaaa mentioned, case is often crucial when it comes to computers. Since when is syntax not important when typing computer commands?
For the CID in particular, its obviously all hinging on a handful of crucial characters. So it needs to be typed exactly right.

redpoint73 said:
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
Click to expand...
Click to collapse
adb works in recovery or while the phone is stuck at loading screen but not in bootloader. Ofcourse, without an OS there's nothing to grant su. Though, he MAY be able to rewrite his CID using the 3.18 method anyway since I imagine the recovery must have SU or equal permissions..
I am less inclined to want to help after all his whining though :/

exad said:
I am less inclined to want to help after all his whining though :/
Click to expand...
Click to collapse
timmaaa said:
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Click to expand...
Click to collapse
redpoint73 said:
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
Click to expand...
Click to collapse
Guys, guys, please do understand that I did many many hours of research before attempting anything. It wasn't until just recently that I began to just go plain crazy and just throw whatever I could get my hands on into commands and such (and that was all done in the matter of one frustrating night actually, so for almost two years I researched and learned things from mostly this board and tried different methods I found useful). You should see the bookmarks I have created on my browser (I deleted a bunch of useless ones recently, but I have 24 as of right now just explaining One X things)!
If you read closely (I know, I have written a lot, because I have seen people get completely flamed for not writing enough information), I mentioned that I have been trying to revive this phone for over a year now (two years this month). The reason I didn't ask for help earlier, which I wanted to do from day one, is for respect to exactly you guys...
1. I was about to make an account on here and post the very first day I got the phone, but after watching the introduction/noob video on YouTube for this website that explains the rules and what to do before EVER posting ANYthing, I decided to do a little more research and do my best to listen and learn from all the tutorials and great help you guys have given to others.
2. I wanted to make sure, as the video and as many of you mention on this forum, to try every avenue and method before coming for help. I did so precisely for the reason of not wanting to look as though I'm "whining". I might have exaggerated a bit in saying that I threw everything I found at the phone, because I did not just blindly do things without the proper research.
The OS I "accidentally" deleted in hoping to get rid of whatever software was on there that really was not changing or allowing me to RUU or anything. I thought that if I deleted it, it would be easier to put a fresh genuine stock copy on it. I was mistaken, and by the time I realized, I had done the damage to the phone. The biggest mistake that caused this irreversible damage was MY OWN unfortunate way of thought of thinking that uppercase and lowercase wouldn't make a difference (actually the truth is, I thought the original CID was lowercase, but seeing as how I had spent almost two years on this project, and I had had a very long day, I didn't double check to make sure, and I figured that I would be able to go back and change it worst case scenario...this my MY mistake, and I am by no means whining or complaining for MY OWN MISTAKE).
All that being said, please gentleman, if there is anything I could do to revive this phone and reverse my wrong-doings, I would appreciate it greatly and be forever grateful. I assure you, I will not perform a single step without confirming that I am doing the right thing. I am definitely wanting your help, and I definitely do seek to leave behind something that other people who make similar mistakes to mine can look back on for future reference.
Long story short, I messed up, it's my fault, I'm not complaining or whining, my Crapple and Samsuck comments were just to poke fun at those companies, and I would really appreciate it if anyone could help me in any shape way or form. Thank you beforehand
Erik

Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086

exad said:
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
Click to expand...
Click to collapse
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand

To be honest I think this was dubious at best, it was worth a try but I didn't hold much hope for it actually working. The only place it might have worked would have been in TWRP, even then your system was wiped so the structure required for the commands doesn't even exist in the partition. Someone else chime in here if I'm wrong, but I still believe jtag is the only option out of this.
Sent from my Evita

EsoteRIcalfreaK said:
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
Click to expand...
Click to collapse
You have stock recovery!? -_- I think timaaa is right then -_- I will flash stock recovery and test ADB just to be sure, just for you homeboy. I will post an update shortly.
---------- Post added at 03:21 PM ---------- Previous post was at 03:05 PM ----------
Yeah, sorry man, Jtag only.