yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It could be a hardware fault. If you want to do some more testing you could run an RUU which will take the phone back to stock. Once the RUU is finished, boot the phone and test the speakers for a day or two. If the problem persists you're most likely experiencing a hardware fault.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] fanaticprakash:
i have this problem from the begining ,taught it was a heanphones problem not anymore.

is it a severe problem bro?

Is there any app could resolve this issue?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The severity of the problem is highly subjective, it's only as severe as much as it annoys you. I doubt there's an app that would fix it, but I'd suggest running the RUU to see if that helps.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Hey timmaaa, as you know I installed BM 3.5 with your help yesterday.

When installing, I chose the Default settings option but saw there's an Advanced option where you can customize to your liking. I've got some questions based on that:

- Is there any way for me to see all the different settings the Default option made? I saw a screenshot in a different thread where someone was looking at their CPU settings details, but I don't believe I can access that screen on mine (think I've looked everywhere). Do I need a separate app to see those settings by chance?

- Is there an ideal combination of settings for BM 3.5 that you can recommend which I could then apply myself using the Advanced setup option? I've browsed around in that Advanced option and see all sorts of settings where you can set min and max speeds for a wide range of things. Just interested to know whether there's any specific settings within there that may be better than the Default package.

- How do I active the 'swipe to unsleep' feature that I believe BM 3.5 makes possible? Currently I still have to hit the top power button to get it to wake up. Would love to be able to swipe instead.

I was thinking about posting this in the BM kernel thread, but figured I'd go directly to you instead (hope that's ok?). Thanks again.
[AT&T, Rogers HTC One X, Telstra One XL] MosesTheTool:
Brightstar US hboot 2.14 - how do i S-OFF?

Hi,

I bought this Brightstar US Evita HTC ONE XL, and I unlocked bootloader through HTCDEV and installed TWRP, but i am not sure how to update to an HBOOT that is supported in one of the S-OFF threads (such as 2.20), I managed to Install ViperXL on the phone, and now it's 4.2.2 (ViperXL 4.2), I am unsure how to continue to gain S-OFF

The phone came with 4.1.1

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Go to the Rumrunner site to get s-off. There is no such thing as a 2.20 hboot, there is a 2.20 software version though. What are your bootloader details?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Download an app called Trickster Mod from the Play Store, it will allow you to tweak your kernel settings. If you selected certain options (overclock, s2w, bln) during the kernel install you will be able to enable those options using that app. If you didn't select those options during the install you can just run the install again and select them. You're more than welcome to ask anything you like in this thread, that's what it's here for. You'll probably get a faster response too.

There aren't really an ideal set of settings as such, every single one of these phones is just a little bit different and therefore can handle different clock speeds. It's really trial and error, set it up then test with a benchmark app like Antutu. Keep setting your clock speed higher each time until you reach the point at which the performance degrades. Of course, overclocking isn't for everyone, and it does decrease the overall life of your CPU. Plus, the performance gains aren't all that great anyway.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] MosesTheTool:
Ok..

Bootloader details:

*** TAMPERED ***

*** UNLOCKED ***

EVITA PVT SHIP S-ON RL

HBOOT-2.18.0000

RADIO-1.34a.32.45.21

OpenDSP-v33.1.0.45.1128

eMMC-boot

Dec 2 2013,00:04:37:-1

I flashed a Firmware.zip from latest Brithtstar OTA before flashing ViperXL, my HBOOT was 2.14, but then ViperXL just bootlooped so i restored backup from TWRP, not sure if the Hboot got 2.18 from ViperXL or from the firmware upadate.

I tried Rumrunner, it didn't do anything (went through all the process)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's impossible for a ROM to change your firmware, so the hboot was changed during the forward update. What do you mean Rumrunner didn't do anything? You need to be as specific and detailed as possible when asking for help.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] MosesTheTool:
Rumrunner did it's process, it checked bootloader and then checked ADB(restarted a couple times), and then it just said "press anything to exit",

after that i checked bootloader and it was still S-ON

Update 02-03-2014:

I tried running Rumrunner again now with ViperXL as my Rom, and this is what i got:
[AT&T, Rogers HTC One X, Telstra One XL] badwiring:
Totally messed up HTC One XL

Hi, I've been searching and fighting with this for hours, can anyone suggest an approach?

I have an HTC One XL. I tried installing the Viper ROM which began to install, got stuck at 0%, then appeared to install, and that's the last time I was able to use the phone.

It wasn't until after hours of searching that I even discovered that both the X and the XL were called "evita," if that's even correct. It was sold as an HTC One X, but I don't see anything anywhere that identifies it as one or the other. It's labeled "at&t" at the top.

