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?

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] Rooting, bootloader & warranty

I have bought my HTC Explorer just 2 weeks ago. I'd really love to have root access to it. But I do not want to spoil my HTC 2 year warranty...
So I have 2 questions.
First, I hear that unlocking the bootloader voids your warranty. But I hear mixed opinions about whether or not it is possible to gain root access without unlocking the bootloader. Is it impossible, or just not YET possible? I hear people talking about an exploit in HTC One that allows it or something... ( wwwmodacocom/topic/353986-testing-rooting-your-one-x-without-unlocking-the-bootloader-windows-mac-linux/ )
Second, let's say it is impossible to root without unlocking. Is it possible for me to backup my current phone data so that after unlocking the bootloader, I can restore the phone to it's previous state? With "it's previous state" I mean that it looks like my phone was never unlocked or rooted, so I can send it for warranty repairs if needed. Is RUU what I need, or more?
Any help would be appreciated. I don't want to wait 2 years to root my phone!!! :crying:

believe me i rooted my phone in a week after i bought it after surfing info on net before buying it and who cares for warranty i can now do whatever i want like new roms etc....

Wouldn't do
I care, because I always have little money on me. I want to be able to repair my phone fast when needed.
Besides, I'm not into flashing ROMs. Sense 3.5 looks good to me. I'm more into replacing system apps with my own apps, replacing HTC ringtones with my own, expanding internal memory, ect.
And really, if you can save both your warranty, and get your phone rooted, isn't that the best?

ya its our wish bt not possiible btw care your phone so much that you may not need to go to service centre
root it don't worry nothing wrong will happen enjoy the world of android without limitations or boundry

nik007rock said:
ya its our wish bt not possiible btw care your phone so much that you may not need to go to service centre
root it don't worry nothing wrong will happen enjoy the world of android without limitations or boundry
Click to expand...
Click to collapse
Thank for your input, but it's not quite the answer I'm looking for. It's a matter of opinion whether rooting is worth voiding your warranty. I'd like to have a more fact based answer.
Is it really not possible to root without unlocking boot loader?
And how about my second question? Can I undo rooting like it never happened?

The thing is, you cannot root your phone, without unlocking the bootloader, then you wont have warranty, however in this thread > http://forum.xda-developers.com/showthread.php?t=1816836 the OP says, that he knows the way, of locking the bootloader again. Locking the bootloader is important thing to do, if you have to use your warranty, rooting is not the issue, the tricky part is, for now I havn't seen anyware that you lock your bootloader and it says LOCKED, there is just a standart way that says RE-Locked, this won't do the trick. My idea is, PM the OP in the thread, if he can help you, root it, if he can't and you are afraid to brick your device, don't root it and stay with stock rom. I hope that's the answer what you looked for.

shortyoko said:
The thing is, you cannot root your phone, without unlocking the bootloader, then you wont have warranty, however in this thread > http://forum.xda-developers.com/showthread.php?t=1816836 the OP says, that he knows the way, of locking the bootloader again. Locking the bootloader is important thing to do, if you have to use your warranty, rooting is not the issue, the tricky part is, for now I havn't seen anyware that you lock your bootloader and it says LOCKED, there is just a standart way that says RE-Locked, this won't do the trick. My idea is, PM the OP in the thread, if he can help you, root it, if he can't and you are afraid to brick your device, don't root it and stay with stock rom. I hope that's the answer what you looked for.
Click to expand...
Click to collapse
Yeah, thanks. That's helped a lot. Just one more question though.
Can I make a 'screenshot' of my current system? A backup of all the data on the phone, including app settings, system settings and even the original ROM perhaps. Do you need to be rooted for that? If yes, then what can you backup without being a superuser?
That was more than one question isn't it...

Without a root, no or atleast I don't know how. Without superuser you can backup files on sd card, like pics and stuff.

hi
im not sure on the explorer but on the one X the fast boot comand
fastboot oem re lock will re lock the boot loader and then we can get the original stock recovery re add it via fast boot command and then flash the orignal RUU via the pc and most of the service guys at least in India are not all that much a techie and wont really chek so mostly ur phone will get warranty service
this is just the info i got by reading in the forum :laugh:

