samsung fascinate frimware 2.2.1 its the super freakin clean rom ebo1 for baseband and build number ....the phone just shuts off randomly and i either have to do a battery pull or reboot with the poweer and volume buttons held in originally i thought it was a hardware issue so i got a new fascinate and this one is doing the same thing someone please help me
This typically stems from not wiping data as well as cache prior to flash...
Sounds like you have a rogue app locking the phone up while it's sleeping. I would do a factory reset, then install your apps one at a time until you figure out what's causing it. Allow the phone to sit idle, and maybe even reboot between installs. Allow the phone to settle down and enter sleep between each install and then try to wake the phone after it has been idle for a minute or two.
The other way would be to try looking at logcat with your phone connected to your computer when the screen is on, then when the display turns off and the phone sleeps. Odds are, whatever is causing the problem will be the last thing displayed if logcat stops giving you output. Otherwise, it should just repeat the same thing over and over (I'd assume so anyway) when it's trying to wake up from sleep.
My friend was having a similar problem so he flashed from SC 2.9 to the Deoxed eb01, wiped all the data on his SD card, and reflashed to SC 2.9, he hasn't had that problem since.
Ok. Problems I have encountered the 2 days I have used the phone:
Constant freeze. The first hour I used the phone it froze and rebooted 7 or 8 times.
Missing SocialLocation.apk. This caused a problem for the GPS in smart actions to work at all. Rooted phone and installed the app, and problem disappeared.
Tried to hard reset the phone because of all the rebooting problems. Guess what, on the first menu coming up where you can choose language, the phone froze and rebooted again. Now still it is constantly freezing and rebooting.
The freezing issues does not really have one specific app causing it. It can happen whenever doing whatever!
Anyone got a solution for this? Maybe a OTA update for Norwegian model?
Well, as my dad's phone is still fine as of now with not a single reboot in 2 days, I'd suggest you get in contact with your carrier and ask for a replacement. This seems to be a phone defect and you should be able to get your replacement easily. Be sure to not mention rooting and installing SocialLocation.apk though!!
You rooted and removed some files from the System, did you not?
Hi everyone,
I've been lurking for the past year or so, but now I got a problem of my own and I hope I can solve it with your help.
For a while now, almost every time, I picked up the phone, tried to check mail, or do something, and it wouldn't do anything. It seemed like it was turned off, except I couldn't turn it on by pressing the power key. It wouldn't react to touching the screen, menu button, plugging in headphones, the USB cable, pressing hardware buttons, sending myself a mail/sms, or calling myself, the alarm didn't go off (especially troublesome), it was, for all intents and purposes, completely frozen, until I removed and reinserted the battery. Then, I could normally turn it on and it seemed like everything was in order and a new message or email (in the account that triggers a notification) was waiting for me.
This started after I upgraded to ICS (official). I also rooted the phone with CF-Root. Everything was working fine, except for these freezes.
Last week, I had enough and I did a factory reset. After that, it seemed to be ok, until 2 days ago, when I flashed it with ICS 4.0.4 and rooted it again. It was fine for 2 days, today it started freezing again. I did not install any new apps - all the apps were (re)installed immediately after the flashing.
I *did* have some problems with the camera (I couldn't see what I was shooting, I found out that it's probably a wrong version of CF-root, so I reflashed that, problem persisted, I reflashed just the kernel of official 4.0.4 and the problem disappeared. This is all I did before I noticed the problem again.
I would think that it might be because of the SD card, some app or something else, but to the best of my observing, it ONLY happens, when a notification should be triggered - instead, the phone freezes.
Any ideas?
Thanks,
Ben
i think your RAM is on its maximum level, try cleaning your RAM once in a while.. go to your Task Manager (if you're on a stock firmware)
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
OK so i have an I9300. for about a year now i think, maybe more.
And up until lately it worked relatively fine, but lately It started to gradually become unbearably crashy and annoying.
the camera very often crashes, leaving me with an "Unable to connect to camera" message, and only after a reboot does the camera work again. it used to happen scarcely, but now i can barely take 2-4 pictures before having to reboot.
Talking about rebooting, Not only do i get random reboots all the time, but after every reboot (not just the random ones) I get a UI crash after UI crash and the only way to fix it is by locking the screen and waiting,
Usage is extremely slow, to the point where launching whatsapp takes up to 5 seconds.
I amusing the cm11 nightlies but i get this with every ROM, I've tried updating cm11 and still nothing. wiping cache and data-also nothing.
the only escape now is full SD card format, but I'm scared to do that getting the same errors after it.
Could you help me figure out what's wrong with my phone? it's the only one i have and it's unusable.
I'm scared it's a hardware problem - that i cannot fix. but the signs are all there: the errors persist through formats (i formatted once about two months ago to no avail) and wipes and reflashes.
If you need any additional details about my system that i forgot to mention, ask me obviously!
I'm guessing you have an i9300 and running cm11? That's what's in you're post so I'll go with that...cm11 is not stable enough atm. That will Explain the reboots from time to time. Best thing for you to do at this time is as always...go back to stock with Odin. Test it. Same reboots?? Back up and format you're int SD and flash again stock firmware with Odin. Still rebooting?? Possible hardware issue.