I've flashed a number of recoveries. The only one that I can get into at all is CM 6.0.4.6. TWRP (2.3.3.1 and the latest 2.6.3 occasionally show me a logo, but usually I'm back to the "HTC quietly brilliant" bootloop.

But I have no idea at this point how to install any ROM. I'm aware of only two options:

Install zip from /storage/sdcard0 - can't mount /storage/sdcard0

Install zip from sideload - cant find device. (I've installed the HTC sync application and a 15-second android drivers toolkit and two other flashing tools.)

The phone was rooted, unlocked, s-off. Can anyone suggest a next step? Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You could try Rumrunner while on the Kickdroid ROM, I've seen multiple people succeed that way.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The HTC One XL and the at&t One X are both codenamed Evita, but the HTC One X is codenamed Endeavoru. It's very important that you don't mix them up because software/firmware from the HTC One X Endeavoru is not compatible with our device and can brick it if flashed. No idea why at&t decided to incorrectly name the device as the One X, it's really the One XL, and has done nothing but cause confusion.

Anyway, where did you download Viper from and what is the exact filename? And where did you download the recoveries from? What method did you use to install the recoveries?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] badwiring:
I downloaded from the goo.im link in the 2nd post in this thread: http://xdaforums.com/showthread.php?t=2334294

The file name is ViperOne_5.0.0.zip.

I got the first recovery from here. http://teamw.in/project/twrp2/99

I also tried the recovery from the ViperOne .zip.

Right now the CM that's working is from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.6-evita.img

I flashed the recoveries by pasting them into the HTC Sync folder of the HTC Sync Manager application (where fastboot.exe is located) and flashing them via "fastboot flash recovery boot.img." For convenience I save each recovery in a folder, name the folder, and rename the file to boot.img.

Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Well, you're incredibly lucky that you don't have a bricked phone right now. Can you see the problem with that Viper ROM? There's a clue in the name, and in the device section from where you downloaded it. You downloaded and installed (well, attempted to) a version of Viper that isn't even for our phone, the version you linked to is for the HTC One. It looks as if you're searching all over the place for ROMs which is a sure fire way to destroy your device. Our device forum main page is here:

http://xdaforums.com/one-x-att

Bookmark that page. Do not ever stray from this device forum, nothing outside of it is compatible with our device and everything outside of it has the potential to brick your phone (with the exception of apps and some mods).

Why are you renaming the recoveries to "boot.img"? What gave you that idea? Do you know what a boot.img is? A recovery and a boot.img are very, very different things, and naming them as each other is very bad practice. If you accidentally flash a recovery to the boot partition you'll end up with a device that can never boot again.

I suggest you use TWRP instead of CWM recovery, it's much better. 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

Once that's done, install a ROM that's meant for our device and your should be fine. Before you do anything though, you should read the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] badwiring:
I performed these steps. When I reboot into recovery the initial TWRP screen appears for a few moments but then the phone reboots and goes back into the bootloop.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
There's no telling what you've done to the device to cause these issues you're having, you've made several major errors. You mentioned earlier that the phone is s-off, are you certain? If so I'd suggest attempting to run an RUU which will hopefully fix the partitions that are probably borked. You should only attempt this if you can get the phone to stay in fastboot mode.

PS. I did ask several questions in my post before. Answering those questions would beneficial to you.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] trouty:
noticed the HTC One has an IR blaster. which i assume our phone does too, or do we simply have a proximity sensor? bcuz mines is used for my gravity screen app to turn on and off my screen. used 2 do the same with my Galaxy S4. havent seen an app for it tho. is it possible? to get IR blaster features on our One X?
[AT&T, Rogers HTC One X, Telstra One XL] MosesTheTool:
I installed Kickdroid and tried Rumrunner and it gave me this:

This is my devices GETVARALL:

I appreciate any kind of help, i'm stuck
[AT&T, Rogers HTC One X, Telstra One XL] badwiring:
How does one determine which RUU to use? I found a post in another forum where it appears you helped someone in a very similar state restore the same phone. (Assuming it's you because it's the same name and image.) Here's the exact information displayed. It doesn't say "tampered."

****Unlocked****

EVITA PVT SHIP S-OFF RL

CID- 11111111

HBOOT- 2.15.0000

RADIO- 1.31a.32.45.16_2

OpenDSP-v33.1.0.45.1128

eMMC-boot

August 14, 2013, 16:02:22:9155

Thanks (it doesn't say "Thanks" - that's me.)
[AT&T, Rogers HTC One X, Telstra One XL] badwiring:
I used the AT&T 5.18.502.1 RUU - link posted here, #15. http://xdaforums.com/showthread.php?t=2593037&page=2

