Rogue One X - The Return - HTC One X

Ok - so some of you might remember my thread from a few weeks back.
I had an assortment of issues - notably a System 7 error when I tried to install CM11.
I read through some of the copious amount of threads on here, and found that Status 7 error may result from not having correct radio installed - or some other software component that is required for the installation to go through properly.
So - I thought - what about trying CM10 again, rather than CM11.
This time, it seems as if the ROM has installed fine.
No errors in installation log etc.
Booting the phone throws up a problem, and this makes me think there's a hardware issue.
Sometimes it will boot to the CM10 welcome screen -and hangs.
Sometimes it hangs on the HTC quietly brilliant screen.
Sometimes it hangs during the CM10 boot screen.
Sometimes the CM10 boot screen animation runs as though the screen were a CRT with a dodgy signal coming in from the aerial.
Once - it loaded to the welcome screen, crashed and the phone emitted a loud, very high pitched squeal, and wouldn't stop until it was switched off...
So - any ideas what could be the problem here?
Hardware? I could take a look inside it, if this thing is a lost cause otherwise...

267 views, and no comments from anyone about this?
Are people completely stumped with my device and what it's doing?
Is this thing just fit for the bin, or being ceremoniously destroyed with a mash hammer?

subharmonic said:
267 views, and no comments from anyone about this?
Are people completely stumped with my device and what it's doing?
Is this thing just fit for the bin, or being ceremoniously destroyed with a mash hammer?
Click to expand...
Click to collapse
Ared you flash the boot.img from rom archive. Maybe the phone is to hot and reboot try cooling the phone while boot maybe faulty battery

Yeah I've flashed the boot.img from the ROM.
Ok - something interesting happened there just there.
It's not been switched on for a few days - booted up great - got to CM10 set up screen - clicked Great Britain English - and on next screen it froze - horizontal lines across the screen, and high pitched scratchy sound (sort of similar to dial up modem sound, only higher pitched).
Just tried to flash boot.img again, and erase cache - crashed on HTC screen.

When it's cool - the phone def seems to boot up better - gets to the CM10 welcome screen ok - but when I try to do anything it then crashes - those weird horizontal lines through the graphics.
The more times the phone is rebooted, the less likely it is to get to the CM10 screen and just hang on HTC screen.

subharmonic said:
When it's cool - the phone def seems to boot up better - gets to the CM10 welcome screen ok - but when I try to do anything it then crashes - those weird horizontal lines through the graphics.
The more times the phone is rebooted, the less likely it is to get to the CM10 screen and just hang on HTC screen.
Click to expand...
Click to collapse
Yeah - just tried all of this again - let it cool down - tried to boot it up - got to CM10 welcome screen -then got through to the 2nd screen where it came up with an error relating to the lack of SIM card.
And then a screwed up screen with that sort of white noise thing.
I then restarted - and each time it would proceed less and less - eventually just getting caught in a boot loop.
Curiously, the boot loop eventually kicks out and phone goes into recovery by itself?
Where do I go with this people?
Any ideas?

Related

[Q] Boot loop/screen issue

After replacing old screen at official service my One X started to work badly, at first it were constant messages about system process crashes, then a boot loop occured. I tried to erase cache, but it take no effect. I've made factory reset and all started to work normally, but after 2 days I spotted that my screen doesn't respond. I can switch it on/off, control volume, but buttons or screen don't work at all. Reboot sometimes fixes this issue, but more often a boot loop occures. Again. I have no customize at all, everything is default and phone is unrooted. Need some advice how to fix it.
service center again
Pantelshtein said:
After replacing old screen at official service my One X started to work badly, at first it were constant messages about system process crashes, then a boot loop occured. I tried to erase cache, but it take no effect. I've made factory reset and all started to work normally, but after 2 days I spotted that my screen doesn't respond. I can switch it on/off, control volume, but buttons or screen don't work at all. Reboot sometimes fixes this issue, but more often a boot loop occures. Again. I have no customize at all, everything is default and phone is unrooted. Need some advice how to fix it.
Click to expand...
Click to collapse
I have a similar issue. My phone started rebooting, getting to the point where it displayed the HTC logo, and then starting over again. Later, I got it to boot normally, but the touch screen won't respond to touch anymore.
I should note that the troubles first started after I found my phone lying in a puddle of water.
Good thing this happened now, so that I at least have a proper excuse to spend way too much money on the new X+.

