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

[Q] dead screen. need assurance about unrooting

First off, thanks for all the help I've had from the xda community over the past few months. I've only just signed up, but I've been an avid noob learner thanks to your guides and various threads. Much appreciated.
Now my question: My Sensation is rooted, currently with Revolution HD (6.?.?) installed and everything has been running smoothly since I first flashed a custom ROM a few months back, but last night it powered down after the battery died and now the screen won't power up. It seems to be charging, it vibrates when I power the phone, and adb recognizes it when I search for connected devices, but the screen is flat out dead. Not a blank, black screen, just dead. No power to it.
Obviously I'd like to send it in for repair, so I need to unroot while making sure the stock recovery has been installed in place of CWM and that it is S-on.
I found a guide to unrooting with adb which seems straightforward enough, but how can I be sure everything has worked without the benefit of seeing the phone's screen?
Thanks in advance
-Bizwax

If your screen ain't working I guess you're SOL

So if I attempt to unroot with adb, can I not then use it (or another app) to confirm the status of my phone's firmware, recovery and s-on/off before I decide whether to send it for repair or not?

I don't know. I have heard of a few people sending in phones that wont turn on and HTC fixes or replaces them anyways. I guess they change out the main board. Wait a while longer and see what other people say.

That's the problem, the phone does seem to boot, so if they simply need to replace the screen they're going to see that it's rooted. Then they've got me over a barrel - they have my phone and would be within their rights to hold it until I pay for their repairs.

I don't know how they do it over in the UK but in the US they can't force you to pay for a repair if you don't want it. I'm pretty sure that they will tell you if there will be a charge before they do the repair. But they may do things differently over there.

hmm..the screen is completely dead and not even showing bootloader screen right
then doing un root and reverting the cid and all is little bit tough but completely possible
first i require some data
for that you need to go to bootloader
to do that
just power off the phone...remove the battery..reinsert the battery and then press power + voulme down buttons together..that should take you to bootloader screen (small vibration happens when you do that )
to verify that phone is connected to bootloader or not
connect the phone to pc ..
then in adb folder
type "adb devices" ->this should not show your device
type 'fastboot devices" -> this should show your device
once fastboot recognizes your device
type this "fastboot getvar all" and post the complete output
except IMEI and serial number (these are sensitive data )
then I'll guide you further

I'm just thinking worst case scenario. I don't know HTC's repair process, but if they check it over instead of running a full diagnostic and realise it's just the screen needs replacing, then they do that and test to see everything is working ok and that's when they spot that it's rooted, that would be a problem. They would already have done the work and I'd be obligated to pay them for that. Maybe I'm being overly cautious/paranoid, but still, if there's a way for me to unroot I'd rather go that route.
Someone on IRC pointed me towards android app VNC Server. That would give me remote access to my phone, plus a live screen capture gui to work through, so that might be a possibility. I know I can use adb to install it and I think I can use it to remotely boot apps on my phone too. I'm still looking into how I would do that though. Then the problem is that VNC requires a rooted device to work, which would probably be fine at the moment, but once I go to unroot that plan goes out the window. Unless I can find an alternative for unrooted phones.
Edit: that's right ganeshp. No screen activity whatsoever. Thanks for the advice, I'll get on that now.

Code:
C:\adb>adb devices
List of devices attached
123456789012 device
C:\adb>adb reboot-bootloader
C:\adb>fastboot devices
123456789012 fastboot
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: 11.22.3504.07_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.401.3
INFOserialno: 123456789012
INFOimei: XXXXXXXXXXXXXX
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4043mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.525s
I know you said to exclude the serial number as well, but 123456789012? Is that a big deal or is it just because it's flashed with a custom rom?
Volume plus power button doesn't work btw. I had to use adb. Just thought I'd add that in case. Every little helps, right?