haree said:
hi
im not sure on the explorer but on the one X the fast boot comand
fastboot oem re lock will re lock the boot loader and then we can get the original stock recovery re add it via fast boot command and then flash the orignal RUU via the pc and most of the service guys at least in India are not all that much a techie and wont really chek so mostly ur phone will get warranty service
this is just the info i got by reading in the forum :laugh:
Click to expand...
Click to collapse
Thanks, but I live in Malaysia. I never went for warranty repair before, but just in case, I need to lock the bootloader in a way that is will say "LOCKED" instead of "RELOCKED", because IF they were to check, the latter voids the warranty. I think your method will make it say RELOCKED, no?
I've browsed the web, and this site, and although I've found a few (very few) that talk about making the bootloader say LOCKED, they all say it's risky, and meant for other phones than the explorer... Except for the link shortyoko gave me. That one is work in progress. :fingers-crossed:
P.S.
Your reply would be a lot easier to read if you use full stops instead of using 4 "and"s. Just saying...

Bump
The site mentioned above is so far a dead end as the OP has gone missing.
Is there no one else that knows how to lock the bootloader of the explorer without saying "relocked"?
Another thing. What other methods besides using HTCdev can you use to safely (read:minimum risk) unlock the bootloader of the explorer?

Djalaal said:
The site mentioned above is so far a dead end as the OP has gone missing.
Is there no one else that knows how to lock the bootloader of the explorer without saying "relocked"?
Click to expand...
Click to collapse
Not sure, but maybe with something like memory addresses or something else.
Djalaal said:
The site mentioned above is so far a dead end as the OP has gone missing.
Another thing. What other methods besides using HTCdev can you use to safely (read:minimum risk) unlock the bootloader of the explorer?
Click to expand...
Click to collapse
I think it should be possible to unlock bootloader without HTCDev, you just send them the "code" and they send you unlock_code.bin. There should be something like keygen. If it isn't created now, maybe in future it will be.
Just using the programmer's logic .

Making the bootloader say Locked instead of ReLocked isnt as easy as it sounds..
And I just had the HTC service center replace my phone.. I hard bricked it playing around with revolutionary(a tool to get S-OFF in HTC)..
And they just replaced it.. Just like that.. No hassle of Unlocked or Locked or Relocked.. Thats the situation in India..
And rooting is matter of perpective.. Some people see fit to do it, others dont.. Rooting is safe.. If you follow the instructions to the letter..
If you decide to go for rooting, HTCdev.com is the best way to go.. If there was anything wrong with the method at HTCdev website, then they wouldnt put it there.. So its thoroughly tested by a lot of users, and the company..
As far as making the bootloader say Locked instead of Relocked, i believe XDA will come up with a way sometime in the future..
A screenshot of your current system is possible, but not a screenshot that can trick HTC into keeping your warranty.. And as the Moderator, Mr. Haree said, the command "fastboot oem relock" will relock your bootloader, but you wont get your warranty back in any case.. Atleast right now..
And one last thing.. As awesome as Sense is, it gets really old and boring after some time.. And I assure you, you are missing out on soo much by not rooting.. ICS, JB, AOSP, AOKP, modded versions of these ROMs, customized Sense ROMs, lot of options to customise your phone any way you want, you can make your phone your own.. People will see your phone, and say "This is <insert your name>'s phone, without a doubt!!'
Again, its a matter of perspective..
You never know, in the two years that you have your warranty(on paper if you root), there is a very high possibility that some way, to reclaim your warranty, will come up for our Explorer..
Hope this helped oot..
Peace.. V

bhargz16 said:
And I just had the HTC service center replace my phone.. I hard bricked it playing around with revolutionary(a tool to get S-OFF in HTC)..
And they just replaced it.. Just like that.. No hassle of Unlocked or Locked or Relocked.. Thats the situation in India..
Click to expand...
Click to collapse
Dude, I think you are our hope to get s-off to our device, because you can anytime give your device back to warranty service. And looks like they doesn't care about bootloader state .
Sent from my HTC Explorer A310e using xda app-developers app

zgintasz said:
Dude, I think you are our hope to get s-off to our device, because you can anytime give your device back to warranty service. And looks like they doesn't care about bootloader state .
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
In a perfect world, I'd say hell yeah!!
But I dont know squat about anything..
I'm still learning.. Lot of reading left to do yet..

