Related
Hello,
I had random reboot before with my leedroid 2.3b, and I had one also 30 minutes ago with AuraxTSense, so I'm asking if the cause is the rom or not.
When he reboot, he's not hot, I see it reboot sometimes and the phone was at normal temperature (approximately with my hands lol). it reboots max 1 time per day.
So I'm tellng myself that's it could be due to:
- radio
- S-OFF
- one app
For radio, I try tu update from 32.48.00.32U_5.11.05.14 to 32.47.00.32U_5.10.05.23, and I'll see.
For apps, the problem is that I would have not to restore all my apps, to see if one app cause it.
What do you think of it?
Thanks
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
Or as fnotsje said, could be hardware related
fnotsje said:
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Click to expand...
Click to collapse
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
eden2812 said:
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
It's installed but not configured in smatass mode, you advise me to uninstall it and to test?
Or as fnotsje said, could be hardware related
Click to expand...
Click to collapse
What is surprising, that if it's that, i t should reboot many more times than one time per day no?
Thanks
thierry_b said:
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
Click to expand...
Click to collapse
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
fnotsje said:
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
Click to expand...
Click to collapse
Yes and always only one time per day, just one time maybe 2.
I desinstalled SetCPU, it changes nothing.
What do you advise me to do?
Wipe and install minimum apps, and see if I've that, and little by lttile, reinstall one new app...test few days again...?, it will be long :-(
Thanks.
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
GoogleJelly said:
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
Click to expand...
Click to collapse
With the minimum of apps, for example to see if it reboot or not?
Because if t's an hardware problem due to the radio, it censed to reboot even with few apps no?
For carrier as I'm at Orange like you, I think, they could change fastly my phone maybe. I will try that if anything works. You think that if I do that, I've to find an orange rom? I'm asking myself if they accept an HTC even restored with RUU.
Thanks
I have the same issue and ITS DRIVING ME MAD!!!!!!!!!!!!
I never experienced this with my stock ROM... so I firstly tried a gingerbread ROM... when it started... i then moved to a Sense Rom and still reboots occured... I'm now on my 2nd cooked sense ROM and still having reboots!!
WTF? is there a quick sollution?
thank you!
SO MANY follks seem to be having problems with [email protected]! Is there seriously no sollution to this or a common cause..?
had the same problem & is with HTC getting fixed
there are a few posts about it if you search - the only fix seems to be to send it to HTC for a new motherboard as some presume that it's overheating.
11 march still waiting on return of my Desire
I can relate to your issues. Mine kept rebooting when I tried to use the GPS. Like you I had mine rooted, S-off and was using a custom ROM.
After many tests, I downloaded a stock RUU, installed a different navigation app and once again, it rebooted.
Bottom Line: take it back. Its probably defective. Just make sure you're running a stock ROM. Download an RUU.
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
Alright, so my girlfriend's Samsung Galaxy S II started to go through these weird partial reboots several weeks ago (maybe even months). The phone would randomly go black, play the stupid shutdown/startup (dont remember which) jingle...then just simply be at the lock screen with a crossed out circle where the signal bars would be (for just a couple of seconds). When this happened, I used to just tell her to shutdown the phone, take out the battery, and let it sit for about 30 seconds, then put everything back together and start it back up. This seemed to work, which made me think it might have just been a software or at worst a memory issue of some kind.
This issue was always intermittent, but now, no matter what I do, it just keeps looping this "restarting" problem. I can't access any internal memory space from my computer because in the time it takes to connect, it just "reboots" again. I made a logcat of the phone up until the "reboot", and in doing so noticed that when I would browse the phone via adb shell, I saw no mount for the sd card...which then lead me to believe maybe it was an issue with that. I checked the sd card for corruption (and prior to even using it, checked that all blocks were read/writable (legit)), but that led nowhere.
Anyways, not having any idea where to go next, nor where to begin or what to look for in the 5000+ lined logcat, I turn to xda with hopes of getting some sort of help. Thanks in advance for any I get!
EDIT: Oops, some other important notes I didn't mention (other than in title); this is running stock firmware, only OTA. I tried once to upgrade her to ICS via Kies, but the upgrade would never complete. She also refused to let me root her phone...so unless there is a stock recovery mode, her phone has none...
bump, as its been a week and no responses. If anyone has any ideas or can figure out whats wrong from the logcat, please help.
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Sent from my SGH-T989 using Tapatalk
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
For starters, thanks everyone for the responses! After this long, its really great to see so many in one day!
richardlibeau said:
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Click to expand...
Click to collapse
Thats what I thought, because it seemed to get exceptionally hot before "rebooting"...at first...then I was noticing it "rebooting" when clearly cold. If it is indeed overheating like I had thought in the very beginning, is there anything I can do about it? What does it use for heat conductivity and displacement? And for that matter, I would think if it was overheating though, it would actually reboot, not the half-ass semi-reboot its been doing...
And what is wakelock exactly that it would cause an issue? Only apps I see using it are WootWatcher, KeyguardViewMediator and PowerManagerService.
krazierokz said:
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Click to expand...
Click to collapse
I would use odin...but the phone doesn't stay on long enough to do much of anything before "rebooting". Also, she is already using stock firmware + OTA updates. And her contacts are not what I am worried about, its her photos and such. This is the very reason why I hate internal memory for phones...
And I'm pretty sure its not a sticky power button, I had seen that being a common issue when researching before posting. And again, if I have not been clear, its not exactly "rebooting", just semi-rebooting; phone starts up, crap starts running, a min or 2 later, phone acts like its restarting (plays sound and all), then just comes back to the lock screen immediately...I can't really describe it much more than that.
And no, I'm not familiar with "download mode"
bzlik88 said:
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Click to expand...
Click to collapse
Ya, like I said in the reply above this, I don't think its the sticky power button problem...but I could always be wrong. I only didn't mention over heating because I felt I did a good job of ruling it out.
DeliciousLimeJuice said:
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
Click to expand...
Click to collapse
Its running GB atm, never updated to ICS via Kies...
I wish I could help you further but i can say one thing, the rebooting that your describing is called a "hot reboot". I know what ur talking about and others will too if u use that term. Good luck.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Im new in this nexus section...i'm asking why my galaxy nexus sometimes reboots? It has the latest 4.2.2 android version stock...it isnt the update, i think, because also before this happen...and when it reboots there's like a opened locket under the google logo....who can help.me? I tried also the nexus toolkit...but when i try to do something with fastboot the program says WAITING DEVICE forever...
Guys, please help!! Its really urgent!
Hi,
I think there are two reasons for random reboots:
1- overheating
2-lack of ram (many running proceses, so ram gets full, so it reboots.
Press the thanks button if I helped
blakstar said:
Hi,
I think there are two reasons for random reboots:
1- overheating
2-lack of ram (many running proceses, so ram gets full, so it reboots.
Press the thanks button if I helped
Click to expand...
Click to collapse
No, even when the battery isnt hot it reboots!!
and it is without any apps installed, only stock apps!! I did also a factory reset from settings..but nothing happened...
Searching on net, i read that the opened locket is the bootloader....is that causing random reboots? If yes, how to relock with toolkit? Beacause it says me WAITING DEVICE
isko95 said:
No, even when the battery isnt hot it reboots!!
and it is without any apps installed, only stock apps!! I did also a factory reset from settings..but nothing happened...
Searching on net, i read that the opened locket is the bootloader....is that causing random reboots? If yes, how to relock with toolkit? Beacause it says me WAITING DEVICE
Click to expand...
Click to collapse
No, unlocking the bootloader shouldn't do this. I have an unlocked bootloader, and I have this phone(xperia arc) for 5 months and I only had one random reboot and it was definitely because of lack of ram
blakstar said:
No, unlocking the bootloader shouldn't do this. I have an unlocked bootloader, and I have this phone(xperia arc) for 5 months and I only had one random reboot and it was definitely because of lack of ram
Click to expand...
Click to collapse
Yes but im talking about NEXUS and maybe its different!!
I used to have that happen all the time. I used to think that the phone sucked but my husband never had that happen with his. I compared the apps and wiped my phone, only installed what he had on there. It still happened. I was really beginning to get mad but I wiped it again. I Installed things one by one only allowing myself to install a new app only after it had gone a week with no nonsense. Yes, this was a painful process but I found the cause of my random reboots. I use Handcent. That alone isn't the cause. When I would get new sounds for my GN, I would have the option of making them a ringtone or a Handcent notification among other things. If I made Handcent notifications, that seemed to cause the problem. If I move a sound into the notifications folder and assign it to contacts in Handcent, everything has been fine.
I don't know if this helps your problem but some settings could affect unexpected things. Good luck!
Sent from my Xoom using xda premium
3devious said:
I used to have that happen all the time. I used to think that the phone sucked but my husband never had that happen with his. I compared the apps and wiped my phone, only installed what he had on there. It still happened. I was really beginning to get mad but I wiped it again. I Installed things one by one only allowing myself to install a new app only after it had gone a week with no nonsense. Yes, this was a painful process but I found the cause of my random reboots. I use Handcent. That alone isn't the cause. When I would get new sounds for my GN, I would have the option of making them a ringtone or a Handcent notification among other things. If I made Handcent notifications, that seemed to cause the problem. If I move a sound into the notifications folder and assign it to contacts in Handcent, everything has been fine.
I don't know if this helps your problem but some settings could affect unexpected things. Good luck!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I did factory reset twice from device's settings, but nothing.
no one who can help? wow!!
I had random reboots on my Verizon GN running the OTA 4.1.1. I got so fed up with it that I went back to 4.0.4. I have had no problems or reboots since doing this.
Are you running Chrome or the stock browser? I've always had the random restarts on my N10, but only started seeing them on my GN after I started using Chrome around the time 4.2.2 came out.
gforce1963 said:
I had random reboots on my Verizon GN running the OTA 4.1.1. I got so fed up with it that I went back to 4.0.4. I have had no problems or reboots since doing this.
Click to expand...
Click to collapse
Reaally? How did you get back to 4.0 ics?
OP, read the return to stickied thread on general forum by efrant, if your problems still happen after restoring back to stock through fastboot, then you may have faulty hw.
Sent from my Nexus
bk201doesntexist said:
OP, read the return to stickied thread on general forum by efrant, if your problems still happen after restoring back to stock through fastboot, then you may have faulty hw.
Sent from my Nexus
Click to expand...
Click to collapse
why when i try to do something with nexus toolkit it says waiting for device?
Heeeeeeeeelp heeeeeeeeeeelp!
why no one can help in here?!?!?!
Do dmesg or logcat, maybe we can help resolving your problem or you can ask your phone service.
Sent from my MT27i using my finger
ahlulnugraha said:
Do dmesg or logcat, maybe we can help resolving your problem or you can ask your phone service.
Sent from my MT27i using my finger
Click to expand...
Click to collapse
How to make logcat??
Really a few people answers!
Bk201 handled it as always. Follow his suggestion. If that can't help you it must be PEBKAC.
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)
felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.
Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app
So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app