When I set password or PIN code, lock screen still unlocks by swiping and when I want to set new code it asks old one and when I enter old it says wrong code.
Ayano_+ said:
When I set password or PIN code, lock screen still unlocks by swiping and when I want to set new code it asks old one and when I enter old it says wrong code.
Click to expand...
Click to collapse
I have same problem, can't set face recognition, iris or fingerprint. Flashed new rom, restored stuff, can't set biometrics, reflashed without restoring system settings, only contacts and few apps, set new password, later when trying to set up fingerprints, it keep asking for password, and then tells me password is wrong.
opiumdance said:
I have same problem, can't set face recognition, iris or fingerprint. Flashed new rom, restored stuff, can't set biometrics, reflashed without restoring system settings, only contacts and few apps, set new password, later when trying to set up fingerprints, it keep asking for password, and then tells me password is wrong.
Click to expand...
Click to collapse
Hope, someone will find fix or maybe new security patch will help. When did your problem start? After what?
Fix
I fixed this issue.
1. Go to TWRP
2. Mount EFS
3. Go to advanced
3. Open file manager
4. Go to efs folder
5. Then to TEE folder
6. And delete all files from TEE folder
7. Restart
P.S. I am not sure if it will help everyone
Thanks!! You just saved my day.
I'm using s9+ with Andriod 10
Ayano_+ said:
I fixed this issue.
1. Go to TWRP
2. Mount EFS
3. Go to advanced
3. Open file manager
4. Go to efs folder
5. Then to TEE folder
6. And delete all files from TEE folder
7. Restart
P.S. I am not sure if it will help everyone
Click to expand...
Click to collapse
Nice
Deleted member 9896136 said:
Fix
I fixed this issue.
1. Go to TWRP
2. Mount EFS
3. Go to advanced
3. Open file manager
4. Go to efs folder
5. Then to TEE folder
6. And delete all files from TEE folder
7. Restart
P.S. I am not sure if it will help everyone
Click to expand...
Click to collapse
bro thank you so much you saved my day appreciate it.
Related
While playing (a bit too much), I must have deleted the password setup icon/file from settings and cannot change or disable the password screen. Anyone knows what the file name is and can post it here or email me the file. I know the password and can get in but I really don't need it and would like to disable it.
The shortcut is exactly like this:
"ctlpnl.exe cplmain.cpl,1"
>> without "" quotes
ezzkht said:
The shortcut is exactly like this:
"ctlpnl.exe cplmain.cpl,1"
>> without "" quotes
Click to expand...
Click to collapse
Thanks ezzkht, but how do I create the shortcut?
Try to copy any shortcut from \windows\start menu\programs\
and paste it to the location you want, rename it & edit it using Total Commander (right-click on it & choose Properties, then go to Shortcut tab and change the TARGET parameter to "ctlpnl.exe cplmain.cpl,1" without quotes.
The icon will automatically change to the password icon
ezzkht said:
Try to copy any shortcut from \windows\start menu\programs\
and paste it to the location you want, rename it & edit it using Total Commander (right-click on it & choose Properties, then go to Shortcut tab and change the TARGET parameter to "ctlpnl.exe cplmain.cpl,1" without quotes.
The icon will automatically change to the password icon
Click to expand...
Click to collapse
Sorry ezzkht, I did exactly what you said but it did not work. Tried with and without quotes, tried 0 instead of 1 but the icon never changes to the password icon just an executable icon but nothing happens when I click on it.
OH yes you are right!! sorry!
Ok here's the shortcut, I just get it from my device..
I opened it with a HEX editor & found the following line inside it:
51#ctlpnl.exe cplmain.cpl,1?\Windows\cplmain.cpl,-6000
plz tell me if it worked with you
Hi ezzkht, I tried but this also does not seem to work.
I checked the registery and their is a mention of a Password.cpl in the Windows directory which is not in mine. I installed logologin and picturepassword and have recently removed them, don't know if they might have also removed this file. It may be the the problem, do you have this file.
Neither me, I don't have password.cpl file in \windows directory!!
I have cplmain.cpl only!
I noticed that the password link points to cplmain.cpl with a parameter of : password.cpl
I guess that cplmain.cpl is a composite file which contains alot of programs, one of them is the password program!
Do u have the cplmain.cpl in windows directory??
check this out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppc2k/html/ppc_tcuts2.asp
ezzkht said:
check this out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppc2k/html/ppc_tcuts2.asp
Click to expand...
Click to collapse
Thanks ezzkht, this was good but it still did'nt work. I think somewhere their is a file missing. I will try emailing MS and see if they have an answer.
You welcome, but I did nothing!!
A hard reset could help, unless you are not willing to install your programs all over again!
ezzkht said:
You welcome, but I did nothing!!
A hard reset could help, unless you are not willing to install your programs all over again!
Click to expand...
Click to collapse
You got that right, finally got all the programs and the look I want. I am going to do a backup via Activsync and a clone backup tonight at home then if all else fails I will do a HR, copy any missing files from the windows directory and reinstall my backups.
Seems a great idea :wink:
Compare the two WINDOWS directories, and copy only the missing files..
Good luck dude
And any tips to what change in it?
FelipeRRM said:
And any tips to what change in it?
Click to expand...
Click to collapse
Use root explorer. Go to /system and press and hold the build.prop file and then select open in text editor. Make sure you mount r/w in root explorer.
Thanks, and there it goes more money on Android Market =[
Edit: If I wanna add anything just add it to the end, save and reboot? This thing does need a search function to see if the line's already in there somewhere. Does it harm to add a line in the end if it is already there somewhere, working like botton lines overriding the top ones?
Any suggestions to add? And what's dalvik heapsize, head some talk about it.
would strongly suggest that you read and learn before making any changes.
FelipeRRM said:
Thanks, and there it goes more money on Android Market =[
Edit: If I wanna add anything just add it to the end, save and reboot? This thing does need a search function to see if the line's already in there somewhere. Does it harm to add a line in the end if it is already there somewhere, working like botton lines overriding the top ones?
Any suggestions to add? And what's dalvik heapsize, head some talk about it.
Click to expand...
Click to collapse
2nd post http://forum.xda-developers.com/showthread.php?p=10536952#post10536952
rendeiro2005 said:
2nd post http://forum.xda-developers.com/showthread.php?p=10536952#post10536952
Click to expand...
Click to collapse
Thanks, but I tried setting the dalvik to 12, as I use only light apps, to see if it would perfom any better (as you said it could be from 12 to 40), and the phone entered an endless loop from boot screen to "Sony Ericsson" screen. Had to re-flash, thankfuly xRecovery still worked and I had a zip in the SD card.
FelipeRRM said:
Thanks, but I tried setting the dalvik to 12, as I use only light apps, to see if it would perfom any better (as you said it could be from 12 to 40), and the phone entered an endless loop from boot screen to "Sony Ericsson" screen. Had to re-flash, thankfuly xRecovery still worked and I had a zip in the SD card.
Click to expand...
Click to collapse
that happen because you didn`t use the right permissions.
from what you`ve described i presume you edit build.prop and then copy paste to system, right?
do this:
enter on system folder, press and hold build.prop file select permitions and then check all. Now copy your new file to system and repeat the proccess (check all permitions).
reboot.
No, I had already changed it from 24 to 28 before, without errors, the only thing I did different in the first time was to "mount r/w". Maybe that's what happened lol.
Edit: Tried again, now mounting the r/w thing, like I did in the first time, but still got the boot loop.
I didn't change the permsions, I'm doing it directly through Root Explorer. click and hold, open in text editor.
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
A quick question. How does one disable the CD ROM pop-up that appears when connecting the phone? I tried using the same code as on the original Incredible (##7764726), and while it does take me to the same feature editor and I can select CD ROM option and do "disable", it reverts to "enabled" immediately.
Thanks in advance!
PS If anyone knows how to move apps onto an external SD Card?
Boris1M said:
A quick question. How does one disable the CD ROM pop-up that appears when connecting the phone? I tried using the same code as on the original Incredible (##7764726), and while it does take me to the same feature editor and I can select CD ROM option and do "disable", it reverts to "enabled" immediately.
Thanks in advance!
PS If anyone knows how to move apps onto an external SD Card?
Click to expand...
Click to collapse
you ll need root and access to /system/
nitsuj17 said:
you ll need root and access to /system/
Click to expand...
Click to collapse
I do have that. Would you happen to have instructions how to get rid of it?
Thanks!
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
*Madmoose* said:
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
Click to expand...
Click to collapse
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
ceayuso said:
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
Click to expand...
Click to collapse
hmmm ##PROGRAM# does nothing for me.
The ##PROGRAM## worked for me and gave me the menu, but no matter how many times i set the cdrom to disabled it never changes, just remains enabled.
Void4ever
ceayuso said:
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
Click to expand...
Click to collapse
I'm with void4ever. Dialing the ## code was the first thing I did, just like on old Inc. I see the menu, but the change to CD ROM setting does not stick. It reverts to Enabled as soon as I hit OK on the selector...
you go to system/etc/ and remove (or re-name to .bak) CDROM.ISO
*Madmoose* said:
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
Click to expand...
Click to collapse
Thanks! That worked. Not quite the way I like to make config changes, but as long as it works.
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Does OK GOOGLE works everytime?
sushant20 said:
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Click to expand...
Click to collapse
Does your camera work? I tried an other method and it messed up my camera, because it only saved a green picture.
Akilesh Akil said:
Does OK GOOGLE works everytime?
Click to expand...
Click to collapse
yes it does!
trapistasajt said:
Does your camera work? I tried an other method and it messed up my camera, because it only saved a green picture.
Click to expand...
Click to collapse
I am using FireHound 7.0 and nothing seems broken to me because of Google Assistant!
Beware if you're on AICP, this locked up my phone, had to restore my backup again. If you're on AICP, just use the other Google Assistant thread and add the entries to build.prop yourself.
I've tried flashing these two files on 3 different ROMs with pico gapps--- Official RR 6.0.1, Graraks CM14, Firehound OS 7.0 but every time, the phone gets struck at 1+ bootlogo. I don't know what's going wrong. Please help.
1 more thing, while flashing the 2nd zip, some Error 1 appears in twrp.
Edit: its working good. I just didn't downloaded that tweak.prop. Now it works flawlessly!
Thanks!✌
Does it work on marshmallow ROMs?
amitgudwill said:
Does it work on marshmallow ROMs?
Click to expand...
Click to collapse
do you even read the requirements?
Just my two cents: there's no need to do any of that really to get Google assistant to work on Android N builds.
Just make sure that you have the latest version of the Google search app, then add these two lines to your build.prop file and reboot. After that, just clear Google search's data and then open the assistant using the same shortcut that you've used to open now on tap before(long press home by default), when asked about setting up "ok Google" select "I'll do it later"(to avoid crashes).
That's it
sar12330 said:
Just my two cents: there's no need to do any of that really to get Google assistant to work on Android N builds.
Just make sure that you have the latest version of the Google search app, then add these two lines to your build.prop file and reboot. After that, just clear Google search's data and then open the assistant using the same shortcut that you've used to open now on tap before(long press home by default), when asked about setting up "ok Google" select "I'll do it later"(to avoid crashes).
That's it
Click to expand...
Click to collapse
can u please explain which two lines to add? There is just one single line which is to be added in the build.prop.
The lines are:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
After putting these in the build.prop and rebooting, clear Google search's data and the assistant should work
not working on Halogen OS 7.0
Just wanted to comment on the OP.
Adding the two lines works. No need to flash anything or delete any lines. It works just as on any other device.
At least on CM14/.1
Tried to activate assistant by put these two lines into build.prop... Seems to be OK but every time I finish voice recognition setup for "OK Google" and want to try it, it starts the setup again...
Any solution?
well can anyone try to help me ?
Resolved
vergilbt said:
Tried to activate assistant by put these two lines into build.prop... Seems to be OK but every time I finish voice recognition setup for "OK Google" and want to try it, it starts the setup again...
Any solution?
Click to expand...
Click to collapse
It's normal, voice recognition isn't working with this method.
@casual_kikoo
Thanks a lot for your information... Could you point me to the right way? The way from op?
vergilbt said:
@casual_kikoo
Thanks a lot for your information... Could you point me to the right way? The way from op?
Click to expand...
Click to collapse
In fact, no way for now.
sushant20 said:
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Click to expand...
Click to collapse
The build.prop uses UNIX endlines. Does es even support those?