I dropped my S3 yesterday from a height of maybe 8 inches. It froze, so I yanked the battery. Initally it got to my spash screen (running liquid smooth 2.9) but froze again. Turned it back on and it only got the boot logo. I tried recovery mode, but it turned off while loading the logo, same with download mode.
When I plug it into a charger without the battery in, it vibrates and the notification light turns red for a second and it dies (doesn't show anything on screen)
Also, it it supposed to turn on as soon as I insert the battery?
I opened it up to see if something was lose and I saw that one of the ribbon cables looked a little weird- is it messed up?
I'm at a loss for what to do
Thanks!
Related
Last night everything was quite allright with my marvel. Then i slept. Morning when i woke up i tried to unlock the phone to check the time. But screen didn't show up. I tried several times but it didn't. So i removed the battery and started the phone. It took long time to boot (about 5 minutes on white htc screen). When it turned on touch screen didn't work. But hardware keys (volume, power) were working. I can boot into ClockworkMod Recovery (it also took long time to boot.) My rom was alquez's Cyanagenmod 7.2. I flashed it to another rom (Cyanagenmod 10.1). But the problem isn't solved. Phone starts desipite of long time but i can't do anything because of the touch screen doesn't work. Also i realized that proximity sensor always lids up (red). The light never off. Additionally phone powers on and loops into white htc screen when connected the charger. When connected charger while powered on the red notification light don't light up and charging very slow.
Hey, I have a problem with an old HTC Desire of my brother: Yesterday the phone was charging and then just crashed. When i power it on, the HTC-screen appears and just after that the screen turns black. Then I have to pull out the battery to be able to do this again.
The screen flickers when the bootscreen is displayed an gets darker before it goes finally black. I think the battery is empty, because the pins in the charging socket are twisted, so I think the battery wont get charged.
If I press the back button and power this menu appears, but then the phone also shuts down. If I press volume down and power the bootscreen appears but the phone turns off before I can see the bootloader
ROM: Cyanogenmod 7
S-Off, Root
What do you think? My brother says that the phone was almost fully charged when it crashed, but when I plug in the charger now the LED normaly shing red is not on..
Edit: I managed to get to the cyanogenmod screen, but then it turned off. Im pretty sure it is the battery
Any help?
Hi guys,
I rooted my phone and flashed cm10.2 on it a while ago. It has been working fine and maybe froze twice here and there.
So, 30 minutes ago I was using my phone and put it down to go eat. I come back, and the screen won't turn on. I tried hitting the home button, and the power button. Neither worked. So I ended up pulling the battery. I plugged the battery back in, and hit the power button. The phone quickly flashed the samsung logo, and then went black. I gave it a minute and nothing happened. I pulled the battery again, and it turned on itself (vibrated as soon as i put it in), then flashed the samsung logo, and then cut right to the cm10.2 logo, and then went black again.
Any ideas? I havent been messing with bad software or anything like that.
Thanks!
I just managed to get it into download mode but it keeps turning off.
update - I managed to plug it into the computer and a red light came on in the phone. It vibrated, and then went dark again. Does this mean anything?
update 2 - I've given up and am going with the "its a faulty power button" - explained here - brickedmyphone.com/ products/ power-button-replacement/
ok so earlier today my s3 ran out of battery and shut off. I attempted to charge it, but noticed the red indicator light wasn't on. I tried to turn the device on, but all it did was vibrate and show the battery level logo with the circle in the middle as if its computing the battery level, then shuts back off. most of the time it will just vibrate and loop the samsung logo and then shut off again. sometimes it also shows that my battery is nearly fully charged after i left it on the charger while i was in class, but then shuts off. the farthest it has showed anything on start up was the at&t logo with the white background, then it shuts back off. i've tried to boot the phone connected to the charger and took the battery out, that didn't work. tried to take the battery out and leave it for 10 mins and put it back in, that didn't work. although it would vibrate everytime i put the battery in. i also tried to boot the phone in recovery mode. it would say recovery mode booting in blue letters, then it would go to the samsung and galaxy s3 logos, but then shut off again. also tried the download mode boot up, but i just saw the OS warning screen for a second, then it shut off.. i've ran out of ideas on what to do. hoping anyone could provide anymore advice for me. thanks in advance!
Hi everyone,
I have an AT&T Samsung Galaxy S7 Active SM-G891A that just became unresponsive. It began with a vertical pink line appearing and disappearing intermittently down the right side of the screen. After a few times if this happening, the phone froze while playing "Laser Overload," which I had just downloaded, for about 30 minutes. I performed a soft reset and the phone went into a boot loop that lasted 20 minutes or so- sometime it would make it to the AT&T screen and freeze, sometimes it wouldn't make it past the "Samsung Galaxy S7 Active" screen.
Finally, it booted up normally but was running slowly. I powered it down, thinking it may have been overheated, and left it alone for a few hours. Upon starting it back up, it worked fine for about 15 minutes but then froze once again. I performed another soft reset, but this time the screen stayed black- no image and unresponsive to touch, but with the top left LED indicator a steady blue. It stayed like this for an hour or so until I plugged it in; the screen did show the lightning bolt charginf icon but it took about 10 minutes for it to display the battery percentage (0%). The phone had 75% battery when it became unresponsive.
Once it had charged to about 15%, I booted it up (leaving it plugged in) and again it became stuck in a boot loop. I rebooted to the system menu (Home + volume up + power) and cleared the system cache in hope that this would resolve the issue, but again the boot loop. Finally, I performed a factory restore on the phone from the boot menu. This time, the phone booted to the AT&T screen before it froze with a horizontal line of static near the bottom of the screen. I soft reset it and the phone made it through the boot screens to a Wi-Fi login. I logged in to the network and the phone froze again, this time shutting down completely and is unresponsive to being plugged in- multiple cables and chargers being used. There is no top-left LED light when plugged in, and attempting to power on the phone using any method does nothing.
Is it possible that playing a game for a half hour was the final straw in killing a graphics processor? I hadn't used this phone for any thing graphics intensive and this game seems rather simple (2D only, no simulated camera, etc.), but it's a secondhand phone that I've had for a few months now. The phone had been dropped a few days ago- only about 2ft onto a rubber mat with no damage to the phone. Could this have caused it?
Is there any way to verify what the issue could be with the phone unresponsive as it is? Any help would be appreciated.