Database Info

How can I get back to the stock rom in AT&T HTC One X

Hello every one,
since HOX from AT&T was sim locked I thought maybe one of the customroms have the ability to unlock the sim but non of them does that.
So now I want to go back to the original "Stock rom" that the HOX from AT&T came with if that possible and how?
I would really appreciate the help.
thanks a lot in advance.

Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry

shakash3obd said:
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry
Click to expand...
Click to collapse
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I know it's not rocket science, but even before I created this thread, I knew that I need to do what you just said but my problems were the following:
When I was trying to relock the bootloader using the windows command line, I got the following message
< waiting for device >
and that stayed there forever, I mean I was waiting for 2 hours just to make sure wither something working or not but it wasn't doing anything.
I got the previous message when I typed the following command
fastboot oem lock
-------
I thought maybe I need to run the RUU first, then I should relock the bootloader but even doing that ended up with error.
By the way, the RUU I used is
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed
and I am currently downloading
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
and I will see if this one works or not.
I hope you can see that I didn't post this thread without doing some search first but in fact it was the time to ask for help so it is not laziness.
Thanks

waiting for device indicates it doesnt see your phone. are you in fastboot USB when you run the command?
do you have FAST BOOT disabled in the OS (settings, power)
there are a couple of tutorials already available on this exact subject...not sure what it is you are looking for at this point, but it sounds like you need to get your computer to see the device
there is zero need to wait 2 hours for fastboot to show up on computer, it should happen immediately assuming you are actually in FASTBOOT USB mode
remember UNLOCKING the phone with HTCDEV?
you pretty much follow those guidelines to get
fastboot oem lock
to work
then you can run the RUU, any RUU made for your device (CINGULAR RUU is correct)

Can't flash a ROM. Help!

I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!

CP24EVA said:
I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!
Click to expand...
Click to collapse
Do some research first because seems like u don't have even a custom recovery or even roooted... Now also never install anything that says endeavour or you will **** up your phone enough said...now do u have att one x or rogers telstra

WOAH, STOP RIGHT THERE.
endeavoru.img IS THE WRONG IMAGE!!!! I can smell a brick!!! the endeavoru image is for the quad core tegra one x. I am assuming you have a OneXL or one of the other Qualcomm DUAL CORE One X's
Our phone is called EVITA.
If you have a non ATT one x like a Telstra One XL or rodgers go to htcdev website.
If you have a ATT version I have recently found out that some versions cannot be rooted, and root is needed to unlock the bootloader. If it has ATT logo on the top where HTC should be, then you need to know the version number of your current rom before putting in any more effort to unlock. Check settings>about phone>
Check the forum in the One X Android Development/[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 10/2/12) for the versions that can be rooted/unlocked.
Hope this helps
-Liam

mine is the ATT version......
My phone isn't bricked yet...phew. SO....going to get the EVITA then. right? for ATT version?

First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.

llambkin said:
First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.
Click to expand...
Click to collapse
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash

WOW, Thats good. Ours are shipped with the latest, well at least my sisters one was. I thought she would have been screwed, But I was able to unlock with HTCDEV
@omario8484, is there a reason for not using CWM? I have it on my OneXL. I got the touch version, TWRP is good I guess, but I am more familiar with the CWM interface.
-Liam

omario8484 said:
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash
Click to expand...
Click to collapse
I'm simply looking for a link to the evita version. I keep seeing the other one .
Sent from my HTC One X using Tapatalk 2

Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2

AWESOME!!!
Try This http://forum.xda-developers.com/showthread.php?t=1777773
:good:

CP24EVA said:
Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
That's because clock work doesn't support out phone officially !!!!!!!!!!!!!

ChummyDays said:
If you flash some roms with cwm, they sometimes will have serious problems. Twrp works with very Rom perfectly fine.
Click to expand...
Click to collapse
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :

llambkin said:
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :
Click to expand...
Click to collapse
Yes use twrp because USB mount works also some Tom's like he said will have problems

Ok, I got it all sorted. Out. My main problem is I didn't know what the goo interface let me do. Once I found out then it was cake from there. I'm loving this AOKP one so far.

I there a way to get to the play store that doesn't include using an internet browser?

CP24EVA said:
I there a way to get to the play store that doesn't include using an internet browser?
Click to expand...
Click to collapse
Maybe the play store app?

I don't see a play store app in the app tray at all. and when I press the PLAY STORE option in the menu tray, it does nothing.

At&t replacement.

Hey guys, I dropped my phone earlier today and now it won't read my sim card. I can use WiFi and all other things on the phone work well. Just not sim card. If I shake it I can hear something lose inside. I am going to make an insurance claim. I will have a couple days to restore my phone back to its original settings. How do I do that? I am pretty sure I know how to tell relock bootloader. But I can never get the ruu to work for me. Any advice? I could sure use some .
Sent from my HTC One XL using xda app-developers app

Once your bootloader is locked restore the RUU that is specific for your device. For ATT i believe it's 1.85 please double check before doing anything. A quick search will get you that file

mgutierrez87 said:
Once your bootloader is locked restore the RUU that is specific for your device. For ATT i believe it's 1.85 please double check before doing anything. A quick search will get you that file
Click to expand...
Click to collapse
There are 3 different RUUs on AT&T: 1.73, 1.85, and 2.20.
If the OP rooted using the X-Factor exploit, then its 2.20.
If the bootloader is relocked, and the correct RUU is still not working, try to re-install the HTC drivers, and try a different USB port.
I don't think they give a crap whether the phone is stock or not, for an insurance claim. Really, you can just run the thing over with a car, and they will replace it for you. But it won't hurt, of course.

