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.
Related
I've been charging my phone all day but It's been refusing to accept a charge. I rebooted it, but the best it would do is charge, then tell me to connect the charger, then intermittently start charging again (even though it was plugged in the whole time). I tried different cables, AC adapters, my PC, with no difference in performance. After a reboot, I noticed it had decided to remove all my widgets, but not any shortcuts. I'm running CM7 Gingervillain. After puttering between 2 and 15% battery level for hours it then started refusing to boot, blinking an orange light at me, sometimes, and then the light would stop.
I took the battery, sim card, and SD card out, unplugged it, and started to vigorously "ninten-blow" all the contacts. Saw a stupid looking post on the web that said I should remove the battery and hold the power button down for a while and try again, so I did that too. It booted, magically, then told me to connect my charger, even though it was connected, and died for the last time.
Held down the power and volume down to get into hboot (I think?) and told it to reboot from there, it just turned off. Tried again and selected clockwork recovery, it worked! All right now I'm getting somewhere. I selected reboot now from the friendly black menu and was greeted by a black screen with a top hat wearing gear-and-arrows-amalgamation (the clockwork logo and no text). It stayed on this for about a minute and that was the last thing the display ever displayed.
Now I have a dark screen and the orange light will blink up at me inconstantly if I try to boot it by using the regular power button or power + volume down. That's when I decided it was time to register a new account here and make my own post instead of lurking.
Please help me.
EDIT: Sometimes the orange light will blink when I don't do anything. It is very inconsistent. Like it's trying to message me with morse code.
EDIT2: Got into hboot, clockwork recovery, selected "backup and restore" this time I am greeted by the clockwork recovery logo with no text again, it displayed this for twenty minutes and then died.
EDIT 3: Strangely, if I set the phone down, the orange light will not blink. It will blink without any particular interval if I pick it up, even if I'm not pushing any buttons or touching the screen. The blinking continues for a short period of time when I set it down, and then stops.
EDIT 4: I have arranged the phone and some furniture so that it is dangling by it's charging cable, which as caused the orange light to glow constantly. Perhaps I just have a bad micro-USB port.
EDIT 5: It booted up fine after charging while dangling. I have a bad Micro USB port, and am paranoid. I guess I will forever have to awkwardly charge it.
CRISIS AVERTED I AM DUMB
I recognize you've tracked your issue down... but as an aside, when you're trying to select an option in Recovery it sounds like you might be trying to use the Power button instead of the trackpad? I believe that's why you're seeing the Clockworkmod logo and no text when you "select" your option. I did this once too a long time ago and freaked myself out.
Hi,
Last night I charged my One X to 100% (reported by the Elixir 2 application as well as the green light being lit on the phone) and then switched it off before I went to bed. When I switched it off the phone seemed to shut down as usual, the Orange shutdown screen displaying, but then the Orange logo stayed on the screen for a minute or so before it all went dark.
This morning I switched the phone on and when I pressed the power button nothing happened. I held the power button for a few seconds, the soft keys at the bottom flashed, and after a couple of goes the phone started normally, but my battery was on about 50% despite being fully charged last night. I looked at the battery use graph and saw the line had a big gap in it, probably coinciding with when I was asleep.
For info I'm running 1.26, Orange branded, unrooted, and fastboot is disabled.
Any ideas?
I was trying to flash the Lifeless rom back onto my phone, and had Aroma wizard started up, and was checking the options I wanted, when I remembered that absentminded me had forgotten to do something in the OS that I can't remember at the moment. I didn't see a cancel button in Aroma, and since I'm so impulsive, I held down power and volume up to reboot the phone. It nearly booted to the OS, with the capacitive keys lighting up at the bottom, when it suddenly shut off and attempted to reboot (maybe because I was flashing AC!D audio earlier and had checked the build.prop tweaks). It didn't reboot, but seemed BRICKED.
Ok, the actual problem.
It seemed totally hard bricked to me, nothing when I plugged it in to my PC or charger, so I, enraged, walked away and left my Optimus plugged in. When I came back, I saw that the notification light was blinking red, one shade of red brighter than the other. I gained some hope back by...
The FIX
... following the directions on YouTube (look it up, I can't post links) on performing a hard reset by disassembling the phone and disconnecting/reconnecting the battery connector. I, however, had to do a little twist to get my phone to PARTIALLY boot.
When I detached the battery connector from the mainboard,(phone still plugged in) the phone would proceed to bootloop, showing up the unlocked Google screen, etc. (flashed the ZVB Teenybin, that's why the Google screen) until it got to the battery charging icon in the center with the lightning bolt in the center. At this point, I reattached the battery connector and BOOM, the phone rebooted NOT LOOPING , PARTIALLY STILL but with the battery icon animation stacking up.
Unfortunatly, my battery was nearly dead so I then waited for a bit and let it charge up.
I held down the power button + vol up (on my bare phone with the backing taken off) to get it to boot into fastboot, then TWRP to flash the rom. I SUCCESSFULLY flashed the rom (relieved at this point) and I booted FULLY :laugh: . It got me to the Optimizing apps numberhere/biggernumberhere screen. Suddenly, the frickin phone shuts off and the notification light blinks red, but with a delay this time instead of a brighter shade of red. I did what I did before numerous times, but the phone would stay alive less and less.
I let the phone cool off for a bit (Heating issues on the Optimus ), tried charging it again, and I managed to finish optimizing my apps. It loaded up the lock screen for a split second, and then shut off with the LG goodbye animation.... Which is a hell of a lot better than a blinking reset light.
So after it shut off I let it charge...
And I was back!
NOTES:
The video I describe was originally made to resolve some other reset indicator, with alternating blinking capacitive buttons and the notification light, but also helps with the issue I had with solely the notification light blinking.
I don't think that anyone has had this issue since not really anyone is retarded enough to force reboot with Aroma loaded up.. but I decided to type this up just in case.
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!
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.