I've got a company-owned Android phone that needs to be wiped to prepare it for re-use, but it's locked with a passcode. I also do not see it listed in our MDM software, so I can't force a remote wipe that way. It appears that it could be wiped with a Google account, but I do not know what Google account it may have been linked to. Is there a way to expose which Google account it was attached to in the hopes it's one we have access to? Or is there a way to totally reset it to factory and wipe the data?

Passwords saved in Samsung Pass will be stored in Knox Vault. So, are the passwords saved in Google Password or other third parties also stored in Knox Vault?

I share an Android 14 tablet with another user, each with their own password. If the other user is active, can I log into my session without having to enter the other user's password? Is there any way to make it so that, if I want to log in with my user, I just enter MY password to access and not the other user's? Thanks!

I faced a problem with my new updated system, HyperOS 14. before I updated my system, there was a feature Shutdown Confirmation. When I want to turn off my device, that forces me to insert a password. If correct, then the device will turn off. I don't know why this feature was not found after the update.

I have an old Allview P5 Energy which I've forgotten the password of, running Android 5.1. I was wondering if there is any possible way to recover its data. adb devices says the device is unauthorized and the recovery mode doesn't have a backup option. It does however have an "update from ADB". By using adb sideload is there any way I could bypass the password?

I just upgraded from Android 11 to Android 12 and now It asks me every single time I unlock the screen. Before, it would ask me for the password only once every half an hour as I had configured it. How can I get back to that behaviour in Android 12 that only ask me for the password once on a while? UPDATE: Same situation in Android 13.

I moved an account from phone x to phone y and secured the account so that phone x had no access anymore. Next I enabled 2FA through the phone number on the new phone, phone y and **discarded** phone x. That worked fine. Then I changed my phone number without updating the 2FA. On phone y I sent an e-mail to myself to confirm that the account was at least working, which it was. When I tried to login on a new phone to the account I ran into problems with 2FA because of the now-defunct phone number. Oddly, the option to hit "tap" on a phone was presented as an option. However, there was no message on phone y about this. No model was mentioned, so possibly it was an alert for phone x for some reason. I went into account settings on phone y and *believe* that added an additional number for 2FA after entering the pattern to confirm that phone y was mine. I also had a confirmation code sent to a secondary e-mail. This I thought would be the solution. Trying to sign-in on phone z to this account brought up an option to sign-in, now specifying phone y by model. However, there were no alerts on phone y as I would expect to see. Ultimately, it turned out that I was now signed out of the account on phone x. I had an e-mail sent with a confirmation code, again, and entered the confirmation code. Now the account is locked for twenty four hours. Clearly, I should've confirmed that phone y was logged into the account and connected. Unfortunately, when logging into the account on phone z the phone number was still listed as the old number. I'm waiting twenty four hours for an e-mail from Google while they evaluate, but is there something else I could've done here? Now that I'm logged out of the account on phone y it's seemingly now behind a wall of 2FA with an old phone number.

A friend gave me an old Android tablet (**Medion Junior Tab S7322**) which dates back into the Android 4.4 days and asked if I can get access to his pictures on the internal storage because she forgot her password she had set up a bunch of years ago. I started researching how something like that can be done and now I ended up here, asking if someone knows any method to "**break-in**" or recover data from the internal memory since all other methods/attempts were either not viable or have failed, due to Androids security restrictions. There is no linked Google account, no pattern lock, and debug mode is off. Though I assume this device has a JTAG connector on the mainboard, which I couldn't verify yet, since I don't want to open the device till all other methods have been exhausted. 1. Are there any tools that can remove/change the password on a tablet via USB connection, ignoring all of the security locks by exploiting known vulnerabilities on the tablet model/ Android 4.4? 2. Can you maybe brute-force the password, since my friend mentioned it probably wasn't too secure.

I am seeking ways to disable installing apps with APK, i.e. make the setting "Allow apps from unknown sources" password-protected or disable completely for user. Is there a way? Maybe it's possible from adb shell? I am running LinageOS 13 on Lenovo Vibe A Plus and can flash 14.1 if needed.

I want to install a software provided by my company but the IT admins only accept devices that support the "Auto factory reset" functionality (automatically perform a factory after if the wrong lock screen password/PIN has been entered 15 times consecutively). They claim nearly every Android phone would have this function. I know that certain Samsung phones have this functionality but Samsung is known to heavily modify Android. So my main question is: **Is or was the "Auto factory reset" functionality ever included in general Android?** I have checked multiple devices with different Android versions running. And except from Samsung no device had this functionality, so I am a bit confused...

