This is starting to get a little frustrating...
Running CM 6.1.1 and i can't get my phone to stop randomly rebooting when i OC
i started all the way at max, and worked my way down to stock clock MHz. still getting random reboots.
but even at stock clock, i'm getting reboots. what's wrong with my phone?
i was thinking, maybe i should try using another kernel? can i use CM 6 with another OC kernel? i flash it just like a rom, right? any suggestions on which kernel to use?
IS IT A KERNEL PROBLEM? that's just my guess.
any help greatly appreciated.
gtmaster303 said:
This is starting to get a little frustrating...
Running CM 6.1.1 and i can't get my phone to stop randomly rebooting when i OC
i started all the way at max, and worked my way down to stock clock MHz. still getting random reboots.
but even at stock clock, i'm getting reboots. what's wrong with my phone?
i was thinking, maybe i should try using another kernel? can i use CM 6 with another OC kernel? i flash it just like a rom, right? any suggestions on which kernel to use?
IS IT A KERNEL PROBLEM? that's just my guess.
any help greatly appreciated.
Click to expand...
Click to collapse
When all else fails, wipe and reflash
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
When all else fails, wipe and reflash
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
i have wiped and reflashed. if i do it again, this shall be my 3rd attempt...
i really dont think it has to do with the flash...
gtmaster303 said:
i have wiped and reflashed. if i do it again, this shall be my 3rd attempt...
i really dont think it has to do with the flash...
Click to expand...
Click to collapse
Have you tried NB_Mod 2.15 or CR_Mod 2.13? Those are froyo stock roms (2.15 being the later version) and if those don't work on the stock kernel, stock clock, etc., then send it in to t-mobile.
MusicMan374 said:
Have you tried NB_Mod 2.15 or CR_Mod 2.13? Those are froyo stock roms (2.15 being the later version) and if those don't work on the stock kernel, stock clock, etc., then send it in to t-mobile.
Click to expand...
Click to collapse
that's the thing
my phone was working completely fine out of the box...
when i installed cyanogen, that's when my phone would randomly reboot
and i can't exactly send it to t-mobile, because i use it on AT&T.
not to mention, i bought this phone off ebay, so it doesn't have a warranty either
unless someone wants to give me a proof of purchase that i could borrow, HTC won't take a look at the phone
gtmaster303 said:
that's the thing
my phone was working completely fine out of the box...
when i installed cyanogen, that's when my phone would randomly reboot
and i can't exactly send it to t-mobile, because i use it on AT&T.
not to mention, i bought this phone off ebay, so it doesn't have a warranty either
unless someone wants to give me a proof of purchase that i could borrow, HTC won't take a look at the phone
Click to expand...
Click to collapse
But have you tried a stock t-mobile rom, to see if you still get the random reboots?
MusicMan374 said:
But have you tried a stock t-mobile rom, to see if you still get the random reboots?
Click to expand...
Click to collapse
a bit confused, sorry... when you say stock t-mobile rom, what i thought you meant was stock form. as in, out of the box. as i said in my previous post, the phone worked fine out of the box. those roms you mentioned are stock tmobile roms? i thought t-mobile didn't release froyo yet for the slide... would you like me to flash one of those roms you mentioned?
i went ahead and flashed NB_Mod 2.15. it's a solid rom, but a tad laggy...
that said, it has not reboot on me. what does that mean exactly?
please dont tell me i can't run cyanogen
i have noticed that my reboots are soft reboots.
the phone doesn't completely turn off. it simply goes back to the CM loading screen and shows the lock screen in a matter of a few seconds.
gtmaster303 said:
i went ahead and flashed NB_Mod 2.15. it's a solid rom, but a tad laggy...
that said, it has not reboot on me. what does that mean exactly?
please dont tell me i can't run cyanogen
i have noticed that my reboots are soft reboots.
the phone doesn't completely turn off. it simply goes back to the CM loading screen and shows the lock screen in a matter of a few seconds.
Click to expand...
Click to collapse
Soft reboots indicate software, if it was overclocking that was the issue it would be hard rebooting, or simply just freezing. I know you've already tried this, but try it one last time, wiping/factory reset and flash 6.1.1 stable. If it still reboots, (if it's reasonable) try to get a logcat right before the soft reboot, maybe we can find what's causing the reboot, an app maybe.
MusicMan374 said:
Soft reboots indicate software, if it was overclocking that was the issue it would be hard rebooting, or simply just freezing. I know you've already tried this, but try it one last time, wiping/factory reset and flash 6.1.1 stable. If it still reboots, (if it's reasonable) try to get a logcat right before the soft reboot, maybe we can find what's causing the reboot, an app maybe.
Click to expand...
Click to collapse
thank goodness for that. it's a great relief to hear that it's only a software problem. i can't tell you how scared i got lol....
i can wipe and reflash the phone again, but what's logcat? i will do as you say, but i would appreciate it if you walk me through. i've never used it before....
i used adb and typed in logcat, but i just got a mountain of garble...
not exactly sure where to go from here, or what i'm supposed to do.
gtmaster303 said:
thank goodness for that. it's a great relief to hear that it's only a software problem. i can't tell you how scared i got lol....
i can wipe and reflash the phone again, but what's logcat? i will do as you say, but i would appreciate it if you walk me through. i've never used it before....
i used adb and typed in logcat, but i just got a mountain of garble...
not exactly sure where to go from here, or what i'm supposed to do.
Click to expand...
Click to collapse
Yes, that garble is what I need to look at
Leave your phone plugged into your computer, type adb logcat, and wait for the phone to soft reboot. If you know how to trigger the reboot, trigger it, and then immediately press CTRL + C in command prompt, that is, immediately after you see the boot screen come up again. Then, right click the command prompt window, click select all, paste it into a text file, and upload it as an attachment in a reply here. I'll take a look and see if it's an app or something else causing it. Someone else probably (hopefully) also take a look at that text file and contribute to my conclusion.
MusicMan374 said:
Yes, that garble is what I need to look at
Leave your phone plugged into your computer, type adb logcat, and wait for the phone to soft reboot. If you know how to trigger the reboot, trigger it, and then immediately press CTRL + C in command prompt, that is, immediately after you see the boot screen come up again. Then, right click the command prompt window, click select all, paste it into a text file, and upload it as an attachment in a reply here. I'll take a look and see if it's an app or something else causing it. Someone else probably (hopefully) also take a look at that text file and contribute to my conclusion.
Click to expand...
Click to collapse
obviously, my phone decides to not reboot anymore once i plug it in...
ran the phone for roughly an hour.
i tried nearly everything to get a soft reboot, but no luck.
however, when i launched angry birds, the game would crash on me, and i would be brought back to the home screen, without warning. no force close notice.
i'm not sure how much help that would be, but i've attached that logcat file.
there is no ryhme or reason as to when my phone reboots. i'm assuming it has to be a background program or something, because none of the normal apps i use, show any patterns. the reboots occur whenever.
would i be able to just leave the phone plugged in, and keep logcat running, or do i have to be present when the reboot actually happens?
i don't mind running it overnight or something...
I'll take a look at the logcat when I'm on a computer, but the angry birds exit to home would probably happen if your phone has usb storage mounted and angry birds was on your sd card. Rebooting should fix that.
Can't leave it running overnight, since command prompt only saves and displays a certain number of lines.
My last suggestion would be to do a fresh install of cm7 or cm6, whichever, and install an app one by one, maybe like 5 a day or whatever, and see when the reboots start. Are there any apps that you use that are handling system stuff, like a task manager? Make a list of your installed apps and post it here, we can probably find what would be more likely than others.
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
I'll take a look at the logcat when I'm on a computer, but the angry birds exit to home would probably happen if your phone has usb storage mounted and angry birds was on your sd card. Rebooting should fix that.
Can't leave it running overnight, since command prompt only saves and displays a certain number of lines.
My last suggestion would be to do a fresh install of cm7 or cm6, whichever, and install an app one by one, maybe like 5 a day or whatever, and see when the reboots start. Are there any apps that you use that are handling system stuff, like a task manager? Make a list of your installed apps and post it here, we can probably find what would be more likely than others.
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
darn, i'm not sure if i got it...
it was like a unicorn sighting.
i went to plug my phone in for an adb logcat, and as soon as i plugged it in, the phone froze and soft rebooted. cmd was filling up with stuff fast, and i wasn't sure if i stopped it in time. in a panic, i forgot how to stop cmd, so i don't know if the error is present in this file.
i attached the text file
i will keep trying for another logcat until you report back. if the logcat is no good, i'll just do a fresh install.
i can provide you with a list of all the apps i run, but is there a way to generate a list? or would i have to type them out manually?
The angry birds logcat LOOKED like a missing lib, probably because the part of the app on the sd card wasn't being loaded. Did you try rebooting?
As for the second logcat, it looks like it MAY have been stopped too late, although, how many seconds do you estimate went by? Because whatever was running when the reboot occurred should stay there for around 10-20 seconds, but I can't completely be sure of that.
Actually, I can see a line that states that the boot had completed on line 124, and it looks like everything above that is post-reboot, sorry, you're gonna have to snatch another logcat :/
As for apps, I don't know of an efficient way of doing it, I know there's an app that exports a list of apps to a text file but for the life of me I can't remember what it's called.
Edit: It's called Zemna app list backup or something like that. Create a list of all apps, and then longpress the list and press send, you can send it to musicman374 at gmail.
MusicMan374 said:
The angry birds logcat LOOKED like a missing lib, probably because the part of the app on the sd card wasn't being loaded. Did you try rebooting?
As for the second logcat, it looks like it MAY have been stopped too late, although, how many seconds do you estimate went by? Because whatever was running when the reboot occurred should stay there for around 10-20 seconds, but I can't completely be sure of that.
Actually, I can see a line that states that the boot had completed on line 124, and it looks like everything above that is post-reboot, sorry, you're gonna have to snatch another logcat :/
As for apps, I don't know of an efficient way of doing it, I know there's an app that exports a list of apps to a text file but for the life of me I can't remember what it's called.
Edit: It's called Zemna app list backup or something like that. Create a list of all apps, and then longpress the list and press send, you can send it to musicman374 at gmail.
Click to expand...
Click to collapse
I just backed up my list of apps and sent it to you.
I will try getting a logcat within the next day or so. If i can't, I will wipe and we can take this through, so i don't mess anything up this time...
Alright, sounds good. And it doesn't look like any of those apps would be causing anything like soft reboots, in fact, I have most of them installed on my phone. Aside from AndroZip and ColorNote, I have all of those, so they definitely shouldn't be the culprit.
MusicMan374 said:
Alright, sounds good. And it doesn't look like any of those apps would be causing anything like soft reboots, in fact, I have most of them installed on my phone. Aside from AndroZip and ColorNote, I have all of those, so they definitely shouldn't be the culprit.
Click to expand...
Click to collapse
so then would wiping and reflashing my phone really solve the soft reboots?
this would be my 4th or even 5th attempt to get my phone to function properly (i lost count).
i don't mind, but my general concern is this...
i would be using the same recovery, with the same rom, and i would be installing the same apps again.
i'm guessing i'm going to have to get a logcat file anyway, unless by some miracle my phone decides to wok properly this time i flash... either that or find a better way of flashing roms
what would you have me do?
UPDATE: YES!
i managed to force my phone into a soft reboot. not exactly sure what i did, but i just kept opening and closing random apps on my phone.
logcat 2. i wasn't sure when exactly i was supposed to stop the file, because CMD was filling up fast. hopefully i nabbed it. i stopped cmd, just a few seconds before the screen went back to the CM loading logo.
did i do it right???
logcat 3 happened when the phone was just sitting still. was not provoked. sorry, i don't want to hammer you with logcat files, but it has been so hard for me to get a logcat. so i'm trying to get every one i can.
please let me know
I was relieved to see the same error messages in your logcat as I see on my wife's slide.
W/SharedBufferStack( 5177): waitForCondition(LockCondition) timed out (identity=2, status=0). CPU may be pegged. trying again.
Click to expand...
Click to collapse
It's possible that we both have a hardware issue, but just FYI, this happened on my wife's original slide, and it's happening on the refurbished warranty replacement we just got.
From searching on the web, it appears that this problem may be caused by openGL. I don't think the stock roms use it, or at least not the newer version like CM does.
you didn't post your application list, but i've had my wife's phone crash while just booting up and sitting at the thunderstorm (free) LWP, which would be the only thing using openGL. I'll have to disable it for a few days and see if that solves it.
umaro said:
I was relieved to see the same error messages in your logcat as I see on my wife's slide.
It's possible that we both have a hardware issue, but just FYI, this happened on my wife's original slide, and it's happening on the refurbished warranty replacement we just got.
From searching on the web, it appears that this problem may be caused by openGL. I don't think the stock roms use it, or at least not the newer version like CM does.
you didn't post your application list, but i've had my wife's phone crash while just booting up and sitting at the thunderstorm (free) LWP, which would be the only thing using openGL. I'll have to disable it for a few days and see if that solves it.
Click to expand...
Click to collapse
i'm not so relieved now... this phone doesn't have a warranty... and if it's hardware, houston we have a problem
I'm not running any applications out of the ordinary.
i attached an app backup list from my phone
UPDATE: apparently, my phone is covered under warranty, even though i bought it off ebay.
i called up HTC and they didn't even ask for proof of purchase or anything. so hardware problem? bring it on.
but the problem still persists regardless...
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
matt2053 said:
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thats what i suspect. Its just a pain to have been waiting for 4 days for something that probably wont fix anything and then to have to start the whole thing over again with samsung. O well
stanleywinston said:
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
Click to expand...
Click to collapse
Deal with the retailer you bought the phone from, and get a replacement from them.
oscillik said:
Deal with the retailer you bought the phone from, and get a replacement from them.
Click to expand...
Click to collapse
I'll give it a go. Im guessing they wont do a doorstep swap like i'd get from t mobile though. Hopefully i wont be without it for long. In our short time together i've grown quite attached to this phone (and almost got used to not touching the volume button)
Couple of questions (you may have already done these -apologies if you have)
Have you tried a factory reset? If not, maybe worth trying it, could be an app doing wierd things.
Also, try running a logcat trace when replicating the issue - see if it helps point in the direction of the issue.
Does the phone still crash when you're in the bootloader? (This _may_ help to rule out application related issues)
I have tried a factory reset. Weird thing is that im pretty sure that it didnt do it for the first few hours that i was playing with it. It was just at the point that i had it all set up that i first noticed it so assumed it was a rouge app and did a factory reset. When it rebooted i signed in and hit volume and it crashed so its definately not an app.
I almost believed that it was the normal volume bug because if i go somewhere more remote in the house, away from all electrical stuff, i can hammer at the buttons for a while before it crashes so maybe ive just got a more extreme version of the bug. Just noone else seems to have anything close. Volume control works fine in a call and when the screen is off but i havent tried in bootloader yet. I'll give it a go
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
waltcoleman said:
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
Click to expand...
Click to collapse
Any special wi-fi config? (That's the culprit in my case.)
garwynn said:
Any special wi-fi config? (That's the culprit in my case.)
Click to expand...
Click to collapse
No...never installed the hotspot hack, did have foxfi installed, but did not reinstall after reloading ff18.
im also having the same problem as well, and the problem has became worse and worse,what started off as once or twice a day,is now at least occurring every 10 min.I think im about to downgrade right now to stock gingerbread and see what happens
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
rocket321 said:
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
Click to expand...
Click to collapse
U can always unroot back to el29(gingerbread)i was having the same problems and now i can enjoy my phone
Sent from my SPH-D710 using xda premium
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
R0CKSTAR3N3RGY said:
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The power button seems to be a common cause of random reboots and that's what I'm leaning towards now as no other software fix has resolved the problem. Supposedly Sprint ordered me a replacement to swap out phones. I'd definitely recommend trying a different Kernel if on FF18 and if that doesn't fix it, try rolling back to EL29.
Question, does anybody know what exactly causes the SSODs in the JB ROMS? Just curious. I've had them happen in the MOST UNWANTED times. Like, I'll be recording a video. Then suddenly the phone will freeze, then either reboot or shut off. I would then have to take the battery out and put it back in. To turn the phone back on.
pwner5889 said:
Question, does anybody know what exactly causes the SSODs in the JB ROMS? Just curious. I've had them happen in the MOST UNWANTED times. Like, I'll be recording a video. Then suddenly the phone will freeze, then either reboot or shut off. I would then have to take the battery out and put it back in. To turn the phone back on.
Click to expand...
Click to collapse
If the source of the problem was known I'm sure it would already been fixed
Sent from my SGH-T989 using Tapatalk 2
meh, alright.
VoiD_Dweller said:
If the source of the problem was known I'm sure it would already been fixed
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Well, not necessarily. First thing is find out what is causing them. Second, will be what can be done with said cause to fix it, without breaking anything. Though, once the cause is revealed, im sure it wont take to long to fix the issue.
note to the op don't remove the battery, you can damage your phone.. just hold the power button, it will restart..
LoopDoGG79 said:
Well, not necessarily. First thing is find out what is causing them. Second, will be what can be done with said cause to fix it, without breaking anything. Though, once the cause is revealed, im sure it wont take to long to fix the issue.
Click to expand...
Click to collapse
Yea I think the two of you are saying the same thing.. Its basically recognize issue and these smart developers for android will squash the bug. The thing that gets me is the question. Like in typing it do you really think that as long as the bug has been out that if someone knew what to do it would not of been done? Also if you check the changelogs you see countless kernel fixes that shows they are trying everything. What needed to be done in this case is trying to understand the changelogs and commits so you better educate yourself on Android
The biggest annoyance for anyone wanting to mess with less-than-stable ROMs is that you really can't tell what's going to cause it. As with any other software/OS/whatever it is completely dependant on what you have done to the phone. The minute you begin adding apps or configuring your phone to anything other than the exact way it comes, you are causing your own unique set of test criteria.
Obviously there are gray areas in all of this, and customizations can often even assist in the understanding of what causes failures, but the bottom line is that it's up to you just as much as it is up to the stability of the ROM.
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