• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Black screen on pixel 2

S

sali01

Guest
I installed an app from playstore and while using it screen went black. I tried to use power button to restart but did not work then i tried power + vol down no effect ,basically the buttons trick is not working to get to the bootloader or safe mode screens.

I have heard and read that maybe i have destroyed or erased by bootloader that is why i cannot access it to flash a new OS or enter safe mode. I want to know what exactly has happened ?

So basically :
-None of button combo are working to pull up the bootloader (so plesae dont suggest using buttons)
-I do get occasionally red dot blinking on top right , but it goes away when i plug the charger according to google its low charge light.
-Also when plugged in to charger i donot see battery charging animation.
- i tired to connect to adb while phone is on black screen. But adb devices does not detect the phone.
- phone was on latest android 10 stock

What can i do from here onwards to get this phone to work ? How can i install brand new OS or bootloader or whatever is necessary to make it work. Please guide me.
 
It would help if you told us a bit more about the phone, especially whether the bootloader is unlocked or whether it is rooted (or otherwise modified).

But it should be more or less impossible to delete the bootloader using an app, even on a rooted phone. Though if you have there is nothing you can do unless you have specialist equipment and know how to use it: you need the bootloader in order to flash a factory image. So if, and that's still an if at this point, that is the situation you'll have to get it repaired professionally.

