Database Info

[Q] One S Dev Phone with root issues

So I bought a One S from craigslist about 2 weeks ago. The guy said it was a dev phone. At the top on the case is a tag of numbers and letters printed on the phone. When I first boot the phone it has a HTC splash screen along with the text
"This build is for development purposes only. Do not distribute outside of HTC without HTC's permission. Failure to comply may lead to legal action."
Booting into the bootloader I get this:
*** LOCKED ***
VLE XC SHIP S-OFF RH
CID-11111111
HBOOT-0.90.0000
RADIO-0.14.31.22_2
OpenDSP-v10.1.0.31.0221
eMMC-boot
Feb 21 2012,14:27:31
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
Also it came with CWM 5.8.1.5 already installed. I tried to use Hasoon's tool to install a more recent CWM but it wouldn't work.
I tried to unlock the bootloader using the htcdev site and token and that didn't work.
I was able to flash it with the UTB ROM using the existing CWM and it works but I cannot gain root access even though supersu is installed and I add apps to its list.
Any ideas on how to get root access?

Looking at your HBOOT version it seems like the device is on early software. You're already S-OFF, so you can try flashing the official TMO release ROM and follow the guides on XDA to root.

hammondnav said:
Looking at your HBOOT version it seems like the device is on early software. You're already S-OFF, so you can try flashing the official TMO release ROM and follow the guides on XDA to root.
Click to expand...
Click to collapse
I don't see the official release. There is a thread here that says T-Mobile USA Complete Rom but there's no link to the actual ROM.

I thought reselling of these phones can land u into trouble ?
I mean the development phones

what about busybox? there's an app to install that if you don't have it
Sent from my Kindle Fire using xda premium

dude thats awesome
post us some pictures of the phone and the HBOOT menu
If you are S-OFF and supercid, the possibilities are endless... flash an ruu, that should bring you upto date with the latest firmware and software..

azzledazzle said:
dude thats awesome
post us some pictures of the phone and the HBOOT menu
If you are S-OFF and supercid, the possibilities are endless... flash an ruu, that should bring you upto date with the latest firmware and software..
Click to expand...
Click to collapse
it wont let me post my photo album because i am still new so i am pm'ing you the link. what are some things i can do with this phone? i'm still a noob but a quick learner. so far i've only flashed a couple of roms. currently using black dragon's. still haven't gotten root access though.

dannyy2200 said:
it wont let me post my photo album because i am still new so i am pm'ing you the link. what are some things i can do with this phone? i'm still a noob but a quick learner. so far i've only flashed a couple of roms. currently using black dragon's. still haven't gotten root access though.
Click to expand...
Click to collapse
You could talk to the devs in the development section (as soon as you have your 10 posts) und help them to get s-off with providing informations maybe.

yeah man that would be a great idea, PM some and see if you can help them as for getting the bootloader unlocked, Unless HTCdev isnt working, there isnt much else yet.
why does it not work ? what errors does it give ?

hmm seems that I'm lacking some knowledge ^^
Is there any necessesity for unlocking the bootlaoder if the device already has s-off? Thouht that s-off would mean no security and full system access.

S-OFF means the NAND partition is writeable, When its S-ON this partition is locked (Security ON ), so with S-OFF we can customise even further, Flashing Radio.IMGs and lots more,
With unlocked bootloader we can do things like install a recovery and flash Root.
the perfect scenario would to have S-OFF AND Unlocked Bootloader.

azzledazzle said:
S-OFF means the NAND partition is writeable, When its S-ON this partition is locked (Security ON ), so with S-OFF we can customise even further, Flashing Radio.IMGs and lots more,
With unlocked bootloader we can do things like install a recovery and flash Root.
the perfect scenario would to have S-OFF AND Unlocked Bootloader.
Click to expand...
Click to collapse
Ah alright, I thought S-OFF would already allow to flash root.

nope usually when using an S-OFF tool, such as revolutionary, It will unlock bootloader at the same time..
surely theres someone out there can can do something really awesome with this developer phone !!

azzledazzle said:
yeah man that would be a great idea, PM some and see if you can help them as for getting the bootloader unlocked, Unless HTCdev isnt working, there isnt much else yet.
why does it not work ? what errors does it give ?
Click to expand...
Click to collapse
well it doesn't give me any errors, and says unlock successful, and just acts as if it went ahead and unlocked, but when i boot into the loader it still says locked. weird.

