Hello ppl, ihave this problem as per topic and the only way to enter is to disable pattern / fp in oos 10 beta 3 rom.
I am on twrp 70 build.
try to use this. Use the numbers for your pattern
1 2 3
4 5 6
7 8 9
Hmm 1234 doesn't work. I meant as per my pattern
Related
Hi, sry in advance for my bad english - i hope u understand my problem..
I "played" around with my device: Diamond 2, with mobile 6.5 [original ROM]
now i have a problem:
I entered: Settings - more - "device lock"
there you can enter a password, so you have to enter a numeric password, everytime you wake up the device. This works just fine.
BUT - how do I deacitvate this? Because, when I try to re-enter: Settings - more - "device Lock", it asks me to tipe the password but it doesn't happens anything. And there is no "ok" button - just a <- and a X
so what can I do, or what should I do?
I really don't want to hard resett my device
mfg Vashi
nobody?
after very long google-session's i found out, that normally you should have an "unlock" button, if you re-enter settings/device lock
this "unlock" button is missing @ my device - i can only type in 1 2 3 4 5 6 7 8 9 0 and X or <-
guys - need you ^^
I am going to trade my iPhone4s (At&T) for a Htc one s (Tmobile) Ive read that everything should work including 3g What exactly will I have to do to get this to work ? ( I am on AT&T Network)
http://forum.xda-developers.com/showthread.php?t=1734541
Sent from my HTC VLE_U using Tapatalk 2
rumdada said:
I am going to trade my iPhone4s (At&T) for a Htc one s (Tmobile) Ive read that everything should work including 3g What exactly will I have to do to get this to work ? ( I am on AT&T Network)
Click to expand...
Click to collapse
Welcome to freedom!
Sent from my HTC One S using Xparent Cyan Tapatalk 2
LikeaG2root said:
Welcome to freedom!
Sent from my HTC One S using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
lol I concur...
..... -_- glacierguy I think you posted the wrong link keeps taking me back here
Heres proper one: http://forum.xda-developers.com/showthread.php?t=1693491
Just follow instructions pop in the sim card enter unlock number and go!!! Good Luck and Good Choice! (actually since SGS III is out I may upgrade just had this for 1 week too )
To make the instructions simple: (I take no credit for this)
To find your SIM UNLOCK CODE you need:
1) Root
2) Android Terminal Emulator (free from the market)
3) Your IMEI number (dial *#06# on your dialler)
There are 4 steps to the process:
1) Obtain your UN_lock_code from your phone
2) Calculate the key from your IMEI number
3) Subtract (2) from (1)
4) Unlock your phone
Step 1
Obtain your UN_lock_code from your phone as follows:
Open the Terminal Emulator app and type:
su [enter]
strings -n 8 /dev/block/mmcblk0p6 [enter]
It will output several lines of data (including your IMEI number)
One of the lines will be [eg] UN_Lock_code=063312345
Make a note of this number (This is NOT your SIM unlock code)!
Step 2
Make a key from your IMEI number:
a) Write down the last 7 digits of your IMEI number in this format: 1234 567
b) Reverse the 2 blocks: 567 1234
c) Add a 4th digit X: 567 X 1234 where:
X = the sum of the first 3 digits (If the sum is 2 digits, write only the 2nd digit)
[5 + 6 + 7 = 18 in the example above so X = 8]
[if the sum is 3, X = 3]
[if the sum is 17, X = 7]
[if the sum is 25, X = 5] etc.
Using the above IMEI number we get:
567 8 1234 (= the key)
Step 3
Perform a simple sum.
UN_Lock_code [step 1] – key [step 2] = SIM UNLOCK CODE
e.g. 063312345 - 56781234 = 6 531 111
This needs to be an 8-digit number, so add a zero at the beginning if necessary
YOUR SIM UNLOCK CODE IS: 0653 1111
Step 4
Unlock your phone
a) Remove your SIM card (no need to turn off the phone)
b) Insert alternate SIM card
c) When prompted, enter SIM UNLOCK CODE obtained from step 3
d) Reboot when instructed
Hey guys,
A few days ago I encrypted my device running the latest Exodus 5.1 with standard kernel. The first few boot ups I had to draw a pattern for boot (in TWRP as well). Now, after a week or so, it doesn't ask me for my pattern anymore. Not on normal system boot, neither in TWRP. But in settings it still tells me encryption is enabled.
Wth? What am I doing wrong?
Cheers
Settings -> lockscreen -> screen lock -> tap on pin / password / pattern (whatever you have set up) -> next screen you can choose if pin/password/pattern should be prompted for at device boot.
Oh, I see. Stupid me. Actually it's good that this is disabled because TWRP unfortunately does not support my 4x4 pattern (any workarounds got this btw?).
But with this option disabled, is the encryption still useful? Probably not right? So if someone steals my shutdown device he can simply access data through TWRP or booting it up, right? Encryption would be useless in this case?
Twrp does support pattern unlock for decrypt since version 2.8.6.0. If your pattern is to swipe the first row from left to right, this would be password "1 2 3" (just like you are swiping over a dialpad).
If you want to secure your data, then you must use a pin/password/pattern lock. If you don't use it, there is no real benefit using encryption.
Yes, TWRP supports 3x3 patterns, but not my 4x4 pattern. So is there any possibility unlocking your pattern via code then? Would it be like this then:
1 2 3 4
5 6 7 8
9 10 11 12
13 14 15 16
And where do I type the code then?
I use a 4x4 pattern lock. I just don't use the option that it has to be entered before boot (after unlocking the SIM card you have to unlock via pattern).
Sorry I misread. Twrp still can only decrypt 3x3 patterns. If your pin/password/pattern is not prompted for at device boot, someone could still access your data through twrp (and e.g. copy it to usb-otg).
Okay thanks. Then I'll hope TWRP is going to be able to decrypt 4x4 soon, so I can enable the boot decrypt. I don't want to go back to 3x3 neither get locked out of my system if I need TWRP to restore, update or whatever.
I have been trying to enable camera 2 api on redmi 5 running miui 11 oreo.
i have already edited build.prop by adding line persist camera.HAL3.enabled=1 and
persist camera.vendor.HAL3.enabled=1
i can see these lines when i pull build.prop using adb i have tried putting both of the lines and single line one by one but nothing worked please help me..
Hi everyone,
I've had the nasty surprise of my pattern not being recognized a few days ago. Might be a memory corruption (bit flip from cosmic rays ) or just a very rare bug. Either way, I've won the lottery, because this hasn't happened in 4 years ...
My aim is to unlock the phone without losing internal storage data.
Fortunately, the fingerprint unlock still worked for three days, so I've:
- enabled USB debugging and approved my PC
- backed-up to SD card with Samsung's Smart Switch and did a backup via USB with adb backup (not sure how safe that is)
Currently the fingerprint doesn't work anymore, it forces me to unlock with the pattern. Haven't restarted yet to see if my original pattern will be restored, out of fear that ADB won't work anymore or the backup I did wasn't good enough and I've lost my chance to do a good backup. I'm waiting for my brute-force to finish (more on that below) and some replies from you guys .
My phone is:
Galaxy S8 (Android 9 - firmware G950FXXS5DSJ1 build date Sep 30 2019)
not rooted
My main question is, does this command silently fail after a number of attempts?
adb.exe shell locksettings verify --old xxxxxxx
I've written a script that loads the pattern combinations from file (kudos to delight.im for sharing the list) and saves the command output to file. I've tested it on Android 10 (updated nov 2020) and it throttles after 4 requests - command output is "Request throttled". On my locked phone (Android 9) it appears to never throttle, the output is always "Old password 'xxxxxxx' didn't match".
Found this comment of alecxs on StackOverflow where he says:
there is a 30 seconds timeout after x attempts (timeout may increase) and twrp will silently fail during this waiting period (even with the right pin) - it can even wipe your data (depends on gatekeeper settings and device).
Click to expand...
Click to collapse
Does this apply also to the locksettings verify command?
Can I view the "gatekeeper" settings somewhere?
If you've got any other suggestion on how to unlock the phone or do a better backup before factory reset, please feel free to write!
Thanks a lot!