yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Please read the OP and provide the information detailed there.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ledthezeppelin:
All set. Thanks @timmaaa @redpoint73

I can't thank you guys, [MENTION=4153349]timmaaa[/MENTION] and [MENTION=660462]redpoint73[/MENTION] enough! I'm finally all set with the phone!

I'll try to be helpful for any new people who might face the same problem I had.

So I wasn't able to flash a stock rom because of an older version of TWRP. I tried to update the recovery, but I couldn't get fastboot to work.

And here's a little tip that I learned the hard way: if you have adb and fastboot installed, and yet you still cant see devices, UPGRADE DRIVERS, and here comes the important part. After updating drivers, RESTART!!!!!!!!! That's where I was having all the issues! After that, I easily upgraded TWRP, installed the rom and since I was S-on, flashed boot.img and now I'm all set!

Thank you guys so much!

Peace!
[AT&T, Rogers HTC One X, Telstra One XL] stormshard:
Hi timmaaa , you said after i get s-off i can check out whats going wrong with my front camera.

So i had the front camera ca. half year ago , then there was a patch by htc and after that patch it was like "removed" naturally not the hardware itself but if you check the hardware information there is no secondary camera , and that is really strange
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yes now that you have s-off we can at least try something. This might sound strange, but you need to return the phone to a stock state via the 3.18 RUU. Doing this will bring everything on your device into line, into a state that I know the front camera usually works on. If the problem continues we can safely assume that you have a hardware problem. If the problem stops we'll know it was software/firmware related. Your unlocked bootloader and s-off status will survive the process, so once you've finished testing you just need to install TWRP again then you can flash a ROM of your choice (or restore a TWRP backup previously made).

Here's what you need to do:

Download the 3.18 RUU from here:

http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe

Connect your phone in fastboot mode and run the RUU.exe in Windows, then just follow the prompts, it's as simple as that. Just make sure no other programs are running, make sure HTC Sync Manager is uninstalled (but leave drivers installed), and make sure screen saver/hibernation is turned off.

The whole process takes about 10-20 minutes. Once it's finished boot up your phone and see if you can use the front camera.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] stormshard:
I get an Error in the RUU ,

Erro[158]: Image error

the RUU cant update the android-phone

Get the right RUU and try again

That sounds strange , to understand that right This is RUU für HTC ONE XL and it still doesnt work

(i'm googling the error )
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You need to change to SuperCID first. You can do that with this fastboot command:

fastboot oem writecid 11111111

Now try the RUU again.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] stormshard:
My hardware is broken i think , exactly my frontcamera is dead. Already checked out how to open the phone but it looks like the camera is onboard , so its on a high risk to remove her and put a new one there without destroying something else. I think i will do nothing to change it , cause i have no more warranty to send it in and a new motherboard only for the frontcam that you use once in the month isnt worth.

Thank you timmaaa for your help all the time, it was really good to understand what you meant.

cya ,

stormshard

last question ^^ , is there any difference between ONE X and ONE XL , except "LTE" ?? specially for the software. I Checked the technical sheets and only the display is different

"tft -> super lcd2" and LTE -> no LTE , everything else is nearly the same. I just ask , cause i read here really often "my one x" and sometimes i am not sure if one x or one xl is meant^^
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Of course the camera is physically there, there was never any question of that. The question is whether it's faulty or not. Did you run the RUU?

There are major differences between the Evita and the Endeavoru, it isn't just the LTE. Our phone has a Qualcomm dual core CPU whereas the Endeavoru has an Nvidia quad core CPU. They also have completely different partition layouts. Absolutely none of the software for either device is compatible with the other because of these facts.

The reason some people refer to this phone as the One X is because of the north carriers. For some reason at&t and Rogers decided to incorrectly market the phone in north America as the One X instead of its true product name. My guess is so they could cash in on the hype surrounding the One X. All it has done is create confusion though.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] stormshard:
Yes i run the RUU successfully, everything is working but again no frontcamera listed in the hardware details , no chance to switch between main and front camera by useing cmaera settings or swipe over the camera screen.

I wont buy a new motherboard i think , and i dont think i can buy a front cam as single product ^^
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Well yeah unfortunately I think your front camera is physically not functional, that's a real shame.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] BenjaminSweden:
Phone stuck at HTC quiety brilliant

My phone is AT&T HTC One X ( 4.04 and 1.20 <--- taken from memory )

Is it possible to get the details about the bootloader without rebooting out of recovery (TWERP)? I just got there and because of my current situation I worry about leaving it.

I think I have no OS installed at the moment.

Used this guide to root my phone maybe that created a backup http://xdaforums.com/showthread.php?t=1952038

So I used the guide above to root my phone and then installed Twrp 2.3.10 and Superuser.