I have a **Realme 8** phone as my primary device. It had a PIN and my fingerprint set up as the screen lock. Around a week ago at around 4 am, I decided to change my PIN as I keep changing screen locks after some 5-6 months. So this time I decided to use PASSWORD (which contains alphanumeric strings and not just numbers like PIN) which I use on my laptop as well. So I navigated to settings to change it, I entered my current 5-digit-PIN as asked, then I enter my new password (alphanumeric) and then at the final step when I had to tap on "Done", I think I accidentally pressed back button. Now after that, when I turned my screen off, I was expecting new Password screen but it was not there (yes I get it, I didn't tap on DONE so it makes sense). As expected, it was again PIN screen which makes sense. What does NOT make sense is that when I entered my old 5-digit-PIN, it said **incorrect password try again.** I've tried my PIN like a 1000 times, it just don't work. But I could still use a fingerprint right? Yes I was able to unlock my phone through fingerprint. As I researched more about this issue, I found an easy fix to this common problem, which was to restart the device (worst mistake). It worked for everybody except me. I restarted my device. Bang. Now I cannot even use my fingerprint (as when an Android device restarts, it doesn't let us unlock the device with fingerprint, a well known fact). So I'm locked out. Is there a way to unlock the device with the fingerprint after rebooting? I cannot factory reset it as it has Gigabytes of my data that I have unfortunately not backed up anywhere else. Please note that the screen calibration is not damaged, I can see what numbers I am typing in the PIN field. It just does not work. Also there is no option of Forget password as well as Google forget password. I can try PINs as many times I want. There is no timer after, say 5, incorrect attempts. I have tried 100 PINS at a time consecutively. I can boot into Realme's stock recovery, it has an option of "Update phone (without losing data)" when I click it, it asks for a "Password" this time (not specifically PIN), on an alphanumeric QWERTY keyboard. But neither the PIN works, nor the password that I had entered at around 4 am. USB debugging is turned off, hence I cannot try ADB. I can access the notification action center and can connect with WiFi as well. Any idea what should be done now? It has my really really important data I cannot afford to lose. It also didn't had an SD card hence I'm worried if formatting it and then data recovery will work or not. Any help is appreciated. If someone wants to know the PIN or password for some reason, let me know. Thank you everyone

I have a Android 8 TV box. In developer settings, I can enable/disable USB debug. After enable, any device in LAN can use adb connect to connect to (no password or auth required) and control it via shell. My questions: 1. Does that mean any app on the Android devices can connect 127.0.0.1:5555 and get a shell permission? (The Android box is rooted. In adb I can use su directly) ss -pnltu | grep 5555 got:

tcp    LISTEN     0      4        :::5555                 :::*                   users:(("adbd",pid=5051,fd=15))

How can I protect my Android from being hacked by an installed app. 2. I can't use setprop ro.adb.secure 1, it says

setprop: failed to set property 'ro.adb.secure' to '1'

It's always 0. So the ROM doesn't support the adb RSA auth security feature. How can I protect my Android from being hacked from other LAN devices. (I want to keep usb debugging on cause I can install/uninstall apps from PC) ------------- **Update**: I come up with a simple trick: changing the port

setprop service.adb.tcp.port 5550

that will hide my adbd from 80% hackers I think. But, still, that's not a real solution. It's just a workaround

I am looking for a way to prevent the installation of apps from any sources (eihter playstore or apk) Is there not anything similar to a "sudo" password for apps installation on android so a password is required before installing any app?

If my phone does not have a passcode, but is encrypted by default, and I factory reset it, is my data safe? Or is there a way someone can decrypt it since it had no passcode

How can I set a distinct password for: 1. The Full Disk Encryption password (used to boot the device) 2. The Lock Screen password (used to unlock the device) For security reasons, I use a 25-50 character password to protect my devices when off and a shorter password for the lock screen. This was previously possible using apps such as: 1. EncPassChanger or 2. Cryptfs Password I just upgraded my phone, and neither of these apps appear to work in Android 10. How can I set a distinct password for [a] the boot password and [b] the lockscreen password in Android 10?

Now a time, whenever you make a login or anything using a username or password, Google prompts you to save the password in your primary account. Unlike earlier, when it was limited to browsers only, but now the prompt comes even when you're logging with an app. How is Google able to know that it is login and they have to prompt to save password?

According to the ASOP documentation , it is no longer possible to use FDE and the user is forced to use File-Based Encryption > Note: Devices running Android 7.0–9 support full-disk encryption. New devices running Android 10 and higher must use file-based encryption . Though I understand the argument for convenience (morning alarms, updates, etc), there are several strong use-cases where it's better to have a FDE with a very long passphrase -- consider journalists, activists, political prisoners, etc crossing borders with oppressive governments. It's better to just turn the device off and rely on FDE to protect absolutely everything in these situations. I see that GraphoneOS's FAQ page talks about FDE and also Android 10, but doesn't directly answer this question. Do the GraphoneOS releases that are based on Android 10 still use FDE? If so, how?

How can I setup Full Disk Encryption in Android 10? According to the ASOP documentation , it is no longer possible to use FDE and the user is forced to use File-Based Encryption > Note: Devices running Android 7.0–9 support full-disk encryption. New devices running Android 10 and higher must use file-based encryption . Though I understand the argument for convenience (morning alarms, updates, etc), there are several strong use-cases where it's better to have a FDE with a very long passphrase -- consider journalists, activists, political prisoners, etc crossing borders with oppressive governments. It's better to just turn the device off and rely on FDE to protect absolutely everything in these situations. So the question is: how do at-risk folks use FDE in Android 10? > Note: creative answers that involve root, custom ROMS, apps, etc are welcome. I'm asking how this can be done on an Android 10 device. I'm not asking if Google "permits" it to be done.

I used dd from twrp terminal to write to userdata on my phone using dd if=userdata.img of=/dev/block/platform/mtk-msdc.0/by-name/userdata when I did reboot, it asks for my password. I tried all the previous passwords I used before, but to no veil. Why is it asking for my password? How to overcome this situtation? Reseting does not seem to be working.

I have forgotten my unlock pattern and tried to lock my device with a password on Android Device Manager (ADM). It did lock and a message, "Your device is locked by Android Device Manager" appears, but there's no way of entering a password on that screen.  There's no password field, and just a back click and it's all gone. Pressing​ that lock icon doesn't work, it's not a button, neither sliding up or down, left or right is any good. How to unlock it?