99.9% sure CM 11 night dec 6th after flashing and setting up security lock screen pin, has forgotten my pin and cannot get back into phone. I can wipe and reflash but wondering if this a bug and should avoid this build. Any one else?
Related
I'm using the latest eos 4g ics ROM and flashing the gapps file. when I try to use face unlock the program tries to display. then it appears to freeze. once it freezes I have to use my alternate security to enter my xoom. once unlocked the system tells me face unlock has stopped running.
anyone know why this would be happening?
If it worked on previous versions, just flash back. Nightlies aren't known for their stability.
Just downloaded the most recent update for cm10 and i had my security pattern grid set to a 6X6 grid. since the update i am unable to unlock my phone and wont even prompt me to put in my email to unlock it, if cm10 even supports that like the stock roms did, but i need a way to unlock it. any ideas?
i was thinking of just grabbing the update before that and flash it over it and unlock and disable the pattern then apply the update
but the reason i cannot unlock is because the grid went from a 6x6 to a 3x3
Whatever you do, do not try to use the CM Updater to go back to an earlier build. I did that and it put me into boot loop. I opened up CWM thinking I'd just restore to the backup I made just before updating and it can't find my backup.
I've updated my moto g to cm13/marshmallow 6.0.1 nightly build on 15th Dec and have been facing WiFi connectivity issues since then(it keeps disconnecting every 10-15 seconds). I am aware that nightly builds are unstable, but now I am unable to get back to lollipop and stuck. I tried to factory reset the phone but no success. Does anybody have a workaround or any solution to this.
Eagerly waiting for reply!
Did you tried to wipe the /data partition from TWRP Recovery to fix the issue ? Try to upgrade to the latest nightly from CM.
Its a cm13 bug all device i know that using cm13 have the same issue in wifi if im right that problem is in the WPA-PSK/WPA2-PSK security on because when i remove the security on my wifi connection it doesnt disconnect anymore, and i think the cm13 doesnt support old wifi router's wifi security
I'm having some issues with my pixel:
Unlocked, but Stock (no root, no twrp) on Android Beta NPG05E (7.1.2). Yesterday morning I've had some issues with hangouts (receiving, but not sending any messages), so I restarted my phone.
On the first reboot it was stuck with the dots animation, at some point i restarted it again by pressing the power button for a long time (like 30 sec?).
This time the phone was booting into OS but there are even more issues: Fingerprint reader not working ("hardware not available") - but gestures do, displays that mobile data is disabled (but is actually enabled), having no notifications at all, the navigation bar button to switch apps does not work (vibration feedback, but no action triggered) and probably a lot more.
Next I checked for Software Updates and also found one - the beta OTA! Seeing this I remembered that the beta dialog was not present at the last boot up and also noticed that Android Version is 7.1.1
This also explains all the issues - going back from Beta to stock is not supported without wipe.
(now i know: --> Somehow the phone might have switched between the two slots?)
While all this happened while I was still on vacation, I then applied the OTA once again and was back to 7.1.2 - but the issues weren't gone. Only Fingerprint reader was working again, the other problems remained.
So next I would probably need to do a factory reset - but I wanted to make a backup with TitaniumBackup first:
Booting TWRP RC1, flashing SuperSU 2.79 SR3, reboot --> no binary found (?)
So I checked and I was back to 7.1.1 again!
Using TWRP I could see that I was on slot B - the build.prop says NMF26U (7.1.1), while on slot A was NPG05E (7.1.2 Beta). So I switched the active slot to A and was on 7.1.2 Beta again - and SuperSU is running well (which means SuperSU installer actually installed on the correct slot, but somehow it got switched right after flash or during reboot).
Did somebody experience something similar? Do you know if there is anything else (besides an OTA) which changes the active slot?
I will probably go for a TB backup now, factory reset and restore the user apps.
Hi guys and gals I have a small issue/ question . I wanted to downgrade to official build from 7.1.2 so I flashed the latest official image but there are at least three issues I found. The notification panel doesn't pull all the way down nor does it display new notifications. Also the fingerprint scanner does work. It says something about hardware not being available. Also home and recent buttons don't work. Is there something I can do without factory reset. Maybe resetting application's data or cache? Any ideas please?