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.
Related
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.
I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.
Anyone else experience this? It happened after upgrading magisk, then reflashing dtbo and re patching with an earlier version of magisk.
Fingerprint gestures still works inside the OS. And when I try to register a new fingerprint, it reads my finger up until the last "read" then throws an error that the fingerprint registration has failed.
I actually have had this error, wifi also stopped working. It's something to do with Flash Kernel and the current way we have to be unlock. If you flash a stock kernel or the modded one with safteynet pass it should go back to normal.
Thanks for the reply, I wiped and started over before I saw your reply. Next time I'll try the OEM kernel first!
Anyone still having the issues with Fingerprint Hardware and Wifi after updating Magisk and flashing a new kernel? I updated Magisk to 15.3 today and also tried flashing Flash Kernel, and I can't get Wifi or fingerprint to work. Have tried flashing back to the Stock+Safetynet Pass Kernel, but still having the same issues.
I just received this error this week.
So, I should just flash stock firmware and it should be good?
Same description: fingerprint won't unlock/verify, but the gestures still work within the OS. Very annoying.
I had to flash a factory image to fully wipe in order to fix this error.
Swiftkey might be the issue
On mine -- Swiftkey was the culprit. Try removing Swiftkey.
HI,
i've installed the latest nightly (cm-12.1-20160822-NIGHTLY-xt925) for the xt925 and gapps. It was running fine so far but after a while it starts crashing during boot or "optimizing apps" and it starts over again. This happens usually after installing updates from the playstore. My guess is that streetcomplete or mapillary might cause this issue (not sure the clock app crashed often too).
So my question is, has anyone else issues with the latest nightly and found a fix?
Are there any other ROMS available? I couldn't find a lineageos Rom.
I am able to reinstall and i think it will work again buts that no solution if i can't update apps.
I'm not sure which bootloader it currently uses. It has the cyanogenmod recovery installed and wiping Cache didn't resolve the issue.
Thx
bitboy85 said:
HI,
i've installed the latest nightly (cm-12.1-20160822-NIGHTLY-xt925) for the xt925 and gapps. It was running fine so far but after a while it starts crashing during boot or "optimizing apps" and it starts over again. This happens usually after installing updates from the playstore. My guess is that streetcomplete or mapillary might cause this issue (not sure the clock app crashed often too).
So my question is, has anyone else issues with the latest nightly and found a fix?
Are there any other ROMS available? I couldn't find a lineageos Rom.
I am able to reinstall and i think it will work again buts that no solution if i can't update apps.
I'm not sure which bootloader it currently uses. It has the cyanogenmod recovery installed and wiping Cache didn't resolve the issue.
Thx
Click to expand...
Click to collapse
For some reason all the official nightlies i have tried have this issue, some cant even make it past the setup screen. I guess something bad ended up in the sources.
Its not maintained anymore for our devices but one of the best CM12 builds in my experience was Mokee OS. You can run the builds for the Photon Q (xt897) just make sure its the old one- i recall having issues with the more recent builds.
Personally though i have moved on to the Nougat builds. I'm currently running the builds for the xt907 and they work fine with my xt926. The crDroid build seems to be the most stable - https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571 The only requirements are you must be running the JBBL and the TWRP version for the XT907 (its linked in the ROMs thread instructions). You also need to format your data and cache partitions as F2FS.
Currently, I am crDroid version 5.11 and any problems I initially had with that custom ROM before are now non-existent. The ROM seems to run a tad smoother than the RETUS Stock ROM I was using before and the internet seems like it runs faster be it on WiFi or Mobile Data considering I was able to update and reinstall apps faster than on Stock ROM. With these, I can see why people still use Custom ROMs. Prior to currently using crDroid 5.11, here's all the software (including stock roms) I have used also. If it helps, my current carrier is MetroPCS.
Metro Stock ROM: Not as smooth considering there are extra Metro apps I don't need. I also can't choose the option to turn off LTE and use HSPA. It's either use LTE or use 2G on that ROM.
RETUS Stock ROM: You can count on stability, but definitely not as smooth. Felt like I could do better, so that's why I'm looking at custom ROMs.
Lineage OS 16: There's an issue where sometimes when I lock the screen, the colors become inverted and I have to keep changing the liveDisplay settings to bring the colors back to normal. No idea how to permanently resolve this.
crDroid 5.12: Does not install properly on my phone at all. Just leads to a black screen after installation with Orangefox/TWRP.
crDroid 6.4: Phone soft bricks when I install Magisk for some reason on that software.
crDroid 6.5: No soft brick when installing Magisk on this one, but the speaker, especially at it's max volume, is too low.
Havoc OS 3.4: Does not install properly either and only boots into OrangeFox recovery with no option to Factory Reset. Might give it another shot, but unsure if Magisk will work on that one or not.
There are a few others listed on the Custom ROMs section I haven't tried, but would like to get the opinion of others before attempting to flash any of them.
Use the command "fastboot -w" in bootloader mode instead of using a recovery to factory reset to get Roms like havoc to boot.
reydarz said:
Use the command "fastboot -w" in bootloader mode instead of using a recovery to factory reset to get Roms like havoc to boot.
Click to expand...
Click to collapse
I'll try that. Thanks. Sorry for the late reply, by the way.
Okay, so I was able to get Havoc to boot, but the problem is that I have no phone signal whatsoever on that ROM.