Now I was ready to just do the easy part of loading a rom. First I had to backup with recovery and that failed so I decided to try to flash the CM 10 anyways, I used this guide for the endearvoru http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru. And flashed my device using fastboot. The phone got stuck at loading screen.

So I followed some quick tips on the web wiping everything system, factory and cache then trying to install the Evita CM 10 and 4.4 gapps. Both of these failed in the Twrp recovery. This is where I am now.

I have hardly any knowledge about what I am doing I really just wanted to be able to share my hotspot on the bus this afternoon. :/

Any help would be greatly appreciated :)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Hmm, you're in a bit of a sticky situation. It looks like you know what you did wrong but I'll point it out just in case. You flashed a ROM that isn't meant for our device (the Endeavoru ROM). While our phone, the HTC One XL / at&t One X (Evita) and the HTC One X (Endeavoru) look similar and share similar naming they're very different internally. None of the software/firmware/radio/anything is compatible. The problem here is that flashing an Endeavoru ROM to an Evita can sometimes cause a brick.

When you say you flashed your device using fastboot what do you mean? You don't use fastboot to install a ROM. After installing the Endeavoru ROM (through recovery I'm guessing) did you try to boot the phone or did the install fail? Exactly what recovery version is installed on your device and where did you download it?

I need you to answer all of the above questions so I can get a better picture of your situation, that way helping you will be easier. Before you've answered those questions I wouldn't suggest booting out of TWRP just yet.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You need to unlock your bootloader, install a custom recovery, and get root first in order to get s-off. Click the compilation resource thread in my signature, navigate to the root section, and click on the 3.18 root method link. You need to follow the instructions there which will give you SuperCID, then you can go to htcdev.com to unlock your bootloader.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The first three issues while they seem to display different symptoms are one and the same. What is your current baseband? You'll find it listed as baseband in Settings>About Phone.

You can still flash KitKat ROMs with the updated firmware.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] info2shail2010:
1.31a.32.45.16_2_10.141.32.34aL

what Baseland is Actually is? and do i need to update it also?
[AT&T, Rogers HTC One X, Telstra One XL] BenjaminSweden:
Hi! Thanks for the quick reply I managed to boot into the bootloader again and this is my bootloader info in case it helps:

EVITA PVT SHIP S-ON RL

HBOOT-1.14.0002

RADIO-0.19as.32.09.11_2

OpenDSP-v29.1.0.45.0622

eMMC-boot

Jun 11 2012, 14:36:28

UNLOCKED

I am using Twrp 2.3.10 and I tried installing the cm10 from the zip with twrp recovery. However the install failed saying the M something (Checksum) didn't match. So then I read that you are supposed to open the zip and flash the boot.img instead with fastboot-mac. And that is what bricked the phone. Is there any way out of it. I read that I might need to format the phone using a pc.

Oh and I downloaded the recovery together with the rooting tools when I rooted the phone following a HTC One X rooting guide. Can't find the download now.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's the correct radio. In response to your earlier question, firmware does not equal radio. Firmware is a pretty ambiguous term and can mean different things.

Pretty much anything electronic these days will have firmware installed, including modern televisions, gaming consoles, hifi systems, even fridges. What firmware does on these devices can vary wildly, from a full operating system to rudimentary control systems.

On our phone though, a firmware package is usually made up of a hboot, a radio, and other modules. A radio is a one portion of the firmware which governs how every piece of wireless technology on the device works.

It might be worth flashing the firmware again just in case, and make sure you flash it twice as per the instructions. Here's a link to the thread where it's contained:

http://xdaforums.com/showthread.php?p=45122768

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Firstly, you didn't brick your phone, as long as the thing powers on at all it isn't bricked. Is there any reason in particular you wanted to install such an old ROM? Cm10 is a few Android versions old now that we're up to 4.4 KitKat. Before we go any further I need to know what kind of ROMs you plan on flashing.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] info2shail2010:
whats the difference between hboot and firmware...?

how do i know which version of hboot i have?

is the 2.15 firmware latest?

i want to know bcoz.. u told me that my firmware is updated and my baseland is also ok.. but still getting restarting problem...
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The hboot is another component of the firmware which is the first thing that runs when you turn on your phone, it basically initialises everything (hardware and software) when you boot.

Your hboot version is displayed in your bootloader. It should be 2.15 since flashing the firmware. It isn't the latest but the later ones are essentially the same so no need to upgrade any further.

