Database Info

FRP bypass Pixel w/ USB Debugging OFF

Hey guys, new here, sorry can't post in recoveries section.
I recently bought a Pixel off ebay and the guy that sold it to me bought it off Gumtree. The original seller left all his stuff on it and the guy i bought it off couldn't even access the phone because it had a passcode lock on it. He tried contacting the owner but he never responded (yayyy).
Then there's me, because I'm smart and was like I CAN JUST FACTORY RESET IT, which kicked in the FRP. Unfortunately Google has had fun developing this phone to be super secure and although I no longer have a passcode to worry about, I can't bypass the FRP and I don't know the original owner's account details.
Here's some details:
USB Debugging is OFF
Only option I have on ADB is sideload
Bootloader is LOCKED
Phone is NOT ROOTED
Currently running 7.1.1
Phone is CARRIER unlocked (I can receive calls and use my data when trying to log into my gmail, which doesnt work because I have to use original account).
Is there any solution to bypass this? Much appreciated. I tried to go through google because I bought the phone off ebay and so the FRP prevents them as I didn't buy it directly off google. Am trying to track down the original owners details via my ebay seller to hopefully force the owner to comply. Any way I can get around this would be amazing.

josiedalek said:
Hey guys, new here, sorry can't post in recoveries section.
I recently bought a Pixel off ebay and the guy that sold it to me bought it off Gumtree. The original seller left all his stuff on it and the guy i bought it off couldn't even access the phone because it had a passcode lock on it. He tried contacting the owner but he never responded (yayyy).
Then there's me, because I'm smart and was like I CAN JUST FACTORY RESET IT, which kicked in the FRP. Unfortunately Google has had fun developing this phone to be super secure and although I no longer have a passcode to worry about, I can't bypass the FRP and I don't know the original owner's account details.
Here's some details:
USB Debugging is OFF
Only option I have on ADB is sideload
Bootloader is LOCKED
Phone is NOT ROOTED
Currently running 7.1.1
Phone is CARRIER unlocked (I can receive calls and use my data when trying to log into my gmail, which doesnt work because I have to use original account).
Is there any solution to bypass this? Much appreciated. I tried to go through google because I bought the phone off ebay and so the FRP prevents them as I didn't buy it directly off google. Am trying to track down the original owners details via my ebay seller to hopefully force the owner to comply. Any way I can get around this would be amazing.
Click to expand...
Click to collapse
If I understand your situation correctly, you have e a rough road ahead of you. The Google kill switch can only be disabled by the legitimate Google account holder, before the phone was reset.

If this was easily unlocked, it wouldn't be an option worthwhile. Basically, if you get it unlocked then Google has wasted their time on developing that feature.
I don't think you'll be getting into that phone and honestly, I hope you don't because then that means mine is less likely to be stolen since it is worthless without my credentials

For years, we've all learned to disable Find My iPhone before we sell an IOS device. Similarly, we have to deactivate Google's kill switch prior to factory reset a Marshmallow or Nougat device. It's really a good anti-theft implementation by Google. It's too bad that many sellers, for whatever reason, don't do it before selling.

I can enter the full OS, but can not enable ADB nor add a new account. Any insight?

Bypass tut not tested on Android 7 but works on marshmallow
https://www.youtube.com/watch?v=7OldC6kzuYk
http://rootjunkysdl.com/files/Apps/FRP/com.rootjunky.frpbypass-1.0.apk

*$M3RT$* said:
Bypass tut not tested on Android 7
https://www.youtube.com/watch?v=7OldC6kzuYk
http://rootjunkysdl.com/files/Apps/FRP/com.rootjunky.frpbypass-1.0.apk
Click to expand...
Click to collapse
Scary, but the logic makes perfect sense. I can see it being very useful for honest people.

josiedalek said:
Hey guys, new here, sorry can't post in recoveries section.
I recently bought a Pixel off ebay and the guy that sold it to me bought it off Gumtree. The original seller left all his stuff on it and the guy i bought it off couldn't even access the phone because it had a passcode lock on it. He tried contacting the owner but he never responded (yayyy).
Then there's me, because I'm smart and was like I CAN JUST FACTORY RESET IT, which kicked in the FRP. Unfortunately Google has had fun developing this phone to be super secure and although I no longer have a passcode to worry about, I can't bypass the FRP and I don't know the original owner's account details.
Here's some details:
USB Debugging is OFF
Only option I have on ADB is sideload
Bootloader is LOCKED
Phone is NOT ROOTED
Currently running 7.1.1
Phone is CARRIER unlocked (I can receive calls and use my data when trying to log into my gmail, which doesnt work because I have to use original account).
Is there any solution to bypass this? Much appreciated. I tried to go through google because I bought the phone off ebay and so the FRP prevents them as I didn't buy it directly off google. Am trying to track down the original owners details via my ebay seller to hopefully force the owner to comply. Any way I can get around this would be amazing.
Click to expand...
Click to collapse
I came up with a way to remove FRP for this device. I currently have the only video up on youtube so it should be easy to find. I cant post links yet so just search google or youtube for "google pixel frp bypass" and it will come up. It involves the use of a USB-C OTG adapter and the dirtycow exploit. It actually works for a truly universal frp bypass for every device vulnerable to the device. The entire process is done on a bootloader locked, usb debugging off, no internet connection and no other device (besides the usb). Enjoy, it took me weeks to figure it out lol.

