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
Related
I recently Hard Reset my Samsung Galaxy Tab A6, SM-T285 through recovery. After booting i cannot sign in to my primary google account because it says "Sign in with a google account that was previously synced on this device". I tried all of my google account
nothing works.
1. Tried Odin Twice with two different version of Firmware
After enabling FRP Lock on Odin, Flashing stuck at "Sending Lock information" and fails
2.Tried Kies3 recovery process
3.Tried to install TWRP using Odin
FRP Lock is still there and i cannot use my phone
Please help me
If the firmware isn't installing it's the wrong one.
You need to go into developer settings and enable OEM UNLOCK.
ashyx said:
If the firmware isn't installing it's the wrong one.
You need to go into developer settings and enable OEM UNLOCK.
Click to expand...
Click to collapse
I cannot enter developer settings because phone requests "Sign in with a google account that was previously synced on this device". Next button is disabled without it.
pradeep.sl said:
I cannot enter developer settings because phone requests "Sign in with a google account that was previously synced on this device". Next button is disabled without it.
Click to expand...
Click to collapse
I would ensure you are using the correct account. My guess is its not.
The Google account will be associated with your device. If it's the correct account then you should be fine.
If you've installed the wrong firmware then Google may see your device as different.
I would sign into your account you think was used on the device via the web then go to Device activity & notifications and ensure your device is listed.
https://accounts.google.com/login
I can see two Devices
1.Samsung Galaxy Tab A6
2.Samsung Galaxy Tab A 7.0 LTE
Mine is Galaxy Tab A6, SM-T285, Recovery email address is correct.
But when i try to login that account on my phone, google says "Sign in with a google account that was previously synced on this device"
Are you not able to wipe data?
ashyx said:
Are you not able to wipe data?
Click to expand...
Click to collapse
I can flash using ODIN but FRP Lock is there
me also faces to this problem too..
already wipe data/factory reset.. account still there .. :crying:
pradeep.sl said:
I can flash using ODIN but FRP Lock is there
Click to expand...
Click to collapse
Try this :
http://www.rootjunky.com/factory-reset-protection/
hi ya
Im sorry I bet this come up a lot..I kind of need to be walked through this, I have some knowledge and disabilities, im good when its broken down and explained or simple logic way,
i have been given 2 tablets from a friend and been told I can keep one if I can fix. I have tried everything,,,
I have little programming knowledge but understand the for if else way of thinking from around 10yrs ago when I studyied at college.
I have tried Hard Reset and blimey its blocked everyway possible.
I can not get into recovery mode nor can I get in safe mode. I tried pluging in usb, sd card and all hard ware buttons are disabled. ive tried pin hole as well as disconnecting the battery and putting it back in..is their away like with pcs motherboard and processer? Although risky?
It has an app appearing to be on the main partition called Fundroid.
I wouldnt mind putting linux on both tbh.
I have photos but can not link them..
HTML:
<img src="https://i.ibb.co/ygsHSth/WP-20190302-07-13-03-Pro.jpg" alt="WP-20190302-07-13-03-Pro" border="0">
<img src="https://i.ibb.co/crDxtBh/WP-20190302-07-13-12-Pro.jpg" alt="WP-20190302-07-13-12-Pro" border="0">
<img src="https://i.ibb.co/KW5bZPW/WP-20190302-07-13-52-Pro.jpg" alt="WP-20190302-07-13-52-Pro" border="0">
<img src="https://i.ibb.co/4Jqg7QC/WP-20190302-07-14-00-Pro.jpg" alt="WP-20190302-07-14-00-Pro" border="0">
<img src="https://i.ibb.co/yPbDHx3/Screenshot-2019-03-02-at-06-04-58.png" alt="Screenshot-2019-03-02-at-06-04-58" border="0">
suzbackwardsbikes said:
Im sorry I bet this come up a lot..I kind of need to be walked through this, I have some knowledge and disabilities, im good when its broken down and explained or simple logic way,
i have been given 2 tablets from a friend and been told I can keep one if I can fix. I have tried everything,,,
I have little programming knowledge but understand the for if else way of thinking from around 10yrs ago when I studyied at college.
I have tried Hard Reset and blimey its blocked everyway possible.
I can not get into recovery mode nor can I get in safe mode. I tried pluging in usb, sd card and all hard ware buttons are disabled. ive tried pin hole as well as disconnecting the battery and putting it back in..is their away like with pcs motherboard and processer? Although risky?
It has an app appearing to be on the main partition called Fundroid.
I wouldnt mind putting linux on both tbh.
I have photos but can not link them..
<img src="https://i.ibb.co/ygsHSth/WP-20190302-07-13-03-Pro.jpg" alt="WP-20190302-07-13-03-Pro" border="0"><img src="https://i.ibb.co/crDxtBh/WP-20190302-07-13-12-Pro.jpg" alt="WP-20190302-07-13-12-Pro" border="0"><img src="https://i.ibb.co/KW5bZPW/WP-20190302-07-13-52-Pro.jpg" alt="WP-20190302-07-13-52-Pro" border="0"><img src="https://i.ibb.co/4Jqg7QC/WP-20190302-07-14-00-Pro.jpg" alt="WP-20190302-07-14-00-Pro" border="0"><img src="https://i.ibb.co/yPbDHx3/Screenshot-2019-03-02-at-06-04-58.png" alt="Screenshot-2019-03-02-at-06-04-58" border="0">
Click to expand...
Click to collapse
Can you reformat those links as they're just html nonsense.
Just post the links.
Also you haven't stated what your issue is?
Hey guys! A friend of mine gave me her old phone (Samsung Grand Prime(SM-G530W)) and I planned to reset it so my Father can have a new phone. Unfortunately, after a hard reset the phone kept asking for the previous gmail account (My friend said it's a very old gmail and have not logged in with it for so long).
So far I have tried to flash 2 stock firmware (both lollipop 5.1.1 and even tried to flash a bell variant firmware) with Odin and no luck so far.
Thanks for the help in advance!
Spin_101 said:
Hey guys! A friend of mine gave me her old phone (Samsung Grand Prime(SM-G530W)) and I planned to reset it so my Father can have a new phone. Unfortunately, after a hard reset the phone kept asking for the previous gmail account (My friend said it's a very old gmail and have not logged in with it for so long).
So far I have tried to flash 2 stock firmware (both lollipop 5.1.1 and even tried to flash a bell variant firmware) with Odin and no luck so far.
Thanks for the help in advance!
Click to expand...
Click to collapse
No compaltion to use old gmail acc. Get a new 1! Till u wanna get any conracts or data back from it
Spin_101 said:
Hey guys! A friend of mine gave me her old phone (Samsung Grand Prime(SM-G530W)) and I planned to reset it so my Father can have a new phone. Unfortunately, after a hard reset the phone kept asking for the previous gmail account (My friend said it's a very old gmail and have not logged in with it for so long).
So far I have tried to flash 2 stock firmware (both lollipop 5.1.1 and even tried to flash a bell variant firmware) with Odin and no luck so far.
Thanks for the help in advance!
Click to expand...
Click to collapse
It doesn't matter how many different versions of firmware you flash. It's a security feature built in to the device to deter theives from stealing it. (Think iCloud lock for Android, similar concept).
There are methods to bypass this but I won't discuss them as I don't know for sure how you came across the phone and don't want to be complicit in theivery, but be sure to check google.
Your best bet at this point is to give your friend some truth serum and torture her for the old password (Or to ask her to initiate password recovery in order to obtain a new password. Please note that after the password has been changed you will have to wait a further 72 hours before accessing the phone.... another google security thing).
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
hackerboy ~AP said:
No compaltion to use old gmail acc. Get a new 1! Till u wanna get any conracts or data back from it
Click to expand...
Click to collapse
Cannot add a new gmail account to the phone unless he is able to access the phone... which he needs the old account information for. The problem is he cannot access the phone because
The phone was already hard reset (No Contacts or Data on the phone, it's been wiped) so this is a mute point.
1- Perform a factory reset using recovery mode
2- when the phone boot up , Connect your phone to a wifi and complete all necessary step until you have to verify your Google account .
3- When you are to the point when you have to verify your account use the the OTG Cable in order to connect your phone to some memory stick which contain the bypass app
4- Navigate to the app and install it .
5- immediately after installing open the app , it will redirect to SETTINGS .
5- open it and navigate to Backup and Reset
6- proceed to the factory reset again
7- choose erase everything
Done
The next time it boot up , Frp should be gone
u0aol said:
It doesn't matter how many different versions of firmware you flash. It's a security feature built in to the device to deter theives from stealing it. (Think iCloud lock for Android, similar concept).
There are methods to bypass this but I won't discuss them as I don't know for sure how you came across the phone and don't want to be complicit in theivery, but be sure to check google.
Your best bet at this point is to give your friend some truth serum and torture her for the old password (Or to ask her to initiate password recovery in order to obtain a new password. Please note that after the password has been changed you will have to wait a further 72 hours before accessing the phone.... another google security thing).
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Cannot add a new gmail account to the phone unless he is able to access the phone... which he needs the old account information for. The problem is he cannot access the phone because
The phone was already hard reset (No Contacts or Data on the phone, it's been wiped) so this is a mute point.
Click to expand...
Click to collapse
Got it bro ty for increasing my knowledge
My method did not work?
downlode Miracle box crack and just press frp remove
all is done
ciel phantomhive said:
1- Perform a factory reset using recovery mode
2- when the phone boot up , Connect your phone to a wifi and complete all necessary step until you have to verify your Google account .
3- When you are to the point when you have to verify your account use the the OTG Cable in order to connect your phone to some memory stick which contain the bypass app
4- Navigate to the app and install it .
5- immediately after installing open the app , it will redirect to SETTINGS .
5- open it and navigate to Backup and Reset
6- proceed to the factory reset again
7- choose erase everything
Done
The next time it boot up , Frp should be gone
Click to expand...
Click to collapse
How do you navigate anywhere without a file browser though? What am I missing? At the point you're asked to sign into the google account there's no option anywhere I can find to navigate anywhere but the password text area
Hey anyone in here able to upload me a good QCN file for this canada model? please?
Spin_101 said:
Hey guys! A friend of mine gave me her old phone (Samsung Grand Prime(SM-G530W)) and I planned to reset it so my Father can have a new phone. Unfortunately, after a hard reset the phone kept asking for the previous gmail account (My friend said it's a very old gmail and have not logged in with it for so long).
So far I have tried to flash 2 stock firmware (both lollipop 5.1.1 and even tried to flash a bell variant firmware) with Odin and no luck so far.
Thanks for the help in advance!
Click to expand...
Click to collapse
Worked for my SM-G530W (Solo Mobile Canada, but has nothing to do with the firmware as is factory unlocked w.w.)
I had the same problem, and i used KIES 3 (not compatible with my phone anyway), but if you go on Kies toolbar to "TOOLS", "Firmware Upgrade and initialisation", it asks you for your device model (for mine i typed SM-G530W, and then it asks you for device serial number (S/N) found under the battery by the IMEI number. After this, follow on screen prompts (Restart your device in Download mode/ PDA, connect USB cable, etc), and let the software download and install (factory rom); After your device restarts, you are good to go (sometimes if it gets stuck on booting, remove battery for fer second and start again.) Now you have to go back and set up everything you want, including re-rooting your device... Good luck. (My device is Galaxy Grand Prime SM-G530W Factory unlocked rom, Android 5.11.
Hi,
I am somewhat in the same boat. My friend's SM-G530W just crashed in her hands, and she ended up buying a new phone. When I got to her place she told me nobody managed to do anything with it, not even her carrier (Telus) , so I said gimme that and i'll see if there really is nothing you can do. Factory reset didn't fix the boot loop , so I grabbed the latest firmware from sammobile and reflashed it using Odin. I didn't even know about FRP until that day. After flashing , the phone came to life.. so I said to myself.. Too easy! .. Then FRP hit me. Because she didn't even understand what a google account is , I ended up resetting her password using her new phone and a google code to change it. Afterwards the phone told me I needed to wait 24h after a password change. It has now been 2 weeks , and same issue. I know I have the right password because if I type another , it tells me wrong password , but when I type the correct one it says to wait 24h, but it never goes beyond that.
I have tried every method possible that I have seen to bypass FRP, including OTG , disconnect wifi during update check, realterm and a few softwares , yet the same problem persist. I also tried Freelancer's tip , but same thing. It still asked for the old account because password was reset, and again tells me to wait 24h because of a password change.
Any more ideas?
SM-G530W Telus
Damn
Out Of all the phones in the world you had to get that one.... that one is impossible to unlock, it uses multiple built-in software and has a glitch in the systems hardware to make it impossible to unlock I have two of them since 2016, december 12th, it is 2017-12-25. and let me tell you I would give anyone 1000$ who ever can prove me wrong... I am very confident that this phone can not be unlocked, it was one of the first phones to use frp and honestly it kinda sucks, I got a samsung galalxy 8s now... perhaps in the distant future someone will unlock this phone.. but ofcourse by then it will be ****...
Working unlock method
Roamin64 said:
Hi,
I am somewhat in the same boat. My friend's SM-G530W just crashed in her hands, and she ended up buying a new phone. When I got to her place she told me nobody managed to do anything with it, not even her carrier (Telus) , so I said gimme that and i'll see if there really is nothing you can do. Factory reset didn't fix the boot loop , so I grabbed the latest firmware from sammobile and reflashed it using Odin. I didn't even know about FRP until that day. After flashing , the phone came to life.. so I said to myself.. Too easy! .. Then FRP hit me. Because she didn't even understand what a google account is , I ended up resetting her password using her new phone and a google code to change it. Afterwards the phone told me I needed to wait 24h after a password change. It has now been 2 weeks , and same issue. I know I have the right password because if I type another , it tells me wrong password , but when I type the correct one it says to wait 24h, but it never goes beyond that.
I have tried every method possible that I have seen to bypass FRP, including OTG , disconnect wifi during update check, realterm and a few softwares , yet the same problem persist. I also tried Freelancer's tip , but same thing. It still asked for the old account because password was reset, and again tells me to wait 24h because of a password change.
Any more ideas?
SM-G530W Telus
Click to expand...
Click to collapse
This is going to sound crazy, but I guarantee that it will work. I have unlocked a dozen plus grand primes SM-G530W phones. You will not need any OTG cables or flash any firmware. But you will have to download a couple apk's to remove the account. So that said. Take your grand prime to MacDonalds. . When there connect to the MacDonalfs free wifi. Normally you cant open a captive portal on google locked phones. But you can with the grand prime. The macdonalds splash screen will open up and you can scroll down to the bottom and click a link for policy. That will open your browser. From there you can download technocaretricks apk and quickshortcutmaker apk and bypass the google account .
---------- Post added at 09:26 PM ---------- Previous post was at 09:00 PM ----------
Miyuki_Izawa said:
Out Of all the phones in the world you had to get that one.... that one is impossible to unlock, it uses multiple built-in software and has a glitch in the systems hardware to make it impossible to unlock I have two of them since 2016, december 12th, it is 2017-12-25. and let me tell you I would give anyone 1000$ who ever can prove me wrong... I am very confident that this phone can not be unlocked, it was one of the first phones to use frp and honestly it kinda sucks, I got a samsung galalxy 8s now... perhaps in the distant future someone will unlock this phone.. but ofcourse by then it will be ****...
Click to expand...
Click to collapse
I will gladly take your thousand dollars. Let me know when you have it and I will send you my address to etransfer it. I have proved you wrong. And hope you can keep your word cheers mate. I will be waiting for my private message requesting my email address for payment.
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.
jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?
I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.
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.
I have a Pixel 4 with Android 10 on it. It also has Android for Work (Enterprise), i.e., it is managed by work admin who can remote reset the device and also control what gets installed or not. It has MobileIron MDM agent installed on it.
How can I wipe all of this Android for Work and remove the MobileIron completely? I have no personal data on it and can do factory reset and the phone is carrier unlocked as well. The OEM unlock in Developer Options is greyed out.
Most likely, the phone was bought from Android Enterprise, which may also mean the app is built into the firmware - loaded as specified by whatever organization ordered the device from Google. But there's a couple things we can check:
Go to Accounts under Settings, make sure there is no work profile there.
Go to Security > Device Admin apps, see if you can remove the app there.
Failing those, try a factory reset. If the MobileIron app survives factory reset, it's built into the firmware.
Unfortunately there isn't much that can be done to get rid of it with a locked bootloader. You could try sideloading an OTA update but that may fail because the firmware won't match. You can also try the Pixel Repair Tool although I suspect that may not work for the same reason.
Let us know how it goes!
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
agaurav said:
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
Click to expand...
Click to collapse
What do you mean it doesn't go to bootloader mode?
Are you able to enable Developer Options and USB Debugging?
My bad. I tried Pixel Repair tool. It went thru successfully but did not remove the Android for Work so I guess I am stuck with a paper weight. Nothing can be done effectively. That's fine. I will wait for black friday deals and buy a new phone. Thanks.
agaurav said:
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
Click to expand...
Click to collapse
If the device is enrolled in Android Zero Touch, there is nothing you can do unless the IMEI is removed from Zero-Touch.