yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
This is actually my original intention, I don't want to have all the junk that comes from HTC and the one from AT&T.

Any recommendation to get something like the kitkat rom that is stable and reliable.

I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.

Really appreciate your help.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Best/recommended/favorite ROM discussions are not allowed on XDA. They are each good in their own way, and everyone has different preferences. Part of the fun of flashing custom ROMs is trying them out, to see what you like the best.

Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.

Bear in mind that KitKat means you will be on an AOSP ROM. Sense is limited to Jellybean, for now.

---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------

Feel free to click the "Thanks" button for any posts that you found helpful.
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
I will check the index of yours when I find it since I am always lost in the xda forum.

Sorry to ask for something not allowed in XDA, I will start looking for AOSP ROM since I want something like KitKat.

If we can forget about "recommendation/best ROM" will anyone can point me to where to find KitKat like ROM for my device or

give a list of names or links to threads in XDA. Or even the whole forum starting point for which i can find these type of ROMs

just to avoid bricking my device since it's S-On
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
What I was afraid of is happening, I run RUU 1.85 and I am right now passed 50 minute with the phone screen is black with HTC logo on it.

is this normal?

should I be doing anything? or just wait more or unplug the phone from the PC?
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
Guys I am running out of options or solutions.

Here is what I tried to do:

1- attempt to run RUU 1.85 and it took more than 50 minutes with no sign of progress so I unplugged my phone.

2- attempt to flash custom ROM, which are

cm-10.2.1-evita

cm-11-20131204-UNOFFICIAL-evita

pac_evita_4.4.Alpha-1_20140301-151438

full_evita-cfxe-OPENMASTER-20131005.070802

non of them flashed using openrecovery-twrp-2.6.0.0-evita

3- attempt to use different recovery and the clockworkmod version that works on my device is

recovery-clockwork-6.0.2.8-evita

but with this one, when trying to flash the above ROMs, I got this error

assert failed: getprop("ro.bootloader") == "2.14.0000" || getprop("ro.bootloader") == "2.15.0000"

(status 7(

Installation aborted.

I can understand that the error is because my HBOOT is 1.09.

Please help me out here. ahhhhh
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Why did you run the RUU after being told it was a step backwards and not needed? There's no point in asking for advice from experienced people if you're just going to ignore it. All you needed to do was flash a ROM. Flash TWRP recovery again. Flash a Sense ROM, get s-off, run the 3.18 RUU to update your firmware, flash the modified version of TWRP 2.6.3.0, flash a KitKat ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
I am very sorry, I didn't mean any disrespect to the experienced people in here. I thought that RUU is the Sense ROM.

Can you point me to one of the Sense ROM since I am obviously very novice and understand nothing about ROM and flashing.

Very sorry guys for causing all the trouble.

I will keep looking for what you called a Sense ROM until I hear from you or any other helpful expert.
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
YOU ARE THE BEST. :D

Thank you for being very helpful. I found the thread Jelly Bean Sense 4+ deo & odex by

I downloaded deodex-JB-Sense4+ ROM

I flashed it with TWRP 2.6.0.0

it worked.

I am so happy and so thankful to all the people who helped me out.

I will do the next steps you said and I will let you know.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok. An RUU is a recovery utility which is used to restore your phone, it flashes the ROM, recovery, and firmware components. A ROM is just the OS, that was what you were meant to flash. Anyway, it looks like you've achieved that now so that's good. You might want to take the time to do some research before going any further, it's crucial that you gain some knowledge, and to know what you're doing when it comes it modifying your device. Without the proper knowledge it's very easy to brick a device. You should start with the threads that I have in my signature, I think you'll find those very helpful.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
Yes, I think I might stick with the ROM I have now and delay the S-OFF for now.

I will have more time in the summer when out of school to read more and not brick the device.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Cool, the ROM that you're running should be perfectly fine with your current setup. If you want to flash a Sense 5 ROM or an aosp ROM there is some work you need to do.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I already linked you to my Index thread in post #14 above. The Index thread is also the top sticky post in the General subforum section.

All ROMs intended for our device on XDA are listed on my Index, and organized by Android version (KitKat, Jellybean, etc.) and AOSP vs. Sense based.

timmaaa already linked you to the "whole forum" (EVITA) in post #6 above. The sections which contain ROMs are "Android Development' and "Original Android Development". Various other mods and tools can also be found in these sections. But my previously mentioned Index thread presents all of this in a much more organized manner.

---------- Post added at 09:46 AM ---------- Previous post was at 09:38 AM ----------

I see you are already back up and running. But for future reference, as timmaaa already covered, RUU returns you to stock OS, stock recovery, etc. Also, running the RUU requires the bootloader being relocked (so if you did not do so, that may be why it didn't run). This is contradictory to what you were trying to achieve (custom ROM) especially since you already went through the trouble of unlocking the bootloader again, and installing custom recovery.

RUU is an option to recover the phone if you have exhausted other options. But you still had plenty of options, so that is why we recommended otherwise.
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
Guys, thanks again for all your support.

Is there an easy way to have superCID for my phone. Most of what I found was related to hboot higher than 1.09 which I have now.

Or, the threads talk about superCID to get the bootloader unlocked which I already have it unlocked!!!!

I don't want to try things myself without asking you, to avoid making another mess.

All I want to do is to get my HTC One X to a ROM that support Bluetooth Lowe Energy BLE

because I want to support Heart Rate monitoring from the Polar sensor that uses smart Bluetooth.

That's why I wanted KitKat ROM or minimum 4.3 JellyBeans

Is this possible?

As in the AT&T, Rogers HTC One X forum thread [S-Off] Facepalm S-Off for HTC One XL

that points to thread	[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit

The information there does not work for my case since I have 1.09

So what should I do just to get superCID?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You can get SuperCID through a couple of methods. As long as you have root you can use the hex edit method. Or you can get s-off via Rumrunner S-off, and then manually change your CID with this fastboot command:

fastboot oem writecid 11111111

I think essentially what you really need though is s-off. If you want to upgrade to 4.3 or later you need to upgrade your firmware via the 3.18 RUU, which requires s-off.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] shakash3obd:
Sorry i didn't reply earlier.

But last night before you point me to these other methods to get the superCID, I found the hex edit method and tried it.

It worked great. Now I have superCID + HBOOT 2.14 + S-OFF

I tried 2 ROMs and with each one, for some reasons, have some issue so I turned to CM11 and it works like a charm :D

My only issue with CM11 is that I was not able to find settings for the Developers to turn on "Enable debugging mod"

I already posted this question in the thread [ROM][4.4.2][NIGHTLIES] CyanogenMod 11.0 for AT&T HTC One XL - evita

Hopefully someone will either tell me what I am doing wrong or maybe the developers of CM11 left it out and they will add it later on.

You don't know guys how happy I am right now that I got what I wanted after all the mistakes I made along the way.

Great jobs guys and members of XDA. Best forum for developers. I am a Computer Science student ( Graduate ) but at school they teach us nothing that is related to the real stuff like what the senior developers in here are doing. I hope in one day I can learn to do what they can.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
This is not an "issue" with CM11. Developer options are hidden as default in KitKat.

Go to Settings > About Phone and then tap on ‘Build Number’ 7 times.
[Android Q&A, Help & Troubleshooting] raphzel:
Hi,

I'm French user, so sorry for my bad english...

I have big problem with my huawei Honor 3X. it remains turn off because I I did something wrong in SP FLASHER TOOLS...

I tried to flash it with SP FLASHER (I have drivers and the good recovery) but I don't HAVE the complete ROM with following files :

PRELOADER

MBM

ERB1

UBOOT

BOOTING

RECOVERY (I have already this files)

SEC_RO

LOGO

ERB2

ANDROID

CUST

CACHE

USRDATA

I think I have to transfert all this files in my ROM to have phone alive ...

Somebody can help me please ???????????

I don't have phone ANYMORE and I need HELP !

Thanks a lot !!!!!!
[Android Q&A, Help & Troubleshooting] xjarl:
You need download a ROM with these files. Not the official ROM.
[Android Q&A, Help & Troubleshooting] xtc_inside32:
I have the same problem.The phone is completly black.How do you fixed?

---------- Post added at 09:25 PM ---------- Previous post was at 09:17 PM ----------

I have the same problem.The phone is completly black.How do you fixed?
[Android Q&A, Help & Troubleshooting] mmmnnn111:
www needrom com/phone-roms/huawei/glory-3-huawei
[Android Q&A, Help & Troubleshooting] Griso502:
Honor 3X to buy/sell

Hello Guys,

did u solve the problem?

If not, anyone of you want to sell his phone?

Mine has broken lcd and power button....So I'm searching for replacements.

In any case, Mother board and all other parts are perfectly working, so in case you need motherboard, I can sell mine.

Just pm me.

Regards.
[Android Q&A, Help & Troubleshooting] xjarl:
Complete black? Can you get into recovery?

If you can get into recovery, Its easy to save your phone.

---------- Post added at 07:04 PM ---------- Previous post was at 06:41 PM ----------

An original Honor 3X screen for replacement in this store oiostore $76. You need not buy a whole phone...
[Android Q&A, Help & Troubleshooting] xtc_inside32:
If someone need help when the phone is completly dead or problem with driver vcom on windows x64,here is the tutorial in chinese site(use google translate)

1. http://tieba.baidu.com/p/3006247438

or

2.http://mp.weixin.qq.com/s?__biz=MjM...&idx=1&sn=1972da6d93489d2912df57b5b83a0b63#rd
[Android Q&A, Help & Troubleshooting] Mchael T.:
Digitizer/LCD for $58.95 to $76.00

http://www.ebay.ca/itm/New-Black-To...e_Replacement_Parts_Tools&hash=item3f35f840cb

http://www.oiostore.com/huawei-hono...ement-p-304.html?cPath=90_88_134#.U8PmnLHCcto

Power Button with Flex Ribbon Cable is only $4.........universal part number.
[Android Q&A, Help & Troubleshooting] Griso502:
Done :)

Hello, I've fixed using spare parts from oiostore! Thx
[Android Q&A, Help & Troubleshooting] ma7moud17:
Download the stock recovery then flash it via sp flashtool then download stock ROM and put it in SD card /dload then update through recovery
[Galaxy S II Q&A, Help & Troubleshooting] Aello:
I did some searching but, though there are plenty of similar (very) old posts, they either have no solution or the issue does not match mine.

I (obviously) own an i9100 (used, which came with the first two batteries that I will list in a moment), with AOSB KK and stock kernel, no battery regulation apps.

I also own 3 (three) Samsung original batteries: an old 2011-dated, a mid-new 2013-dated, a brand new 2014-dated.

I bought the last one because it felt to me like the first one could use some rest, its average life time IS 8 hrs usage + 7 deep sleep.

Before I bought the new one, I firstly tried the mid one (2013), but experienced the following: average life time 5 hrs usage + shutdown when battery still signs ~20%, no way to turn it back on but to plug in the charger and wait 10-15 minutes. This ALWAYS happens, it's not a matter of one-two days usage, I've been trying this battery for some weeks (not continuously, since its behaviour is very annoying) switching different kernels and roms, no way to make it work properly.

So I said "ok, guess it is faulty, I will stick to the old one unitll I decide to actually buy a brand new one", which I did, 4 days ago.

Guess what, same behaviour as the 2013 one, no difference; same life time, same death at ~20%.

2 faulty batteries out of 3? Doesn't sound possible to me.

Phone issue? Then why does the old 2011 one works correctly, with normal death at 0%?
[Galaxy S II Q&A, Help & Troubleshooting] MauFerrusca:
Hi, I'm also having a few issues with my battery now, but mine is the original one, so I've used it for about one and half years.

Have you seen/used this kind of battery? The only think I'm interested in is the higher ampere-hour capacity, but I'm a bit hesitant about the brand.

http://www.ebay.com/itm/350791460553?ssPageName=STRK:MESINDXX:IT&_trksid=p3984.m1436.l2649
[Galaxy S II Q&A, Help & Troubleshooting] Aello:
No I bought only one original samsung (the other two came with the phone), though via ebay, so it COULD be fake...

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Q&A, Help & Troubleshooting] MauFerrusca:
There are some tempting things on ebay, but this one looks very dubious. The only interesting thing is the higher capacity and the low price.

http://www.ebay.com/itm/321327792803?ssPageName=STRK:MESINDXX:IT&_trksid=p3984.m1436.l2649
[Galaxy S II Q&A, Help & Troubleshooting] Aello:
No I highly discourage buying any of the golden ones, there are plenty of negative comments about them around the net, with some cases of battery explosion.

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Q&A, Help & Troubleshooting] MauFerrusca:
Gotcha. I wasn't really going to, but now I'm absolutely not going to.
[Galaxy S II Q&A, Help & Troubleshooting] Aello:
Ok some news for the detectives:

