Phone blocked on unlock phase. - LeEco Le Pro3 Questions & Answers

Hi,
This last days I have stranges things with my phone, and it is the first time that happened.
When I reboot after install magisk modules or adaway file host, my phone cannot be unlocked.
I type the pin code for unlock my sim card, and after the pin code for unlock the phone.
At this moment I have a black screen and I must retype my code ever and ever.
Nothing to do, just reinstall all the rom. Unable to use a clean backup, this is the same problem.
If anybody knows this issue and can save my life, you're welcome.
Thanks a lot, cordialement

I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?

Lethalben said:
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Click to expand...
Click to collapse
Hello, I am updating my mom's phone and saw your post.
Unfortunately that bug has been around for a few months, I have a quick temporary fix for you but unfortunately the bug will return, if you can live without a screen lock that may be you only solution for now.
Lock Screen ( delete the lock)
Boot to Recovery
Go to Recovery File Manager
Navigate to the /data/system folder
locate and delete the file called : locksettings.db
Now you no longer have a screen lock and you can easily get into the phone.
FYI : If you want the lock again , simply create a new key or pattern
This issue could be anything such as corrupted permissions, It seems that it pops up after installing audio mods and substratum. But I don't think it is caused by either one.
If your phone gets hot while experiencing this issue flash the thermalfix 7 file, located on the thermals thread https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18

This morning I've formated my phone to be sure is not an error from me. I will try your solution if it happens again.
Thanks for your response my friend!

Is it possible f2fs formating data partition is the issue?

Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.

Forsaken75 said:
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Click to expand...
Click to collapse
I'm go back to ext4 and everything is OK.
I saw a magisk module who's made for stop this issue.
If there is a magisk module for that I think the problem is f2fs!

Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
I don't think so because I only use Ext4

Well, I think I finally found the true origin of this problem: Magisk Hide interferes with newer Webview implementations, as explained here:
https://www.didgeridoohan.com/magisk/MagiskIssues#
I also found several workarounds:
1) Disable Magisk Hide. I need some banking apps, so for me this is not an option.
2) Use Chrome Beta and select its engine as default Webview in Developer Options. Chrome Beta signature is not buggy, so it works as it should. This is the solution that I've chosen, by the way.
3) Ask our developers @codeworks @mosimchah and the others if they could include this commit that fixes invalid signatures in their future releases:
https://github.com/LineageOS/android_vendor_cm/commit/a3a76f5d1cc233ad8024ffdc74bb3a786e1605c3

Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.