trjv said:
I came up with a way to remove FRP for this device. I currently have the only video up on youtube so it should be easy to find. I cant post links yet so just search google or youtube for "google pixel frp bypass" and it will come up. It involves the use of a USB-C OTG adapter and the dirtycow exploit. It actually works for a truly universal frp bypass for every device vulnerable to the device. The entire process is done on a bootloader locked, usb debugging off, no internet connection and no other device (besides the usb). Enjoy, it took me weeks to figure it out lol.
Click to expand...
Click to collapse
I'm curious to see if the OP will have luck with this

magnumtripod said:
I'm curious to see if the OP will have luck with this
Click to expand...
Click to collapse
I posted this in the dirtycow forums section but I figure it has relevance here as well. Sorry if this is considered double posting.
This method wont help you to root the device, just to bypass FRP. Since dirtycow doesn't persist after a reboot (I think) it wont help as far as gaining root. However it will help you to modify files on the device. I also realized that it only has the power to overwrite files that the current user has read access to, despite whether the filesystem is mounted read-only. With this in mind I was looking over my Nexus 6P and checking to see which files had read access as user and realized that GoogleLoginService.apk and GoogleLoginService.odex both fall under this category. The files are located at /system/priv-app/GoogleLoginService and associate with Google Account Manager when installed as a system app. When the data is corrupted you can install Google Account Manager as a user app, which changes the location and file names to /data/app/com.google.gsf.login-1/base.apk and base.odex. If you corrupt these files at this point then try to disable and uninstall and select replace with the factory version it wont have anything to "replace with the factory version" and tell you that uninstall failed. Once this happens you can reinstall GoogleAccountManager.apk which will again install as a user app, which will then let you perform a full successful uninstall of Google Account Manager. At this point you have full control to be able to downgrade to a previous version of Google Account Manager without it telling you that "data is corrupted" and from there perform the web sign in activity. I've tested on multiple devices and multiple versions and this works on every single device on every version of Android including the latest 7.1.1 as long as it is not on the most recent December 5 2016 security patch since dirtycow was removed with those updates.

trjv said:
I posted this in the dirtycow forums section but I figure it has relevance here as well. Sorry if this is considered double posting.
This method wont help you to root the device, just to bypass FRP. Since dirtycow doesn't persist after a reboot (I think) it wont help as far as gaining root. However it will help you to modify files on the device. I also realized that it only has the power to overwrite files that the current user has read access to, despite whether the filesystem is mounted read-only. With this in mind I was looking over my Nexus 6P and checking to see which files had read access as user and realized that GoogleLoginService.apk and GoogleLoginService.odex both fall under this category. The files are located at /system/priv-app/GoogleLoginService and associate with Google Account Manager when installed as a system app. When the data is corrupted you can install Google Account Manager as a user app, which changes the location and file names to /data/app/com.google.gsf.login-1/base.apk and base.odex. If you corrupt these files at this point then try to disable and uninstall and select replace with the factory version it wont have anything to "replace with the factory version" and tell you that uninstall failed. Once this happens you can reinstall GoogleAccountManager.apk which will again install as a user app, which will then let you perform a full successful uninstall of Google Account Manager. At this point you have full control to be able to downgrade to a previous version of Google Account Manager without it telling you that "data is corrupted" and from there perform the web sign in activity. I've tested on multiple devices and multiple versions and this works on every single device on every version of Android including the latest 7.1.1 as long as it is not on the most recent December 5 2016 security patch since dirtycow was removed with those updates.
Click to expand...
Click to collapse
Yeah so I'm Zhythe on YouTube I was actually already talking to you on there before I checked this thread. I have Dec 5 security patch is there anything you can do to get around it that doesn't involve dirtycow? :/

josiedalek said:
Yeah so I'm Zhythe on YouTube I was actually already talking to you on there before I checked this thread. I have Dec 5 security patch is there anything you can do to get around it that doesn't involve dirtycow? :/
Click to expand...
Click to collapse
oh hey whats up! nice to see you here as well im still trying to fix my pixel since it bricked when trying to update it haha. Been a little distracted though this morning since phonlab hase stolen my method and now he and rootjunky are passing it off as if they found it first without giving me credit for it and charging to teach the method. serious backstabbing right there. but once i get this pixel up and running again i'll find a method and host it from my website so no copycats rip me off.

