Related
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Use the original usb cable and use Smartswitch recovery, on the back is your serial number you need. And then keep on trying in Smartswitch, it took me a while but it worked and could restore my S6 to stock. And fixed Knox and the FRP lock. And I also tried everything but Smartswitch recovery saved my phone.
Sent from my SM-G928F using XDA-Developers mobile app
SOLVED
Hello, I after countless attempts with firmware that seemed to stock it did not work I SOLVED downloading the firmware directly from the Samsung server using "SAMFIRM" and then flash it with ODIN.
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
vooks said:
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
Click to expand...
Click to collapse
nazreen nasaruddin said:
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Click to expand...
Click to collapse
Here's the thing. I had a guy help me fix the FRP problem. And even he had some trouble doing so. And this was done last year, so I only kind of remember how he helped fixed it and I can't guarantee your guys' issue will be fixed if you follow my steps. And you guys may have to know the email and password associated with the phone. I took care of the dm-verity issue on my own afterwards.
Again, I THINK these steps may work, so please don't get mad if these steps don't work. if you guys can, try to flash TWRP or a custom kernel (via ODIN). I know you guys may be having the same problem, but try it out first. If you can't, try finding a combination file for your device (yes, combination file. On Google, search for "[model number] combination file" and download it). Afterwards, flash it to your phone via ODIN. This will allow the phone to boot up, but it's functionality will be very limited. Now, I think this is where you'll be able to login to Google in the settings and the FRP problem will be fixed, IIRC. If you can't login or don't have the details, there's not really much more I can help out with since I believe this is what fixed my problem (really fuzzy memory, sorry). Try rebooting and flashing TWRP again. The combination file itself may have fixed the issue.
If the above fixed the frp problem, GREAT! You should now be able to flash TWRP via ODIN. When you flash TWRP, the dm-verity problem should be fixed, as well. But now your phone needs a ROM and custom kernel. So now find the ones you want. Your phone should be working now!
If for whatever reason your phone still won't work, let me know. I may have another solution.
CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
godkingofcanada said:
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
Click to expand...
Click to collapse
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
CrazyTechnoBoy said:
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
Click to expand...
Click to collapse
you make me calm, cause i think combination file will save my phone which also i encountering the same like what you encountered before. and now i've read this post that you solved by flashing the combination file. i'm still waiting for my combination file cause i have binary 5 official rom while the combination files that i found is binary 4.
thanks!
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
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?
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
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want
Thanks a lot, this worked!
tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself