Hi everyone,
I acquired a Galaxy S4 that apparently worked but had a broken screen. I replaced the screen and initially seemed to work but quickly noticed it keeps crashing and restarting. It seems to happen after it has been on about 20 minutes, it can work fine, I tested with youtube videos and the longest it worked for was 30 minutes before freezing. Sometimes it can crash even as it is starting up.
Most times it crashes the screen will freeze and completely lock up the device for a few seconds, then turn off, vibrate and restart. Rarely but sometimes, the graphics on the screen will turn different colours and show lines just before restarting.
I have updated the firmware via Odin using a stock rom from sammobile, I have not tried doing anything to the kernell.
The last thing I tried is to clean the motherboard PCB with some PCB cleaner and did a low temperature (about 200degC) attempt at a reflow, but I don't think I did anything long enough to solve any potentially dry or cracked joints as I was worried I would just damage the motherboard all together.
I suspect it would be a dry joint but I have no idea.
I would absolutely love to have this phone working, can anyone offer any advice?
many thanks,
Graham
I'm sure it's not helpful at all, but it sounds like an overheating issue. Does the device get hot before it reboots?
My old Galaxy Nexus experienced these issues after I flashed and overclocked it, and changed the governor. It would get so hot it was almost uncomfortable to touch. Then it would reboot and would be fine for about an hour. Rinse and repeat.
Just as a test, Liquid stable just released, so maybe try flashing that through goo manager and then use performance control to underclock the processor. See if the amount of time between reboots increases?
citenx said:
I'm sure it's not helpful at all, but it sounds like an overheating issue. Does the device get hot before it reboots?
My old Galaxy Nexus experienced these issues after I flashed and overclocked it, and changed the governor. It would get so hot it was almost uncomfortable to touch. Then it would reboot and would be fine for about an hour. Rinse and repeat.
Just as a test, Liquid stable just released, so maybe try flashing that through goo manager and then use performance control to underclock the processor. See if the amount of time between reboots increases?
Click to expand...
Click to collapse
Thank you, it does not get hot at all before freezing. I will give liquid stable a go when I finish work, can't hurt to try!
citenx said:
I'm sure it's not helpful at all, but it sounds like an overheating issue. Does the device get hot before it reboots?
My old Galaxy Nexus experienced these issues after I flashed and overclocked it, and changed the governor. It would get so hot it was almost uncomfortable to touch. Then it would reboot and would be fine for about an hour. Rinse and repeat.
Just as a test, Liquid stable just released, so maybe try flashing that through goo manager and then use performance control to underclock the processor. See if the amount of time between reboots increases?
Click to expand...
Click to collapse
Just as a side note, GPS is buggy and handsfree headphones won't work for me. If you decide to flash, turn off wifi locationing and then GPS will work.
citenx said:
Just as a side note, GPS is buggy and handsfree headphones won't work for me. If you decide to flash, turn off wifi locationing and then GPS will work.
Click to expand...
Click to collapse
I just tried to put liquid stable on my phone, did not try via goomanager since I don't have it, but sent it as an adb sideload while in cwm recovery, it failed to install and now my phone does not turn on, just stuck on Samsung logo, so now I am reflashing stock rom again.
thanks
I have it turning on again now, but most times it actually freezes on the loading screen and half way through the welcome noise. I will test how long it can survive in recovery mode.
When it did turn on I went into camera and started recording to see how long it would last. Strangely enough it crashed during recording but the camera itself was still working and the screen was updating with the camera, however all buttons were unresponsive, the home and return buttons wouldn't even light up, and the recorder time was stuck on 4 seconds. I had to turn it off by holding the power button for about 10 seconds.. maybe this could be useful information for someone to diagnose?
graham0122 said:
I just tried to put liquid stable on my phone, did not try via goomanager since I don't have it, but sent it as an adb sideload while in cwm recovery, it failed to install and now my phone does not turn on, just stuck on Samsung logo, so now I am reflashing stock rom again.
thanks
Click to expand...
Click to collapse
I just noticed from a different post on the Liquid 2.4 thread that the original post was for GSIII (WTF?). If you feel lucky and want to try again, here's the link off of goo and the MD5 is 72b3e6cc79f298f85b8e21f99a990b90.
---------- Post added at 02:34 PM ---------- Previous post was at 02:19 PM ----------
graham0122 said:
I have it turning on again now, but most times it actually freezes on the loading screen and half way through the welcome noise. I will test how long it can survive in recovery mode.
When it did turn on I went into camera and started recording to see how long it would last. Strangely enough it crashed during recording but the camera itself was still working and the screen was updating with the camera, however all buttons were unresponsive, the home and return buttons wouldn't even light up, and the recorder time was stuck on 4 seconds. I had to turn it off by holding the power button for about 10 seconds.. maybe this could be useful information for someone to diagnose?
Click to expand...
Click to collapse
And the only thing wrong with it was the screen? Two days after I got my S4 I went hiking and got it wet (shame on me) but the unresponsiveness sounds just like water damage. Are any of the moisture sensors tripped?
citenx said:
I just noticed from a different post on the Liquid 2.4 thread that the original post was for GSIII (WTF?). If you feel lucky and want to try again, here's the link off of goo and the MD5 is 72b3e6cc79f298f85b8e21f99a990b90.
---------- Post added at 02:34 PM ---------- Previous post was at 02:19 PM ----------
And the only thing wrong with it was the screen? Two days after I got my S4 I went hiking and got it wet (shame on me) but the unresponsiveness sounds just like water damage. Are any of the moisture sensors tripped?
Click to expand...
Click to collapse
The screen is perfect, no moisture sensors tripped. I know the screen was a working one, and as far as I am aware the only problem with this phone is the screen was smashed. I have checked the motherboard and it doesn't seem to be damaged. But if it was I would expect it not to work at all?
The crashing doesn't seem to be due to holding it or moving it, it just happens regardless if its resting untouched etc.
It has now restarted about 10 times in the past few minutes, sometimes as soon as I hear the vibrate to signal it is turning on, because it vibrates 2 or 3 times in the space of a few seconds.
It definitely seems to be getting worse!
It seems to sit in recovery mode as long as it likes though..
Related
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
hpcolombia said:
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
Click to expand...
Click to collapse
I had it happen to me once, when I first got the phone. Exactly as you described, except I had to battery pull. I was using an app called Screen Filter, so I could dim the capacitive lights. I figured it had to do with that app, so i removed it. I haven't had it happen since. I'm not sure if it was Screen Filter that caused it or not, but I haven't had it happen again since I removed it. Either that, or just a coincidence.
Happened to me once when I was messing with a root script that had a bug. Ended up clearing some of my app data too. Seems like a common "brain death" state that the phone can get into. I'm pretty sure it's software related and nothing to worry about.
Mike
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Started happening to me after i installed either switkey x or the amazon app, i am not sure but i think that's what caused it
SwiftKey works fine for me... try reinstalling it. Same far any other apps that cause issues, make sure the download was good and reinstall.
If the phone freezes, remember that the only ways to get a try restart is a dead battery or battery pull. Wifes phone froze and shut off, would not restart until a battery pull.
Good luck!
Sent from my phone
Happens to me too and it is really irritating.
GhettoBSD said:
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Click to expand...
Click to collapse
It works perfect for dimming (well turning off) the buttons, check your settings!
so i keep having the same problem even without the swiftke y installed tried to reboot and even factory reset no luck. did you find any solutions.
used to happen a lot when i had aosp roms on my old hero
Are you guys overclocked?
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
iliapiano said:
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Damn....I may have to do that. Sprint allowed you to exchange with no hassle? It seems to happen so randomly that I don't think my Sprint Store will exchange it if they can't reproduce it.
freeza said:
Are you guys overclocked?
Click to expand...
Click to collapse
My wife was oc when hers froze
Sent from my phone
I'm overclocked but the issue @ hand is software related. When I had the OG Evo, certain kernels would cause the screen to act in the same matter stated in the op. A lot of bugs that people report would be resolved once we get perm. Root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
SO this has happened to me and I am freaking out thinking its the aosp rom. how long did it take for the screen to light up again. it been like two hours for mine.
I've had this phone for about 2 weeks now and I'm starting to have this weird problem. The phone is not rooted and nothing has been done to it. Every time I place a call, the phone will go black and it'll stay like that even after the person hangs up. I can't press the home button or power button! So I tried some things! I downloaded watchdog to see if any of my apps were causing this, didn't work. Next thing I did was install the XXKI3 (2.3.5) upgrade with ODIN, went smoothly but problem still occurs. Then lastly I factory restored the phone and it went fine but it the problem still occurs...
I don't know if this could be the problem but I went to a Ghost Armor kiosk and had them install a screen protector for me (yesterday). The phone worked fine before I had it installed!
Another thing, when I place the call, my sensor turns red and it stays like that.
PhiChong said:
I've had this phone for about 2 weeks now and I'm starting to have this weird problem. The phone is not rooted and nothing has been done to it. Every time I place a call, the phone will go black and it'll stay like that even after the person hangs up. I can't press the home button or power button! So I tried some things! I downloaded watchdog to see if any of my apps were causing this, didn't work. Next thing I did was install the XXKI3 (2.3.5) upgrade with ODIN, went smoothly but problem still occurs. Then lastly I factory restored the phone and it went fine but it the problem still occurs...
I don't know if this could be the problem but I went to a Ghost Armor kiosk and had them install a screen protector for me (yesterday). The phone worked fine before I had it installed!
Another thing, when I place the call, my sensor turns red and it stays like that.
Click to expand...
Click to collapse
the screen protector might be interfering with your proximity sensor making the phone think you still have it held to your head.
PhiChong said:
I've had this phone for about 2 weeks now and I'm starting to have this weird problem. The phone is not rooted and nothing has been done to it. Every time I place a call, the phone will go black and it'll stay like that even after the person hangs up. I can't press the home button or power button! So I tried some things! I downloaded watchdog to see if any of my apps were causing this, didn't work. Next thing I did was install the XXKI3 (2.3.5) upgrade with ODIN, went smoothly but problem still occurs. Then lastly I factory restored the phone and it went fine but it the problem still occurs...
I don't know if this could be the problem but I went to a Ghost Armor kiosk and had them install a screen protector for me (yesterday). The phone worked fine before I had it installed!
Another thing, when I place the call, my sensor turns red and it stays like that.
Click to expand...
Click to collapse
Hi,
It has to be firmware issue. but its really weird.. ...indeed
When the proximity sensors turns red - it means that it is activated (operational). If it stays red all the time - something is wrong. I would recommend turning the proximity sensor off (in settings/call). And as a final fix i would consider flashing another firmware. If you want to stay in official FW, see this: http://forum.xda-developers.com/showthread.php?t=1075278. Pick a FW of your choice and flash it using few easy steps. When you follow the steps carefully - nothing wrong will happen ;-) I can recommend XWKI4 official firmware. its better than stock 2.3.5 so far.
---------- Post added at 03:15 PM ---------- Previous post was at 03:10 PM ----------
damn it... sorry for my previous post ;-) I was not reading carefully ... you know... noobs ;-) But the last sentence about recommended official FW is nothing but true ;-)
Thanks guys! I found the issue. It wasn't the firmware (thanks for helping though), it is actually the screen protector! I took off the Ghost Armor screen protector and bam it worked, lol. What a waste of money..$20 bucks for the screen protector and it serves no purpose but a hindrance to my phone. I slapped on a cheap screen protector I got from my phone case and it covers the sensor but the material doesn't block the sensor.
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
void4ever said:
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
Click to expand...
Click to collapse
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
blazingwolf said:
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
Click to expand...
Click to collapse
Just factory reset it, skipped setup completely and started making calls, same issue. You maybe right about the sensor though. The first call acted up like i explained. The second call the screen was staying on like i expected, but once i switched speaker phone off and then back on the screen shut off and started acting like call one again.
I just got this phone 6 hours ago i wonder how hard it will be to convince verizon there's a hardware fault. I guess i'd better unroot it and remove recovery so i can call in the morning.
Void4ever
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
void4ever said:
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
Click to expand...
Click to collapse
There are directions in the RUU that will explain all of the steps. You will connect your phone with the USB cable.
It shouldn't be to hard to convince them. Just show them the steps you did to reproduce the issue. Good luck.
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
void4ever said:
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
Click to expand...
Click to collapse
No problem. Glad you got a new one coming.
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Good to hear man. Enjoy that puppy.
void4ever said:
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Click to expand...
Click to collapse
Awesome.
Sent from my ADR6410LVW using Tapatalk 2
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
jfall said:
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
Click to expand...
Click to collapse
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
suyash1629 said:
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
Click to expand...
Click to collapse
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
jfall said:
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
Click to expand...
Click to collapse
Strange issue.. never had it ever, m flashing CM from more than a year.. Try to do a new flash downloading new files..
Hey,
i am having some trouble with my Le Max 2. My screen does not wake up anymore, but the phone is still active. This especially takes place, when the screen is off for more than 5 minutes or so. Then i only get a black screen and hear the unlocking noise, but i cannot see the content any more. Backlight is working, but only a black screen. Whatsapp Web, etc. still works when the screen wont turn on. The only thing i can do then is to press the power for 10s to force a restart. Then everything works like a charm until the screen is of for a specific time.
I already flashed new ROMs (RR Nougat, MIUI Marshmallow) both dirty and clean. Also did multiple full wipes. problem is still there. Anybody of you already had something similar?
Do you think its HW or SW related?
Thank you so much
Kampfgans said:
Hey,
i am having some trouble with my Le Max 2. My screen does not wake up anymore, but the phone is still active. This especially takes place, when the screen is off for more than 5 minutes or so. Then i only get a black screen and hear the unlocking noise, but i cannot see the content any more. Backlight is working, but only a black screen. Whatsapp Web, etc. still works when the screen wont turn on. The only thing i can do then is to press the power for 10s to force a restart. Then everything works like a charm until the screen is of for a specific time.
I already flashed new ROMs (RR Nougat, MIUI Marshmallow) both dirty and clean. Also did multiple full wipes. problem is still there. Anybody of you already had something similar?
Do you think its HW or SW related?
Thank you so much
Click to expand...
Click to collapse
Have you tried to change your firmware? Kernel? Try going back to stock?
Supertacomonkeyexplosion said:
Have you tried to change your firmware? Kernel? Try going back to stock?
Click to expand...
Click to collapse
I tried going back to stock. But i am pretty sure now its some HW issue. The screen just wont turn on when the phone itself is cold. When i pull it out of my pocket and its kinda warm, it works like a charm.
But if it is sitting on the table / i have it in my hands outside - the screen wont turn on anymore. If its too cold it wont even reboot...
Stange problem - could there be any loose solderings or something?
Kampfgans said:
I tried going back to stock. But i am pretty sure now its some HW issue. The screen just wont turn on when the phone itself is cold. When i pull it out of my pocket and its kinda warm, it works like a charm.
But if it is sitting on the table / i have it in my hands outside - the screen wont turn on anymore. If its too cold it wont even reboot...
Stange problem - could there be any loose solderings or something?
Click to expand...
Click to collapse
I have no idea about that. Sorry.
Especially since it was fine, and is hit and miss with the problem.
Is it within warranty?
Supertacomonkeyexplosion said:
I have no idea about that. Sorry.
Especially since it was fine, and is hit and miss with the problem.
Is it within warranty?
Click to expand...
Click to collapse
Nope i am out of warranty
I guess that the display is defect or maybe some connectors are loose or something...