I don't know why you're still getting reboots but I think flashing the firmware again is the first step.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] BenjaminSweden:
Thank you Timmaaa really kind of you to help me out. Actually I don't have much of a clue of what the difference is. My goal is to share my hotspot so that I can use my phone's 4g on my laptop while travelling. I guess my only worry about installing KitKat is that if my HTC One X might not be able to handle it. Which ROM are you using? And could you instruct me on how to install that?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Your phone can definitely handle KitKat. You've got a bit of work to do to update your phone before you can flash anything though. In order to do that you need s-off first. I think the way to do this is to follow these steps:

1. Download a Sense 5 ROM like Kickdroid from our Android Development section. Use TWRP to install it. You're only using this ROM temporarily in order to get s-off. You might end up liking it and want to keep it though, but it'll still require some updating because it'll suffer random reboots and signal losses otherwise.

2. Go to the Rumrunner site and follow the steps there to get s-off.

3. Run the 3.18 RUU. This step requires a Windows machine. This returns your phone to a stock configuration but it's the update step so it's necessary. Your unlocked bootloader and s-off status will survive the process though.

At this point I need to know whether you still want to flash an aosp ROM or you want you stay with a Sense ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That method gives temp root in order to obtain SuperCID on the device, it's only applicable to at&t model phones. Is your phone an at&t model? Also, can you please post your bootloader details?

Root isn't required to install a custom recovery, that's a common misconception. Once you have achieved SuperCID you need to go to htcdev.com to unlock your bootloader, this is all that's required to install a custom recovery.

If your phone isn't an at&t model though you do not need to achieve SuperCID first, you go straight to htcdev. If your phone isn't an at&t model you can achieve SuperCID at a later stage (after getting s-off) using a much easier method.

Once you have installed a custom recovery you can either install a root app (Superuser or SuperSU) to gain root, or install a rooted ROM.

If your phone is not an at&t model, at this point you can also use a fastboot command to get SuperCID. The command is:

fastboot oem writecid 11111111

You'll know you have SuperCID because if you have an at&t phone you would have had to go through the 3.18 root method before unlocking at htcdev. If it isn't an at&t phone you would have used the previously mentioned fastboot command to get SuperCID. Either way if you want to check you can use this fastboot command:

fastboot oem readcid

You will know you have root because you will have either installed a root app or a rooted ROM earlier. Root is only required for the s-off stage though, it isn't required to run the RUU. If you want to confirm that you have root before getting s-off just search for root checking apps on the Play Store.

If you have any further questions just ask me. I'd suggest you read my Evita FAQ and How-To Guide For Beginners threads, the links are in my signature. They contain some very valuable information.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Kenouno:
I can get response from ADB but when i typed that command i just getting "< waiting for device >". Should I put my phone in bootloader an select FASTBOOT there?

How i get out of FASTBOOT at my phone after reading the CID?

Sorry for asking so much... I just wanto to be sure (communications, drivers, etc) everything is working fine before proceed.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Boot your phone into the bootloader and connect the usb cable, it should now automatically display "fastboot usb" on the screen. Now can use fastboot commands. You can manually reboot the phone afterwards or use this fastboot command:

fastboot reboot

While you're there please post your bootloader details like I asked before. I also still need to know whether your phone is an at&t model or not. When requesting help on XDA please make sure you answer all questions that are asked of you, we ask them for a reason.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Kenouno:
Attached capture of my bootloader screen. This the info I get with "fastboot getvar all":

version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main: 3.18.502.6
version-misc: PVT SHIP S-ON
serialno:
imei:
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: CWS__001
battery-status: good
battery-voltage: 4085mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok, thanks. You do have an at&t phone. He's what you need to do:

1. Use the 3.18 root method to get SuperCID.

2. Go to htcdev.com and unlock your bootloader.

3. Install a custom recovery.

4. Install root via a root app, or install a rooted ROM.

5. Get s-off by either Facepalm S-off or Rumrunner S-off.

6. Flash the stock recovery again (if you can find it) or just run the 3.18 RUU to get it back.

7. At this point you can go back to the at&t update thread and install the official update.

You might decide that you want to ditch the idea of the at&t stock ROM and instead enjoy the many benefits that a custom ROM with root can offer. If this is the case forget about the last two steps and install a custom ROM instead.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] BenjaminSweden:
Excellent guide! I think a Sense ROM is safer but that is just me. Maybe you get more out of your phone using an AOSP but I don't really need it all I want is to share the hotspot and use facebook messenger :).

Anyway STEP 1: Tried it, doesn't work I get this message:

