wondering if there is a workaround for this,my tablet has given me no issues,up till now...this morning it was asking for a backup password(which i cant remember) i normally use pin or fingerprint for security...any help..kinda vexing
Did you setup a Samsung account? This worked for a coworker with a S5 - fingerprint scanner went wonky and she forgot her backup password as well.
Try doing this:
View attachment 3712498
Source: http://trendblog.net/how-to-bypass-android-phone-lock-screen-pattern-pin-password/
so im not the only one, this happened to me as well, no finger scanning option only backup password (which I cant remember)
what I did is delete 2 files using TWRP file manager under data/system password.key and gesture.key.
reboot your phone and you'll end up with a swipe to unlock
go to settings and change your backup password (will prompt fingerprint) . you may activate your lockscreen with fingerprint again, it may ask you for the backup password but this time, you already know what it is and once you put it in, everythign should be back to normal
let me know if you have question
---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ----------
--
additional: the steps above is assuming that you got locked out and cant get past through your lockscreen.
Last night i changed screen lock password and now i am stuck as i forgot the password.
I have tried following solutions that i found on google.
1. Android lock screen can be bypassed by overloading with massive password ( Failed as my android is patched, not able to copy from dial screen ).
2. ADB can not be used as developer mode is disabled.
3. Google Android device manager has failed to ring or change the screen lock password as internet is off and there is no way to turn on WI-Fi or Data on lollipop when screen is locked.
Do i have any option other than Wipe Data/ Factory Reset. :fingers-crossed:
I downloaded and installed official LineageOS to my Galaxy Note 10.1 (2014 Edition) P-605 from
https://download.lineageos.org/lt03lte
Install TWRP Recovery
Install latest downloaded file from the link given above
Install open gapps (mini)
Everything working fine except
Usb MTP connection is not working
On boot Setting app closes
Less battry life than the stock rom
MTP connection issue is a huge problem for me. Do anyone know a fix? I searched everywhere and couldn't find anything
I confirm all the above issues with the nightly build 2018-02-22.
Let me add another (serious) one: if you encrypt the storage, every time you reboot a bunch of applications go in restart loop, until eventually the device restart. This is basically a bootloop. I will try to wipe cache and dalvik and restart to see if the problem persists.
I'm not used to rant just for the sake of, also considered the amazing work devs do, but this time I'm a bit pissed. I bought this tablet specifically because it is listed in the "Lineage OS supported devices" list. It would be nice to put a big disclaimer if the current build has so many crippling issues.
---------- Post added at 10:39 AM ---------- Previous post was at 10:16 AM ----------
That's annoying... TWRP does not manage to decrypt the storage partition... So I'm pretty much screwed.
I will try to format the storage to remove the encryption, and then re-install the latest Lineage nightly using either adb sideload or a micro-USB pendrive.
OK, kind of works. I started TWRP recovery and formatted all the device (removing encryption), then copied back the lineageOS (I used the last nightly, 2018-02-22) and addonsu zip files using a microUSB stick. Reinstalled everything. It works, the only annoying thing is that by formatting the sdcard I lost the backup I had previously done with TWRP of the original firmware, but that's fine, I was not planning of using it anyway.
- enabled USB debugging, root apps+ADB, enable third-party apps
- added F-Droid repo
- downloaded CryptFS from F-Droid
- Settings -> Security -> set up a temporary password for screen unlock
- Plugged in tablet, Settings -> Security -> encrypt device (using the temporary password above)
- reboot, this time seems to work (modulo the usual annoying "settings app has stopped working" one-time popup)
- changed encryption password with CryptFS (requires root of course)
- Settings -> Security -> changed screen unlock to a normal PIN
Everything seems to work so far: the device asks for the long decryption password at boot but only short PIN to unlock screen.
Planning to install WrongPINshutdown now, to complete anti-theft security setup.
So far so good, except ADB still doesn't work. Keeping a close eye on battery usage.
Coming next:
- testing whether TWRP can decrypt storage
- making sure at least LineageOS can mount USB drives... since MTP doesn't work it would be annoying having to use network or ADB to transfer large files...
---------- Post added at 01:17 PM ---------- Previous post was at 12:59 PM ----------
Babality!
- TWRP still cannot decrypt storage, does not even ask for the passphrase, just does not see the partition
- after trying the above, somehow the encrypted partition header got screwed: if I start Lineage OS, when I'm prompted for the passphrase. I always got "wrong password". Either using the "right" password, or using the old temporary password I used before, or the current device PIN, nothing: everything is "wrong password".
I'm reinstalling everything again and do a couple of final tests before giving up and forgetting about encryption.
I suspect this might be an issue of TWRP. I'm using version 3.0.2-0. I'm installing now the latest version (3.1.1-0) and see if things change.
Also, coming next MTP test.
---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------
TWRP 3.1.1-0 bootloops tablet... I have to start from Odin again.
F**k all this s**t, my next device's gonna be an Apple :angryface:
I managed to make the double-encryption work: now when I boot the tablet it requests the passphrase, but to unlock the screen just a PIN (however, Wrong PIN Shutdown powers off the tablet after a few wrong PIN trials).
I'm not entirely sure how I did it to be honest, but I suspect the reason is the following: the encryption of the tablet can only be done by setting up a password for screen unlock at first.
Then you use Cryptfs to change the encryption password.
Then you change the screen protection option to "PIN" instead of password. If you are running one of the latest Lineage OS builds, when you are asked "do you want to require a PIN also at boot?", counterintuitively, answer "yes".
THEN you must run Cryptfs again and re-set the storage encryption password. This way it works.
I did not dare starting TWRP again in recovery mode , I'm afraid it would mess up with the encryption.
Keeping an eye on the battery: it's pretty bad to be honest. I was used to my beloved Lenovo tablet, I was using it only as a PDF reader (flight mode, uninstalled all the crap etc) and, with the stock firmware, it had pretty much the same battery life of a real Ebook reader, I could easily leave it in the closet for weeks and find it still charged when I needed it. This Galaxy Note 10.1 is not even close with Lineage 14.1, now I killed all the unnecessary processes and set battery mode to maximum span, let's see if it gets better.
After a few days of test I can confirm poor battery life. Less than two days in complete standby, flight mode, energy saving mode. That really sucks.
I have to add: SIM card not recognized, only WiFi works.
TL;DR: do not install this ROM.
Did anybody test the official LineageOS build for the SM-P605 (lt03lte) ?
Is it working by now?
Has anybody an old (Octobre or Septembre) version of the official LinageOS for SM-P605 (lte03lte)? Unfortunately after the decision to no longer maintain that ROM all older downloads have been deleted and I have some problems with the december version
In MIUI it only has the option to use the lock screen PIN to encrypt the data partition. I know I can change the encryption password to something different manually, as described here
https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/
However when MIUI boots it only seems to allow users to enter a numeric decrypt password. I prefer to use an alphabetical or alphanumeric, as I find it less confusing using one PIN (for the lock screen) and an alphabetical or alphanumeric password for decryption and they're also longer and thus more secure than a 4 digit PIN.
Is there a mod for MIUI that will allow me to enter a alphanumeric decrypt password at boot?
Is no-one else bothered by this? Does everyone just use the same PIN for decryption and lockscreen? This seems like bad practice because if someone sees you enter your lockscreen PIN, they will then be able to unlock/decrypt the phone even after it is turned off or the battery runs out.
I've also found with the Note 5 the decrypt PIN screen on boot is very dim, making it more difficult to enter the PIN that it needs to be. My Note 4 isn't like this. I have Redfox Recovery on my Note 4 and OrangeFox on the Note 5 but I wouldn't have thought that would be causing this.
Hi,
I have Mi 9 SE with global rom v 10.2.2.0(PFBMIXM).
When I go to system settings->Additional settings->Privacy->Encryption & credentials, it shows that my device is encrypted. But in the past on other xiaomi phones I owned there used to be an option "Encrypt Device with lock screen password" which is missing in MI 9 SE.
So, in the past the phone used to ask for lock screen password during boot and only then then system/data disks would be decrypted and phone would start booting. Now this is not happening because the phone is using whatever device default password it has for decrypting the device during boot up. So I have following questions,
1) Can someone with above version of global rom confirm that they also do not have "Encrypt Device with lock screen password" option?
2) Can we also confirm if China and EEA Roms are also missing these options?
3) Is there any possibility of somehow enabling the "Encrypt Device with lock screen password" because I would really like to use my password for encryption rather than some device default password.
Many thanks in advance for your help
There is no way doing this and it's this way on all ROMs.