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
Related
my nexus 7 puts itsekf to sleep and I can get to the passcode screen but when I enter the password it resets itself straight back to the password screen again! i have to do a system reboot to get it to work. I am running a clean version of the latest version of android and i dont know what is causing the bug but I`m assuming it mudt be software rather than hardware. any help is appreciated!
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
I was running CM 12.0 for a long time with encryption and no major issues, until recently I upgraded to 12.1, without formatting etc. Then I had this issue.. after the full boot, the phone reboots in a boot-loop at the pattern unlock screen. If I turned it off fully and restart, I would get to the SIM unlock screen, with the unlock dots showing below that, and after inputting the PIN it dissapears to a blank screen, where you can just pull the Dialer out, but with phone still not decrypted.
So I went into TWRP, pulled my data, fully formatted and started clean, installed 12.1 from scratch and used it for some days without any problems... until I turned encryption on, and after ~12 or so minutes (with the Android logo and some text saying it's encrypting etc).. I have exactly the same issue.
What's going on? Can I fix this without having to format all again?
Update: if I remove the SIM card it works, so maybe the issue is not directly related to the encryption.
Update2: the following steps seemed to resolve it, for now.. not sure what will happen on next reboot:
Remove SIM card
Access phone normally
Go to settings, Security, pattern unlock
Remove the lock. Then turn it on again (you'll need to draw the pattern once more)
Turn off.
Insert SIM back
~Working with some minor issues.
I have a stock moto x play whose hardware sku is XT1564. It's on android ver 5.1.1 and system version is 23.21.25.lux_lra.en.US
I have not performed any soft mods or alterations, be it root or bl unlocking.
The only thing that I would think is different than normal is that the phone is encrypted, so it asks for password whenever it boots up.
I got a notification to update to 24.74.5.en.US a few days ago and decided to try doing it today.
It downloads the update fine and when I press on the notification for it to start the update process where it says it needs to perform a reboot to update it goes into a "phone will reboot in 10 seconds" screen and when countdown finished it shows the "shutting down..." popup that appreas when you try to shutdown the phone.
Then the phone stays with that popup until it finally shutsdown like 4 minutes later on what appears to be a hard shutdown because it doesn't reboot. I have to manually power it on and then the phone starts up normally asks me for my password and about a minute after android fully loads the phone tries to shutdown again without any input. And then it just keeps doing that until I boot the phone into fastboot and try to get it to bootloader, where it shows the dead android logo with a red yield sign and promptly shutsdown. Then when I start the phone normally it shows an "update unsuccessful" screen.
Anyone have any idea what might be the problem?
I've been thinking it might be the encryption but IDK. Also I've checked the thread with the firmware versions and couldn't find mine there. Is there a way I could dump mine for backup in case I **** something up trying to get OTA to work.(without unlocking bootloader and rooting, of course)
Now the update has stopped appearing and I can't get it to recognize there being an update for this device.
Fudge!
Hello everybody,
two days ago, my Mi A1 just spontaniously restarted while running.
But since then it is stuck in the "Android one" screen. With multiple restarts, I finally manage to get to the unlock screen.
If I then enter my pattern the screen changes to "Android is starting", but after two seconds the phone restarts again until I'm at the "Android one" screen again.
So I can't enter the actual system.
I can enter the stock bootloader and also fastboot, but I'm not entirely sure what I can do there (except a factory reset).
I also tried to enter the failsafe mode (by hitting the shutdown icon longer in the unlock screen), but the phone just normally restarts as mentioned early. I don't seem to get into that mode.
My suspicion:
For a few months I'm running out of disk space. Because of that I couldn't install all the big updates lately. I suspect, that the OS somehow forced an update that failed because of the space issue. At least this is the only thing that I notice lately what could explain the situation.
Do I have other options to resolve my problem, except a factory reset?
My last backup is two months old, so I would survive deleting everything, but it would be way better if I don't have to
Do you guys have any hints for me?
regards and thanks in advance,
koala
I was getting nervous and just did the factory reset.
And it seems to have worked just fine.
Some data is lost though.