Database Info

[Q] HTC ONE XL size Issue

Hello there guys,
Been trying to root my XL from Telstra (AUS) but some weird things are going on.
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
http://forum.xda-developers.com/showthread.php?t=1952038
Also, tried to root my phone using this thread below:
http://forum.xda-developers.com/showthread.php?t=1859478
So far, I have achieved to Installed S-OFF and CWM.
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Im uploading some of the current photos taken so you guys can have more information on S-OFF and CWM.
Thanks in advance.
Ps: One of the pictures was a Failed OTA from Telstra, is there a way to go back to and be able to install the OTA from Telstra instead of any custom ROM (In case we cant find what is causing the phone to block the supercid and the super SU)

Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app

31ken31 said:
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?

Desertum said:
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
Click to expand...
Click to collapse
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Desertum said:
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Click to expand...
Click to collapse
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Desertum said:
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Click to expand...
Click to collapse
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.

redpoint73 said:
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
Click to expand...
Click to collapse
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks

Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Click to expand...
Click to collapse
No you've got it backwards. The boot.img goes in your fastboot folder on your pc, not on your phone.
You need to fastboot flash the boot.img from each ROM you want to flash. So, if you want to install CM10.2, you must extract the boot.img from the ROM zip and put it in your fastboot folder on your pc (not your sd card in your phone). Then you put the ROM zip on your phone, and install it in recovery (after wiping cache/dalvik cache/factory reset/system), then reboot to bootloader and flash the boot.img using fastboot. You must follow this process for each new ROM you want to flash.
Do a backup of your current setup in recovery before flashing anything new though.
Sent from my Evita
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
By the way, even though our phone doesn't have a physical sd slot, we refer to the stage as the sd card.
Sent from my Evita

Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
Click to expand...
Click to collapse
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
Desertum said:
Hello there,
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Click to expand...
Click to collapse
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.

redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
Hi there,
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
I was trying to update the RUU, then restart the phone, went into S-off, then into recovery and Wipe factory/data reset, then install the CM10.2 build
Is something missing here?
Thanks.

Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Also, what do you mean you "went into s-off"?
Sent from my Evita
Click to expand...
Click to collapse
Sent from my Evita

Desertum said:
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
Click to expand...
Click to collapse
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.

redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
Sent from my Evita
Click to expand...
Click to collapse
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.

Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
Click to expand...
Click to collapse
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.

Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Click to expand...
Click to collapse
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita

John uallowt
redpoint73 said:
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
Click to expand...
Click to collapse
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Are you able to do some prompts in regards of what to do?
So far, IMAO I need to to this:
Flash the Correct RUU (Gotta find it first)
Use S-off to Install the Custom ROM (ROM is already copied to the phone's memory)
Install the new Custom ROM, however, not to sure about the GApps, which are google apps.
http://www.reddit.com/r/Android/comments/1kbeoh/gapps_20130813_for_android_43_and_20130812_for/
I guess that you need to copy them before you install the new ROM?
Thank you for your patience.

redpoint73 said:
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Click to expand...
Click to collapse
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?

Desertum said:
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Click to expand...
Click to collapse
As you've been told at least 3 times now, what you should do is READ READ READ.
None of this is hard to understand once you start diving into it and learning.
I'm personally not going to spoonfeed you any more steps (and suggest against doing it either), as shortcutting the learning process is only going to turn your phone into an expensive paperweight.

timmaaa said:
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.

Desertum said:
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Click to expand...
Click to collapse
We're getting there, here are the exact steps you need to take:
1) Read a lot.
2) Read some more.
3) Flash a superuser zip on your current stock ROM, or flash a rooted Sense ROM so you have root.
4) Get SuperCID.
5) Get s-off.
6) RUU to latest.
7) Flash whatever ROM you want.
Sent from my Evita
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Desertum said:
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Click to expand...
Click to collapse
Just go to our Android Development section here and flash one of the new Sense 5 ROMs. They're already rooted.
Don't get information/software from anywhere except XDA by the way.
Sent from my Evita

He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app

31ken31 said:
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Good catch. I missed that.
To the OP: you don't need to RUU to install cm10.2 on your device as you already have the required hboot/firmware. Without s-off you will need to manually flash the boot.img using fastboot though.
Sent from my Evita

[Q] Set Telstra HTC One XL to s-off

Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks

jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita

timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?

jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita

timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.

No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita

timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?

No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita

jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.

Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.