1) I've installed a time-voltage-percentage logger, and noticed that somehow, with the two new batteries, the system isn't able to correctly understand where is the bottom value. Let's just say that in semi-idle mode, with normal background processes on, it often relates ~50% to a stable 3.70V, which is (as far as my aknowledge goes) way too low to be halfway the charge. If 4.2V is the maximum value, the battery shouldn't drop below ~3.4V, so I'd say 3.70V is about 25%, almost time to give me an alert to plug in the charger!

2) For other reasons, I went to recovery mode, and noticed it actually signed my battery level at 20% (3.70V - 50% in the logger, just a couple seconds earlier, inside the ROM). As soon as I rebooted, the system seemed to syncro with the recovery, to a reasonable 20%. (The logger shows a drop from 3.70 50% to 3.69 20% in a single step, with a resolution of a step every minute)
[Moto G Q&A, Help & Troubleshooting] dineshtather:
Hi People,

I bought this phone moto g and thought it was wonderful. It is wonderful but I think there is some problem with the display of my screen.

It is showing some of the white lines mostly in mail apps like gmail and yahoo I am even attaching the screen shot of the same and i have even placed a replacement return request to which flipkart people said to try out the dead pixels detect and fix app from google play, did not help.

Please let me know if any one has any thought over this screen if its dead or white lines in the screen display. Please do check the screen shot attached