hmmmm..
maybe theres a command you can use in adb ? Im not sure..
I know the command to relock is ''fastboot oem lock'' maybe ''fastboot oem unlock'' might do something lol.
i have no idea as with most things in my life

question about RELOCKED status - Can someone try it?

Hello all,
I have an idea and I would like to ask someone to prove or confute it.
Given a Desire S out of box, full stock. What if we downgrade it to the oldest RUU, and S-OFF with the Revolutionary way. install engineering HBOOT, and tries to restore its stock status (standard HBOOT, S-ON, unrooted etc). The question is: what if we upgrade it to the latest (2.3.5 w/ Sense 3.0) RUU? What will be seen in the bootloader's header? LOCKED or RELOCKED? Because if you unlock your phone via HTCDEV.com, the new software version (or how to call it) will record this somewhere, but downgrading to an older version this can't be seen (but we know it is there). So if it is only because of the behaviour of the latest software, can we circumvent it with a downgrade?
In other words (just to clear thing up):
known to void warranty: HBOOT 2.00.0002 --> unlock via HTCDEV.com --> fastboot oem lock --> bootloader shows RELOCKED (downgrading makes this disappeared, but comes back after upgrading to current version)
method in question: HBOOT 2.00.0002 --> downgrade to 0.98.000x --> unlock/S-OFF via Revolutionary --> relock/S-ON --> upgrade to HBOOT 2.00.0002 --> bootloader shows ???
Unfortunately I don't own a DS personally, but one of my friends do, but he doesn't want to put a custom ROM on his phone until he is sure it is possible to keep the warranty this way.
Any answer is appreciated, and of course thanks in advance.

Already reported by several people on the forum. Will show RELOCKED. As you said yourself, the status bits don't change with downgrade, and when upgrading back - the new bootloader reads just what there was before the downgrade.

Thank you, but what really interests me is the oldest RUU. Is this bit set by this also? 'cause I understand what you wrote, this bit is there whether you are using the 1.28​.401​.1 or the 2.10​.401​.9, but is this bit set by both and read only by the latter? In this case it is a no go for my friend without void the warranty
So I'm curious does 1.28​.401​.1 also set this bit to "tampered"?

craftman said:
Thank you, but what really interests me is the oldest RUU. Is this bit set by this also? 'cause I understand what you wrote, this bit is there whether you are using the 1.28​.401​.1 or the 2.10​.401​.9, but is this bit set by both and read only by the latter? In this case it is a no go for my friend without void the warranty
So I'm curious does 1.28​.401​.1 also set this bit to "tampered"?
Click to expand...
Click to collapse
This "feature" was implemented in Sense 3 update after the launch of htcdev.com. It is present on previous versions like 1.28.401.1, therefore nothing is read by the bootloader. But the flag is there and nobody managed to find and change it so far.
Sent from my HTC Desire S

That's a pity. Then he has to wait for the offical ICS with Sense 3.6 which is not so far (hopefully).
Thanks for both of you for helping out a newbie.

[Q] going back to stock

hi everyone,
Sorry if I posted this in the wrong forum. I have the One X which I just rooted, unlocked BL and also did S-off just over the weekend as I was wanted to try some JB. Now my sim card slot failed, it keeps saying no sim card found. I tried my sim on a different phone and the sim works. Now I am trying to get back everything as close to stock(2.20) as possible, so that I can get a exchange with att/htc. I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ? I still have s-off, Is there anyway I can go back to s-on and reset my c-id ?
Thanks in advance.

Just to elaborate on my original message below, though I have s-off, and unlocked bootloader, I have not flashed any ROM. I just flashed the twrp recovery.
Now I have everything back to original but for the following
a) I am still S-off. Can I go S-On ?
b) bootloader says relocked, can I make it to say locked ?
c) can someone point me to the link for 2.20 RUU zip file ?
Thanks,
onex_001 said:
hi everyone,
Sorry if I posted this in the wrong forum. I have the One X which I just rooted, unlocked BL and also did S-off just over the weekend as I was wanted to try some JB. Now my sim card slot failed, it keeps saying no sim card found. I tried my sim on a different phone and the sim works. Now I am trying to get back everything as close to stock(2.20) as possible, so that I can get a exchange with att/htc. I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ? I still have s-off, Is there anyway I can go back to s-on and reset my c-id ?
Thanks in advance.
Click to expand...
Click to collapse