Or report it as lost and use to play with same cost either way
Sent from my HTC One XL using xda premium

ATT ONE X cid problem. Please help

i've unlocked my att one x got supercid.. and then i decided to change it to htc_405... so... it was the wrong choice! and now i can't get back to supercid, i've tryied all guides on forum but no one works..
from adb shell.. command writes.. device not found.
also installed newest htc drivers but nothing changes.. the hasoon allin1 tool doesnt work and i dont know what to do..hellppp :crying:

Are you s-on or s-off?
Sent from my Evita

timmaaa said:
Are you s-on or s-off?
Sent from my Evita
Click to expand...
Click to collapse
i'm s-on

Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4

panda_mode said:
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
i know but i changed it to recieve eu update.. didn't know that he has other cpu.. so now i cant change it to supercid or the original one..

You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita

timmaaa said:
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
Click to expand...
Click to collapse
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded

denny094 said:
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
Click to expand...
Click to collapse
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4

panda_mode said:
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread

Ah I see. Well I can't be much of help then. Sorry
Sent from my HTC One X using Tapatalk 4

denny094 said:
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Click to expand...
Click to collapse
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.

s79336951 said:
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
Click to expand...
Click to collapse
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate

denny094 said:
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
Click to expand...
Click to collapse
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.

redpoint73 said:
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
Click to expand...
Click to collapse
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)

denny094 said:
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
Click to expand...
Click to collapse
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.

redpoint73 said:
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
Click to expand...
Click to collapse
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?

denny094 said:
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
Click to expand...
Click to collapse
That post is really confusing, your sentence structure and punctuation is all over the place. Can you clear it up a bit and ask again?
Sent from my Evita

Yeah, not sure what was being said there. Did going back to ICS fix the adb issue, or did you find another way? So you have SuperCID now? If so, do the facepalm method to get s-off.
If you are still trying to get SuperCID, I don't think hasoon's all-in-one tool will work. Believe its looking for the AT&T CID (cws__001), so any other CID, it will fail. You'll have to use the hex edit method.

Problem is solved thanks I did s-off but I would like to ask you another question.. I installed clear rom sense 5 but the device has very low signal the radio firmware is 0.24p are there new updates to increase the quality?
Inviato dal mio HTC One S usando Tapatalk 4

I'm not sure which which radio you're referring to there. Have you updated the firmware as suggested in the CR thread?
Sent from my Evita

SIM unlock didn't work, factory reset wiped everything, phone doesn't boot.

But wait, there's more.
I just exchanged an Xperia S for this HTC One S in excellent condition. It was already bootloader unloked, has TWRP only that it was sim locked. I tried the unlock.sh script (both from terminal emulator, and root explorer) then manually getting the UN_lock_code and subtracting the reversed 7 digits from the IMEI (with the added one), and even the automated app. The script kept running and never show the unlock code, and the one I got using this method wasn't accepted.
Then I thought I should to a factory reset and try again. So I reboot to bootloader, chose factory reset and now everything is wiped. No OS installed so I can't boot, TWRP won't mount USB storage so I can' flash any other rom.
Please help.

Is this a ville or the ville C2?
From your hbot, it seems like C2

42freelancer said:
Is this a ville or the ville C2?
From your hbot, it seems like C2
Click to expand...
Click to collapse
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?

cars ontols
zgomot said:
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
Click to expand...
Click to collapse
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want. As far as SIM unlocking, shouldn't you be S-Off first?
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.

42freelancer said:
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want.
Click to expand...
Click to collapse
How about ViperSC2? Will that do?
42freelancer said:
As far as SIM unlocking, shouldn't you be S-Off first?
Click to expand...
Click to collapse
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
42freelancer said:
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
Click to expand...
Click to collapse
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.

For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
zgomot said:
How about ViperSC2? Will that do?
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
Click to expand...
Click to collapse
Not sure if you saw my last post before this one, I forgot to reply with your quote.

42freelancer said:
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
Not sure if you saw my last post before this one, I forgot to reply with your quote.
Click to expand...
Click to collapse
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.

That seems to be an issue with Windows 8.1. It also seems to be the only OS affecting fastboot. There is a file I used to get all of my drivers working properly, with ADB and fastboot. Fastboot is required with any S-Off attempt. I'll go scope out the file and return here.
---------- Post added at 08:04 PM ---------- Previous post was at 07:59 PM ----------
zgomot said:
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
Click to expand...
Click to collapse
Try this! This should work: http://forum.xda-developers.com/showthread.php?t=2588979
This is what I used last night to reinstall my drivers with working ADB and Fastboot. It also comes with a picture guide on how to fix the device detection. It's fast, easy, lightweight, and best of all, it works!

Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.

Tried that and I still can't get fastboot devices to enumerate my device. Pfffft.

zgomot said:
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Click to expand...
Click to collapse
No sweat. I've got nothing going on later, so I'll do some research for ya! Night

OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?

zgomot said:
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
Click to expand...
Click to collapse
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601

42freelancer said:
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
Click to expand...
Click to collapse
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.

zgomot said:
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
Click to expand...
Click to collapse
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?

42freelancer said:
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
Click to expand...
Click to collapse
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.

zgomot said:
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
Click to expand...
Click to collapse
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess

42freelancer said:
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
Click to expand...
Click to collapse
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.

zgomot said:
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
Click to expand...
Click to collapse
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] http://forum.xda-developers.com/showthread.php?t=2644607 TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.

42freelancer said:
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
Click to expand...
Click to collapse
PROGRESS!
I managed to get S-OFF. Do I try sim-unlocking now, or is there anything else I have to do first?