[Q] DHD Display flickering; How to repair?

Hello Forum,
seems that my DHD has an irreparable error.
But i've still a little hope that maybe someone of you guys out there can point me into the right direction to repair the phone again.
What happened:
on December, 20. for no apparent reason the Display started flickering approximately 2 cm from the top.
The upper Part (the first 2 cm from the top of Display) was showing the normal Picture, on the lower Part the Picture was flickering at irregular time intervals, but the touch gestures were still working without any Problems.
Setup at that Time:
- Latest 4ext Touch Recovery
- Latest MIUI.us Rom by bliind
- Custom DPI set to '190' (with ROM Toolbox)
- Max CPU Speed set to 1200 Mhz (with Set CPU)
(Had this setup working fine without any issues for approx. last 2 Months...)
Last change i did before the error occured: Set Custom Boot Animation with Rom Toolbox
The Flickering started not immediatly after setting the new boot Animation but i think 2 days and some reboots later...
Actions that i've already tried to solve the Problem:
1. Shut down the Phone, pull out the Battery, wait some Minutes, reboot the phone.
-> The flickering was gone and the Display looked normal after reboot.
2. After some time I took the Phone out of my pocket and the flickering was there again like before.
Tried to set DPI back to original value '240'
reboot the Phone
-> The Flickering still was there and it seemed to me that the responsiveness of the touch was slightly slower than normal.
3. Reboot into Recovery
Nandroid Backup all Partitions to SD-Card
wipe all partitions except SD-Card
new, totally clean flash of latest MIUI.us Rom by bliind
Reboot the phone
-> The flickering was gone; responsiveness of the screen normal as it was always before.
4. restore all apps; put the phone on the charger over night. everything worked fine again.
on the next Morning this strange flickering was there again; the Touchscreen was very slow responsive in the flickering area
Managed once more to reboot into recovery, but the flickering was now even in the Recovery and on the boot screen.
-> The Touch got more and more unresponsive.
Could no more start a new ROM flash out of Recovery.
5. Tried to access the phone via aahk tool and restored last stock ROM
-> After Reboot the DHD vibrates (like it usually does for startup)
the screen shows a bunch of black and white Stripes that chnge their Color when the Boot Animation should show up,
and later again when the lockscreen should appear.
It makes the boot jingle and i can send Commands via adb.
but Touch commands doesnt work, (tried to put in the Pin blind, but it shows no reaction)
Stupid, but I can't change it: my Warranty and the extra Insurance that i purchased for the DHD ended just 2 weeks before on 6. December.
6. Disassembled the whole phone with Help of you tube disassembling Guide, carefully cleaned all contacts and assembled it again.
-> nothing changed; same behavior like before disassembling.
What can I do? Any ideas except of small rasping and stirring into the soup? :crying:
Can it be only the display? Maybe the Graphic Chip?
Any other ideas?
thank you for reading this all and i appreciate any suggestion that might give my DHD a new spirit of life
Greetings from Cologne
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
bananagranola said:
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
Click to expand...
Click to collapse
Thanks for your reply!
That was the same what I thougt after disassembling and cleaning with no result.
Cause it seems to me that the Display is still working, but the Signal that's coming in is broken.
I alsready supposed that the Graphic engine is broken.
Just had a little Hope that someone might had the same Problem and got it solved,
before I start practice for mobile phone throwing competition...
i suggest another ROM JB used to cause my DHD flickering (earliear versions)
My DHD was with same problem 1 year a go, and that usually happen when i played games like Angrybirds or Asphalt, or when the device temperature was high.
I was worry at that time, thinking that the device was gone.
Take the same solutions that you had (except disassemble the phone) but they're only temporary.
By that time i decide root the device and install a new rom, (nothing to loose had i think) and Revolution HD was my choice.
After that my DHD didn't flick any more.
I didn't ever know what was the origin of that flickering but for me, that was the big solution.
I'm using Viper Venom 1.2.3 for now, and still with no flickering insues.
So, my advice for you is... give a try to other rom's and kernels, maybe you resolve your insue has i did.
Good luck with that.
Sent from my HTC Desire HD using xda app-developers app
Thanks for you Answers guys,
the Problem i have is, that my DHD does show only sripes even if I try to boot into Recovery, I can't see anything and am not able to start a flash process...
cause i have installed 4ext touch recovery i need the screen to wipe and flash a new ROM.
But i will try to flash an CWM - Recovery through ADB and then to start the flash Process blind by tapping the buttons...
let's see what will happen. There's nothing to loose...
For now, cause I was sitting without a mobile phone at all, I've ordered a cheep one from Amazon... - Huawei U8510 (Ideos X3) -
And oh WONDER!!!: I've got a fully functioning phone with CyanogenMod 7.2 and all the stuff i use my phone for is working without any Probs..
And the whole thing has 2 years of warranty at a cost of € 80,-
only the Display for my HTC would cost € 40,-
so I'm thinking of selling the broken phone on ebay and let anyone try to repair it who is able to....
but I will give it a try to flash another ROM.
Already downloaded the JellyTime R30...
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
It seems to be broken since today morning. I wiped the phone and restored the backup I made the afternoon before, and then the first vertical stripes occured. I wiped it and flashed the same rom (CodefireX 4.2.1) again. Same issues. Now I tryed to flash a GingerBread Strock Rom. Even the same issues, and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Stupid situation, today my Warranty ended.
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Thanks in advance!
daniel_DHD said:
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
[...] and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Click to expand...
Click to collapse
Seems to be the same like my DHD. But for me it ended up 2 Weeks after end of Warranty!
daniel_DHD said:
Stupid situation, today my Warranty ended.
Click to expand...
Click to collapse
The T-Mobile Customer Support told me, that they would have accepted the case as Warranty, if my DHD had ended up during the first week after End of Warranty. Don't know where you bought yours, but maybe there's a small chance for you to get Warranty Support through their obligingness.
If I were you I would try this...
daniel_DHD said:
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Click to expand...
Click to collapse
If your dealer don't accept your Warranty Call, I can't give you much Hope... Sorry for you...
... would imagine you should look for a new phone...
That's what I did....
Similar problem
I have also got a similar problem. Had my phone for two years and have also just hit the same problem. Flashed a new ROM, everything was working fine, then all of a sudden top half of the screen is displayed correctly, the bottom half is always flickering. This occurs in the bootloader as well. Anyone would think that HTC decided to make sure the phone only works for two years and a few weeks after the warranty expires to make sure it experiences problems.