well you are SOFF and supercid ..thats all i need..i mean you can actually RUN any RUU
but I Think you are from UK and orange network (from your profile )...so lets go for that corresponding RUU
get the ICS RUU from this thread
SHIPPED PYRAMID ROMS
i found one along the line "RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe" get that if you have normal sensation
if you got sensation XE
i cant find XE version of ORANGE RUU (the name has LE ..means an XE version) ...search the thread
otherwise get this XE version
"RUU​_Pyramid​_LE_HTC​_Europe​_1.73​.401​.4_Radio​_10.58​.9035​.0.."
then running the RUU
connect your phone to pc while in fastboot ..(just like earlier) then
run the ruu from pc
follow the onscreen instructions
this RUU ..will wipe everything and make it stock...except SOFF and supercid
once RUU run is over
we will change the cid back to normal
first get your cid from here (i think your cid is ORANG001..but confirm from the thread again)
CID LIST
once you know the cid...back to fastboot and connect it to PC
type this command
fastboot oem writecid <yourCID> (eg fastboot oem writecid ORANG001)
this will get your cid back to normal/original
now reboot normally (this is must to change CID)
using command
fastboot reboot
now the most important and careful step (this should be done last..i MEAN LAST)
back to fastboot again..and connect it to pc
now type this
fastboot oem writesecureflag 3
after this
do a reboot using fastboot reboot
thats all now you are stock

I am with Orange but my Sensation (standard not XE) was unbranded when I bought it. I take it the RUU_Pyramid_HTC_Europe_ roms are the ones I should be looking at?
The Fileserve links aren't working anymore but I found another collection of RUUs here. Is that site ok because I'm grabbing one of them now (RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe)
Oh and about the serial number, how do I get that back to what it should be? eg. SH15FG36536. I do have the CWM backup from when I first rooted if it's needed
Please excuse my noobness.

Bizwax said:
I am with Orange but my Sensation (standard not XE) was unbranded when I bought it. I take it the RUU_Pyramid_HTC_Europe_ roms are the ones I should be looking at?
The Fileserve links aren't working anymore but I found another collection of RUUs here. Is that site ok because I'm grabbing one of them now (RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe)
Oh and about the serial number, how do I get that back to what it should be? eg. SH15FG36536. I do have the CWM backup from when I first rooted if it's needed
Thx
Click to expand...
Click to collapse
RUU will take care of it..no worries..and no one check it too afaik

Kevc44485 said:
I don't know how they do it over in the UK but in the US they can't force you to pay for a repair if you don't want it. I'm pretty sure that they will tell you if there will be a charge before they do the repair. But they may do things differently over there.
Click to expand...
Click to collapse
They can never force anybody, I'm pretty sure that's illegal worldwide. Anyway, try and ask HTC how much it will be but I'm guessing a lot. I enquired how much it would my semi bricked sensation which is now perfect and it was £100.
Sent from my Sensation using XDA

sensation lover said:
They can never force anybody, I'm pretty sure that's illegal worldwide. Anyway, try and ask HTC how much it will be but I'm guessing a lot. I enquired how much it would my semi bricked sensation which is now perfect and it was £100.
Sent from my Sensation using XDA
Click to expand...
Click to collapse
They could if you gave them a phone that was supposedly under warranty and then it turns out that the warranty turns out to be void due to custom software.
Hope you get everything sorted out op
Sent from my sensational sensation 4g

Quick update; ganeshp's instructions at the bottom of page 1 of the thread helped a lot and I now have a stock Sensation with cid HTC__001 and S-on. It's booked for pickup by HTC tomorrow.
I did run into an issue after running the RUU update though. The installation completed ok but then I couldn't get the phone to show up in adb or fastboot devices. After retrying the RUU install a few times (with plenty of failed RUU install attempts and another issue where the phone wouldn't get out of recovery mode in adb) I finally got it to work and completed ganeshp's steps. All is good
I just hope the serial number thing (showing as 123456789012 in adb) doesn't come back to bite me on the backside. I found another guy on here with the same issue and apparently it was down to a corrupted pds partition.

Sorted. Got the phone back this morning, new screen and main board. Thanks lads