Then

I confirmed that the phone booted without issue

flashed the TWRP 2.6.3.0 recovery you had posted in #938 via fastboot

cleared the cache

Rebooted again, everything is still good

Copied the AICP 2.0 ROM zip to my sdcard from my computer

Installed the ROM from recovery

Wiped dalvik cache

Rebooted, AICP loaded, warned that my data was inconsistent

Rebooted back to recovery, performed wipe/factory reset

Rebooted again, AICP now works perfectly.

I'm not entirely unfamiliar with all of it. I probably had to restore my Xperia Tablet Z and start all over a dozen times in the learning process, and I installed AOKP on my wife's Nexus 7.

The hardest part about learning was that most "step-by-step" descriptions usually skipped over something. Like "flash a recovery" would be a step by itself without explanation. In this case I was thrown off by the names, which are a little ambiguous. And it doesn't help that the phone itself doesn't visibly identify itself.

But that's half the fun. It's working now. Thanks for steering me the right way.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The IR blaster is nothing like a proximity sensor, it's used so you can use the phone as a TV remote. Our phone does not have one so we can't have those features.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's entirely possible that because you've somehow upgraded your firmware there is some kind of protection which is stopping you from getting s-off. If this is the case, which is very possible, there's nothing I can say to help you.

PS. You should remove your IMEI from your post, never post your IMEI publicly.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The first time you flashed AICP it looks like you forgot to perform a wipe, you need to perform a full wipe every time you flash a new ROM. But it looks like you've solved your problem, which is excellent. I'd suggest you still read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] MosesTheTool:
Ok thanks anyway,

I am also able to flash Firmware through rebootRUU, i thought that is only possible with S-OFF.

last question,

I need to update to 4.4.2 software, what would be the steps?

last time i did this i ended up not having reception and having random boots.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It should only be possible with s-off. All you need to install KitKat ROMs is the unofficial modified TWRP 2.6.3.0 from our Original Android Development section.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] trouty:
is there a google play edition rom for our device by any chance?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Google Play Edition basically just means aosp. There are several aosp ROMs available in our Original Android Development section.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
I went to flash BM 3.5 again so I could re-install this time with Custom settings (instead of Default). I adjusted all of the individual settings options (clock speeds) to medium instead of the Default lowest settings. Then wiped cache partition and rebooted. When I tried to reboot, it got stuck on the initial HTC white boot up screen and stayed like that for at least 10 mins. At which point, I went back to the bootloader screen and tried flashing it again after making the same adjustments in Customized. Each time I did this it got stuck on that initial HTC bootup screen. It didn't bootloop, rather just stayed on the white HTC screen and the device got pretty warm.

Eventually I went back to the bootloader screen and tried installing BM 3.5 again this time with just the Default option like I successfully did prior. I just wanted to get it back to where it was before I tried re-installing with Custom settings. And now it's stuck on the HTC screen and I can't get even get it to boot with default settings.

- Is this uncommon? Does rebooting sometimes take a long time to do, especially if you're trying to customize install settings? If so, how long? 30 mins? Longer?

- Since I can't get it to boot now even after trying to install with Default settings again, is there any other option for me to try in bootloader Recovery?
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Update: The battery eventually died after being stuck on the HTC screen for about an hour and still not being able to boot.

After charging it for a bit, I tried reinstalling BM 3.5 again with Default settings and then rebooting with no success. Stuck at same white HTC screen. Then I selected "wipe dalvik cache" within the Advanced option. I thought this might help since I remembered in other threads how people were told to do that after installing other things like ROMs. Now I think it might've caused a different problem, but can't say for sure.

Now when I try installing BM again and select "install zip", then "choose zip from/storage/sdcard0" it gives me the message "E: Can't mount/storage/sdcard0"

- What does that mean and I assume it needs to be fixed ("remounted"?) before I can try reinstalling BM again?

- I see an option for "mounts and storage".. do I need to go into there and do something?

I can still currently access bootloader and CWM, but that's it.

Any help would be much appreciated.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Beastmode has been known to be a bit temperamental on some devices, some devices just can't flash it sometimes for unknown reasons. It should never take longer than a few minutes to boot after flashing anything.

Is it possible that somewhere during your attempts to get the phone to boot you performed a factory reset from the bootloader?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
It definitely did not like installing with Customized settings (i.e. with customized CPU speeds). It wouldn't boot after many attempts at a customized setup. And it now won't boot at the Default settings option which I was at least able to do a couple days ago and have been using since without issue.

If by "factory reset from the bootloader", you mean from the white HTC screen itself - then no, absolutely not. The only option I ever select from there is Recovery. Then it always takes me to CWM.

