So I managed to get my phone back up and running... to a degree... but it is randomly locking up and rebooting when being used randomly. It seems like its an overclock problem where if your trying to push it too hard it locks and reboots but I'm having this problem on complete stock with no oc or uv. Any suggestions?
What happened to your phone? What rom and kernel are you running?
It just randomly started doing what I described in my prior post. Its doing it on every Ron and kernel combo I use, including stock...
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
It just randomly started doing what I described in my prior post. Its doing it on every Ron and kernel combo I use, including stock...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Well...it sounds like you might have to odin back to stock and see about getting a replacement from your carrier.
That's no issue I've ever heard of :/
Related
Any one know of anything else I can do with my fascinate. Running 1.1 Zinc with no kernel. My phone does not approve. Anything I'm missing out on?
zachsx said:
Any one know of anything else I can do with my fascinate. Running 1.1 Zinc with no kernel. My phone does not approve. Anything I'm missing out on?
Click to expand...
Click to collapse
I wouldn't approve of that, either!
Seriously, if you were able to flash a ROM, and you did it through Clockwork Recovery/ROM Manager, then you are running a modded kernel.
Voodoo seems to be causing some people more trouble than they feel it's worth, so I'd suggest one of jt1134's or Dirrk's non-Voodoo kernels, or Birdman's once it's past the testing stage.
Non-voodoo? I must have missed those. Search is not being my friend. Care to link a guy up? The only kernel threads I can find are their voodoo kernels.
Sent from my SCH-I500 using Tapatalk
PhoenixPath said:
Non-voodoo? I must have missed those. Search is not being my friend. Care to link a guy up? The only kernel threads I can find are their voodoo kernels.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
swing by irc #samsung-fascinate on freenode.net. check topic for kernel links
My phone started lagging badly 3 days after the vodoo lagfix...how ironic. When I disabled it, it nearly bricked my phone. Desperate to get my phone up and running, I did a wipe. It killed the phone's internal memory. Had to reflash back to stock and since then my phone has been running really well w/o the lagfix even. Maybe my phone had a bad image like a computer. Not doing anything else to my phone til froyo comes out. I am rooted though.
Sent from my SCH-I500 using XDA App
You could try more cow bell. I heard it's the only cure for some fevers.
I've been semi-bricked three times when I've disabled Voodoo, and I did it right. So I use a non-voodoo kernel now. I'll wait until these bugs are ironed out. Join the irc chat and jt and the other devs commonly post kernel links.
Yup.. Using jt's 1031 test kernel now (novoodoo). Running beautifully.
Sent from my SCH-I500 using Tapatalk
Technically voodoo hasn't bricked a single phone. User error and then likely a small error in the proccess itself have caused some ugly problems but it can be overcame with a little work
Sent from my SCH-I500-Fascinate using XDA App
ksizzle9 said:
Technically voodoo hasn't bricked a single phone. User error and then likely a small error in the proccess itself have caused some ugly problems but it can be overcame with a little work
Sent from my SCH-I500-Fascinate using XDA App
Click to expand...
Click to collapse
I said semi-bricked. It wouldn't get past the boot screen. It couldn't have been user error two of those times, because I used reboot button to do it.
Kamar234 said:
You could try more cow bell. I heard it's the only cure for some fevers.
Click to expand...
Click to collapse
Thank you for this. Seriously though, I've been running jt's voodoo kernels since their release with only minor problems. I've disabled voodoo and flashed other kernels no less than three times without issue. Granted it does take a while to boot after enabling/disabling voodoo. The first few times I thought I screwed up, but it always boots for me.
Sent from my SCH-I500 using XDA App
Mean Bro Greene said:
Thank you for this. Seriously though, I've been running jt's voodoo kernels since their release with only minor problems. I've disabled voodoo and flashed other kernels no less than three times without issue. Granted it does take a while to boot after enabling/disabling voodoo. The first few times I thought I screwed up, but it always boots for me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think it's a phone to phone thing. Some people have no problems just turning off voodoo when they flash ROMs and kernels. I have to use adrynalyn's voodoo uninstaller and wipe completely if I want to change ROMs or kernels.
Weird.
Yea when I tried to turn voodoo off it took 4 reboots before it took. No issues after that though.
*EDIT* Posted in wrong thread...my apologies
Used the "reboot button" app to disable Voodoo. It hung on "Samsung" for over an hour after robot women said "operation completed" or whatever. i finally admitted defeat and did a battery pull. Restart resulted in a boot loop. I was able to recover following the "remove Voodoo" thread and flashing the stock Nandroid. From there I flashed jt's v.4 Super Clean ROM with Frost's theme. Having had the stones to try Voodoo again but honestly my phone is running good with just the Super Clean ROM. Having a recent Titanium backup really helped get my phone back in order quickly.
While it was an unpleasant experience it ended well and resulted in a nice clean and fast Fascinate. Best part though is that I'm no longer afraid to flash my phone since I now know I can recover fairly quickly.
Martian21
martian21 said:
Best part though is that I'm no longer afraid to flash my phone since I now know I can recover fairly quickly.
Martian21
Click to expand...
Click to collapse
...that way lie the dragons...
Yeah, that's pretty much what destroyed any hope I had of *not* being a total ROM-a-holic. I have owned this thing for no more than 2 weeks and have pushed over a dozen different roms/kernels on it.
I cannot even imagine what this poor phone will be going through once we start getting things like Cyanogen's up and running.
(currently using jt's 1031 USCC non-voodoo kernel...at least until I get home.)
Hey, lovin my TB! recently after returning from TB back to fresh rooted froyo, everything's been ok. Then I flashed bamf 1.7 fine. Stripped version getting shut offs, not reboots.. I don't notice till I reach in my holster and the HTC logo appears. I thought it might be the rom so I flashed cm7.0.0 RC. Still getting them. Is anyone else getting these? This is serious considering i almost woke up late today after setting my alarm last night only to find my phone is turned off.
Sent from my ThunderBolt using XDA App
I'd start by checking kernel settings. Too low won't wake. Too high will cause a shut off. Not all processors respond well to extreme over/under clocking and under voting.
Sent from my ADR6400L using XDA Premium App
keith.mcintyre26 said:
I'd start by checking kernel settings. Too low won't wake. Too high will cause a shut off. Not all processors respond well to extreme over/under clocking and under voting.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I actually have not touched the kernel nor the radio.. but I'm wanting Netflix so I'm going to have to flash the gb radio I think. As for the kernel it is the one that came with cm7, the highest clocking is around 1ghz. I guess ill show around for a decent kernel.
Sent from my ThunderBolt using XDA App
shut off fix worked for me
I was having the exact same problem and I flashed the new cdma radio and the old LTE radio combo and I have not had a problem since.
here is the line to the thread where I got the radios from:
http://forum.xda-developers.com/showthread.php?t=1045081
alluzzion2o9 said:
I actually have not touched the kernel nor the radio.. but I'm wanting Netflix so I'm going to have to flash the gb radio I think. As for the kernel it is the one that came with cm7, the highest clocking is around 1ghz. I guess ill show around for a decent kernel.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
Most likely the dumb radio then..last couple radio releases have reboot issues depending on the person...seems your an unlucky one too.
n0vemberrain86 said:
I was having the exact same problem and I flashed the new cdma radio and the old LTE radio combo and I have not had a problem since.
here is the line to the thread where I got the radios from:
http://forum.xda-developers.com/showthread.php?t=1045081
Click to expand...
Click to collapse
Ill give it a try. Thanks for the link.
EDIT: as an update. So i reached 24hrs without a single shutdown. I flashed cm7 dream kernel 1.8 and one of the radios from above link.. only question is the types of signals of each combo from the link looks like hyroglyphs to me.. which is the recommended radio running cm7?
Sent from my ThunderBolt using XDA App
I cant pinpoint at all whats going on. I get at least 5 screens of death each day. I full wipe and everything before I flash a rom on my phone. I'm currently on Turkbey v7. Someone please help me out
Return to stock, if it happens still probably best to return it if you can.
LiLChris06 said:
Return to stock, if it happens still probably best to return it if you can.
Click to expand...
Click to collapse
oh no... i just got a replacement a few weeks ago..
Did you mess with clocks/voltage at one point? There may be an init.d script or some other kernel settings leftover from those that you gotta get rid of. Flashing back to stock should fix that if I'm not mistaken.
Can you still return your replacement?
afrojoc said:
oh no... i just got a replacement a few weeks ago..
Click to expand...
Click to collapse
that jus tmeans you'll need another
Did you clean out the kernal settings between ROMs/Kernals?
No I didn't mess with any overclock or voltage settings.
I can still get another replacement phone until a year has passed since this phone has been released since thats when I got the first phone.
And tomorrow I'll try flashing back to stock and then flashing a rom afterwards. I have to study for my summer class tonight.
Thanks alot everybody!
afrojoc said:
oh no... i just got a replacement a few weeks ago..
Click to expand...
Click to collapse
well replacements are usually refurbished, if im not mistaken. Theres probably a higher chance that something is wrong with a refurbished phone over a brand new phone. So maybe not that unexpected that something will go wrong, especially with custom software
I would try running the kernel cleaning script and flashing a new kernel. I known NEAK didn't like me and locked up several times a day. But its so darn fast....just giving an example. What kernel r u running now?
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I would try running the kernel cleaning script and flashing a new kernel. I known NEAK didn't like me and locked up several times a day. But its so darn fast....just giving an example. What kernel r u running now?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
NEAK...
NEAK is working great here with UCLD4. I used to have tons of SoDs with LD3 on the stock kernel, just about every time I turned the phone off it would SoD within a couple minutes.
So because I felt too lazy to go to stock, I found the kernel cleaning script and wiped everything off my phone and flashed the script. Then I reflashed the Turkbey rom since I just like it and so far I haven't gotten any SODs as of yet.
afrojoc said:
So because I felt too lazy to go to stock, I found the kernel cleaning script and wiped everything off my phone and flashed the script. Then I reflashed the Turkbey rom since I just like it and so far I haven't gotten any SODs as of yet.
Click to expand...
Click to collapse
Yayz! If I wasn't such a fanboy of AOKP I'd try it. I just totally fell in love with this ROM. maybe one day....glad things are working for ya.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
Yayz! If I wasn't such a fanboy of AOKP I'd try it. I just totally fell in love with this ROM. maybe one day....glad things are working for ya.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Its not bad. Im mostly on it cause i thought i got the least amount of SODs on here hehe. Its my safe zone to be at.
But anyway thanks for your help and everyone else who spent time and effort to help me solve this stupid problem! I love this forum..
Voltage
Min volts may be set too low. Bring first step up to 200. Allot of times its too much deep sleep.
After use for a while....the screen gets real unresponsive. To the point where if I try to scroll down on FB...it will actually register a click instead of a swipe and open up the picture I happen to swipe over.....anyone else???
Galaxy S III I747
fmllc said:
After use for a while....the screen gets real unresponsive. To the point where if I try to scroll down on FB...it will actually register a click instead of a swipe and open up the picture I happen to swipe over.....anyone else???
Galaxy S III I747
Click to expand...
Click to collapse
This only happens to me when I'm trying to use my phone while it is plugged in and charging. It acts all crazy, but once I unplug it the thing works fine. I pretty much keep my phone in ECO mode and haven't switched that off to see if it makes a difference.
Same here. I keep my phone on ECO mode and have no issues with responsiveness, except for once in a while when it's plugged in and charging.
Sent from my LG-E970 using XDA Premium HD app
That's horse ****! Someone has to come up with a fix for this! Doesn't eco mode cap the processors at 1.1 or something?
LGOG E970
Seems cycling the screen off and back on will get rid of the lag....until it happens again....lol
LGOG E970
I don't have that problem at all with mine. I am unlocked, rooted and running Notach's Base ROM.
jamesc760 said:
I don't have that problem at all with mine. I am unlocked, rooted and running Notach's Base ROM.
Click to expand...
Click to collapse
I DO have that problem with mine. I am unlocked, rooted and running nottach's Base ROM the problem has reoccurred with the stock ROM and versions 0.5, 0.6.5 and 0.7.3 .
It's probably a kernel-level memory or CPU issue because for most people it appears to be a specifically time-based problem. The longer your uptime is, the worse the problem gets. Reboot your phone and the problem goes away for awhile.
Sent from my LG-E970 using xda app-developers app
Have you tried restarting your phone lol. I've never lagged once.
Sent from my LG-E970 using xda app-developers app
amrando said:
I DO have that problem with mine. I am unlocked, rooted and running nottach's Base ROM the problem has reoccurred with the stock ROM and versions 0.5, 0.6.5 and 0.7.3 .
It's probably a kernel-level memory or CPU issue because for most people it appears to be a specifically time-based problem. The longer your uptime is, the worse the problem gets. Reboot your phone and the problem goes away for awhile.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Amrando, inflammatory and unhelpful statements aren't going to win you any help with your problems. It's just alienating those that would otherwise help you out and gets you reported to the mods.
Sent from my LG-E970 using xda premium
amrando said:
I DO have that problem with mine. I am unlocked, rooted and running nottach's Base ROM the problem has reoccurred with the stock ROM and versions 0.5, 0.6.5 and 0.7.3 .
It's probably a kernel-level memory or CPU issue because for most people it appears to be a specifically time-based problem. The longer your uptime is, the worse the problem gets. Reboot your phone and the problem goes away for awhile.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I've edited your post. This is a great example of the same phone, running a similar set up behaving completely different. The user you quoted wasn't doing anything other than stating that they don't have this problem so chill out a little and accept that each person can have a different experience and opinion. If you've got nothing useful to say, say nothing.
Thanks
AvRS
Hello xda
I'm getting a problem..
Sometimes my phone heats up while charging that it starts bootlooping!
But today battery was about 15% and I didn't put it on charge.. then also it started bootloop. My dad put it on charging and it keeps on rebooting and it was so hot when I came back!!
Actually, why is it rebooting again n again? It was working so fine from 2-3 days n I did nothing!
I'm using foxhound 2.4 on stock kernel.
I just wanna know that is it a hardware issue?? or what?
as it's a new phone so it tenses me.. and I didn't started development on it yet
bought around 2 weeks ago
Try re-flashing the rom but with Siyah kernel. This is what i run and it's perfect. I run overclock @ 1.7ghz and get no excess heat. Also 20 hour batrery life under standard use.
Search before asking, Ask before acting and you will succeed.
jonniboi1985 said:
Try re-flashing the rom but with Siyah kernel. This is what i run and it's perfect. I run overclock @ 1.7ghz and get no excess heat. Also 20 hour batrery life under standard use.
Search before asking, Ask before acting and you will succeed.
Click to expand...
Click to collapse
So u mean it's not an hardware issue?
And its just a kernel or rom issue?? Right?
Sent from my GT-I9300 using xda premium
I can't see it being a hardware issue, no. Especially if all was fine before flashing the ROM. It May be issues with the rom and stock kernel.
Search before asking, Ask before acting and you will succeed.
jonniboi1985 said:
I can't see it being a hardware issue, no. Especially if all was fine before flashing the ROM. It May be issues with the rom and stock kernel.
Search before asking, Ask before acting and you will succeed.
Click to expand...
Click to collapse
After flashing rom also.. its working fine..
Only sometimes it happens..
I can't get! Why does it bootloop without any reason?
Sent from my GT-I9300 using xda premium
Did you take a back up before flashing? Hopefully you did.....?
If so, then flash your stock back up and leave for a few days. If problem persists then you have an hardware issue. If problem is fixed then it was the rom and kernel issue.
As i said i akso use Fox hound 2.4 but with Siyah kernel and my handset faultless.
Search before asking, Ask before acting and you will succeed.
jonniboi1985 said:
Did you take a back up before flashing? Hopefully you did.....?
If so, then flash your stock back up and leave for a few days. If problem persists then you have an hardware issue. If problem is fixed then it was the rom and kernel issue.
As i said i akso use Fox hound 2.4 but with Siyah kernel and my handset faultless.
Search before asking, Ask before acting and you will succeed.
Click to expand...
Click to collapse
Lol
Yes I have backup!
Seriously, after using foxhound I dont wanna go back to stock
Ok.. thanz for ur support..
Lets see what happens!
Sent from my GT-I9300 using xda premium
Just run stock for a few charges. You have to find the fault. If no fault running stock thdn go back to Foxhound but try a different kernel. Goodluck!
If it works please press thanks
Search before asking, Ask before acting and you will succeed.