trjv said:
oh hey whats up! nice to see you here as well im still trying to fix my pixel since it bricked when trying to update it haha. Been a little distracted though this morning since phonlab hase stolen my method and now he and rootjunky are passing it off as if they found it first without giving me credit for it and charging to teach the method. serious backstabbing right there. but once i get this pixel up and running again i'll find a method and host it from my website so no copycats rip me off.
Click to expand...
Click to collapse
Hey! Yeah that's such a dog move by both of them seriously... not cool. No worries I'll keep an eye on your website for updates Best of luck!

Check this out!!

See what I mean? Haha idk why I ever wanted to be a part of this place anyways lol. Nothin but disrespect since the moment I posted the method.

trjv said:
See what I mean? Haha idk why I ever wanted to be a part of this place anyways lol. Nothin but disrespect since the moment I posted the method.
Click to expand...
Click to collapse
Yeah I totally ignored it :/ dw you're so much better and obviously smarter cause you did it before them

NBreunig3 said:
Check this out!!
Click to expand...
Click to collapse
Hi @NBreunig3!
trjv said:
See what I mean? Haha idk why I ever wanted to be a part of this place anyways lol. Nothin but disrespect since the moment I posted the method.
Click to expand...
Click to collapse
You could report that YouTube video and show/link to your source of where you first posted the method. Get them to take them down!

Frp google pixel
can be reseted with XTC2CLIP if u have unlocked bootloader i tested on my device.

warrior26ro said:
can be reseted with XTC2CLIP if u have unlocked bootloader i tested on my device.
Click to expand...
Click to collapse
@warrior26ro I stated clearly the bootloader was locked. XTC2CLIP is also for HTCs. Please don't post unless you've read the question properly.

Technically the Google Pixel is an HTC device since they are the manufacturers of them. Not that that helps the situation any more or less to know just figured I'd mention it lol. You can even issue some proprietary HTC fastboot commands on Pixel devices, but I haven't gotten them to do anything special from using them. Commands such as fastboot oem rebootRUU makes the phone reboot but not into anything special that I've noticed, just reboots the phone. I'm sure there are others but that one in particular is definitely HTC only lol.
On a side note I'm still diligently working on a method for the newer devices every day. It's only a matter of time before I get it lol. While on the subject at least here's a couple thoughts if anybody has any insight...
I've been looking at other binary commands to gain a foothold of, sort of like the whole idea behind run-as that the dirtycow peeps use. After installing Nethunter on my 6P I noticed that there is another command with potential privilege abuse called "procmem". It doesn't need superuser privileges to use nor does it only respond to ROOT or SHELL users, so its basically universally allowed from "untrusted app" users (i.e. termux, terminal emulator, material terminal, etc.). The only thing is that I'm pretty sure that command is only installed with a proper busybox installation, and further it only has the proper setuid bit needed + standard user permissions (that I've seen) when installed into /system/xbin. So basically my idea is to leverage a modified procmem binary to gain (insert something here) that might lead to (insert something else here) lol. Not really a whole plan but I figure if I can find a way to get procmem into /system/xbin on a non-rooted device then at least I have something to work with lol. Otherwise I've also been looking into a way to become SHELL user without using "adb shell". I know that with the Moto 360 there was some fancy adb command to enable native adb support but I can't seem to remember how to go about it. So yeah, thats all I've got so far lol.

Google Factory Reset Protection & used phones

Hi all,
I'm a bit confused at the moment.
My mum dropped her phone and needs a new one. I was able to retrieve all her data and would also like to set up a device for her with a minimal custom rom, etc.
Now, she doesn't have a lot to spend on a phone, so the logical decision would be to get a good used device. That's when I learned of FRP. However, I'm unsure how exactly it works.
Is there any way to get around it, at all, without having the Google account data? (And without sending it to the manufacturer, as that would surely raise the costs, making it pointless.)
I've read on a few threads that it's possible to re-flash the stock firmware, but then someone wrote that the account still was needed to install custom roms.
Is this heavily dependent on the device or are there some general rules to follow?

NovusDeus said:
Hi all,
I'm a bit confused at the moment.
My mum dropped her phone and needs a new one. I was able to retrieve all her data and would also like to set up a device for her with a minimal custom rom, etc.
Now, she doesn't have a lot to spend on a phone, so the logical decision would be to get a good used device. That's when I learned of FRP. However, I'm unsure how exactly it works.
Is there any way to get around it, at all, without having the Google account data? (And without sending it to the manufacturer, as that would surely raise the costs, making it pointless.)
I've read on a few threads that it's possible to re-flash the stock firmware, but then someone wrote that the account still was needed to install custom roms.
Is this heavily dependent on the device or are there some general rules to follow?
Click to expand...
Click to collapse
FRP isn't an issue if the device is properly reset, many people don't.
FRP on most Android devices can be bypassed, just do a search on YouTube for FRP, the device and current Android version.
Best to ask the seller if the device is FRP locked before buying.
Sent from my Moto E (4) using Tapatalk