Now, is it possible I accidentally hit factory reset from CWM? Perhaps, but doubtful since I've tried to be super careful from what I select from there. The only other selection I've intentionally made is to clear the davlik cache from the Advanced menu within CWM.

In summary: My phone currently won't boot and I can't try reinstalling BM because of the error message that the phone can't mount to the sdcard0.

- What are the steps (if possible) to get my sdcard mounted again from CWM? It seems like that would be the first thing I need to take care of? Or am I incorrect? Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Performing a factory reset from within recovery only erases the data partition and wouldn't cause the mounting issue you're currently experiencing. I'm unsure how to mount the sd card using CWM as I don't use that recovery, I'm not sure if that option even exists. Have a look through the menus and see if you can find anything, otherwise maybe flash TWRP recovery instead. Once you've figured your mount problem out you'll need to flash your ROM again to get it booting.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Yeah, I didn't do a factory reset within recovery.

There's an option "mounts and storage" within CWM. From there, when I select the option "mount/storage/sdcard0", it gives me the message "Error mounting/storage/sdcard0!".

In your FAQ thread, you touch on the mounting issue by saying..

Connect the phone to a Windows PC, open Device Manager. There you should have the option to format the SD memory. Format as FAT32, and this should fix the SD card corruption.

You can also use the wipe feature in TWRP 2.6 to wipe the sd card/internal storage and it should become usable again.

This is a bug within hboot, and factory resets should only be done in TWRP.

In CWM, there's a "format/storage/sdcard0" option. Under that option, here are the choices:

- default

- vfat

- exfat

- ntfs

- ext4

- ext3

- ext2

I realize this is CWM and not TWRP, but are any of these options the same as "FAT32" like I would see in TWRP? If so, which one?

My hope is that one of these formatting options would get my sdcard at least formatted correctly and mounted again? Or is formatting something totally different and unrelated from mounting?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Formatting is completely different from mounting. Formatting a card or drive removes all existing data and returns it to a blank state, ready to be written to. That section in the FAQ thread relates to situations where the sd card has become corrupted via a factory reset in bootloader. Your card might be corrupted which might be what's causing it to not mount properly. I'd flash TWRP 2.6 or above and see if it'll mount using that recovery.

If it does turn out that you need to format your card, the only format type you should use is fat32, and I don't see it in that list. It might be default but there's no way to know. You can use the advanced wipe menu in TWRP to wipe the sd card, which should format it.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
I have no idea if the sdcard needs to be formatted or not, only thing I know is that it's apparently not mounted anymore. I can't select the BM zip file that's been on the sdcard for the prior 3 days - who knows if it's still on there or not.

The problem is that I can't flash TWRP to the phone since it can't boot. And I can't access the sdcard because it's not mounted any longer. And it perhaps may not be formatted correctly any longer. So even if I could somehow add TWRP onto the sdcard, my phone wouldn't be able to read/see it. Yet apparently I can't move forward with anything until TWRP is somehow on my phone. So it seems like a circular problem with no definitive starting point which needs to be fixed.

All I have at my disposal right now is CWM and the FAQ says CWM version 6.0.2.8b is ok for this phone. I guess that's why I still had hope that I could fix my phone with CWM. That, and the fact that I can't get TWRP on my phone and it won't boot.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You can get TWRP on your phone. You don't need the phone to boot to flash a recovery, it doesn't need to go on the sd card at all, you use fastboot. All you need to do is put the phone into fastboot mode and use a fastboot command to flash it. It's explained in detail in my How-To Guide For Beginners thread, the link is in my signature.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You haven't entered the command correctly, you must include the file extension (.img) in the command.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
I tried downloading the unofficial modified version of TWRP onto my PC from here:

http://www.androidfilehost.com/?fid=23252070760973615

It says the disk image file is corrupted once I try installing it. Can you recommend a better link?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm pretty sure that is the only place, did you check the md5?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
What's the md5? There wasn't any check box to select on that page - just the download link to click on.

I just downloaded the file to my PC and then when I double clicked to open it, it immediately gave me that error msg. I've subsequently deleted it from my PC and re-downloaded it again, but I keep getting the same error msg.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I don't think there's anything wrong with the file, you aren't meant to try to open it on your PC. Did you read the directions in my guide thread as I suggested? It doesn't say anything about double clicking the file. Either way you need to check the md5 of anything before you flash it.

An md5 is like a digital fingerprint of a file, it is listed on the download page. Once you've downloaded the file you use an md5 checking app to confirm that the md5 of the file you downloaded matches the original md5 on the download page. If it matches you're fine, if it doesn't match it means the file has become corrupted during the download.

Sent from my Evita