Glad to see you got it all sorted mate.
Sent from my Evita

Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers

Which ROM are you on?
Sent from my Evita

timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946

You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita

timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.

The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita

timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?

You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita

timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!

[Q] Cannot flash any roms!

I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!

Flashing boot.img did not work. I'm in bootloop hell.

mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app

Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita

mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I thought so.....hboot 1.12......

timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
Good catch Timmaaa!
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
****, what's my original CID, I didn't write it down?
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012

timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
ted77usa said:
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
I thought so.....hboot 1.12......
Click to expand...
Click to collapse
No I have "Android Debug Bridge version 1.0.31".

Ah ok, that makes more sense! Are you absolutely sure the ROM you're flashing is an Evita ROM? Where did you download it and what is the full filename?
You said the phone was s-on but not anymore? Why did you return it to s-on? You're gonna need to get s-off again so you can RUU up to 3.18 so you can flash the recent aosp ROMs. When you get the error 99 after flashing the zip, just force a reboot back to bootloader by holding volume down and power together. Once you're back in bootloader you can start again (without the adb reboot bootloader command because you're already in bootloader) and you should get error 92 now. Now, before you give the adb soffbin commands you need to make sure the screen is unlocked and stays unlocked, also make sure usb debugging is enabled in developer options. If it's an aosp ROM you'll also need to grant root access to adb in developer options.
For now my suggestion would be to download a Sense ROM, preferably Android 4.0 or 4.1, this should at least boot and enable you to get s-off on your phone again. Don't forget top flash the boot.img via fastboot.
Sent from my Evita
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
mollysue said:
No I have "Android Debug Bridge version 1.0.31".
Click to expand...
Click to collapse
Your adb version is fine, you can leave that the way it is.
Sent from my Evita

mollysue said:
****, what's my original CID, I didn't write it down?
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
Click to expand...
Click to collapse
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE

ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.

mollysue said:
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
Click to expand...
Click to collapse
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE

ted77usa said:
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks!!!! The rom worked. I'm going to let it sit for a while before doing any more tampering. At least I have a working phone *happy dance*

[Q]Please help connecting to PC

I hope I'm in the right place. I can't connect at all to the PC since I flashed the AOKP_jb_mr1_build4 ROM. The PC says can't find device driver.
Also, I would love to update to newer builds, requiring a newer hboot version I gather, but not quite sure as to how to go about that, and deal with s-on. I only want to do what has to be done to get the latest AOKP ROM builds. Any advice would be greatly appreciated...
I am using HTC one x, Evita, rooted, (not sure about supercid, I think so), s-on, hboot 1.14, and trwp 2.6+.
Even though I've had my phone a year, I'm still quite the noob when it comes to all this. Heavy forum reading...re-reading. I'm looking for any definitive help on getting me set up on the last steps here.
Sent from my One X using xda app-developers app

Newer builds do require an upgrade but it's not just the hboot that needs upgrading, it's the firmware as a whole which needs upgrading. The firmware does contain the hboot as a component and it is also usually identified by the hboot version number that it contains, I guess that's why there's a common misconception that it's just the hboot you need to upgrade.
Anyway, what you need to do is run the 3.18 RUU which will give you the 2.14 firmware modules. In order to run the RUU you'll first need s-off otherwise you'll end up with a brick. In order to get s-off you need to be sure you have SuperCID, without SuperCID the s-off process won't work. I know this all seems like a lot of work but it's a pretty easy process. Not having s-off at this stage is a stupid hindrance, without it you basically cannot flash any current ROM because they all require some kind of update (which itself requires s-off).
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita

timmaaa said:
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita
Click to expand...
Click to collapse
Done and title changed:good:

Thanks. Trying to find noob-proof instructions to accomplish all you mentioned. But I do appreciate being pointed in the right direction. Its good to know definitively what I need to do, now just gotta get down the how lol...
Sent from my One X using xda app-developers app

Ok, I'll make it a bit easier on you. The easiest way for you to get it done will be to follow these steps:
Flash a Sense 4 Android 4.1 ROM with root. It cannot be Sense 5 Android 4.2 though. You'll find plenty in our development section.
Determine whether you have SuperCID or not. Boot into bootloader and connect to your PC then issue this fastboot command:
Code:
fastboot oem readcid
If it shows up as 11111111 or 22222222 you have SuperCID and can continue to the s-off step. If it shows up as anything else you don't have SuperCID, in that case you van use this method to obtain SuperCID:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can get s-off by following this guide:
http://forum.xda-developers.com/showthread.php?t=2155071
So now you should have s-off, which means you can run the 3.18 RUU. You'll find it here:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
All you need to do is connect your phone to your PC, run the RUU exe program and follow a few prompts. Make sure no other programs are running and make sure screen saver/hibernation is turned off. Also make sure HTC Sync is uninstalled (leave divers installed) because it gets in the way.
When the RUU is complete you will have a stock ROM and stock recovery on your phone (your bootloader will remain unlocked and you'll still have s-off though) so you'll need to flash TWRP recovery again. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash any aosp ROM you want.
Sent from my Evita

Thanks...
Thanks for all the help. I was SuperCID, I achieved S-Off, i think. It says s-off on bootloader, but when I was entering the final 3 commands, the second one said error, I resubmitted it, and it went thru. Now it says S-Off. So is everything cool there?
I am a little concerned as to how terrible sounding running the RUU 3.18 can be. Am I cool to go now with no problems forseen?
Thanks for your responses btw. Very Helpful
Also, do I connect to PC in bootloader, or up and running rom, while running RUU?

If you are s-off running the ruu is entirely safe
Sent from my VENOMized HoxL

Everything went smooth today. I am running s-off, and hboot 2.14. Instructions worked perfectly. Thanks to everyone that helped me.
Sent from my One X using xda app-developers app

:thumbup:
Sent from my Evita

[Q] Brick or not?

HI all,
I tried to flashed the RUU but it seems that the version I flashed was lower than the one I had.
Now the screen is just black and I can not use the power + down vol to get to fastboot at all.
it will be greatly appreciated if I can get some guidance to get to the fastboot.
Cheers

What exactly did you flash? What does the phone show up on windows as? Does charge light come on when plugged into wall? Did the ruu complete? s-on or s-off?
You really didn't give much info.
Sent from my iPhone using Tapatalk

apology - duplicate post

bricked
thanks you for the response.
sorry I was not sure what info to give.
I was trying to flash RUU asia HK because I originally from STOCK turge but everytime I have a conversation my phone keep shuting down.
so I did (quoting from the instruction page):
Download HTC One X Stock Recovery
Download correct HTC One X boot.img and RUU based on CID. Download CID Getter from Google Play Store and run it, it will show your CID.
For this case, cidnum is HTC_044. The correct RUU is X.XX.707.X. Make sure you have downloaded the correct RUU.
Extract Fastboot.zip into a new folder, renamed the folder to Fastboot. Recommended to extract the folder to drive.
Copy and paste the downloaded stock recovery img and boot img into Fastboot folder.
Boot HTC One X into fastboot mode by press and hold Volume Down + Power button.
Connect your phone to the computer via USB cable.
At your computer, open up Command Prompt windows. (To OpenCommand Prompt –> Windows Logo–> Type CMD in search box –>Enter)
Type fastboot flash recovery endeavoru_recovery_signed.img , followed by fastboot reboot-bootloader and fastboot erase cache.
Once you flashed the stock recovery, continue to flash boot.img to your phone. Type fastboot flash boot boot.img, followed by fastboot reboot-bootloader and fastboot erase cache.
Now, relock the bootloader by typing fastboot oem lock, followed by fastboot reboot-bootloader and fastboot erase cache.
Your phone will restart after you have relock the bootloader.
Boot into Fastboot mode.
Double click the RUU, follow the updater instruction.
Wait the sending file to your phone, it normally takes 5-6 minutes.
Once the installation/update completes, your phone will automatically reboot.
when I last look at the details My CID is still 11111111 but status "RELOCKED" - it says also "EVITA PVT SHIP S-OFF RL"
HBOOT 2.14.0000
does this mean that I can safely run RUU:
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.7z
If there still more things to do, would you kindly direct me to the correct link to follow.
THank you

Never mind, didn't read properly. Will edit and repost.
Sent from my Evita
---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------
Your first problem is that you're flashing things that aren't intended for your device. The recovery you flashed is for the Endeavoru, you have the Evita. The second problem is it looks like you're getting your information from the wrong place, to go back to stock you don't need to flash a recovery or a boot.img, all you need to do is flash the right RUU for your device. What RUU did you already run? I need the exact filename. Does your phone power on at all? Can you reach the bootloader?
Sent from my Evita
---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------
I see you're looking at all kinds of different threads at the moment, that isn't going to help because I don't think you know exactly what you're doing, you don't know what you've done, and you don't know how to recover from it. Your best bet is to stay in this thread and I'll try to help you work out what's gone wrong.
Sent from my Evita

RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers

ardabelati said:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers
Click to expand...
Click to collapse
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!

You got seriously lucky. You ran an RUU intended for the HTC One X (codename Endeavoru), you don't have that phone. You have the HTC One XL / at&t One X (codename Evita), they're completely different phones. Note how the first RUU you ran has Endeavoru in the filename, that's bad, really bad, don't ever flash anything that doesn't have the Evita codename within the filename. If it has Evita in the filename it's for your phone, if it has anything else don't touch it, burn it, run away. Like I said, you're incredibly lucky your phone isn't bricked right now.
I can only assume that you're a bit confused and have been hopping between the two forums for these phones. In future stay within this device forum that you're posting in now, don't ever go anywhere else. You don't even need to visit other websites because, seriously, everything you'll ever need is right here within this device forum. Plus other sites don't properly distinguish between the models which causes confusion.
Anyway. The second RUU that you've listed there is perfectly fine for your phone. I can't guarantee that it's going to work though because previously running the wrong RUU could have really messed things up on your phone. But your only hope is to cross your fingers and run it now. Let me know how it all goes.
Sent from my Evita
---------- Post added 28th November 2013 at 12:12 AM ---------- Previous post was 27th November 2013 at 11:49 PM ----------
ndmuni said:
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!
Click to expand...
Click to collapse
What are you talking about? He doesn't need to use an RUU with the same radio/baseband that's currently on his device, that's just wrong. Firstly the idea of an RUU is to update your device, therefore traditionally you'd be updating to a newer radio version than the one that's currently installed. With s-on you can only run an RUU that contains a firmware version that's equal to or greater than your current firmware. This user has s-off though so he can run any RUU that he wants to, including earlier ones (RUU'ing backwards). I don't know where you got the idea that you need to run an RUU with the same radio as your existing radio but it's just plain wrong, and you really shouldn't be telling people that.
Sent from my Evita

ndmuni said:
U should download one that has the same radio as yrs
Click to expand...
Click to collapse
False. With s-on, you can only run RUUs for your CID, and with the same or latter hboot and firmware number. So if you were having trouble flashing an RUU, its probably because you were s-on and trying to either flash another carrier's RUU, or an older version.
The OP is s-off, so therefore all security checks are off. He can flash the RUU for any carrier, any version. As long as its meant for our device (EVITA), of course.

Hi guys
Thank you for all the guidance.
I got the 4.1.1 on my phone now and phone is use-able. I can not thank you guys enough for the help.
After i finished RUU flash the phone detected the new firmware update. When i dowloaded and tried to update, it says that the phone has been modified and they can not run/install the update. When i checked my boot it shows :
"relocked"
cid is still 111111.
Evita pvt ship s-off RL
HBOOT: 2.14
radio : 0.23a.32.09.29
Do i need to do more installation before my phone can get the update from HTC like the one coming out from the factory?
Cheers.
Arda
Sent from my HTC One XL using Tapatalk

You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita

timmaaa said:
You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita
Click to expand...
Click to collapse
I searching in the forum about changing CID. But it seems that is all about how to change CID to 111111. Is there any tutorial to revert back to original CID?
Do i need to sort out my s-off first before changing CID?
Thank you in advance.
Regards
Arda

You said in a previous post that you're s-off. So are you s-off or s-on? Please boot into bootloader and post your bootloader details again.
Sent from my Evita

Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated.
Cheers

All you need to do is issue a fastboot command:
Code:
fastboot oem writecid xxxxxxxx
The x's represent the new CID.
Sent from my Evita

Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated. I have attached the screen shot
Cheers

I did :
fastboot oem writecid 622 but it came back with ....INFOfail: [writecid] invalid CID
I flashed the RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe
was the 622 number incorrect?
cheers

No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita

timmaaa said:
No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita
Click to expand...
Click to collapse
Hi Timmaa
My phone is HTC ONE XLTE
I use CID Getter and it came up with HTC__622, so I entered that into the fastboot command and it changed my CID but when I try to flash the new update downloaded directly through the phone it came up with the messsage below after verifying the phone.
not sure why.....( pls see attached)

So you ran the RUU.exe? You didn't extract it or anything? What have you done to the phone since then?
Sent from my Evita