ganeshp said:
well you are SOFF and supercid ..thats all i need..i mean you can actually RUN any RUU
but I Think you are from UK and orange network (from your profile )...so lets go for that corresponding RUU
get the ICS RUU from this thread
SHIPPED PYRAMID ROMS
i found one along the line "RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe" get that if you have normal sensation
if you got sensation XE
i cant find XE version of ORANGE RUU (the name has LE ..means an XE version) ...search the thread
otherwise get this XE version
"RUU​_Pyramid​_LE_HTC​_Europe​_1.73​.401​.4_Radio​_10.58​.9035​.0.."
then running the RUU
connect your phone to pc while in fastboot ..(just like earlier) then
run the ruu from pc
follow the onscreen instructions
this RUU ..will wipe everything and make it stock...except SOFF and supercid
once RUU run is over
we will change the cid back to normal
first get your cid from here (i think your cid is ORANG001..but confirm from the thread again)
CID LIST
once you know the cid...back to fastboot and connect it to PC
type this command
fastboot oem writecid <yourCID> (eg fastboot oem writecid ORANG001)
this will get your cid back to normal/original
now reboot normally (this is must to change CID)
using command
fastboot reboot
now the most important and careful step (this should be done last..i MEAN LAST)
back to fastboot again..and connect it to pc
now type this
fastboot oem writesecureflag 3
after this
do a reboot using fastboot reboot
thats all now you are stock
Click to expand...
Click to collapse
Hello there, I was in a very similar position the OP was in.
My Sensations' screen was only displaying static. I left the screen on and after returning to the phone, the display was frozen. After taking the battery out and restarting it, it would only show static (when the HTC logo should appear) but the phone was functional as I could change the volume and hear sounds from the phone, but there was only static showing,
So I needed to get it repaired from HTC but the phone was rooted, S-OFF and supercid so I was very happy when I found this guide as it explained how to get back to stock when you can't see the display.
This was is how my phone was when it was S-OFF and supercid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After following the guide to get S-ON and cid back to stock (orange branded):
I installed the RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe.
I sent the phone off exactly 2 weeks ago and got the phone back today not repaired.
A letter with the phone stated the phon was BER (Beyond Econimic Repair) since the phone had "Unauthorised Engineering".
I was sure everything was back at stock so how can they say it is BER because of "Unauthorised Engineering".
Apologies for the long post but what can I do?

carlitob10 said:
Hello there, I was in a very similar position the OP was in.
My Sensations' screen was only displaying static. I left the screen on and after returning to the phone, the display was frozen. After taking the battery out and restarting it, it would only show static (when the HTC logo should appear) but the phone was functional as I could change the volume and hear sounds from the phone, but there was only static showing,
So I needed to get it repaired from HTC but the phone was rooted, S-OFF and supercid so I was very happy when I found this guide as it explained how to get back to stock when you can't see the display.
This was is how my phone was when it was S-OFF and supercid
After following the guide to get S-ON and cid back to stock (orange branded):
I installed the RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe.
I sent the phone off exactly 2 weeks ago and got the phone back today not repaired.
A letter with the phone stated the phon was BER (Beyond Econimic Repair) since the phone had "Unauthorised Engineering".
I was sure everything was back at stock so how can they say it is BER because of "Unauthorised Engineering".
Apologies for the long post but what can I do?
Click to expand...
Click to collapse
you know what mistake you did ?
you had the wrong RUU flashed
the RUU is of Europe unbranded one
you should have flashed the correct RUU
based on your CID ..you should flash this
"RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe"
see in the screenshot the version-main is 1.45.401.2
but it should be x.xx.61.x for ORANGE UK phone (so tha above one will have 1.35.61.1)
that's how they figured it out about your issue
EDIT: forgot to tell you what you should do
try revolutionary SOFF and get the above RUU and flash it
here the ruu download link
flash it again
do SON
and send it back