My starting point is to eliminate the simplest possibility: that it's just the screen not working. That sounds unlikely, but nothing you've said completely excludes the possibility - though if that is the case it sounds like a hardware failure rather than software (it is was software you'd see the usual splash screen, bootloader etc, just it would go black when you booted into Android). ADB will only work if you already have it enabled and have left the computer authorised, but if it is the display you'd be able to boot it normally (press and hold power key for 20 seconds or so to force a restart - even if you can't see what is happening) and then call it, so it's very easy to exclude this possibility.

Another possibility, perhaps more likely, is a catastrophic battery failure. The phone always runs off the battery, even when plugged in to a charger, so if the battery has failed completely it could produce the results you see.

Obviously if it is either of these things the only solution is a repair. And also if it's a hardware failure then it's nothing to do with the app, that's just a coincidence.

Please give us any more information you have, but so far my instincts are that whatever the cause is this isn't a home repair: either it's a hardware fault or (less likely) the firmware is so corrupted that you'll need a jtag rig or similar to get it to a state where you can reflash it (and it's really, really hard to see how it could get into that state when you were running Android. I know how to do that to a phone - it's very obvious to anyone who knows a little about them - but I'd have to be running fastboot rather than an android app).
 
  • Like
Reactions: sali01 and Dannydet
Upvote 0
It would help if you told us a bit more about the phone, especially whether the bootloader is unlocked or whether it is rooted (or otherwise modified).

But it should be more or less impossible to delete the bootloader using an app, even on a rooted phone. Though if you have there is nothing you can do unless you have specialist equipment and know how to use it: you need the bootloader in order to flash a factory image. So if, and that's still an if at this point, that is the situation you'll have to get it repaired professionally.

My starting point is to eliminate the simplest possibility: that it's just the screen not working. That sounds unlikely, but nothing you've said completely excludes the possibility - though if that is the case it sounds like a hardware failure rather than software (it is was software you'd see the usual splash screen, bootloader etc, just it would go black when you booted into Android). ADB will only work if you already have it enabled and have left the computer authorised, but if it is the display you'd be able to boot it normally (press and hold power key for 20 seconds or so to force a restart - even if you can't see what is happening) and then call it, so it's very easy to exclude this possibility.

Another possibility, perhaps more likely, is a catastrophic battery failure. The phone always runs off the battery, even when plugged in to a charger, so if the battery has failed completely it could produce the results you see.

Obviously if it is either of these things the only solution is a repair. And also if it's a hardware failure then it's nothing to do with the app, that's just a coincidence.

Please give us any more information you have, but so far my instincts are that whatever the cause is this isn't a home repair: either it's a hardware fault or (less likely) the firmware is so corrupted that you'll need a jtag rig or similar to get it to a state where you can reflash it (and it's really, really hard to see how it could get into that state when you were running Android. I know how to do that to a phone - it's very obvious to anyone who knows a little about them - but I'd have to be running fastboot rather than an android app).

I'm the same person who started the thread just shifted from guest to new account to reply to you.

Thanks for the detailed reply, really appreciate it. Based on your answer it might be possible this is a battery issue. I do have some additional info for your to base your conclusion on :

When i installed the said app and was using it the phone turned black and i instantly though of pressing the power button to restart and it did restart once but only upto the google logo not beyond that and when black again. Then i tried it again and it did show the google logo. But that was the last time it showed google logo or something on the screen. So basically after the first blackout it showed google logo twice when power button was pressed. Does this info help ?

As for the unlocked bootloader i am not sure maybe maybe not. I do know that developer mode is enabled and USB debugging and OEM unlocking too. Does this help my situation ?
 
Upvote 0
Phone crashes, attempts to restart, gets less far each time. Yes, that helps: it rules out a display problem, but is consistent with a battery problem. I also think it makes a bootloader corruption even less likely: if that were the case I would expect it to do the same thing each time, rather than progressively degenerating over 3 restarts.

Enabling OEM unlocking is a necessary step towards unlocking the bootloader but does not in itself unlock it (though unless you were planning to unlock it I don't know why you'd enable it). You need to use a fastboot command to complete the unlocking, so if you've not done that the bootloader isn't unlocked.

But my guess is the battery. You could try just plugging it into a charger (not a computer but a proper charger) and leaving it for many hours, maybe a day. If the battery is completely depleted it may require some time trickle charging before it will actually begin to charge normally, so in the best case if you leave it on charge for an extended period it might come back to life. But even if this works I would have a lot of doubts about the battery health after this, and there are no guarantees that it will - it's just the one thing I can think of to try.
 
  • Like
Reactions: sali01 and Dannydet
Upvote 0
Phone crashes, attempts to restart, gets less far each time. Yes, that helps: it rules out a display problem, but is consistent with a battery problem. I also think it makes a bootloader corruption even less likely: if that were the case I would expect it to do the same thing each time, rather than progressively degenerating over 3 restarts.

Enabling OEM unlocking is a necessary step towards unlocking the bootloader but does not in itself unlock it (though unless you were planning to unlock it I don't know why you'd enable it). You need to use a fastboot command to complete the unlocking, so if you've not done that the bootloader isn't unlocked.

But my guess is the battery. You could try just plugging it into a charger (not a computer but a proper charger) and leaving it for many hours, maybe a day. If the battery is completely depleted it may require some time trickle charging before it will actually begin to charge normally, so in the best case if you leave it on charge for an extended period it might come back to life. But even if this works I would have a lot of doubts about the battery health after this, and there are no guarantees that it will - it's just the one thing I can think of to try.

Yes i did OEM unlock because i was planning to flash an older version of stock android a few weeks back but abandoned the plan but did not untick OEM unlock so its ticked. But i did not follow the step to connect with adb or use the fastboot command. So i guess it still a locked bootloader.

Most likely this is a battery issue. Is there any way to check and verify this is a battery issue starting with the most non intrusive way (i.e not opening the phone). I also i don't want to go out and buy a new battery just to find out later that this is not a battery issue. How do you suggest being dead sure that i need to buy a new battery ?

As for charging i have tried several times to charge it enough to see the google logo screen leaving it plugged for upto max 1hr but to no avail. After plugging in the red light does disappear for sometime though. i try leaving for a day now.
 
Last edited:
Upvote 0
I have a brand-new Google Pixel 2. Today the phone fell of like 20 centimeters from my hand to a table (literally nothing). But the phone showed a blue screen with lines and then screen went black. I tried to turn it but the screen did not go on, however, I noticed the phone vibrated when I touched the screen. It also vibrated when I rang it with another phone. I tried to do a reset, hard reset, safe mode... but it doesn't work. However, the screen goes white for a split of a second and then black again. I plugged it to the laptop and it recognises the device.
screen is done. no amount of troubleshooting will fix a hardware issue. either get it fixed or get a new phone at this point.
 
  • Like
Reactions: Hadron and Dannydet
Upvote 0
Yeah, it's hardware. May be as simple as a damaged contact, but no amount of resets will fix it. And since it started with a drop this was always going to be the case.

It may have landed in just the wrong spot, or it may have added to damage that had been done previously. But practically it makes no difference.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones