Recovering data from SM-J510FN with forgotten lockscreen PIN - Samsung Galaxy J5 Questions & Answers

Greetings everyone!
I've stumbled upon a bit of a interesting problem today. I came to visit my cousin living abroad and was asked if I could somehow recover her data from SM-J510FN which she forgot a password for (she wasn't using it after she got a new phone, hence the reason she forgot the PIN ...). Phone is fully stock, (she is not tech savvy) so I believe she didn't even touch developers options (I don't know if USB debugging is on by default) and device has a FAP lock when I booted into download mode *It really does say it in the upper left corner of the screen when booted in DL mode*. So I tried the following:
Tried deleting *.key with ADB (didn't show the device with "adb devices" command)
Flashing TWRP with Odin (failed because of the FAP lock)
I could enter bootloader and update device via ADB sideload/SD card (vol up + home key combo when booting)
Phone is fully stock, I know I could just wipe/factory reset and call it a day, but there must be a way to recover it
Thanks in advance!

Vuxa said:
Greetings everyone!
I've stumbled upon a bit of a interesting problem today. I came to visit my cousin living abroad and was asked if I could somehow recover her data from SM-J510FN which she forgot a password for (she wasn't using it after she got a new phone, hence the reason she forgot the PIN ...). Phone is fully stock, (she is not tech savvy) so I believe she didn't even touch developers options (I don't know if USB debugging is on by default) and device has a FAP lock when I booted into download mode *It really does say it in the upper left corner of the screen when booted in DL mode*. So I tried the following:
Tried deleting *.key with ADB (didn't show the device with "adb devices" command)
Flashing TWRP with Odin (failed because of the FAP lock)
I could enter bootloader and update device via ADB sideload/SD card (vol up + home key combo when booting)
Phone is fully stock, I know I could just wipe/factory reset and call it a day, but there must be a way to recover it
Thanks in advance!
Click to expand...
Click to collapse
Was it pin or other type of lock?

Yes, it's a PIN type lock, also I forgot to mention that it's running 7.1.1 firmware

Vuxa said:
Yes, it's a PIN type lock, also I forgot to mention that it's running 7.1.1 firmware
Click to expand...
Click to collapse
Then...you can't.

Related

[Q] Screen cracked and unresponsive but display still visible. Need help getting data

Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site

Blindly wipe A310f - some problems

Hi,
as my screen is defect, I want to sell my A310f in parts. Before that I obviously need to wipe it.
The following things I tried in the last days:
- wiping via ADB was not possible -> "unauthorized device" (I had no chance to put in USB-Debug-Mode [the phone should have been in this mode because I always put my phones in debug mode])
- wiping it straight from the phone -> I am on Marshmallow with stock recovery (had a custom recovery with custom kernel on Lollipop)
-> question1: when flashing Marshmallow, does it replace my custom recovery with the stock recovery?
-> question2: is the stock recovery in 6.0 identical to the one on Lollipop?
I assumed the recovery to be stock on my phone und to be identical to the one on Lollipop. So I booted my A310 in recovery and navigated blindly to wipe:
- 4*volume down
- 1* power
- 7*volume down
- 1* power
wait for some seconds
- 1* power
---> phone should have rebooted ... but it did not. It did not respond at all so I had to remove the battery.
After doing this I connected my phone via USB to my PC and tried to look if the internal SD has some more space (should be the case if the wipe was completed).
But now my PC doesn't show the internal SD in the explorer. Phone is charging as usual via USB.
Is this a good sign (wipe done) because the stock settings dont allow the PC to have access to the internal SD? Or did I screw up?
Thanks and regards,
blub
blub0815 said:
Hi,
as my screen is defect, I want to sell my A310f in parts. Before that I obviously need to wipe it.
The following things I tried in the last days:
- wiping via ADB was not possible -> "unauthorized device" (I had no chance to put in USB-Debug-Mode [the phone should have been in this mode because I always put my phones in debug mode])
- wiping it straight from the phone -> I am on Marshmallow with stock recovery (had a custom recovery with custom kernel on Lollipop)
-> question1: when flashing Marshmallow, does it replace my custom recovery with the stock recovery?
-> question2: is the stock recovery in 6.0 identical to the one on Lollipop?
I assumed the recovery to be stock on my phone und to be identical to the one on Lollipop. So I booted my A310 in recovery and navigated blindly to wipe:
- 4*volume down
- 1* power
- 7*volume down
- 1* power
wait for some seconds
- 1* power
---> phone should have rebooted ... but it did not. It did not respond at all so I had to remove the battery.
After doing this I connected my phone via USB to my PC and tried to look if the internal SD has some more space (should be the case if the wipe was completed).
But now my PC doesn't show the internal SD in the explorer. Phone is charging as usual via USB.
Is this a good sign (wipe done) because the stock settings dont allow the PC to have access to the internal SD? Or did I screw up?
Thanks and regards,
blub
Click to expand...
Click to collapse
"unauthorized device" means you'll have to click OK on the pop-up dialog in the phones display before you can use adb.
You have to do when you connect to adb first time, or after a factory reset to authorize cumputer access to it.
Probably not that easy with a broken display.
Q1: Yes, it will overwrite recovery with stock one.
Q2:Yes, they should function the same.
Do you have a lock on your screen?
Computer won't get any access to internal memory before is unlocked.
If you havn't removed your accounts in phone, then it's probably frp lock on as well.
I once was in the same position but for another device, but I managed to find a engineering boot/sboot which allowed adb at all times.
tys0n said:
"unauthorized device" means you'll have to click OK on the pop-up dialog in the phones display before you can use adb.
You have to do when you connect to adb first time, or after a factory reset to authorize cumputer access to it.
Probably not that easy with a broken display.
Q1: Yes, it will overwrite recovery with stock one.
Q2:Yes, they should function the same.
Do you have a lock on your screen?
Computer won't get any access to internal memory before is unlocked.
If you havn't removed your accounts in phone, then it's probably frp lock on as well.
I once was in the same position but for another device, but I managed to find a engineering boot/sboot which allowed adb at all times.
Click to expand...
Click to collapse
Additional info: before the described "wipe" procedure I was able to access the internal storage via PC (without having to click something on the screen, as it wasn't possible because of the broken screen).
Just after this "wipe" it is now not possible to access storage.
How long does it take to wipe the data? I probably just waited for some seconds
Yes I had a lock screen on my A3 (but as described I could access the storage no problem).
Sry, I dont understand what youn mean by that:
If you havn't removed your accounts in phone, then it's probably frp lock on as well.
Click to expand...
Click to collapse
Google is my friend...
The FRP lock would also suggest that the wipe was done correctly, right?
blub0815 said:
Additional info: before the described "wipe" procedure I was able to access the internal storage via PC (without having to click something on the screen, as it wasn't possible because of the broken screen).
Just after this "wipe" it is now not possible to access storage.
How long does it take to wipe the data? I probably just waited for some seconds
Yes I had a lock screen on my A3 (but as described I could access the storage no problem).
Sry, I dont understand what youn mean by that:
Google is my friend...
The FRP lock would also suggest that the wipe was done correctly, right?
Click to expand...
Click to collapse
Well..I don't know. Maybe you successfully wiped it if you can't see anything on your computer.
FRP lock means that if you factory reset your phone with pin/pattern lock set AND have a google account activated on phone,
you will have to log in with your google account after factory reset before you can use it again.
It is locked to your google account.
(if you sell it and someone changes the screen, it still needs to be logged in to your google account before frp can be removed so he can use the phone)
tys0n said:
Well..I don't know. Maybe you successfully wiped it if you can't see anything on your computer.
FRP lock means that if you factory reset your phone with pin/pattern lock set AND have a google account activated on phone,
you will have to log in with your google account after factory reset before you can use it again.
It is locked to your google account.
(if you sell it and someone changes the screen, it still needs to be logged in to your google account before frp can be removed so he can use the phone)
Click to expand...
Click to collapse
So it seems there is no way around and I need to check the mainboard with a display unit ...
Samsung gets on my nerves ....
Thanks for the Help!

Loads of trouble with removing FRP from A5 2017 (A520F)

So, this has been giving me lots of trouble. The phone is locked with FRP. (By the way I am a complete noob). I tried to flash(root? what is it called?) the phone with CF-Auto-Root but it gave me a "Custom Binary(RECOVERY) Blocked By FRP Lock" in the Odin mode. I tried flashing with TWRP also and I got the same thing. I obviously cannot access the phone to remove the "OEM protection", which is apparently the fix. Also, excuse me if I'm going about this the wrong way and there is a much simpler method of removing the FRP from my phone. Thanks
Download the Smart Swtich and connect phone with USB
Make sure all samsung USB drivers are installed
Then start SS and press MORE button and select Emergency Software Recovery wait about 1Hour Maybe less to firmware download and the phone will boot but u need to enter your gmail and password to acess it
Press Thanks if it works
Cheers

PIN is not corect after Oreo update

Hey guys
Today i got update to Oreo (1.6g) on my LG G6 (Italy)
After update got finished phone booted like normaly do.
I typed my PIN , which was perfectly correct , then PIN from my SIM card,and usually there is 3rd lock screen that is fingerprint or PIN number (4 digits).
I was like : Oreo here i come, BUT NO not happend , i had fingerprint to unlock so i tried that, but it said : u can't use fingerprint now , so i typed my 4 digits lock screen code and it said that its wrong one , i tried multiple times and even different ones , that made me really confused (i'm 100% sure its the correct one), i rebooted the phone and the story stays the same , but now the 1st PIN (on the bootload screen) that where correct for the 1st time is not working at all (it was the same as fingerprint unlock).
What should i do? backup and factory reset or what? is that a well known Oreo bug?
go in TWRP, and go data/system with the file manager, and delete the file locksettings.db, restart the phone and it will be good
but i have a completly stock device , with bootloader locked.
Or am i'm missing something...?
im stuck at secure startup.
bizzqu1t said:
but i have a completly stock device , with bootloader locked.
Or am i'm missing something...?
im stuck at secure startup.
Click to expand...
Click to collapse
ok without TWRP will be impossible to unlock your phone the only solution is reinisialization :/
Its whatever i can do factory reset , but can i backup my files atleast? when i connect my device to PC i can hear the sound that he got connected but nothing more , no folders or atleast icon , that means that device is not fully turned on or smth? no chance to backup?
bizzqu1t said:
Its whatever i can do factory reset , but can i backup my files atleast? when i connect my device to PC i can hear the sound that he got connected but nothing more , no folders or atleast icon , that means that device is not fully turned on or smth? no chance to backup?
Click to expand...
Click to collapse
Alas you can not recover your data the purpose of a lock is to block access to sensitive data in case of stolen for example so that it is impossible to recover anything : /
Thx for all the responses,i really appreciate that,i guess RIP.
i experience the same thing, my galaxy J8 got update this morning and after the phone restart it asked me for the pin, and after i enter "my pin", itu says it is incorrect. this is awful
guys how did it end. I have secure start-up screen in LG G6 after OTA. My regular pit is not working

MDM Locked Galaxy Tab A

I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!
I can fix it remotely the last hope
Same Issue here,
Any one had any luck with MDM T307U. Please assist.
rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.
How to Remove MDM Control from Android?​For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.
Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3

Categories

Resources