My phone screen stopped functioning, as in it stays as a black screen no matter what, during boot up, recovery, and Fastboot screen. The phone system itself is still functioning, If I boot into the system I get notifications from my apps which causes the notification LED to go off and I feel notification vibrations.
The most confusing part about this is it happened randomly, I checked my phone in the morning and it was fine, I shut it down and left it for an hour and came back and that's when I started having this issue.
I have tried rebooting the phone many times, and also to recovery and Fastboot and no luck, the screen stays black. I can fortunately access my files through my computer when I connect it through usb and its in the recovery screen. Also, Fastboot recognizes my device through my pc when its in Fastboot mode.
I have checked it around and it doesn't seem anyone has had this issue except maybe this guy:
https://forum.xda-developers.com/mi-9t/help/black-screen-9t-t3999649
But he doesn't seem to have found a solution.
As for my ROM, I was running Pixel Experience Buttery Smooth and I have also used the screen overclock mod:
https://forum.xda-developers.com/mi-9t/themes/screen-overclock-mode-t4079693
However It never ended up working for me so I stopped using it months ago.
If anyone has any suggestions for what I can do, I am extremely desperate as sending this phone for repairs is going to be really hard to do, I am really hoping this is an issue I can solve without doing that.
Thank you for any help
So I decided to try accessing my phone through my Pc by using a software like Vylor to mirror my screen to my PC, the problem is I can't get my device to be recoginzed by ADB. It is recognized by fastboot when in fastboot mode and when it is in recovery I can access all my files through the file explorer. However, when I boot my phone normally it adb does not list it under adb devices when it is connected through USB.
Does anyone know what could be the issue? I am sure I had usb debugging on before by screen stopped working.
Related
Hello,
my friend has a problem with his phone. He neither installed a custom rom, nor he rooted it. He updated OTA and after a week, while he was talking, the phone shut down.
When he powers it on the screen lights up and nothing else happens. Sometimes the vodafone splash came up, but nothing more.
I don't know if the phone boots into recovery as I don't see anything on the screen.
I tried booting to fastboot mode, and the pc detects it. But I whatever I try to do, (flash,erase etc) I get the error: Remote not allowed...
Any ideas how to fix it?
Have you considered hardware problem?
Yes I have but first i want to make sure that it isn't any software problem
Hello people,
I have a German Nexus 4 and it gets stuck in bootloop whenever I turn the power on.
I've had issues with the phone since the last few months - i.e. random reboots, random program crashes.
But recently I tried to root it in order to install the Android L developer preview. It was during the booting process, when my Nexus crashed and it has been unable to boot ever since.
When I push all three buttons (power + 2 volume rocker buttons) simultaneously, I get the fastboot screen.
Choosing the following options has these effects:
Start --> phone tries to boot but gets stuck in bootloop forever and ever
Restart bootloader --> restarts the fastboot screen
Recovery mode --> phone shows the robot with an opened belly and a red warning sign (see photograph)*
Power Off --> turns the power off
Also, it is NOT detected or recognized by my Macbook when I connect the Nexus via USB cable. So it's impossible for me to access the phone via my Macbook.
*This is the screen shown when I try to go into Recovery mode in fastboot:
[can't upload outside link to image]
So this leaves me with no options as I never get further than the 4 turning circles forever and ever.
Is my Nexus 4 broken or is there still a chance to unbrick it? (I have a MacBook, so Windows programs won't work for me)
Of course it's not possible to recognize it when OS is not running.
Download WugFresh toolkit, ADB drivers (Universal) and the factory image. Enter fastboot, connect USB and flash the image
Your phone is not hardbricked, because it boots into the bootloader.
It might be recovered if you can access it with fastboot.
Try uninstalling all related drivers and install the Naked Universal Driver.
Thanks for your replies!
Unfortunately, the programs you mentionned don't work on my Mac (they seem to be Windows-only).
Also, how can I install stuff on my Nexus? Since it is not recognized by my MacBook, I can't load any files onto my Nexus.
And since any command on the fastboot screen only leads to the phone powered off, restart of the fastboot screen or the mentionned bootloop, I cannot perform any actions on the Nexus ...
Go to a friend with Windows.
Problem solved!
Somehow after the 1000th bootloop I finally reached the screen where I could wipe the phone.
And then it finally booted! Now all the data are lost and it's like a new phone, but at least it's working again!
How long was the boot loop? Was it the new boot animation from L?
Because when you flash L, the first boot up may take up to 15 minutes, leading you into thinking it's a boot loop.
I might have bricked my LG G2.
Here is everything I did:
-I rooted the phone with the IO root kit
-wanted to installed a recovery so I installed TWRP manager
-applied SD card patch
-tried to install recovery with TWRP manager several times but app always crashed
-installed SDK on the PC
-started adb and executed "adb reboot bootloader"
the phone got a backlight screen and hasnt been reacting so far.
When I held the power button the screen went black but sometimes the backlight appeard again. I don't know how to reproduce the backlight though.
adb can't detect the phone when connected to the PC.
As soon as I plug it in dozens of Partitions show up. Windows show an error message for each of these partitions. It says I have to format the volumes to use them.
After testing I realized that everytime i long-press the power button for a few seconds the windows errors start popping up.
When i long pressed the power button for 30+ seconds to completely shut it down the notification LED started blinking red 8 times in roughly second intervals. then there was a short break and the 8 blinks repeated.
Thank you for all help, it would suck to have a 1 day old phone broke...
You probably chose the wrong device in TWRP Manager. Choosing the wrong device can easily lead to a brick because TWRP Manager may attempt to flash to the wrong partition. The G2 does not have a TWRP Manager flash available due to loki, so you couldn't have chosen the right device.
Almost have the same problem... the only difference is my black screen is blinking continuously while it is connected to the mac... Seems like it tries to boot but gets blocked and retries in a loop. Tried around now for two evenings without any progress...
Anybody who can help?
Tried to install a custom ROM on my old N4 via Toolkit but got a bootloop on the Nitrogen logo. Right after the screen the phone would turn off. So, i rolled back to stock rom, unrooted and everything but now it seems the problem its even worse: the boot doesnt go past the Google logo. When the phone is charging i can access the recovery and even boot into Android. Off the charge it looks like i cant do nothing other than go to fastboot. If i choose the recovery option the phone turn itself off. I tried to install other ROM via TWRP when charging, but right after 2 seconds after the process begins, the phone turns off.
I think it may be a battery problem, but i wanna make sure it is so i dont waste money.
Thanks
Pwoper said:
Tried to install a custom ROM on my old N4 via Toolkit but got a bootloop on the Nitrogen logo. Right after the screen the phone would turn off. So, i rolled back to stock rom, unrooted and everything but now it seems the problem its even worse: the boot doesnt go past the Google logo. When the phone is charging i can access the recovery and even boot into Android. Off the charge it looks like i cant do nothing other than go to fastboot. If i choose the recovery option the phone turn itself off. I tried to install other ROM via TWRP when charging, but right after 2 seconds after the process begins, the phone turns off.
I think it may be a battery problem, but i wanna make sure it is so i dont waste money.
Thanks
Click to expand...
Click to collapse
hi buddy, problem is also happend to me, unfortunatly its not a software issue , its a battery problem, and its only fix with changing battery or you could turn on airplane mode (to turn off radio and only in custom rom) and keep using the phone offline.
Hello friends, I have a similar problem with my nexus 4.
I can use the device well if it is connected to a USB or plug. (If the device isn't connected, this turns off). But I can use TWRP without problems (works without connect to a USB or plug), I can install ROMS until finish, but when I want to start the system, only stuck on Google Logo and the device turns off (I tried to start the device but just stuck in Google Logo and turns off again) But if it is connected to a USB or plug works well without problems.
I tried to install all STOCK roms too but only work well when the device is connected. I think that isn't a battery problem because I can use TWRP (without connect to a usb or plug) and install every rom.:crying:
Someone would like to help me. Thanks a lot.
Angel Hyerald said:
Hello friends, I have a similar problem with my nexus 4.
I can use the device well if it is connected to a USB or plug. (If the device isn't connected, this turns off). But I can use TWRP without problems (works without connect to a USB or plug), I can install ROMS until finish, but when I want to start the system, only stuck on Google Logo and the device turns off (I tried to start the device but just stuck in Google Logo and turns off again) But if it is connected to a USB or plug works well without problems.
I tried to install all STOCK roms too but only work well when the device is connected. I think that isn't a battery problem because I can use TWRP (without connect to a usb or plug) and install every rom.:crying:
Someone would like to help me. Thanks a lot.
Click to expand...
Click to collapse
i told just above your post,that is a battery problem and only fixes with changing battery, the reason you can use twrp is that the voltage needed for boot phone in recovery mode is less than for booting the whole system with apps and radio functions
If I have my phone off, and power it on it will boot straight into the bootloader but have a black screen, if I press the powerbutton I assume I am choosing "resume poweron" because the phone restarts and then powers up with a black screen for 30 seconds before the animated part of the boot animation starts.
I have done a full reflash(afaik) from LOLINET using my device model file XT1926-5 and my region RETAPAC and when I reboot it still has the black screen.
I have Magisk installed and I believe my bootloader is unlocked, the only thing I remember doing was trying to flash TWRP but I have done a full restore since then using LOLINET.
Usually a black screen like this wouldn't be a problem, however the real annoyance is my phone constantly will freeze up for no reason, I will be mid way writing a message and the whole phone will hard freeze, I have tried doing another restore to see if this will fix it and alas it has not, so I am at a loss to what is going on, I have booted into TWRP and tried repairing partitons thinking something could be flipped and it was angry but no.
So I am a tad bit out of ideas unless anyone has anything for me? Logcat doesn't turn up anything interesting reguarding the crashes, I haven't found any events that are logged with ERROR,ASSERT or WARNING at the time of crash.
Anyone got something for me?
WhatDreamIsthat said:
If I have my phone off, and power it on it will boot straight into the bootloader but have a black screen, if I press the powerbutton I assume I am choosing "resume poweron" because the phone restarts and then powers up with a black screen for 30 seconds before the animated part of the boot animation starts.
I have done a full reflash(afaik) from LOLINET using my device model file XT1926-5 and my region RETAPAC and when I reboot it still has the black screen.
I have Magisk installed and I believe my bootloader is unlocked, the only thing I remember doing was trying to flash TWRP but I have done a full restore since then using LOLINET.
Usually a black screen like this wouldn't be a problem, however the real annoyance is my phone constantly will freeze up for no reason, I will be mid way writing a message and the whole phone will hard freeze, I have tried doing another restore to see if this will fix it and alas it has not, so I am at a loss to what is going on, I have booted into TWRP and tried repairing partitons thinking something could be flipped and it was angry but no.
So I am a tad bit out of ideas unless anyone has anything for me? Logcat doesn't turn up anything interesting reguarding the crashes, I haven't found any events that are logged with ERROR,ASSERT or WARNING at the time of crash.
Anyone got something for me?
Click to expand...
Click to collapse
Are you able to get in recovery mode, or the bootloader just freeze.
If I try go to recovery it falls through tight away to the boot loader
riyan65 said:
Are you able to get in recovery mode, or the bootloader just freeze.
Click to expand...
Click to collapse
Even if I use adb reboot recovery it just reboots into the black screen fastboot.