Database Users

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB

(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

Samsung S8-SM-G950F custom binary blocked by FRP lock

Samsung S8-SM-G950F custom binary blocked by FRP locked, i saw so many theards about this and i read them, and i still don't know what to do, so my question is if i download firmware with "SamFirm" and then use oddin will i get my phone unlocked from that ? As i had custom rom for year and half and today i got that error for the 1st time , also if the "SamFirm" is not good for that can someone give me link for firmware for my phone as updato and all other sites download soo slow at 15 kb/s and i can't use them it will take 20hours to download that (

Similar situation, I broke my S8 screen, so never got it fixed, and was recently without a laptop, so thought id use the S8 thru Dex, it all worked no probs, however, I used to unlock bootloaders to install custom firmware and os's but didnt think id done it on my S8 as it was still under warranty, so upon looking in the developer options, i saw that OEM Unlock was on, so i switched it off, not remembering rooting the phone, now i get same error it bootloops and says custom binary frp lock. Did u ever get yours sorted? I know my google account to login 2 it if i ever get the official rom back working, but trying odin and smartswitch restore im still stuck, just keeps failing, saying frp lock. Cant even get into recovefry mode to factory reset, didnt thiunk i had TWRP installed on it, but i must have. Anyway, if anyone can pls help me pls contact me here or at dcillusionz at proton dot me. Thanks.

PS - I tried downloading from SamFW and using Odin, but FAILED. Hoping u had some luck?

Sm-t280 frp locked binary

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

SM-935A FRP Lock, am I screwed? (accidentally upgraded to Binary A)

Purchased the phone off guy on Facebook. It appears that he wiped it without realizing about the FRP lock. It had 7.0 on it. I tried all the tricks you see on the youtube videos to bypass FRP but none of them worked. I know how to use ODIN and Z3X, so I flashed an 8.0 firmware thinking I would try some of the bypass methods for 8.0. Those didn't work so then I tried to move back to 7.0.....and then I learned that you can't downgrade bootloaders. In odin it would say Fused 10 > Binary 4, for example. To be clear, the firmware that I am on is G935UUESACSF1.
The next thing I tried was to load a combination firmware. I used G935AUCUAASF1. That allowed me to load up "Factory Binary" and within that firmware I have access to the settings menu and IMEI dialer. I went into the menu, enabled developer options, and made sure that USB debugging was enabled. There was no option for "OEM Unlock". I used the dialer to bring up USB settings and set it to MTP+ADB. Then I brought up Z3X 29.5 thinking I would use the FRP unlock feature there. The SM-935A does not have a feature for that, but the SM-935T and F models do. So I took a risk and pulled up the T model and I selected FRP Reset. It did it's thing and it said that it was successful. I followed the instructions to do a factory data wipe directly after.
I wasn't sure what to do next, so I put the phone back into download mode and used ODIN to flash the 8.0 firmware back on. When that booted up, nothing had changed..it was still FRP locked. I'm not sure if I'm missing something in the process or what I should do next, if anything can be done. It seems I'm very limited in what I can do because from what it seems, I can't downgrade to a lower bootloader binary so I can't, for example, go back to 7.0 or 6.0.1. I can't even go back to earlier versions of 8.0 and try some of the tricks for those (like the S Voice Terms and Conditions trick..S Voice isn't listed during startup on my firmware)...
Anything that I can do? Any help is appreciated.

Can you get into custom recovery? If you can, flash no verity opt encrypt and it will be fixed or if not, also flash RMM bypass

freakwithracket said:
Purchased the phone off guy on Facebook. It appears that he wiped it without realizing about the FRP lock. It had 7.0 on it. I tried all the tricks you see on the youtube videos to bypass FRP but none of them worked. I know how to use ODIN and Z3X, so I flashed an 8.0 firmware thinking I would try some of the bypass methods for 8.0. Those didn't work so then I tried to move back to 7.0.....and then I learned that you can't downgrade bootloaders. In odin it would say Fused 10 > Binary 4, for example. To be clear, the firmware that I am on is G935UUESACSF1.
The next thing I tried was to load a combination firmware. I used G935AUCUAASF1. That allowed me to load up "Factory Binary" and within that firmware I have access to the settings menu and IMEI dialer. I went into the menu, enabled developer options, and made sure that USB debugging was enabled. There was no option for "OEM Unlock". I used the dialer to bring up USB settings and set it to MTP+ADB. Then I brought up Z3X 29.5 thinking I would use the FRP unlock feature there. The SM-935A does not have a feature for that, but the SM-935T and F models do. So I took a risk and pulled up the T model and I selected FRP Reset. It did it's thing and it said that it was successful. I followed the instructions to do a factory data wipe directly after.
I wasn't sure what to do next, so I put the phone back into download mode and used ODIN to flash the 8.0 firmware back on. When that booted up, nothing had changed..it was still FRP locked. I'm not sure if I'm missing something in the process or what I should do next, if anything can be done. It seems I'm very limited in what I can do because from what it seems, I can't downgrade to a lower bootloader binary so I can't, for example, go back to 7.0 or 6.0.1. I can't even go back to earlier versions of 8.0 and try some of the tricks for those (like the S Voice Terms and Conditions trick..S Voice isn't listed during startup on my firmware)...
Anything that I can do? Any help is appreciated.
Click to expand...
Click to collapse
can you Kindly Share the stock rom you used. i am having the Same issues. Thank you in advance .