Any ideas on why this is? Got the same error when trying to install CM10. I just thought of it but could it be due to me having to ReZip the archive when I download the zipped ROM. My mac automatically unzips the archive when I download them :-/
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's a big problem, can you get your Mac to leave the zips intact upon download? That's essential.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Please be a bit more specific. What see you trying to achieve? What are your bootloader details?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] betocl2:
Thanks for your answer, i'm trying to flash CM 11, and i i've already update the HBOOT to 2.15, SuperCID, S-Off, etc. The Evita is on ViperXL 4.2.0 I think the firmware is 3.18 AT&T but i don't know how to look for that. The question: Is it absolutely necessary to do the RUU thing¿?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Please post your bootloader details as they appear in your bootloader screen. You say you updated your hboot, was it just the hboot or did you install the 2.15 firmware package? You also say you think you have the 3.18 firmware which contradicts having the 2.15 firmware installed.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] betocl2:
Sorry, this is the info in the bootloader.

About the firmware, when i tried to unlock/supercid/root the phone i found 2 guides, one for version AT&T 2.20 and another for version AT&T 3.18, i did it with AT&T 3.18, then flashed ViperXL 4.2.0 with Sense 5, then the phone was getting random reboots and bad wifi and data signal, so i updated the HBOOT to 2.15. Sorry, if i can't be very specific, english is not my native language
[AT&T, Rogers HTC One X, Telstra One XL] BenjaminSweden:
Thank you Timmaaa, it worked I got the KickDroid installed. I haven't done the other steps yet, but does it matter that the phone now gets stuck on the HTC One BeatsAudio screen?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok that's good, that's exactly what I needed to see. You actually upgraded your firmware after flashing Viper, not just the hboot. The hboot is just one component of the firmware package. It can be confusing because the firmware package is referred to by the hboot number contained within it.

Anyway, long story short, you don't need to run the 3.18 RUU. All you need to do in order to flash CM11 or any other KitKat ROM is the modified TWRP 2.6.3.0 recovery, you'll find it here:

Download the modified version of TWRP.2.6.3.0.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:

fastboot flash recovery "filename.img"

(the exact filename, minus the talking marks)

fastboot erase cache

fastboot reboot-bootloader

Now you can flash any KitKat ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Your still s-on so you need to flash the boot.img via fastboot. Tree are detailed instructions in my How-To Guide For Beginners thread in my signature.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Konatsu_M:
Hello guys, I'm sure you get this a lot but I'm trying to root my AT&T HTC One X running Android 4.1.1 with AT&T 3.18 and I've run into a bit of trouble with abd recognizing my phone. It just won't show up for me at all :/ I'm trying to do this without bothering people too much, but I just can't figure out what's going on :(

My phone used to show up in HTC manager, however some time after I tried using an out of date method (pretty much the first google result >.> , you can view it here: http://www.android.gs/how-to-root-att-htc-one-x-with-one-click-method/), HTC Sync stopped recognizing my phone, and later when I actually learned how to check abd devices, I found that nothing was showing up there. After that I tried to use the EZToolkit Advanced located here: http://xdaforums.com/showthread.php?t=2587677 . However since my phone didn't show up to abd, nothing worked. When I used motochopper in fastboot USB via that tool, some of the operations showed device not found, however apparently it did something, because it told me to press enter to continue, which did restart my phone. However I could not continue to the next step; it simply did not see my phone and sat there waiting for me to do something.

At that point I tried all sorts of things, trying the first step of using motochopper with HTC Sync installed or uninstalled, in the boot menu of the phone and in it's normal state, plugged into different USB locations of my laptop, USB debug on and off, uninstall reinstall HTC drivers, and lots of combinations of those things. Nothing seems to have an effect, I just can't get my phone recognized in anything but fastboot USB mode from the phone's boot menu. Something I noticed is that HTC Sync, if I leave it installed, starts up like it's supposed to by default when I plug in my phone, but then doesn't actually recognize my phone unless I'm in fastboot usb mode.

-AT&T HTC One X

-Bootloader details:

EVITA PVT SHIP S-ON RL

HBOOT-2.14. 0000

RADIO-0.24p.32.09.06

OpenDSP-v34.1.0.45.1219

eMMC-boot

-Kernel version:

3.4.10-g310e8f1

root@abm030 #1

SMP PREEMPT

Not sure my recovery, just the default one?

I'd like to avoid resetting my phone if at all possible. Also I'm not even sure I need to unlock the bootloader , all I really want to do with the root is use titanium backup and also be able to record my screen. Not sure I want to dive into custom ROMS, because as you can tell, I'm not the brightest and I'm probably missing some really simple thing somewhere :P

.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Unfortunately you have to unlock your bootloader to root your phone. Root requires a custom recovery, custom recovery requires an unlocked bootloader. First step is to completely uninstall HTC Sync Manager and the drivers. Uninstall adb/fastboot as well. Download the Android SDK and install adb/fastboot again from there. Hey the latest HTC Drivers from this thread and install them. Do not install HTC Sync Manager again, it can interfere with adb and fastboot.

Sent from my Evita