Hello,
the other day I had my phone on the sofa next to me, working fine, I leave it there 30 min, pick it up, and the screen has all kinds of weird glitches. After a couple hours now the screen is completely blank and whenever I press the power button the notification light blinks a couple times. It's kinda weird tho because touch seems to be working (if I boot to recovery, then tap on the screen the phone vibrates just like TWRP buttons) and I can still boot to fastboot. Of course when I say boot it means that `fastboot devices` shows the device ready, but I can't actually see anything on the screen. I'll try flashing the latest MIUI now, does anyone know what this could be? I mostly just like to know whether I should try changing the screen only or if it's likely to be a bigger problem and I'd be better off replacing the phone entirely. Kinda sad, I loved this phone. Thanks.
Related
Tonight my G1 displayed some very odd behavior. It was running normally and I pressed the power button to make it sleep and I set it aside. About half an hour later I picked it up and tried to turn it on by pressing menu. The phone gave no response other than lighting up the five buttons on the bottom. I tried sliding the keyboard out and the keyboard lit up as well, but the display remained black. Plugging it in via USB to my computer did absolutely nothing (no sounds, no notification light, etc.), and I got the same result when I plugged it into the charger. I finally decided to take the battery out in order to turn the phone off, and then put it back in and pressed the power button. The phone booted up normally, and now everything seems to be working in proper order. I am slightly concerned, however, as I have never had this behavior in the year that I have owned my G1. I am running Cyanogen 4.1.999 with the Hard SPL boot loader. I am unsure whether this behavior has anything to do with the mod and I am wondering if anyone else has experienced anything similar. I do realize that if my phone is bricked it is my fault, and I want to determine if this was simply a freak accident or if I need to do something differently with the phone.
first of all if your phone was bricked you wouldn't be able to use it. as for your problem it doesnt sound too serious so if i were you i wouldn't worry about it. but if it does happen again reflash your phone and if it happens after that, pitch it to cyanogen to see if there is a problem with the rom.
I do realize that it isn't bricked now, but I am worried that this behavior could mean that I am pushing the phone too hard. I am mostly curious as to whether or not anyone else has experienced similar behavior from their G1.
Turn off compatibility mode in spare parts.
don't worry this is a common problen It happens to me all the time any hero I flash plays nice for about a day. and then boom no problems with cyan!
I had the same problem, but unfortunately my G1 is still not working properly.
In the morning, turning off the alarm I left the phone for 5 minutes. An attempt to turn it on did not work: there was no reaction on display, although the buttons were lighting up. I restarted phone taking the battery out and now I have following:
- keyboard fully closed: no reaction/black display, buttons are lighted up
- keyboard open: I can do everything: change ROM/make call/write messages/Internet/GPS/... - everything what is possible to do with rooted G1
- keyboard partially open (visible only lowest row with such buttons as ALT, SHIFT, SPACE): similar to 'open' but with changed orientation
Can anyone help/advise? Did almost everything: ROM changed, full wipe, recovery
It started about 30mins ago, was on a call which the screen locks off when u on a call like stand by, but when ending the call the screen would turn on back no matter what. anyways i took out the battery thinking maybe the roms just buggy or the battery dead since it was on low. puttin back the battery the phone wouldnt turn on, took it out and tried again same result.
so i put it on charged nothing, gave it about 2mins charge it came on, but the boot screen with the X just had some green pixel dots all over and horizontal lines for about 3 secs then back to normal, but the phone wont boot pass that.
took out the batteries again, back in then try boot into fastboot or bootloader but nothing, just the boot screen, then the rom booted after waiting, took longer than normal. so i turned it off and try the bootloader or fastboot but it wont load just the rom, so i restarted to recovery mode from the rom it worked, turn off and try bootloader or fastloader mode they worked, now it seems all working fine, also my touchscreen is responding perfectly and the rom loading ok.
but anytime i boot the phone the bootscreen has the green pixels and lines just the same. im abit worried as i dont want things getting worse, is there anyway to fix this, is it some virus? could i just flush everything and start over???
any help would be greatful, thanks.
ppl with simular problem:
http://forum.xda-developers.com/showthread.php?t=642761
http://www.google.com/support/forum/p/android/thread?tid=77fefa8bdd57d7a3&hl=en
You guys think updating my radio from 4.06 to probably 5.08?
Almost similar with few different colors but I dropped my n1. It took me almost a day to see that the LCD was broken. Turn off the phone or screen and look in sunlight. They really were hard to notice and I showed to 4 different peoples whom all failed to notice until I showed them. Hope yours is just a minor software problem.
well i just check its not broken and it didnt fall from me so im guessing its software but im wondering if it can fix but i dont wanna flash my phone and things get worse or even brick my phone, so im asking before i try anything more.
Hello everyone. I have had my Droid Bionic since day one and I have never had an issue with it. It has been wonderful.
Until today. I am on the stock OS. I had a Live Wallpaper that showed a little Android figure that melts based on the percentage of my battery. I went into my Gallery and clicked on "Set As Wallpaper" on an image I took with my camera on the phone.
At the bottom of the phone, a small popup showed up that said "COMPLETED". When I went to the home screen, there was no wallpaper in the background. It was just black, though the icons were still there and it was responsive. I thought maybe the image was corrupt, so I went and tried another image.
This caused the phone to reboot. When it rebooted, there was a notification bar, the time, the lock screen, and a thing that said No Signal. I tried to unlock it, but the phone was unresponsive.
Then I got a text message, even though I had no signal. The notification light was blinking. I could not unlock the phone. I hit the sleep button, and it went to sleep. I tried hitting it again, and it would not wake up.
I tried pulling the battery and putting it back in, and now it won't properly boot. Right when it boots, it goes to sleep (the little shutdown animation). I texted myself from my sister's phone and the notification light blinks, the phone vibrates, and the screen turns on and shows I have a text on the notification bar. The screen and the buttons are completely unresponsive, however.
I tried calling myself from my home line and I could pick up the call just fine and end the call. I could not, however, go back to the home screen while on the call. The capacitive buttons on the bottom were completely unresponsive. When I hung up the call (by touch), it went to a completely black screen with the notification bar showing that I had some text messages and the time and my service, etc.
I have rebooted the phone five times now by removing the battery and it keeps going to this. I have never rooted the phone (I wouldn't even know how to) and I am concerned because of all of the information that I have saved on the phone.
Yes I have tried removing the SD card. Didn't help.
Any suggestions? :/
UPDATE: Now the phone doesn't even boot, it gets stuck at the Red Eye spinning logo. It vibrates twice and the notification light begins blinking, meaning it is letting me know that I have received text messages... but it isn't actually booting to the Android home screen. Really strange...
You should fxz back to stock
It will wipe your application data but not you're sdcard info or internal storage
Sent from my DROID BIONIC using xda premium
Hard reset using all three external buttons
Try doing a hard reset - it's one of those things they only tell you about at the Verizon store when you're stuck:
Once you have the phone on and at least responsive, press and hold BOTH volume keys, then hold the power button down for 10 seconds (it's really about 6, but 10 will do it for sure). This procedure can also be done to force a reboot when you load a gnarly application that sux and locks your phone up - without having to disassemble everything and pull the battery.
Hopefully with any luck, you're phone will do a back-flip and come up!
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
tdrussell said:
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
Click to expand...
Click to collapse
ask franco if fsync is enabled default and if is barrier=0 in the kernel
Try holding in the power button for 45-60 seconds. If that doesn't work then Plug in the unit, and let it try to charge for an hour or two. Then try holding in the power button for 45-60 seconds again.
There seems to be a glitch where the unit will die when the battery is low. Some people have report something similar when the unit was ~23% battery life.
Hello all,
I got this phone about a month and a half ago, and since I got it I've noticed a lot of freezing and crashing (more so after the 5.1 update).
Some examples:
-I try unlocking the phone from active display and the screen goes black. The only way to get out of it is to hold the power button to restart.
-Sometimes the phone freezes on the lock screen randomly, and when I pick up the phone to look at it, the time is wrong and I can't physically unlock the phone, only turn the screen on and off, leading to me having to hold the power button down to shut off and restart.
-When on some apps, like twitter for example, the phone freezes, and I cannot do anything except turn off the screen by pressing the power button. When I try waking the phone, it stays black or sometimes theres a flash of the screen I was on before, and then it goes black again. Only thing I can do here is hold the power button down until "Power Off" shows up on the screen, and I press that to shut the phone off.
Today I cleared the cache, and since then the phone has froze once, causing me to do a hard reset. What should I try next? Any idea what the problem could be?
Thank you for the help.
I have pretty much the exact same thing going on. It started last night... I first noticed I had some charging issues where the phone wasn't charging very quickly after the battery died (after a day of heavy use). I let it sit for awhile, then it booted up, and it showed the motorola splash screen. It gets all the way to the lock screen, although I'm unable to unlock the phone. The screen goes dark. It appears to still be getting texts and the like- although this screen blackness issue makes it so I can't unlock the phone. The one thing I can do is hold down the power button and turn it off. I've tried loading fastboot and doing a factory reset, although nothing appears to happen and it boots the same way. The other thing about it is that it appears to be running hot- way hot. Any ideas? I'm running stock rom, Verizon network, just updated to 5.1 when it came out last week.