This has happened twice in the almost 2 weeks that I've had the phone (most recently today).
I'm on T-Mobile and rooted using the GS3 Toolkit v1.0 and the "ALLINONE [Flash Insecure Boot, CWM, Root phone + Install Busybox]" option. I can't remember if the first time it happened was before or after this, but I think before.
So, most recently, I opened Contacts, scrolled down, opened a contact, then the phone became unresponsive. After a about 5 seconds, the screen briefly went black, back to the home screen, and mobile data was along with cell signal. Those came back up after a couple seconds and everything worked fine. At no point did I receive a popup about an application needing to close.
Anyone else experience anything like this with their GS3 or another phone? Just wondering if I need to get a replacement or just ignore. Or maybe flash a new ROM if it's software and not hardware.
Related
The other day I started to prepare to upgrade the wizards shipped ROM with one of the newer versions out there. I used aWizard to CID unlock and back up the ROM. After that I noticed the machine acting odd. It started getting extremely sluggish (hanging in the windows splash screen for several minutes) and for whatever reason any programs icon associated with a short cut was not displaying correctly in the PHM Tray launcher. After several soft boots and much frustration, I took the plunge and hit the “Clear Storage” process under the systems tab. This got the PDA going again, however the phone reception was now terrible. I was told by people on the other end that it sounded like I had a car window opened all the time.
I since then re-flashed both the ROM and Radio ROM using the backups. I even took the battery and SIM card out for several minutes to see if Cingular (my carrier) noticed any changes to the device when powered up again and perhaps download any patches. This seemed to rectify the problem, until today when I was back on the phone and the wizard went into sleep mode. The reception went goofy again until I hit the power button. Being that I did not have any of these reception problems before the backup, what could be the problem?
Thanks All
I've had my unlocked Cingular 8525 for about 3-4 months now, and never really had a problem with it. At first it worked great, but recently more and more when i have it open to text and then close it the screen would get garbled and messed up, easy fix of just hittin the end call button a few times and it would clear right up. Well friday my phone apparently decides it has had enough of me.. It froze up. So as a fix all on my part i just ripped the battery out and put it back in, worked fine for a few seconds then froze again. So i thought maybe it was because i had so many text on my phone (over 8000 in my inbox and around 7300 in my outbox), so i started deleting all of those. After doing all that it continued to freeze and lock up in the middle of doing things. It has been doing it since friday morning now, and i have no idea what to do to fix it. It had all the original 8525 rom and os and everything on it, i just flashed to Windows Mobile VI - Black Edition 3.0.1 a few hours ago, and it worked perfectly...for like 45 minutes. Then it went right back to freezing all the time, when it freezes it doesnt have to be in standby, i could be writing a text, or clicking through a menu, or changing a setting, ANYTHING. I love the phone but idk what made it start doing this, i didnt change a single setting and i have never uploaded any programs or anything, just the stock progs from cingular and i uploaded a few ringtones. I have read that it could be the storage card, but it seems odd that it would just start doing it after the card i have has been in for months now (Sandisk2.0G). Idk what it could be, im at a loss..
ok guess my phone is just jacked then...
My old Alpine used to freeze up with TomTom (before they patched it to 5.21) because of the SD card problem, but I don't think it's related to the problem you're having.
It sounds more to me like a hardware problem - do you get any other symptoms exhibited by the handset when you get the freezing issue, or does it just happen without any warning?
Have you tried installing something like acbTaskMan to monitor your CPU usage and maybe log to a file to see if there's any excessive CPU usage before a freeze?
my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..
Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje
Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?
everything was stock on mine, no root.......maybe thats why i could recover it??!!
Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.
I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.
Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions
That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!
I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1
Guys, I don't usually post on forums but now I just can't make myself sending it back without making sense of this first.
So I got the Nexus 7 one month ago, barely used it and didn't install any fancy stuff on it. One week ago I saw an app that I wanted and before installing it I had to install BusyBox. In my foolishness I didn't read the description that the tablet has to be rooted before I install it.
When the installation finished this exact problem suddenly happened: youtube.com/watch?v=5d319gUeYLM
Why I'm determined it's a hardware problem:
- The next morning I turned it on and everything was back to normal, however, after 15 seconds it slowly dimmed and got back to that exact screen
- You can navigate the menus and hear the sounds
- The morning after again, back to normal, I hurried and did a factory reset and deleted everything. This didn't help at all, the problem was still there and the screen never went back to normal even for a few seconds.
- It keeps the same lines in the recovery menu and on boot.
While everything points it's a hardware problem and the guy on YouTube said Asus replaced his display, how can this simply be a COINCIDENCE? For this to happen exactly when I installed something it wasn't supposed to be installed if the tablet wasn't rooted?
So I've attempted to debug this best I could but I've come up with absolutely nothing thus far.
About a month ago, I'd say, I started having very infrequent complete lock-ups. I'd pick up the phone and try to turn on the screen and nada. It would still be running as the notification LED would sometimes pulse according to my Lightflow settings. Plugging it into my computer, it appeared as an unrecognized device and adb wouldn't be able to get anything from it. I've never had this happen while I was actively using the phone, mind.
Holding down the power button until it force shuts down and rebooting it works just fine, but it's a bit annoying and worrying to have it go blank every few days. Once, it was even completely working but the touchscreen would not respond regardless of what I tried.
I since did a factory reset, thinking it might've been a kernel issue (I was running on faux's kernel) and it went fine for a week but it just did it again... And this is on stock 4.4.2, rooted, without any new app in a long time (ie. I can't think of an app that I'd have installed when the crashing started).
Any ideas, short of writing it off as the occasional problem and planning on a much earlier replacement than initially expected?