[Q] modded/rooted One X screen issues: hardware related?

So, recently my One X (EU version, endeavoru) begin showing some problems, as outlined below. It was the newest stable CM (10.3) and a somewhat older version of CWRM. After the problems showed, I managed to upgrade to the latest CWRM and CM. Here's the problem:
- When I tried to unlock my phone, the screen stayed black, so I reset the phone.
- When it started up, the HTC logo looked fine, but the CM logo was shifted down and banded: the top of the circle was visible on the bottom of the screen and the bottom of the circle on top of the screen. After that logo the screen turned black.
- It DID boot though, as I could feel the haptic feedback when trying to unlock, and I could hear the sounds of making a screenshot (power+vol down).
- After some resetting etc I finally got an image of the screen again, and saw that I moved some widgets around, so the touch screen def. works when the screen was black.
- I wanted to make sure it was a hardware problem, so I did a total wipe (factory/dalvik) and flashed a new recovery. This worked, but a few times when working in recovery the image froze. I'm not sure if the recovery crashed and did not respond to input, or that the screen just froze, as CWRM only has visual feedback.
- I managed to install the latest CM, tried it, it worked, and then the screen showed some green lines, and a slight shift upwards (the top rows of the status bar showed at the bottom), and I couldn't do anything anymore as far as I could tell.
- The bootloader also showed some problems: the letters were enlarged and overlapped while the image was also smeared across the screen.
Now, basically my question is: can I be sure this is a hardware problem? HTC will fix it if that's the case, but otherwise I will have to be a bunch of money for nothing, because then they will pin the problem on the custom software/firmware/recovery installed. However, I don't think any of the firm/software can actually influence the bootloader, am I right? So if there are problems with the bootloader, it cannot be the case that something I installed on the phone causes the problem.
i think what u have there is Screen Flickering ,, and it's due to a hardware problem ,,someone had the same problem and he had to replace the screen and the motherboard !!!
again am not sure !!
hasan.nj said:
i think what u have there is Screen Flickering ,, and it's due to a hardware problem ,,someone had the same problem and he had to replace the screen and the motherboard !!!
again am not sure !!
Click to expand...
Click to collapse
Thanks! I searched for one x screen flicker and found a video that showcased my problem perfectly:
youtube.com/watch?v=BfnwMFtD2_A
One of the comments said that if they pressed the screen just below the HTC logo it worked again (temporary), and I could reproduce this on my phone. Now I have no doubt at all it's a hardware issue, and I will contact HTC for repairs!

