Decrypting loop after OTA update - Samsung Galaxy S7 Edge Questions and Answers

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.

Related

Unable to decrypt samsung galaxy s4

Hi, I have an i9505 which I have rooted with the help of some of the guides on here.
Anyway, I encrypted my phone from settings -> security not really knowing what I was doing. I was just thinking that it would make my phone more secure or whatever.
Anyway, following this I now have to enter a password every time I lock my phone screen which I find very inconvenient and I understand that I can't install any custom roms in the future.
I have tried to decrypt the phone from settings -> security but the process doesn't seem to complete.
It says that the decrypting process is irreversible ect ect.. it will take one hour ect... ect.. then when I click to confirm it and begin the decryption process the phone just seems to switch off then it turns back on by itself within 30-60 seconds and that is it. The phone is still encrypted?
Can anyone help me please?
I am really gutted!!!
Thanks
I am experiencing the same problem right now, did you ever find a solution?
imstilly said:
Hi, I have an i9505 which I have rooted with the help of some of the guides on here.
Anyway, I encrypted my phone from settings -> security not really knowing what I was doing. I was just thinking that it would make my phone more secure or whatever.
Anyway, following this I now have to enter a password every time I lock my phone screen which I find very inconvenient and I understand that I can't install any custom roms in the future.
I have tried to decrypt the phone from settings -> security but the process doesn't seem to complete.
It says that the decrypting process is irreversible ect ect.. it will take one hour ect... ect.. then when I click to confirm it and begin the decryption process the phone just seems to switch off then it turns back on by itself within 30-60 seconds and that is it. The phone is still encrypted?
Can anyone help me please?
I am really gutted!!!
Thanks
Click to expand...
Click to collapse
Encryption is irreversible without a factory restore.
read here http://www.dummies.com/how-to/content/encrypt-your-samsung-galaxy-s-4.html
did you try to back to stock with odin?
samersh72 said:
Encryption is irreversible without a factory restore.
read here http://www.dummies.com/how-to/content/encrypt-your-samsung-galaxy-s-4.html
did you try to back to stock with odin?
Click to expand...
Click to collapse
I was keeping my hopes going because there is a "decrypt device" option in the security settings, but that wouldn't work and I was hoping I was ****ing it up somehow. Guess device cleansing is my only option.
Penetal said:
I was keeping my hopes going because there is a "decrypt device" option in the security settings, but that wouldn't work and I was hoping I was ****ing it up somehow. Guess device cleansing is my only option.
Click to expand...
Click to collapse
Samsung device have the "decrypt device" option and it works, tried it multiple times.
Decrypting a Samsung Galaxy S4
Had the same problem several times. Make sure "USB Debugging" is off in the "Developer Options" section of the Settings screen.
Dont fret....go to settings<lock screen and then change it to swipe....Hope this works!
imstilly said:
Hi, I have an i9505 which I have rooted with the help of some of the guides on here.
Anyway, I encrypted my phone from settings -> security not really knowing what I was doing. I was just thinking that it would make my phone more secure or whatever.
Anyway, following this I now have to enter a password every time I lock my phone screen which I find very inconvenient and I understand that I can't install any custom roms in the future.
I have tried to decrypt the phone from settings -> security but the process doesn't seem to complete.
It says that the decrypting process is irreversible ect ect.. it will take one hour ect... ect.. then when I click to confirm it and begin the decryption process the phone just seems to switch off then it turns back on by itself within 30-60 seconds and that is it. The phone is still encrypted?
Can anyone help me please?
I am really gutted!!!
Thanks
Click to expand...
Click to collapse
Last night i had the same problem but i managed to fix
If you press decode it says password and then enter a password of at least 6 digits AND AT LEAST 1 NUMBER to activate the decoding part i tottaly missed that but i realized it a few hours after.
And then it started decoding for about half an hour and it was fixed.
Hope this was usefull so you wont need a system reset.
Given that the original post was in 2013, the OP likely had to reset, if none of the other posts from 2013 in the thread helped.
4.1/2 years on - there must be someone out there that knows how to decrypt the GT-I9195 ??
I spent yesterday researching pro's & con's of encrypting my phone. Couldn't find anyone saying password had to be entered EVERY TIME I USE the phone, just people wrongly advising that I would have to enter password every time I switch the phone on. I could live with that, I thought, so I encrypted it. Big mistake. Why anyone wants a phone that needs a password on every use, I do not know.
Please help me decrypt my phone. Thanks

[A3 2016] Recover data from FRP Lock bootloop?

