Related
I've made a bit of a mess and I need help please. My s4 is softbricked, but as softbricks go, it's rather hard.
I have an early S4 i9505 bought from Carphone Warehouse (UK, unlocked, pre knox). I rooted it, installed TBackup, greenify and got it how I wanted it. Then I downloaded a stock firmware from Sammobile and tested to see if I could get it back to 'warranty' condition, which was a success.
Confident that I could obtain warranty if I needed it, I re-rooted it, installed TB and greenify, and it ran sweetly for months from that point onwards.
I read about the arrival of updates (and knox) and concluded I didn't need them. It was working, leave it alone.
Then out of the blue, my nice stable machine broke. I didn't change anything I was aware of to cause it.
No normal boot.
No recovery.
Download only.
Using Odin, I tried allsorts, eventually getting the same Sammobile firmware to run.
2 days later, it broke again, same as before, but worse!?
Then I tried all sorts of stuff downloading no end of things trying to get it to boot or even go into recovery. The most promising approach was to reload the firmware along with a .pit file, but still no joy. I've lost track of the other things I tried, but I've been doing it for a week, so a lot has been done. In desperation, I even tried downloading the latest firmware, so I now have signs of knox of the odin page.
I now have the following symptoms:
Booting into recovery brings up the blue 'booting recovery' message then just blackness.
Normal boot is exactly the same as above.
Unpowered conection to my laptop gives a 5 second boot loop featuring the buzz only.
I can reliably boot into download and download stuff with Odin and change the little Odin page status messages. After (foolishly) trying the latest firmware, these messages say
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Wrinklespots said:
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Click to expand...
Click to collapse
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
spamtrash said:
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
Click to expand...
Click to collapse
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Wrinklespots said:
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Click to expand...
Click to collapse
1. Are you able to go to recovery mode?
2. Assuming that your previous communicates were taken from the screen in download mode - you're clean.
If answer for 1 is: NO, and assuming 2: do not bother the flash counter. Flash counter does not means you messed with custom ROMs, it just means amount of the ROM update tries. As they are unable to prove that the counter was not increased by failed KIES updates, you're safe.
To go deeper, service will have to flash and wipe your phone.
One thing: remove your sd card prior to giving/sending it out.
Try a different usb cable.I was in same boat as you (after stupidly thinking mobile odin pro liked modems).
Luckily I had an unused cable off my tab 3.
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly.
(I know my google account and password)
I was curious is it safe to stay with reactivation lock checked in case this happens:
Lets say the soft bricks into a boot loop who knows why but recovery still works.. so if I want to factory reset from custom recovery(philz recovery, with Nandroid and efs backed up), I think it is the best to unroot before factory reset(hope I'm wrong), witch will be imposible if the root didn't worked because of the reactivation lock, the unroot won't work too?
I gues before trying any flashing etc is good to uncheck reactivation lock, but I can allways make a mistake and forget it on.
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
I want to activate it for safety but this safety could block me too?
Do you guys keep it on after rooting?
I hope the readers will understand my question and don't get any headakes, sometimes I gould it hard to express myself in english, sorry about that.
alexpu1u said:
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
Click to expand...
Click to collapse
Well reactivation lock is an anti-theft feature. Theft deterrents are good although they only have significant value when they are well implemented. Which is arguable in this case. It's hardly undefeatable. 2 strikes. And can be as annoying as hell in not liking your custom kernel. Strike thr ...
Bottom line, if you are good at making backups and believe in theft deterrents, then enable it. It makes it slightly more likely that a lost phone would make it back to you. Or at least ruin the thief's day. There should always be a way to restore your device if you have a backup and your credentials.
However if you are forgetful, bad with backups or simply have no patience for having to search XDA threads or enter something on a command line to disable reactivation lock and recover from a bootloop, etc.. then obviously don't use it. It could cause you some exasperation if you are in an unbootable state and it is interferring with an Odin flash.
Pick one. And either way try not to lose your phone.
.
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
alexpu1u said:
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
Click to expand...
Click to collapse
Well, I'm not concerned with being locked out of my phone permanently. Nor convinced that RA would really stop a stolen phone from being reactivated. But it's plausible that it would delay some thieves from using Odin to obliterate your tracking software.
So a longer window in which it might be possible to pin down your phone's location. Or perhaps spur someone to return your phone in the case of a lost, rather than stolen phone.
Whether to use RA depends mostly on your willingness to put up with some temporary frustration should your phone somehow end up unbootable and you have to jump through a few hoops to disable the reactivation lock.
.
alexpu1u said:
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly...
Click to expand...
Click to collapse
But you can't enable this option after root, it does not work!
knox 0x1 (2)
jgfernog said:
But you can't enable this option after root, it does not work!
Click to expand...
Click to collapse
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
MaXi32 said:
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
Click to expand...
Click to collapse
Yeah! There are some problems with it. I saw people saying that their devices had KNOX enabled even with the option unchecked in settings.
I wouldn't bother with reactivation lock for any scenario
1. Easy to bypass
2. Only causes problems for yourself if you forget to disable it before flashing
3. Anyone who knows how to flash a new ROM, which is what it's designed to prevent, can bypass it flashing a KitKat ROM anyway
4. You've lost your phone anyway, they're not gonna give it back because they can't use it
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 devices 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.
So long story short I was intoxicated and for some reason disabled OEM in debugging then sometime later I restarted my tablet to get the frp binary locked. It has a custom rom with twrp I absolutely need the data off of this tablet and the only way I see is to reinstall the default os through Odin but that wipes the device I need a method to get the data off of the tablet or a method to bypass frp entirely it would be mighty appreciated if I could have some help
Why don't you try a backup in TWRP?
Reinstalling the stock firmware with Odin won't wipe the device.
slop_me said:
So long story short I was intoxicated and for some reason disabled OEM in debugging then sometime later I restarted my tablet to get the frp binary locked. It has a custom rom with twrp I absolutely need the data off of this tablet and the only way I see is to reinstall the default os through Odin but that wipes the device I need a method to get the data off of the tablet or a method to bypass frp entirely it would be mighty appreciated if I could have some help
Click to expand...
Click to collapse
It's difficult to say if you can keep your data. The binary FRP lock is quite different that the average FRP lock that's associated with the Google sign in. Usually whenever you trip the binary lock it's because some firmware was installed such as a Root or a ROM that was flawed or invalid. It's an overstacking of binaries and therefore you get a "Custom Binaries Blocked by FRP Lock" notification. I've had this problem on another varient of the Tab A, the Galaxy Tab A6 SM-T580. I have found about four diferent variations of this. You may not have turned off OEM because in Binary lock it will act like you have. Possible reason to think that is the way it acts in Download Mode where you can't seem to flash anything especially the official firmware. Sound familiar?
Version 1. If you try to go to Recovery you get redirected to a screen similar to the Download Mode. In the upper left are red lettered "Custom Binaries Blocked by FRP Lock.. Download Mode is accessable but won't initialize when trying to flash stock firmware. Binary 4 FRP Unlock file was accepted and flashed in by Odin3. Stock firmware installs afterwards.
Version 2. Device is stuck in bootloop. "Custom Binaries Blocked by FRP Lock" appears on Logo screen. Recovery and Download Modes are so far, useless. Binary 4 FRP Unlock used, no positive results. Binary U 4 used. Positive result. Stock firmware flashed in afterwards.
Version 3. "Custom Binaries Blocked by FRP Lock" appears on Download Mode which either stalls right after or fails to initialize. Binary 4 FRP Unlock and Binary U 4 yeild no positive results. (This ones on it's way to me).
Version 4. "Custom Binaries Blocked by FRP Lock appears on Recovery Mode. Download Mode useless. I'm currently following this one.
Solution: I don't know if the one I have will work, they may be device specific. Research for a "SM-T280 Binary 4 FRP Unlock" which I couldn't yet find.
Casper Young said:
It's difficult to say if you can keep your data. The binary FRP lock is quite different that the average FRP lock that's associated with the Google sign in. Usually whenever you trip the binary lock it's because some firmware was installed such as a Root or a ROM that was flawed or invalid. It's an overstacking of binaries and therefore you get a "Custom Binaries Blocked by FRP Lock" notification. I've had this problem on another varient of the Tab A, the Galaxy Tab A6 SM-T580. I have found about four diferent variations of this. You may not have turned off OEM because in Binary lock it will act like you have. Possible reason to think that is the way it acts in Download Mode where you can't seem to flash anything especially the official firmware. Sound familiar?
Version 1. If you try to go to Recovery you get redirected to a screen similar to the Download Mode. In the upper left are red lettered "Custom Binaries Blocked by FRP Lock..
Solution: I don't know if the one I have will work, they may be device specific. Research for a "SM-T280 Binary 4 FRP Unlock"
But I couldn't find one.
Here's my post, it may help.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
ashyx said:
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
Click to expand...
Click to collapse
I hate to argue with you but that wasn't so easy with mine. While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. Trial and error followed. The solve was first I had to flash in the Binary FRP Unlock and then I could flash in the firmware. With another device the owner tried the Binary Frp Unlock which didn't fix it. Later he flashed in the U4 Binary and that worked for him. I passed the info along to some others in the same predicament and it helped them. So I don't know what to tell you but what you're stating is not always applicable.
Casper Young said:
I hate to argue with you but that wasn't so easy with mine. While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. Trial and error followed. The solve was first I had to flash in the Binary FRP Unlock and then I could flash in the firmware. With another device the owner tried the Binary Frp Unlock which didn't fix it. Later he flashed in the U4 Binary and that worked for him. I passed the info along to some others in the same predicament and it helped them. So I don't know what to tell you but what you're stating is not always applicable.
Click to expand...
Click to collapse
Trust me, I have 3 of these devices. I've bricked them, frp locked them every possible way during development for this device.
The T580 is a different device and may be more difficult to bypass if and only if FRP has kicked in because of a device reset.
However for EVERY Samsung device that has simply had non stock software installed the only fix that's required is to install the stock firmware.
This is the case on all the Samsung devices I own and I have quite a few from lollipop to Pie.
ashyx said:
Trust me, [not happening!]I have 3 of these devices. I've bricked them, frp locked them every possible way during development for this device. [Well, umm. No, you haven't. And take a wild guess how many devices I have, like that matters.]
The T580 is a different device and may be more difficult to bypass if and only if FRP has kicked in because of a device reset. [Everytime you turn off the device it resets.]
However for EVERY Samsung device that has simply had non stock software installed the only fix that's required is to install the stock firmware. [You obviously have difficulties comprehending that I said otherwise]
This is the case on all the Samsung devices I own and I have quite a few from lollipop to Pie.
Click to expand...
Click to collapse
Wow, you're on a roll ain't ya? Hey ASHYX, dont misjudge me because of my stats you see here. Over a decade ago I was stacking ROMs into my HTC-G1. 3 decades ago I was an Electrical Engineer and Sonar Operator in the Navy. Let me tell you point blank, you're mistaken! Normally you would think you can just flash in stock OTA firmware into the device via Odin3 and you get to return to normal. Well that wasn't the solve for this. This was a new one to me also. If you think you're so right on what you say I'll be more than happy to point you in the direction of some XDA visitors, two of which are still Binary FRP locked. You can try telling them what you just told me and they'll probably call you a blooming idiot. No offense but you could try reading it properly which might help.
I said, [QOUTE] " While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. [END QOUTE]
Take my word for it, the method you stated was already tried AND DID NOT WORK!
If you want to insist you're all that, here ya go, these people need your expertise in development
https://forum.xda-developers.com/ga...frp-locked-t3772512/post80420061#post80420061
Data loss when flashing stock firmware.
ashyx said:
Reinstalling the stock firmware with Odin won't wipe the device.
Click to expand...
Click to collapse
That depends on which stock firmware you're using. Typically what you get OTA (over the air) is the same as the 4File Official Stock Firmware. These are the 4 files that go into each section when using Odin3 to flash firmware. BL is for the Bootloader which controls security, start-up and recovery. AP is Android Partitioning, CP is Cellular Processor. Now let's talk about the CSC. file. The 4File contains two CSC files, one is listed as HOME CSC. If you flash the CSC file you will lose your App data. If you flash the HOME CSC you do not lose your App data.
Casper Young said:
That depends on which stock firmware you're using. Typically what you get OTA (over the air) is the same as the 4File Official Stock Firmware. These are the 4 files that go into each section when using Odin3 to flash firmware. BL is for the Bootloader which controls security, start-up and recovery. AP is Android Partitioning, CP is Cellular Processor. Now let's talk about the CSC. file. The 4File contains two CSC files, one is listed as HOME CSC. If you flash the CSC file you will lose your App data. If you flash the HOME CSC you do not lose your App data.
Click to expand...
Click to collapse
ashyx said:
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
Click to expand...
Click to collapse
Thank you for confirming I won't loss any data upon installing the original ROM I did just have a custom ROM installed I was super concerned that I would lose all the data upon installing the original ROM thank you so much <3
slop_me said:
Thank you for confirming I won't loss any data upon installing the original ROM I did just have a custom ROM installed I was super concerned that I would lose all the data upon installing the original ROM thank you so much <3
Click to expand...
Click to collapse
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
ashyx said:
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
Click to expand...
Click to collapse
Yeah it was just stock lollipop with a root. Will that cause an issue or am I good to continue?
ashyx said:
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
Click to expand...
Click to collapse
Props to you thanks for the knowledge it worked flawlessly I mean kinda half way through it did say erasing and I kinda **** the bed and got scared because I really needed the data off of there but my man you are right just flashing stock ROM worked flawlessly everywhere online says it will wipe the device but it didn't. Thank you so much for your fantastic help <3
Hi I am new to this but i have a samsung Tab A 10.1 SM-T595 from my university and it is locked with their knox cloud service so i have tried to restore OS with Odin and now i cant login or anything to their knox nor get android so i wanted help getting android to my tab without access to any settings is there any way? the Bootloader is locked aswell so i cannot use them i was searching for a workaround so i need help. i have maximum access to the connect to wifi screen before knox takes over and i lose previlges to anything cuz everything is blocked by their service
Deleted
JJcoder said:
Did you trip Knox?? If you did none of the knox features will work anymore.
Click to expand...
Click to collapse
i dont know if i have tripped it im just stuck in the initial setup screen and cant do anything from there on
Deleted
reply
Hi im rlly sorry for the late reply but i reset the os bcuz i rlly had nothing to do in the previous version which was basically locked to a few apps that they control and I cannot access anything from it and i did it cuz one of my pals did the same and worked for him https://500px.com/photo/1018025656/IMG2020070120281001-by-Spin-Gaming/ this is the screen that shows up after wifi and then itll take you to the know login page with the id and password i just blurred out the university name
Deleted
we have followed the exact same steps whereas he was able to access all settings in the setup screen and i wasnt and also what is a combination firmware and what all can i do with it also if you can find a u4 file can u send a link over will be very much helpful thank you
Deleted
its Fine no worries
Through the combination firmware i have unlocked the bootloader but if i flash the samsung os i still get the enrollment page so i was wondering if there is any other way and i am not able to flash twrp for some reason as it switches into a diff page and i dont know if there are any cutsom os for the tablet .i wont be using cellular anyways so if there is a custom os that works i can try
what he did was take a tablet owned/provided by his school who have a mdm service on it that is set to lock the device if it is wiped specicically to prevent ppl from modifying it or stealing it.
its basically an mdm lock.. you need to contact the school and ask them to remove the mdm lock. any time you connect to data which is required when mdm locked it will lock or set up the mdm again.
you cant get rid of it by simply flashing firmware...
Deleted
JJcoder said:
Are you sure there is no way to bypass it?
Click to expand...
Click to collapse
oh there is but not gonna get it out of me.. im against it as it is unethical (borderline stealing)..
they put mdm on devices for a reason.. to top it off its supposed to be used for his education.. hopefully it wasnt bought with taxpayers money..
basically its tied to the imei/serial.. when it was first installed it sets flags on the device so depending on what they set up it can block factory reset, block ota upgrades including in download mode etc.
when it starts up it sees that it is tied to an mdm via the flags and requests internet connection to move forward at which it updates with tbe server and loads any policies or w.e back to the device
Deleted
JJcoder said:
Okay, so I found out how to bypass it
1. You need to get the PIT file for your device. I found this guide on how to get it: https://www.getdroidtips.com/how-to-extract-pit-files-for-any-samsung-galaxy-device/
2. Once you have the PIT file boot your device into Download mode and connect it to your computer.
3. Load the stock firmware into Odin (BL, AP, CP, CSC OR if your firmware is just one file then load that file)
4. Then load the PIT file into Odin.
5. Go to the Options tab on Odin and make it look like this:
6. Go back to Log and click on Start
7. Wait for the firmware to flash and for your device to boot up.
8. Once it's done the enrollment page will be gone
If you have any problems or questions please let me know
Click to expand...
Click to collapse
the pit file is in the firmware files lol every firmware has the pit file.. u just extract it..
and thats not permanent.. soon as it phones home itll register the mdm again..
Deleted
JJcoder said:
I know but that's if you have the CSC file, if your firmware is just one file then it's not there.
Also, are you sure? The Nand Erase Option will Erase everything and reconstruct the EFS along with all other Partitions removing the MDM lock.
Click to expand...
Click to collapse
well yea, i meant regular 4 file firmware (or 5) ap bl cp csc home csc and userdata..
and yes.. they use your imei and/or sn which is enrolled in their portal/server so eventually they can send policy over the internet..
you can even get a trial and check it out urself.. type in knox manage or knox suite or knox configure etc.
Deleted
JJcoder said:
But it still works, right? If it doesn't work, how is it even possible to bypass then? Wouldn't you have to change your IMEI and/or SN?
Edit: I also found this: https://www.isla7.net/how-to-remove-knox-mdm-on-samsung-devices/
Click to expand...
Click to collapse
u ask a question about everything ? unfortunately i dont have time to reply constantly.. i suggest continue browsin around n readin.. its how i learned stuff
Deleted
elliwigy said:
oh there is but not gonna get it out of me.. im against it as it is unethical (borderline stealing)..
they put mdm on devices for a reason.. to top it off its supposed to be used for his education.. hopefully it wasnt bought with taxpayers money..
basically its tied to the imei/serial.. when it was first installed it sets flags on the device so depending on what they set up it can block factory reset, block ota upgrades including in download mode etc.
when it starts up it sees that it is tied to an mdm via the flags and requests internet connection to move forward at which it updates with tbe server and loads any policies or w.e back to the device
Click to expand...
Click to collapse
Nope it isnt tax payers money it is my own and also due to the quarantine i havent found a use for it as neither the school updates it or neither am i able to do anything so yeah its just sitting there like some junk so yeah