ganeshp said:
you know what mistake you did ?
you had the wrong RUU flashed
the RUU is of Europe unbranded one
you should have flashed the correct RUU
based on your CID ..you should flash this
"RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe"
see in the screenshot the version-main is 1.45.401.2
but it should be x.xx.61.x for ORANGE UK phone (so tha above one will have 1.35.61.1)
that's how they figured it out about your issue
EDIT: forgot to tell you what you should do
try revolutionary SOFF and get the above RUU and flash it
here the
flash it again
do SON
and send it back
Click to expand...
Click to collapse
OK thank you ganeshp, I am in fastboot at the moment and the phone is detected. I run revolutionary but its says "waiting for device" and nothing happens.
Why is revolutionary not detecting my phone?
EDIT: Nevermind, got it working

ganeshp said:
you know what mistake you did ?
you had the wrong RUU flashed
the RUU is of Europe unbranded one
you should have flashed the correct RUU
based on your CID ..you should flash this
"RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe"
see in the screenshot the version-main is 1.45.401.2
but it should be x.xx.61.x for ORANGE UK phone (so tha above one will have 1.35.61.1)
that's how they figured it out about your issue
EDIT: forgot to tell you what you should do
try revolutionary SOFF and get the above RUU and flash it
here the
flash it again
do SON
and send it back
Click to expand...
Click to collapse
What about the bootloader? Isn't that supposed to be locked since HTC's warranty will not cover unlocked bootloader?
And how do check with adb if bootloader is locked or unlocked?
Thanks

[Q] Telstra One XL Help.....

I was wondering if someone could help me? ... I recently acquired a Telstra Htc One XL and am having troubles trying to update.
Current stats
android 4.1.1
sense 4+
software 3.17.841.2
EVITA PVT SHIP S-OFF RL
*****locked*****
CID-11111111
HBOOT 2.14.0000
RADIO- 0.23a.32.09.29
I'm 99.9% sure most testra one xl's are up to 4.2.2 with sense 5 which is i think two updates in front of mine
can anyone shed some light on my situation?

When you say you're having trouble updating what exactly do you mean?
Sent from my Evita

When i "Check for Updates" it tell me that there are no more updates.... when Im sure there are another two...

Are you in Australia?
Sent from my Evita

Sure am ... Good old city of churches" Adelaide" ..

timmaaa said:
Are you in Australia?
Sent from my Evita
Click to expand...
Click to collapse
His profile says he is

Yeah, but still needed to check. Have you thought about re-unlocking your bootloader? It's been modified in the past which might have something to do with your update problem. If you unlock your bootloader you'll be able to install a custom recovery and then you can install whatever ROM you like. We have the stock Telstra Sense 5 Android 4.2.2 ROM in our development section. We also have a few other Sense 5 ROMs to choose from, ranging from stock to tweaked.
Sent from my Evita

The thing is that it hasnt been messed with.I got the phone from a HTC rep that i know ... he had it in his draw for over six months ...I just wanted the stock update but maybe rooting might be the easier way

It definitely has been messed with, phones that are s-off and have SuperCID don't come out of the factory like that. Somewhere along the way someone has done those alterations to the device.
There is just one problem I've realised, your phone has a SuperCID of 11111111 which has been blocked by htcdev. You're s-off though so you can actually change that as many times as you like using fastboot. If you want to unlock your phone you'll need to change it to 22222222 using the following fastboot command:
Code:
fastboot oem writecid 22222222
You can then check the new CID by using this command:
Code:
fastboot oem readcid
Once that's done you can go to htcdev and go through with the unlock bootloader process.
In order to do the above process you will need to install adb/fastboot and HTC drivers.
Sent from my Evita

No problem ... thanks for that ....I have rooted my one x before HTC_023 fairly basic but my mate swears that the phone came straight from HTC as a Tell us what you think before we send you more kind of thing .. Cheers for the info ...
Actually one more thing ... is it possible to do a RUU update with this to 4.2.2?

There is no RUU for 4.2.2, the only way is to run an earlier RUU and take OTA updates to get there. Since you can't get the OTA I guess that isn't an option though.
Sent from my Evita