txiscoman said:
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
Click to expand...
Click to collapse
It's some app compatibility issue with Android Pie/Webview for sure. In my case was my banking app, changing to Chrome beta fixed the problem (app still crashes from time to time, but I'm not having the damned screen lock problem anymore)
You can try using Webview component alone from Play Store (I notice that in my case it's working too) or do some research to find out which app is causing the issue and uninstall it (if you can live without it, of course)

Deleted

Related

[Problem identified] CM 12.1 - Wifi connectivity VS mobile data priority problem

[Solution HERE: disable AFWall+-2.0-alpha2]
Hey there,
I installed the optimized CM12.1 20150602 with Xposed and Xprivacy and now I got a connectivity problem:
When I come back from flight mode or enter a known wifi, wlan0 connects to my local wifi but Internet still gets routed through mobile data (LTE).
ping rounter not possible
Wifi icon has a "!"
netcfg shows:
Code:
rmnet_usb0 UP 10.175.104.107/29 0x00000041
wlan0 UP 192.168.2.126/24 0x00001043
on turning off mobile data, wifi data starts working and keeps working when I turn mobile data back on
I tried with a clean system: no problem, added Xposed/Xprivacy: no problem. So I guess one of my apps with root access must have caused that bug.
Possible candidates: AFWall, AdAway, droid VNC, OpenVPN, OS Monitor, SSHDroid, Tasker, TB.
Anyone knows how to fix this? I guess it must be a problem of how and what gets prioritized.
The setup took me quite some time and it would be great if I could fix this without starting from scratch. Plus I'd like to know the source of the problem.
Log attached.
I run none of the apps you mention and have the same issue and it happens on all wireless networks. I know of two workarounds, if they can be called that.
First is to cycle WiFi from within settings. When I do that it normally works right for a few days after.
Second is to power cycle my wireless router. That normally only works for a day or so as well.
I personally feel this is a flaw in CM as I have also seen the exact same issue on CM and any ROM built from it.
FIX
I found a fix for my problem by trial and error:
First I dirtyflashed the system again which didn't help, so I thought the problem must be in /data... thats where wpa_supplicant.conf is located so I had a look at it and strangest thing was:
The priority numbers for high eventhough it had only three entries. I changed them to 1/2/3 and rebooted. After that automatic connection to wifi worked again. BUT:
I rechecked the
Code:
/data/misc/wifi/wpa_supplicant.conf
again and the priority was back to the old state: 41/47/38 - in this order for the only three networks.
So the fix for me was: Change priority and save. Reboot afterwards.
Can someone elaborate on how this could fix the problem?
Oh and I must revoke my solution. Didn't work on the other network. :/
OK next trial and fail: deleting wpa_supplicant so it gets renewed. No difference.
Maybe I just try to install a fresh install and just restore /data.
I tried deleting the whole /data/misc/wifi folder. Didnt fix it!
And now I even installed from scratch and restored /data only from backup. Didn't help either!
What do I have to remove to fix this???
Rule number 1 of the Optimized ROM: do not use Xposed if you want support. So, uninstall Xposed, make a logcat of your issue if uninstalling Xposed doesn't fix it, then send that to AntaresOne.
He doesn't read the threads in Q&A, and wouldn't reply to this one anyway because of Xposed.
Strephon Alkhalikoi said:
Rule number 1 of the Optimized ROM: do not use Xposed if you want support. So, uninstall Xposed, make a logcat of your issue if uninstalling Xposed doesn't fix it, then send that to AntaresOne.
He doesn't read the threads in Q&A, and wouldn't reply to this one anyway because of Xposed.
Click to expand...
Click to collapse
Yes, thank you, I know that.
I didn't report a bug, I'm just trying to understand the problem, so I won't run into it again.
I tried tried a clean system and a clean system with Xposed and Xprivacy installed and did not have that problem, so I ruled that out.
Lucky for me: I did mention that in my OP.
My point is that you're presenting your information to the wrong audience. You need to post the logcat, without Xposed, on the Optimized CM12.1 thread, if you haven't already done so. That way the people who can actually do something about it can attempt to fix it.
I do apologize however for not reading the thread properly. It was late at night for me and I was half asleep. *sigh*
SOLUTION
So I hope it is fixed now.
My last resort was to flash a new modem/non-hlos.
I was on a 4.4.2 modems (DTM-I9505XXUGNG8_I9505DTMGNG3_I9505XXUGNG8_HOME.tar) before and updated to the latest modems for T-Mobile Germany: DTM-I9505XXUHOD5_I9505DTMHOD1_I9505XXUHOD5_HOME.tar.
This seemed to have solved my Wifi problem.
Step-by-step (no data loss but still: make a backup):
Check which is the latest ROM for your country/carrier on sammobile.com
Download ROM on sammobile.com or samsung-updates.com (no account necessary).
Extract ZIP > rename extracted *.tar.md5 to *.tar > extract modem and non-hlos file from *.tar with WinRAR or the likes.
Shutdown mobile and start into Download mode (Vol-Down)
Run Odin, disable Auto-restart and flash modem and reboot back into Download mode (I did that twice because people were hinting that but I doubt it's necessary).
Flash non-hlos in case you have a S4-LTE version.
Reboot and test.
/edit: didn't fix it.
Solved this time?
I think I finally found the problem: AFWall v2.0-alpha2 seems to cause the connectivity problem.
As soon as I deactivate the Firewall connection won't have any problems. I can't believe I needed so much time to find the bad boy.
Guess I didn't want to reduce security on my system, so I tried to avoid disabling/deleting my firewall.

Issue with Wifi on Yoga Tablet 2-1050F : quick setting flicker and reboot

Hi,
Since some weeks i have issues with my Wifi connection :
It stops working and the "Wifi" quick setting button flicker. I can't disable and/or enable it. The only thing i found to resolve the issue is to reboot the tablet, then it works for some times.
I have Android 5.0.1 (last update).
Do you know this issue ? If yes, how to resolve it ?
I made a video of the issue :
https://youtu.be/ylyMgieQktM
Thanks
Can you find wifi in settings/apps and clear cache or data and see if that works.
Don't have me tab on me so can't test.
If that doesn't work boot to custom recovery and clear cache and dalvic cahe
Sent from my SM-G901F using Tapatalk
Hi,
Can you find wifi in settings/apps and clear cache or data and see if that works.
Click to expand...
Click to collapse
I don't have "Wifi" in settings\apps.
If that doesn't work boot to custom recovery and clear cache and dalvic cahe
Click to expand...
Click to collapse
I don't have custom recovery. I have stock rom and so stock recovery. Can i clear cache and dalvik cache in stock recovery ? If yes, do you know how to boot to stock recovery ?
Thanks
I have the same problem with my Yoga Tablet 2 - 1050F.
Any solutions?
nonobio said:
Hi,
Since some weeks i have issues with my Wifi connection :
It stops working and the "Wifi" quick setting button flicker. I can't disable and/or enable it. The only thing i found to resolve the issue is to reboot the tablet, then it works for some times.
I have Android 5.0.1 (last update).
Do you know this issue ? If yes, how to resolve it ?
I made a video of the issue :
Thanks
Click to expand...
Click to collapse
Do you have root? In which case you could do a dmesg or logcat output to skim the logfiles for any error messages that could pinpoint the issue.
Hi,
I don't have solution
These is others topics about this issue :
https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Issue-with-Wifi-flickering-on-my-Yoga-tab-2-1050-F/td-p/3269564/highlight/false/page/2
https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Tab-2-1050F-tablet-reboot-caused-by-WiFi/td-p/3275391
Hi,
I contacted my reseller (Amazon) and it tell me to restore to factory default my tablet, what i did, with internal sd card format.
After the reset, i don't have the issue anymore, but i didn't connected my Google account and didn't installed my own apps : tablet is in a fresh stateand since yesterday : no issue.
Now, i think i will install my apps one after the other to try to determine if one app could be the cause.
For help my diagnoze, could you list all your installed apps to see if we have some commons ? you can use this app :
https://play.google.com/store/apps/details?id=com.projectsexception.myapplist
These are apps i had on my user session :
3D Bones and Organs_3.0.0.apk
ABC Anglais_3.5.apk
Agenda_5.3.3-113058720-release.apk
Amazon_5.51.6210.apk
Amazon_5.9.0.200.apk
Android System WebView_48.0.2564.106.apk
Androidify_4.2.apk
App-Shop_release-20.0000.912.1C_650000010.apk
Appli*Google_5.8.58.19.x86.apk
AppMgr III_3.86.apk
Banque_3.5.apk
Beauty Salon_1.5.apk
Candy Crush Jelly_1.9.1.apk
Chordbot Lite_2.15.apk
Chrome_48.0.2564.95.apk
Chromecast_1.13.15.apk
CineTrailer_3.1.11.apk
Clavier SwiftKey_6.2.1.151.apk
CoursdeGratte_1.4.apk
Docs_1.6.052.12.73.apk
Drive_2.3.544.17.73.apk
Earth_8.0.2.2334.apk
Ensemble Composer_1.2.9.apk
ES Explorateur de Fichiers_4.0.4.4.apk
Evernote_7.6.apk
feedly_31.1.0.apk
Firefox_44.0.2.apk
Gmail_5.11.115007468.release.apk
Google Play*Musique_6.4.2415W.2615976.apk
Google+_7.2.0.114390191.apk
Google*Cloud*Print_1.33b.apk
Google*Play*Films*et*séries_3.11.5.apk
Google*Play*Jeux_3.6.25 (2616091-070).apk
Google*Play*Livres_3.7.75.apk
Google*Play*Store_6.0.5.apk
Guide de l’utilisateur_1.5.5_20150527.apk
Guitar chords and tabs PRO_2.2.9.apk
GuitarTuna_3.5.2.apk
Hangouts_7.0.113317058.apk
HERE Maps_1.1.10114.apk
iPrint&Scan_2.1.1.1.apk
KeepScore_1.5.1.apk
Kodi_16.0.apk
LastPass_4.0.14.apk
LeclercDrive_6.1.8.apk
Leo's Fortune_1.0.4.apk
Link2SD Plus (New)_1.1.apk
Link2SD_4.0.12.apk
MAPS.ME_5.6.2-Google.apk
Maps_9.20.1.apk
Maître du Rythme_4.2.1.apk
MediaMonkey Pro_1.1.0008.apk
MediaMonkey_1.1.3.0554.apk
MMRemote_v2.7.apk
Monument Valley_2.4.22.apk
Movie Mate_5.9.1.apk
MSQRD_1.0.3.apk
Music Composition_1.2.apk
My Incredible Body_3.0.09.apk
My*Maps_2.0.apk
NotesDeMusique_3.11.apk
Notifly_1.0.2.apk
Nova Launcher Prime_D.apk
Nova Launcher_4.2.2.apk
park4night_4.0.1.apk
Plex_4.21.0.528.apk
Pocket_6.2.1.0.apk
Pushbullet_17.6.5.apk
QuickPic_4.6.9.1426.apk
QuickSupport Add-On Lenovo_10.0.3086.apk
QuickSupport_11.0.4555.apk
Rayman Fiesta Run_1.2.8.apk
SensCritique_1.0.2.9.apk
SeriesGuide_28.apk
Service du périphérique_V4.3.1.1021tri.apk
Services Google*Play_8.4.89 (2428711-270).apk
Sheets_1.6.052.07.73.apk
Skitch_2.8.5.apk
SolfaRead_1.01.apk
Soundcorset accordeur et métronome_2.89.apk
SoundHound_6.9.3.apk
Spotify_4.7.0.878.apk
SyncMe_2.08.8931.apk
Synthèse vocale Google_3.8.14.apk
Tabs_4.3.5.apk
TalkBack_4.4.1.apk
TeamViewer_11.0.4376.apk
TeslaUnread_4.0.1.apk
Timote_1.13.0.apk
Toca Builders_1.0.8.apk
Toca City_1.0.4-play.apk
Traduction_4.4.0.RC01.104701208.apk
TripAdvisor_14.4.1.apk
Unified Remote_3.4.0.apk
Virtual Makeover_2.9.apk
VLC_1.7.5.apk
Wifi Analyzer_3.9.9-L.apk
Wunderlist_3.4.4.apk
Yatse Queue Plugin_1.2.0.apk
Yatse Stream Plugin_2.3.0.apk
Yatse Widget Unlocker_2.1.0.apk
Yatse_5.9.7.apk
Yousician_1.6.1.apk
YouTube_11.04.56.apk
Do you have some common app ?
Maybe we can compare others things like :
Are you rooted ? i'm not.
Do you have apps disabled ? I had some system apps disabled.
What is your firmware version ? Mine is YT2-1050F_USR_S100256_1601190545_WW52_ROW
Do you have several user on your tablet ? I had 2 differents users sessions.
Thanks
I take a quick research about this problem, an found some users at the official Lenovo forum saying that this is a "general" issue with Lillipop. I also used Android 5.0.1 when I had this problem. I never had this problem in the year before I upgraded to LP. Also I downgraded to Kitkat 4.4.2 two days ago and till now no problem with Wifi! Hope this solved the wifi-issue.
Ok but i would like stay on LP.. During the first month with LP i didn't have any issue.
Could you just tell me if you had common apps installed by checking my list ?
thanks
I have this issue as well. I dont have root but I did do a lazy attempt at rooting a while back using kingroot so I have su binaries, checked with adb, but no root so I can't remove them. OTA updates have worked up till now even with su binaries in place, but the last one from march fails before the end but the tablet will boot.
makromedia said:
I have the same problem with my Yoga Tablet 2 - 1050F.
Any solutions?
Click to expand...
Click to collapse
makromedia said:
I take a quick research about this problem, an found some users at the official Lenovo forum saying that this is a "general" issue with Lillipop. I also used Android 5.0.1 when I had this problem. I never had this problem in the year before I upgraded to LP. Also I downgraded to Kitkat 4.4.2 two days ago and till now no problem with Wifi! Hope this solved the wifi-issue.
Click to expand...
Click to collapse
Hi, does it always work for you ? I made a factory reset, it worked first days but then the issue is back
I discovered the reason.
If you save your apps to SD card, then WiFi stop work.
If you save apps to internal memory, then everything is alright.
It works on my yoga 1050f.
nonobio said:
Hi,
Since some weeks i have issues with my Wifi connection :
It stops working and the "Wifi" quick setting button flicker. I can't disable and/or enable it. The only thing i found to resolve the issue is to reboot the tablet, then it works for some times.
I have Android 5.0.1 (last update).
Do you know this issue ? If yes, how to resolve it ?
I made a video of the issue :
https://youtu.be/ylyMgieQktM
Thanks
Click to expand...
Click to collapse
Something similar happend to me when i switched the default isntallation location for apks to force istall to SD card. Wifi flickered after reboots so i switched it back to system default.
Hope this helps.
**Damn, sorry for the now useless post, my mistake!
ponczo said:
I discovered the reason.
If you save your apps to SD card, then WiFi stop work.
If you save apps to internal memory, then everything is alright.
It works on my yoga 1050f.
Click to expand...
Click to collapse
ericsyabi said:
Something similar happend to me when i switched the default isntallation location for apks to force istall to SD card. Wifi flickered after reboots so i switched it back to system default.
Hope this helps.
**Damn, sorry for the now useless post, my mistake!
Click to expand...
Click to collapse
Hi,
Since my last factory reset, i had the issue only 2 or 3 times but nothing important.
Thanks for this tip, i will check this if the issue come back.

[TWRP] 3.1.1-0 Encrypted device - Password fails but PIN works

I'm using the official version of TWRP flashed to my device.
If I set the device encryption with a password then TWRP is unable to mount the encrypted file system - It fails with 'Incorrect Password'
If I change to use a PIN then TWRP successfully mounts and decrypts the file system.
Is this a known issue, or is there any work round to enable to use of a password rather than a PIN?
Anyone?
iam-q said:
I'm using the official version of TWRP flashed to my device.
If I set the device encryption with a password then TWRP is unable to mount the encrypted file system - It fails with 'Incorrect Password'
If I change to use a PIN then TWRP successfully mounts and decrypts the file system.
Is this a known issue, or is there any work round to enable to use of a password rather than a PIN?
Click to expand...
Click to collapse
iam-q said:
Anyone?
Click to expand...
Click to collapse
Known TWRP issue across multiple device types. Google is your friend.
Alas google hints at a problem with some versions and some phones - there is no actual word from the developer(s) and if you care to check the github site you will find a mass of bugs raised with no replies and missing information. Most of the issues others have raised relate to nothing working at all or patten unlock not working.
iam-q said:
Alas google hints at a problem with some versions and some phones - there is no actual word from the developer(s) and if you care to check the github site you will find a mass of bugs raised with no replies and missing information. Most of the issues others have raised relate to nothing working at all or patten unlock not working.
Click to expand...
Click to collapse
Yes - given the number if independent reports it is reasonable to suspect there is an issue that either can not be replicated or is noting addressed

Is there a way to fix the fingerprint after reboot issue?

I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Thebluemace said:
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Click to expand...
Click to collapse
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
tsongming said:
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
Click to expand...
Click to collapse
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Thebluemace said:
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Click to expand...
Click to collapse
Its a bug, with the current version of the msm8996Pro base, which all Roms use
The developers are aware of the bug and it will be fixed on the next build. For now you can row back to an earlier rom that didn't have that issue or wait for the next build of the Rom you are using.

Faceunlock not working "Certificate has expired" error

Hi, I bought a used Pixel 4, and when I tried to configure faceunlock I got a "Certificate has expired" error. To resolve the error, I tried to flash all versions of Android Os available for this device, including Beta 11. Can anyone know the solution to my problem?
I have the same problem. Anyone can help?
delete the face and add again
just don't use the face unlock for now, taking off your mask to unlock is not practical anyway.
I have the same error now. Any help?
abeninski said:
I have the same error now. Any help?
Click to expand...
Click to collapse
Hi there! Just wanna share some useful information about how to fix Face Unlock error on Pixel 4. Someday i noticed that Facecontrol just throw you an exception, like "face enrollment error" etc. And I also tried everything: hard reset, to flash an old android 10-11 builds - nothing helps. Then i started experimenting. So you need to uninstall updates from several Gaps (First 6 on screenshot): carrier services, motion sense bridge, adaptive connectivity service, device personalisation and device gealth service. Better to remove it one by one cheking Facecontrol become alive after every uninstallation. Not sure how these apps works, but removing patches from them solved this problem, at least in my personal case. The main thing is that your current OS build don't matter, for example my brother got this issue on android 10. If it'll cure your Pixel, make a backup of working build. Hope this post will be helpful

Categories

Resources