No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
ScottHW said:
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
Click to expand...
Click to collapse
As advised flash the stock firmware. DATA won't be affected.
ashyx said:
As advised flash the stock firmware. DATA won't be affected.
Click to expand...
Click to collapse
Really? Many posts I've seen have noted that "all user data will be deleted".
Do I just use ODIN, and flash AP? No app, or user data will be erased, or formatted like that?
A few mention "Initializing with Smart Switch"; I haven't done that before. Is that different than flashing firmware?
ScottHW said:
Really? Many posts I've seen have noted that "all user data will be deleted".
Do I just use ODIN, and flash AP? No app, or user data will be erased, or formatted like that?
A few mention "Initializing with Smart Switch"; I haven't done that before. Is that different than flashing firmware?
Click to expand...
Click to collapse
Searching for that question directly, it seems like flashing a ROM (e.g. stock firmware) will not directly erase user data; downloads, photos in DCIM, etc.
But, sounds like any user-installed apps will be erased (so any internally stored data would be lost).
And, data stored in system apps would be lost, too; e.g. tabs that were open in Chrome.
There's no way around the FRP lock, eh?
Here is Samsung's statement about FRP (Factory Reset Protection)
It describes the Google account "protection" features, but doesn't really describe how FRP lock leads to bootloops.
https://www.samsung.com/us/support/frp/
Factory Reset Protection (FRP) Feature
What is Device Protection, or Factory Reset Protection (FRP)?
Android™ devices provide built-in security features you can use to protect your device and information, including screen locks and data encryption. Data protection, or Factory Reset Protection (FRP), is a security feature on Android devices with Lollipop 5.1 and higher.
FRP is automatically activated when you set up a Google™ Account on your device. Once FRP is activated, it prevents use of a device after a factory data reset, until you log in using a Google username and password previously set up on the device.
How does FRP work?
When you perform a Factory Data Reset, all settings are returned to the factory default settings. All data is erased, including files and downloaded apps.
If you have a Google Account set up on the device, FRP is active. This means that after the reset, you'll be required to log in to the Google Account using the username and password. If you have multiple Google Accounts set up on the device, you can log in using any of the accounts.
If an unauthorized person tries to reset the device by another method, the device would still require log-in using the Google username and password. This means that if your device is lost or stolen, another person would not be able to reset it and use it.
What do I need to know about FRP?
If you want to reset your device to factory defaults, make sure you know your Google Account and password, because you'll need to log in at the end of the reset.
If you want to reset your device to factory defaults, but don't remember your Google username and/or password, you can do one of these:
Check your device’s Account settings for your account name, and reset your password via the device or at www.google.com.
It can take 24 hours for the password reset to sync with all devices registered to the account.
Remove the account before you reset the device.
If you already reset your device, but don't remember your Google username and/or password, the device can't be used. In that case, you can do one of these:
If you know your Google username but can't remember the password, you can reset your password on the device, or at www.google.com. It can take up to 24 hours for a new password to sync with all registered devices. After 24 hours, you can try logging in to your phone with the new password.
If you have multiple Google Accounts, and you can't remember which Google Account you set up on your device, visit https://www.google.com/android/devicemanager.
Log in with your Google username and password and check the list of devices registered to the account. If you don't see the device listed on the account, it means the device is registered to a different account. Use the same process to check for devices linked to your other Google Accounts. When you find the registered account, use it to log in to your device.
If you can't remember any of your Google Account information, you can send your device, along with proof of purchase, to an authorized Samsung Service Center. Samsung has special tools to reset the phone to factory defaults with no protection enabled.
Click to expand...
Click to collapse
Looking for a Samsung Authorized Support Center, apparently there are ZERO listed around Omaha, NE.
http://support-us.samsung.com/cyber/locator/asc_locator.jsp
There must be ASC's somewhere; I'm hesitant to mail the phone away because I think the tech will just wipe it. The whole point is to maintain the data :-/
What do I need to flash to remove "Custom binary" ?
Will flashing the bootloader back to stock unlock the FRP lock?
That's BL throuh ODIN, right?
Do I have to flash AP ?
Won't that remove all user apps and their data, and any user data associated with system apps?
ScottHW said:
What do I need to flash to remove "Custom binary" ?
Will flashing the bootloader back to stock unlock the FRP lock?
That's BL throuh ODIN, right?
Do I have to flash AP ?
Won't that remove all user apps and their data, and any user data associated with system apps?
Click to expand...
Click to collapse
Not being funny, but you're panicking over nothing. I can pretty much guarantee you will NOT lose any data, apps or settings. The DATA partion is untouched by stock firmware.
Just flash the whole stock firmware(not repair firmware) and you'll be fine.
If you're super paranoid about losing data then just flash the AP part.
ashyx said:
Not being funny, but you're panicking over nothing. I can pretty much guarantee you will NOT lose any data, apps or settings. The DATA partion is untouched by stock firmware.
Just flash the whole stock firmware(not repair firmware) and you'll be fine.
If you're super paranoid about losing data then just flash the AP part.
Click to expand...
Click to collapse
Thanks for the reassurance. I am pretty paranoid, because I feel like such an ass for making such a dumb mistake.
Will I lose:
Contacts?
Text messages??
Chrome Bookmarks???
My numerous open Chrome tabs?!?!
I'm just trying to understand what's happening, know what I'm doing.
Because I was clearly stupid enough to uncheck OEM Unlock. (WTF was I thinking?!)
ScottHW said:
Thanks for the reassurance. I am pretty paranoid, because I feel like such an ass for making such a dumb mistake.
Will I lose:
Contacts?
Text messages??
Chrome Bookmarks???
My numerous open Chrome tabs?!?!
I'm just trying to understand what's happening, know what I'm doing.
Because I was clearly stupid enough to uncheck OEM Unlock. (WTF was I thinking?!)
Click to expand...
Click to collapse
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
ashyx said:
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
Click to expand...
Click to collapse
Thanks for the more specific information.
I've never found any discussions about how to solve the frp lock bootloop, with the intention of preserving user data.
If you will indulge me a bit more, I'd like to learn, test, and then share this for others.
Do you know exactly Custom binary blocked by FRP lock ""security" works?
Where is the flag that gets tripped?
In order to solve this bootloop, technically just Boot loader and Recovery need to be flashed (the exact versions must be used, or comparability issues can occur).
Bootloader should be simple enough: BL is one of the specific upload choices in Odin.
Recovery is a .bin that's contained with the AP.tar, correct?
Is it possible to specifically flash only the Recovery?
(I am reading other posts and pages as I write this, sorry if some of these points and questions seem "obvious"; I'm still learning. Aren't we all )
This thread is particularly detailed re: ODIN flashing, although it is from 2013, and for a specific device
https://forum.xda-developers.com/showthread.php?t=2154762
ScottHW said:
Thanks for the more specific information.
I've never found any discussions about how to solve the frp lock bootloop, with the intention of preserving user data.
If you will indulge me a bit more, I'd like to learn, test, and then share this for others.
Do you know exactly Custom binary blocked by FRP lock ""security" works?
Where is the flag that gets tripped?
In order to solve this bootloop, technically just Boot loader and Recovery need to be flashed (the exact versions must be used, or comparability issues can occur).
Bootloader should be simple enough: BL is one of the specific upload choices in Odin.
Recovery is a .bin that's contained with the AP.tar, correct?
Is it possible to specifically flash only the Recovery?
(I am reading other posts and pages as I write this, sorry if some of these points and questions seem "obvious"; I'm still learning. Aren't we all )
This thread is particularly detailed re: ODIN flashing, although it is from 2013, and for a specific device
https://forum.xda-developers.com/showthread.php?t=2154762
Click to expand...
Click to collapse
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
n00b mistake
ashyx said:
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
Click to expand...
Click to collapse
Sh!t, sorry, boot.ing /= bootloader. Rookie mistake. #StillLearning
OK, so boot.img and recovery.img should both be contained within the AP component of stock firmware.
I can just flash those two, can't I?
ashyx said:
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
Click to expand...
Click to collapse
Is there any non-GUI way to toggle the OEM UNLOCK?
Bootloader? Download mode? Recovery? Fastboot? ADB?
I assume not, since that might be a "security" risk. And also, if there were, problems like this would have solutions posted mentioning how to do that.
Sh!!!!!!!t... I was thinking I would have screenshots of the exact build that's loaded on my phone. That way I can find the right stock firmware.
Seems those screenshots are still in the phone, didn't get moved to external memory
All I know for sure is it's Andorid 5.1.1, but that probably isn't specific enough to get the exact right boot and recovery images.
I intend to flash the boot.img and recovery.img to my phone. Hopefully, this will avoid any data loss, while clearing the FRP lock bootloop.
I got the stock firmware for Android 5.1.1 for my Galaxy A3 (2016) (SM-A310M) here:
https://www.sammobile.com/firmwares/galaxy-a3-/SM-A310M/TTT/download/A310MUBU2APE2/73991/
This set of instructions says to extract the .img file(s) to flash, then just .tar them up using 7zip, and flash it as AP in ODIN.
http://howto.highonandroid.com/sams...extract-stock-recovery-from-samsung-firmware/
But... this one says to use Unified Android Toolkit, option ‘8’ (Create an Odin flashable tar), and then flash with ODIN.
https://skipsoft.net/flashing-a-single-partition-i-e-system/
Fortunately, I have a Galaxy A3 (2017) (SM-A320Y), which I was just about to upgrade to for my daily driver. It's blank, running Android 7.0, so it means I can test this process, see if data is preserved, with almost no risk to actual data. Got that firmware here:
https://www.sammobile.com/firmwares/SM-A320Y/COO/download/A320YDXU1BQH2/189605/
Ironically... I don't yet have a great method to intentionally trip the FRP lock bootloop
I think rooting and then unchecking OEM Unlock should do it (that's what wrecked my A310M)
FRP lock - Usb does not recognize
Hi, Everyone!
Sorry my english.
My problem is the same as yours.
however, after this frp lock message appeared, my phone goes into download mode, but the pc does not recognize any more. what can i do to get flash from the rom stock and solve the frp lock problem.
Help me, please!
Thank you all
ScottHW said:
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
Click to expand...
Click to collapse
FRP Custom binary Lock
ashyx said:
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
Click to expand...
Click to collapse
Could you help me to get access to my data? I'm running port of S8 on my S7 and got bootloop. Someone told me that even if I'll flash AP only I might lose my data because of difference in the way the memory is formatted.
Blackion said:
Could you help me to get access to my data? I'm running port of S8 on my S7 and got bootloop. Someone told me that even if I'll flash AP only I might lose my data because of difference in the way the memory is formatted.
Click to expand...
Click to collapse
If they're both stock based firmware then you can just flash the stock S7 firmware. Data should remain untouched.
Hi
I am just stuck with the same problem. I have downloaded the latest Stock ROM. But unsure which options to select in ODIN and what files to select.
I presume only select AP. Also, hope I will not lose any data.
Please help me out.

Sm-T580 FRP lock and custom binary blocked by frp. Cant flash twrp recovery.

So im trying to install twrp recovery but when i try to flash it thru odin, i get a Custom Binary (RECOVERY) blocked by FRP lock. I cant factory reset because it also disabled by FRP. I cant verify the tablet because i dont know the account information as the tablet was bought through craigslist. I have tried flashing a stock firmware version and that installed fine, but i still couldnt get past the verify screen. So thats when i decided to try and flash twrp but came into the binary error. I have been trying for the past two days to find a way around the verify identity and the frp lock. I cant enable oem unlock. I have tried rootjunky method but OTG flash wont pull up the file manager when plugged into the tablet. I cant use adb because i cant enable the developer settings because you guessed it i cant get past verify identity screen. Any help would be greatly appreciated.
Sounds like you need to find the Combination Firmware.
softasspoptart said:
So im trying to install twrp recovery but when i try to flash it thru odin, i get a Custom Binary (RECOVERY) blocked by FRP lock. I cant factory reset because it also disabled by FRP. I cant verify the tablet because i dont know the account information as the tablet was bought through craigslist. I have tried flashing a stock firmware version and that installed fine, but i still couldnt get past the verify screen. So thats when i decided to try and flash twrp but came into the binary error. I have been trying for the past two days to find a way around the verify identity and the frp lock. I cant enable oem unlock. I have tried rootjunky method but OTG flash wont pull up the file manager when plugged into the tablet. I cant use adb because i cant enable the developer settings because you guessed it i cant get past verify identity screen. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Read the post by Beut in this thread and then watch the video.
4929york said:
Read the post by Beut in this thread and then watch the video.
Click to expand...
Click to collapse
I already tried that method but didn't work. It's on android 7.0. I tried downgrading to sm-t580.. XAR firmware 6.1 and it worked but when it boots it goes straight to a black screen asking for a password. I tried the frp call method as well but it doesnt have wifi calling.
softasspoptart said:
I already tried that method but didn't work. It's on android 7.0. I tried downgrading to sm-t580.. XAR firmware 6.1 and it worked but when it boots it goes straight to a black screen asking for a password. I tried the frp call method as well but it doesnt have wifi calling.
Click to expand...
Click to collapse
It only works with certain versions of 6. The one ending is PL4 is the one you want. The trick is in adding the fake wifi network instead of connecting to your home network. Pay close attention to the beginning of the video.
lewmur said:
It only works with certain versions of 6. The one ending is PL4 is the one you want. The trick is in adding the fake wifi network instead of connecting to your home network. Pay close attention to the beginning of the video.
Click to expand...
Click to collapse
Okay thank you. I will try that again when I get home. And this works on version 7.0? The device is currently on 7.0 but when I tried the pl4 md5 it flashes it but when I boot up the device it just goes to a black screen and asks for a password. It doesn't start at the setup wizard
softasspoptart said:
Okay thank you. I will try that again when I get home. And this works on version 7.0? The device is currently on 7.0 but when I tried the pl4 md5 it flashes it but when I boot up the device it just goes to a black screen and asks for a password. It doesn't start at the setup wizard
Click to expand...
Click to collapse
You have to use Odin to install PL4. You can't flash it via TWRP. Also, make sure you wipe everything first.
lewmur said:
You have to use Odin to install PL4. You can't flash it via TWRP.
Click to expand...
Click to collapse
I know. I can't install twrp like I said. I've been using Odin to flash everything. But when I flashed the pl4 file and tablet goes to reboot. It doesn't load the setup wizard. Doesn't show the welcome screen and pick a language. It goes straight to a black screen and asks for a password. Doesn't ask for an email or anything.
softasspoptart said:
I know. I can't install twrp like I said. I've been using Odin to flash everything. But when I flashed the pl4 file and tablet goes to reboot. It doesn't load the setup wizard. Doesn't show the welcome screen and pick a language. It goes straight to a black screen and asks for a password. Doesn't ask for an email or anything.
Click to expand...
Click to collapse
Never heard of that. Can you boot from there into recovery and wipe again?
lewmur said:
Never heard of that. Can you boot from there into recovery and wipe again?
Click to expand...
Click to collapse
Yea but when I try to factory wipe it says mdm doesn't allow factory reset and reboots and takes me back to that same black screen. I can only wipe cache partition. I will post a picture of the screen when I get home.
softasspoptart said:
Yea but when I try to factory wipe it says mdm doesn't allow factory reset and reboots and takes me back to that same black screen. I can only wipe cache partition. I will post a picture of the screen when I get home.
Click to expand...
Click to collapse
I found this site. It is apparently an "MDM lock" and not FRP.
lewmur said:
I found this site. It is apparently an "MDM lock" and not FRP.
Click to expand...
Click to collapse
Tried this as well. I did it about 20 times before giving up. I might try it again and do it about 30 to 50 times. If I was just able to get to settings I'd be straight but I can't get to the settings so that's why I'm trying to reset it as a completely new device. Do you know if I could flash the 7 inch tab A firmware onto the smt580? Or flash the smt585 firmware onto the t580 and flash the BL AP and CSC?
softasspoptart said:
Tried this as well. I did it about 20 times before giving up. I might try it again and do it about 30 to 50 times. If I was just able to get to settings I'd be straight but I can't get to the settings so that's why I'm trying to reset it as a completely new device. Do you know if I could flash the 7 inch tab A firmware onto the smt580? Or flash the smt585 firmware onto the t580 and flash the BL AP and CSC?
Click to expand...
Click to collapse
From what I've read, Airwatch MDM lock can't be removed by flashing ANYTHING. It is third party anti-theft protection that has nothing to do with what ROM is installed. I know I ran into their stuff a few years ago with a used laptop I bought and only Airwatch was able to solve the problem after contacting their customer and verifying the laptop wasn't stolen.
4929york said:
From what I've read, Airwatch MDM lock can't be removed by flashing ANYTHING. It is third party anti-theft protection that has nothing to do with what ROM is installed. I know I ran into their stuff a few years ago with a used laptop I bought and only Airwatch was able to solve the problem after contacting their customer and verifying the laptop wasn't stolen.
Click to expand...
Click to collapse
Okay thanks. I'll get in contact with airwatch.
lewmur said:
I found this site. It is apparently an "MDM lock" and not FRP.
Click to expand...
Click to collapse
I did end up finding this. Seems the device is completely locked with no way to get around. When i flashed the device i may have deleted the admin privilages so there is no way of gettting around it as of now. I might end up paying someone to fix it or get around it or i wasted 180$ on a locked device. The guy i bought it from either blocked my number or deactivated his number as i cant get in contact with him. Pretty pissed. Thanks for all the help tho
I had the black screen password happen to me when I downgraded my SM-P580 from Android 7 to 6. Try clearing the cache. If that doesn't work, try reflashing, then turn it off and reboot to recovery and clear the cache.
BBowermaster said:
I had the black screen password happen to me when I downgraded my SM-P580 from Android 7 to 6. Try clearing the cache. If that doesn't work, try reflashing, then turn it off and reboot to recovery and clear the cache.
Click to expand...
Click to collapse
Okay I'll try that. Didn't try that yet. Will keep updated
lewmur said:
I found this site. It is apparently an "MDM lock" and not FRP.
Click to expand...
Click to collapse
Do you think if i changed the CSC to a different region on the tablet, and put a unlocked bootloader on it, would it might get rid of the frp lock? Do you happen to have a smt580? If so do you think there is anyother way of getting around this? say if i flashed like your firmware on to my tablet? Im desperate to get this thing unlocked as i would be out 180$ :crying:. Thanks for all your help so far. I really appreciate it man. Thanks to everyone who has helped so far.
Or what if i downgrade it to 6.1 and then downgrade it again to a even farther back version? Do you think this might work and gett me around the black screen? If so then i would be able to bypass the google verify account. Ima go ahead and try it unless its a risk of bricking the tablet completely.
I also read somewhere that if i flash the cp part on odin that it will erase all data. Think that might be worth a shot? But what do i need to insert in the cp slott? I know BL goes to BL and AP to AP and CSC home goes in CSC. So what goes in the cp slot?
EDIT: So instead of putting csc home in the csc slot i put the other csc file in its place. I checked the re partition box. When i did this i got a new message on the tablet in the top left of tthe download mode that says FRP is enabled, ignore PIT download. Any idea what this means?

**FIX** BL Flashed through RMM State Prenormal (OEM Locked) - IMEI/BASEBAND RESTORE

Excellent news and a solution i havent found anywhere else yet!
Follow up from - https://forum.xda-developers.com/galaxy-s8/help/restore-imei-attempt-stock-rom-flash-t3802527
TL;DR attempted to re-root as soon as the bootloader unlocked. It all seemed to stick again, and got the big red message of doom again.
"Official Binaries Only" - Last time i was able to restore to at least switch on the phone to run down the rmm state timer to zero to flash again.
Tried the several methods of flashing through a locked bootloader (old BL file, quickly restart download mode and spam start on odin, etc) - literally nothing would allow me to flash anything that included the BL file. IMEI and baseband remained unknown. Phone went in drawer for a few days.
Just went and downloaded the latest XSA (Australia, Unbranded) build - https://www.sammobile.com/firmwares/galaxy-s8/SM-G950F/XSA/ and guess what boys and girls?
This sucker flashes straight away with Odin 3.13.1
It has completely restored my IMEI and baseband, i now have full Cell connectivity again, and its all back and working again. OEM unlock is still disabled, Samsung Pay still locked out which is fine, but otherwise, i have gone from brick to fully working Exynos S8 again.
TL;DR IF YOU HAVE ISSUES WITH A BRICKED PHONE BECAUSE IT WONT LET YOU FLASH ANY STOCK ROMS TRY THAT ONE.
Thanks for the replies to my other threads trying to help out with this. Much appreciated.
Peace out.
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Ive had a few cracks at this now but the date keeps resetting itself when you reset the phone despite having the automatic update option switched off.
Thanks for the info tho ill keep trying.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, boot it and setup once. Then reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
kratosjohn said:
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, and reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
Click to expand...
Click to collapse
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash) - I used comsy as it is mentioned in hte post OREO S8 update. It allows TWRP to be flashed but maybe thats whats breaking everything else. Ill try magisk next.
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
UPDATE - Everything restored installed titanium backup root held. Rebooted phone aaaaaaaaand - "Only official released binaries are allowed to be flashed" - Back to square one. Will attempt same reflash now, but the root procedure kills everything. Back in download mode again. RMM State: Prenormal returned.
It is now succesfully flashing the stock rom in Odin 3.13.1 - Accidentally started it with Comsy and it DID NOT WORK. You MUST use the normal version to flash the rom im using.
Looks like we def have a stable way to refire up the phone again, and get around RMM state prenormal nice and quickly, so ill go ahead now and try and find whats going on with things breaking afterwards!
Thanks again guys.
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Funkmonkey said:
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash)
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
Click to expand...
Click to collapse
Someone should clean this up and get it stickied.
I imagine there are alot of users here with this same issue, after the CRED update we can't downgrade our bootloader, and in a panic you can get stuck here.
kratosjohn said:
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Looks like that wont be an issue any more to be honest this phone is now a backup thankfully so i can play around with it to my little hearts desire.
Im about to try the magisk install. SuperSU/Aroma definately breaking something somewhere. Or verity. I dont know but rooting the phone at the moment is killing it again.
Also, i have NOT lost IMEI or baseband this time. At the very least for Australian SN-G950F phones, this is a 100% flashable stock rom regardless of your RMM or phone status. I cannot say this for any other model in any other country on any other carrier, but this is all working for a carrier free Exynos S8.
Maybe y'all better archive the actual stock somewhere before someone realises theyve made a mistake somewhere and it gets pulled. Im definantly backing it up.
I just got that oem unlock trick to happen in 2 shutdown/restarts NOT reboots. BUT. I did NOT enable developer mode until i had disabled automatic time updates and turned the date back 8 days. The option came up instantly. Is something comparing a hardware clock deep in the system to a software clock in the os to and developer mode comparing something in between? Either way, on to reflash TWRP again now. This is a good day.
Click to expand...
Click to collapse
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Funkmonkey said:
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Click to expand...
Click to collapse
Have you found and used this after getting your phone setup right (w/twrp)?
I think you should flash magisk, then this after.
After I had this "panic" I flashed the custom rom I was aiming for (once RMM: Official). That rom has a kernel with the RMM state fixed/locked.
Maybe look for a custom kernel if you want root, I believe this is the fight we have to put up even on stock w/root.
Download the Australian stock rom and install it but do not recover IMEI or coverage. I think it's because my G950F (singlesim) cell phone thinks it's G950FD (double sim). This causes the cell phone to get confused and not recognize any imei or sim. Does anyone know how to fix it?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Do we need to factory rest or just reboot phone after we change date?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
Sorry i missed your reply i hope you got it fixed if not post again and ill see if i can help. Ive definantly gotten that oem unlock trick working which is awesome but its fiddly. I dont think it works if you turn on flight mode and you have to let the phone fight you between 'no automatic date and time' and the network forcing the time.
Of course now i cant get the oem unlock trick working...
RE the dual sim issue... i think you would need the stock rom specific to your model try sammobile, see if there is a CRED release for your model. I cant guarantee it will work tho.
kratosjohn said:
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Click to expand...
Click to collapse
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Smartphones13 said:
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Click to expand...
Click to collapse
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Funkmonkey said:
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Click to expand...
Click to collapse
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Smartphones13 said:
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Click to expand...
Click to collapse
I think we might be looking at different issues.
This is to fix a semi bricked phone that has locked up its bootloader. In the past to resurrect a samsung all you had to do was flash twrp and your new rom but since Oreo some funkiness has been added to the system which only lets you flash a stock rom, (i.e. restoring a phone to factory settings and software) via ODIN/HEIMDALL then it locks up the bootloader for a week so you CANNOT flash anything into the phone that modifies the bootloader (i.e. TWRP OR *any* rom) until its timer runs out. This is most likely an anti theft feature esp with samsung and google pay use as it means there is no way to easily break into a stolen phone and use it as normal, and reflashing breaks all of the security features of the phone (e-fuse) - no knox no samsung or google pay no samsung pass as your device is insecure and could spoof false banking details etc.
The rom i linked to is important as it is a new AUSTRALIAN unbranded STOCK rom, that for some reason you can flash OVER a locked bootloader, meaning you can resurrect (australian at the very least) SN-G950F phones (exynos)
If you already have a working phone and can get to your developer settings then most of this thread is irrelevant to you.
Now - OEM unlock - You just bought a brand new galaxy from samsung (or youre me and you bought a MINT second hand one from cash converters for $700 less) - your phone is factory standard and schmicky. THE BOOTLOADER IS LOCKED. THE RMM STATE SHOULD NOT be triggered. If right now you went to flash something it would fail.
So you go to about phone - software information and you tap 'build number' seven times to unlock developer mode. Hit back twice and developer mode will be at the bottom of settings.
Click into this and you should see without swiping down 'OEM UNLOCK' - If you enable this, you can then reboot straight into download mode (power vol down and bixby) and flash twrp or whatever rom.
If you dont see this option, you either have a snapdragon model (youre **** outta luck permanently) or RMM is PRENORMAL and you either have to try the unlock trick(s) or leave your phone SWITCHED ON for 1 week and it will unlock itself.
The biggest issue at the moment is that i keep breaking something after i attempt to root so not sure whats happening there so use major caution.
Now as i said the trick posted above to unlock without having to wait a week (which i think youre asking about) im now not sure how it works because i cant get it to work any more.
Automatic time and date off, set date back 8 days, reset the phone. Do this a couple of times, then turn on automatic date and time again. HERE THERE BE ISSUES. When i first did it - i switch off time and date and change then reset, when the phone came on, auto date and time was on again. Turn off, change date, reset. Again, its back on. Turn off, change date, reset. Its back on. I give up and leave it, and notice later the option was available, so it worked. I broke the phone, reflashed again, did the trick in ONE reboot. Fcked something again, reflashed, now auto time and date stays off and the trick wont work so i cant help you with that until someone comes up with more info im sorry! Its a bit zarbis.
Im not going too nuts trying to fix it as i now have a fully working stock backup phone that sits on DeX plugged into my bedroom tv full time and im not into custom roms, root keeps breaking the phone, and ive sonce replaced it with a mint S8+ that im not even THINKING about considering rooting until its replaced maybe next year. Its not as easy to get around anymore and thankfully a) picasa and hangouts are no longer stock apps and can be banished and b) you can now disable all the other built in apps natively so its now a lot more bearable with a totally stock phone.