grekojim said:
Sure am ... Good old city of churches" Adelaide" ..
Click to expand...
Click to collapse
Within 30 minutes drive from me no doubt
Supercid and s-off from factory or not still means you are off the official path.
Things I might do:
fastboot oem writecid TELST001
Then try the OTA again
or
RUU back to 1.89.841.9 as a RUU exists for that, then ota forwards to 5.06.841.1
or
Unlock bootloader
Flash Turges 5.08 firmware zip and then take one of the Sense 5 ROMs. There is a stock Telstra ROM even.
PS nag the HTC rep for a more recent RUU, eg 2.40.841.4, 3.17.841.2, 3.17.841.9 or 5.06.841.1 and share with us
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
timmaaa said:
Once that's done you can go to htcdev and go through with the unlock bootloader process.
Click to expand...
Click to collapse
He has s-off does he need a token or even need to unlock at all?

I have often wondered the same thing, but I've been assuming that in order to flash TWRP recovery you need an unlocked bootloader.
It's nice to see a few Aussies on here by the way, I'm in Melbourne myself.
Sent from my Evita

great ... trying the cid thing first ...

My phone from an att employee came s-off and with a locked boot loader as well. It just looks like that's how HTC and att do it.
Sent from my HTC One XL

Alright cid change didnt work ..now to find the 1.89.841.9 RUU

Click the link in my signature, from there you'll find a link to the HTC RUU thread.
Sent from my Evita

RUU links all changed and the index doesnt keep good track of the current RUU sites.
Try:
http://www.androidruu.com/?developer=Evita
http://www.androidruu.com/getdownlo...09.01_10.93a.32.20L_release_266699_signed.exe

Thank you heaps .....

Just in case .. i got the unlock code from htc deV But when my cid was 11111111 .....would that matter if i use that code now that my cis is telst001?

Htc one x help scared croatian :(

Hello guys
Sorry for my bad english but il try to be precise as i can. I bought my htc on ebay it says new and it feels new. But after i read may treads here it seems its not new . I have problems with automatic software update it freezes on 20% then it reboots after few minutes, if i regard this problem the phone works fine. But im fustrated i want new software . Now i got in boot loader in this is what it says:
++++locked+++++ - in one tread i read this should be relocked
evita pvt ship s-off rl - i belive this is s-off i need your confirmation
cid - 11111111 - i dont understand fully this yet but its a good thing i belive
h-boot 1.09.0000 - dont understand what this means
RADIO - 0.16a.32.09.17_2 - i belive this is software for my phones antena
open dsp - v25-1-0-32-0405 - dont know if this is imortant
emmc -boot
Apr 2 2012, 21:08:24 - is this last known software update i manufacturing date
Know i need you help to explain this thing to me and if its safe and what do i have to do to install new software. Which software whould you
recommend and maybe can i install viper xl
Thanks

The phone definitely isn't new. You have SuperCID (11111111) and s-off which means it has been unlocked at some point. But the good news is you can easily unlock the bootloader at htcdev, then install a custom recovery, and then install Viper if you wish.
Sent from my Evita

Thanks for the reply, now i never unlocked bootloader can you give me some advice on the safest way to do that and where can i see when bootloader is unlocked, sorry for dumb questions but if i dont ask ill never learn

Can somebody send me some links where can i find instructions on how to unlock bootloader, make recovery image and then how to install viper xl rom

Is your phone an at&t model? If it is it'll have the at&t logo above the screen, otherwise it'll just have the HTC logo.
Sent from my Evita

Itd at&t phone
Sent from my HTC One XL using xda app-developers app

You already have SuperCID so you can go to htcdev and unlock your bootloader.
Sent from my Evita

timmaaa said:
You already have SuperCID so you can go to htcdev and unlock your bootloader.
Click to expand...
Click to collapse
The phone is s-off, does the OP even need to unlock the bootloader to install TWRP, flash ROM, etc.?
You typically won't receive OTAs for AT&T phones outside of North America. So that is probably why the update is failing.

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