I think i screwed myself (Galaxy S8 Root)

Hey i couldnt find anything else so i hope this isnt a duplicate,
im somewhat of a noob when it comes to rooting but i know a little bit
Today i rooted my Galaxy s8 , everything whet smooth and without a problem,
but then for some reason i deactivated the OEM unlock and rebooted my phone.
Obviously that locked me out of my phone, after trying to flash my phone with the stock firmware that i downloded through samfirm
i got the error sw rev check fail bootloader device 5 binary 4 and i couldnt get that to work.
My next step was to try the Samsung smart switch emergency recovery, which failed.
I got the error that my device was not supported.
After that my S8 also stared showing me a blueish screen with the message : "An error has occurred while updating the device software....",
i can still access downlod mode tho
At this point i really dont know what to do and i should really be in bed because its 2 in the morning .
I really hope someone can help me out here, thanks in advance and a good night for now.

Hirnvitamin said:
Hey i couldnt find anything else so i hope this isnt a duplicate,
im somewhat of a noob when it comes to rooting but i know a little bit
Today i rooted my Galaxy s8 , everything whet smooth and without a problem,
but then for some reason i deactivated the OEM unlock and rebooted my phone.
Obviously that locked me out of my phone, after trying to flash my phone with the stock firmware that i downloded through samfirm
i got the error sw rev check fail bootloader device 5 binary 4 and i couldnt get that to work.
My next step was to try the Samsung smart switch emergency recovery, which failed.
I got the error that my device was not supported.
After that my S8 also stared showing me a blueish screen with the message : "An error has occurred while updating the device software....",
i can still access downlod mode tho
At this point i really dont know what to do and i should really be in bed because its 2 in the morning .
I really hope someone can help me out here, thanks in advance and a good night for now.
Click to expand...
Click to collapse
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.

spawnlives said:
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
Click to expand...
Click to collapse
Thanks for your reply!
That's what I found out too but I couldn't find a "higher" bootloader, I would have thought that if I download it through SamFirm it should have the proper BL
Do you have any recommendations on where to download the proper bootloader?
Yea that was a big f**k up haha
I just tried to get Poke Go to run but it wouldn't let me login because it detected that the Device was rooted I guess and after changing my device fingerprint and adding PokeGo to MagiskHide and still not being able to login I followed some FAQ blindly Wich recommended to turn off OEM unlock, and other things to hide the hardware site or the root, thinking about it again it should have been super obvious that this is a stupid idea, but you are always smarter afterwards right? Haha

spawnlives said:
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
Click to expand...
Click to collapse
Wow I feel stupid, I'm flashing the stock through Odin right now as I type this, I've downloaded 2 firmwares first one was a random one from online second one was the SamFirm , after realizing the first didnt work I must have deleted the samfirm variant by accident, I redownloaded it and now it's working , but thanks for replying!