Database Users

Locked Out of S5

I'm locked out of my S5 and the only way to unlock it seems to be by alternate password, which I don't remember.
Google Android Manager will no longer allow you to reset the lock screen password, there are no other options listed, and it seems that my phone will undergo a factory reset about 10 failed attempts at guessing the password. I have one guess left.
Is there any way to save the data on my phone before the factory reset, or a way to bypass it completely?
The phone is not rooted at all, and I'm unsure as to the specific software version, as I can't look to see.

I think you can boot into recovery and maybe backup your files
Sent from my SM-G900V using XDA Free mobile app

How so?
I'm in recovery mode now.. I don't have any CWM or anything like that, and I don't see any options.
Maybe I should try to apply the recent update and see if that resets everything?

Updated to the latest version.
Doesn't look like that helped anything.
Still locked, and I don't want to try another password incase I'm still on my last try.

I can set up the ADB while in recovery mode... Can I backup via the ADB in recovery mode?

When I use adb devices, my device comes up as "sideload" rather than device? Why?

[Guide] FRP Bypass Solution *WITHOUT* USB OTG (Tested on Stock Rooted Project Fi Rom)

So I fell victim to googles new FRP Security feature that requires you to log in using the same gmail account associated with the phone before it was reset. Short of it was I decided to flash a 6.0 ROM after using the 5.1.1 ROM to get my Project Fi account activated correctly.
After flashing 6.0 and I began going through the setup wizard where I was eventually prompted to enter the credentials for the account that I had used previously. I entered my credentials and was then sent to another screen asking me to reset my Gmail password (Turns out google decided my login attempt was suspicious...). So i reluctantly reset the password not knowing I had just screwed myself(for 72 hours at least). There is a 72 hour reset time from the time you changed your account password until you're able to use it to authenticate during the setup process and until you authenticate you cant use the phone.
Not having a backup phone I took to google and found that the only way around this problem involved a USB OTG storage device loaded with an apk that causes the settings app to launch allowing you to do a real factory reset(complete wipe of all credentials and data). Resetting the phone this way removes any account associations allowing you to setup the phone as if it were new once you've re-flashed it.
Not having the tools needed to do it that way I thought about it and decided to try a few things out and eventually found my solution.
Disclaimer: I am not responsible for any damage or loss of data that may result from the following procedure.
Solution
Requirements
A computer with adb installed
USB cable
Rom with Persistent ADB Enabled (I used the 5.1.1 Stock, Rooted Project Fi ROM)
Phone booted and at the Setup Wizard
Procedure
Have the phone turned on and sitting at the startup wizard
Connect the USB to you computer and then plugin your phone ( I assume you've already setup ADB)
The phone may then prompt you and ask to verify the device fingerprint which you will say yes to
open a terminal and type:
Code:
adb shell
Code:
am start -S com.android.settings -c android.intent.category.LAUNCHER 1
This will launch the Settings.apk
***NOTE: This will completely wipe your phone!*** (Edit: The Reset program claims to wipe all internal storage but for whatever reason my SDcard data was not touched. Would still recommend pulling any wanted data from the device prior to resetting)
Go to the Backup & Reset menu and perform a factory reset
After the phone finishes resetting, proceed to boot back into Recovery mode and re-flash your ROM
The Setup Wizard will now go through the steps without the FRP authentication steps.
Again, I have only tested this on my T-Mobile Nexus 6 (using Project Fi) running 5.1.1 so your mileage may vary depending on your setup. If you find this worked or didn't work for your particular setup/situation then post your results here.
Hope this helps!
EDIT: The original solution using the USB OTG storage can be found here.
Just to clarify a bit. The problem that these two methods try and fix stems from a new feature introduced in Lollipop called FRP(Factory Reset Protection). It is meant to keep someone that has stolen a phone from being able to use it by simply doing a factory reset and reinstalling the OS. To counter this, google requires the user to verify they're the owner of the device that was reset by giving the credentials of the google account associated with the phone before it was reset. The issue arises when the password to this account is changed after the device was reset but before verifying ownership of the device during the setup process. When this happens, you have to wait 72 hours before you will be able to verify ownership using the new password.
Edit 2: Specified having a ROM with Persistent ADB Enabled as a requirement for this to work.

I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk

joyrida12 said:
...snip...
Click to expand...
Click to collapse
Ah, a workaround, nice!!! Tahnks for sharing!
Keep "OEM unlocking" enabled in the future. It will disable "Device protection"
---------- Post added at 02:27 PM ---------- Previous post was at 02:27 PM ----------
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This is not about 2 way auth i'm affraid

ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No, this isn't an issue with 2FA. From Google's standpoint this isn't an issue at all actually. This verification is, to my understanding, only required when the device is factory reset in recovery mode.
The purpose of 72 hour lock period seems to be there to protect user in the event someone is trying to gain access to their phone/account.
This normally isn't an issue since most people won't change their password in that small timeframe. In order to not require the verification, you have to disassociate the account from the phone before resetting it. This is done for you when you do a reset from the settings app on the phone. That's the reason for using these methods, it does a full reset including account removal.
Sent from my Nexus 6 using Tapatalk

@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!

Droidphilev said:
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Click to expand...
Click to collapse
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk

joyrida12 said:
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
perfect, thanks!

Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.

I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk

So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.

player911 said:
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
Click to expand...
Click to collapse
That was my thoughts exactly as it was happening to me, I initially was trying to figure out if there was an alternate authentication method and was a little surprised not to find one.
I really like the direction they're moving with thus security feature but I think it was thrown out a bit early. Nexus users are more likely to be doing factory resets and locking them with no way of fixing it (aside from waiting 3 days) out because they did so on a custom recovery isn't very cool on their part lol.
Sent from my Nexus 6 using Tapatalk

sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, that will work just fine.
yossijoe said:
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
Click to expand...
Click to collapse
It worked for me. Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
Edit: It could be that the project fi ROM has USB debugging enabled by default(just a guess, haven't looked at the source to verify).
Edit 2: Confirmed that the Stock, Rooted, decrypted 5.1.1 ROM for Project Fi has persistent ADB enabled. Adding this as a requirement to the original post.
Sent from my Nexus 6 using Tapatalk

sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
He's wrong, that absolutely will not be fine.
You need to make sure to remove any screen locking you've setup, sync your Google account, and then remove your Google account before resetting.
http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504

My nexus 6 doesn't have custom recovery installed,It has only stock one,the phone is on stock rom,and it is stuck in setup screen asking for 1st used gmail !
I have OTG usb cable but it is useless ,not working, seems motorola improved security in nexus 6,to be specific the phone has OEM lock ,so i can't install cust.recovery
is there any trick to apply those adb commands ?

any help friends ? im still stuck ,any way to disable OEM lock or to flash custom rom on frp locked nexus6 ?

joyrida12 said:
Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
...
.... the project fi ROM has USB debugging enabled by default
Click to expand...
Click to collapse
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5

W60 said:
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
Click to expand...
Click to collapse
Hey, first time poster, long time lurker. This is the first thing I have not been able to find a solution for.
In order to connect to ADB in recovery, does one need a custom recovery? My Nexus 6 bootloader is locked, running 5.1.0 LMY47D. I have fastboot access but can't pull up an ADB shell.:crying::crying:
I bought a Nexus 6 on eBay that was reset and I do not have the original users info. (I thought I was getting a pretty sweet deal because I'm so good at phones and blah blah)
Thanks in advance for any assistance!
- Beej

Beej4real said:
In order to connect to ADB in recovery, does one need a custom recovery?
Click to expand...
Click to collapse
As far as I know, yes, you need a newer version of a custom recovery. Anyway, if ADB doesn't connect, you certainly need another recovery, and you can't install that if you have a locked bootloader.
....
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?

W60 said:
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
Click to expand...
Click to collapse
I did give it a shot. No dice. I also tried entering lots of numbers in as the emergency number. No response from the phone.

Hi guys can you help to frp bypass on Samsung SM-G530H Galaxy Grand Prime without otg function, can i use this tut or need another rom for sm-g530h? where i can find Rom with Persistent ADB Enabled? Thanks

Does anyone have OEM Unlock on the SM-J530G?

I've been trying for a long time to get OEM unlock with the Samsung Galaxy J5 Pro SM-J530 G variant. I've seen people unlocking the BL in the J730G, same exynos chip.
Here is what I have tried so far:
All date/time tricks
Factory reset
Flash Stock ROM
Waited 7 days
My last attempt made me give up and ask for help here... I completely flashed the most recent stock rom, wiped everything using the CSC file not the CSC-HOME, I did the start setup logging into samsung account and google account, after completing the start setup I inserted the SIM card otherwise that stupid start setup would consume 4G costing me $$$.
Waited for 168 hours with the device always on, and still no OEM UNLOCK, I mean what else can I do... there's almost nothing about this problem with this device here on XDA... I'm hoping someone with a SM-J530G and that had OEM Unlock could tell me what was the process to enable this option. Or what are my options here? Thx
And by the way, I've seen something called Miracle Box, but I dont want to use it since it does not look very legal, I think its meant for FRP bypass. I'm just an android user trying to root my personal device e.e

I'm having the same problem, I'm tired of this, never buying Samsung again. I tried all the things I searched on the internet for hours and nothing works, I do not want to wait 7 days, if you find a method of bypassing that actually works, please do tell me, I will do the same if I find one.
I'm so pissed.

I have good news for you my friend, and for everyone that is reading this. I tried many and more times the same procedure changing small things. I will try to write it out as best as I can so I can help some fellow buddies who've got the same problem.
1 - (As I had already everything backed up and got nothing to lose) Factory Format the device (I did it from the bootloader), hell, I even also cleared cache just for god's sake.
2 - Proceed to initiate Android, DON'T sign-in to any account (nor Samsung nor Google), don't change the date during installation, finish set-up.
3 - DON'T enable Developer's Mode yet. Change the date, I've set it for a month back just to be damn sure (disable automatic date-set). Now go to the Software Updates tab and disable auto-updates and manually check for updates, once done, re-boot.
4 - Once rebooted enable auto-date (that should correct the old date and replace it with the actual one) and re-do the manual check.
5 - Re-boot and enable Developer's Mode and hopefully, for the love of Ragnar Lothbrok, OEM Unlock should be there. I hope it is for all of you.
Hope it helped, good luck buddy/buddies!

Franz Enz said:
I have good news for you my friend, and for everyone that is reading this. I tried many and more times the same procedure changing small things. I will try to write it out as best as I can so I can help some fellow buddies who've got the same problem.
1 - (As I had already everything backed up and got nothing to lose) Factory Format the device (I did it from the bootloader), hell, I even also cleared cache just for god's sake.
2 - Proceed to initiate Android, DON'T sign-in to any account (nor Samsung nor Google), don't change the date during installation, finish set-up.
3 - DON'T enable Developer's Mode yet. Change the date, I've set it for a month back just to be damn sure (disable automatic date-set). Now go to the Software Updates tab and disable auto-updates and manually check for updates, once done, re-boot.
4 - Once rebooted enable auto-date (that should correct the old date and replace it with the actual one) and re-do the manual check.
5 - Re-boot and enable Developer's Mode and hopefully, for the love of Ragnar Lothbrok, OEM Unlock should be there. I hope it is for all of you.
Hope it helped, good luck buddy/buddies!
Click to expand...
Click to collapse
That is awesome! I'm going to try it tomorrow, I've been using the device doing my third 168 hours. If it fails again I will repeat everything like you did.
Thank you!!
Sent from my SM-J530G using XDA Labs

Another 168 hours wasted and I followed the trick above, it does not work it was patched with the august 2018 security patch, my device is running with the november 2018 security patch.
My frustration is beyond what I expected to experience with this device... I guess most people were able to activate this thing except me >.<

Enlighten me
When you keep it for 168 hours does the WiFi have to be on or is that not necessary

Sameer521 said:
When you keep it for 168 hours does the WiFi have to be on or is that not necessary
Click to expand...
Click to collapse
I tested with wifi always on and logged to google and samsung account so it could sync whatever it had to sync, still no success. I have no idea on how to meet the requirements to unlock the BL on this phone

scroll-lock said:
I tested with wifi always on and logged to google and samsung account so it could sync whatever it had to sync, still no success. I have no idea on how to meet the requirements to unlock the BL on this phone
Click to expand...
Click to collapse
Is their any other method for 2019.am at my wits end

OK I tried something and it worked to unlock the oem.
Have a Samsung account,then go to find my mobile website and press unlock.it did the trick for me.hipw it helps you as well

Firstly, i use miracle box and then i use samsung tools pro to "reboot" my device because when you unlock the bootloader there is a fail on the room.
here you have a video which could help you.

HELP!!! SM-P585Y FRP with Oreo

[SOLVED]
I apologize for my stupidity...
On a recent trip to China I recklessly purchased the used TAB A 10.1 model SM-P585Y.
The tablet worked perfectly, but when I came home I did a reset to clean it and once restarted the system remains with the FRP Lock.
The operating system is Oreo and I can't load any more twrp.
If I downgrade to Marshmallow, it doesn't reboot but only enters Factory Recovery mode...
In this mode, if I enable the Developer Option and then usb Debugging in the settings, there is no trace of the OEM unlock.
I can't load TWRP with odin nor with ADB (but maybe I don't do the correct procedure...)
If I do the update again at Oreo there is no recovery...
This is because when I flash Oreo with Chimera, the image file in the firmware is greater than the PIT, so I have to skip otherwise it stops.
When I start the system only arrives at the google account screen but I can't go any further, not even by opening a sort of chrome browser reduced by touching the google sign from one of the info screens that I can access from the keyboard settings.
Can someone please help me?

grifonedisanremo said:
I apologize for my stupidity...
On a recent trip to China I recklessly purchased the used TAB A 10.1 model SM-P585Y.
The tablet worked perfectly, but when I came home I did a reset to clean it and once restarted the system remains with the FRP Lock.
The operating system is Oreo and I can't load any more twrp.
If I downgrade to Marshmallow, it doesn't reboot but only enters Factory Recovery mode...
In this mode, if I enable the Developer Option and then usb Debugging in the settings, there is no trace of the OEM unlock.
I can't load TWRP with odin nor with ADB (but maybe I don't do the correct procedure...)
If I do the update again at Oreo there is no recovery...
This is because when I flash Oreo with Chimera, the image file in the firmware is greater than the PIT, so I have to skip otherwise it stops.
When I start the system only arrives at the google account screen but I can't go any further, not even by opening a sort of chrome browser reduced by touching the google sign from one of the info screens that I can access from the keyboard settings.
Can someone please help me?
Click to expand...
Click to collapse
Any chance of turning off FRP through the Google account of whoever's account was on the tablet once you had it? I thought you could disable that by logging into Google with that account and turning it off via the web.
Then again, I'm not the sharpest tool in the shed, others probably know much better.
Good luck!
Steve

steven.rn said:
Any chance of turning off FRP through the Google account of whoever's account was on the tablet once you had it? I thought you could disable that by logging into Google with that account and turning it off via the web.
Then again, I'm not the sharpest tool in the shed, others probably know much better.
Good luck!
Steve
Click to expand...
Click to collapse
When I bought the used tablet, I didn't know about the FRP, now I'm at home, and I wouldn't even know how to find the Chinese who sold it to me...

grifonedisanremo said:
When I bought the used tablet, I didn't know about the FRP, now I'm at home, and I wouldn't even know how to find the Chinese who sold it to me...
Click to expand...
Click to collapse
Solved, thanks!

grifonedisanremo said:
Solved, thanks!
Click to expand...
Click to collapse
Just out of curiousity, what worked for you?
Steve

steven.rn said:
Just out of curiousity, what worked for you?
Steve
Click to expand...
Click to collapse
External service, they connected remotly with me and did it...

Shield TV won't accept Google login credentials

I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.

Jesterium said:
I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem. Did you manage to get this fixed by chance?

Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload

Jesterium said:
Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...

Aripex said:
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...
Click to expand...
Click to collapse
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.

Jesterium said:
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.
Click to expand...
Click to collapse
Cool - thanks for the advice. Like you, I tried everything too. I tried 2FA on/off, turned on the "Less secure apps" option in my Google Account > Security. I also tried to factory reset without any success, as well as using a different Wi-Fi network and opened a new dummy Google Account just to make sure my original account wasn't the problem! None of it worked and had me tearing my hair out.
I have a 2015 Shield TV that was sealed and unused until the last week. I have never seen an issue before where even an older Android device cannot be signed into Google. At least it is a lesson learned for the future....!
Anyway, I've successfully flashed a newer version of Android now and it works. Hallelujah!

Right guys I have just got a replacement NVidia pro 500gb from them for a bricked unit and I am having the same problem. As I am a novice I have no clue about flashing an updated image to it. Is there anyone who is will to spell it out for me in easy to follow instructions??