This is happening on MRA58R, stock, non rooted and rooted.
This happened on average two times a day. The screen became black when I exited out of an app, Audible this time but I had it happen to other apps also. Touches still registered, the notification center still worked, but I wasn't able to enter the homescreen via the home button, or settings through the notification center. I could bring up the power menu and shut down normally. Rebooting fixed it but it comes back.
I didn't have this problem on MRA58K. I thought it was a problem with root so I flashed my phone back to complete stock just today and the problem persists.
I can't post any images, but I uploaded screenshots to imgur. /a/tpx44
Related
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!
A strange occurrence happened yesterday with my Galaxy s6 from T-mobile. It is stock, unrooted, and on latest release. all of a sudden, the display screen went into monochrome (black and white ) mode. Battery was at 44%, so i dont think it was due to power saving. I also connected charger to further charge it. After some minutes, i turned it off, and restarted. While restarting, i can see samsung logo in color, and lockscreen was in color for few seconds, and then display immediately went mono. after few couple of more reboots, i wiped the cache in hope to clear any issue due to any app update. but still the same result. Then switched from Nova launcher to Touchwiz , but still the same even after one more reboot. So, i thought the phone may have become defective. Then , after a while, just pressed home button few times trying to unlock the phone, and this time, the screen came back to color!!!!
Has any one ever experienced this? What could be the cause? Software or Hardware?
ok, finally figured out what happened. There is a "Accessibility" menu, and one of the "direct access" shortcut is to make the screen grayscale, for whatever reason, that shoutcut key was checked. once you press home key 3 times in succession , that feature will be enabled.
Just created a pre-rooted rom using nordic combined 23.5.A.0.570_R11D and flashed (locked bootloader method). But I have a couple of issues. One is that a few seconds after the phone boots up the screen goes blank and the only way to get a display again is to press the power button for a few seconds which makes the power menu and the home button appear. I'm then able to press the home button. Only seems to happen after reboot. Anyone else seen this? I didn't for one of the UK based roms as I was worried about bloatware / customisations by Vodafone or Virgin Mobile.
The other issue is with the alarm clock - when the alarm goes off the screen comes on but only shows the background wallpaper. Only way to stop the alarm is to hold power button to get power menu and reboot. I've managed to get around this by removing the 20.1.A.0.12 clock app that came with the rom and installing a 20.0.A.0.28 version from KK.
Hmm after another reboot after repairing the alarm clock with the KitKat version the blank screen's not appearing anymore so perhaps related.
Its hardware problem your screen needs to be replaced same happened on my Z3 D6603 and hopefully the warranty saved me
I flashed 4.4.4 then 5.0.2 but same problem so its not a software issue.
I'm facing the same problem the screen goes blank .Nothing work to fix it .I've flashed the phone with lolipop it goes back normal but after few hours it goes blank again.Any idea guys ?
XMoDuLeSx said:
Its hardware problem your screen needs to be replaced same happened on my Z3 D6603 and hopefully the warranty saved me
I flashed 4.4.4 then 5.0.2 but same problem so its not a software issue.
Click to expand...
Click to collapse
That's what I thought originally as it had just come back from repair after having the screen fixed but I've not had a problem since removing the clock apk.
Hi all,
I'm having this same issue. I've just updated my D5803 to Marshmallow 6.0.1, build 23.5.A.0.570. Ever since the update, whenever I reboot the phone, it shows a black screen, and I have to press and hold the power button to get the home screen icon to show. And when my alarm goes off, just the wallpaper shows. If I press and hold the power button, I can get back to the home screen, but there is no way to turn the alarm off, I have to reboot the phone - not so fun when I just want to hit snooze!
I find it hard to believe no one else has had this issue before this build was officially released? I'm considering going back to the previous version
Edit: Well, this is interesting. If I take the phone out of its case the alarm works fine, put it back in the case, doesn't work. Take it out, it works. Put it in, doesn't work.
Edit 2: So, I reverted to Lollipop 5.1.1 and the alarm and phone worked perfectly. Updated again to Marshmallow - same problems, black screen and alarm not working while in the case, but alarm works when not in the case. Seems pretty definitive to me that it's a Marshmallow problem!
Bug is still present on .575 update. The strange ting is, on my phone when I disable the smart cover(Settings -> Sound & notification -> Notification access) it stays off, and then the phone is working fine. On my colleagues phone's it's switches itself back on after a call. I have no idea why this is not happening on my phone. Can't find any relevant setting differences.
YoMarK said:
Bug is still present on .575 update.
Click to expand...
Click to collapse
Wonderful
I have a Note 8 that i have never dropped, had this phone since release haven't rooted. However it is running one of the early Oreo Beta builds CQLB the phone is on Sprint. This has happened once before about 2 months ago and i can almost guarantee it happened in the same fashion as the most recent time a few days ago. It seems while receiving a call i go to reach in my pocket and hit several buttons pulling it out (because of the bulky case) then my screen goes completely black.
(This is where it starts to sound like the normal black screen issue that there are a thousand YouTube videos for)
The phone still makes noises for notifications, rings when calling and other noises like emails and low battery alarm. The screen however doesn't display anything whatsoever and has a blue led blinking.
(This is where it differs)
I've done every button combination i can think of with no avail.
-The regular restart button combination Vol Up + Power and hold for 7-10 secs,
-I've tried to boot into Recovery mode by guessing at what time the Samsung logo should be on the screen and pressing the vol button down several times
-I've tried to boot into safe mode by pressing the Bixby button, power and Vol Up and without the screen displaying anything i can of course not see if i was in Recovery or not.
The screen doesn't display a Samsung Logo, No sprint splash screen NOTHING. The last time this only lasted for about 3 hours and it suddenly came back up when being on the charger and restarted several times. This is now day 3 and after dozens of restarts nothing has worked, on or off the charger. I mentioned the Oreo build because maybe it's linked to that? i haven't had this issue on regular Nougat. ANY help is appreciated and thanks in advance
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
..
WizP said:
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
Click to expand...
Click to collapse
nope, i cant get anything to show on the screen at all
winol said:
How did you get an Oreo firmware?
Click to expand...
Click to collapse
By flashing the Oreo beta builds via Odin etc..
go back to a stable build.
bober10113 said:
go back to a stable build.
Click to expand...
Click to collapse
Kinda hard to do without anything displaying on the screen whatsoever, anyway i mailed it off yesterday for repair from Samsung. It was either that or a 2 hour drive to 12 Mile (Detroit) to bring it to the Ubreakifix store.
Unfortunately Sprint doesn't offer loner phones and can't activate any phone that is non sprint outside of some iPhones which sound a bit strange but now I'm out a phone for 9-11 days :silly:
Have you solved this issue? I have the same issue with my phone. It started happening to me even when I was on Nougat. Happens to me several times already. It goes black screen for about an hour to 3 hours then randomly get back to normal (get notification sounds, can receive call, etc). I am now on Oreo. Everything is stock. Never rooted my device as well.
Tried to bring to Samsung but all they did is 'Software Update' the device which is basically reinstalling the firmware and wipe everything. Service Center sucks and doesn't want to claim it is a defective unit.
My note 8 began experiencing this yesterday and after some frustrations and work around, I managed to pinpoint the issue.
Work around was go unlock phone and drag down taskbar, then click on systems and the system interface would open, after which I could press buttons on lower part of phone and clearscfeen to get back to homepage.
Problem was with Google. In my case I realised when I opened Google maps, the screen went black, so I went into applications and cleared the Google cache and Google maps cache. No 0roblems since.
Is it something with Snapdragon?
Hi guys
Just a quick one. Got a strange issue with the screen on my note 8 and just seeing if anyone has had the same issue or any idea on a fix.
Last week updated to the 9.0 beta and all seemed to be going well with no notable issues just a bit of lag here and there. However last night I turned my phone off and when I came to turn it back on this morning it started to boot as normal I entered my password successfully and it started to boot. As soon as the password registered and the unlocking pad lock appears it quickly shifts to the bottom right hand corner instead of the centre as normal. The phone continues to boot and from then on the screen just goes black and is unresponsive. The handset is on cause people can still ring, notifications still get received and all the hardware buttons make noise as if they are working. The screen will just not turn on. If I try doing a soft reboot with the power and volume down I can start the phone and the Samsung logo comes up as normal and the pin screen as normal but as soon as I enter my pin the same issue happens. If I hold the power button on its own to turn off the phone the multi menu (reboot, power off, emergency) all briefly appear but are enlarged and sitting on the right of the screen.
Any ideas guys, cheers.
Try reinstalling Oreo back onto it. It could be an issue with the Beta Version of Pie that you installed on your device.
The beta software is intended for this very purpose, you found a problem, then you report it to the releaser to be fixed, the creators of the software are the ones that will evaluate and improve the software, you see, it did not work for you, just try to reinstall it, if the issue persists, provide feedback to samsung, and flash a stable firmware
Possibly this bug Pie Beta + Secure Startup + WQHD = Black Screen?
It happened to me too. I installed over my existing UAE firmware with Indian one then the one ui update. After reboot got the same blank screen issue. I then did a factory reset and everything is back to normal for the last couple of days with improved battery life probably due to the reason that many region specific Samsung app like Samsung pay doesn't work.
So had a bit more of a play when I got chance and I managed to resolve the issue. Still being hit with the same problems for some reason I tried unlocking the phone again but sideways (don't ask not sure why) and the screen unlocked. From then on phone worked completely normal until next reboot. Same thing every time until I hold phone on its side and unlock with the fingerprint reader.
I've since reverted back to 8.0 and sent feedback over. I'm gonna try testing again weekend see if I have same luck.
Cheers for the replies guys, hope anyone else has this issue the comes across this.
you must disable secure start up
I had the same issue after updating to beta 1 with secure boot enabled. I wiped the phone and it started as it should, since I couldn't unlock the phone even with fingerprint. I noticed that the screen was only showing for few seconds the 1/4 of the image (unlock sim with PIN).