Hi,
I wanted to give an old phone to my son and upgrade to OS to Lineage 14 from stock.
I flashed the original rom, and it asks for google account verification, where I log in as my son's account (with me as the parent, because it needs family link). All is fine at this point, I can do that and restart the phone just fine.
I remove his account so I can enable OEM unlock then I flash TWRP and install Lineage OS. So far so good.
But when I install Gapps, and log in as my son into his google account on Lineage, the next restart says the phone is FRP locked, and can't boot, not even to recovery.
Lineage doesn't have OEM unlock.
It's a galaxy j3 2016 j320F.
I feel like I'm missing just one step that I can't figure out.
As soon as I logged in with a google child account, on the next restart the phone wouldn't start, not even to recovery.
I ended up creating an adult google account for my son and with that, it works just fine.
Related
He guys,
I have a serious problem with my SM-G531f model phone on 5.1.1. I've rooted the phone and made sure that I booted stock, after wipe/factory reset and having ticked the box that says that it may be unlocked for OEM under development, I even unticked the box for checking the apps through usb. Of course I didn't make a Google-account at that point and disabled the Samsung account. Then again, when I'm done rooting the phone, and after I added the Google-account, I can't go back to TWRP because of this error with the FRP blocking custom binary.
I've tried many times now, and still this message keeps popping up. I don't know what to do anymore about this.
Anyone knows what I'm doing wrong or any advise on how to keep this error-message at bay?
Thanks!
And the solution is as simple as can be. Remove Google account and then reboot into TWRP. After installing whatever it is you want to do in Recovery simply reinstall Google account and let it sync. No more binary blocked by FRP.
mhadjih said:
And the solution is as simple as can be. Remove Google account and then reboot into TWRP. After installing whatever it is you want to do in Recovery simply reinstall Google account and let it sync. No more binary blocked by FRP.
Click to expand...
Click to collapse
I join this old thread because I got the same issue on a Samsung Grand Prime. Do you confirm that the issue is solved by installing TWRP and rooting with no Google account active?
Thank you
Aldo
you must reflash stock rom before do anything
hi i removed google account using 2 ways
first one https://www.youtube.com/watch?v=baa8vdiIf84&t=187s
second https://www.youtube.com/watch?v=uYu1h6_2tyE
both ways are tested first one is for ANDROID 5.1.1 and down
second is for android 6 and Up
I sold a nexus 6p online. I shipped it out to the buyer. He received it and he is unable to sign into his account on the phone. It is telling him that it's still attached to my account. I was wondering if there was a way to remotely delete my account so the buyer and sign into it with his account.
mflammger said:
I sold a nexus 6p online. I shipped it out to the buyer. He received it and he is unable to sign into his account on the phone. It is telling him that it's still attached to my account. I was wondering if there was a way to remotely delete my account so the buyer and sign into it with his account.
Click to expand...
Click to collapse
Search google for FRP (factory reset protection).
As far as I know there is no way to do it remotely. I think you should have signed out of your google account before you reset the phone. Most likely he will have to ship it back to you so you can sign in and then remove your account.
Here: https://security.google.com/settings/security/activity?pli=1
But I'm not sure how that will affect the device.
You could always change your password to something stupid for a few seconds for him to sign in and sign out depends how sensitive data you have on your account..
Will Android device manager do it? Will it remotely wipe the phone and remove my account from it, or will it flag the phone as stolen. I cannot get any solid information from repeated Google searches as to what happens after the device is remote wiped.
Android Manager will wipe the device but when it turns on it will ask for any Google account it was bound to before wipe. The other person needs to enter your Gmail account, then his, then you can either change password to your account or wipe it with Device Manager and next time it boots it will accept your account or his (because both were added before wipe).
You can always set a temporary password to your Google account, send it to the buyer and have him log in with his account. After that, you change your password back and voilà.
Is all of this a working protection against simply Fastboot unlocking bootloader, flashing stock image then rebooting into a working phone?
Mangala_Dharma said:
Is all of this a working protection against simply Fastboot unlocking bootloader, flashing stock image then rebooting into a working phone?
Click to expand...
Click to collapse
If the bootloader is currently locked, I believe you would have to go into developer options to enable the OEM unlocking setting... Which you can't get to because of the FRP.
Mangala_Dharma said:
Is all of this a working protection against simply Fastboot unlocking bootloader, flashing stock image then rebooting into a working phone?
Click to expand...
Click to collapse
Unlocking bootloader (OEM unlocking in dev options) deactivates this protection but to do it you still need to get in there somehow and you can't without first logging into a Google account it is currently bound to. And as you probably know without unlocked bootloader you can't flash anything.
And even if he could flash new ROM my friend had bought used Samsung S7 Edge and previous owner also left it locked. You can flash different ROMs with S7 Edge out of the box but the FRP survived several attempts at flashing stock/custom ROMs. We had to use the workaround found here at xda S7 forums.
Thanks for all the info.
I did not unlock the bootloader on the phone. I read a little bit about Factory Reset Protection and the only way around it was to sign in to the phone and then remove your account from the phone. It's something that was new this year for Android devices and I was just unaware of it.
It's actually been around awhile, just not widely implemented. If you remember which monthly security update you last installed, he might be able to get around it. YouTuber root ninja has some videos depending on patch. The one I watched just for kicks (since I'd like my 6P to be protected if lost) was a few months old though.
Sent from my Nexus 6P using Tapatalk
I heard that with a simple factory reset with the stock recovery should remove the account from the phone.
Lol good luck with getting that off remotely it's impossible it's kinda like apple cloud system which is really good.
Just wanted to share that I have working Android Pay with my rooted Nexus 6 XT1003.
Phone Info:
Nexus 6 XT1003
Bought it from ebay for $180 (from China)
Android version: Nougat 7.1.2
LineageOS version: 14.1-20180202-Nightly-shamu
Process:
Unlocked bootloader
Fastboot boot'd latest twrp (no install)
Wiped the phone and installed latest LineageOS from their site + gapps package with twrp
Upon first boot, skipped all account setup and first boot setup
Accessed developer settings and enabled "OEM unlocking"
Back to fastboot boot twrp
Flashed SU package provided by LineageOS
Ran Fastboot OEM lock command
Waited what seemed like 20 minutes for the first boot to complete
Setup phone as normal
Opened Android Pay and added my card
Now a few more details.
Before using this at the store, I enabled root for apps in settings for an app "System app remover (ROOT)" Excellent app, get it here: ( https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp )
After this with root still enabled, went to the store and attempted to pay with Android Pay.... "THIS PHONE CAN NO LONGER BE USED FOR PAYMENTS" - That was a huge let down and I was sad.
I thought right off the bat, DUH! Disable root in developer settings..... no dice, same error.... but my bootloader is locked and root is disabled....
I followed the google message and sent feedback in the app and said "My bootloader is locked and root is disabled"
Now I didn't really expect this to work with Google's security with this service.
I went to the store a few days later with root still disabled, after a reboot or two and tested it... IT WORKED!
I wonder why it didn't work the first time? Maybe because I had not restarted my phone after disabling root? Maybe because I cried to Google? (doubt it)
I'm going to re-enable root at some point and test it out again to see if a simple restart after disabling is what fixes this.
Does Android Pay work for you?
My Android Pay works on current Lineage OS, but I never flashed root. I did install TWRP as normal. Otherwise I did the same as you. (Doesn't help you answer your question, though, sorry.)
I have magisk installed and android pay works fine with it.
OEM unlocked too.
los+magisk 15.3+universal-safetynet-fix-v2-beta-5= work fine
Disabling root access in the developer settings and rebooting worked for me.
I was just wondering. Is there any way to pass frp lock by installing a custom ROM without actually flashing gapps? Leaving the phone only with the ROM's pre-installed apps and downloading Google account manager or a specific frp bypass apk to get into a new account, assuming right now your phone is already connected to a Google account. After, flashing gapps the phone should now work by the Google account that is connected without being frp locked, right? Or there needs certain Google apps to link your account while using the mini frp bypass tool?
And so, if that's working. Could you actually go back to stock with no frp lock?
You don't need any custom rom... Download bypass apk, keep it in pendrive or sd card... Connect via otg, then install that app which will open ur device's settings and reset your device from there... That's all.. You're done ?
Hi everyone, i’m having an extremely weird issue with my Samsung J5 Prime (SM-G570Y/on5xelte). First of all; sorry for bad english, this post will be a bit long.
So i want to unlock OEM, to install custom recovery and custom ROM (and being able to login with google account from gms (Google Play Service app)).
i activate developer options.
Then go to Settings > Developer Options, but OEM Unlock is missing (i did'nt have the screenshot of the settings), i already try every method to reappear it but nothing worked.
Trying my luck, im rebooting my phone to download mode, on there i didn’t see any text that says OEM Unlock, i tried to flash OrangeFox Recovery using ODIN. And suprisingly it worked, i even double-checked it by actually booting to recovery. i did'nt expect it to work though...
Then i install RadicalQuack Custom ROM, and do some root-level customization.
But as soon as i try to login Google account from Google Play Service (this didnt affect web login or any other login) on Stock/Custom ROM, and reboot the phone... my phone was FRP locked, i was shocked because my configuration isn’t even backed up.
I have to flash stock rom in download mode, get to setup, login google, remove the account, then i can get rid of FRP lock.
And at this point is where everything is confusing.
If i use stock rom without any changes, the "OEM Unlock" option is'nt appearing at all.
But if i use custom ROM (in this case i use RadicalQuack), the "OEM Unlock" option Appears (until i remove "ro.frp.pst" in build.prop)
So i can do anything but CANNOT login using Google Account from Google Play Services or get FRP locked and All data destroyed.
Now my question is, is it safe to enable "Unlock OEM"? Because i dont know if OEM Unlock is currently enabled or not, i dont know how to check if the bootloader is actually locked, i dont want to get locked forever on samsung stock and bloated shtt again.
PS:
Somehow... i can login Google account without getting FRP locked by:
Unlocking OEM (on the custom ROM ofcourse, since it won't be visible on stock ROM anyway...)
and removing "ro.frp.pst" (especially "ro.frp.pst=/dev/block/persistent") on /system/build.prop, /system/vendor/build.prop, /vendor/build.prop
what did you do?
Hiii, what did you do? I need to unlock oem un my j5 prime
Same Problem Happens to me But Now How you use custom rom without getting frp lock please Tell I Have Also J5 prime And Same Happens to me also I need to flash stock rom from which my custom rom get erased