Thanks and regards,

Dinesh Tather.
[Moto G Q&A, Help & Troubleshooting] lightningdude:
If it shows up in a screen shot, it's not your screen, at least in terms of hardware. If you took the picture with another device, then it could be your screen.
[Moto G Q&A, Help & Troubleshooting] dineshtather:
hey lightning it's my phones screen shot only

Hi it's my screens screen shot only
[Moto G Q&A, Help & Troubleshooting] jaspreet997:
Oh yes its a rendering bug. Don't worry your screen is fine..its a kk bug...moto knows it
[Sony Xperia Z Ultra] fnf:
These are flashable zip file and FTF pairs for the latest KitKat firmware 14.3.A.0.681 for C6833/C6806/C6802 based on [NUT]'s modifications. I couldn't wait for his firmware so decided to make it :) .

The upgrade instructions are exactly the same as in this thread: http://xdaforums.com/showthread.php?t=2631768 . You only need to use the flashable zip and FTF files in this thread instead. In a nutshell:

Install recovery (either via a root exploit or unlocking the bootloader). Note: unlocking the bootloader will typically result in data loss, you are advised to use the root exploit on the older firmware instead of touching the bootloader.

Enter recovery and flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip

Power off the device and enter flash mode

Flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf using FlashTool (0.9.15.0 or later, older versions won't work)

These instructions are relatively safe and you can always downgrade using the other flashable zip/FTF if you so wish.

Lots of credits go to NUT & co. for making the original flashable zip!.

Notes:

- Some people run into a bug that makes camera non-functional. If you have this bug you can try flashing zip/stripped FTF from another region (e.g., US) instead.

- If you have issues remounting /system in TWRP you can try [MENTION=4904057][NUT][/MENTION]'s patch for the recovery here: http://xdaforums.com/showpost.php?p=51378028&postcount=88 . It can be flashed after you flash the flashable zip with adb sideload recoverypatch.zip inside the package on Linux or running install.bat on Windows.

Download links:

Flashable zip for C6833:

-- Mega -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip

-- GDrive -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip

Flashable zip for C6806:

-- Mega -- C6806_14.3.A.0.681 US_Unbranded_flashable.zip

-- GDrive -- C6806_14.3.A.0.681 US_Unbranded_flashable.zip

Flashable zip for C6802:

-- Mega -- C6802_14.3.A.0.681_Generic HK_flashable.zip

-- GDrive -- C6802_14.3.A.0.681_Generic HK_flashable.zip

FTF for C6833:

-- Mega -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf

-- GDrive -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf

FTF for C6833: C6833_4.4.2_HK_Stripped.ftf

FTF for C6833: C6833_14.3.A.0.681 _Euro-LTE_Stripped.ftf

FTF for C6833: C6833_1275-9413_R3C 14.3.A.0.681_Singapore Generic_Stripped.ftf

FTF for C6806:

-- Mega -- C6806_14.3.A.0.681 US_Unbranded_Stripped.ftf

-- GDrive -- C6806_14.3.A.0.681 US_Unbranded_Stripped.ftf

FTF for C6802:

-- Mega -- C6802_14.3.A.0.681_Generic HK_Stripped.ftf

-- GDrive -- C6802_14.3.A.0.681_Generic HK_Stripped.ftf
[Sony Xperia Z Ultra] scoobydu:
Thanks for the work; have you installed via this method yourself?

I ask as there are a couple of other requirements for this to work in Nuts Z1 thread on the same subject here -> http://xdaforums.com/showthread.php?t=2687443

Whereas you link to the 4.3 update without the init.d requirements?

Thanks
[Sony Xperia Z Ultra] fnf:
Yes, I'm running KitKat with the firmware that I posted.

I didn't need to enable init.d support and can confirm that dr.initd.active is set to false in my XZDR config. SuperSU works as well as the rest of the firmware.

Not to devalue the work that people have done (on the contrary it is much appreciated!), but there are a lot of conflicting information on how to root the device. I feel the rooting guides are much longer than necessary. Here is why (and how) we can root and keep the bootloader locked:

We root a firmware (e.g., 14.1.G.1.534) and install recovery

With recovery we can install the system tarball of any other firmware versions (e.g., KitKat). The flashable zip also installs SuperSU (among other) in the process.

We will then flash everything from the new KitKat firmware but system image. Stripping at least the system image out of the FTF ensures that it will not be reflashed by mistake.

Regarding init.d support, it is no longer needed on 4.3 onwards as daemonsu will be started by install-recovery.sh .
[Sony Xperia Z Ultra] android_myan:
Stripped FTF is not working

Your stripped ftf is not working. Please check and upload. Thanks!!!!!
[Sony Xperia Z Ultra] fnf:
Weird, I'll check when I come back in an hour or so. If you want to make it work in the mean time, you just need to flash the Germany KK FTF instead of this FTF in the General forums and exclude system, userdata from the flash and especially uncheck all items in Wipe section. If you're unfamiliar with Flashtool it's better to wait.
[Sony Xperia Z Ultra] atrix2:
Will this work with c6802 as well as c6806?

Unlocked bootloader.
[Sony Xperia Z Ultra] fnf:
I can produce the zip and FTF for these devices but I won't be able to test it. That said, if you have an unlocked bootloader wouldn't it be easier to just flash the dual recovery kernel and then supersu to gain root?. Being able to flash custom kernel is an advantage that us with locked bootloader can't enjoy :).
[Sony Xperia Z Ultra] scoobydu:
OK thanks for the explanation.

Did you make any progress on tracking the error with the stripped down ftf at all?
[Sony Xperia Z Ultra] dadme:
Installed, but camera won't work. Only preview. Other camera apps works ok, only Sony camera won't make shoots. I try to flash full ftf to see if works.
[Sony Xperia Z Ultra] fnf:
I have redownloaded the FTF and compared the checksum, it doesn't appear corrupted to me so I think the problem is you're using FlashTool 0.9.13. Newer Sony firmwares work with 0.9.15.0.
[Sony Xperia Z Ultra] fnf:
If you flash the full FTF you will lose root unless you exclude 'system'. I'd suggest clearing the Camera app's data. Camera works fine for me. I just upgraded from 4.3 so mine has not been factory reset.

Edit: Are you storing the photos to the SD card by any chance?. I have applied the fix for SD card permissions so not sure if it is an issue or not.
[Sony Xperia Z Ultra] android_myan:
Thank! I will try with new flashtool version.
[Sony Xperia Z Ultra] abuihsan:
my device is C6802, I was on rooted .681 with unlocked BL. I want rooted but with locked BL so I did these:

with TWRP I wipe dalvik and cache and then flashed 6833 flashable zip

power of and then flash stripped ftf via flashtool 0.9.15.0

reboot - restore TA - reboot

done.

now I got root with locked BL

thanks!
[Sony Xperia Z Ultra] dadme:
Tryed everything, only front camera works, with back camera i can't make shoots with sony camera, and autofocus is not working in other camera apps. I upgraded from 4.3. with or without factory reset problem is here.
[Sony Xperia Z Ultra] fnf:
Can anyone else please confirm?. There are nothing specifics to my device in the FTF or the zip so I suspect flashing the full FTF won't fix it.

The binaries were generated from the Germany KK firmware if that helps.

[MENTION=4742570]abuihsan[/MENTION]: thanks for letting me know, the only difference between Z Ultra variants that I've seen is radio so the worst we'll get is losing LTE.

If anyone wants me to create the files for other variants then let me know.