Just picked up an HTC ONE XL
Seems to have some issues I did some research and found out there was an issue with updates.
Issues
1.IF I do a factory reset as phone is loading speaker phone speaker works. Then stops after home screen loads
2.Home back apps buttons are use less (very common)
My Phone
evita s on
hboot 2.14
3.18
I used a ruu nothing changed. Is there any way for me to root or downgrade this phone.
It seems the only option I could find are with linux(which I never used) .
Why are you wanting to root/downgrade? If you've run an RUU and those problems are still present you're dealing with hardware faults. Only a repair will fix those.
Sent from my Evita
timmaaa said:
Why are you wanting to root/downgrade? If you've run an RUU and those problems are still present you're dealing with hardware faults. Only a repair will fix those.
Sent from my Evita
Click to expand...
Click to collapse
Not at all. For some reason select htc one XL were not compatible with the 3.14 update.
People with these phones lost there front touch panel and some people lost the speaker.
my speaker randomly turns on and off since update, my front touch panel lights up but has no use.
If you're confident the problems were caused by the update itself then that sounds like it should be covered by warranty.
Sent from my Evita
Related
Hello guys. I tried to search the forum for acceptable answers to my question but couldn't find it. I have the dreaded dead screen problem with my One X. The phone still operates and I can even answer calls but it's completely black. Can't even get to the bootloader screen. I contacted AT&T and since it's within 12 months they're sending me to a Service Center. Will they even be able to diagnose the problem (mainly see that I'm rooted, S-off, and unlocked) or just replace the thing? It has no cosmetic damage whatsoever. I can't flash back to stock since I have no idea what's happening on the phone!
I'm thinking (hoping) they will just replace it.
I haven't really heard of this problem (black screen), at least not as a more "common" issue. So the screen does not turn on at all, but still responds to touches? Could actually be a hardware failure.
AT&T doesn't give a poo whether its bootloader unlocked, running a custom ROM, etc. They will just give you a refurb.
redpoint73 said:
I haven't really heard of this problem (black screen), at least not as a more "common" issue. So the screen does not turn on at all, but still responds to touches? Could actually be a hardware failure.
AT&T doesn't give a poo whether its bootloader unlocked, running a custom ROM, etc. They will just give you a refurb.
Click to expand...
Click to collapse
Yeah the only reason I'd said that is because I found a lot of threads about it from a few months ago. It's apparently an issue with the tegra chip overheating and shifting location. The screen won't turn on but I still get notifications, calls, and can "unlock" the phone (still no visual though).
Only thing I was worried about was AT&T caring but I'm good with a refurb as long as they don't hassle me about the phone's state.
Thanks!
kotchishm said:
Yeah the only reason I'd said that is because I found a lot of threads about it from a few months ago. It's apparently an issue with the tegra chip overheating and shifting location. The screen won't turn on but I still get notifications, calls, and can "unlock" the phone (still no visual though).
Only thing I was worried about was AT&T caring but I'm good with a refurb as long as they don't hassle me about the phone's state.
Thanks!
Click to expand...
Click to collapse
These phones don't have the Tegra chip. That's the One X International.
Sent from my One XL using XDA Premium
I returned mine and got a refurb. I flashed the AT&T RUU beforehand but still had S-OFF and even a custom bootsplash and they took it right back and gave me a replacement.
Can't you RUU without seeing the phone's screen? Pretty sure nothing needs to be viewed on the screen to do that. Since you are S-off, its safe to run the 3.18 RUU.
If you RUU and still a black screen, my gut would say its a hardware issue. As already mentioned, we don't have the Tegra chipset (our is Snapdragon S4). But it can be something with the GPU, the screen has gone bad, a bad connection somewhere, or other hardware issue.
I had the same problem and yes, its a hardware issue. I went to a service center and they replaced it no problem. I was rooted, boot unlocked, the whole deal.
Sent from my HTC One X using xda app-developers app
milkytron said:
I had the same problem and yes, its a hardware issue. I went to a service center and they replaced it no problem. I was rooted, boot unlocked, the whole deal.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just went. They replaced it no questions asked. Now to root and unlock again...
timmaaa said:
These phones don't have the Tegra chip. That's the One X International.
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
Sorry meant the snapdragon. Either way it was definitely a hardware issue.
I recently took the plunge and upgraded my Hboot to 2.15. Followed the instructions exactly. Everything went smooth. Installed the updated Carbon and everything was ok. Then I noticed I am not able to get any signal higher than EDGE. I have done all the tricks I know of such as setting network to WCDMA only. The 3G and H will pop up but it will be grayed out. Then it drops down to EDGE again. This is the case on all roms I try. I installed the RUU for Jellybean (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2) Although I don't think it touched the Hboot, it installed fine.I am not sure if the 4G worked because I don't have it at home. But I needed a rooted rom so I reinstalled recovery and installed another rom. Sounds like a hardware problem right? Well it seems that it has happened to several people here on the forum. As well as T-Mobile forums. And it is not an outage since my wife and son get 4G fine on their phones. Any help or suggestions would be appreciated.
Ever thought of installing another Radio?
http://forum.xda-developers.com/showthread.php?t=1998270
Yeah using Temporary radio installer . But CM uses radios differently so not sure if that is a factor. I installed a lower RUU which downgraded my Hboot. Reinstalled Viper so we will see how this works. I am sure it is not a hardware problem since it happened at once when I upgraded Hboot and the same for others when they got the Jellyean update.
This is quite a common issue that a few people have faced.
Problem is, so far there seems to be no solution other than to send the phone back to HTC and get the mainboard changed (or apparently by hard bricking your phone and then unbricking it, via JTAG I would guess).
The same issue happened to me a couple weeks ago. I tried every single RUU, firmware, HBOOT, radio, you name it. But no matter what I did the phone was stuck in 2G mode and could only get 3G randomly for a few seconds when first booting up. Ultimately, my phone got hard bricked by an official RUU... go figure.
Not sure why it happens, but some have mentioned that it could be a side effect of upgrading to the Jellybean RUU while being S-OFF.
That's the weird thing. All I did was upgrade the hboot. I don't have 4g at home so I didn't even notice it right away.
Sent from my HTC One S using xda app-developers app
Same issue...
I have the same issue with my One S, after upgrading HBoot to 2.15, no more mobile data above 2G. Both TMO and HTC are saying the phone has to be sent in, but out of warranty I'd have to pay for it out of pocket.
So I agree that it seems to be the HBoot upgrade doing it. The ONLY thing I have not tried yet, is downgrading the HBoot <because of the complexity and desire to not screw this phone up even more>.
Looking for solid answers...
C.
Ever since I bought my phone, before being rooted and even on stock ROM, I'll get delayed text messages and they wont recieve until I reboot my phone or switch airplane mode on and off. Then they hit me ALL at once. This happens atleast once a day and people will end up thinking I'm ignoring them because of this problem. Is it a problem with the HTC One X in general? or Android? It still happens on every single ROM I tried too and I have tried various radios and none fix it. I am on AT&T, and currently on MagioRom. It still does it regardless of what ROM though. This is the one single thing that I have just sort of learned to put up with, as much as I hate it. I came from an iPhone and they never had that problem so I really miss that. I reboot my phone about 5 times a day to remedy it. Besides that this phone is amazing of course.
Oh and was the bug with iPhone screenshots being sent through text to the One X and coming out really really tiny ever fixed? Im still getting that problem too.
It's not a problem with the phone or Android as such. Do you ever suffer signal drops which may cause this to happen? Or do you live in an area with low signal? It sounds more like a carrier bug to me.
Sent from my Evita
timmaaa said:
It's not a problem with the phone or Android as such. Do you ever suffer signal drops which may cause this to happen? Or do you live in an area with low signal? It sounds more like a carrier bug to me.
Sent from my Evita
Click to expand...
Click to collapse
I always have great signal, no signal drops ever, so I never thought it would be my carrier, thats strange... Now I don't know if its AT&T or a defect with my phone...
It could be an issue with your phone? Have you tried running an RUU? I'd do that and leave it stock fire a few days to see if it continues. You'll want to make sure you're safe to RUU first though, what are your hboot details?
Sent from my Evita
Hboot 1.14
I can't RUU yet though cause I'm still S-On, which I haven't tried to do yet because I didnt wanna risk messing my phone up... Would that actually help?
And could it be an Hboot version problem or firmware problem? Cause I bought my phone about 1 year ago and it came with Icecream Sandwich. And I've had to deal with this problem the entire year.
It could be anything. Do you have SuperCID? You definitely must get s-off before running an RUU.
Sent from my Evita
Yep, it says 111111111111
I'll try getting S-Off and running RUU then, I just really wanted to avoid doing that but I guess I have no choice.
Sometimes it's the only way to find out what you're dealing with. The process is simple, it took me five minutes.
Sent from my Evita
I began posting this problem in a previous thread but am starting a new one to avoid clogging said thread.
Here are my phone details at the moment:
S-Off
SuperCID
HBoot 2.14
Radio 0-24p.32.09.06
Open-DSP-v34.1.0.45.1219
I bought the phone used off kijiji. It was stock when I got it. Rogers, Android 4.1, 3.17 firmware. I unlocked the bootloader, got SuperCID and S-Off, flashed TWRP and flashed a custom ROM - CleanROM. Things were okay for a bit.
Then I started getting random restarts and losing signal. I realized I was on 2.14 hboot so I updated to 2.15. I thought it fixed the problem but no- before long, more random reboots--though I did fix the signal issue.
So I flashed Beastmode kernal. Now, I did this without doing a full wipe - just threw it on top of CleanRom. Possibly a bad idea because everything kinda got all screwy at this point. The phone started acting really oddly--freezing a lot, restarting even more often, and sometimes the touchscreen would act up.
Next step: I tried to do a full wipe and flash a different ROM: KickDroid. Only thing was, it wouldn't flash. The installer would crash, most of the time at 30%. The phone would then restart, though it wouldn't boot (obviously), so I'd have to hold down the volume to put it into the bootloader.
Tried flashing CleanROM then - no go. It wouldn't flash either - phone would just power down.
This became a theme. The phone would just start turning itself off all the time. Even sometimes when I was doing a wipe in TWRP, the thing would just crash partway through and turn off. Somehow, this morning, I DID manage to get CleanROM to flash, but then it wouldn't boot- froze at the Google splash screen and turned off...
On timmaaa's suggestion at this point I went to an RUU and tried to get the phone back to stock. Went with the 3.18 Cingular RUU. For whatever reason, it didn't work the first time (might have been my fault - I forgot to uninstall HTC Sync Manager) but when I tried it again, it did. I was excited - phone was, hopefully, back to its old self, after all!
Booting to splash screen: freezes on the HTC logo. Turns off, randomly. AAGGHH!!!
So I try again, knowing, at this point, it's futile. The phone BEGINS to boot up. Gets to the Cingular screen and then just enters into Android - says it's going to start refreshing apps or whatever... and then it turns off.
Note that I have it sitting in the bootloader right now and it is not turning off. The bootloader itself seems to work well enough.
Even now, I tried to boot the thing up just one more time, and it again just nearly got into Android but turned off before fully loading.
I'm at a loss. It's not like I've been just randomly flashing things on here - I only used ROMs that worked for the phone. Maybe my dirty flash (is that the right terminology) of Beastmode was the problem, but I feel like it shouldn't continue to persist this long, after using an RUU. I'm wondering if perhaps it's a hardware issue at this point.
Any thoughts, ideas, suggestions, etc. are amazing... thank you.
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
timmaaa said:
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
Click to expand...
Click to collapse
Darn. Anything that can be done about that? Is it feasible or even worth it to try to replace it?
Get this - it just booted to Android, and seems to be staying there. For the time being, anyway.
Edit: never mind. lol. Turned right off again after connecting to wifi.
It all depends on whether you think it's worth the money to repair it, or just to buy a new device.
Alright. Thanks a lot for your help. I'll try to consider my options.
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
johnnyp12321 said:
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah, I'll give that a shot, too. Thanks. Though I'm not that optimistic at this point, lol.
On a related note: I have the opportunity to buy an HTC One XL with a broken screen for cheap. What do you guys think the options are for me (a) taking the mobo out of the broken one and using it in mine or (b) replacing the screen on the broken one with the working one from mine? Do you know how difficult/manageable either process is?
The phone seems to be more or less completely dead now. It will occasionally power up but can't do much beyond the bootloader. Anyone have any experience replacing motherboards on the HTC One XL? Is it possible to swap one out from a working phone? Or is it possible to use my screen to replace one on a phone with a broken screen?
Hi all
I have a One XL (evita). For the past few months it has been crashing and locking up a lot. Multiple times a day. It started on the stock rom. I tried a few different roms, etc and it does the same thing on all of them. It's currently on Cyanogen 11-20140916-SNAPSHOT-M10-evita 4.4.4 Sometimes when it's on charge it get extremely hot and doesn't actually charge,
The phone is mostly usable, but annoying. I'm probably going to be upgrading it. But I'd rather not just bin it.
How can I diagnose the issue?
Wrong forum, you have evita (One XL/AT&T One X), but posted in endeavouru (Int. One X). Apart from that mistake it looks like battery or other hardware issues.
If you're having the same problem across multiple ROMs it's probably a hardware fault. Run an RUU and leave it stock, if the problem persists you can confirm that it's hardware.
Transmitted via Bacon