Related
I can no longer seem to be able to install custom roms,ive tried the resurrection remix rom and the cm13 rom but both are asking for a password after it installs and reboot(like when you encrypt the phone) so i cant access anything and my google password does nothing nor have i set another password
All i can do is the three finger recovery and reflash a full stock rom which does work.
I have checked the OEM unlock in developer options as well and full wiped before installing roms.
There shouldnt be any anti theft on the phone because afaik i have disabled all the anti theft options so there should be no reason why it asks for a password.
Does anyone have any idea why this is happening?
Does anyone know if doing a full factory reset through twrp instead of through the phone could be the reason why?
Good to see someone else is also having this ****ing stupid problem. I've been struggling with a way to fix this as well. I'm on the EVA-109 with a single SIM and its been giving me this problem no matter what I do. I read through one of posts on the CM 13 thread which stated you need to use Surdu's tweaked TWRP in order to not have the password booting problem. It'd be nice to get an official response from Surdu on this as he hasn't mentioned the need to use his version of TWRP.
Although, despite trying this I'm still having the password problem at boot but it might be worth a try if you do it. I'll pass you the link - Do let me know how it goes, though I wouldn't place all my faith in this. https://forum.xda-developers.com/p9/development/twrp-t3493979
My Moto X4 XT1900-2 Fingerprint Sensor Not Working, Even It's Option is Missing From Setting, Anyone Having Same Issue ?????
Ritesh Mhatre said:
My Moto X4 XT1900-2 Fingerprint Sensor Not Working, Even It's Option is Missing From Setting, Anyone Having Same Issue ?????
Click to expand...
Click to collapse
Try factory reset
I do...but doesn't solved
Did you flash any ROM on it ? Maybe you tried to downgrade the device from Oreo ?
Today when I tried to find a solution to not installing OTA, I've flashed 7.1.1 as a downgrade. It failed, but after reboot my fingerprint sensor disappeared, too. Then after I reflashed Android 8 it appeared again.
emcom said:
Did you flash any ROM on it ? Maybe you tried to downgrade the device from Oreo ?
Today when I tried to find a solution to not installing OTA, I've flashed 7.1.1 as a downgrade. It failed, but after reboot my fingerprint sensor disappeared, too. Then after I reflashed Android 8 it appeared again.
Click to expand...
Click to collapse
It doesn't unlocked my bootloader ??????
Coz i doesn't want to void my warranty !!!!!
Ritesh Mhatre said:
It doesn't unlocked my bootloader ??????
Coz i doesn't want to void my warranty !!!!!
Click to expand...
Click to collapse
So, what were you doing with the phone ? Flashing it ? Any information ?
flashing will unlocked my bootloader or not ????
Can't you answer simple question ?
WHAT WERE YOU DOING WITH THE PHONE ?
Set a pin or password security and the option to unlock it with the fingerprint will appear again
MeltingSnowman said:
Set a pin or password security and the option to unlock it with the fingerprint will appear again
Click to expand...
Click to collapse
It doesn't appear
When you did a factory reset did you restore from backup afterwards or set it up as a new phone? If you set it up as a new phone and it still didn't work then I'd say you probably need to contact Motorola and ask about getting it repaired.
trwrt said:
When you did a factory reset did you restore from backup afterwards or set it up as a new phone? If you set it up as a new phone and it still didn't work then I'd say you probably need to contact Motorola and ask about getting it repaired.
Click to expand...
Click to collapse
Ohk..thank you
Bro i have the same problem
Yes i have same issue
Till yesterday fingerprint sensor was working absolutely fine, and then suddenly it stopped working, then after i tried restarting device but didn't solved. Anyone has the solution then please help me
+1, same problem
i do have the same problem, no fingerprint option in security and the senser is not reacting on anything.
had fingerprints registered and working, but after the first october update the problem occurs.
When i flash back to los 15.1 build from 2018-09-26 the fingerprint sensor works again, option to configure reapears and all already registered prints are there.
Karamelmar said:
i do have the same problem, no fingerprint option in security and the senser is not reacting on anything.
had fingerprints registered and working, but after the first october update the problem occurs.
When i flash back to los 15.1 build from 2018-09-26 the fingerprint sensor works again, option to configure reapears and all already registered prints are there.
Click to expand...
Click to collapse
Then you need to remove those fingerprints before flashing back to stock
bcrichster said:
Then you need to remove those fingerprints before flashing back to stock
Click to expand...
Click to collapse
My post was a little unclear, sorry. i am on los 15.1 and do have this issue on any build after 2018-09-26. i already opened up a regression on los jira bug/regression tracker (REGRESSION-2178), but since no one voted for it or seems to have this problem, i though it may be some step i took.
Anyway. in the meantime i tried to clear all fingerprints before flashing but it did not help
(i did not flash back to stock but to los)
I also did a complete factory reset, formatted data/ wiped everything and then did a fresh install of los 15.1 most recent build, but still got the problem.
I bet you still have a fingerprint file somewhere that needs removed..
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
I bet you still have a fingerprint file somewhere that needs removed..
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
@bcrichster: Thanks for pointing me in the right direction...
i flashed back to los 15.1 (2018-09-26), removed the fingerprintes and pin, flashed to the most recent version of los 15.1 but it did not work.
flashed the build LOS 15.1 (2018-10-30), then the menu was there and the sensor works!
So my question: where are the fingerprint files on the x4 stored... read about fingerprints and searched on the device, but did not find them...
Is there a difference between Slot A/B regarding the fingerprints?
Thanks
I had the same issue when I first flashed RR room. Ended up flashing back to stock then going through the whole custom ROM setup again. Fixed the sensor and all the other little issues I was having (no headphone sound, etc). Not sure what the underlying issue was but for the sensor, left over files makes sense.
Hi all
in july 2017 i made a big mistake: i tried to install an xposed module on my mi5 with MIUI.This affected my phone with many bugs,so i uninstalled the module but i couldn't solve all of them...
Initially,i had seldom a touch screen bug,that forced me to switch-off my phone and then switch-on it again to solve the problem.Now,in addition to that,passing by Android 7 to 8,i have one more important bug:every time i switch on my phone,my proximity sensor go out of calibration,forcing me to go in diagnostics menu where i can manually calibrate it.This bug is so important that convinced me to swipe again everything and then flash my xiaomi.eu rom not 1,but 2 times.I also tried to change recovery,or swipe/repair system.
If i remember well i tried to install xposed from this page or similar one ( https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634)
can you try to help me?
thank you very much
P.S. : i still have to try fastboot global rom flash to solve it but i don't want to do it
Fastboot flash is needed.
emalele94 said:
Hi all
in july 2017 i made a big mistake: i tried to install an xposed module on my mi5 with MIUI.This affected my phone with many bugs,so i uninstalled the module but i couldn't solve all of them...
Initially,i had seldom a touch screen bug,that forced me to switch-off my phone and then switch-on it again to solve the problem.Now,in addition to that,passing by Android 7 to 8,i have one more important bug:every time i switch on my phone,my proximity sensor go out of calibration,forcing me to go in diagnostics menu where i can manually calibrate it.This bug is so important that convinced me to swipe again everything and then flash my xiaomi.eu rom not 1,but 2 times.I also tried to change recovery,or swipe/repair system.
If i remember well i tried to install xposed from this page or similar one ( https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634)
can you try to help me?
thank you very much
P.S. : i still have to try fastboot global rom flash to solve it but i don't want to do it
Click to expand...
Click to collapse
That's probably a firmware level problem. You can try to update/downgrade your firmware, but probably end up reflash your OS from fastboot.
Which rom have i ti flash via fastboot?global rom,global stable,others?and can i do it via mi flash?
I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.
Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..
As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:
summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!
Gdhhs
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
baleskoil said:
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
Click to expand...
Click to collapse
Did you find a solution?
Nope
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
baleskoil said:
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
Click to expand...
Click to collapse
As of right now me and you are the only two that seem to have this issue.when I get home from work I'm going to go ahead and I'm actually going to relock my bootloader and and do everything and then I'm going to unlock it and see what happens.I can let you know in this thread if it works for me and that way you don't have to waste your time unlocking and relocking
Yes please
i would say lock and unlock again and just install everything again
baleskoil said:
Yes please
Click to expand...
Click to collapse
So i locked the bootloader ,then unlocked it and did a fresh install of 11 and i have face unlock back
Good .
I need to reflash the Factory image before relocking right ?
To be safe
baleskoil said:
Good .
I need to reflash the Factory image before relocking right ?
To be safe
Click to expand...
Click to collapse
I locked the bootloader then rebooted back into the boot loader and unlocked it and then flashed
Works for me too.
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
neo_lithic3K said:
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
Click to expand...
Click to collapse
I tried that and it's a no go. Looks like bootloader is the way for now.
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
seipersei said:
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
Click to expand...
Click to collapse
I had the exact same problem as you. face unlock became unreliable after the Android 11 upgrade, so I deleted face data and tried to set up again. It keeps saying 'fit face into frame' no matter the angle or the lighting. Did a factory reset and no improvement. I have never rooted or unlocked the bootloader on this phone. I informed google support and they are sending me a replacement.
Just to share an experience with the community: After android 11 update I was having glitches with face unlock. (Totally stock, no root & all latest ota) This got worse until it wouldn't work at all. Deleting face & starting over didn't work as it just refused to even acknowledge trying to register anything. Then the auto brightness starting flicking up and down and finally half the screen disappeared under green flickering. A factory hard reset made no difference. I even did it twice but the welcome screen on rebooting was still covered in green flickering. Searching for a new phone reluctantly. I picked up my pixel 4xl again to see if I could think of a way of selling it for any purpose & it was fine! Set up & reinstalled a backup & everything including face unlock works perfectly like new. What was all that about!?
Can you describe full algorithm for noob, please?
Stiil don`t working
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
I've done relocking bootloader, but it didn`t help, face unlock still not working, OC is stock, latest.
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
kingkong0821 said:
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
Click to expand...
Click to collapse
This is a known problem, and so far Google has not fixed it. Unsure if they ever will.
Sent from my Pixel 4 XL using Tapatalk