About a week and a half ago I got water into my GS3 and it ruined the OLED panel. It was a relatively slow process, and I was able to use it up until most of the screen turned black (touch still functioning properly). I ordered a new Screen Assembly which included the frame, OLED panel, digitizer, and glass as ONE unit, pre-assembled.
Upon taking the broken phone apart and re-assembling it into the new frame/screen, the phone hangs for a long time on the "Samsung Galaxy SIII" with Cyanogenmod Cid character, but finally boots, however the touch screen is unresponsive.
All hardware buttons work, and the capacitive buttons work as well (back and menu), it is only the touchscreen that doesn't function, but it looks beautiful!
is this a digitizer issue (faulty hardware sent to me)? It seems as if the phone is trying to communicate with the digitizer or some other hardware, gets stuck in that loop because it can't detect it, times out, and then finishes booting.
I tried re-flashing CM to see if it was a kernel error or something of the likes, but the issue persists.
Any Ideas? Thank you so much in advance.
XdrummerXboy said:
About a week and a half ago I got water into my GS3 and it ruined the OLED panel. It was a relatively slow process, and I was able to use it up until most of the screen turned black (touch still functioning properly). I ordered a new Screen Assembly which included the frame, OLED panel, digitizer, and glass as ONE unit, pre-assembled.
Upon taking the broken phone apart and re-assembling it into the new frame/screen, the phone hangs for a long time on the "Samsung Galaxy SIII" with Cyanogenmod Cid character, but finally boots, however the touch screen is unresponsive.
All hardware buttons work, and the capacitive buttons work as well (back and menu), it is only the touchscreen that doesn't function, but it looks beautiful!
is this a digitizer issue (faulty hardware sent to me)? It seems as if the phone is trying to communicate with the digitizer or some other hardware, gets stuck in that loop because it can't detect it, times out, and then finishes booting.
I tried re-flashing CM to see if it was a kernel error or something of the likes, but the issue persists.
Any Ideas? Thank you so much in advance.
Click to expand...
Click to collapse
Only way to tell if it's a hardware issue is to go completely to stock. If you can't get it to work at that point then something is wrong. Could be a broken digitizer, or could be a problem with the connection to the board.
I would try to make sure your connection is solid and you didn't miss anything. But I'd say going back to stock is a necessity. Just make sure you Odin a 4.1.2 image, and if your screen still doesn't work then pull the battery so it can't update, then decide where to go from there.
BadUsername said:
Only way to tell if it's a hardware issue is to go completely to stock. If you can't get it to work at that point then something is wrong. Could be a broken digitizer, or could be a problem with the connection to the board.
I would try to make sure your connection is solid and you didn't miss anything. But I'd say going back to stock is a necessity. Just make sure you Odin a 4.1.2 image, and if your screen still doesn't work then pull the battery so it can't update, then decide where to go from there.
Click to expand...
Click to collapse
Thanks for the input, I appreciate it!
I have double- and triple-checked the connections. So what exactly would Odin-ing back to stock get me? The software/firmware worked flawlessly beforehand, so wouldn't that eliminate the possibility of software/firmware issues on my device?
XdrummerXboy said:
Thanks for the input, I appreciate it!
I have double- and triple-checked the connections. So what exactly would Odin-ing back to stock get me? The software/firmware worked flawlessly beforehand, so wouldn't that eliminate the possibility of software/firmware issues on my device?
Click to expand...
Click to collapse
Theoretically yes, but if you go back to stock you'll know for sure. If the digitizer isn't working anyway you have nothing to lose. If everything is completely stock then you know for sure it isn't software related and it has to be the digitizer.
Okay thank you, I appreciate your help!
Sent from my ASUS Transformer Pad TF700T using XDA Free mobile app
BadUsername said:
Theoretically yes, but if you go back to stock you'll know for sure. If the digitizer isn't working anyway you have nothing to lose. If everything is completely stock then you know for sure it isn't software related and it has to be the digitizer.
Click to expand...
Click to collapse
Sorry for reviving my dead thread and noob questions, but I'm still having issues.
My phone is perfect except for the screen doesn't recognize touches, although all buttons and capacitive buttons work well.
I am currently running CM11 using clockworkmod recovery, and I want to return to rooted stock, as you mentioned.
I am wondering if the firmware for the display is not present, since it is a new display (entire assembly, including frame).
How would I go about returning to stock rooted, and flashing as much stock firmware as possible to hopefully ensure that the display firmware is flashed?
As a side question, does the MF1 firmware AiO include things like display firmware? I flashed that with no result, so is flashing back to stock pointless?
I would like a 4.1 Stock ROM or whatever DOES NOT have Knox, so that I at least have the option to go back to CM if I wish if I sort out the issues.
Thank you all so much
XdrummerXboy said:
Sorry for reviving my dead thread and noob questions, but I'm still having issues.
My phone is perfect except for the screen doesn't recognize touches, although all buttons and capacitive buttons work well.
I am currently running CM11 using clockworkmod recovery, and I want to return to rooted stock, as you mentioned.
I am wondering if the firmware for the display is not present, since it is a new display (entire assembly, including frame).
How would I go about returning to stock rooted, and flashing as much stock firmware as possible to hopefully ensure that the display firmware is flashed?
As a side question, does the MF1 firmware AiO include things like display firmware? I flashed that with no result, so is flashing back to stock pointless?
I would like a 4.1 Stock ROM or whatever DOES NOT have Knox, so that I at least have the option to go back to CM if I wish if I sort out the issues.
Thank you all so much
Click to expand...
Click to collapse
I'm almost sure Knox wasn't added until 4.3 ML1
From my Wicked S3 on SOKP
ShapesBlue said:
I'm almost sure Knox wasn't added until 4.3 ML1
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Yeah, I think you're right
So anything Stock that will allow me to still have an unlocked bootloader when I'm done with it would be great!
4.0 - 4.2
XdrummerXboy said:
Yeah, I think you're right
So anything Stock that will allow me to still have an unlocked bootloader when I'm done with it would be great!
4.0 - 4.2
Click to expand...
Click to collapse
Correct. Custom roms will work just stay away from anything in the development forums that says BL LOCKED or any variation of that
From my Wicked S3 on SOKP
ShapesBlue said:
Correct. Custom roms will work just stay away from anything in the development forums that says BL LOCKED or any variation of that
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
But to solve my issue I need the stock firmware, which means stock (and rooted) ROM. Is there a forum for that in the development section or where could I get my hands on it?
Thanks!
XdrummerXboy said:
But to solve my issue I need the stock firmware, which means stock (and rooted) ROM. Is there a forum for that in the development section or where could I get my hands on it?
Thanks!
Click to expand...
Click to collapse
I'm assuming you mean 4.1.2?
Edit: I found it, I don't know if the links work though. http://forum.xda-developers.com/showthread.php?t=2178482
From my Wicked S3 on SOKP
ShapesBlue said:
I'm assuming you mean 4.1.2?
Edit: I found it, I don't know if the links work though. http://forum.xda-developers.com/showthread.php?t=2178482
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
That was the right thread, the links were dead but took me to the right website, where I found this under archived devices:
http://www.scottsroms.com/downloads.php?do=file&id=511
Stock rooted 4.3 WITHOUT Knox, meant for people who haven't locked their device.
EDIT:
Just flashed, and WAHOOO Touch screen works well!
Thank you all so very much!
Related
As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?
Which rom did you flash?
Try lastest version of ics
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.
I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.
CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.
Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.
Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.
Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.
I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.
..
Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?
..
In ~November I used my moms upgrade and got the S3. I rooted and flashed CleanRom right away.
As far as I know the GPS on the phone never worked correctly and I had no idea how much I used the GPS feature. It always messes up and says I'm 100m+ away from where I actually am. I'll be driving and it constantly reroutes and says I'm on different roads. I can normally get to where I'm going but it is pretty dangerous while I am driving
Anyway, two days ago I dropped the phone and shattered the screen. I called Verizon and told them about the GPS and the screen and said since the screen was damaged the warranty was void and to call Samsung.
My question now is.... after I fix the glass, (which I'm already going to do, already bought the kit), do you think Verizon would warranty it still to fix the GPS?
Thanks.
PS. I have tried a lot to fix the GPS, including the screws by charger fix, reflashing the rom, etc.
sheamolt said:
In ~November I used my moms upgrade and got the S3. I rooted and flashed CleanRom right away.
As far as I know the GPS on the phone never worked correctly and I had no idea how much I used the GPS feature. It always messes up and says I'm 100m+ away from where I actually am. I'll be driving and it constantly reroutes and says I'm on different roads. I can normally get to where I'm going but it is pretty dangerous while I am driving
Anyway, two days ago I dropped the phone and shattered the screen. I called Verizon and told them about the GPS and the screen and said since the screen was damaged the warranty was void and to call Samsung.
My question now is.... after I fix the glass, (which I'm already going to do, already bought the kit), do you think Verizon would warranty it still to fix the GPS?
Thanks.
PS. I have tried a lot to fix the GPS, including the screws by charger fix, reflashing the rom, etc.
Click to expand...
Click to collapse
Have you tried other Roms I have noticed some are way off others spot on I'm on moar ATM and it is fairly accurate. I could not use clean ROM due to it being so inaccurate also kernel that is used can change the accuracy too.
mirrin said:
Have you tried other Roms I have noticed some are way off others spot on I'm on moar ATM and it is fairly accurate. I could not use clean ROM due to it being so inaccurate also kernel that is used can change the accuracy too.
Click to expand...
Click to collapse
I've honestly never tried any other rom except for CleanRom (I did try synergy, but it was only for about a day; and didn't try gps).
Any ROM suggestions? Would you recommend MOAR?
Did you try tightening the screws in the upper corner by the GPS antennae as well?
Also your warranty was voided the second you flashed clean Rom. You'd have to Odin stock to trick them. The screen shouldn't matter as long as the repair puts back an oem screen.
corbn89 said:
Did you try tightening the screws in the upper corner by the GPS antennae as well?
Also your warranty was voided the second you flashed clean Rom. You'd have to Odin stock to trick them. The screen shouldn't matter as long as the repair puts back an oem screen.
Click to expand...
Click to collapse
I 2nd the tightening of the screws. Mine phone was always awful with the GPS until I did that and its much much better
mirrin said:
Have you tried other Roms I have noticed some are way off others spot on I'm on moar ATM and it is fairly accurate. I could not use clean ROM due to it being so inaccurate also kernel that is used can change the accuracy too.
Click to expand...
Click to collapse
JFrawls said:
I 2nd the tightening of the screws. Mine phone was always awful with the GPS until I did that and its much much better
Click to expand...
Click to collapse
I tightened all of the screws, but focused on the bottom screws. Should the top screw (right next to headphone jack) also be tightened pretty well?
The only improvement i've ever seen is when I do the a-gps but i'm not even sure if it works - i think it may just be me thinking...
I have noticed the gps works a little better at night but again that could just be me thinking it does.
I think the way the phone is laid out the GPS receiver is in the top portion so those are the screws that you would want to tighten up for results
sheamolt said:
I've honestly never tried any other rom except for CleanRom (I did try synergy, but it was only for about a day; and didn't try gps).
Any ROM suggestions? Would you recommend MOAR?
Click to expand...
Click to collapse
Ive run just about every rom on the Sprint side..i always go back to The Peoples Rom. If u guys have it. Try it out. Just my pref. Wish i could help.
Sent from my SPH-L710 using xda app-developers app
sheamolt said:
I've honestly never tried any other rom except for CleanRom (I did try synergy, but it was only for about a day; and didn't try gps).
Any ROM suggestions? Would you recommend MOAR?
Click to expand...
Click to collapse
yeah i would also what modem are you running
mirrin said:
yeah i would also what modem are you running
Click to expand...
Click to collapse
Just tightened the upper screws. GPS is working a little better, will try tomorrow when I go to class.
Here's my about phone - http://imgur.com/NOJfPJD - not sure what modem I'm running
your on the vrlhe modem that one is an ics modem while your on jellybean flash this VRBMF1 this one is the latest and if your on any of the latest ota this is what you should be running.
mirrin said:
your on the vrlhe modem that one is an ics modem while your on jellybean flash this VRBMF1 this one is the latest and if your on any of the latest ota this is what you should be running.
Click to expand...
Click to collapse
Ok, will try. I forgot to use the gps earlier today but will try tonight. Do I just flash that zip through recovery?
sheamolt said:
Ok, will try. I forgot to use the gps earlier today but will try tonight. Do I just flash that zip through recovery?
Click to expand...
Click to collapse
Yes you do.
I am having trouble with my Galaxy S3 (SCH-I535), mainly the touchscreen does not respond to input, but still has a display. This all came about after I tried rooting and updating the ROM. I was able to successfully root and unlock bootloader, but then I tried doing a system update via the Stock ROM and upon a restart my touchscreen stopped working. I tried a factory reset from stock recovery and now I am stuck on the the screen that says Language selection English, Espanol, and some other languages. The 2 soft keys on either side of the home button respond to touch (make a noise and light up the screen, but do nothing for the screen I am on). Volume rocker works fine, I just cant move forward in the screen!! Like I said, I am able to get into stock recovery, as well as ODIN.
I bought this phone on eBay and just got it activated this past Thursday. Samsung told me the phone is out of warranty. The ebay seller said it came from Amazon and might have a receipt, but I'm not sure if that would even help anything. Can someone tell me what my options are in this situation? Screen replacement? Soft brick?
Thanks!
Anyone?
Bump
Any help is most appreciated...thanks!
I would Odin back to stock. Sounds like you updated to 4.3 so just Odin to 4.3 and factory reset after. If that does not fix it then it's a hardware problem. Do you have a warranty?
Sent from my SCH-I535 using Tapatalk
Galaxy S3 touchscreen not working
Sandman-007 said:
I would Odin back to stock. Sounds like you updated to 4.3 so just Odin to 4.3 and factory reset after. If that does not fix it then it's a hardware problem. Do you have a warranty?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'll try that, thanks!
No warranty...bought off eBay from a regular auction, not an agent or licensed retailer.
Still bricked...
Sandman-007 said:
I would Odin back to stock. Sounds like you updated to 4.3 so just Odin to 4.3 and factory reset after. If that does not fix it then it's a hardware problem. Do you have a warranty?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ODIN'd to the 4.3 file in this thread http://forum.xda-developers.com/showthread.php?t=2586319 and did a factory reset, still no screen response. Looks like a hardware issue after all. I think I am at 4.3, though because the menu background looks different and so was the bootup splash.
pinto4598 said:
ODIN'd to the 4.3 file in this thread http://forum.xda-developers.com/showthread.php?t=2586319 and did a factory reset, still no screen response. Looks like a hardware issue after all. I think I am at 4.3, though because the menu background looks different and so was the bootup splash.
Click to expand...
Click to collapse
Sounds like it. Sorry bud.
Sent from my SCH-I535 using Tapatalk
How severe a hardware issue?
So I definitely have a hardware issue, but is there anyway to determine how severe (read: costly) the issue is? If I'm looking at a simple screen replacement that is under $50 I might consider, but if we are talking a digitizer that is the cost of what I paid, then fugggetaboutitttt
Any way to determine this?
pinto4598 said:
So I definitely have a hardware issue, but is there anyway to determine how severe (read: costly) the issue is? If I'm looking at a simple screen replacement that is under $50 I might consider, but if we are talking a digitizer that is the cost of what I paid, then fugggetaboutitttt
Any way to determine this?
Click to expand...
Click to collapse
It's either the LCD or Digitizer. Definitely not the glass. If you get the whole Assembly (LCD and Digitizer) its around $130 just for the part. Your call. The glass panel is only $10 but your issue is the digitizer. Might be mobo (maybe).
This link include the the glass panel too but it's only worth $10. So LCD+Digitizer=$120
http://www.amazon.com/gp/aw/d/B00D5Y42LQ
Sent from my SCH-I535 using Tapatalk
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!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.
Did u over or under clock..flash a mod to control kernel? That's what it sounds like
I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Look under Tims sig
marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita
SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.
Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda
There's a way to diagnose it. Download an app called sensor on play store