The problem is that most sellers don't seem to even know about this, as it's done automatically opt-out (I didn't either, but my phone is already older than Android 5 and I've just used it with Lineage all the time and didn't bother).
I've talked to a handful of sellers online now and asked them if their accounts were removed, but they always just reply with "sure, the phone is factory reset", then you have to explain to them what FRP even is and why they need to check manually. Some didn't even respond after that yet, one still didn't fully get my issue. It's a complete mess, I just wanted to buy a used phone for my mum.
sd_shadow said:
FRP on most Android devices can be bypassed, just do a search on YouTube for FRP, the device and current Android version.
Click to expand...
Click to collapse
Thanks for the hint, I didn't even consider looking on Youtube. I've had a quick search and I can see that it's easier to show the instructions that way, so no wonder I haven't found much concrete info.
However most I've seen just replace the Google account with their own one. I presume you would swap out the account with your own, then disable FRP and delete the account? Does that work?
My mum doesn't have a Google account, I have one, but I don't really want it sitting on there. I didn't even plan on installing any Google services to begin with..

Accessing a deceased person's locked phone (Android 6, ZTE Blade V770/Orange Neva 80)

Hello all from a noob on the forum,
I have a very specific use case: I want to access the content of the internal memory of my recently deceased father's phone. We'd like to get the photos, messages, anything personal that might be worth storing elsewhere.
The is a ZTE BLade V770 (branded as Orange Neva 80 in France), it runs Android 6.0.1. When I got hold of the phone if was already turned off, and of course not rooted. The developer mode is not activated either.
I want to access the content of the phone memory. Obviously I could get the content of the external SD card easily and I also managed to reinitialize the PIN code for the SIM card through the PUK code. But now the phone asks for the phone code, which is a PIN code. I tried many codes that I know he used but unfortunately it seems that there is a limited number of tries at it is now saying I have only a few tries left before it erases all data.
I do have access to the Google account used by the phone but it seems that I can't reinitialize the code from the Google account site. And I did not find a way to access the backup on Google site, it seems to be available only from the phone that made it.
Basically I have a full physical access to the phone and also the google and operator's accounts, I just miss the lock code.
I googled around and tried to find information in the forum but I am not an Android expert and this is not a simple use case.
I can boot into recovery mode but that only allows me a factory reset which I don't want.
I read that some versions of Android (5 ?) have some kind of buffer overflow exploit in the form for the PIN but that does not work.
I also read that after a few tries the phone could ask to unlock by using the google account, but the phone never prompted that after my many tries. Or it did and I missed it and now it's too late.
It seems that the code could be reinitialized by removing some file in /data, but as the phone is not started I can't connect using adb. And in recovery mode this does not seem possible.
What I want is to find a way to bypass/replace/erase the locking code so I can have access to the content of the internal memory of the phone.
Any help appreciated !

gfraysse said:
Hello all from a noob on the forum,
I have a very specific use case: I want to access the content of the internal memory of my recently deceased father's phone. We'd like to get the photos, messages, anything
...
What I want is to find a way to bypass/replace/erase the locking code so I can have access to the content of the internal memory of the phone.
Any help appreciated !
Click to expand...
Click to collapse
Hi,
You're in a uncomfortable situation, because what may have allowed us to bypass the phone's password is root. Unfortunately developer options aren't enable so we're stuck here...
But if you have another phone, you can try sign-in to his Google account on the phone, and see if he has a Google drive backups. Usually those G-Drive backups can't be opened like that, but can be restored to a new device.
Give it a try
Also, toutes mes condoléances pour votre père

gfraysse said:
Hello all from a noob on the forum,
I have a very specific use case: I want to access the content of the internal memory of my recently deceased father's phone. We'd like to get the photos, messages, anything personal that might be worth storing elsewhere.
The is a ZTE BLade V770 (branded as Orange Neva 80 in France), it runs Android 6.0.1. When I got hold of the phone if was already turned off, and of course not rooted. The developer mode is not activated either.
I want to access the content of the phone memory. Obviously I could get the content of the external SD card easily and I also managed to reinitialize the PIN code for the SIM card through the PUK code. But now the phone asks for the phone code, which is a PIN code. I tried many codes that I know he used but unfortunately it seems that there is a limited number of tries at it is now saying I have only a few tries left before it erases all data.
I do have access to the Google account used by the phone but it seems that I can't reinitialize the code from the Google account site. And I did not find a way to access the backup on Google site, it seems to be available only from the phone that made it.
Basically I have a full physical access to the phone and also the google and operator's accounts, I just miss the lock code.
I googled around and tried to find information in the forum but I am not an Android expert and this is not a simple use case.
I can boot into recovery mode but that only allows me a factory reset which I don't want.
I read that some versions of Android (5 ?) have some kind of buffer overflow exploit in the form for the PIN but that does not work.
I also read that after a few tries the phone could ask to unlock by using the google account, but the phone never prompted that after my many tries. Or it did and I missed it and now it's too late.
It seems that the code could be reinitialized by removing some file in /data, but as the phone is not started I can't connect using adb. And in recovery mode this does not seem possible.
What I want is to find a way to bypass/replace/erase the locking code so I can have access to the content of the internal memory of the phone.
Any help appreciated !
Click to expand...
Click to collapse
I sympathize with you, I know what it means to lose a father and I know you just want to hold on to whatever you can from your father..
But......
Unfortunately, the XDA rules prevent us from helping you bypass the PIN on a device that you don't own. It is a privacy/legality issue and XDA prefers not getting involved with privacy and legal issues, anything that is illegal does not get discussed here. We have no way of knowing if you are telling the truth, we have to take your word for it, for all we know, the device could actually be your girlfriend's phone or any number of scenarios where the phone isn't yours and we couldn't help in any of those scenarios because the device/data is not yours.
The reason we can't discuss it, even if you are telling the truth, is because even though your intentions would be legitimate, anything we told you that helped you break into the phone could be used by others that have nefarious purposes.
Yes, I know there are other discussions on XDA involving this subject, but, even in those cases, the members here should not have offered information that allows someone to unlock a phone that isn't theirs.
Even though they may have felt like were trying to help or do the right thing, the other member @Raiz should not have attempted to help you gain access to the data on the device.
I do wish you luck though.
Sent from my SM-S767VL using Tapatalk

@Droidriven: Thank you for your detailed answer. I understand your point from the XDA point of view: the use case is technically almost identical to accessing any phone without the person's permission. However it is a valid and painful use case and if there was a legit process at Google or ZTE (the manufacturer) for example to unlock phones in this situation there is official paperwork to prove it. Apart from technical solutions that are in a grey area, it should be possible for people on the forum to point out, as @Raiz did, to try legit solutions that could help in this situation.
I unfortunately understand between the lines that no such legit process exists. Otherwise someone would probably have pointed me to it.
@Raiz: merci and thank you for your answer. I did try after your suggestion to reset another phone and initialize it with his Google account. But it did not restore anything to the new phone. I also realized that it is possible to see the content of a Google backup from Google Drive itself. I realized that the backup was a few months old and that few things were indeed backed-up. So the data are only in the phone.

gfraysse said:
@Droidriven: Thank you for your detailed answer. I understand your point from the XDA point of view: the use case is technically almost identical to accessing any phone without the person's permission. However it is a valid and painful use case and if there was a legit process at Google or ZTE (the manufacturer) for example to unlock phones in this situation there is official paperwork to prove it. Apart from technical solutions that are in a grey area, it should be possible for people on the forum to point out, as @Raiz did, to try legit solutions that could help in this situation.
I unfortunately understand between the lines that no such legit process exists. Otherwise someone would probably have pointed me to it.
@Raiz: merci and thank you for your answer. I did try after your suggestion to reset another phone and initialize it with his Google account. But it did not restore anything to the new phone. I also realized that it is possible to see the content of a Google backup from Google Drive itself. I realized that the backup was a few months old and that few things were indeed backed-up. So the data are only in the phone.
Click to expand...
Click to collapse
One way to bend the rules and help while at the same time, keep the information from being available to whoever wants to see, is to reply with suggestions via PM.
And yes, it is a grey area and people do make posts to help in these situations.
But, in the grand scheme, there is that wild scenario hanging out in limbo that comes to the forums, gets answers/help cracking a phone, then explodes into a legal case with people coming looking for all parties involved with and have knowledge of the device being cracked/invaded. A very bad situation for XDA and the members that provided the help. There is no way of knowing which scenarios are threats or not.
Just saying.
Sent from my SM-S767VL using Tapatalk

i dont understand what this means

had this same problem now for a while but cant sort it . so i got in toutch with samsung. the problem is i have no play store on my phone . had to send samsung reports on my phone . and this is the responce i got as pictured below

tazzuk2020 said:
had this same problem now for a while but cant sort it . so i got in toutch with samsung. the problem is i have no play store on my phone . had to send samsung reports on my phone . and this is the responce i got as pictured below
Click to expand...
Click to collapse
Try using fdroid and aroura store

Nameless Foe said:
Try using fdroid and aroura store
Click to expand...
Click to collapse
yeah thats fine but i still want to know what the issue is

tazzuk2020 said:
yeah thats fine but i still want to know what the issue is
Click to expand...
Click to collapse
Tbh, im not sure about whats going on there... I have personally never seen that before. Hopefully someone will stumble across and have the answer. Good Luck!

Nameless Foe said:
Tbh, im not sure about whats going on there... I have personally never seen that before. Hopefully someone will stumble across and have the answer. Good Luck!
Click to expand...
Click to collapse
Ok thanks anyway

Someone here knows about this but not me. Couldn't find much about it;
App installation | Knox SDK
Samsung tech support sucks.
Sounds like a Knox issue. Somethings not configured correctly or got corrupted.
Did Playstore ever work?
Is the phone a carrier one? Carrier tech support can be much better than Samsung's if you get a knowledgeable tech.
Try deleting your Goggle account(s), full nuke them, then recreate your primary account.
Clear Playstore and Goggle Play Services app data.
Do not have any disabled or Firewall blocked, Android, Google apks for now.
Reboot and clear system cache on the boot menu (NOT a hard reset!).
Try again, reboot if it fails.
Make sure the Goggle account is working correctly; trying using gmail.
Reboots are generally needed after you correct the issue for Playstore, it's a pain.
You can try a hard reboot (NOT reset!) but doubt this will help.
A hard reset (factory reset) may get it but it could reoccur so try to find the root cause.
If it's a none stock configuration or rooted phone you'll need advance help from XDA members who play with these issues for fun, giggles and to learn new curse words. Lol, I haven't as yet... I already curse like a Nam Vet
If you don't find a solution bump this thread each day as needed. Be patient as their is a wealth of knowledge here within the site's members.

blackhawk said:
Someone here knows about this but not me. Couldn't find much about it;
App installation | Knox SDK
Samsung tech support sucks.
Sounds like a Knox issue. Somethings not configured correctly or got corrupted.
Did Playstore ever work?
Is the phone a carrier one? Carrier tech support can be much better than Samsung's if you get a knowledgeable tech.
Try deleting your Goggle account(s), full nuke them, then recreate your primary account.
Clear Playstore and Goggle Play Services app data.
Do not have any disabled or Firewall blocked, Android, Google apks for now.
Reboot and clear system cache on the boot menu (NOT a hard reset!).
Try again, reboot if it fails.
Make sure the Goggle account is working correctly; trying using gmail.
Reboots are generally needed after you correct the issue for Playstore, it's a pain.
You can try a hard reboot (NOT reset!) but doubt this will help.
A hard reset (factory reset) may get it but it could reoccur so try to find the root cause.
If it's a none stock configuration or rooted phone you'll need advance help from XDA members who play with these issues for fun, giggles and to learn new curse words. Lol, I haven't as yet... I already curse like a Nam Vet
If you don't find a solution bump this thread each day as needed. Be patient as their is a wealth of knowledge here within the site's members.
Click to expand...
Click to collapse
The phone is not rooted. I’m not getting options to factory reset . I’m not really clued up very much thf

tazzuk2020 said:
The phone is not rooted. I’m not getting options to factory reset . I’m not really clued up very much thf
Click to expand...
Click to collapse
Try what I suggested. Recreating your Google account will most likely fix it. Learn by doing.
Play with it. The stock Android OS are pretty much impossible to damage short of bad 3rd party apps. The more you play with it, the more you learn. Make sure all your critical data is completely backed up*; be prepared for a reload at any time to prevent data loss.
If you need to download apps from Playstore now and have a device that can connect to Playstore do this. Install the apps you want on that device then use ApkExport to copy those apps then transfer and install on the troubled device
APK Export (Backup & Share) - Apps on Google Play
Manage and extract your apps.
play.google.com
Google how to bring up the boot menu on your model. The clear system cache option is found there; it can cure many erratic behavior issues.
The hard reboot is a different key sequence, Google for that model.
Do not do a factory reset until you exhaust all other solutions if the load is still fresh and no viruses are present otherwise it's a waste of time.
If you feel you have no other solutions you can use it, but if it doesn't fix it or it reoccurs you'll be right back where you started.
Contact your carrier tech support, ask to talk to advanced tech support, escalate your case if need be. They will likely be more helpful than Samsung. Remember a tech that tells you nothing but to do a factory reset isn't giving you tech support. It's the easiest solution for them, not you!!!
Note: if it's an old OS load by all means punch in a fresh copy though; after a year or so, or any major firmware update a factory reload is good practice.
*back up to SD card if you have one and/or your PC. Back that PC copy up on at least one stand alone hdd. Develop a complete back up plan before you need it.

blackhawk said:
Try what I suggested. Recreating your Google account will most likely fix it. Learn by doing.
Play with it. The stock Android OS are pretty much impossible to damage short of bad 3rd party apps. The more you play with it, the more you learn. Make sure all your critical data is completely backed up*; be prepared for a reload at any time to prevent data loss.
If you need to download apps from Playstore now and have a device that can connect to Playstore do this. Install the apps you want on that device then use ApkExport to copy those apps then transfer and install on the troubled device
APK Export (Backup & Share) - Apps on Google Play
Manage and extract your apps.
play.google.com
Google how to bring up the boot menu on your model. The clear system cache option is found there; it can cure many erratic behavior issues.
The hard reboot is a different key sequence, Google for that model.
Do not do a factory reset until you exhaust all other solutions if the load is still fresh and no viruses are present otherwise it's a waste of time.
If you feel you have no other solutions you can use it, but if it doesn't fix it or it reoccurs you'll be right back where you started.
Contact your carrier tech support, ask to talk to advanced tech support, escalate your case if need be. They will likely be more helpful than Samsung. Remember a tech that tells you nothing but to do a factory reset isn't giving you tech support. It's the easiest solution for them, not you!!!
Note: if it's an old OS load by all means punch in a fresh copy though; after a year or so, or any major firmware update a factory reload is good practice.
*back up to SD card if you have one and/or your PC. Back that PC copy up on at least one stand alone hdd. Develop a complete back up plan before you need it.
Click to expand...
Click to collapse
i cleared system cache. done a hard reboot. still the same . cant even find the option to do a factory reset. im not worried about backing phone up. the phone is a samsung a51. i have got another firmware downloading as we talk im not convinced its going to sort the problem

tazzuk2020 said:
i cleared system cache. done a hard reboot. still the same . cant even find the option to do a factory reset. im not worried about backing phone up. the phone is a samsung a51. i have got another firmware downloading as we talk im not convinced its going to sort the problem
Click to expand...
Click to collapse
Google it for that model. It's should be on the boot menu though. Also in settings as well.
I don't know what to say. This isn't that hard... small steps first.
I was completely PC illiterate 16 years ago. Was building up custom machines within the first year and probably crashed 50 or more XP loads, lol.
I was completely Android illiterate 6 years ago.
I'm 63 yo...
I have done little coding but you need to acquire a certain level of wherewithal to use PCs/Androids well, to keep them and your data secure.
You learn by doing and the Android OS is far easier to learn than XP or XPx64.
If you don't immerse yourself in it you will not learn.
It's fun to play with.
Explore it, play with it... you can't cause any permanent harm to a stock Android. You will occasionally need to undo a setting(s) change you made that may soak up a lot of time tracking it down but that's how you learn.
Go through all the settings and learn what they do.
Turn on Developer Options, play with it.
Google for the answers as your questions arise.
I'm constantly learning by doing that not just for Androids but a broad range of topics.
Lol, the internet is a whole pseudo library at your fingertips. Pretty cool.

blackhawk said:
Google it for that model. It's should be on the boot menu though. Also in settings as well.
I don't know what to say. This isn't that hard... small steps first.
I was completely PC illiterate 16 years ago. Was building up custom machines within the first year and probably crashed 50 or more XP loads, lol.
I was completely Android illiterate 6 years ago.
I'm 63 yo...
I have done little coding but you need to acquire a certain level of wherewithal to use PCs/Androids well, to keep them and your data secure.
You learn by doing and the Android OS is far easier to learn than XP or XPx64.
If you don't immerse yourself in it you will not learn.
It's fun to play with.
Explore it, play with it... you can't cause any permanent harm to a stock Android. You will occasionally need to undo a setting(s) change you made that may soak up a lot of time tracking it down but that's how you learn.
Go through all the settings and learn what they do.
Turn on Developer Options, play with it.
Google for the answers as your questions arise.
I'm constantly learning by doing that not just for Androids but a broad range of topics.
Lol, the internet is a whole pseudo library at your fingertips. Pretty cool.
Click to expand...
Click to collapse
No factory reset on boot menu. And nowhere to be seen on phone. I even typed it in to search bar on phone . Maybe this is all linked. Only option I have is to reinstall the firmware I have got downloading but that won’t be finished for a few hours

You should be able to factory reset from recovery. Google how to boot to recovery for your device

xunholyx said:
You should be able to factory reset from recovery. Google how to boot to recovery for your device
Click to expand...
Click to collapse
Nothing from boot menu.

tazzuk2020 said:
Nothing from boot menu.View attachment 5212005
Click to expand...
Click to collapse
Part of the reason I left Samsung years ago. They do stuff different than any other OEM. You can't even use fastboot commands ffs

xunholyx said:
Part of the reason I left Samsung years ago. They do stuff different than any other OEM. You can't even use fastboot commands ffs
Click to expand...
Click to collapse
i got a feeling its to do with knox. is there anything i can do about this . i brought the phone 2nd hand. the phone works perfect apart from play store

Question FRP Lock on A22 5G

Hi folks,
a family friend inherited an A22 from a deceased friend, but she did not have the password for it.
As I had never heard of FRP before, I advised her to reset the phone, which is how the FRP took effect. I now feel guilty for giving obviously wrong advice and would like to fix it.
I guess there is no proof of purchase for the phone anymore and all the passwords from the documents didn't work. A Vodafone employee advised me to scrap the phone, but I don't think so.
I found the software "**** your FRP" here in the forum and tried it, but the A22 is not on the list of Knox-compatible devices. Therefore, the code #*0#* does not work either and I can't get any further.
I got a little further with the talkback function. I was able to open the Google Assistant and navigate to Chrome or the settings. Unfortunately, I could not activate the developer options, couldn't navigate to the app settings or allow the installation of apps from unknown sources.
After about 8 hours and several attempts, I am at my wit's end. I have the deceased's email address and name. Unfortunately, this was not enough to reset the password. If I am informed correctly, his number has also been deactivated, so I can no longer receive SMS. I don't have the SIM card either, but I might be able to get it.
I hope you guys can help me.
Best regards,
Felix

Contact Samsung service / a phone service.
You could so it yourself, but the time needed will be too much

As I said, the people at Vodafone said you can only scrap it. I had read that you can get the device unlocked with the help of the proof of purchase, but no one knows exactly where the receipt could be.
dotuletz said:
You could so it yourself, but the time needed will be too much
Click to expand...
Click to collapse
I'm not in a hurry, I'm just looking for a tool to do this with, or instructions on how to bypass the FRP.
I can forget Google, as 99% of the results are scam and the remaining 1% did not work.

Ive heard that YouTube has just the right type of guide for almost exactly those probs, and by all accounts very very simple to follow, as I did recently on my sister's device she left at home, no longer wanted, ditched for an apple contraption. I will add, no one with nefarious reasons, stolen devices should use the helpful tools there. Getting a job and buying a device the bloody deviants should....damn the swines.

ianreesdavies said:
Ive heard that YouTube has just the right type of guide for almost exactly those probs, and by all accounts very very simple to follow, as I did recently on my sister's device she left at home, no longer wanted, ditched for an apple contraption. I will add, no one with nefarious reasons, stolen devices should use the helpful tools there. Getting a job and buying a device the bloody deviants should....damn the swines.
Click to expand...
Click to collapse
The problem with YouTube videos is that Samsung (and pretty much every other major manufacturer) has teams of employees whose sole job is to look through the internet for how-to videos and posts, make a note of how the trick/bypass works, and submit it to the software development team to be fixed in the very next update. That's why the how-to videos are full of comments saying "this didn't work for me" or "I don't have that option on my device".
There's a professional 3rd party business that I've used for things like this before. Discussion of paid services isn't allowed in the forums, but anyone who wants a recommendation can DM me

I completely agree mate, it's hit and miss, there are plenty of other sources out there. Just coincidentally, I found myself reading a comment that was the exact situation I was in yesterday. Obviously, not wanting the member to be struggling I gently nudged him towards a simple and 100% idiot's guide that will put him right. Admittedly a large majority of these things are countered/blocked or absolute bollox as I have encountered many times lmfao

BooWseR said:
Hi folks,
a family friend inherited an A22 from a deceased friend, but she did not have the password for it.
As I had never heard of FRP before, I advised her to reset the phone, which is how the FRP took effect. I now feel guilty for giving obviously wrong advice and would like to fix it.
I guess there is no proof of purchase for the phone anymore and all the passwords from the documents didn't work. A Vodafone employee advised me to scrap the phone, but I don't think so.
I found the software "**** your FRP" here in the forum and tried it, but the A22 is not on the list of Knox-compatible devices. Therefore, the code #*0#* does not work either and I can't get any further.
I got a little further with the talkback function. I was able to open the Google Assistant and navigate to Chrome or the settings. Unfortunately, I could not activate the developer options, couldn't navigate to the app settings or allow the installation of apps from unknown sources.
After about 8 hours and several attempts, I am at my wit's end. I have the deceased's email address and name. Unfortunately, this was not enough to reset the password. If I am informed correctly, his number has also been deactivated, so I can no longer receive SMS. I don't have the SIM card either, but I might be able to get it.
I hope you guys can help me.
Best regards,
Felix
Click to expand...
Click to collapse
Also mate, getting to chrome is most of it done. 4 files to download, 2 through the galaxy store which allows them to install, then through those, sorry, plus ios14 launcher allows you to activate unknown sources etc..it's not difficult. Worked like a charm. Just find the Samsung a22 5g frp unlock, activate unknown sources how to.