onex_001 said:
I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ?
Click to expand...
Click to collapse
No, you've got it backwards. Its intended to say RELOCKED (or UNLOCKED) once its been unlocked. It might be possible to change these flags, if you have S-Off. But such a thing has not been discovered yet. Nor has a method to S-on been discovered yet (or at least not that has been posted here).
Just relock and RUU. It will still say RELOCKED and S-Off, (otherwise stock). But AT&T doesn't seem to care about the bootloader being unlocked on this device. Many people have gotten warranty service from AT&T for phones that say RELOCKED. I think some folks have even warrantied devices UNLOCKED and running custom ROMs! Just make sure you go through AT&T, as HTC themselves are known to be much more strict about their warranty coverage.
---------- Post added at 04:46 PM ---------- Previous post was at 04:42 PM ----------
onex_001 said:
c) can someone point me to the link for 2.20 RUU zip file ?
Click to expand...
Click to collapse
Don't know why people ignore this, and make life so hard for themselves:
http://forum.xda-developers.com/showthread.php?t=1671237
You can also get it straight from HTC's support website.

Going back to S-on is simple fastboot command, but there's no reason to do it.
You can edit some of your bootloader text in various ways. Start with this thread:
http://forum.xda-developers.com/showthread.php?t=2156368
But don't try any of this unless you know what you're doing.

HTC One X AT&T 2.20 Firmware Stock boot.img file

I need the boot.img file for my phone At&t Htc one x with firmware 2.20 please
This is very important to me because my phone doesn't work .
Thank you so much .

If you're not rooted you could look for the 2.20 ruu and reflash it. Or better yet get your phone s-off and not have to worry bout flashing boot img's any more.
What the issue you're having there? When you say it won't boot, what's it doing?
Sent from my now S-Off HTC OneXL
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
http://forum.xda-developers.com/showthread.php?t=1814217
Easy search...
Sent from my now S-Off HTC OneXL

redbike said:
I need the boot.img file for my phone At&t Htc one x with firmware 2.20 please
This is very important to me because my phone doesn't work .
Thank you so much .
Click to expand...
Click to collapse
Did you flash any ROM and got stuck in boot loop? If so the boot.IMG will be inside the rom zip file itself

this is the stock boot_signed.img pulled out of the rom.zip for 2.20
link to the 2.20 ruu htc_one_x_RUU_2.20.502.7_att_us_08022012.exe a40cd830e8c57109d140e1e68e2d1328

I just got a htc one x and it was supposed to be unlocked, it's not and has viperXL on it so the unlock code is not working. Would this file put me back to 'stock' to unlock my sim?

unlocked bootloader is not the same as unlocked sim, so when you bought it unlocked the seller probably mean't the bootloader.

I was told it would work with tmobile - so i assumed that would of been a sim unlock. guess i was wrong. Either way I know nothing of this type of stuff and just want a working phone. searching posts it seems the sim unlock code will not work if it's not on a 'stock rom' but I dont have a copy of this because i didn't change it. It has viperXL 3.2.5 So if i'm comprehending all of this I need to get a bootloader and go back to a stock rom (?) Sorry this is really all new to me.

tweek69 said:
I was told it would work with tmobile - so i assumed that would of been a sim unlock. guess i was wrong. Either way I know nothing of this type of stuff and just want a working phone. searching posts it seems the sim unlock code will not work if it's not on a 'stock rom' but I dont have a copy of this because i didn't change it. It has viperXL 3.2.5 So if i'm comprehending all of this I need to get a bootloader and go back to a stock rom (?) Sorry this is really all new to me.
Click to expand...
Click to collapse
it only has to be a sense rom which ViperXL is. there is no end user method to sim unlock without paying for it, so you'd have to buy an unlock code or ask the person you bought it from if he meant sim unlocked or bootloader unlocked.

I did purchase a unlock code and it didn't work. That's when I hound a post about someone saying they had issues when it wasn't on a 'stock' flash. Do you think the viper xl isn't the problem then? Cause if not I'd be more then happy to just leave it on

if you haven't got your unlock code to work you could try a more stockish sense rom like cleanrom

[Q] AT&T HTC ONE XL custom rom & recovery installed on locked phone

Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.

Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?

Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.

you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.

srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.

redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers

srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.

Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?

Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita

Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse

Have you checked your APNs?
Sent from my Evita

srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.

It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers

Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.

Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?

srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.

Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......

So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers

What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita

timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.