I upgraded to MM v20c and had a pattern unlock set - since then I can no longer unlock. I even went to Android Device Manager and set a code lock - but still can't unlock. I have some important info on the device and do not want to reset the system. Is there any way to do it?
Just to add - I do have access to my gmail, so if there is a way to reset the lock screen do let me know.
Using ADM I can again "lock" the device but dont get a prompt to enter the code. I can also make my phone call another number - but there seems np way to unlock it. Any help will be appreciated. Thanks!
EDIT: There is no option to enter the code from ADM anywhere.
EDIT 2: I can use adb
Try with this methods
redentor666 said:
Try with this methods
Click to expand...
Click to collapse
I am not rooted
Just curious if anyone has tried to change the first boot unlock procedure so that it can be unlocked with fingerprint instead of a pin as I don't like leaving it on swipe.
razgriz1234 said:
Just curious if anyone has tried to change the first boot unlock procedure so that it can be unlocked with fingerprint instead of a pin as I don't like leaving it on swipe.
Click to expand...
Click to collapse
The only way I know of is through an Xposed module but Xposed only goes up to Android 7. It's a safety feature google put into Android, there were some custom ROMs for the Nexus 6p that had the feature, so maybe we will see it in the future in a custom Rom.
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
SnowFuhrer said:
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
Click to expand...
Click to collapse
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
-sofiann- said:
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
Click to expand...
Click to collapse
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
The Galaxy A3 2015 (SM-A300FU) has no OEM unlock as A3 from 2015 don't even have FRP Lock, neither it has RMM state. That means there is no lock which prevents you to flash any custom binaries like TWRP recovery with Odin. You'll only lose access to knox apps/services (because of knox 0x1), rest remains the same.
SnowFuhrer said:
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
Click to expand...
Click to collapse
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
-sofiann- said:
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
Click to expand...
Click to collapse
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
SnowFuhrer said:
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
Click to expand...
Click to collapse
Hi !
Thank you very much both of you for your help. Indeed there was no OEM unlock.
Many posts talking about OEM unlock existing on that A3 and the fact that I couldn't check if it was locked or not using the two methods advised (with adb or with a special code to dial up on the phone interface) led me to stop at that step to be sure before going on.
It is advises not to root a divise with a bootloader locked to avoid bricking it.
Anyway, trusting your input I did the whole process of rooting and putting a custom rom and it's all great !
I recently had a stock Pixel 2 die, couldn't access anything to try and fix the problem because the I never allowed OEM unlocking, too bricked to access recovery or anything. To avoid this happening with my Pixel 2 XL, I want to unlock the bootloader just in case I need to flash anything to recover the device if something similar happens again. No interest in flashing anything custom anymore, can't be bothered to attempt to hide apps from root since I've had problems doing that in the past just to get my online banking to work.
My question is, will allowing OEM unlocking on a stock image stop anything like banking apps and Google Pay from working? I know a lot of these apps can detect root and stop themselves from working, but would this do the same with just allowing OEM unlock in the developer settings? I wouldn't unlock the bootloader through ADB until something goes wrong to begin flashing etc.
ridley1000 said:
I recently had a stock Pixel 2 die, couldn't access anything to try and fix the problem because the I never allowed OEM unlocking, too bricked to access recovery or anything. To avoid this happening with my Pixel 2 XL, I want to unlock the bootloader just in case I need to flash anything to recover the device if something similar happens again. No interest in flashing anything custom anymore, can't be bothered to attempt to hide apps from root since I've had problems doing that in the past just to get my online banking to work.
My question is, will allowing OEM unlocking on a stock image stop anything like banking apps and Google Pay from working? I know a lot of these apps can detect root and stop themselves from working, but would this do the same with just allowing OEM unlock in the developer settings? I wouldn't unlock the bootloader through ADB until something goes wrong to begin flashing etc.
Click to expand...
Click to collapse
I don't believe it will stop Google Pay from working, but have not tested it. As for other apps, it depends on whether that app checks for an unlocked bootloader. Some apps do check for unlocked bootloader.
Hi guys.
I was adding face unclocking and I've also set up a new PIN code. Everything was working great until the periodic prompt with need to enter a PIN. Unfortunately I don't remember it and I've got a big problem right now. Is there a way to reset the PIN code somehow? My phone is OnePlus 7t with root and unlocked bootloader. I don't know if it helps but my biometric uncloking methods should also work (fingerprint and face). I just need to pass that prompt for PIN and then reset it somehow. I've access to all Google accounts logged in the phone, but I don't see the option to reset the PIN code on www.google.com/android/find.
Is there any hope for me?
Best regards,
Tom.
Format data in recovery should remove lock screen pin--not Google password
thardy00 said:
Hi guys.
I was adding face unclocking and I've also set up a new PIN code. Everything was working great until the periodic prompt with need to enter a PIN. Unfortunately I don't remember it and I've got a big problem right now. Is there a way to reset the PIN code somehow? My phone is OnePlus 7t with root and unlocked bootloader. I don't know if it helps but my biometric uncloking methods should also work (fingerprint and face). I just need to pass that prompt for PIN and then reset it somehow. I've access to all Google accounts logged in the phone, but I don't see the option to reset the PIN code on www.google.com/android/find.
Is there any hope for me?
Best regards,
Tom.
Click to expand...
Click to collapse
Do you have TWRP custom recovery? If not, you need to install TWRP then use TWRP to delete your lock settings.
Unfortunately google has discontinued that unlock feature.
deleting locksettings.db works only on devices encrypted with default_password. For OnePlus 7t it will destroy encrypted data, because encryption keys cannot retrieved without login credentials.