Hi There,
Shortly after updating my Nexus 4 to 4.2.2 OTA today the screen went blank and I've been unable to get it to function correctly again.
The phone is still showing some signs of life, I am getting notification LEDs and I am unable to unlock the phone with facial recognition even though the screen remains blank - I can tell from the vibration and the LED stopping that it has unlocked. Pressing the power button to lock it starts the notification LED again.
I have tried a hard boot (Volume Down + Power) and the screen did come on to display the google logo followed by the X but as soon as they had been shown it returned to a blank screen.
Does anybody have any ideas of what this could be or how to solve it or should I contact Google in regards to this issue?
Thanks in advance for any help
seems like the OTA update has corrupted somewhere. You should reboot into bootloader and use fastboot to flash the stock 4.2.2
Is there anything else worth trying before doing that? I wouldn't have a clue where to start as this is my first android device
Ok so I got it working but did lose all my data. If anyone else comes across this issue I had to boot into recovery mode and do a full wipe/factory reset. The first time i did this the phone started up with no problems but during configuration when I entered my Google account the blank screen strangely returned so I again did a full wipe in recovery mode, skipped the 'set-up google account' step and then entered it manually later in settings once the device had started up.
No idea what caused this and if its a bug in 4.2.2 or an issue with some settings in my google account that are being backed up and restored to the phone but either way I had no problems until 4.2.2 update installed and the issue occuring even after first data wipe rules out any third party apps being the cause.
I had a similar problem after updaing that the screen stay blank and it wo'nt unlock
As soon as i disable the bluetooth the problem solved.
It's happened when i paired it with my pc
Related
Hello I am trying to fix a friend nexus 7 first gen
the problem is that it keeps flashing the white google logo like its boot looping , the system doesn't even seem to be restarting just a flash on flash off google logo , no nexus logo or anything else at all.
I cannot get into recovery it will just shutoff everytime i try even from the bootloader menu
tablet doesn't have debugging mode on so only thing I can do is work via fastboot
already tried to flash like 5 different versions of android and everytime it finish (succesfully) and goes to restart it just keep doing the same on the google screen.
any help is greatly appriciated, and I have been searching all around the internet for hours now and have seen many solutions to bootlooping which I have pratice before on many of my other android devices but nothing like this problem.
thank you and pardon my english.
When you turn on the tablet with the power button and the screen's backlit turns up, press the VolDown button. This way you can boot into bootloader and flash a factory image provided by Google.
yup like I said before I did got into bootloader and flashed factory stock images like 10 times now and still having the same problem, this is what i usually do when I get into bootloops with any other android device but for some reason this time is different.
its not idle at google and I dont even get to see the nexus logo it just shows the google logo for one second and screen goes black then again the google logo and black screen like infinite restarts with one second delay.
Then it maybe hardware related (corrupted nand/partition/etc) so you might consider to send it to Asus/Google to repair.
So for a few weeks now, my phone has been having bootloop issues. I've been trying to fix it on my own, but no luck so far.
I can get it into download mode. Up until I tried to restore it to its stock version via the User Tool, I could get it to the factory reset options, which led to the options to wipe cache, reboot, etc. However, none of those options worked. When I attempted to reset to factory settings, I got the "dead" green android with the red triangle. Then the screen goes black and starts bootlooping again.
Once in awhile I can manage to turn it on after having it turned off for hours, or even days and it works like normal, except that if I lock it or turn it off it will end up restarting and starting to bootloop again. Which is bad seeing as it drains somewhat fast due to being overheated while having the screen constantly on.
As for my experience trying to use update recovery, it gets to the downloading part then stops and gives me this message "[011.700.147.062.092]??? ??? ? ? ????". I don't even know if I am using the correct stock rom for my phone, since I only know its MEID and model name.
do u resolved this, i have the same problem
Hey everyone,
So my phone died and then I got it charged and turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened, I think I might have accidentally turned on the secondary encryption, but this really sucks, I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode. I really hope someone can help or knows what is going on because, I really dont want to lose all my stuff.
Thanks for your time
I tried posting link but im new, if you look up s7 edge frozen encryption, its the first link , another person describes the same issue.
I had this issue. In recovery, tell it to clear the delvic cache. Then try a reboot.
It too a few attempts before the phone would not boot directly into recovery. But once i got it to do a normal boot, it started normally.
Then after it's running, back it all up, boot into recovery, and do a system restore.
Hi I wonder if anyone can help me. I restarted my phone, it asks for my pin which I enter correctly. It then gets stuck on spinning padlock. I've tried a soft reset (I think that's what it's called, holding down power and volume keys). It restarts, I enter pin, it says starting android then gets stuck again. I'm not very tech minded (typical girl). Can anyone help. I'd rather not lose all my photos and apps. Thank you so so much in advance. Toni x
I am facing the same issue, but with a Samsung Galaxy S8.
- Safe mode: doesn't boot
- Recovery mode: works, clear cache doesn't solve the problem.
So since nothing worked to make it work (except the Factory Reset, but I didn't tried this option), I decided to wait in the padlock screen. After 3 hours the phone started.
I guess that the phone is decrypting some big file during startup. Indeed, some days before before this problem happens, I downloaded some big files via torrent (~2-4 GB video files).
I'll delete these files and make some tests to understand the source of this problem.
Have same issue after recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
Have exactly the same issue..Please help
After recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
Hi All,
I installed DP2 today via OTA (fully stock, locked bootloader) on restart I have to enter my password to boot/unecrypt. When the phone is started I have to type in the password as fingerprint won't work after restarting.... at this point the screen goes blank and drops me back to the lock screen. I know it is the correct password as there is no error and it is the same password I booted with.
Is anyone else experiencing this? I think it will be a factory reset for me! (
Thanks Andi
I reset my phone and am very pleased that the google backup is so much more fully featured these days.
I think that the issue may have been caused by my companies MDM software as there was an alert / notification I could not read/action.
All working nicely on dp2 now
Hello,
So today I woke up today to find my device stuck in the google text bootloop, did a quick search on how to fix it and found this guide : https://www.xda-developers.com/nexus-6p-bootloop-fix/
I did everything and I guess it worked correctly, except the fact that now my bootloader being unlocked I stumble upon the "your device can't be checked for corruption" error, and so I'm stuck on another different bootloop. Locking the bootloader fixes the corruption error but I'm back to my previous google bootloop (even if I flashed the image that was in the guide).
So whether the bootloader is locked or not I'm stuck on one of the two bootloops (by the way I tried flashing a factory image after that but didn't fix the google loop).
Is there any way I can fix it?
Thanks!
Keagghan said:
Hello,
So today I woke up today to find my device stuck in the google text bootloop, did a quick search on how to fix it and found this guide : https://www.xda-developers.com/nexus-6p-bootloop-fix/
I did everything and I guess it worked correctly, except the fact that now my bootloader being unlocked I stumble upon the "your device can't be checked for corruption" error, and so I'm stuck on another different bootloop. Locking the bootloader fixes the corruption error but I'm back to my previous google bootloop (even if I flashed the image that was in the guide).
So whether the bootloader is locked or not I'm stuck on one of the two bootloops (by the way I tried flashing a factory image after that but didn't fix the google loop).
Is there any way I can fix it?
Thanks!
Click to expand...
Click to collapse
The corruption error you get from unlocked bootloader is nothing to worry about. It should resume after the message is displayed. Unless it pauses then you can resume by pressing the power button .
Exodusche said:
The corruption error you get from unlocked bootloader is nothing to worry about. It should resume after the message is displayed. Unless it pauses then you can resume by pressing the power button .
Click to expand...
Click to collapse
Well the problem is just that it goes into a loop, this message into google text into this message into google text etc
I'm still stuck in a bootloop except that instead of only having google text switching into black screen it's now google text switching into corruption error :/
Keagghan said:
Well the problem is just that it goes into a loop, this message into google text into this message into google text etc
I'm still stuck in a bootloop except that instead of only having google text switching into black screen it's now google text switching into corruption error :/
Click to expand...
Click to collapse
You will just have to try the bootloop threads an hopefully something will get it working. However even if you do phone will be slower maybe time for upgrade.