bhargz16 said:
Making the bootloader say Locked instead of ReLocked isnt as easy as it sounds..
And I just had the HTC service center replace my phone.. I hard bricked it playing around with revolutionary(a tool to get S-OFF in HTC)..
And they just replaced it.. Just like that.. No hassle of Unlocked or Locked or Relocked.. Thats the situation in India..
And rooting is matter of perpective.. Some people see fit to do it, others dont.. Rooting is safe.. If you follow the instructions to the letter..
If you decide to go for rooting, HTCdev.com is the best way to go.. If there was anything wrong with the method at HTCdev website, then they wouldnt put it there.. So its thoroughly tested by a lot of users, and the company..
As far as making the bootloader say Locked instead of Relocked, i believe XDA will come up with a way sometime in the future..
A screenshot of your current system is possible, but not a screenshot that can trick HTC into keeping your warranty.. And as the Moderator, Mr. Haree said, the command "fastboot oem relock" will relock your bootloader, but you wont get your warranty back in any case.. Atleast right now..
And one last thing.. As awesome as Sense is, it gets really old and boring after some time.. And I assure you, you are missing out on soo much by not rooting.. ICS, JB, AOSP, AOKP, modded versions of these ROMs, customized Sense ROMs, lot of options to customise your phone any way you want, you can make your phone your own.. People will see your phone, and say "This is <insert your name>'s phone, without a doubt!!'
Again, its a matter of perspective..
You never know, in the two years that you have your warranty(on paper if you root), there is a very high possibility that some way, to reclaim your warranty, will come up for our Explorer..
Hope this helped oot..
Peace.. V
Click to expand...
Click to collapse
Yeah, that helped.
And yeah, I just realized the greatness of custom ROMs. There are many benefits of rooting I know, the most important one to me right now is the ability to create more space for apps. That internal memory is really lacking on the explorer...
I realize that a way to lock the bootloader might be created before I need to send it for repairs (if ever), although I am not sure what the chances are. That's why I'm now looking into how to unlock it.
The thing is, I don't want to use HTCdev, not because it doesn't work, but for the following two reasons.
I live in Malaysia, and I believe they WILL check the bootloader. But just in case they won't check it, my warranty stays intact (on paper).
HOWEVER, I've read on multiple threads (of other android phones) that unlocking your phone using HTCdev will alert HTC that you have rooted it, and it will automatically void your warranty (on paper). No hope for warranty repairs there, even if they don't check bootloader.
I've also read on threads (of other android phones) that attempt locking the bootloader (without it saying relocked), that it doesn't work for phones that have been unlocked using HTCdev.
That's why I ask if there is another way to do it for the explorer.

Djalaal said:
Yeah, that helped.
And yeah, I just realized the greatness of custom ROMs. There are many benefits of rooting I know, the most important one to me right now is the ability to create more space for apps. That internal memory is really lacking on the explorer...
I realize that a way to lock the bootloader might be created before I need to send it for repairs (if ever), although I am not sure what the chances are. That's why I'm now looking into how to unlock it.
The thing is, I don't want to use HTCdev, not because it doesn't work, but for the following two reasons.
I live in Malaysia, and I believe they WILL check the bootloader. But just in case they won't check it, my warranty stays intact (on paper).
HOWEVER, I've read on multiple threads (of other android phones) that unlocking your phone using HTCdev will alert HTC that you have rooted it, and it will automatically void your warranty (on paper). No hope for warranty repairs there, even if they don't check bootloader.
I've also read on threads (of other android phones) that attempt locking the bootloader (without it saying relocked), that it doesn't work for phones that have been unlocked using HTCdev.
That's why I ask if there is another way to do it for the explorer.
Click to expand...
Click to collapse
You've read correctly.. There's actually two stages to unlocking your phone.. Rooting comes after unlocking.. Unlocking your bootloader and radio.. What the HTCdev website does, is unlock the bootloader.. There is no way to unlock radio for our phone yet.. And thats because this phone is relatively new..
For more info on this, just google 'What is S-OFF'... You'll find all the info you need..
Also, there's this thing called an XTC Clip.. It turns your phone to S-OFF.. A piece of hardware, it is.. A 1 time use XTC clip costs around 70 US$..
Not compatible with Explorer yet..
And also, this just in.. HTC phones unlocked from the official HTCdev website, turned to S-OFF, have been successfully Locked and S-ONed.. LOCKED.. Not RELOCKED... So they got their warranty back.. I believe they were HTC EVO 3Ds...
And there are a lot of theories flying around, for ideas regarding S-OFF or Locking instead of RElocking.. You can find them all here on XDA..
Most of them in the HTC Wildfire S forum..
And also, as long as you have S-ON, it is impossible to hard brick your phone, because all the changes that you make to the partitions, are lost on reboot.. So no error sticks.. Unless you are crazy enough like me, to try some other phone's gold card into your Explorer..
So, you wont be needing your warranty, unless you damage your phone physically, as it is not possible to (soft)damage an HTC without S-OFF..
Everybody else.. If I'm wrong in this somewhere, please correct me..
---------- Post added at 04:49 AM ---------- Previous post was at 04:44 AM ----------
HTC phones are hauntingly complicated..

I've tried unlocking the bootloader on my explorer, downloaded the files and followed the process but somewhere along the line something goes wrong.
1. What is the RUU?
I noticed on the tut. That I used the first time, it said nothing about it. Once it didn't work I tried a different tut. It mentioned flashing the RUU to update. But on that tut. On the htc.dev sight it gave that option, on the one I used that wasn't an option. Is changing the RUU mandatory and if so how?
2. Which file needs to be extracted, in the beginning there are three files that have to be pasted in a folder that I have to create. I did that and when I open the window to give the commands I notice that on the tut. It shows as admin/user: but mine reads user/user: what did I do wrong? I can't get passed that point. Any help will be appreciated. I'm anxious to root my ex. And start modifying. Thanks fellas!:what:
Sent from my HTC Explorer using xda app-developers app

daddybux said:
I've tried unlocking the bootloader on my explorer, downloaded the files and followed the process but somewhere along the line something goes wrong.
1. What is the RUU?
I noticed on the tut. That I used the first time, it said nothing about it. Once it didn't work I tried a different tut. It mentioned flashing the RUU to update. But on that tut. On the htc.dev sight it gave that option, on the one I used that wasn't an option. Is changing the RUU mandatory and if so how?
2. Which file needs to be extracted, in the beginning there are three files that have to be pasted in a folder that I have to create. I did that and when I open the window to give the commands I notice that on the tut. It shows as admin/user: but mine reads user/user: what did I do wrong? I can't get passed that point. Any help will be appreciated. I'm anxious to root my ex. And start modifying. Thanks fellas!:what:
Sent from my HTC Explorer using xda app-developers app
Click to expand...
Click to collapse
An RUU is Rom Update Utility.. Its given out by the company in the form of updates over the stock Rom.. As far as I know, an RUU isnt required for htc explorer yet..
To unlock the bootloader, you need two commands.. ADB and Fastboot.. Download this package..
http://forum.xda-developers.com/attachment.php?attachmentid=992962&d=1333997171
It has ADB and fastboot.. so you dont need to download the whole sdk.. Also, download htc sync for drivers..
After that, follow the instructions given on the htcdev website.. and if everything goes properly, you'll hve an unlocked bootloader..

shortyoko said:
The thing is, you cannot root your phone, without unlocking the bootloader, then you wont have warranty, however in this thread > http://forum.xda-developers.com/showthread.php?t=1816836 the OP says, that he knows the way, of locking the bootloader again. Locking the bootloader is important thing to do, if you have to use your warranty, rooting is not the issue, the tricky part is, for now I havn't seen anyware that you lock your bootloader and it says LOCKED, there is just a standart way that says RE-Locked, this won't do the trick. My idea is, PM the OP in the thread, if he can help you, root it, if he can't and you are afraid to brick your device, don't root it and stay with stock rom. I hope that's the answer what you looked for.
Click to expand...
Click to collapse
You can do it but no dev( with that knowledge) is interested to look in our small Pico
Example
Wildfire s bootloader can be controlled without HTCdev
There is a software by which you can unlock relock and show locked also !!!
Sent from my HTC Explorer A310e using xda premium

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