T580 - Suddently got FRP Lock after over 6 months of use. Any way to recover?

Hi Guys,
I have a couple T580 tablets for my kids, and we had just gotten a new one for Christmas that I set up. I THOUGHT I had done everything correctly, but the new tablet is giving me the FRP Lock suddenly.
Any idea how that could happen? Is there any way to recover the tablet or do I have to do a original rom flash?
Thanks
sjbayer3 said:
Hi Guys,
I have a couple T580 tablets for my kids, and we had just gotten a new one for Christmas that I set up. I THOUGHT I had done everything correctly, but the new tablet is giving me the FRP Lock suddenly.
Any idea how that could happen? Is there any way to recover the tablet or do I have to do a original rom flash?
Thanks
Click to expand...
Click to collapse
Somethings not right. You don't "suddenly get an FRP lock". An FRP lock occurs only after you "factory reset" the tablet and don't know the google account login. And that is only if you hadn't enabled "OEM" in "Developer options". What makes you think it is the "FRP lock"? And if it is locked, flashing a ROM with Odin won't help. You'll still need the google account info to access the tablet.
lewmur said:
Somethings not right. You don't "suddenly get an FRP lock". An FRP lock occurs only after you "factory reset" the tablet and don't know the google account login. And that is only if you hadn't enabled "OEM" in "Developer options". What makes you think it is the "FRP lock"? And if it is locked, flashing a ROM with Odin won't help. You'll still need the google account info to access the tablet.
Click to expand...
Click to collapse
Because this is what it says when I start the tablet...
https://i.imgur.com/u8PXyBD.png
I have a google account, and info, for the tablet. Not sure how I put it in when the boot process is blocked though...
My only thought is something happened with Magisk?
sjbayer3 said:
Because this is what it says when I start the tablet...
https://i.imgur.com/u8PXyBD.png
I have a google account, and info, for the tablet. Not sure how I put it in when the boot process is blocked though...
My only thought is something happened with Magisk?
Click to expand...
Click to collapse
Again, unless something has changed, which I doubt, that is not the way the FRP lock works. First of all, you said nothing about having a custom ROM installed. But even if you did, the FRP lock would NOT prevent the tablet from booting. It would merely ask for your google account info when it did boot. Have you tried booting into recovery and performing a factory reset?
edit: Let me explain what FRP means. In early versions of Android, if your phone/tablet were lost or stolen, anyone could bypass your "screen lock" simply by booting into recovery mode and perfoming a Factory Reset. So Google came up with the Factory Reset Prevention lock. So if someone tried to use the Factory Reset, the lock would demand the google account login and password to access the tablet. So if you wanted to sell your tablet, you either had to enable "Developer options" and then use that to "Enable OEM", prior to reseting the tablet or put in a google account whose info you could pass to the buyer, remove your real account, and then reset.
In any case, the tablet did NOT show the message you are getting. I've bought several T580s on eBay that WERE locked, and none of them gave that message. A locked tablet would still let you install stock ROMs with Odin, but the tablet would still ask for the google account info. But the way around that can be found in this forum.
lewmur said:
First of all, you said nothing about having a custom ROM installed.
Click to expand...
Click to collapse
I dont think I do, its stock rom, but Magisk is installed which I believe is not a custom rom.
lewmur said:
Have you tried booting into recovery and performing a factory reset? .
Click to expand...
Click to collapse
When I turn on the power, the screen comes on, and then says "Custom Binary blocked by FRP Lock" then the screen turns off. I have not tried a factory reset because I was hoping to find a solution without losing everything before I did something that could not be undone.
The only thing left is, I know samsung will (if detected) attempt to remove software. I wonder if it somehow tried to reset automatically and in so doing caused this.
A factory reset does not help in your case.
First option is: contact your person, who sell the phone. Because he must unlock this one in his Google settings.
The question is: how many times a wrong oe no account was insert, that the device doesn't start up till the possibility to insert the correct account.
sjbayer3 said:
I dont think I do, its stock rom, but Magisk is installed which I believe is not a custom rom.
When I turn on the power, the screen comes on, and then says "Custom Binary blocked by FRP Lock" then the screen turns off. I have not tried a factory reset because I was hoping to find a solution without losing everything before I did something that could not be undone.
The only thing left is, I know samsung will (if detected) attempt to remove software. I wonder if it somehow tried to reset automatically and in so doing caused this.
Click to expand...
Click to collapse
You don't lose everything with a Factory Reset and what you do lose should be easily recovered from your google account backup. And nothing else could be done that wouldn't also cause a reset.
mad0701 said:
A factory reset does not help in your case.
First option is: contact your person, who sell the phone. Because he must unlock this one in his Google settings.
The question is: how many times a wrong oe no account was insert, that the device doesn't start up till the possibility to insert the correct account.
Click to expand...
Click to collapse
No one sold me this phone, I bought it new. There is no unlock option. The phone doesnt event start booting, the screen turns on says the FRP lock, then turns off.
Ab FRP Lock said, that the phone is looked via a Google account.
In a normal case, you can only unlock the device, if you insert the correct Account with password.
I don't know.. maybe you have insert 3 time wrong credentials... why the device give your not the possibility to unlock the device.
Try an complete wipe / factory reset out of the recovery menu, so that the OS can start.
The lock isn't away, but maybe you have the possibility to insert the correct data.
In Download Mode here is what I see:
https://i.imgur.com/5eZ2YmH.png
Alright I just flashed the latest rom and that fixed it.
I now know a little bit about what is going on. When I got the tablet, I set it up for me. Then I discovered googles "family link" so I set it up again for my daughter.
Child accounts have FRP protection. I dont know what triggered it, but somehow it activated recently when it discovered magisk which I had installed some time back.
Now I am super irritated and over Family Link...

Categories

Resources