[Q] N7 becomes super slow intermittently. I flexed it and it seemed to fix it.

Bare with me I know this sounds weird. My 2013 Wifi N7 worked well for quite a while, then would intermittently get extremely slow to the point of being unusable. It was previously unlocked and rooted so I reflashed the factory image a few times but it would still have issues. I was starting to think the flash memory in it was bad.
Just today I reflashed 5.1.1 (was on 5.0.1 which was the last time I used it). Upon first boot the startup animation started going extremely slow, occasionally speed up to normal speed, stop and appear to freeze then start moving slowly again. The animation continued to speed up, slow down and freeze. After about 10 minutes it still had not not gotten to the initial Android sign in screen.
I picked it up and slightly flexed it from 2 opposite corners and suddenly the boot animation starting playing at full speed. I stopped flexing it and it slowed to a crawl again. I did this a few times and each time slightly flexing it caused it to work correctly. I held it in the flexed position and the boot animation continued to display at normal speed and it finally completely booted up. Once it booted it asked to connect to Wifi and again was super slow and unresponsive after I let go of the corners to touch the screen. I then flexed it back and forth a little more forcefully and it has continued to work normally since then. I have played with it a little and rebooted a few times with no issues.
I am assuming there is something loose internally that flexing somehow fixes. Does anyone have any idea what would be causing this? I don't have a problem opening it up and trying to permanently fix whatever is causing the issue but I'd like to know the cause before I attempt a repair.
Fuzzy_Dunlop said:
Bare with me I know this sounds weird. My 2013 Wifi N7 worked well for quite a while, then would intermittently get extremely slow to the point of being unusable. It was previously unlocked and rooted so I reflashed the factory image a few times but it would still have issues. I was starting to think the flash memory in it was bad.
Just today I reflashed 5.1.1 (was on 5.0.1 which was the last time I used it). Upon first boot the startup animation started going extremely slow, occasionally speed up to normal speed, stop and appear to freeze then start moving slowly again. The animation continued to speed up, slow down and freeze. After about 10 minutes it still had not not gotten to the initial Android sign in screen.
I picked it up and slightly flexed it from 2 opposite corners and suddenly the boot animation starting playing at full speed. I stopped flexing it and it slowed to a crawl again. I did this a few times and each time slightly flexing it caused it to work correctly. I held it in the flexed position and the boot animation continued to display at normal speed and it finally completely booted up. Once it booted it asked to connect to Wifi and again was super slow and unresponsive after I let go of the corners to touch the screen. I then flexed it back and forth a little more forcefully and it has continued to work normally since then. I have played with it a little and rebooted a few times with no issues.
I am assuming there is something loose internally that flexing somehow fixes. Does anyone have any idea what would be causing this? I don't have a problem opening it up and trying to permanently fix whatever is causing the issue but I'd like to know the cause before I attempt a repair.
Click to expand...
Click to collapse
Hi,
I had the same issue like you, do you get what was wrong with your Nexus?
osi666 said:
Hi,
I had the same issue like you, do you get what was wrong with your Nexus?
Click to expand...
Click to collapse
Unfortunately no. I ended up giving it away to someone else with a N7 that had a cracked screen so they could attempt to transplant the working screen from my unit.

Pixel XL stuck in bootloop.

There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Gnatcatcher said:
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Click to expand...
Click to collapse
Maybe replace battery?
Hi there! I am not sure if your problem was fixed yet. But my Pixel XL died yesterday and did the same exact thing. It went into an infinire boot-loop, and after trying many times to power off and reboot, some weird artifacts appeared.
I think I messed up the phone, because at first the phone booted and then restarted, but now it just restarts and never ends....
EDIT: After some hours of rebooting, and more artifacts, the Pixel finally booted on android. Battery was at 4% so I guess that helped. It keeps rebooting from time to time, but at least I can copy my photos now haha.

Categories

Resources